December 2002
Welcome to Novell® exteNd™ Director Version 4.1.
These Release Notes include the following sections:
| Installing Director 4.1 | A listing of what is required before starting the Installation Wizard, and a description of the differences between typical and custom installations |
| Software and database requirements | A listing of application servers, operating systems, databases, and browsers supported by this version of Novell exteNd Director |
| What's new in Version 4.0 | A listing of the new features in the 4.0 version of SilverStream eXtend Director |
| What's new in Version 4.0.1 | A listing of the new features in the 4.0.1 version of SilverStream eXtend Director |
| What's new in Version 4.1 | A listing of the new features in the 4.1 version of Novell exteNd Director |
| Getting started | Directions to introductory documentation on using Director |
| Converting existing Director applications | Information about converting Director applications to Version 4.1 |
| Known issues for 4.1 | Descriptions of known problems with this version of Director, providing workarounds if available |
This section discusses what you need to consider before running the Installation Wizard.
Director 4.1 requires Workbench 4.1. If you have not yet installed Workbench 4.1 when you install Director 4.1, the Installation Wizard will install Workbench before continuing with the Director installation.
Before installing Novell exteNd Director 4.1:
If you previously installed SilverStream eXtend Director Version 4.0 or 4.0.1, do the following before installing this version:
Uninstall SilverStream eXtend Director Version 4.0 or 4.0.1.
Uninstall SilverStream eXtend Workbench 4.0 or 4.0.1.
Delete the existing installation directories for Director and Workbench.
Reboot your machine.
If you intend to use the Cluster Cache Coordinator feature of Director (which is enabled by default), you must determine what RMI port the Cluster Cache Coordinator will use.
The default RMI port value is 5449.
Have your license string ready.
The Installation Wizard provides two installation options: Typical and Custom. If you choose the typical installation, all features of Director are installed, including:
If you do not want to install one or more of these components, you can choose the custom installation and omit them. You might also want to choose the Custom option if you want to change any of the default settings for the Installation Wizard.
NOTE: The Compatibility Realm is the only supported realm for Version 7.0 Service Pack 1. See instructions for configuring your Version 7.0 server to run with Director.
NOTE: You must use the JDBC2 option with DB2—JDBC1 is not supported
NOTE: Netscape 7.0 is not supported.
NOTE: The Base LDAP and PersistManager realms are appropriate when you don't need any application server security integration. When you use either of these realms, the principal is not bound to the session once authenticated.
The Getting Started section of the Director online help provides an overview of Director capabilities, instructions on how to quickly build and deploy a Director application, and links to more information about Director. The Getting Started section includes these topics:
| Welcome | Provides a high-level summary of Director features and some quick links to introductory information. |
| Where to Begin | Describes the recommended paths to follow in the documentation based on your level of expertise and what you want to know about Director. |
| Release Notes | Opens these Release Notes. |
| Quick Start | Serves as a primer for experienced J2EE programmers who want to begin using Director immediately. Provides instructions on how to create, deploy, and examine a complete Director application. |
| Help and Documentation | Provides instructions on how to use Director online help. Also includes Novell legal, trademark, and copyright information. |
| Novell Links | Provides links to the Novell home page and the Novell DevCenter. |
The Core Development Guide provides a more detailed presentation of Director functionality, architecture, and development environment and processes.
You can convert Director 3.0 applications to Director Version 4.0 by running the Upgrade utility. For detailed information about planning and procedures required to upgrade existing applications, see the Upgrade Guide.
NOTE: You cannot run the Upgrade utility in Version 4.1. You need to have Version 4.0 of Director installed to run the Upgrade utility.
Once you've upgraded a 3.0 application to Version 4.0, you need to uninstall Version 4.0, install Version 4.1, and use the Update facility of the Director Project Setup Wizard to update it to Version 4.1, as described below.
You can update Director 4.0 and 4.0.1 applications so they work with Director Version 4.1. To do this, you use the Director Project Update facility of the Director Project Setup Wizard.
To update a Director 4.0 or 4.0.1 application to Version 4.1:
IMPORTANT: If you've changed the default name of the Portal Web application (Portal), or if your project includes multiple Web applications, you will need to run the Update facility again after you have run it on the project, as described in the next procedure.
To update an individual Web application:
Post-update procedures
After using the update facility, you need to edit a few of the Director XML files by hand. These hand-editing procedures are described below.
Editing the realm name: As part of the rebranding for 4.1, the names for Director realms have changed. The realm name is stored as a value in the Directory service config.xml file:
<property>
<key>com.sssw.fw.directory.api.EbiSilverServerRealm</key>
<value>exteNd Server</value>
</property>
This file is not altered as a result of update. Instead, the old name is retained, as shown below (PPR 35589):
<property>
<key>com.sssw.fw.directory.api.EbiSilverServerRealm</key>
<value>SilverStream</value>
</property>
Therefore, you need to change this value by either editing the config.xml directly or by using the Director project configuration editor to reselect the correct value and save it. If you do not change this value, you will have problems when you open the XML file. When you open an XML file that contains the old value, the editor will not find an appropriate match and the first realm in the list (LDAP) will be displayed as the selected value.
Editing the version and license string: When you update a Director 4.0 or 4.0.1 application to work with Director 4.1, the Update facility does not set the version and license string to work with 4.1 (PPR 35549). You can fix this by editing the Framework config.xml file. To set the version, change the value of the license.version property to 410. To set the license string, change the value of the license.string property to the license string you were given.
To update a project from J2EE 1.2 to J2EE 1.3, right-click the SPF file name in Workbench and select Update Project Version. The Workbench documentation provides complete details on migrating from J2EE 1.2 to J2EE 1.3. For more information, see "How to handle J2EE versions" in Getting Started in Workbench online help.
Director 4.1 known issues are described in the following sections:
When you deploy a Dlite WAR to a clean database, the default group page is blank the first time you go to the Portal Personalizer. In addition, the PAC indicates that no group pages are available. To work around this problem, go to the myPortal page first, then log in and go to the Portal Personalizer (or the PAC). When you do this, you should see the default group page. Once you've done this, you can go to the Portal Personalizer directly and you will see the default group page. (PPR 35588)
When you select exteNd Server (compatible) as the realm for a Director application, the data source name for the Directory subsystem is set to SilverMaster. You need to change this so that it matches the actual name of the data source (for example, SilverMaster40). (PPR 35666)
To change the data source, open the config.xml file in the directoryservice-conf folder and change the value of the DirectoryService/realms/silverusers/datasource key so that it includes the actual name of the SilverMaster database. For example, to set the data source to SilverMaster40, you would change the value to Databases/SilverMaster40/DataSource.
When you remove a user from a directory with LDAP, the cache is not updated properly the first time you start your server after deployment. To remedy this problem you can flush the cache in the PAC, as follows:
Click General Configuration in the PAC.
Open the Cache tab.
Open the Cache Holders tab.
Click the Flush Cache button.
This problem only occurs the first time you start your server after deployment. (PPR 35671)
If you export a CM folder that contains a subfolder, the access control lists (ACLs) for the main folder are exported, but the ACLs for the subfolder are not. Instead, the subfolder inherits its parent folder's ACL. (PPR 35672)
If you export a folder that contains a document that has been assigned to a category, the ACLs for the category will not be exported. (PPR 35673)
The Directory subsystem allows you to remove Director Locksmith users and groups. However, you need to be very careful when removing Locksmiths. Make sure you keep at least one Locksmith user. Otherwise, security will be open to everyone.
If you need to remove a Locksmith user from the Directory service, remove the user first from the Locksmith ACL list defined by the Security service. These are the steps for removing a Locksmith user from the PAC:
Go to the PAC.
Click the Security Management icon at the top. Select locksmithElementType, and remove the user from the list.
Click the Directory Management icon at the top. Remove the user from the realm.
Also make sure you have at least one user remaining in the Locksmith ACL list. Otherwise, security will be open to everyone.
On Netscape 6.1 and 6.2, you cannot drag and drop components in the Layout Selector. Instead, you need to select a component by clicking on it, then click the section you want to move the component into. This has the same effect as dragging and dropping a component. (PPR 35054)
The EbiUserQuery interface provides three methods that select entries based on a specified userID value. The methods are whereUserID( ), whereUserIDBetween( ), and whereUserIDIn( ). These methods will return correct results if the userID values are specified as simple string values such as "mary" or "John Smith." However, if the value is provided in full LDAP 'dn' format such as "cn=john smith,ou=marketing,o=novell", only the 'cn' portion of the string will be used in the query search operation. This issue will be resolved in a future release as directory servers add support for extensible match filters. (PPR 35464)
If a Windows Web folder contains documents with extended characters (such as MBCS or French with accents), you will not be able to connect the folder to the Director WebDAV server. (PPR 33640)
When you configure the data import descriptor (contentmgmt_did.xml) to overwrite all existing elements in the CM repository, the content importer attempts to delete existing elements before importing new elements. If the CM repository contains layout styles or document types with associated layout styles, an exception may occur during import. (PPR 35542)
There are two workarounds:
Configure the data import descriptor (DID) not to overwrite layout styles or document types.
In the PMC, remove the layout style descriptors associated with layout styles before importing content with overwrite enabled for layout styles and document types.
This version of Director does not provide support for BLOB datatypes in Oracle. (PPR 30931)
When upgrading an application that uses the RSS component, in order to authorize users and/or groups to delete RSS URLs from the RSS table in your Director database, you need to create a security role called RSSAdmins. You should give it the description Administrators who can delete RSS URLs. You can then add users and/or groups to this role. For information on role-based security and creating security roles, see Chapter 4, "Role-Based Authorization," in the User Management Guide.
NOTE: You do not need to create this security role for new projects. The RSSAdmins security role is automatically created for new 4.1 projects that include the RSS component.
If a custom task name includes extended characters, you cannot access the Task tab in the PMC. An exception is thrown. An exception is also thrown when a query is embedded in a task definition and the <content-search> tag contains extended characters. (PPR 33922)
When importing document types and fields that contain special characters, the import process throws an exception. (PPR 33889)
If you use the PMC to add a custom field that has a name containing MBCS characters, you will not be able to search on this field. (PPR 34819)
Because of the way Autonomy handles custom fields (metadata), you will get invalid search results if you add new custom fields to the content repository after creating documents that use a preexisting set of custom fields. (PPR 32009)
To recover, you must reinitialize the DRE to read in the new field set—as follows.
To reinitialize the DRE to read in the new field set:
Remove all documents from the DRE.
Reconfigure the DRE by issuing a reset from the DRE Administration console.
Restart the DRE.
Reindex your contents back into the DRE.
These steps are described in detail in Chapter 8, "Troubleshooting the Conceptual Search Process," in the Search Guide.
IMPORTANT: You must perform these steps every time you add new fields after creating documents that use custom metadata. To avoid the problem, add all custom fields before adding any documents in the content repository.
Because of the way Autonomy handles custom fields (metadata), you may get invalid results when you test the component that implements full-text search in Lesson 16 of the Director tutorial. The problem and workaround are described in Search results become invalid after restarting the Autonomy Dynamic Reasoning Engine (DRE), just above.
On Solaris, the process of importing content into the DRE database can sometimes take longer than on other platforms. If the server session timeout is set too low, the transaction may time out. This can cause a rollback, in which case the transaction doesn't complete and the CM database and the DRE database will have data that is not synchronized. To ensure that this does not happen, increase the session timeout interval on the server. For example, if you set it to 5 minutes, the transaction will most likely complete successfully. (PPR 35001)
Certain aspects of the Workflow subsystem are not enabled for cluster support. (PPR 31584 and 34053)
Due to a limitation in the version of Sun NetBeans used in Workbench, the extends chain for interfaces is not fully expanded. As a result, valid API calls may not show up as available when using code completion. See the Director API Reference for the full set of valid API calls.
Director manager APIs contain EJB wrappers. However, Novell does not officially support their use in Version 4.1.
The following deprecated API call has been removed from Director:
EbiSecurityManager.userHasAccessRight(EbiSession
sess, String right, String elementIID, String elementType)Instead you can use the method:
EbiSecurityManager.userHasAccessRight(EbiContext
ctx, String right, String elementIID, String elementType)
In Workbench, you cannot enter multibyte characters in the XML editors. To include multibyte characters in a Director XML file, you need to edit and save the file in an editor that has MBCS support, such as Notepad or Wordpad.
In the Portal Personalizer, you cannot create a user or group page with a name or description containing extended or multibyte characters. (PPR 33514)
There is a Workbench issue with spaces in path names to project directories that may cause single-file compiles to fail. This happens because of a reported Sun bug (4272706), which is scheduled to be fixed in JDK 1.4. To work around this problem, avoid using spaces in path names to project directories.
If you add a tag library to a Director project, the TLD file for the library is marked as 1.1 (J2EE 1.2) regardless of which J2EE version was specified for the project. Typically, this will not present a problem at deployment time, as long as the DOCTYPE correctly specifies the DTD version being used. However, if you like, you can edit the DOCTYPE to specify the correct tag library DTD version (1.2) and URL for J2EE 1.3 projects. If you do this, you will also need to make some minor modifications to the elements in the TLD so that they conform to the format for 1.2 tag libraries. (PPR 34355)
When running the Calendar component on IBM DB2, a stack trace is generated when you click a date in the calendar. (PPR 34962)
The PhoneList component does not work properly on Sybase ASE 12.0. If you execute a Find operation using the PhoneList component, the operation does not return any results. (PPR 34941)
Oracle does not allow more than one column to have a LONG data type in any database table. In the data load process, an attempt to populate such a table fails: the table is created, but no data is loaded. There is no known workaround for this problem. (PPR 33425)
Deploying a Director EAR multiple times to the same server could cause a memory leak of approximately 10 MB on each redeployment. (PPR 32529)
Accessing WebDAV on any supported server from Macromedia UltraDev 4 requires you to be running UltraDev Version 4.01. In general, if you are using Dreamweaver, you must also use UltraDev 4.01.
If you intend to use WebDAV functionality with WebFolders on Windows 2000, you must install Windows Office 2000 SR-1a Service Pack on the computer running the server.
On WebSphere, when switching themes, the user may see the following error in the WebSphere console:
[6/18/02 23:39:36:193 EDT] 3112fd79 SystemOut U java.lang.IllegalStateException:
ERROR: Cannot set header. Response already committed.
This error is harmless—you can ignore it. (PPR 33766)
WebSphere has a bug that causes content with names containing spaces or special characters (like % signs) to be URL encoded when added via WebDAV. On WebSphere, extra path info on the URL is URL-encoded, but on other application servers it is not. For example, if you add a folder to your Content Management repository via WebDAV that is called My Folder, the folder My%20Folder is actually added to your repository.
When using a browser to view content using WebDAV, you must include the first folder under the repository root in the URL. For example, if you have a top-level folder in the default repository called RootCollection, you must use this URL:
http://hostname/earnamespace/WebDAVService/main/RootCollectionUsing http://hostname/earnamespace/WebDAVService/main does not allow access to content stored in the RootCollection folder.
You cannot deploy more than one Director EAR to a given WebSphere server if these EARs access the same data source. You can deploy multiple Director EARs to WebSphere, as long as these EARs use different data sources.
On WebSphere, an IllegalStateException is thrown the first time a component is loaded. This exception is harmless—you can ignore it. (PPR 33859)
You can use Director on WebLogic 7.0 only by migrating from WebLogic 6.1 Service Pack 2. This section describes the procedure to follow.
To configure WebLogic 7.0 to run with Director:
For example, if you installed the 7.0 server to c:\bea7, the setting should read:
-Dbea.home=c:\bea7
set WL_HOME=WebLogic 7.0 installation directory\weblogic700\server
For example, if you installed the 7.0 server to c:\bea7, this line should read:
set WL_HOME=c:\bea7\weblogic700\server
set PATH=%WL_HOME%\bin;%PATH%
set CLASSPATH=%WL_HOME%\lib\weblogic_sp.jar;%WL_HOME%\lib\weblogic.jar
set JAVA_HOME=WebLogic 7.0 installation directory\jdk131_03
For example, if you installed the 7.0 server to c:\bea7, this line should read:
set JAVA_HOME=c:\bea7\jdk131_03
-Djava.security.policy==%WL_HOME%/lib/weblogic.policy
NOTE: If the name of your custom application is not Portal, substitute your name in the URL above.
When you export from the PMC using WebLogic, no data is saved to the export ZIP file, even though it appears that the ZIP file is being saved properly. You can import data from a correctly structured ZIP file on WebLogic—but the security and admin parts will not be valid. (PPR 33628)