Release Notes for iPlanet Unified Development Server (UDS)

Version 5.0, SP1

Updated December 7, 2001




These release notes contain important information available at the time of the release of iPlanet Unified Development Server, Version 5.0, SP1 (UDS). Information on significant updates, known problems, fixed bugs, and other issues are addressed here. Read this document before you begin using this release of UDS.

These release notes contain the following sections:




General Information

UDS Version 5.0, SP1 contains fixes for problems that were found with iPlanet Unified Development Server, Version 5.0. This release is available to all currently supported customers through iPlanet's SubscribeNet service and will be shipped to new customers. New customers who want access to this release, please contact iPlanet sales.

The distribution for this release includes the following:

Changes in Distribution Format

The format for the distribution files has changed for this release. The section in this document, "UDS Distribution Files," provides information on how to prepare the downloaded distribution files for installation.

Note: UDS for the OS/390 platform is only available on IBM 3490 tape media. The SubscribeNet web site contains information about obtaining the UDS for the OS/390 distribution.




Supported Systems and Software

UDS Version 5.0, SP1 has been certified for specific combinations of hardware, operating systems, and third party software, as described in the platform matrix available at the following location:

http://docs.iplanet.com/docs/manuals/uds.html#matrix

Support for SOAP v1.1

UDS Version 5.0, SP1 conforms with SOAP v1.1, as defined by the W3C (http://www.w3.org/TR/2000/NOTE-SOAP-20000508), with some limitations.

Limitations include issues such as interoperability with systems that require or prohibit type specifications and support for arrays, unsigned integers, and In-Out parameters. For more information on SOAP support in UDS Version 5.0, SP1, including information on possible workarounds for some limitations, refer to the iPlanet Knowledge Base article 7655, available at:

http://knowledgebase.iplanet.com/ikb/kb/articles/7655.html




Updates in UDS, Version 5.0, SP1

This section lists the following significant updates that are included with iPlanet Unified Development Server, Version 5.0, SP1.

Windows XP Support

Support for Microsoft Windows XP Professional has been added for this release. This support is limited to the Windows XP Professional Edition and certification is only for UDS runtime and development clients. Refer to the platform matrix for complete information on supported systems and software.

Full Unicode Codeset Support

iPlanet Unified Development Server Version 5.0, SP1 provides full Unicode codeset support. UDS partitions can now run using the UTF-8 codeset. This release provides 31 new files for UTF-8 locales to support date, time, and monetary formats used in most countries.

This allows all UDS partitions, including iPlanet Integration Server EAI proxies and process engines, to use UTF-8 everywhere for character data representation.

The new locales provided with this release are:



Table 1    New locales provided with UDS Version 5.0, SP1

da_DK.utf8 

es_MX.utf8 

ms_MY.utf8 

de_CH.utf8 

fi_FI.utf8 

nl_BE.utf8 

de_DE.utf8 

fr_BE.utf8 

nl_NL.utf8 

en_AU.utf8 

fr_CA.utf8 

no_NO.utf8 

en_CA.utf8 

fr_CH.utf8 

pt_PT.utf8 

en_GB.utf8 

fr_FR.utf8 

ru_RU.utf8 

en_HK.utf8 

is_IS.utf8 

sv_SE.utf8 

en_MY.utf8 

it_IT.utf8 

zh_CN.utf8 

en_SG.utf8 

iw_IL.utf8 

zh_HK.utf8 

en_US.utf8 

ja_JP.utf8 

zh_TW.utf8 

es_ES.utf8 

ko_KR.utf8 

 

For details on locale support in UDS, refer to the iPlanet Knowledge Base article 7737, available at:

http://knowledgebase.iplanet.com/ikb/kb/articles/7737.html

Character Encoding Support for XML APIs

UDS Version 5.0, SP1 adds support for a wider variety of character encodings for XML documents. The XML APIs for the XMLParser, XMLDOM2, and XMLSAX2 libraries now support all of the encodings supported by UDS plus UTF-16.

Documentation for character encoding support is available from the UDS online help. After opening the online help, search in the index for "Character Encoding Support."

For more information on the XML parser and XSL processor in UDS, refer to the iPlanet Knowledge Base article 7717, available at:

http://knowledgebase.iplanet.com/ikb/kb/articles/7717.html

For further details on character encoding support in UDS, refer to the iPlanet Knowledge Base article 7737, available at:

http://knowledgebase.iplanet.com/ikb/kb/articles/7737.html




Bugs Fixed in UDS, Version 5.0, SP1

Below is a short description of critical bugs fixed (or otherwise resolved) in UDS, Version 5.0, SP1.



Table 2    Bug Fixed in UDS Version 5.0, SP1

Number

Category

Description

31315  

Display 

After modifying a message catalog, switching back to locale puts "garbage" characters in messages. 
31357  

System Management 

fcompile can fail when processing a bom file of 500 or more files. 
41774  

System Management 

Under OpenVMS, using fcompile in batch mode does not generate output errors. 
54413  

Web HTML Projects 

The ExpressClassHandler.HandleTag can cause poor performance when accessed by multiple clients. 
54680  

Database 

Error message "Informix SQLSTATE: IX000, Informix error: -479" generated processing long queries in Informix 9.2. 
54772  

Framework 

Automatic cloning of classes can lose public internal methods in the newly cloned class. 
55159  

System Management 

Compiling a workspace before a save operation on the workspace is complete can cause the IDE to hang. 
55337  

System Management 

Interpreted server partitions can crash when accessed by a large number of clients. 
55339  

System Management 

On OS/390 platforms, running start_nodemgr with out specifying "-fnd flag" can cause the start_nodemgr process to time out. 
55382  

Display 

The version number displayed in the Help>About iPlanet UDS box needs to be updated. 
55427  

Runtime 

Processing a UTF-8 document that contains a UTF-8 encoded version of the Unicode byte order mark can cause a segmentation fault. 
55445  

Display 

The Help>About iPlanet UDS box displays an incorrect product name and there are minor errors in the Splash screen. 
55451  

Installation 

Server node installations on Windows platforms are missing the FORTE_ROOT\userlib directory. 
55452  

Display 

The Application Launcher's System tab needs to be updated to use the current naming conventions for UDS. 
55476  

External Systems 

The OLE library shipped with UDS 5.0.0 was invalid. 
55514  

Installation 

The Windows uninstaller does not remove references in the registry to the name service and repository service. 
55530
55757  

Installation 

The license agreement needs to be updated and some minor typos fixed. 
55544  

Runtime 

Forte app hung after opening and closing (spawning) tasks repeatedly under Japanese Windows 95/98 with IME (Input Method Editor).  
55544  

Runtime 

Applications hang after opening and closing (spawning) tasks repeatedly under Japanese Windows 95/98 with IME (Input Method Editor).  
55573
55619  

Runtime 

Starting an iIS process engine can cause a segmentation or access violation in the Forte executable. 
55576  

Runtime 

Importing pex files that contain extremely long lines causes a segmentation fault. 
55590  

External Systems 

Enhancement request for ONC socket support that allows the listener queue length to be set using an environment variable. 
55592  

External Systems 

For Windows platforms, ole.lib is not in FORTE_ROOT\userlib and partitions including OLE do not compile. 
55689  

Runtime 

Importing a pex file can cause a segmentation fault because memory hasn't been allocated for a system font object. 
55694  

External Systems 

GenerateXMLServerJava creates non-conforming appdist\envname subdirectory if the environment name is greater than eight characters. 
55706  

Runtime 

Problem setting the partition thread package so an application can run on multiple platforms. 
55710  

External Systems 

The Microsoft RichTextBox v 6.0 ActiveX field does not recognize the initial click by a user. 
55769  

Runtime 

For VMS-DECNET, there are not enough communication channels available. 
55861  

Installation 

On some UNIX platforms, the UDS installer cannot determine if DB2 is installed when the DB2 directory is a symbolic link, and thus terminates before completing the installation. 
55881  

Display 

On Windows 98, menus options with child options do not always display the correct child options. 
55899  

Web Service Interface 

Client IP addresses that contain a 0 get corrupted by the Web service object. 
55907  

Display 

Mnemonic access keys for submenu items do not work. 
55925  

System Management 

Enhancement request to add Econsole and Escript to UDS runtime distributions so runtime applications can have management utilities. 
55952  

Installation 

Installer for Alpha VMS 7.3 platform, during pre-installation check, searches for incorrect version of DECWindows runtime libraries. 
56009  

Display 

Mnemonic access keys in locales with multi-byte character sets fail, causing UDS to crash. 
56030  

Runtime 

Large compiled partitions that run without incident in previous versions of the product now fail with UDS 5.0. The partition compiles fine, but cannot be loaded. 
56080  

Runtime 

The unknown encoding handler for the XML parser is not being initialized correctly, causing a segmentation fault. 
56097  

Display 

Typeface error (SYSTEM ERROR: `0' is not a legal value for the TypeFace parameter) occurs on Window classes that access fonts that are not available. 
56108  

Runtime 

If you run an application that uses HTTPBaseRequest.Send from the workshop, canceling the running application can cause a segmentation fault. 
56195  

Web HTML Projects 

An HTMLScannerException occurs when navigating from master page to detail page 




Known Problems

This section lists known problems with this release, suggesting possible workarounds.



Table 3    Known Problems 

Bug Number

Details

56084  

Econsole may throw an exception when accessing a log file of a partition running with UTF-8 codeset.

Workaround: You can use any text editor, such as vi, to read the log file.  
55759
56259  

The default thread package (native threads) is not being set for DB2 partitions on Solaris platforms.

Workaround: The partition workshop incorrectly assigns Forte threads in this situation. To workaround this problem, specify Native threads in the workshop before running autocompile. 
56325  

On OS/390 (MVS) platforms using DB2, the flag that automatically prefixes the DB username (cfg:18:1) does not prefix the username to the tablename when using the UNION query statement. 




UDS Distribution Files

The installation guides provided with this release do not describe how to unpack the distribution files before you begin installing the software. This section describes how to unpack the distribution files and then begin the installation process.

Distribution File Formats

This release is available as a download from iPlanet's SubscribeNet service for currently supported customers and on CD for new customers. The format of the distribution files varies slightly, depending on whether you download the files or receive them on a CD.



Table 4    Distribution Files for UDS 

Distribution Source

Details

SubscribeNet 

Distributions from SubscribeNet are available according to platform. Each platform contains a single tar (or zip) file that itself contains all the UDS product components for that platform. Extracting the contents of this file produces a tar or zip file for each component. The following section, "Unpacking a UDS Distribution," describes how to extract the distribution files for each product component prior to installation. 

CD 

New customers to UDS receive a set of UDS distribution CDs. Each UDS product component is in a tar (or zip) file on a separate CD. The following section, "Unpacking a UDS Distribution," describes how to extract the distribution files for each product component prior to installation. 

Unpacking a UDS Distribution

The process for unpacking the distribution varies according to the platform.

The following sections provide instructions for unpacking the files into a local directory for each platform. After unpacking the files into a local directory, you can follow the procedures in the installation guides to proceed with installing UDS. The following installation guides are available from the UDS Version 5.0 Documentation distribution:

Windows Platforms

For Windows platforms, the distribution file is a self-extracting executable file that begins with the prefix "pc_w32_." For example, the self-extracting executable for UDS Runtime is:

pc_w32_RTV.exe

Execute this file to unpack the distribution to a local directory. After unpacking the file, proceed with the installation, as described in the sections for installing on Windows platforms in the installation guides.

UNIX Platforms

For UNIX platforms, the distribution file is a tape archive (tar) file whose contents must be extracted to a local directory prior to installation. Each UNIX platform has a separate distribution file. For example, the following distribution files are available on the UDS CD:

axp_osf_dev.tar (Compaq Tru64 UNIX)
hp_ux_dev.tar (HP 9000)
ibm_aix_dev.tar (IBM RS/6000)
seq_ptx_dev.tar (Sequent)
sun_sol_dev.tar (Sun SPARC)

Before extracting the files, make sure you have enough disk space to hold the contents of the tar files. The following table lists the disk space requirements for the contents of the extracted files.



Table 5    UNIX Disk Space Requirements for Extracting Distribution Files 

UDS Product Component

UNIX Platform

Disk Space Required (Approx.)

UDS  

IBM RS/6000

Other Platforms 

92 MB

80 MB 
Runtime Version  

IBM RS/6000

Other Platforms 

46 MB

34 MB 
Web Enterprise  

Compaq Tru64 UNIX
IBM RS/6000
HP 9000

Other Platforms 

62 MB

 

45 MB 
Express  

All Platforms 

7 MB 

To extract the installation files, mount the CD and copy the appropriate distribution file for your platform to a local directory. Then use the tar command to extract the installation files. For example, on Sun SPARC the command would be:

tar xvf sun_sol_dev.tar

The extracted files reside in a top-level CDROM_PlatformName directory that corresponds to a root directory on a CD image. You can now proceed with the installation, as described in the sections for installing on UNIX platforms in the installation guides.

Compaq Open VMS Platform

For Open VMS, the distribution file is a self-extracting executable file that begins with the prefix "axp_vms_." For example, the self-extracting executable for UDS Runtime is:

axp_vms_dev.exe

Copy this file from the CD to a local directory and then execute your copy of the file:

run axp_vms_dev.exe

This unpacks the distribution to your local directory. After unpacking the file, proceed with the installation, as described in the sections for installing on Open VMS in the installation guides.




Documentation Errata

This section provides corrections to significant errors or omissions in the documentation provided for UDS, Version 5.0, SP1.

Documentation References to the Platform Matrix

The iPlanet UDS System Installation Guide and other manuals provide an outdated URL to the iPlanet Unified Development Server platform matrix. The correct URL to the platform matrix is:

http://docs.iplanet.com/docs/manuals/uds.html#matrix




How to Report Problems

If you have problems with UDS, contact iPlanet customer support using one of the following mechanisms:

So that we can best assist you in resolving problems, please have the following information available when you contact support:




For More Information

Useful iPlanet information can be found at the following locations:

Use of iPlanet Unified Development Server is subject to the terms described in the license agreement accompanying it. Copyright © 2001 Sun Microsystems, Inc. All rights reserved.

Last Updated December 07, 2001