SilverStream eXtend Director
Version 4.0.1
Release Notes

October 2002

Welcome to SilverStream eXtend Director Version 4.0.1.

These Release Notes include the following sections:

Installing Director 4.0.1

This section discusses what you need to consider before running the Installation Wizard.

Director 4.0.1 requires Workbench 4.0.1. If you have not yet installed Workbench 4.0.1 when you install Director 4.0.1, the Installation Wizard will install Workbench before continuing with the Director installation.

Before you install

Before installing SilverStream eXtend Director 4.0.1:

• If you previously installed SilverStream eXtend Director Version 4.0, do the following before installing this version:

1. Uninstall SilverStream eXtend Director Version 4.0

2. Uninstall SilverStream eXtend Workbench 4.0

3. Delete the installation directory for Director 4.0 and Workbench 4.0

4. 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.

Understanding the differences between typical and custom installations

The Installation Wizard provides two installation options: Typical and Custom. If you choose the typical installation, all features of SilverStream eXtend Director are installed, including:

• SilverStream eXtend Director
• Documentation (including the API Reference)
• Autonomy DRE
• Cluster Cache Coordinator

If you do not want to install one or more of these components, you can choose the custom installation and omit them.

Software and database requirements

Application servers supported by Version 4.0.1

• SilverStream eXtend Application Server Version 3.7.5 and 4.0
• BEA WebLogic Server Version 6.1 Service Pack 2 and Version 7.0 Service Pack 1
  

  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.

• IBM WebSphere Server Advanced Edition Version 4.0.2

Operating systems supported by Version 4.0.1

• Windows NT 4.0, Windows 2000
• Solaris 2.6, 2.7, 8.0
• AIX 4.3
• HP-UX 11.0

Databases supported by Version 4.0.1

• Oracle 8.1.7 and 9i
• IBM DB2 7.1 (with FixPak 3) or 7.2

NOTE: You must use the JDBC2 option with DB2—JDBC1 is not supported

• Microsoft SQL Server 7.0/2000
• Sybase Adaptive Server Enterprise (ASE) 11.x/12
• Sybase Adaptive Server Anywhere 6.0 and 8.0

Web browsers supported by Version 4.0.1

• For the PAC and Portal tiers:
• Internet Explorer 5.0 and higher
• Netscape 6.x

NOTE: Netscape 7.0 is not supported.

• For the PMC:
• Internet Explorer 5.5 and higher

What’s new in Version 4.0

• Major Portal subsystem enhancements
• New Portal Personalizer
• New predefined layouts
• Wizards for creating custom layouts
• Portal themes for defining visual characteristics that apply to an entire portal application
• Portal decorators for rendering the title bars, bodies, and footers of components
• Portal options for adding actions to component title bars
• Support for Netscape 6.0 and higher
• Enhanced Director 4.0/Workbench 4.0 integration
• Redesigned Director EAR Wizard
• Resource set configuration tool
• Resource analyzers
• Relationship Viewer
• Resource set search facility
• Resource set views
• Transcoding editor enhancements
• Wireless device editor
• New sample components, workflow activities, and project templates, as well as enhancements to existing components and sample applications
• Dreamweaver extension for developing pages using PIDs
• RSS Feed capability to provide RSS channels from a content management query
• WebDAV XP support and enhanced move and delete capabilities
• Content Management subsystem enhancements
• Import and export facilities
• Portable Content Query Application (CQA) XML definitions that allow the same CQA settings to be used on different servers
• Search capability in the PMC
• Workflow and transcoding engine JSP tag libraries
• Major Workflow subsystem enhancements
• UI Binding Policy API
• New and updated samples
• Workitem reassignment
• Better rules engine integration
• Extended Engine API
• Enhanced exception handling
• Web Service activity
• Rules engine enhancements including new conditions, actions, and templatized fields
• Framework enhancements
• Enhanced resource set
• IPDR (Internet Protocol Detail Record) logging, used to record information about usage activity (see http://www.ipdr.org/)
• JAXP (Java API for XML processing) support, allowing pluggability of XML parsers and XSLT engines
• PAC enhancements
• Enhanced documentation and API Reference
• New SilverStream eXtend Director 4.0 tutorial delivered as part of the Director 4.0 online help

What’s new in Version 4.0.1

• J2EE 1.3 certification
• Support for the creation of 1.3 EARs that use Director services
• Director 1.3 EARs have been certified to run on SilverStream eXtend Application Server 4.0, BEA WebLogic 7.0, and BEA WebLogic 6.1 Service Pack 2
• Oracle 9i and Microsoft SQL Server type 4 driver support
• HP support for Autonomy
• Enhanced documentation and API Reference
• New chapter on Content Management import and export (Content Management Guide)
• Revised documentation on updating a Director EAR (Core Development Guide)
• New chapter on developing Struts applications that use Director services (Core Development Guide)
• New chapter on using the XML and IPDR logging providers (Core Development Guide)
• Updated documentation for core and sample components (Samples)
• Updated tutorial (Tutorial)
• Updated documentation on searching for numbers and searching in languages other than American English (Search Guide)
• Updated documentation on user management (User Management Guide)
• New Workflow tag library chapter (Workflow Guide)
• Updated documentation describing the Workflow Issue Tracking sample (Workflow Guide)
• Replacements for deprecated API classes and methods are now listed in the deprecated section (API Reference)
• Fixes for problems that existed in Director Version 4.0
• PPR # 34124: Upgrade Utility fails if any Portal WAR includes JSP pages mapped as servlets
• PPR # 33977: Unnecessary errors logged during runtime migration of multiple Portal WARs
• PPR # 33261: Help buttons not enabled in Director wizards within Workbench
• PPR # 33845: Tasks throw exceptions on WebLogic
• PPR # 33011: Internet Explorer 5.5 prompts for wrong file name when saving on export
• PPR # 34613: DRE service can't start on MBCS machine

Getting started

The Getting Started section of the SilverStream eXtend 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:

The Core Development Guide provides a more detailed presentation of Director functionality, architecture, and development environment and processes.

Converting existing Director applications

Upgrading Director 3.0 applications to Version 4.0

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.0.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.0.1, and use the Update facility of the Director EAR Setup wizard to update it to Version 4.0.1, as described below.

Updating Director 4.0 applications to Version 4.0.1

You can update Director 4.0 applications so they work with Director Version 4.0.1. To do this, you use the Director EAR Update facility of the Director EAR Setup wizard.

To update a Director 4.0 application to Version 4.0.1:

1. Back up your project.
2. In Workbench, select the Project>Director EAR>Setup menu option.
3. In the Director EAR Setup wizard, select Update, accept all the defaults, and click Next.
4. Make sure the Copy new files option is unchecked.
5. In the From location: box, enter the location of the templates folder in your Director installation, for example, C:\SilverStream\eXtendDirector\templates\Director.
6. In the To location: box, enter the location of the root of your EAR project, for example, C:\Director_Projects\My_Project.
7. If you would like to see what files will be updated before you actually perform the update, select the Trial and Create detailed log options and press Go. The Director EAR update facility writes a log with the details to the folder specified in the To location box.
8. To perform the update, deselect the Trial option and press Go. The Director EAR update facility writes a log with the details to the folder specified in the To location box.

IMPORTANT: If you've changed the default name of the Portal Web application, or if your project includes multiple Web applications, you will need to run the Update facility again after you have run it on the EAR, as described in the next procedure.

To update an individual Web application:

1. In the Update facility, enter the location of the Web application template directory in the From location: box, for example C:\SilverStream\eXtendDirector\templates\Director\Portal.
2. Enter the location of your Web application in the To location: box, for example C:\Director_Projects\My_Project\My_Portal.
3. Repeat this step for each Web application in your project that is not named Portal.

Updating projects from J2EE 1.2 to J2EE 1.3

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.

Known issues in Version 4.0.1

Director 4.0.1 known issues are described in the following sections:

• Updating from 4.0 to 4.0.1
• Director functionality
• Server issues—general
• Using Director with IBM WebSphere Server
• Using Director with BEA WebLogic Server

Updating from 4.0 to 4.0.1

• Product version number is not set correctly by the Update facility

  When you update a Director 4.0 application to work with Director 4.0.1, the update facility does not set the version to 4.0.1. You can fix this by hand editing the Framework config.xml file. To do this, change the value of the license.version property to 401.

Director functionality

• RSS requires manually created security role

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.0.1 projects that include the RSS component.

• Checkout status improperly cached after deleting an attachment in the PMC

This applies to Content Management documents that have attachments. After checking out the document in the PMC and deleting its attachment, the original document appears to still be checked out. To work around this problem, click Check-In. (PPR 33654)

• Layout styles not exported when exporting from a folder in the PMC

If a document's document type has a layout style associated with it and you export the folder containing the document, the layout style will not be exported. To ensure that the layout style gets exported, you can export the entire contents of the Content Management subsystem by clicking the Export button in the PMC toolbar. (PPR 33778)

• Document links not exported when exporting from a folder in the PMC

If you have created links between documents, the links will not be exported when you export from the folder containing the document, even if both documents are contained in the same folder. To ensure that links get exported, you can export the entire contents of the Content Management subsystem by clicking the Export button in the PMC toolbar. (PPR 33779)

• You cannot use extended characters in content management custom task names

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)

• Extended characters in document types and fields throw exceptions on import

When importing document types and fields that contain special characters, the import process throws an exception. (PPR 33889)

• You cannot import binary document formats on MBCS

MBCS binary data cannot be imported into the Autonomy DRE. Therefore, it is not possible to search on binary documents that have MBCS data. (PPR 34824)

• You cannot search custom fields with MBCS characters

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)

• Search results become invalid after you restart the Autonomy Dynamic Reasoning Engine (DRE)

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:

1. Remove all documents from the DRE.

2. Reconfigure the DRE by issuing a reset from the DRE Administration console.

3. Restart the DRE.

4. Reindex your contents back into the DRE.

These steps are described in detail in the "Troubleshooting" section of Chapter 1, "Using the Search Subsystem," 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.

• Full-text search may produce invalid results in the tutorial application

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.

• Autonomy search database can get out of sync when transaction times out on Solaris

  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 Content Management 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)

• Autonomy-based search is not supported on AIX

Autonomy-based Search subsystem capabilities are not supported on the AIX operating system.

• Workflow subsystem does not support server clustering

Certain aspects of the Workflow subsystem are not enabled for cluster support. (PPR 31584 and 34053)

• Extends chain for interfaces not fully expanded

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.

• Using EJB wrappers not fully supported

Director manager APIs contain EJB wrappers. However, since this feature has not completely gone through the QA process, SilverStream does not officially support their use in Version 4.0.1.

• Deprecated call to EbiSecurityManager has been removed

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)

• Final release of KBase sample application

Director 4.0.1 includes the final release of KBase. KBase will not be supported in the future.

• You cannot use multibyte characters in the XML editors

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.

• You cannot use multibyte characters in the Portal Personalizer

In the Portal Personalizer, you cannot create a user or group page with a name or description containing extended or multibyte characters. (PPR 33514)

• Portal Personalizer loses changes when user presses Enter key

If the user presses the Enter key after typing a user page name in the Page Name field on the Portal Personalizer page, the page will be reloaded and changes will be lost. This problem may also occur in the Description field. If you use the Enter key in these fields, the page will be unusable. (PPR 33600)

• Spaces in path names

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.

• Tag libraries are marked as 1.1 (J2EE 1.2) for J2EE 1.3 projects

  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 and 35011)

Server issues—general

• KBase application does not work out of the box

The KBase application does not work out of the box because of a problem with localization. The kb_maint page fails to initialize and the KBase application is not functional.

For localization to work, the EboLocalization class and the resource files need to be at the same level within the EAR. This is not the case in the KBase application. In this application, the resource files are contained within a WAR. When the resource files are placed within a WAR, they cannot be found since EboLocalization is in the FrameworkService.jar file, which is maintained at the EAR level. To ensure that the resource files are found, you need to put them in a separate JAR and include this JAR at the EAR level within your project. (PPR 34392 and 34339)

• Calendar component does not work on DB2

When running the Calendar component on IBM DB2, a stack trace is generated when you click a date in the calendar. (PPR 34963)

• Calendar and PhoneList components do not work on ASE 12.0

The Calendar and PhoneList components do not work properly on Sybase ASE 12.0. When you try to add an event using the Calendar component, the operation fails and an empty browser window is displayed. If you execute a Find operation using the PhoneList component, the operation does not return any results. (PPR 35051)

• When you are using an Oracle database, data is not loaded in tables with more than one LONG-datatyped column

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)

• You must use Oracle_schema.sql when using an Oracle database with a custom subsystem

When you are using an Oracle database, the data load process always uses Oracle_schema.sql and never uses OracleThin_schema.sql. If you have created a custom subsystem, make sure your schema file is named Oracle_schema.sql regardless of the driver you use. The database schema files are located in the library/subsystemname-conf/database directory of your Director project. (PPR 33280)

• Memory leak on redeployment

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 using Macromedia UltraDev

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.

• Using WebDAV with WebFolders on Windows 2000

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.

Using Director with IBM WebSphere Server

• Using WebDAV functionality to add content names that contain spaces or special characters

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.

• Using WebDAV functionality to view content

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/RootCollection

Using http://hostname/earnamespace/WebDAVService/main does not allow access to content stored in the RootCollection folder.

• Deploying Director EARs

You can deploy only one Director EAR to a given WebSphere server.

• Unnecessary exception thrown when a component is first loaded

On WebSphere, an IllegalStateException is thrown the first time a component is loaded. This exception is harmless—you can ignore it. (PPR 33859)

• Use the same database type for the administrative database and the Director database

SilverStream recommends using the same database type for the administrative database and the Director database when you use WebSphere. Using different databases—for example, DB2 for the WebSphere administration database and Oracle for the Director application database—will result in exceptions when you set the custom security realm. This is due to a limitation in the way WebSphere 4.0.2 handles two-phase commit (XA) drivers. (PPR 29217)

IBM has stated that this problem will be addressed by version 4.0.3 or 4.0.4 with an eFix. However, this has not been verified. Director 4.0.1 is certified to work with Version 4.0.2 of WebSphere.

• Login possible on WebSphere with invalid password

WebSphere has a bug that makes it possible for an existing user to log in to the PAC using an invalid password. (PPR 34458)

IBM has stated that this problem will be addressed by version 4.0.3 or 4.0.4 with an eFix. However, this has not been verified. Director 4.0.1 is certified to work with Version 4.0.2 of WebSphere.

Using Director with BEA WebLogic Server

• Director supports Compatibility Realm only on 7.0 Service Pack 1

  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:
  1. Install and start the WebLogic 6.1 Service Pack 2 application server.
  2. Configure the 6.1 Service Pack 2 server to run Director, as described in Chapter 14, "Deploying a Director Application," in the Core Development Guide.
  3. Deploy a Director project to the 6.1 Service Pack 2 server.
  4. Create default users using the DirectoryInitServlet, as described in Chapter 14, "Deploying a Director Application," in the Core Development Guide.
  5. Test the deployment by browsing to a Director subsystem that forces the use of security, such as the Portal Administration Console (PAC) or the Portal Management Console (PMC).
  6. Stop the 6.1 Service Pack 2 server.
  7. Install the WebLogic 7.0 Service Pack 1 application server in a directory other than where the 6.1 Service Pack 2 is installed.
  8. Back up the existing 6.1 Service Pack 2 domain by making a copy of the directory mydomain under the same parent directory config.
  9. In the original 6.1 Service Pack 2 installation directory, open the command file StartWebLogic.cmd in the mydomain directory and change the following settings:
     • Modify -Dbea.home to point to the WebLogic 7.0 Service Pack 1 installation directory.

       For example, if you installed the 7.0 server to c:\bea7, the setting should read:

       -Dbea.home=c:\bea7

     • Define WL_HOME after the line that begins with set JAVA_HOME=, as follows:

       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

     • Modify the PATH to point to the WebLogic 7.0 Service Pack 1 bin directory, as follows:

       set PATH=%WL_HOME%\bin;%PATH%

     • Modify the CLASSPATH to point to the 7.0 versions of weblogic_sp.jar and weblogic.jar, as follows:

       set CLASSPATH=%WL_HOME%\lib\weblogic_sp.jar;%WL_HOME%\lib\weblogic.jar

     • Modify JAVA_HOME as follows:

       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

     • Change the security policy to the 7.0 version as follows:

       -Djava.security.policy==%WL_HOME%/lib/weblogic.policy

  10. Save your changes to StartWebLogic.cmd.
  11. Start the 6.1 Service Pack 2 server. When prompted, enter your 6.1 Service Pack 2 user and password.
  12. Start the administrative console. The 7.0 Service Pack 1 console appears.
  13. Verify that the project is deployed, by following these steps:
      • Verify that CompatibilityRealm appears under Security/Realms.
      • Browse to http://server:7001/Portal/main. The default main page for your Portal application should appear.

        NOTE: If the name of your custom application is not Portal, substitute your name in the URL above.

      • Browse to http://server:7001/PMC/main and log in as a user with administrative privileges for the Portal Management Console (PMC). The main page for the PMC should appear.

• You cannot export Content Management data from the PMC with WebLogic

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)

• Server clustering does not work with WebLogic

Due to limitations of the WebLogic API, server clustering does not work with WebLogic.