Sun ONE Unified Development Server 5.2.0 Release Notes

Sun™ ONE Unified Development Server 5.2.0 Release Notes

Version 5.2.0

Part Number 819-0864-10
September 2004

These release notes contain important information available at the time of the release of Sun™ Open Net Environment (Sun ONE) Unified Development Server Edition, Version 5.2.0. Feature enhancements, bugs fixed, known limitations and problems, technical notes, and other information are addressed here. Read this document before you begin using this release of Unified Development Server.

The most up-to-date version of these release notes can be found at the Sun ONE documentation web site: http://docs.sun.com/coll/S1_UnifiedDevelopmentServer_52. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and manuals.

These release notes contain the following sections:

Revision History

Table 1  Revision History 

Date

Description of Changes

September 24, 2004

Initial release of these release notes

About Unified Development Server, Version 5.2.0

Unified Development Server 5.2.0 contains fixes for a number of issues identified in Unified Development Server 5.1. See Table 2 for details.

Use the Unified Development Server 5.0 Documentation with UDS 5.2.0. The Unified Development Server 5.0 Documentation contains iPlanet branding. You can find the documentation at the following location:

http://docs.sun.com/coll/S1_UnifiedDevelopmentServer_52

For customers downloading UDS 5.2.0 from the Sun Online Support Center, each supported platform now contains separate distribution files that must be unpacked before you can install the product. For information on unpacking the distribution files and installing the distribution, refer to "Installation Notes" in these release notes.

What’s New in Unified Development Server Version 5.2.0

This section describes the following significant updates that are included with Unified Development Server 5.2.0.

Merge of UDS and WebEnterprise

In Sun One UDS 5.2, WebEnterprise is merged with UDS. There is no longer a separate WebEnterprise installer. To understand what these changes mean to the WebEnterprise installation and configuration, read the following sections:

WebEnterprise Directories and Files in UDS 2.0 Installation Directory

The following directories and files are installed by the UDS 5.2 installer the same way they were installed by the WebEnterprise installer and the we_lib.scr script in previous UDS releases:

- html/
- install/web/src/
- install/examples/web/
- userapp/http/
- install/scripts/we_proj.scr
- install/scripts/web.dat

In addition to these directories and files, the UDS 5.2 installer creates the install/web/forte directory which contains all the UDS Web Server components.

Configuring WebEnterprise on a UDS Server Node

In UDS 5.2, the HTTP library is included as a public library in the system repository. Any UDS 5.2 repository will contain it by default.

The UDS 5.2 installer doesn't import the WebEnterprise projects. If you need them, run the fscript script we_proj.scr as indicated in the WebEnterprise Installation Guide.

Refer to the WebEnterprise Installation Guide, page 45, to see which WebEnterprise environment variables need to be set in your application.

Configuring WebEnterprise on a Sun One UDS Server Node

To install the UDS Web Server components, copy the FORTE_ROOT/install/web/forte directory at the desired location, usually in the root directory of the web server.

To configure WebEnterprise with Sun Java System Enterprise Web Server 6.1 see the article 75319 in SunSolve.

To configure WebEnterprise with Microsoft IIS Web Server see the WebEnterprise Installation Guide, page 58.

WebEnterprise Designer Components

All the WebEnterprise Designer components are installed by the UDS 5.2 installer. To use WebEnterprise Designer, you still need to install Express.

Support for Oracle® OCI 2 Library

In this release of UDS 5.2.0, the obsolescent Oracle 7 OCI routines have been replaced with Oracle OCI 2 routines. In other words, this release of UDS 5.2.0 uses the Oracle OCI 2 routines for accessing an Oracle database. These routines enables UDS customers to take advantage of Oracle's Transparent Application Failover (TAF) features. BLOB and CLOBs are supported as well.  In addition to the functionality in UDS 5.1, UDS 5.2.0 has the benefits of being able to use the Oracle Advanced Connect Data Parameters. The new Oracle OCI 2 routines library has been integrated into UDS 5.2.0 and will seamlessly replace the old library and no configuration changes will be needed to use the new library

This release contains changes to the Oracle OCI interface. To understand what these changes mean to your production environment, read the following sections:

Transparent Support for Oracle OCI 2 Library

The support for Oracle OCI 2 library is transparent to developers. The UDS Oracle library name 'qqOR' has been retained to enable transparency to customers. The UDS Oracle library 'qqOR' is a collection of routines using the Oracle OCI 2 interface instead of the old Oracle 7 OCI.  Applications that dynamically load 'qqOR' library using 'FindLibrary' will automatically load the new UDS Oracle library.  No configuration changes are required. 

If TAF (Transparent Application Failover) is being used and it reconnects in response to a command that may have changed the database, TAF issues a "ORA-25408: cannot safely replay call" message (exception) to the application. This "new" exception will need to be handled appropriately if TAF features are used in the application.

Support for old Oracle Library

 The original Oracle 7 OCI library has now been renamed to Oracle7 ('qqO7') and is accessible through a new Oracle7 resource manager (for backward compatibility only). It should be noted that reverting to Oracle7 (the previous library) will require potential system reconfiguration and possibly recompiling the application. To load the original library using 'FindLibrary', use LibName = 'Oracle7' , FileKey = 'O7' and ClassName = 'qqdb_OracleSession'.  We however recommend that the applications not be re-compiled or re-configured so as to take advantage of the seamless integration of the Oracle OCI 2 library.

NOTE :
This release of UDS 5.2.0 supports the use of multi-threaded connections with Oracle. Multi-threaded database connections are not supported with Informix or Sybase. 

Log File Rotation

A UDS application has been added in the examples that demonstrates rotation of  log files of the all the partitions running in an environment. Refer to the readme.htm file in FORTE_ROOT/install/examples/util to see how to install and run this application.

Certifications on new DB and OS versions

In this release of UDS 5.2.0, support has been added for new Database, Operating System versions and other third party software.
For more information and the exact combination of Database and Operating Systems certified, please refer to the  Hardware and Software Requirements Section.

Bugs Fixed in Unified Development Server 5.2.0

Below is a short description of the most important bugs fixed in Unified Development Server 5.2.0.

Table 2  Fixed Bugs in Unified Development Server 5.2.0

Bug Number

Description

4808677

4838265

UDS cannot connect to Oracle OPS because of complex connect string

Request for UDS to use Oracle TAF feature

4651787

Currently UDS does not support Sybase Numeric data type  when selected with texts

4911327

Shift-clicking on multiple select field with nothing selected causes a violation

4951108

ExpressServices.BusinessClient.Update can access violate when compiled

6155457

Object 'ExpressTabFolder' of class 'qqds_TabFolder' - method cannot be called on an unrealized field

6156716

WebEnt:  ".." notation in <?forte include> tag is not recognized anymore in UDS

6041355

Dumpstatus can cause a mutex deadlock

4995313

Provide easier handling of log files for online partitions

5052749

HTTPSupport does not CRLF characters before boundary

5058403

 <>Oracle Packed Decimal had no precision if first SetValue = null

5044544

UDS compile errors on z/OS 1.4 due to missing class prototype in appcexc.cdf

5015559

Express windows with customized 'validate on keystroke' feature display numeric data backwards

5034000

HTTPSupport library truncated results from client when transfer-encoding was set to chunked

4976422

DecimalData.Multiply() /Divide differences between UDS 5.0.x and 5.1.x

4985091

SetPrinterName() does not send output to designated printer in UDS.

4987133

Security scan can disable load balanced partitions

4992401

Cut & paste into a field fails after RunCommand()

4994002

Comments longer than 2037 characters cause compilation to fail

4996282

Inconsistent behavior in Express when using arrow keys on DropList widget

5004405

Submenu accelerator keys do not work on Wintel platforms

5011757

URL gets corrupted when tunnelling in HTTPSupport

4977740

Problem with the service name

4989034

Hash key distribution for integers is very inefficient for large amount of data

4996002

Race condition handling errors on remote IIOP calls can corrupt threads

4944266

Nodemgr crash when network interface is re-started in a connected environment

4944472

Window crashes if Line widget has property Style/Line Weight = NONE

4948792

Memory leak in XMLParser

4959161

UDS traceflag cfg:db:10:2 does not work with UDS CTLib

4947323

There is a syntax error in the header of $FORTE_ROOT/install/inc/cmn/sysact.h

4868200

UDS window flickers when tabfolder is built

4928701

Sublcassing LDAPSessions raises scope error at runtime

4941794

TabFolder flickers in UDS window when clicking on a droplist

4912170

UDS native thread partitions passing large data elements consume CPU

4917489

DecimalData.IsEqual() returns incorrect results

4919614

Native threads consuming CPU when constructing hash table

4854459

The WSDL file is generating all structs and arrays within the SO's namespace instead of a namespace that includes just the project name

4899032

 Install which allowed spaces in $FORTE_ROOT caused problems with fcompile

4905147

 If a ServiceName is not found, fortensapi will return a message with the original input which could contain a "malicious tag" and script that would then be run on the webserver

4908948

 UDS 5.1.3 / Missing Oracle DB Resource Manager on HP/UX

4995313

 Provide easier handling of log files for online partitions

4978004

 HTTP truncates the returned page to the browser - the transfer never completes

4955916

HTTPAccess partition crashes with error "...illegal multi level lock ..."

4910080

Security scan can disable UDS web access partition port

Hardware and Software Requirements

UDS Version 5.2.0 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.sun.com/coll/S1_UnifiedDevelopmentServer_52

Installation Notes

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 the Sun Online Support Center for Support customers only. This release is not available for new customers.

Table 3  Distribution Files for UDS 

Distribution Source

Details

Sun Online Support Center

Distributions from Sun Online Support Center 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.

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 and 5.1 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:

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:

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 4  UNIX Disk Space Requirements for Extracting Distribution Files 

UDS Product Component

UNIX Platform

Disk Space Required (Approx.)

UDS

Sun SPARC
IBM RS/6000
Compaq Tru64 UNIX
HP 9000
z/OS  

 144 MB
 185 MB
 171 MB
 167 MB
 282 MB

Runtime Version

Sun SPARC
IBM RS/6000
Compaq Tru64 UNIX
HP 9000

 78 MB
120 MB
 99 MB
 97 MB

Express

All Platforms

7 MB

To extract the installation files, 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:

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:

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

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.

IBM OS Mainframe

For z/OS, UDS is distributed as a 3490 tape. See the document entitled Installing Sun ONE UDS and the Sun ONE UDS Transaction Adapter on OS/390, on the Sun documentation web site, for details.

Errata and Unified Development Server Documentation Updates

In the Unified Development Server “Integrating with External Systems” manual, page 302 states:

“The following table lists the iPlanet UDS libraries for which iPlanet UDS provides C++ APIs, along with the files that map the C++ handle classes to TOOL classes. For more information, see the iPlanet UDS online Help. “

None of the files listed in the table, such as framework.txt, are in FORTE_ROOT/install/inc/handles directory, as the manual describes.

The files do not exist.

Documentation References to the Platform Matrix

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

http://docs.sun.com/coll/S1_UnifiedDevelopmentServer_52

Documentation in Text Format

You can download a full zipped set of Sun ONE UDS 5.0 documentation in ASCII file format.

We provide these files for individuals who are unable to use the PDF files as delivered. The ASCII files can be used with assistive technologies that enable specialized input and output capabilities and make the documentation accessible by people with disabilities.

Known Issues

This section contains a list of the more important known issues at the time of the Unified Development Server 5.2.0 release.

Table 5  Known Issues With UDS 5.2.0

Bug Number

Description

4658532

Fscript-generated Java files do not contain the correct type conversion.

In the manual Integrating with External Systems, Table 7-1 on page 139 states that a UDS long data type maps to a Java long data type. This is incorrect. A UDS long data type maps to Java int data type.

4720947

qqxd_attr class is not a subclass of qqxd_Node exception

Workaround:
Make the XMLDOM2 library a supplier plan to your XML project and instantiate something from it, like an Element, in one of the service object’s init methods. This forces the library to load.

4875645

Private attributes are found in WSDL generated by XML Server

Workaround:
XML Server does not serialize/deserialize the private attributes, so XML Server behavior is still consistent. Remove private attributes in generated WSDL document.

For example, strPrivate is a private string attribute in UDS. Under "types" in WSDL document, locate this private attribute and delete it before generating third party proxies and clients with the WSDL document.

<types>
  ....
  <complexType name="SimpleType">
    <sequence>
       <element name="i" type="xsd:int"/>
       <element name="sh" type="xsd:short"/>
       <element name="str" type="xsd:string"/>
       <element name="strPrivate" type="xsd:string"/>
    </sequence>
  </complexType>
</types>

How to Report Problems and Provide Feedback

If you have problems with Sun ONE Unified Development Server, contact Sun 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:

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. Email your comments to Sun at this address:

Please include the part number (819-0864-10) of the document in the subject line and the book title (Unified Development Server 5.2.0 Release Notes) in the body of your email.

Additional Sun Resources

Useful Sun ONE information can be found at the following Internet locations:

Copyright © 2004 Sun Microsystems, Inc. All rights reserved. U.S Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Use is subject to license terms. Sun, Sun Microsystems, the Sun logo, Java, Solaris and Sun[tm] ONE are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.
ORACLE is a registered trademark of Oracle Corporation.

Copyright © 2004 Sun Microsystems, Inc. Tous droits réservés.L'utilisation est soumise aux termes du contrat de licence.Sun, Sun Microsystems, le logo Sun, Java, Solaris et Sun[tm] ONE sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.UNIX est une marque déposée aux Etats-Unis et dans d'autres pays et licenciée exlusivement par X/Open Company, Ltd.