Novell exteNd Director 4.1 Standard Edition SP2 Readme August 30, 2004 Overview Novell exteNd Director 4.1 Standard Edition Support Pack 2 resolves bugs from the initial release of exteNd Director 4.1 Standard Edition. 1.0 New in Novell exteNd Director 4.1 SP2 2.0 Defects Resolved in Novell exteNd Director 4.1 SP2 3.0 Known Issues with Novell exteNd Director 4.2 SP2 4.0 New in Novell exteNd Director 4.1 SP1 5.0 Defects Resolved in Novell exteNd Director 4.1 SP1 6.0 Known Issues with Novell exteNd Director 4.1 SP1 7.0 exteNd Director Documentation 8.0 System Requirements 9.0 Running Novell exteNd Director Standard Edition on Novell exteNd Application Server 10.0 Technical Support Information 11.0 Legal Notices 1.0 New in Novell exteNd Director 4.1 SP2 There are no new features in this support pack. 2.0 Defects Resolved in Novell exteNd Director 4.1 SP2 - Issue where Query Gadgets could handle only one connection object to a database. - Lost connection error (504) when using onDemand Budget Handler gadget with iChain. For more information, see the "Known Issues with Novell exteNd Director 4.1 SP2" section of this document. - Portal communities showing each user multiple times in the "team member list." - Issue where the Portal Stats gadget did not show statistics for other portal servers. - The activeX control, localexec, allows any .exe to run on the client workstation. 3.0 Known Issues with Novell exteNd Director 4.2 SP2 This section explains issues you might encounter while installing and operating Novell exteNd Director 4.1 SP2 3.1 Cannot Upload a File That Includes Extended Characters When you create a file that includes specific extended characters in the filename, this file becomes corrupted after you upload it using the Network File gadget. 3.2 Lost Connection to Origin Server Error (504) on iChain If you are not using iManager on the same box and are experiencing long delays, add the following to PortalServlet.properties: System.SyncRequests=false 4.0 New in Novell exteNd Director 4.1 SP1 The following is a list of the new features in exteNd Director 4.1 SP1: - Configure Authentication gadget to simultaneously log out of exteNd Director and iChain. - Create self-defining macros. - Disable single sign-on by turning off Net Identity setting. - Set up forgotten password recovery and password self service (you must have iManager 2.0 or 2.01 to use this feature). - Reduce user login time using Dynamic Group caching. - Support exteNd Application Server. - Support JVM 1.4.2 and xerces. - Set all passwords to the same encryption string to prevent locking user passwords. 5.0 Defects Resolved in Novell exteNd Director 4.1 SP1 - Setting on directory flags where rights were not always granted. 6.0 Known Issues with Novell exteNd Director 4.1 SP1 This section explains issues you might encounter while installing and operating Novell exteNd Director 4.1 SP1. For more information about known issues, see TID (http://support.novell.com/cgi-bin/search/searchtid.cgi?/10081069.htm) 10081069. 6.1 Installation For complete installation instructions, see the Novell exteNd Director Documentation (http://www.novell.com/documentation/lg/nedse41). If Tomcat is not located in the root drive, an error might occur that the Web application server was unable to successfully expand the nps.war file. This means some of the paths that are extracted from the nps.war file exceed the allowed operating system character limit. To resolve this error, install the Web application servers at the root of your drive. 6.2 Upgrade For complete upgrade instructions, see the Novell exteNd Director Documentation (http://www.novell.com/documentation/lg/nedse41). You might encounter an Error 500 after upgrading to Novell exteNd Director. If this occurs, do the following: 1. After you upgrade, move the new exteNd Director files out of the webapps directory to a temporary location, then delete the files from that directory. 2. Copy your old Novell Portal Services files back into the webapps directory. 3. Copy the new exteNd Director files back into the webapps directory and overwrite the old files. 6.3 Unable to Edit Portal Administrators after Renaming Container If you want to rename the container where an administrator was created, you need to rename the container in the System.PortalConfigurationObjectDN file then restart exteNd Director. Otherwise, exteNd Director will no longer recognize that object. 6.4 Screen Might Be Blank After Typing Server/nps On some systems, only the word "com" might appear when you type server/nps. This occurs if you attempt to access Novell exteNd Director before and after you configure it. You need to type server/nps/index.html or http://server/nps/servlet/portalservice. 6.5 Some Strings in the Registration Gadget Appear in Only English Some of the strings in the Registration gadget are not translated. 6.6 Some Gadgets Might Not Work After the Upgrade If you are upgrading from a previous version of Novell Portal Services, you might need to reconfigure some of your gadgets after you upgrade. For information about configuring gadgets, see the Novell exteNd Director documentation (http://www.novell.com/documentation/lg/nedse41). 6.7 HTML Gadget Gets Invalid URL Message When Pointing to SSL Page An invalid URL message occurs if you have a gadget that points to a Web page with SSL links or links that redirect to an SSL page and have redirectthroughportal=on. To resolve this error, you need to import the root CA certificate into the java cacerts file. Example command: keytool -import -alias customcacert -keystore cacerts -file customcacertfile.cer 6.8 exteNd Director on Windows with exteNd Application Server Does Not Connect to SSL Installing Novell exteNd Director on Windows using the exteNd Application server does not connect to the directory using SSL. An error message indicates that it cannot find the directory server. 6.9 Additional Community and Administration Pages Might Appear After the Upgrade Currently unresolved. 6.10 Latency Problem with Using Chat Gadget on Internet Explorer Chat gadget becomes inactive when you use it on Internet Explorer v6 SP1 with the Sun Java plug in for version 1.3.1. 6.11 Container Gadget Shown in Commander List Do Not Work Container gadgets (Admin, PreferencesContainer) that show in the Commander gadget list do not work. To use these gadgets, access the gadgets through pages. This can be addressed when configuring the Commander gadget. 6.12 Issues With SunOne Application Server 7 To resolve the issues with the SunOne application server 7, you need to open the servlet.policy file and permissions. 6.12.1 Accessing Novell exteNd Director When you install Novell exteNd Director on SunOne 7, you need to add the following permissions for it to run properly (make sure each permission stays on one line):grant{ permission java.security.SecurityPermission "putProviderProperty.SSLProvider"; permission java.security.SecurityPermission "insertProvider.SSLProvider"; permission java.security.SecurityPermission "insertProvider.SunJSSE"; permission java.security.SecurityPermission "setProperty.sun.ssl.trustmanager.type"; permission java.util.PropertyPermission "java.protocol.handler.pkgs", "read,write"; permission com.sun.net.ssl.SSLPermission "setHostnameVerifier"; permission java.lang.RuntimePermission "setFactory"; permission java.io.FilePermission "/exteNd.xar/-", "read,write,delete"; };The /exteNd.xar/ is the resource set directory. The path to this directory might be different on your machine because its location is based on whatever Java is reporting as your user.home directory. Wherever the path is located, the directory needs the beginning quote ("), dash after the forward slash at the end of the path (-), and the ending quote ("). 6.12.2 Changing Community File Store Location Prevents Community Access To access communities after changing the File Store Location, you need to add the following permission to specify a cifs/smb share to use (make sure each permission stays on one line):grant{ permission java.util.PropertyPermission "*", "read,write"; }; 6.12.3 Running Servlet Configuration Before you run the servlet configuration on Solaris/SunOne Application server 7, you need to add the following permissions (make sure each permission stays on one line):grant { permission java.lang.RuntimePermission "createClassLoader"; permission java.net.NetPermission "specifyStreamhandler"; permission java.lang.RuntimePermission "setContextClassLoader"; }; 6.12.4 Using CIFS Provider on SunOne Application Server 7 To use the CIFS provider, you need to add the following permission (make sure the permission stays on one line):grant{ permission java.util.Property.Permission "*","read,write"; }; 6.13 Network File Gadget Does Not Upload Files or Create Directories in Solaris Currently unresolved. 6.14 NetBIOS Names for NetWare Fail Using CIFS Provider Using the Network File Gadget configured with the CIFS provider, you must use an IP address or DNS name for NetWare servers when configuring the Initial Destination Entity. A NetBIOS name for a Windows server will work. 6.15 Alta Vista Gadget Does Not Return Results on SunOne 7 Possible issue with SunOne 7 configuration. Currently unresolved. 6.16 SunOne Application Server Gadgets Might Not Appear in the Commander Gadget If this occurs, stop and restart the application server. 6.17 Chat Gadget Hangs on Linux and Solaris The Chat gadget might hang on a machine hosted by Linux or Solaris. It might also hang when using it through BorderManager NAT and iChain. 6.18 Secure All Messages Does Not Work in the Chat Gadget If you configure the chat gadget to use HTTP and Secure All Messages together, the applet does not find any other users. If you turn Secure All Messages off, it locates the other users and functions properly. 6.19 Drag and Drop Does Not Work With Netscape 7.01 The change layout buttons work, but not the drag and drop feature. 6.20 Commander Gadget Does Not Automatically Open In Netscape This occurs only when the pop-up blocker is enabled. Disable the pop-up blocker feature for this to function properly. 7.0 exteNd Director Documentation For complete exteNd Director installation and configuration instructions, see the Novell exteNd Director Documentation (http://www.novell.com/documentation/nedse41/treetitl.html). 8.0 System Requirements 8.1 Minimum Novell exteNd Director Requirements - Operating systemWeb ServerWeb application servereDirectory 8.6.2 or later (NetWare 6.5 requires eDirectory 8.7.1 or later)JVM 1.4.0 or later This release of Novell exteNd Director supports JVM 1.4 on the Novell exteNd Application Server. You can get the required JVM from the Novell Product Download site (http://download.novell.com/filedist/pages/PublicSearch.jsp). 8.2 Operating Systems Supported by Novell exteNd Director - NetWare 6.5 with the exteNd Application Server 5.1NetWare 6.0 with Support Pack 3Linux (SuSe 8.2, Redhat 8.0, Red Hat AS 2.1)Solaris 8Windows 2000 SP2 or later with the exteNd Application Server 5.1Windows 2003 8.3 Minimum Memory Requirements - 512 MB RAM140 MB free space 8.4 Web Browsers Supported by Novell exteNd Director - Netscape Navigator 7.0 or laterInternet Explorer 6.0 or later for Macintosh; Internet Explorer 5.01 or later for a PC 8.5 Tested Operating System, Web Server, Web Application Server, and JVM Combinations These configurations include, but are not limited to the following: NetWare 6.5 - Web server: Apache 2.0.xWeb application server: Tomcat 4.1.18, Novell exteNd Application Server 5.1JVM: Novell 1.4.0 or later NetWare 6.0 SP3 - Web server: Apache 1.3.27Web application server: Tomcat 4.1.18JVM: Novell 1.4.1 or later Linux (SuSe 8.2, Red Hat 8.0, Red Hat AS 2.1) - Web server: Apache 2.0.44Web application server: Tomcat 4.1.18JVM: Sun 1.4.2_0x Solaris 8 - Web server: Apache 2.0.44Web application server: Tomcat 4.1.18JVM: Sun 1.4.2_01 Windows 2000 SP2 and SP3 - Web server: IIS 5.0, Apache 2.0.44Web application server: Tomcat 4.1.18, Novell exteNd Application Server 5.1 with JVM 1.4.2_0x; Novell exteNd Application Server 4.0 with JVM 1.3.1_03 Windows 2003 - Web server: IIS 5.0, Apache 2.0.44Web application server: Tomcat 4.1.18, Novell exteNd Application Server 5.1 with JVM 1.4.2_0x; Novell exteNd Application Server 4.0 with JVM 1.3.1_03 9.0 Running Novell exteNd Director Standard Edition on Novell exteNd Application Server You must deploy to Silver Master for the Web application server to run properly. Running Novell exteNd Director with the Novell Application server 4.0 is supported on Windows 2000 SP3. The install and configuration processes are the same as other Web application servers. Refer to the Web and Application Services documentation (http://www.novell.com/documentation/lg/nw65/index.html) for instructions on how to deploy the nps.war file. 10.0 Technical Support Information For Technical support information, access the Novell Support Connection (http://support.novell.com/search/kb_index.jsp). 11.0 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.Copyright 2004 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.Novell is a registered trademark of Novell, Inc. in the United States and other countries.All third-party products are the property of their respective owners.