|
Sun ONE Integration Server EAI 3.2.1 Release Notes |
Sun™ ONE Integration Server, EAI 3.2.1 Release Notes
Version 3.2.1
Part Number 819-1529-11
March 2005
These release notes contain important information available at the time of the release of Sun™ Open Net Environment (Sun ONE) Integration Server, Enterprise Application Integration Edition, Version 3.2.1 (Integration Server, EAI). 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 Integration Server, EAI.
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_IntegrationServerEAI_32
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
January 4, 2005
Initial release of these release notes
March 8, 2005
Updated for release 3.2.1 and Windows support
About Integration Server, EAI, Version 3.2.1
This release of Sun ONE Integration Server, EAI 3.2 contains fixes for several issues identified in Integration Server EAI 3.1 and 3.2.0. See Table 2 for details.
Bundled with this release are the following products
- Sun ONE Unified Development Server 5.2.3
This is a patch release of Sun ONE UDS 5.2, and must be installed before you install Sun ONE Integration Server, EAI 3.2.1.
- Sun ONE Message Queue 3.5 SP2 Enterprise Edition
For customers downloading EAI 3.2 from the Sun Online Support Center, each supported platform 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.
This section describes the following significant updates that are included with Integration Server, EAI 3.2 :
What's New in Integration Server, EAI Version 3.2Installation Changes
The Sun ONE Integration Server, EAI 3.1 product was available for install in two editions: Professional Editiion and Enterprise Edition. Sun ONE Integration Server, EAI 3.2 can only be installed as Enterprise Edition. A Professional Edition installation is no longer available.
Here is how the 3.2 installer sequence looks:
IS-EAI, Enterprise Edition Option Menu
--------------------------------------
Option Descriptions
------ ----------------------------------
1 Install on UDS Central Server Node
2 Install on UDS Simple Server Node
3 Install Runtime Client Only
q Exit Installation Program
Enter installation option [1, 2, 3, q (default is 3) :
Log Rotation
Log file rotation is a new feature that has been added in EAI 3.2. This makes it possible to change the name of a JMS-enabled proxy's log file while the proxy is running. The log file name is modified by adding an extension to the default name. The new file is located in the same directory as the original one, i.e. $FORTE_ROOT/log.
The default log file name for a JMS-enabled proxy has the form proxyname_jms.log. To add an extension to this name, create a file named proxyname_jms.dat in $FORTE_ROOT/log that contains the extension you want to add. As soon as this file is created, a new log file named proxyname_jms_extension.log will appear in $FORTE_ROOT/log.
The RotateLogFile application located in $FORTE_ROOT/install/examples/util uses this feature to rotate the log file of all the partitions running in a given environment.
Bugs Fixed in Unified Development Server, UDS 5.2.3
Below is a short description of the most important bugs fixed in Unified Development Server, 5.2.3, the companion software for Integration Server, EAI 3.2.2. 5.2.3 is a patch release built upon Unified Development Server 5.2.0.
For a complete list of bugs fixed in Unified Development Server 5.2, please refer to
http://docs.sun.com/app/docs/coll/S1_UnifiedDevelopmentServer_52
Bugs Fixed in Integration Server, EAI 3.2.1
Below is a short description of the most important bugs fixed in Integration Server, EAI 3.2.1.
Table 4 Fixed Bugs in Integration Server, EAI 3.2.1
Bug Number
Description
6226944
Unix installer does not let user select platform distributions
5040414
MQ Proxy does not acknowledge messages when item not on worklist
5042742
Empty XMLData with SOAP causes proxy to generate an exception
5032812
Poor proxy performance with large activity lists
5023352
Unnecessary recovery of processes
4955465
Using assignment rules causes performance degradation
4996291
Make DBService reconnect timeout configurable
4877164
Cconsole help 'about' closes the window it is selected from
5011615
Process recovery time increases exponentially
4947235
Unhandled exceptions in the engine code results in engine hangs
4920371
Proxy does not reconnect when message broker is restarted
4833392
After engine recovery a timer is left in invalid state
Hardware and Software RequirementsFor information about hardware and software requirements for this release of Integration Server, EAI, refer to the platform certification matrix at the following location: http://docs.sun.com/coll/S1_IntegrationServerEAI_32
Installation NotesBefore you install Sun ONE Integration Server, EAI 3.2.1, you must install Sun ONE Unified Development Server 5.2.3. For Integration Server, EAI patch releases, you must install the corresponding patch release of UDS.
Unpacking the Distribution Files
This section describes how to prepare the downloaded files for installation.
Following table lists the distribution files available with this release.
Table 5 Integration Server, EAI Distribution Files
Distribution File
Platform
axp_osf_eai.tar
Compaq Tru64 UNIX
hp_ux_eai.tar
HP 9000
ibm_aix_eai.tar
IBM RS/6000
pc_w32_eai.exe
Windows platforms
sun_sol_eai.tar
Sun SPARC
After downloading the distribution, you need to unpack the files before beginning your installation. The instructions for unpacking the files vary according to platform. Refer to the following sections for instructions on unpacking the distribution files.Windows Platforms
For Windows platforms, the distribution file, pc_w32_eai.exe is a compressed file. To extract the files necessary for installation on Windows:
- Create a target directory for the extraction inside a top-level local directory.
For example, create an eai\eai_3_2 directory.
- Extract the contents of this pc_w32_eai.exe file to the eai_3_2 directory
You are now ready to proceed with your installation on Windows, as described in the iPlanet Integration Server Installation Guide.
When you extract Integration Server, EAI to the target directory on Windows, Sun ONE Message Queue 3.5 SP2 is extracted to a messagequeue3_5 directory within that target directory. Documentation for Sun ONE Message Queue 3.5 SP2 can be found at the following location:
http://docs.sun.com/app/docs/coll/MessageQueue_35_SP2
UNIX Platforms
The Integration Server, EAI install script for UNIX platforms is based on an installation CD image that includes directories for each platform certified for this release. Download the Solaris distribution to your Sun SPARC server and then extract the distribution files:
% tar xvf sun_sol_eai.tar
This creates a CDROM directory. The CDROM directory contains an ALL_UNIX directory and a SUN_SOL directory.
You are now ready to proceed with your central server node installation on Solaris, as described in the iPlanet Integration Server Installation Guide. After you complete your central server node installation, you can then proceed with either a server node or runtime client node installation.
When you extract Integration Server, EAI on Solaris, Sun ONE Message Queue 3.5 SP2 is extracted to a messagequeue3_5.zip archive within the SUN_SOL directory. Documentation for Sun ONE Message Queue 3.5 SP2 can be found at the following location:
http://docs.sun.com/app/docs/coll/MessageQueue_35_SP2
Errata and Integration Server, EAI Documentation UpdatesUse the Integration Server, EAI 3.0 Documentation with Integration Server, EAI 3.2. The Integration Server, EAI 3.0 documentation contains iPlanet branding. You can find the documentation at the following location:
http://docs.sun.com/coll/S1_IntegrationServerEAI_32
Documentation Errata
- In the readme for the ebXML example application located in the FORTE_ROOT/install/examples/fusion/ebxml directory, there is a section that is no longer relevant to the setup of the example application.
In the subsection “Modifying the smplecpa.xml CPA” of the section “Setup Related to Secure Trading Agent”, you can ignore the “From the remote directory:” directions.
- In the section on configuring JMS proxies in the Integration Server Backbone System Guide it should state that the only JMS message body types (or classes) Integration Server, EAI proxies can handle are TextMessage and ByteMessage.
- On p. 127 of the Integration Server Process System Guide, the following example command is given to start the Dump/Restore utility from a UNIX, OpenVMS, or Windows command line:
ftexec -fnict -fcons -fi bt:\$FORTE_ROOT\userapp\wfdrdump\c20\wfdrdu0
This command is incorrect. The correct syntax for the dump command looks something like this:
ftexec -fcons -fi bt:$FORTE_ROOT/userapp/wfdrwind/cl1/wfdrwi0 -d <directory>
The -d option is now required, not optional
Syntax for drdump command:
drdump -e engine_name -d directory_name [-v data_file_name] [-t registration|state|history]
- The FNscript commands AddToJvmArgs, RemoveFromJvmArgs, AddToJmsClasspath, and RemoveFromJmsClasspath are documented in the Integration Server Backbone System Guide as backbone level commands, when they only work at the proxy/component level.
Call the FNscript commands AddToJvmArgs, RemoveFromJvmArgs, AddToJmsClasspath, and RemoveFromJmsClasspath at the proxy/component level.
- The following supported FNscript commands are missing from the Integration Server Backbone System Guide:
- SetLocaleName
- ClearLocaleName
- SetLoggerFlags
- ClearLoggerFlags
SetLocaleName and ClearLocaleName Commands
Both Integration Server, EAI and the base Unified Development Server product have features for localization of your systems. These new FNscript commands allow you to configure an Integration Server, EAI backbone and its proxies for a specific locale from the set of locales supplied with these products:
SetLocaleName locale
The SetLocaleName command works at the backbone and proxy levels.
NOTE: A locale set at the proxy level overrides one set at the backbone level.
The locale argument uses the same format as the FORTE_LOCALE environment variable. For a description of FORTE_LOCALE, see the manual iPlanet UDS Building International Applications. For a complete list of locales supplied with Sun ONE Integration Server, EAI 3.2 and Unified Development Server 5.1, see SunSolve support article 7737.
ClearLocaleName
This command clears the locale set at the backbone or proxy level.
NOTE: If a proxy's locale is cleared, the locale set at the backbone level will take effect the next time that proxy is started.
SetLoggerFlags and ClearLoggerFlags Commands
Logger flags generate low-level data for problem analysis or override default behavior. The following FNscript commands allow you to configure logger flags for an Integration Server, EAI backbone and its proxies:
SetLoggerFlags file_name(file_filter)[file_name(file_filter)...]
SetLoggerFlags sets logging at the backbone or proxy level.
NOTE: Logger flags set at the proxy level override those set at the backbone level.
The parameter for SetLoggerFlags requires the same format as the argument for the -fl command-line logger flag. For more information about logger flags, see the UDS System Management Guide. For trace flags and configuration flags specific to the Integration Server, EAI backbone and proxies, see SunSolve support article 6914.
ClearLoggerFlags
This command clears the logger flags at the backbone or proxy level.
NOTE: If a proxy's logger flags are cleared, any logger flags set at the backbone level will take effect the next time that proxy is started.
- In the Integration Server Process System Management online help, the description of the Log flags field for all engine component startup parameters in the Configure New Engine and Reconfigure New Engine dialog boxes is incorrect.
Currently it states: Log flags
Specifies which tables (current state and history log) are enabled and which object state changes are recorded if the history log is enabled. String contains any of the following entries, separated by commas:
[STATE] [,LOG] [,LOG_ACTIVITIES] [,LOG_ATTRIBUTES] [,LOG_LOCKS] [,LOG_PROCESSES] [,LOG_SESSIONS] [,LOG_TIMERS]
The history log can grow quite large, so set logging selectively. You might have to monitor, back up, and flush the history log tables on a regular basis.
It should state: Log flags
Specifies log flags for internal debugging traces.
For more information about setting log flags and log flag syntax, see the chapter “Troubleshooting,” in the iPlanet Unified Development Server System Management Guide.
Documentation References to the Platform Matrix
The iPlanet UDS System Installation Guide and other manuals provide an outdated URL to the Integration Server, EAI platform matrix. The correct URL to the platform matrix is:
http://docs.sun.com/coll/S1_IntegrationServerEAI_32
Documentation in Text Format
You can download a full zipped set of Sun ONE Integration Server, EAI 3.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.
Compatibility IssuesWebsphere MQ 5.3 with IBM AIX 5.2
Customers who want to use Websphere 5.3 on IBM AIX 5.2 for use with Integration Server JMS proxies must use JDK/JRE versions listed in the software requirements of IBM's Websphere. For more information, please check the IBM website.
Microsoft Visual Basic .Net
In the newest version of Microsoft's Visual Basic product (Visual Basic .Net), the implementation of the declaration of session objects has been changed.
Code examples in the ActiveX chapter of the Process Client Programming Guide will not work with Visual Basic .Net. Likewise, the ActiveX example application, Expense Reporting, shipped with Integration Server, EAI 3.2 will not work with Visual Basic .Net. Numerous changes to the implementation of the Visual Basic environment require that you change ActiveX object declarations considerably.
The following short code examples demonstrate the previous way to declare an ActiveX session object and the new way to declare an ActiveX session object
Visual Basic 6 and earlier declaration of an ActiveX object
Dim DirectorySO As Object
Set DirectorySO = CreateObject("CONDUCTORCLIENT.WFDirectoryServiceCtl.1")
Visual Basic .Net declaration of an ActiveX object
Dim DirectorySO As ConductorClientLib.WFDirectoryService
DirectorySO = New ConductorClientLib.WFDirectoryService()
For customers with previous versions of ActiveX clients, Sun recommends using a previous version of Visual Basic to compile session code.
If you want to upgrade your ActiveX applications to use Visual Basic .Net, refer to Microsoft's Visual Basic documentation for information on how to migrate old ActiveX applications.
The ActiveX libraries included with Integration Server, EAI 3.2 are supported with the use of previous versions of Visual Basic and the new version of Visual Basic .Net.
Known IssuesThis section contains a list of the more important known issues at the time of the Integration Server, EAI 3.2 release.
Table 6 Known Issues with Integration Server, EAI 3.2
Bug Number
Description
4900080
ActiveX Expense Reporting example (plus doc) needs updating if customers decide to upgrade to Visual Basic .Net from previous versions.
Workaround: See the Incompatibilities section for details on Visual Basic .Net ActiveX object declarations.
4912790
Fnscript commands documented as backbone are actually proxy level only.
The FNscript commands AddToJvmArgs, RemoveFromJvmArgs, AddToJmsClasspath, and RemoveFromJmsClasspath are documented in the Integration Server Backbone System Guide as backbone level commands, when they only work at the proxy/component level.
Workaround: Call the FNscript commands AddToJvmArgs, RemoveFromJvmArgs, AddToJmsClasspath, and RemoveFromJmsClasspath at the proxy/component level.
4913426
The documentation for SetProtocol FNscript command states the following for setting an ebXML proxy’s protocol:
SetProtocol Name=ebXML ProcessName=procName | ProcessName=
The ProcessName argument is required. If the proxy is not intended to initiate a business process, the value for this argument should be left blank.
ProcessName=procName specifies a process registered with the process engine that an Initiator proxy service will interact with.
ProcessName= specifies that there is no process created by the service. Use this argument with Sender and Receiver services that interact with engine processes that are already started.
The ProcessName= argument does not work as intended.
Workaround: When specifying that there is no process created by the service, use Process= instead of ProcessName= to set the protocol.
4913444
AddtoJvmArgs and RemoveFromJvmArgs FNscript commands are not working correctly.
Workaround: You can only add one JVM argument at a time using AddToJvmArgs.
RemoveFromJvmArgs does not work. There is no workaround for this command.
How to Report Problems and Provide Feedback
If you have problems with Sun ONE Integration Server, EAI, contact Sun customer support using one of the following mechanisms:
- Sun Software Support services online at
http://www.sun.com/service/support/software
This site has links to the Knowledge Base, Online Support Center, and ProductTracker, as well as to maintenance programs and support contact numbers.
- 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
Sun Welcomes Your Comments
Sun is interested in improving its documentation and welcomes your comments and suggestions.
To share your comments, go to http://docs.sun.com and click Send Comments. In the online form, provide the document title and part number. The title for this document is Integration Server, EAI 3.2 Release Notes and the part number is 819-1529-10.
Additional Sun Resources
Useful Sun ONE information can be found at the following Internet locations:
- Documentation for Integration Server, EAI.
http://docs.sun.com/coll/S1_IntegrationServerEAI_32- Sun Documentation
http://docs.sun.com/prod/sunone- Sun Professional Services
http://www.sun.com/service/sunjavasystem/sjsservicessuite.html- Sun Software Products and Service
http://www.sun.com/software- Sun Software Support Services
http://www.sun.com/service/support/software- Sun Support and Knowledge Base
http://www.sun.com/supportraining- Sun Support and Training Services
http://www.sun.com/supportraining- Sun Consulting and Professional Services
http://www.sun.com/service/sunjavasystem/sjsservicessuite.html- Sun Developer Network
http://developers.sun.com- Sun Developer Support Services
http://developers.sun.com/prodtech/support- Sun Software Training
http://training.sun.com- Sun Software Data Sheets
http://wwws.sun.com/software
Copyright © 2005 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, Sun[tm] ONE and Sun One Integration Server EAI Edition 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.
Copyright © 2005 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, Sun[tm] ONE et Sun One Integration Server EAI Edition 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.