Release Notes for Unified Integrated
Framework
Version 6.0 SP2 (for iAS 6.0 SP2, SP3, and SP4)
Updated October 3,2002
These release notes contain important information relating to the Version 6.0 SP2 release of Unified Integrated Framework. New features and enhancements, installation notes, known problems, and other late-breaking issues are addressed here. Read this document before you begin using Unified Integrated Framework.
These release notes contain the following sections:
What's New in UIF, Version 6.0 SP2
UIF Tracing
UIF provides the tracing API that is used for connector developers as well as application developers for dumping messages in UIF runtime and connector runtime.
This feature is turned off, by default, in the UIF installation, for example, ENABLE_TRACING=0. When the user needs to turn on the UIF tracing switch, set ENABLE_TRACING=1 in the UIFTraceConfig.properties file.
Impact on UIF Applications and UIF Connectors:
-
Application Developers - Edit the UIFTraceConfig.properties in <iASinstall_location>/ias/APPS directory to enable Tracing and dump tracing messages at runtime.
-
Connector developers - Use the UIF Tracing API to dump messages at various points in the connector execution. Edit the UIFTraceConfig.properties to make matching flag entries.
Table 1 lists the changes and impacts on UIF Tracing.
Table 1 Changes and Impacts on UIF Tracing
UIFTraceConfig.properties file |
locate in <iASinstall_location>/ias/APPS directory
Out of the box entries are .....
ENABLE_TRACING=0
UIF_RUNTIME_CONNECTOR=1
UIF_RUNTIME_POOLING=1
UIF_RUNTIME_FUNCOBJ=1
UIF_RUNTIME_SP=1
This file can be extended by adding connector keys. For Example MY_CONNECTOR_POOLING=1
MY_CONNECTOR_EXECUTION=1
...etc |
ENABLE_TRACING |
Setting to 1 will enable tracing. Setting to 0 will disable tracing completely. |
UIF_RUNTIME_CONNECTOR |
Setting to 1 will dump the UIF and connector interaction messages Setting to 0 disables the messages. |
UIF_RUNTIME_POOLING |
Setting to 1 will dump the UIF pooling related messages. Setting to 0 disables the messages. |
UIF_RUNTIME_FUNCOBJ |
Setting to 1 will dump the UIF Function Object related messages. Setting to 0 disables the messages. |
UIF_RUNTIME_SP |
Setting to 1 will dump the UIF Service Provider related messages. Setting to 0 disables the messages |
Tracing API (for ECB SDK users only)' |
The tracing API is available in CoErrorLogMgr.h
HRESULT
UIFTraceMsg(
/* [in] */ LPSTR pTraceFlagName,
/* [in] */ LPSTR pFormat,
...) ;
Usage
#include "access_cErrorLogExt.h" UIFTraceMsg("MY_CONNECTOR_EXECUTION", "Executing function object %s", functionObjectName) ;
... and make the MY_CONNECTOR_EXECUTION flag entry in the UIFTraceConfig.properties file. When ENABLE_TRACING=1 and MY_CONNECTOR_EXECUTION=1, UIFTraceMsg will start dumping messages in to KJS log file. |
Single Click Installation
UIF is installed directly from the CD.
Impact on UIF Applications and UIF Connectors:
-
There is no longer a need to unzip the UIF bits on to a hard drive. You can run setup, directly from the CD.
Repository Browser
All the strings and image locations have been internationalized. The Repository.properties file containing the key value pairs is located in the <iASinstall_location>/ias/APPS directory. When being translated to Japanese, for example, this file needs to be renamed as Repository_ja.properties and the values need to be changed to Japanese. The same procedure needs to be followed for other languages, with proper language code. For example fr for French, fr_FR for French & France, en_US for English and US etc.)
The Repository Browser images are kept in the <iASinstall_location>/ias/APPS/bspimages/en directory. To localize to Japanese, for example, you should create a 'ja' directory under <iASinstall_location>/ias/APPS/bspimages and edit the image files. The image file name should not be changed.
For localized versions please contact you nearest iPlanet sales representative.
Impact on UIF Applications and UIF Connectors:
The Repository Browser can be viewed in different languages.
LDAP Failover Support
UIF runtime switches to a secondary LDAP server in case the primary LDAP server fails. The following describes two scenarios for LDAP failover support:
-
iAS installed with LDAP failover support:
-
When iAS is installed with LDAP failover support, UIF configurations are updated appropriately during the install time. Hence UIF fails over to the secondary LDAP server, when the primary one fails.
-
Secondary LDAP server added at a later time to iAS installation:
-
If a secondary LDAP server is added at a later time to iAS installation, the BSPConfig.properties file needs to be updated.
To Update the BSPConfig.properties File
-
Open the BSPConfig.properties file located in [iAS_install_directory]/ias/APPS.
-
Add the secondary host name to the key 'hostname', with a space.
For example, if the 'hostname' entry is mentioned as 'hostname=myprimaryhost', a secondary host name can be added as 'hostname=myprimaryhost mysecondaryhost'. The other LDAP parameters do not need to be modified.
Installation Notes
UIF can be installed directly from the CD. This feature is available on NT and Solaris. See Single Click Installation.
Upgrading from Unified Integrated Framework 6.0 SP1 to SP2
You should check to ensure that iPlanet Application Server 6.0 SP2 is installed before upgrading Unified Integrated Framework.
To Upgrade from Unified Integrated Framework 6.0 SP1 to SP2
-
Export the UIF Repository by clicking "Export Root" in the Repository Browser.
-
Uninstall UIF 6.0 SP1.
-
Install UIF 6.0 SP2.
-
Import the repository by clicking "Import Root" and then import the previously saved repository.
Known Problems and Limitations
Problem 533221
In UIF Version 6.0 SP2 release the "&" character can not be used in the repository.
Problem 526169
iAS Tuxedo Extension - FML32 numeric input buffers defaults to zero.
The UIF assigns a default value to integers when the XML is loaded into the repository.
Workaround
Wrap the integer in an array to avoid the integer being default to '0'.
How to Report Problems
If you have problems with Unified Integrated Framework Version 6.0 SP2, contact iPlanet customer support using one of the following mechanisms:
The telephone dispatch number associated with your maintenance contract
So that we can best assist you in resolving problems, please have the following information available when you contact support:
-
Description of the problem, including the situation where the problem occurs and its impact on your operation
-
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
-
Detailed steps on the methods you have used to reproduce the problem
-
Any error logs or core dumps
For More Information
Useful iPlanet information can be found at the following Internet locations: