Novell
exteNd Director
5.2.1 RELEASE NOTES
March 2005
Welcome to Novell® exteNd DirectorTM (Version 5.2.1). These release notes include the following sections:
Important note about
5.2.1 documentationWhere to find information about Version 5.2.1 of Novell exteNd Installing exteNd Director How to prepare for installing Novell exteNd Director System requirements Software and hardware needed to run Novell exteNd Director What's new in 5.2 New features in Version 5.2 of Novell exteNd Director What's new in 5.2.1 New features in Version 5.2.1 of Novell exteNd Director Documentation updates Updates to the documentation for Novell exteNd Director Known issues Known problems with this version of Novell exteNd Director Problems fixed in Version 5.2 Problems that have been fixed in 5.2, including problem numbers Problems fixed in Version 5.2.1 Problems that have been fixed in 5.2.1, including problem numbers Release note updates To check for updates to these release notes, click here.
Documentation specific to the 5.2.1 maintenance release of exteNd is provided in the product release note files:
- exteNd Suite Release Notes
- exteNd Director Release Notes (which you are reading now)
- exteNd Composer Release Notes
- exteNd Application Server Release Notes
These files include:
- Directions for upgrading to 5.2.1
- Descriptions of new features
- Added information about some existing features
The other exteNd help and PDF files are still primarily at the 5.2 level; they have not been updated to reflect 5.2.1 product changes (except where noted).
For a complete guide to installing exteNd Director and the exteNdTM 5 Suite, see Installing Novell exteNd in the exteNd 5 Suite help.
Upgrading your exteNd Director applications
When moving to the new exteNd version (5.2.1), you must also think about upgrading your existing exteNd Director applications as needed. For details, see the Upgrading exteNd Director applications guide.
This section describes the software and hardware needed to run exteNd Director:
Development environment
System requirements for the development environment are listed in the exteNd Suite Release Notes.
Server environment
System requirements for the server environment are listed in the exteNd Suite Release Notes.
For information about new 5.2 features, see What's New in the exteNd Director help.
This section describes the new features of exteNd Director for 5.2.1:
New Content Administration portlets available
exteNd Director 5.2.1 provides new Content Administration portlets called CAP portlets that allow you to access basic content management functions directly from a shared or personal portal page in any browser and operating system supported by exteNd Director 5.2.1. In earlier releases of exteNd Director you were restricted to the Content Management section of the Director Administration Console (DAC). This tool runs only in Windows, requires Internet Explorer version 5.5 or higher, and is available only to administrators.
For information about how to use the new CAP portlets, see Content Administration Portlets.
Upgrade to Autonomy Suir Server
exteNd Director 5.2.1 incorporates a new version of the Autonomy search engine called Suir Server version 5.0, which is part of the Autonomy IDOL search engine product suite. Advantages of the Suir Server include the ability to process custom field automatically and an easier install process on Linux. The Suir Server replaces Autonomy DRE Server version 3.x, the server supported by earlier versions of exteNd Director.
For information about how to install and use the Autonomy Suir Server, see Changes to the Autonomy Search Engine.
exteNd Director no longer requires a global transaction manager
Significant imrovements have been made in the way exteNd Director uses database connections. Because of these improvements, exteNd Director no longer needs a global transaction manager. The Enable User Transaction Support checkbox has been removed from the Framework Configuration panel of the Project Wizard. In release 5.2.1, Director always uses a single database connection to make database changes and perform commit and rollback operations.
To ensure that database connections are handled properly by the application server, you need to disable Global Transaction (XA) support for a connection pool used with a Director application. (PPR 41525, 48619, and 45755)
XForms plug-in available
You can now download and install an XForms client-side processor plug-in for MS Internet Explorer. It is available at: http://developer.novell.com/xforms.
If you have been using an earlier version of the XForms plug-in, make sure you get the current version to ensure proper operation with exteNd 5.2.1 and with EPM (Novell Enhanced Provisioning Module for NsureTM Identity Manager).
(PPR 47741, 49171)
Portal Data Import utility has been enhanced
The Portal Data Import utility (available via the Director Administation Console) now allows you to specify:
- Whether to import security settings
Choose Yes only when the security realm of the imported artifacts matches a security realm on the target server and you want to import the existing security settings for the pages and portlets in the source .zip file. When you choose yes, you are prompted to specify whether to import user settings and/or group settings.
If the security realms to not match, choose No.- Whether to overwrite existing data if objects of the same name and type exist in both the import file and the target server.
- The access level for imported objects.
The options are: All users or Administrator only.
If you chose to import security, then the access level is only applied to the imported objects where a security setting failed to be imported. If you chose not to import security settings then the access level is applied to all objects that are imported.- How to map the portlet application names in the archive to existing portlet applications on local server.
(PPR 48507)
exteNd Director no longer supports EAR namespacing
The EAR namespacing panel in the Director project wizard has been removed.
Discussion Forum portlet available
A new Discussion Forum accessory portlet is available. This portlet allows users to share open discussions.
When a user chooses a forum from the discussion forum list, a list of messages in that discussion appears. The list includes all the main messages and shows the orginator of each message and the number of replies. Discussion threads are displayed in tree view form.
Users can display any message or reply at any time by clicking its title, which shows the author and creation date. When a message is displayed, the details (author, subject, date and abstract) appear in the first section. The content of the message is displayed with the option to make a direct reply to it.
NOTE: Each instance of this portlet must be assigned a unique name before the instance will run on a portal page:
- After selecting the Discussion Forum portlet for your portal page in the Content Selector, click the Content Preferences link to display the Content Preferences dialog.
- Enter a name for this portlet instance in the Unique name for this portlet field and click Save Preferences to return to the Content Selector.
(PPR 48843, 48833)
The following updates apply to the documentation and help for exteNd Director:
Specifying a Webserver URL for the NetStorage portlet
To specify the NetStorage Webserver URL in NetStorage portlet preferences, enter only your host name, in this format:
http://hostname
. Do not enterhttp://hostname/NetStorage
. The portlet automatically appends NetStorage to the URL. (PPR 49035)
Assigning Container and Shared pages as defaults for groups
Administrators can now assign a Container and Shared page as the default page set for all users in one or more groups. (PPR 48617)
To assign a default Container page to one or more groups, follow these steps:
- Log into your portal application with administrative privileges.
- Select Portal Administration, then choose Maintain Container Pages.
- Select the desired Container page from the Container Pages list.
- Click Group Defaults in the bottom right tool bar.
- In the Page Defaults dialog, select one or more groups and click > to add them to the Current Assignment list.
- Click Save, then click Close.
To assign a default Shared page to one or more groups, follow the same steps as for assigning a default Container page, except select Maintain Shared Pages as your Portal Administration tool.
XML Remote portlet documentation is missing file size limit
The documentation for the XML Remote portlet should have indicated that an out of memory error (java.lang.OutOfMemoryError exception) may occur when processing very large XML files. The error occurs immediately after the browser tries to open a page that uses the XML Remote portlet to process a large XML file.
XML files ranging from 9 to 12 megabytes in size consistently cause out of memory errors to occur. As a practical matter, you should try to keep the XML file size much smaller than this (below 2 megabytes). To ensure that out of memory errors do not occur with the XML Remote portlet, make sure that the HTML content sent to the browser is always meaningful to the user. Do not waste bandwidth by sending text that will never be read by the user. Also consider the number of concurrent users, the RAM available to the application server, and the number of machines available for processing if clustering is used. (PPR 48775, 48647, 48648)
Searching for a user profile when the Portal is configured for an LDAP realm
When your portal application is configured to use LDAP as the Directory Service and JDBC (not LDAP) as the user service and you want to search for a user profile, the search string must include the user DN format. For example, cn=a. The search will not return any results if you do not use this format. (PPR 49053)
Setting a default search string needs clarification
The Directory Administration Console (DAC) and Portal Administration tool provide text fields for searching for users, groups, and containers (LDAP only). By default, the fields are set to search for all users whose IDs start with the letter a. This default may return an inordinately large number of users for some organizations. (PPR 48668)
To change the default search string in the DAC, follow these steps:
- In your exteNd Director project, open WEB-INF/lib/PAC_resource.jar.
- Change the default searchstring value in the following files:
- AuthUserList.xml
- DirectoryDetails.xml
- DirectoryList.xml
- PacPrincipalMap.xml
- UserDetails.xml
- UserList.xml
- Redeploy the exteNd Director application.
- Restart the application server.
To change the default search string in the Portal Administration tool, follow these steps:
- In your exteNd Director project, open WEB-INF/portlet.xml.
- Search for PortalPagePermissions.
- Change the value of INITIAL_SEARCH_TEXT.
- Change the value of INITIAL_SEARCH_TYPE as needed.
- Redeploy the exteNd Director application.
- Restart the application server.
Naming security roles needs clarification
When you create a security role in exteNd Director, you must provide a display name for the security role in its descriptor file. However, the name of the security role is the root name of its descriptor file, not its display name. When you save the descriptor, the name of the descriptor file defaults to the display name, but you can substitute any file name you want. For example, if you create a security role with a display name of My Administrator, but save the descriptor to a file named MyAdmin.xml, the name of the security role is MyAdmin.
This point was not clearly stated in the User Management Guide and the Workflow Guide. (PPR 44238)
Content Search documentation does not clarify how documents are batched for deletion
You can configure the Autonomy search engine to batch up documents deleted from the content repository before removing them from the search server. The Content Search documentation explains that you implement this feature by enabling batch synchronization and specifying the number of documents to batch up in the configuration parameter com.sssw.cm.search.synch.removes.batch.size.repository. It is important to note that no documents are removed from the search server until the number of deleted documents equals the number specified plus one. For example, if you set the parameter to 100, the search engine does not remove any documents from the search server until 101 documents have been deleted from the content repository. Then, it removes the same 101 documents from the search server to synchronize with the content repository. (PPR 48876)
LDAP directory realm not FIPS-compliant
In exteNd Director project configuration, native LDAP access is not FIPS-140 compliant (because it uses JSSE and not Phaos). If you're using the exteNd Application Server, you can achieve FIPS-compliance by doing the following:
- Use the SMC (Server Management Console) to set up LDAP access on the application server (which is FIPS-compliant).
- Specify exteNd Server LDAP as the directory realm in your exteNd Director project configuration.
For more information on FIPS support, see the "Setting Up Security" chapter in the exteNd Application Server Administrator's Guide. (PPR 46501)
Troubleshooting your Server Accessible Temp Directory
Before you deploy an exteNd Director project to your application server, make sure you have specified a valid Server Accessible Temp Directory on the Framework Configuration panel in the Director Designer (select Project>Director>Configuration, then click Framework). If the specified path is not valid for the target server, the temporary directory and PortalCache subdirectory needed by exteNd Director won't be properly configured and accessible.
In particular, make sure the path syntax is correct for your server's operating system. For example, specify a Windows path (with backslashes) if the server runs on Windows. Specify a Linux path (with slashes) if the server runs on Linux. (PPR 48698)
Workflow documentation incorrectly states that addressee may be a group
The Workflow Guide states that an addresse for a workitem may be a user, group, or role name. This is incorrect. The addressee must be a user or role name.
Rules documentation makes reference to a RuleWrapper portlet that does not exist
The Rules Guide includes a statement about the RuleWrapper portlet, which is incorrect. Earlier versions of exteNd Director included a RuleWrapper component. This component has not been converted to a portlet, and is, therefore, not available with the product.
Documentation on getting fault information with a scoped path not provided
The Pageflow and Form Guide did not include information on how to get fault information by using a scoped path. To get this kind of information, you need to use the following scoped path expression:
/Flow/exception/FAULTThis expression returns a DOM that looks like this:
<?xml version="1.0" encoding="UTF-8"?> <m:FaultInfo xmlns:m="http://novell/extendComposer/SystemFault"> <m:DateTime>Wed Apr 21 20:09:59 BRT 2004</m:DateTime> <m:ComponentName>WebServiceTest</m:ComponentName> <m:MainCode>-1</m:MainCode> <m:SubCode>1</m:SubCode> <m:Message>Fault Error because num=3</m:Message> </m:FaultInfo>In this case, to get to the Message one can use the following scoped path expression:
/Flow/exception/FAULT/*[local-name()='FaultInfo']/*[local-name()='Message']/text()
Documentation on asynchronous portlet processing provides incorrect information about allocating threads
- The Portlet Guide identifies the element for allocating threads from the application server's thread pool as <backgroundThreadMax>. This is incorrect. The element is <backgroundThreadsMax>.
- The Portlet Guide incorrectly states that you should add the <backgroundThreadsMax> descriptor to your deployment plan after the <warJar> descriptor. Instead, you must add the <backgroundThreadsMax> descriptor inside the <warJar> descriptor, but not inside any other elements within that descriptor.
- The Portlet Guide does not indicate what happens if you do not add the <backgroundThreadsMax> descriptor to the deployment plan. If you omit this descriptor, your Web application will not be able to process portlets asynchronously because the application server assumes that it should not spawn additional threads for processing requests.
(PPR 48114)
There is a new property for enabling group membership caching
You can set a property in the Directory Service configuration file to cache groups and group membership lists. The property is called DirectoryService/Cache/GroupMembership and is disabled by default, as follows:
<property> <key>DirectoryService/Cache/GroupMembership</key> <value>false</value> </property>You should set this property to true to enable group membership caching in a clustered environment when you run the exteNd Application Server cache manager and exteNd Director Cache Coordinator. The Directory Service configuration file is located in your exteNd Director project at library/ConfigService.jar/DirectorService-conf/config.xml. (PPR 45265)
The code example that shows how to perform a SQL-based search of standard document metadata has been updated
The code example in the chapter Implementing SQL-Based Searching in the Content Search Guide has been updated to use new where methods and show how to iterate through the search results. (PPR 29351)
Here is the updated code:
public void executeDocMetaSearch(EbiContentMgmtDelegate cmgr, EbiContext context) throws EboUnrecoverableSystemException, EboSecurityException, EboItemExistenceException { // Search for all the Movie Review documents where // (Author is 'JSmith' or Title starts with 'A') // AND // where YearOfRelease is between the year 1990 and the year 2000. EbiDocQuery docQuery = (EbiDocQuery)cmgr.createQuery(EbiDocQuery.DOC_QUERY); docQuery.selectAll(); EbiQueryExpression expr = docQuery.whereDocTypeName("Movie Review", EbiDocQuery.ROP_EQUAL, false); EbiQueryExpression expr2 = docQuery.whereAuthor("JSmith", EbiDocQuery.ROP_EQUAL, false); EbiQueryExpression expr3 = docQuery.whereTitle("A", EbiDocQuery.SOP_STARTS_WITH, false); EbiQueryExpression expr4 = docQuery.whereFieldValueBetween_ByName("YearOfRelease", EboMisc.getInteger(1990), EboMisc.getInteger(2000), false); // (Author is 'JSmith' or Title starts with 'A) expr2.orExpression(expr3); expr2.parenthesize(); // (Author is 'JSmith' or whose Title starts with 'A') // AND // YearOfRelease was between the year 1990 and the year 2000 expr.andExpression(expr2); expr.andExpression(expr4); docQuery.setWhere(expr); // Sort results by creation date/time, in ascending order docQuery.orderByCreateDate(true); // Execute the search and filter the results based // on security constraints Collection results = cmgr.findElementsFiltered(context, docQuery); //Iterate through the results for (Iterator i = results.iterator();i.hasNext();) { EbiDocument result = (EbiDocument)i.next(); System.out.println(result.getName()); } }
Shared library configuration and IBM WebSphere Application Server realms
The documentation that describes when a shared library configuration is required for the IBM WebSphere Application Server in Developing exteNd Director Applications needs further clarification. An exteNd Director project requires a shared library configuration when you choose WebSphere realm as the project's Directory Realm specification. It is not required when you are deploying to an IBM WebSphere application server that uses WebSphere custom realm that you have written. (PPR 48651)
XForms and alert messages
XForms generated via the XForms Designer Wizard automatically include two default alert messages. These messages are displayed for invalid data and for invalid submission elements. The default messages apply to all controls on the form.
You can also create custom alert messages for specific controls. To find out more about adding custom alert messages for individual controls in the Pageflow and Form Guide. When you add a custom alert message for an individual control, the default alert message displays before the custom alert message. If you want only the custom alert message to display then you must remove the default invalid data entry message. Removing the default message also removes the invalid data action from the form. This means that you will have to add custom alert messages for all of the other controls that should display an error message when invalid data is entered.
Here are the steps for removing the default alert message:
- Open the form in the Form Designer.
- Click the Model tab.
- Expand the Actions node.
- Click on the message entry.
- Identify the default alert message action. (It is typically associated with the first Actions node. The text is "The data is invalid. Please check it and try again".)
- Select the action, and delete it.
- Save the form.
(PPR 48442)
WebDAV Client API
The exteNd Director API for developing custom WebDAV clients for the exteNd Director Content Management (CM) subsystem is no longer supported. You can use other third pary or open source WebDAV clients to develop this functionality. (PPR 45209)
Using the exteNd LDAP Realm
If you deploy an exteNd Director application with an exteNd LDAP realm and SSL enabled, you must import the LDAP server's CA cert to the exteNd Application Server. The instructions for importing the CA cert are included in the chapter on deploying exteNd Director Applications in Developing exteNd Director Applications. However, the instructions for using the keytool command leave out an important parameter called -trustcacerts. Here is an example of the command using this parameter:
keytool -import -trustcacerts -alias aliasName -file certFile -keystore cacerts -storepass changeit(PPR 45710)
Content Management Importer/Exporter Sample Files
The Content Management Guide provides incorrect names for the Data Export Descriptor (DED) sample files. It states that the samples are:
contentmgmt-export-descr_5_0_sample.xml
contentmgmt-export-descr_5_0_sample2.xml
contentmgmt-export-descr_5_0_sample3.xml
contentmgmt-export-descr_5_0_sample4.xml
contentmgmt-export-descr_5_0_sample5.xml
The samples are actually:
contentmgmt-export-descr_4_0_sample.xml
contentmgmt-export-descr_4_0_sample2.xml
contentmgmt-export-descr_4_0_sample3.xml
contentmgmt-export-descr_4_0_sample4.xml
contentmgmt-export-descr_4_0_sample5.xml
They are still located in the library/ContentMgmtService/ContentMgmtService.spf/DTD directory. (PPR 47351)
Documentation describing simultaneous logout from Director and iChain contains an error
In the User Management Guide, there is a section that talks about simultaneous logout from exteNd Director and iChain. It has the following statement:
To work with iChain, exteNd Director must be using the same eDirectory realm as the iChain server.This statement is incorrect and should not have been included in the documentation. (PPR 48820)
The code example that shows how to assign ACLs to content elements has been updated
The code example on assigning ACLs in the chapter Securing Content in the Content Search Guide has been updated to use new API methods and illustrate the following techniques:
- Using a security delegate to add principals to an element in the Content management system, in this case a folder
- Using a directory delegate to obtain a list of principals in the Directory Realm
- Adding a folder with no ACL (inherits the ACL from its parent folder)
- Assigning ACLs to a folder
(PPR 48615)
The technique for adding principals to an element in the content management system is to call the method addPrincipalsToAcl() on a security delegate, as follows:
EbiSecurityAclDelegate delegate = com.sssw.fw.security.client.EboFactory.getSecurityAclDelegate(); delegate.addPrincipalsToAcl(context, elementIID, elementType, permission, principalUUIDs, type);
Here is a description of each argument in this method:
Argument Description context Portal Context (EbiContext or EbiPortalContext) elementIID Id of the content element, in this case a folder (folder.getID()) elementType Type of element, in this case a folder (EbiDocFolder.EL_DOC_FOLDER) permission Type of permission: LIST, PROTECT, READ, WRITE, or PUBLISH (for documents only). Permission types are obtained via EbiDocFolder.LIST, EbiDocFolder.PROTECT, EbiDocFolder.READ, EbiDocFolder.WRITE, and EbiDocument.PUBLISH.
principalUUIDs Array of type String that contains the Directory Realm UUIDs of the users, groups, or containers (for LDAP) to be added to the ACL elementType Type of principal to be added to the ACL: user, group, or container (for LDAP). Principal types are obtained via EbiDirectoryConstants.FW_PRINCIPAL_USER, EbiDirectoryConstants.FW_PRINCIPAL_GROUP, and EbiDirectoryConstants.FW_PRINCIPAL_CONTAINER
Here is the updated code example, which uses these techniques to show how to create private folders for a set of principals. Note that context is passed as an argument.
import java.util.*; //Portal/Framework/Content Management imports import com.sssw.cm.api.*; import com.sssw.fw.security.api.*; import com.sssw.fw.directory.api.*; public void addACLsToFolder(EbiContext context,) throws EboUnrecoverableSystemException, EboSecurityException, EboItemExistenceException, EboFactoryException, NotOwnerException { // Get the Content Manager and save the root folder EbiContentMgmtDelegate cMgr = com.sssw.cm.client.EboFactory.getDefaultContentMgmtDelegate() ; EbiDocFolder rootFolder = cMgr.getRootFolder(context); // Grab the Security Delegate in order to assign the ACLs EbiSecurityAclDelegate delegate = com.sssw.fw.security.client.EboFactory.getSecurityAclDelegate(); // Get the Directory Delegate in order to obtain the list of users EbiDirectoryDelegate dirMgr = com.sssw.fw.directory.client.EboFactory.getDirectoryDelegate(); // Get the List of Users Collection users = dirMgr.getUsers(context); // For each user, create a folder and make sure that only that user can act on that folder for (Iterator iter = users.iterator(); iter.hasNext(); ) { EbiRealmUser user = (EbiRealmUser) iter.next() ; //Create a folder with no ACL; it inherits the ACL from its parent folder EbiDocFolder userFolder = cMgr.addFolder(context, rootFolder, user.getShortName(), EbiDirectory.DIR_TYPE_DEFAULT, "User Folder", null); //Get the UUID for the user String[] principalUUIDs = {user.getFullQualifiedName()} ; // Set all the permissions on this folder for this user. //READ delegate.addPrincipalsToAcl(context, userFolder.getID(), EbiDocFolder.EL_DOC_FOLDER, EbiDocFolder.READ, principalUUIDs, EbiDirectoryConstants.FW_PRINCIPAL_USER); //WRITE delegate.addPrincipalsToAcl(context, userFolder.getID(), EbiDocFolder.EL_DOC_FOLDER, EbiDocFolder.WRITE, principalUUIDs, EbiDirectoryConstants.FW_PRINCIPAL_USER); //LIST delegate.addPrincipalsToAcl(context, userFolder.getID(), EbiDocFolder.EL_DOC_FOLDER, EbiDocFolder.LIST, principalUUIDs, EbiDirectoryConstants.FW_PRINCIPAL_USER); //PROTECT delegate.addPrincipalsToAcl(context, userFolder.getID(), EbiDocFolder.EL_DOC_FOLDER, EbiDocFolder.PROTECT, principalUUIDs, EbiDirectoryConstants.FW_PRINCIPAL_USER); } }
Reconnect sleepinterval for Cache Coordinator is expressed in milliseconds
In the Developing exteNd Director Applications book, there is a section that describes the reconnect.sleepInterval property for the Cache Coordinator. This section does not make it clear that the value for this property must be expressed in milliseconds, not seconds. (PPR 48875)
Scoped path for Resource Set URL requires a trailing slash
In the Developing exteNd Director Applications book, the discussion on the Portal/URL/ResourceSet/ scoped path does not state that the trailing slash is required. To get the URL to the Resource Set, you must include this slash. If you do not, the scoped path will return null. (PPR 47104)
Documentation on workflow in a cluster needs a correction
In the workflow administration chapter of the Workflow Guide, the section on configuring workflow to run in a cluster states that you need to deploy a project that contains a workflow to each server in the cluster. This is incorrect. You need only deploy the application once to the SilverMaster database and all servers in the cluster will pick it up. (PPR 49033 and 49034)
The following is a summary of current known issues with exteNd Director. Note that you may encounter other issues; check the release note updates for more information.
- Common issues
- Portal issues
- Development environment issues
- Content management and search issues
- Portlet issues
- Pageflow issues
- Workflow issues
- Localization issues
- API issues
- Administration issues
- Installation issues
- Platform issues
Common issues
- Rules subsystem does not support multiple resource sets All subsystems except for the Rules subsystem have been changed to work with multiple resource sets. Therefore, all rule artifacts must still be present in the Portal WAR resource set. If you create pageflows or workflows that use activities that fire rules, you need to be aware that the rules must reside within the Portal resource set, even though the pageflows or workflows may reside in separate portlet application WARs. (PPR 45938)
- Resource set does not detect when resources are deleted The Resource set is currently unable to notice when resources are deleted. For example, in the development environment, if you delete a portal category, the category will still be visible in the list of available categories for a portal style, even though it has been deleted. (PPR 46293)
- Database schema changes The column CONTENTENCODING VARCHAR(80) has been added to the CMDOCCONTENTS and CMDOCCONTENTSVERSIONS tables. When a document in HTML format is saved in one locale where the application server runs, it will be displayed incorrectly in the Content Management section of the DAC when the application server runs on another locale. The CONTENTENCODING column has been added to ensure that the default locale encoding is saved together with the document. When the locale is changed, the document will be displayed properly using the saved encoding.
If you are on exteNd Director 5.0 and have existing content in Content Management, and you want to change the locale followed by an upgrade from exteNd Director 5.0 to 5.2, you must do the one of following options:
- Right after installing exteNd Director 5.2 in the new locale, login to the Content Management section of the DAC. This will automatically create CONTENTENCODING on the CMDOCCONTENTS and CMDOCCONTENTSVERSIONS tables.
Then use DBA tool to run SQL statement:
UPDATE CMDOCCONTENTS SET CONTENTENCODING = old-locale-encoding; UPDATE CMDOCCONTENTSVERSIONS SET CONTENTENCODING = old-locale-encoding;where the value of old-locale-encoding can be obtained from the old locale application server console, by issuing this command:
get file.encoding- Before changing application server to run in a different locale, manually create CONTENTENCODING field in CMDOCCONTENTS and CMDOCCONTENTSVERSIONS tables, and run the sql statement:
UPDATE CMDOCCONTENTS SET CONTENTENCODING = old-locale-encoding; UPDATE CMDOCCONTENTSVERSIONS SET CONTENTENCODING = old-locale-encoding;where the value of old-locale-encoding can be obtained from old locale application server console, by issuing this command:
get file.encoding(PPR 45906)
- New property added to support MBCS names in pathInfo The config.xml file for the Framework has a new property called com.sssw.fw.converURI_to_UTF8. This property was added to address a problem that occurs on WebSphere and Tomcat 4.1.30. On these platforms, user pages with multibyte character set names could not be accessed. This problem occurs when ISO-8859-1 is used by the servlet container to decode the pathInfo. When UTF-8 encoding is used to decode the pathInfo, the MBCS pages display correctly.
When the com.sssw.fw.convertURI_to_UTF property is set to true, the Framework converts the String to the right encoding. This property should be set to true for WebSphere and Tomcat 4.1.30. For all other configurations, the property should be set to false.
Note: An alternative way to fix the problem for Tomcat 4.1.30 is to set com.sssw.fw.convertURI_to_UTF8 to false, and set the attribute URIEncoding to true in the Tomcat server's server.xml configuration file.
When this property is not specified in the config.xml file, the default value is assumed to be false for the exteNd Application Server and WebLogic, and true for Tomcat and WebSphere.
(PPR 46375)
- Components are deprecated As of exteNd Director 5.0, the Portlet 1.0 standard has been implemented. The use of components has been deprecated. Some public API will be in the javadoc for components. Some of these are there for the portlet support, and others will be deprecated in exteNd 5 point releases.
- Do NOT lock down the Application Server at installation During the installation, instead of Application Server lockdown as suggested by default, select not to restrict Application Server access. Otherwise, after you deploy the project you will have to unlock the Application Server in order to access the application deployed.
- License deactivated message displays when starting the Cache Coordinator The Cache Coordinator runs in client mode, which means it does not require a license. For those utilities that don't require a license to run, the console displays the following message:
License DeactivatedYou can ignore this message, since the behavior of the utility is not affected. (PPR 48991)
Portal issues
- Required name for a theme's XML file When creating a new theme, make sure that the XML file generated for it is named theme.xml. Otherwise, the theme will not appear in the portal. (PPR 46349)
- Application launch function of Shortcut portlet may cause security breach The ability to launch applications was removed from the default behavior of the Shortcut portlet. The application launcher uses an ActiveX plug-in that could be used to launch harmful applications via a Web link. The portal server and browser client are vulnerable to this security breach. To determine whether your server and browser are affectedand to correct the problemsee TID 10093176. To reactivate the application launcher for the Shortcut portlet, see TID 10093193.
- Portal startup when deployed to WebSphere You can ignore the following informational message at Portal startup:
Resource reference JDBC/XXXX could not be located, so default values of the following are used: [Resource-ref settings] res-auth: 1 (APPLICATION) res-isolation-level: 0 (TRANSACTION_NONE) res-sharing-scope: true (SHAREABLE) res-resolution-control: 999 (undefined) [Other attributes]This informational message occurs because a resource reference is missing from the application's deployment descriptor. For more details on this error message, consult your WebSphere documentation. To prevent the message from displaying, you can add the missing resource reference entry to the application's deployment descriptor using exteNd Director's Deployment Descriptor Editor. For more information about the Deployment Descriptor Editor, see Utility Tools in the online help system.(PPR 47051)
- Portlet does display according to layout setting If a portlet has a width setting that exceeds the limits of the layout, the portlet is not displayed according to the layout setting. For example the Flash portlet's default object width is 410 px. Because this exceeds the size of the 30% section of the layout, the Portal pushes it to 50/50. (PPR 46350)
- Preferences lost when renaming shared or container pages When you rename a shared or container page, the following information is not updated to match the new page name:
- Portlet settings
- Portlet preferences
- Child page references to the renamed parent
Page security and page categories may be updated. (PPR 45459)
- Error occurs on WebSphere when modifying a preference On WebSphere, the following error message displays whenever a user modifies a content preference for a personal page.
================================= J2CA0086W: Shareable connection MCWrapper id 55185d80 Managed connection com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@3f85d80 State:STATE_TRAN_WRAPPER_INUSE from resource JDBC/MyOracleThin was used within a local transaction containment boundary. =================================This is caused by a known problem with the Oracle thin driver. According to the IBM documentation, shared connections are not allowed within a local transaction containment boundary. exteNd Director uses local transactions. (PPR 46433)
- Getting named dispatcher fails on WebSphere When you call the getNamedDispatcher() method on the PortletContext object in a portlet running on Websphere, an exception is thrown. The workaround is to get the dispatcher by path using the getRequestDispatcher() method. (PPR 44243)
- Unable to specify text field area parameters for preferences of type string If a portal preference is of type string, a text field of fixed size is presented in the portlet preference sheet. The preference sheet does not give you the ability to specify whether a text area or text field is required, or specify the dimensions in novell-portlet.xml. For example, the message portion of the MessagePortlet can contain HTML, but it is currently presented in a single line. (PPR 43943)
- Portal controller servlet needs to honor accept header The Portal Controller servlet should respond with a 406 Not Acceptable when the URL is found but the content type is not what the request expected. For example, when looking for an image, the accept header on a request might specify that the request only accept images for the response. However, if the URL specified a HTML file, the controller server would currently return the HTML file instead of honoring the accept header. (PPR 46365)
- Portal page names can not be localized In this release, it is possible to localize the name of a shared page, container page, or personal page. (PPR 43706)
- Address Book search fails on GW WebAccess portlet using Microsoft Internet Explorer v6.0 It does not fail when using a Mozilla-based browser.(PPR 49042)
- When using the GroupWise Mail and Mail/Calendar portlets all messages may not be displayed It depends on the number of messages in the mailbox and the number of messages displayed by the portlet. For example, if the portlet display is set to 5 and there are 6 messages in the mail box it will only display 5 messages. Once message 7 is received all messages will be displayed properly.
(PPR 49042)
- Using the Network File Portlet's RMI feature To access NCP-based file systems on NetWare and OES/Linux using the Network File Portlet's RMI feature on a Linux-based portal, follow these steps:
- Install the NJCL clientless libraries on NetWare as outlined in the existing Network File Portlet Help file. If accessing OES/Linux server via RMI this step is not required other than to obtain the jar file for next step.
- Copy njclv2r.jar from Netware to Linux:
sys:/java/njclv2r/lib/njclv2r.jar to /opt/novell/exteNd5/common/jre/lib/ext- Restart SilverServer on the Linux-based portal
(PPR 49042)
- Nested s3-component rendering not supported The Portal should allow portlets to render s3-component tags that are rendered by the portal. This would enable portlets to render content of other portlets. However, this behavior is not supported in this release. (PPR 43404)
- Newly created SilverUsers aren't visible in the DAC without flushing cache If you create new SilverUsers on the exteNd Application Server, you will not be able to see them in the Security Management tool within the DAC until you restart the application server or use the Flush Cache option in the Directory Management and Security Management sections of the DAC. (PPR 44885)
- Improper iChain LDAP configuration may cause authentication exception When used together, exteNd Director and iChain must be configured to access the same identity store, since they both do their own separate authentications. iChain authenticates first and, if successful, passes the credentials on to exteNd Director. If exteNd Director is configured to access a different identity store, its authentication will fail, resulting in an exception. (PPR 48824)
- Portal authentication Require User Authentication in the Server Management Console is supported in exteNd Director. However, if your server is configured to use an LDAP realm and you authenticate with \SilverStream\Login, you will not be logged in to the Portal. The Portal will ask for your credentials again.
- Portlet User Information User Information (portlet<user-attribute>) has not yet been implemented. (PPR 36687)
- Other Portal issues
- Changing portal context name will break Portal. (PPR 39455)
- The Headline News component is no longer shipped with exteNd Director. Use the RSS portlet to access freely available news sources.
- CMPidReaderPortlet is no longer shipped with exteNd Director.
Development environment issues
- LDAP user attribute employeeNumber is misspelled in New Project wizard The LDAP user attribute employeeNumber is spelled incorrectly as employNumber in the User Options dialog of the New Project wizard. Therefore, if you create a new project that uses LDAP for authentication, you will not be able to retrieve the employee number of a user. (PPR 49112)
To work around this problem when creating a new project that uses LDAP, change employNumber to employeeNumber in the Include User Attributes text field on the User Options dialog of the New Project wizard.
To fix this problem in an existing project that uses LDAP, follow these steps:
- Open the project in the Director Designer.
- Select Director>Configuration from the Project menu.
- Select the User tab.
- change employNumber to employeeNumber in the Include User Attributes text field.
- Click OK and redeploy the project.
- Allocating more memory for WebLogic deployment When deploying to WebLogic from exteNd Director, an Out of Memory error may occur. To resolve this error, more memory must be allocated to the Java VM that is started by the WebLogic deployment tool. To allocate more memory, go to Project>Deployment Settings>Deployment Info, then in the JVM Options specify -Xmx and -Xms. For example:
-Xms128m -Xmx256m(PPR 45733)
- Using Director Designer search If you use the Director Designer's search (Edit>Find or CTRL-F) and you search on the string \u, you will encounter the following error during subsequent startups of the Director Designer:
java.lang.RuntimeException: Assertion 'exception' failed:Error: Unable to load persistent find settingsYou can work around the error by deleting the findprops.xml file from the /tools/Resources/Preferences directory before restarting Director Designer.(PPR 48994)
- Director Designer context-sensitive help on Windows XP SP1 with Firefox browser On Windows XP, with SP1 installed, if Mozilla Firefox is your default Web browser, context-sensitive help calls do not work with the product as installed. But there is a simple fix for this problem:
- In Director Designer, select Tools>Preferences to display the Preferences dialog.
- In the Web browser field, delete the expression
-url "%1"
including the quotation marks. Leave the rest of this field as is.- Click OK to close the Preferences dialog.
You do not have to restart Director Designer for this fix to take effect.
(PPR 48761)
- XForms Designer and invalid CSS property names If your form contains invalid CSS property names, you will only be able to edit the form using the Source tab of the XForms Designer. The XForms Designer will not allow you to switch to the Form, Model, or XForms Preview tabs.
(PPR 49003)
- Undeploy from SMC may not be recognized by the exteNd Director development environment and cause quick-deploy to fail If you are using quick-deploy in the exteNd Director development environment and undeploy your project using the SMC, the development environment does not recognize that this project has been removed. On the next deploy it will only deploy what it thinks has changed as per the quick-deploy option. To avoid this problem, always use the exteNd Director development environment to undeploy projects that are using the quick-deploy option.
- Error stating deployment plan file newer than deployment descriptor This is expected behavior if you go in and modify the deployment plan after the deployment descriptor is generated. This happens often when using EARs, where you create the deployment plan as a second step. The error will not cause any loss in functionality.
- Problems when using the xsi:schemaLocation attribute If you use the Form Wizard to create a form from sample data that uses the xsi:schemaLocation and/or xsi:noNamespaceSchemaLocation attributes, the wizard will NOT add any schema URIs from those attributes to the model element's schema attribute. You must do this manually. It is your responsibility to copy the schema files into the resource set in order for the form to work at runtime and in the preview tab of the development environment.
- ANTLR problem in analyzing files that have a one-line comment at the end Do not include a comment line at the bottom of a custom class file; it may cause a compilation error.
- Layout region after a nested repeat is not a supported configuration In the Form Designer, the Event Editor cannot currently add a layout region after a nested repeat. (PPR 39792)
- Compatibility with pcAnywhere You may have trouble running exteNd Director with pcAnywhere, due to a known compatibility issue between pcAnywhere and Java. (Products similar to pcAnywhere may also cause problems.) See the exteNd Director configuration file (bin\xd.conf) to learn about a switch you can set to address this situation.
- Setting up EJB projects with EJB subprojects You may have two or more EJB projects that share some common session or entity beans. In that case you can separate those shared beans into subprojects for inclusion in your main EJB projects. When doing so, follow these steps to ensure a proper project structure:
- Use the EJB-client architecture to organize the shared bean classes. This involves setting up two projects for them: an EJB-implementation JAR project (containing SessionBean objects) and an EJB-client JAR project (containing home and remote interfaces).
- Use the resulting EJB-client JAR project as your shared subproject. This involves adding its project (SPF) file to the classpath of your main EJB projects.
If you don't follow this approach and instead add the project file of an old-style (combined) EJB JAR to the classpath of your main EJB projects, you may have problems when editing deployment descriptors (including messages about beans not found).
- Using a proxy server If you are using a proxy server, you need to specify the proxy host and its port in xwb.conf, in the exteNd Director bin directory (see xwb.conf for details). If you set these values, everything will work fine -- as long as you don't use the Deployment Plan Editor, which communicates with the Novell exteNd Application Server using the exteNd HTTP implementation instead of Sun's. The exteNd implementation does not use the proxy server system properties. Thus the Registry Manager and Web Service Wizard will fail when they need to contact a proxy server (for example, if the wizard needs to find a DTD or Schema outside the firewall). You need to restart exteNd Director for the proxy server support to work again. (PPR 30320)
- Generating an EJB session bean Web Service To generate a Web Service for an EJB session bean, you must start by providing the Web Service Wizard with the home or remote interface. Starting with the SessionBean object doesn't work at present. (PPR 26241)
- Classpath for EJBs using EJB-client architecture Before you build a standalone EJB project using the EJB-client architecture, you must add the EJB-client JAR project (SPF) file to the classpath of the EJB-implementation JAR project. Use the Classpath/Dependencies tab of the Project Settings dialog. If you use the Project Wizard to generate your EJB-client JAR project, this will be done for you.
- Java files not to compile When you add Java source files to a project, there's currently no way to flag certain ones as not-to-be-compiled. As a workaround, you can change the file extension of such files (for example, MyClass.java.txt).
- Server profile names and properties When you create a server profile, make sure the profile's name is not the same as the value in its server name or database name property. Otherwise, profile information may not display properly when requested. (PPR 33997)
- HTML editor does not allow you to specify encoding If you use the HTML editor to create an HTML file, and type Japanese characters in the file, the file may not display correctly at runtime. The reason for this is that the HTML editor does not allow you to specify the encoding (UTF-8, or whatever is specified in the HTML source) when you save the file. Instead, it picks up the default encoding for the machine. If the encoding on your machine does not match the HTML you are writing, you must change the encoding on your machine or use another editor that allows you to specify the encoding. (PPR 46884)
Content management and search issues
- Adjusting Autonomy configuration if MBCS in install path The exteNd installation program incorrectly edits an Autonomy path property in a configuration file if MBCS (multibyte character set) characters are used in the install path. You should edit this configuration file by using exteNd Director's XML Editor (to ensure that proper UTF8 is saved):
exteNd_dir\Director\templates\Director\library\ConfigService\ComposerService-conf\config.xmlMake sure the path in this section is valid (the install may have entered bad characters):
<!-- This points to the directory where Autonomy's OmniSlave technology is installed. --> - <property> <key>com.sssw.cm.fetch.binary.filters.dir</key> - <value> C:\Program Files\Novell\exteNd5\Director\autonomy\OmniSlaves </value> </property>If you have already created projects (including the Express Portal project created by the install), you should fix the file in each project, for example:
exteNd_dir\Projects\Express\library\ConfigService\ContentMgmtService-conf\config.xml(PPR 46676)
- Editing config files for supported MIME types and file extensions In the following template config files:
Novell\exteNd5\Director\templates\Director\library\ConfigService\ContentMgmtService-conf\config.xml Novell\exteNd5\Director\templates\Director\library\ConfigService\FrameworkService-conf\config.xmlthe lists of supported MIME types and file extensions should be the same, but are not. As a result, you may need to manually edit these config files in your project (under the project's library\ConfigService directory) in order to upload a particular file type in Content Management. (PPR 48917)
- Errors occur when viewing PDF documents with foreign characters in file names If you use WebDAV to connect to the content repository with Internet Explorer, you will get file not found errors when you try to view PDF documents with foreign characters in their file names. To work around this issue, either upgrade to Adobe Acrobat Reader 7.0 or disable the View in Browser feature in earlier versions of Acrobat Reader, as described in http://www.bnl.gov/itd/webapps/pdf_help.asp. (PPR 48412)
- Document Types do not support default categories at the API level The PMC currently allows users to specify default categories for Document Types. However, this capability is not provided in the API. Currently, document types only serve the purpose of categorizing extension meta fields (Custom Fields). (PPR 45798)
- Document Types do not support default folder at the API level The PMC currently allows users to specify a default folder for Document Types. However, this capability is not provided in the API. Currently, document types only serve the purpose of categorizing extension meta fields (Custom Fields). (PPR 45797)
- EbiDocContent.getDataAsStream needs to operate on stream rather than byte array The EbiDocContent.getDataAsStream method needs to be changed to operate on stream rather than byte array. This will allow very large document content to be streamed to the client without consuming a large chunk of memory. The current behavior makes it difficult to store large documents (such as high resolution pictures) in the Content Management system. (PPR 39493)
- Child of link failures cmgr.CopyFolder and cmgr.MoveFolder fail when document has child of link. (PPR 28279)
- 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.
- Content importer attempts to remove CM elements when trying to overwrite existing elements 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 CMS Administration Console, remove the layout style descriptors associated with layout styles before importing content with overwrite enabled for layout styles and document types.
- Document imports on Solaris using Autonomy's Java JNI library throw Java exceptions When exteNd Director performs document imports on Solaris using Autonomy's Java JNI library, the Autonomy implementation sometimes throws Java exceptions, causing processing to terminate. The problem is reported as an unknown error by the Autonomy implementation. The Autonomy import log indicates that the import was processed normally. Novell has provided all the necessary materials to Autonomy so that they can investigate this issue. (PPR 48869)
Portlet issues
- NetStorage portlet fails when using the host server on OES/Linux or NetWare To use the NetStorage portlet when you install NetStorage on the same OES/Linux or NetWare server that runs your exteNd Director portal, you must configure the portlet to use the host server and a local port. If you add the NetStorage portlet to a personal page and modify its preferences in the Portal Personalizer, the value you enter for the local port is not saved the first time. As a result, when you run the NetStorage portlet on a personal page and attempt to log in to the NetStorage server, the portlet generates the message Error rendering portlet in doView. To fix the problem, reenter the local port number and save preferences again in the Portal Personalizer. (PPR 49127)
- IE MS04-004 patch affects Shortcut, IFrame, Netmail, Exchange, and Notes portlets Microsoft Security Patch MS04-004 Cumulative Security Update for Internet Explorer negates basic authentication functionality which (depending on configuration) may be used by the Shortcut, IFrame, Netmail, Exchange, and Notes portlets. This patch disallows URLs in the form
http://username:password@server
.See http://support.microsoft.com/default.aspx?scid=kb;en-us;834489 for details on uninstalling the patch. A more secure option is to implement form-based authentication if the destination server makes this available. See the individual portlet preference descriptions and TID 10093277 for details. (PPR 46700)
- eGuide fronted by iChain If eGuide is fronted by iChain, the eGuide portlet will not work. This occurs because the eGuide application does not accept form based authentication. Authentication is acheived in eGuide by passing the userid and password as URL parameters. iChain does not allow the password to be passed as an URL parameter. If the eGuide application is fronted by iChain, the iFrame portlet should be used to access eGuide.
The following preferences for the iFrame portlet should be used:
Preference Value URL https://yourhost/eGuide/servlet/eGuide URL/Form Parameters Leave blank Encode URL parameters: true Encoding UTF-8 Form Post? false Authentication Required? false Username Leave blank Password Leave blank (PPR 46388)
- Shortcut portlets and SSL For shortcut portlets that are:
The third-party server's root CA must be included in the exteNd Application Server's agrootca.JAR file. The agrootca.JAR file is installed in the exteNd suite's Common\lib directory. It includes many known root CAs by default. If you encounter an error that includes the text: "Chain does not terminate with a trusted CA" then you'll have to add the root CA of the target server to the application server's agrootca.jar file.
- Deployed in an exteNd Director portal on an exteNd Application Server.
- Accessing third-party servers using SSL.
To add the root CA to agrootCA.jar:
Make sure to import the root ca using no compression (the 0) option in the jar command.
- Shut down your application server.
- Make a copy of your application server's agrootca.jar file (in Common\lib).
- Obtain the third party root CA and save it to a file in DER encoded binary format. (Some browsers allow you to export it.)
- Use the jar command to add the third part root CA to agrootca.jar file. For example:
jar -uvf0 agrootca.jar c:\yourCertFile- Restart the application server
(PPR 43763)
- Using macros in Network File portlet preferences In some cases, it is necessary to use a macro in the InitialDestination preference of the Network File portlet in order for end users to be automatically directed to their home directories. This applies when using eDirectory and LDAP in a NetWare environment.
- When using the NJCL provider, and you are using the format
//servername/volumename/HOME/
in the InitialDestination preference, you need to append the expression${User/attr/uid}
, for example://servername/SYS/HOME/${User/attr/uid}- Similarly, when using the CIFS provider, and accessing Nterprise Service for LINUX (NSL), you need to use the expression
${User/attr/uid}
to provide the user's share name, for example://servername/${User/attr/uid}To implement this technique after deploying a project:
- With your project open in Director Designer, open the Director Project Configuration dialog by selecting Project > Director > Configuration.
- Click the User tab.
- In the Data Store section, make sure that Directory LDAP Realm is selected.
- In the JNDI Options section, add
uid
to the Include User Attributes expression.- Click OK.
- Redeploy your project.
Note that if you are authenticating against a SQL database, the required macro expression might be different.
(PPR 45936)
- Message portlet preference field needs to be a text area In the preferences editor for the Message portlet, the Message preference field only shows a single line space in which to enter the message. This makes it difficult for the user to see what has been entered and make appropriate edits. (PPR 43825)
- Messages that contain special characters should be encoded for JavaScript Portlet messages that are going to be used in JavaScript should be encoded. In some system portlets, special characters cause JavaScript to fail because they are not escaped.
(PPR 43786)
- Setting preferences for eGuide and NetStorage portlets via Novell Security Manager When you use the Novell Security Manager proxy to access an ExpressPortal application running on NetWare, you may not be able to use the content preference sheets for the eGuide and NetStorage portlets. Clicking Cancel or Descriptions on the preference sheets for these portlets may generate the error Cannot find server or DNS. (PPR 49106 and 49107)
- PID portlet has been removed The PID portlet has been removed from exteNd Director in this release. (PPR 46434 and 46454)
- Logoff action in LoginPortlet is hard coded In the LoginPortlet, the Logoff action in the URL is hard coded. In case of a security exception (such as an unauthorized user accessing a particular page), the aggregation engine will redirect the logged in user to an error page that displays the security message and a link to log out (so the user could log in with the appropriate credentials to gain access to the page in question). However, in order to create the logout link, the engine passes the following hard-coded query param:
?login_action=logoffThis works fine when you're using the installed LoginPortet, but is problematic for developers who want to write their own Login or Logout portlets.
(PPR 42190)
- Margin preferences of Exchange portlet can be overridden by HTML settings The margin preferences of the Exchange portlet are ignored if a document hosted by the portlet sets its own margin-left or margin-right properties, either in Cascading Style Sheets (CSS) or through the leftMargin or rightMargin properties of the HTML element. (PPR 43743)
- CAP portlets cannot open Open Office documents unless file extension is provided When you add an Open Office document as content for a document you create using the Content Administration portlet and CAP Editor portlet, you must include the Open Office file type extension (such as sxw) in the document name. Otherwise, you will not be able to open the document in a browser because the Open button is not displayed in the dialog. Only the Save and Cancel buttons appear. This restriction does not apply when you use the Content Management section of the Director Administration Console (DAC) to import an Open Office document. (PPR 48898)
- Minimize and maximize buttons do not work when previewing a document using CAP portlets If you try to minimize or maximize the content of a document you are previewing in the CAP Reader portlet from the CAP Inspector portlet, you will lose the content in the pane. To redisplay the content, you need to close the CAP Reader window and select Preview again from the CAP Inspector. (PPR 48735)
- Calendar in CAP Editor portlet may crash an Internet Explorer (IE) browser running on Windows XP When you select a publish date or expiration date for a new document in the CAP Editor portlet, navigating back and forth between months in the calendar may crash an IE browser running on Windows XP. This behavior does not occur when running the CAP Editor portlet in a Mozilla browser on Windows XP or in an IE browser on Windows 2000. (PPR 48803)
- HTML portlet preference settings required for some Web sites When using the HTML portlet to provide access to certain Web sites (for example, Google.com or MSN.com), users might get a browser error (Unknown Connection Failure: 404 [Object Not Found]) when performing a search unless you use specific portlet preference settings.
Sites such as Google and MSN perform a GET upon form submission, and do not implement POST, which is the default method for the HTML portlet.
Users can perform successful searches on such sites only if the following content preferences are set for the HTML portlet instance (Portal Administration>Maintain Shared Pages>Choose Content>Content Preferences):
- The Link Destination preference must be set to either Within the portlet or Within the portlet maximized.
- The Search and replace strings in URL content preference must include the expression:
on(s|S)ubmit="(.*?)"~
- The Do a post for any form submission preference must be set to False.
(PPR 47970, 47971)
- HTML portlet preferences might depend on site coding Because there are so many different ways to code a Web site's home page, the HTML Portlet may require changes to its preference settings in order to work correctly for a particular site. (PPR 48998, 49009)
- GroupWise portlets require template files on the GroupWise server The GroupWise portlets will not function properly unless the corresponding template files are installed on the GroupWise server. Please consult the NPS documentation on novell.com for information on installing the GroupWise templates. (PPR 45812)
- HTML portlet generates date exception with some URLs During the processing of some URLs, the HTML portlet wizard generates an exception when getting and setting the date for the page. This problem does not seem interfere with the runtime behavior of portlet, but does cause an error message to be dispayed in the console for the application server. Here's what the message looks like:
exteNd Director ExpressPortal-ResourceSet EboResourcesSecondaryKeyProcessor completed (102171ms) PortletURLHelper.updateCookieValue(): exception thrown trying to get date and set expire property .updateCookieValue()->Exception: java.text.ParseException: Unparseable date: "Thu, 15 Apr 2010 20:00:00 GMI"You may see this message when using the Wizard to configure the URL for the HTML portlet. The problem seems to be caused by the date format for the target page. (PPR 49001)
- HTML portlet Divide Page feature does not work with all URLs During the processing of some URLs, the HTML portlet wizard hangs and generates a stack trace when you try to use the Divide Page feature. When this problem occurs, you will see the following message in the console:
org.apache.regexp.RE.matchNodes(RE.java:1376)\uD\uA\u9at ... java.lang.StackOverflowError\uD\uAYou may see this message when using the Wizard to configure the URL for the HTML portlet. The cause of the error is unknown. (PPR 48999)
- Weather Service portlet does not work for some locations When you run the Weather Service portlet, it may or may not display weather data, depending on the location (zipcode or city, state) you request. Locations successfully tested include Green Bay, WI and Miami, FL. If the location you specify fails, you'll see this text:
Last updated on PlaceHolder(PPR 48661)
Pageflow issues
- Composer Pageflow wizard does not support null input or output documents The Composer Pageflow wizard does not support Composer services that have either a null input or output document. Although the wizard works best with a Composer service that has both an input and output document defined, it also supports a Composer service with output but no input. In all other cases, you will get a dialog indicating that the service is not supported.
Although the wizard imposes restrictions on which types of services are supported, the Composer activity does not impose these restrictions. A Composer activity works with Composer services that have input and output, no input with output, input with no output, or no input and no output. The only caveat is you would need to manually create the pageflow, leaving the input/output fields blank in the Composer activity when appropriate. One other thing to keep in mind is that the Composer Activity does not currently support multiple inputs nor multiple outputs. (PPR 40905)
- If a form is on a page, a browser refresh does not cause a request When a portal page contains a pageflow with an XForms Web form, and the user clicks the browser Refresh button, an HTTP request is not submitted to the Portal as it should be. The reason for this is that every state change in a pageflow with a form is handled through an XForms submission. The XForms submission does not uses the standard browser submission but instead uses the xmlhttp object. The browser is unaware of the fact that the page has changed due to submission and therefore will not resubmit the form data when the refresh button is pressed. Due to this technical barrier, it seems impossible at this time to instruct the browser to rerequest the page from the server. (PPR 46167)
- Pageflow applications containing XForms actions (deployed on Apache Tomcat 4.1) must be included in the main Portal WAR If you are deploying pageflow applications that contain XForms actions to Apache Tomcat 4.1, they cannot be packaged in Portlet Application WARs. (PPR 46510)
- New Request button sometimes fails on Results page of Web Service Pageflow When you click the New Request button in a Web Service pageflow, you may see an error message and notice that the browser appears hung. This problem is due to a technology barrier in Microsoft Internet Explorer that surfaces when the XForms exteNd Director server-side processor is used to render an XForms Web form. The reason for this is that the xmlHttp object used in Microsoft Internet Explorer for network communications with the XForms server-side processor enforces a size limit on data submitted. If the amount of data is significant, you may encounter this barrier.
This problem only occurs with the server-side processor, and should not arise when the browser plug-in is used for XForms processing. (PPR 46886)
- Web Service pageflows and WebLogic need 4 additional JARs in Classpath To run a Web Service pageflow on WebLogic 8.1, you need to add the following jars to the WebLogic classpath:
wssdk.jar CSHelper.jar commons-httpclient.jar commons-logging.jarAdd these to the setClassPath in the startWebLogic.cmd in the user projects/mydomain of the WebLogic install, as shown below:
set CLASSPATH=d:\bea\server\lib\xercesImpl.jar;%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%;%JAVA_HOME%\jre\lib\rt.jar; %WL_HOME%\server\lib\webservices.jar;C:\Novell\Director\autonomy\autonomyJNI.jar;D:\AddToClassPath\wssdk.jar;D:\AddToClassPath\CSHelper.jar; D:\AddToClassPath\commons-httpclient.jar;D:\AddToClassPath\commons-logging.jar;%CLASSPATH%
Workflow issues
- Workflow queue performance affected by total workitems in system The time it takes to view workitems in an individual user's workflow queue increases as more workitems are added to the overall queue (whether or not the individual user's queue is growing in workitems). That's because the overall queue is searched to provide users with the workitems in their particular queues.
If you use clustering to improve application server performance, you should partition workflows across the cluster. Otherwise, the entire cluster will have the same performance as a single system. (PPR 48169)
Localization issues
- There are a number of issues related to localization text For example, some pages are not fully localized. Some issues relate specifically to Japanese and Chinese locales. (PPRs 46439, 46437, 46065, 43885)
- Some portal theme images are not localized Each of the portal themes includes an image used to present a preview of the theme. Each of these images is called preview.gif. These images are screen captures of English-language portal screens and are not localized. For more information on portal themes, see the chapter on Working With Portal Themes in the exteNd Director Portal Guide. (PPR 46540)
API issues
- Extends chain for interfaces not fully expanded Due to a limitation in the version of Sun NetBeans used in the exteNd Director development environment, 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 exteNd Director API Reference for the full set of valid API calls.
- Using EJB wrappers not supported exteNd Director manager APIs contain EJB wrappers. However, Novell does not officially support their use in this version.
Administration issues
- Securing a PMC application If you would like to lock down your PMC application, please see TID: 10087460.
- Exercise caution when using Synch Base Attributes Running Synch Base Attributes can result in data loss when your portal application uses LDAP as the directory service, but JDBC (instead of LDAP) for the user service database. Synch Base Attributes synchronizes all user attributes from the directory service to the user service database. Therefore, updates to user profile data in the user service database will be overwritten by the settings in the directory store. Use Synch Base Attributes only when you want directory service data to prevail. (PPR 46903)
- LDAP host parameter should be defined as a full DNS name or IP address When you configure your exteNd Director portal for LDAP authentication, you need to specify an LDAP host on the Directory LDAP Options panel, accessible from the Directory tab of the Director Project Configuration dialog. The default value for this parameter is localhost:389. This setting may not work even if the LDAP source is local. Instead, use a full DNS name or IP address in place of localhost. (PPR 49125)
- Harmless SilverCacheCoordinator errors on Linux and NetWare When starting SilverCacheCoordinator on Linux or NetWare, you may see several error messages that look like this:
exteNd Director FAILURE: Failed to load services for subsystem 'ComposerService'. Reason: SAX Error parsing config document:Relative URI "framework-services_3_0.dtd"; can not be resolved without a base URI. Please check document for validity!. This subsystem will not function properly.You can ignore these messages. (PPR 46512)
- Editing classpath in SilverCacheCoordinator.ncf On NetWare, the classpath specified in SilverCacheCoordinator.ncf contains absolute paths based on the default exteNd Director install location. If you install exteNd Director to a different location, you'll need to edit SilverCacheCoordinator.ncf to adjust those absolute paths. This also applies to ShutdownCacheCoordinator.ncf. (PPR 46452)
- Creating a new user with NewUserPortlet You cannot create a new user by running NewUserPortlet directly in the browser using the URL http://localhost/ExpressPortal/portal/portlet/NewUserPortlet. The credentials you enter for the new user are not retained. (PPR 48982)
- Add user in the DAC when using Mozilla has "Admin" prefilled This is a Mozilla browser settings issue. In the browser, you can go to Edit|Preferences|Privacy & Security|Passwords|Manage Stored Passwords and delete the admin user name. The next time you log in to the DAC, don't let it store the admin user name and password; now admin will not show up in the Add Users user ID text box.
- Caution must be exercised when removing Locksmith users and groups The Directory subsystem allows you to remove exteNd 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. To remove a Locksmith user:
- Open the DAC.
- 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, then remove the user from the realm.
IMPORTANT: Make sure you have at least one user remaining in the Locksmith ACL list. Otherwise, security will be open to everyone.
- Logging levels set in the DAC are not persisted When you set logging levels in the DAC, the values reset to the default level 3 after you restart the server. To persist logging levels, change the LoggingLevel setting in the configuration file (config.xml) of the target subsystem, then rebuild and redeploy the project. (PPR 47574)
- Default Security Authority dropdown menu is not populated when setting LDAP security for clusters When you configure an LDAP security provider server at the cluster level in the System Management Console (SMC), you cannot select a default security authority from the dropdown menu. When you select LDAP as your default security realm, you must type in the server name for the default security authority, then click Update. (PPR 45212)
Installation issues
- Cache Coordinator does not support spaces in install directory If using the exteNd Director Cache Coordinator on Windows (typically only used in a production environment), the exteNd Suite must be installed in a directory without a space. By default, the exteNd 5 install chooses Program Files as the root of the install. You will have to change this at install time if you plan to use the Cache Coordinator.
- Sun's JCE must be installed into the JRE for Application Servers that run on JRE 1.3 This is a simple copy of four Jars (downloadable at http://java.sun.com/products/jce/index-122.html) into the jre/lib/ext directory of the app server's jre. This needs to be done ONLY if the Application Server is running 1.3 JRE. If this is not done, encryption of portlet preferences will be disabled at runtime.
Platform issues
- Tomcat needs to be started in a certain way to support XSL transformations To avoid this problem, start Tomcat from the command line using the following batch file: C:\Tomcat4.1\bin\startup.bat
- When using Tomcat, you must deploy the portal WAR before deploying any portlet application WARs This is an issue only with Tomcat. If you need to clean your databases, you will have to undeploy both the portlet application and the portal WAR and then redeploy them in the correct order.
- CMS Administration Console access causes stack trace on the Tomcat server When exteNd Director is deployed on Tomcat, a stack trace is issued on startup and shutdown if the user accesses the CMS Administration Console during the session. This is an issue with Tomcat where Apache is attempting to persist session information across server shutdowns. You can add this to your server.xml to not persist sessions:
<Manager className="org.apache.catalina.session.StandardManager" algorithm="MD5" checkInterval="60" debug="0" duplicates="0" expiredSessions="1" maxActive="1" maxActiveSessions="-1" maxInactiveInterval="300" pathname="" randomClass="java.security.SecureRandom" rejectedSessions="0" sessionCounter="5"> </Manager>
- Using JBoss with the IBM JDK The JBoss Application Server uses the Sun JDK by default. To use IBM JDK 1.4.2, follow these steps:
- Set your JAVA_HOME to the IBM JDK directory
- Add the IBM JDK's /bin directorty to the path
- In the JBoss run.conf file (in the JBoss\bin directory), look for this entry:
if [ "x$JAVA_OPTS" = "x" ]; then JAVA_OPTS="-server -Xms128m -Xmx128m"- Remove the "-server" option.
(PPR 48897)
- J2EE 1.4 Features not supported If you are running with J2EE 1.4 and are creating a new exteNd Director project, you must select J2EE 1.3 from the J2EE version dropdown (on the first panel of the New Project Wizard).Your application will run in 1.3 backward compatibility mode. You will not be able to use J2EE 1.4-specific functionality. (PPR 48922)
- Oracle Thin Driver needs XA to be turned off The Oracle Thin Driver will work fine if you unselect the XA flag when you add the connection pool using this driver. (PPR 40681)
- Oracle OCI Driver needs XA to be turned on The Oracle OCI Driver will work fine if you leave the XA flag on when you add the connection pool using this driver.
- NetWare X-Windows GUI opens when Portal is accessed When accessing the Express Portal URL (http://hostname:83/ExpressPortal/portal), the NetWare server will load the X-Windows GUI if it is not loaded. If it is loaded, the NetWare server will switch console screens to the GUI. To stop this from occurring, restart the Application Server in the following way:
silverserver +Djava.awt.headless=true
(the + sign forces the Java option through to the JVM). This parameter solves the problem.
Many problems were fixed in Version 5.2. The following table lists the problems commonly encountered.
Number
Description
45511 Administration - DAC Directory Management - Wrong user info is displayed for selected user 45188 Administration - DAC Directory Management - Confusing filter in Directory Management when using LDAP 44904 Administration - Login portlet - New user attributes are not saved with LDAP realm 44823 Administration - DAC Workflow Administration - Suspending a process does not remove it from user's queue 44849 Administration DAC Administration Tools - Create database tables requires pageflow 45756 API - The method StringBuffer.indexOf(String) called in EboStringMisc.replaceString() uses JDK 1.4 method 43838 API - EboSqlHelper uses JDK 1.4 specific method. 45513 API - EboCookieUtil.getCookieFromBrowser not finding valid cookies 45233 API - Problems occur when you stop or destroy the TheadPool manager service 44195 API - Languages other than English do not work in Custom Preferences Editor 44326 API - Remaining occurances of double-check idiom 42745 API - Deprecated component-specific public API 41228 CM and Search - Invalid parameter binding Exception occurs when multiple users create or publish documents 44080 CM and Search - Using 5.0 Novell Server and ASA8/JConnect produces Exception when Publishing document 46345 CM and Search - Microsoft Publisher documents are not handled 45042 CM and Search - Internal server error occurs when displaying content 37142 CM and Search - MySQL - Copying a folder or adding a document can spike the database CPU usage 43178 CM and Search - Bad performance when retrieving taxonomy/category tree 45528 CM and Search - Exception generated when deleting a category 44316 CM and Search - Should not allow CM folder delete when files are in the folder 36947 CM and Search - A document can be published after its expiration date 37043 CM and Search - setUnlinkChildren() throws exception when parent is removed 45882 CM and Search - CM Performance Document Hierarchies operation (getChildren) 45446 Development environment - Setting project up to use sharedlib jars for deployment - when copying sharedlib jars, ConfigService jar was not copied 46100 Development environment - Pageflow Activity wizard - Logging code check box does nothing 45363 Development environment - In the Project/Configuration/User tab, if the Directory LDAP Realm is selected and focus is shifted away from the User tab. Upon returning to the User tab, the Director Data Source radio button is displayed as selected, though the LDAP JNDI option fields are editable. 45335 Development environment - Opening portlet.xml editor is very slow 45252 Development environment - The message "The directory you have chosen already contains files, and some of them may be overwritten. Would you like to continue? " can be seen after creating a portlet web service and then trying to create another one. It is the first thing that appears in the wizard. This message does not inform what directory was chosen. 44934 Development environment - Portlet Wizard does not validate the packages name for invalid naming 44905 Development environment - Numerous editors cannot create more than one file at a time 45294 Development environment - Portlet Application Wizard adds duplicate entries in deployment descriptor 45522 Development environment - Undeploy of EAR does not clean up the entries in the SilverMaster AgResources table 46083 Development environment - When creating a Portlet Application to go in an EAR project, the classpath can be wrong. The wizard prompts you for a place to place the project. If you place the project outside of the EAR, the classpath for the new Portlet App War's resource set includes references to ..\library\XX.jar. This will not work since ..\library would only be valid if the portlet WAR project were under the EAR project directory. 35962 Installation - After install of directory, hard-coded paths are in config files 45035 Internationalization - Support Custom Localization Configuration: Login page, personalizer, and choosing locals for portlets 46427 Internationalization - Welcome Portlet message showing up in English 44019 Internationalization - Weather Portlet not fully localized (preferences) 43684 Internationalization - Unable to access certain portlet help files 43160 Internationalization - MBCS: Child page names are not listed with correct characters in Navigation portlet 43889 Internationalization - Failed to display user page (name contains MBCS) after returning from Portal Admin 44104 Internationalization - MBCS: Display names of the layouts (from layout mgr) are incorrect 43317 Internationalization - Can't modify display name for specific locale (not default) from DAC 44140 Internationalization - Layout of multi-byte characters is not correct for some portlets 38284 MySQL - CPU spikes on queries with multiple subqueries 44406 MySQL - No tables are displayed when creating a new database Pageflow or entity bean from existing table 45746 MySQL - Cannot find user with search string when realm is extendserver/ldapsecurity 41116 Pageflow - Exception when running two Pageflows on a page if both are Web Services 41781 Pageflow - Null pointer exception occurs when trying to execute link with expression 42376 Pageflow - Pageflow doesn't work initially on default shared page 43014 Pageflow - JSP activity throws NullPointerException on Tomcat - engine unavailable 43444 Pageflow - Exception handling does not show correct source of exception 43584 Pageflow - XForms with input documents that have CDATA sections do not render 43737 Pageflow - XForms:upload element generates a classnotfound exception 44221 Pageflow - StartProcess with properties methods do not work 44927 Pageflow - Database Pageflow displays a null when session times out 44265 Portlets - Groupwise MailCalendar portlet not building URL correctly for sub page or msgs 45569 Portlets - Network File Portlet - Naming issue when Portal runs on Solaris 42692 Portlets - Survey should have option for one response per user 42729 Portlets - Text does not show in any portlet title if you add the HTML portlet to a page 43499 Portlets - Weather portlet throws exceptions when running as anonymous 43696 Portlets - RSSNews portlet doesn't support news feed without an extension 43276 Portlets - iFrame failure causes inability to return to default corporate page 44978 Portlets - Notes portlet - username, pwd, maildb should not be requiured in preferences 44501 Portlets - Survey Portlet questions repeat each time after going into Content Preferences 43387 Portlets - Cannot change preference for HTML portlet 43596 Portlets - Complex preference utility - select locale 43359 Workflow - Running in a cluster: When you start a process the other machine in the cluster does not pick up the queue
Number
Description
46218 Accessory Portlets - Network File Portlet / NJCL throws NameNotFoundException 46570 Accessory Portlets - Add & Remove buttons missing from user shortcuts 43099 Accessory Portlets - NJCL fails in NetWare only environment 46443 Accessory Portlets - GW Mail portlet requests additional logins with GW Linux server 46235 Accessory Portlets - Survey portlet is not consistent with "Add Question" order 46487 Accessory Portlets - GW Mail-Calendar login not current 46520 Accessory Portlets - WebMail portlet help not fully localized 46695 Accessory Portlets - Shortcut portlet login dialog box has corrupted characters in Japanese 46982 Accessory Portlets - CAP - creating a table within a document shows table above the portlet 45624 Accessory Portlets - Reply window doesn't close on WebAccess portlet 46615 Accessory Portlets - Change Password portlet needs additional error trapping 46262 Accessory Portlets - Two portlets have wrong URL for exteNd doc page on novell.com 46654 Accessory Portlets - WebMail portlet corrupts attachment path 43171 Accessory Portlets - Fixes to Network File portlet help 43763 Accessory Portlets - shortcut wizard can not open ichain site 44025 Accessory Portlets - Redirect when using notes portlet uses a bad url. 44551 Accessory Portlets - NIMS pref. description updates on the MS patch warning 43274 Accessory Portlets - Network file portlet - Wrong file name displayed when selecting Save Target As 42910 Accessory Portlets - POP3 binary attachments won't detach 43743 Accessory Portlets - Exchange - margin pref. not working 46060 Accessory Portlets - column headings are not localized in stockportfolio portlet 46447 Accessory Portlets - StockTicker code not localized and contains old copyright info 46203 Accessory Portlets - User macro fails with Network File portlet deployed to linux using Samba shares 45068 Accessory Portlets - Change of userid/pwd pref in NetworkFilePortlet not reflected until new session 47122 Accessory Portlets - CAP - EboItemExistenceException, when creating a document with the existing name 45905 Accessory Portlets - Strange behavior when sending reply or forwarding an email from GW Mail portlet 47062 Accessory Portlets - IFrame portlet gets stuck in infinite refresh loop 47112 Accessory Portlets - CAP Editor - Missing required fields specification 46775 Accessory Portlets - Network File portlet needs additional info in built-in help 46978 Accessory Portlets - CAP - CAP editor and reader need scrollbars 46980 Accessory Portlets - CAP - no error message is displayed when deleting a linked document 46983 Accessory Portlets - CAP - NullPointerException in CAPPortlet when not logged in 46737 Accessory Portlets - eGuide reporting failed login only after search attempt 47665 Accessory Portlets - Additional DOC needed for GroupWise portlets 47682 Accessory Portlets - Error when viewing GroupWise mail portlet containing messages with Japanese 45170 Accessory Portlets - Problems using HTML Accessory Portlet 43360 Accessory Portlets - move njclv2r.jar to a new clear case location 43176 Accessory Portlets - all source should contain sample copyright tag (not standard) 42909 Accessory Portlets - IMAP throws null pointer exception retrieving messages with attachments 46964 Accessory Portlets - Need upload functionality for CAP portlets 46976 Accessory Portlets - CAP - Clicking edit on a jpg file does not launch correct editor 47530 Accessory Portlets - Child shared pages do not visually render below parent in a 3 generation display 41230 API (Director Portal) - Portal Aggregator throws exceptions when running with multiple threads 46638 API (Director Portal) - Getting "LDAP connection not available" when calling getUserInfoByUserUUID() 43562 Assistant-EJB (XWB) - EJB persistent file screen throws exception after deleting a row and focusing. 34511 Assistant-EJB (XWB) - Allow the ability to double click a method to edit it 47733 Assistant-Form - NoSuchMethodError trying to create/open an XForm 41032 Assistant-Form - Schema used in form generation should be set in model attribute 47080 Assistant-Form - Form wizard - repeat blocks UI needs work 46115 Assistant-HTML to XHTML - HTML TO XHTML wizard cannot handle more than one input file at a time 46940 Assistant-JavaBean (XWB) - DEFECT000376301 Input data will disappear after you click the "Up" button. 42948 Assistant-RPL (Director PF) - Checkpoint activity of generated rpl flows not useful 46875 Assistant-Tag Handler (XWB) - DEFECT000373499 tag handler wizard - wrapped text & inproper localized text 46943 Assistant-Web Service (XWB) - DEFECT000376307 A select box unusual display when you create a Web Services 34022 Assistant-Web Service (XWB) - Add wizard page to allow entry of multiple namespace-to-package mappings 43196 Assistant-Web Service Flow - Wizard generates input ctrl when schema says text content is illegal 46941 Assistant-XML - DEFECT000376302 There is a little strange square behind the right arrowhead. 46114 Assistant-XSL - XSL Wizard does not validate for XML file as input 47741 Base Servlet (Portal Tier) - support for xForms IE plugin in the portal 45562 Cache Coordinator (Director FW) - Unexpected caching message on Login 47059 Cache Coordinator (Director FW) - Sax parsing errors when starting the Cache Coordinator in Netware 34083 CM Search Services (incl. Autonomy) - Upgrade to Autonomy DRE 4.x 47026 CM Tasks (Director CM) - Class EboTaskManager does not stop EboTimerFactory during undeploy 45448 Content Management (Director CM) - add mime types to fw config for OpenOffice when available 46703 CSS Editor - DEFECT000366343 Add content tags error in Director CSS Editor 47672 Data Data/Access (Portal Tier) - "Illegal mix of collations" is caused when creating a director designer project 47061 Data/Data Access (Director FW) - NPE in EboKey.toString() method 35268 Deploy (Director Design time) - EJB jar a requirement on Tomcat 46280 Deployment Descriptor Editor (XWB) - Error opening deployment descriptor with a Composer Project added 47071 Deployment Descriptor Editor (XWB) - Exception trying to add new role to EAR deployment descriptor 34479 Deployment Plan Editor (XWB) - No prompt to save DP when editor is closed, after automatic update from DD. 47568 Deployment Plan Editor (XWB) - Resource bundle error opening deployment plan editor 33656 Deployment Plan Editor (XWB) - CAR resourceReference mapping should have the same GUI as other project types 47635 Directory Service (Director FW) - JBoss Integration 36899 Directory Service (Director FW) - error when login PAC/PMC/Portal for Ldaprealm 33608 Directory Service (Director FW) - session does not get teminated right after calling logoff on WebLogic 44910 Docs & Help (Director) - Link to reference for device profile spec requires a logon now 44414 Docs & Help (Director) - Javadoc for EbiPortletAppModel getSecurityConstraints method signature is wrong 44960 Docs & Help (Director) - Help page defaulting to Start_Director_Start.html for HTML to XHTML wizard 46801 Editors (Director) - DEFECT000372426:Director - option [image tab] - truncated text 45801 Editors (Director) - Device Definition editor does not prompt for saving after switching to XML view 47074 Editors (Director) - NullPointerException trying to create a new Portal Option 46806 Editors (Director) - DEFECT000372429:portal - layout- general settings - truncated text 46802 Editors (Director) - DEFECT000372424:director - general settings tab - truncated text 46800 Editors (Director) - DEFECT000372425 Director[general tab] truncated text 47044 Editors (Director) - new PortalOptions wizard fails with NPE 46422 Editors (Director) - Creating a new rule makes SMC and App Server icons disappear from toolbar 46600 Editors (Director) - Theme editor labels need to be enlarged - Japanese 46387 Editors (Director) - Portlet Option editor needs to be able to add multi-language text 46696 Editors (Director) - DEFECT000370641 Button label is wrong translated in the edit window of a select 47662 Editors (Director) - Portal Option editor labels are appearing in English 47427 Editors (Director) - 2 sets of Find and Replace Dialog Boxes, 1 of the Replace boxes not always open 46711 Editors (Director) - DEFECT000373482 the cancel button does not work in the theme designer 41373 Editors (Director) - Director xml editors show * in source tab, though file hasn't been modified 47098 Editors (Director) - Save/Save As changes made in XML view, graphical view thinks it's modified 47018 Editors (Director) - XWB must have a check box for the external attribute on directories. 42949 ExpressPortal (OTB) - We need to replace the linux penguin in ExpressPortal error pages 47198 ExpressPortal (OTB) - Images are not displayed properly when running ExpresPortal using an IP address 46952 Find (XWB) - DEFECT000376657 open an error file when using find file output panel 42933 Form Designer - Class Dialog - Undo/redo of modify class styles does not show up in UI 46664 Form Designer - Class Dialog - DEFECT000370854 css styles will disappear after cut and paste 43079 Form Designer - Event Editor - xpath nav context wrong for setvalue expression (if using mult. instances) 44916 Form Designer - Property Inspector - Schema SimpleType with Restrictions not honored for control formatting 46908 Form Designer/Form tab - General Editing - DEFECT000375968 Japanese xform label garbled after set portal css theme & paste 47050 Form Designer/Form tab - General Editing - NPE on save from non-UI view when UI view has never been activated 44017 Form Designer/Form Tab - Layout Region - Error & strange behaviour after drag from non-layout region then undo 41100 Form Designer/Model Tab - XPath navigator not able to concatenate expressions 47156 General UI/Other (XWB) - Path to mySQL jar file not correct in xd.conf file 47867 General UI/Other (XWB) - Path in xd.conf for MySQL JDBC driver is incorrect on Linux 47070 General UI/Other (XWB) - Designer unable to locate MySQL Driver 46936 General UI/Other (XWB) - DEFECT000376384 cannot save the hide state in portal option 46970 General UI/Other (XWB) - Archive viewer date formats are not correct 45743 General UI/Other (XWB) - EboEarProjectSetupSubsystemPage uses String.getBytes() with no encoding 47899 jBoss (Director) - express.ear deployed failed on JBoss 4.0 47600 Layout Manager (Portal Tier) - Cannot sort child shared pages by priority 45803 Layout Manager (Portal Tier) - No Cancel link in Content Selector in Layout Manager 47884 Layout Manager (Portal Tier) - Problem after creating a personal page (can't modify, remove, or create another) 46857 Migration-Data (Director) - Data Migration Help About needs to be updated 47863 Migration-Data (Director) - DataMigration tool does not allow you to change the install path for browser 46913 Migration-Data (Director) - Migration Tool is not set up to obtain doc from web 47082 Migration-Data (Director) - NoClassDefFoundError: com/sssw/ebs/datamigrate/EboProcessMigrator 46912 Migration-Data (Director) - Migration Tool - browser default path is set to IE on Linux 46916 Migration-Data (Director) - WfProcessMigration.sh is not installed on Linux - only the batch file 46914 Migration-Data (Director) - WfProcessMigration does not work - ArrayIndexOutOfBoundsException 31734 Multi-page Layout (Portal Tier) - Multi page layout - Portal Theme Selector Page- missing Orange Flame image 47086 PAC/DAC (Director) - Navigation "simpleTree" layout broken in exteNd5.2 46073 PAC/DAC (Director) - portal management font inconsistence 42261 PAC/DAC (Director) - portal admin shouldn't change user password 45555 PAC/DAC (Director) - Confusing filter in Security Management when using LDAP 46044 PAC/DAC (Director) - Remove Create Database Tables feature from DAC 45657 Pageflow Designer (Director PF) - Copy Scoped Path panel should allow you to move paths up and down 41418 Pageflow Designer (Director PF) - Inbound Docs dialog (PI, form activity) shouldn't auto-close 47034 Pageflow Designer (Director PF) - xforms:group does not work properly in html renderer 46902 Pageflow Designer (Director PF) - Vulturing is not working for xform changes 42607 Pageflow Designer (Director PF) - Restrict Portlet Size = true, causes slashes 47033 Pageflow Designer (Director PF) - Nested repeats - index() function does not return proper value 46886 Pageflow Designer (Director PF) - New Request button fails from Results page of Web Service Pageflow 46846 Pageflow Designer (Director PF) - ClassCastException occurs after redeploying pageflow 43415 Pageflow Designer (Director PF) - Form processor locale is never being set 47608 PMC (Director) - Both the MIME type and the content must be supplied, or neither of the two. 45854 PMC (Director) - JP characters display as vertical line in Doctype Custom Fields(DEFECT000365768) 46040 Portal Admin UI - Localization:page uri isn't translated on Japanese 47217 Portal Admin UI - Mozilla: selecting on wrong page when creating shared/container page 46370 Portal Admin UI - zn_TW only, more CONTENT PREFERENCES pages are not fully localized 47192 Portal Admin UI - Using Double-Quotes in Shared or Container Page Names causes problems 47181 Portal Admin UI - Portal Page Admin - allowed dup page name for container page - causes stack trc 46816 Portal Admin UI - Error message when updating a copied DefaultContainer page for the first time 46817 Portal Data Import Export - import portlet registration failed with different war context name 47628 Portal Data Import Export - Need UI to not import ACLs 47616 Portal Data Import Export - Changes to Director API to handle rollback 47517 Portal Data Import Export - Portal Data Import Export UI should allow producer mapping 45640 Portal Preferences (Portal Tier) - Enh: Settings tab should fill in with the name after Registering a new Portlet 46869 Portal Preferences (Portal Tier) - portlet preference editor not working as expected 47540 Portal Preferences (Portal Tier) - Extra Carriage Returns get added to HTML after a 'SAVE' 45710 Portal Security - Deploying a project with exteNd LDAP realm with SSL breaks the portal 47035 Portlet Container - portal option links generate 'windowstate=normal' regardless of actual state 47130 Portlet Container - Portlet exception - Back to Default link 46093 Portlet Container - Typo in error message for missing preference 47144 Portlet Container - PortletContextImpl.getRequestDispatcher(..) error handling 47235 Presentation Manager (Portal Tier) - Personalize Page in Director 5.2 does not fully support https 46451 Presentation Manager (Portal Tier) - flawed xml encoding detection in EboPortalAggregationHelper method 42877 Presentation Manager (Portal Tier) - Seeing full paths instead of absolute paths in some cases 47184 Presentation Manager (Portal Tier) - Child shared pages do not render properly if name length is shortest. 44965 Presentation Manager (Portal Tier) - after edit gets redirected to portlet prefs editor, handle save like render req. 44596 Presentation Manager (Portal Tier) - "Maximize this porlet" should say "Maximize this content" 46517 Presentation Manager (Portal Tier) - Portlet edit button not localized 43713 Presentation Manager (Portal Tier) - Ability to assign groups to a particular container/shared page 42761 Presentation Manager (Portal Tier) - Very slow response using Administration Interface on NetWare 46414 Presentation Manager (Portal Tier) - Child shared pages do not disappear after you've hovered over parent shared page 46079 Presentation Manager (Portal Tier) - typo in EboPresentationLog when Force render timeout 46298 Profile (XWB) - Accelerator (D) on Server profile dialog is used more than once - Japanese 46915 Project Upgrade (Director XWB) - web.xml, portlet.xml, novell-portlet.xml not updated 46573 Project Upgrade (Director XWB) - Project upgrade text does not line up on Japanese machine 46901 Project Upgrade (Director XWB) - unwanted references to trove.jar and wssdk-ssl.jar 46900 Project Upgrade (Director XWB) - abstractMethodError during deploy 47359 Project Upgrade (Director XWB) - WAR upgrade fails if the data/workflow-process does not exist 46606 Project-Add (XWB) - Designer: Project>Director>Setup... Does not get active with 5.0 project 46504 Project-Compile/Build (XWB) - Build all throws NPE when JSP removed and deleted 34925 Project-Compile/Build (XWB) - Compiling 1000 Source Files - java.lang.OutOfMemory 47016 Project-Deploy (XWB) - Add support in the UI for the JBoss deployer 38582 Project-Deploy (XWB) - Deployment to exteNd 4.XX fails from Director/DUT 5.0 fails 46815 Project-New (XWB) - DEFECT000373221 project - truncated text 46945 Project-New (XWB) - Remove "Enable User Transaction" option from new project wizard 46675 Project-New (XWB) - ConcurrentModificationException on selecting new Project on Linux box 46848 Project-Settings (XWB) - MissingResourceException editing the Project Settings 46698 Project-Settings (XWB) - DEFECT000369679 Shortcut key can not work in the project settings window. 47896 Project-Settings (XWB) - Default the deployment verbosity setting to 1 for non-English 39685 Projects (Director) - portal application war needs boot entry 33227 Projects (Director) - Add information to search configuration pane in EAR wizard about Autonomy 37475 Projects (Director) - portlet.xml that gets created after director wizard does not conform to schema 46306 Projects (Director) - Project > Director > Information - copyright needs to be updated 37837 Projects (Director) - novell-portlet not merging nodes correctly 38220 Projects (Director) - The wizard that assembles the portlet descriptors into one, does not assemble al 46853 Projects (Director) - Case of project path is not maintained 38558 Projects (Director) - portlet application wizard builds bad portlet.xml file 37973 Projects (Director) - Hardcoded messages in the wizards need to be localized. 46738 Projects (Director) - Looks like some debug messages left in build process 47522 Projects (Director) - Resourceset.xml has incorrect entries for new Director war 42029 Projects (Director) - can't build portlet app 37486 Projects (Director) - contents of individual portlet's novell-portlet.xml needs to aggregated 46949 Projects (Director) - Directory LDAP Options panel does not keep administrator or password 39732 RPL Runtime (Director PF) - NPE in database pageflow after reload flow 46745 Rules Des/Engine (Director) - Content Query Action buttons not visible running in Japanese 42339 Sample Portlets/Components - njclv2r.jar contains .java source files 31502 Sample Portlets/Components - Weather Component is missing images 46862 Sample Portlets/Components - Incorrect rendering of xml components 47107 ScopedPath (Director FW) - Problems with URLs containing $CONTEXT_URL$ tokens 47128 ScopedPath (Director FW) - NPE in scoped path / xpath evaluation when XML file is in ResourceSet root 47127 ScopedPath (Director FW) - Scoped path using xpath in resource set returns empty string 47116 ScopedPath (Director FW) - ResourceSet ScopedPath return wrong results 46959 ScopedPath (Director FW) - Scoped Path for a password is not working for the GroupWise Portlets in 5.2 46095 Security Service (Director FW) - Locksmith user is not over written on subsequent deploys 47317 Session (Director FW) - Infinite loop in EboWhiteboardHttp if the session is null 46993 Session (Director FW) - invalid cookie causes NPE in EboCookieUtil.getCookie() 45785 Styling (Portal Tier) - Suggestion for xFormDetection.xsl to make links correct 47955 System Portlets/Components - GW Mail portlet does not seamlessly reconnect 47497 System Portlets/Components - GroupWise WebAccess Portlet does not display correctly the first time 47045 System Portlets/Components - Login and NewUser Portlet created fully qualified URLs for css and js links 27603 System Portlets/Components - if 14 components are placed in any quadrant the 14th will be over written by 13 44708 System Portlets/Components - Using MyNovell.com causes Navigation Portlet to Malfunction 47353 System Portlets/Components - Imbedded   in the mail subject causes display problem with GroupWise Portlet 47663 Tomcat (Director) - Need to add JBoss support to the design environment 46662 Tools (Director) - Netbeans parser DB files need to be regenerated for Director Designer 47870 Tools (Director) - Unable to launch SMC from Designer on Linux 47607 UI (Director) - Long list of pages makes Favorites push down into dark gray portion of image... 41440 UI (Director) - There are extra/unused images in the images folder 38701 Uncategorized (Director) - display director build/version #s to console on startup 46501 Uncategorized (Director) - LDAP access using SSL doesn't use Phaos 47850 Uncategorized (Director) - XML file needs to be cleaned up to remove comment 44516 UserService (Director FW) - Using XWB on Linux, LDAP datasource cannot be set to JNDI 46903 UserService (Director FW) - DAC user profile management's "Synch Base Attributes" is broken 46871 WebDav Client - Two different behaviors of WebDAV client behavior regarding login and logout 33640 WebDav Client - can't map WebFolder (WebDAV) on French machine 47011 WebDav Server - WebDAV Basic Authentication failure is not communicated to Client 46626 Wizards - 1.2 EAR has a 2.3 ContentMgmtService.war 46699 Wizards - DEFECT000371444 "Tab" key doesn't work on the EJB Imports panel. 46270 Wizards - Empty dialog should not be displayed when no resource elements are found 46748 Wizards - DEFECT000371445 "Tab" key doesn't work on the Java Interface panel. 47097 Wizards - Typo in Workflow Activity and Workflow Link descriptions 46408 Workflow Engine - getProcesses returns some finished process from EbiWFlowEngine 47132 Workflow Engine - Class loading Issue On WF Engine Startup 42665 Workflow Engine - Exception when using getNextWorkitem(context) in JavaActivity 46385 Workflow Engine - Unlocalized strings in com.sssw.wf.resources.EboQueueResources 47630 WSSDK General - -noinline flag to rmi2wsdl causes NullPointerException 47629 WSSDK General - Unexpected namespaces from rmi2wsdl 47157 XForms Processor-Server (XWB) - Pageflows with XFORMS failing to display in browser 47805 XForms Processor-Server (XWB) - Hint does not appear at runtime, only in XForms designer 40197 XForms Processor-Server (XWB) - ::repeat-item does not apply. 40635 XForms Processor-Server (XWB) - bind as readonly not working in html rendering-input fields are still editable 41400 XForms Processor-Swing - preview shows controls at larger height than specified 46821 XML Editor-General - DEFECT000372436: Ja : portal-componet[general settings tab] unlocalized text 46868 XML Editor-General - NPE when adding a new Option state
Copyright © 2004-2005 Novell, Inc. All rights reserved. Copyright © 1997, 1998, 1999, 2000, 2001, 2002, 2003 SilverStream Software, LLC. All rights reserved.