BEA WebLogic Integration Release Notes

Date	Summary of Changes
March 8, 2002	Added support for IBM AIX and Red Hat Linux. For details, see Platform Support and Hardware and Software Requirements.

Date

Summary of Changes

March 8, 2002

Added support for IBM AIX and Red Hat Linux. For details, see Platform Support and Hardware and Software Requirements.

Platform	Version	Database
Microsoft Windows NT	4.0 with Service Pack 6 or later	Oracle 8.1.6 Oracle 8.1.7 Cloudscape 3.5.1 SQL Server 7 SP3 SQL Server 2000 Sybase System 11.9.2 ^{See Note 2}
Microsoft Windows 2000	Professional with Service Pack 2 or later Advanced Server	Oracle 8.1.6 (thin driver) Oracle 8.1.7 (thin driver) Cloudscape 3.5.1 SQL Server 7 SP3 SQL Server 2000 Sybase System 11.9.2^{See Note 2}
Sun Solaris	7 (formerly referred to as 2.7) 8 - with system patches recommended by Sun Microsystems^{See Note 3}	DB2 UDB V7.1 Oracle 8.1.6 (thin driver) Oracle 8.1.7 (thin driver) SQL Server 7 SP3 SQL Server 2000 Sybase System 11.9.2 ^{See Note 2}
Hewlett-Packard HP-UX	11.0	Oracle 8.1.6 (thin driver) Oracle 8.1.7 (thin driver) SQL Server 7 SP3 SQL Server 2000 Sybase System 11.9.2 ^{See Note 2}
IBM AIX	4.3.3 5.1 with maintenance level 1	Oracle 8.1.7 (thin driver) DB2 7.2
Red Hat Linux	7.2	Oracle 8.1.7 (thin driver)

Platform

Version

Database

Microsoft Windows NT

4.0 with Service Pack 6 or later

Oracle 8.1.6
Oracle 8.1.7
Cloudscape 3.5.1
SQL Server 7 SP3
SQL Server 2000
Sybase System
11.9.2 ^{See Note 2}

Microsoft Windows 2000

Professional with Service Pack 2 or later
Advanced Server

Oracle 8.1.6 (thin driver)
Oracle 8.1.7 (thin driver)
Cloudscape 3.5.1
SQL Server 7 SP3
SQL Server 2000
Sybase System
11.9.2^{See Note 2}

Sun Solaris

7 (formerly referred to
as 2.7)
8 - with system patches recommended by Sun Microsystems^{See Note 3}

DB2 UDB V7.1
Oracle 8.1.6 (thin driver)
Oracle 8.1.7 (thin driver)
SQL Server 7 SP3
SQL Server 2000
Sybase System
11.9.2 ^{See Note 2}

Hewlett-Packard HP-UX

11.0

Oracle 8.1.6 (thin driver)
Oracle 8.1.7 (thin driver)
SQL Server 7 SP3
SQL Server 2000
Sybase System
11.9.2 ^{See Note 2}

IBM AIX

4.3.3
5.1 with maintenance level 1

Oracle 8.1.7 (thin driver)
DB2 7.2

Red Hat Linux

7.2

Oracle 8.1.7 (thin driver)

Change Request Number	Description
CR051037	The bulkloader command cannot be run with the initialize option.
CR051410	A deadlock situation can occur if insufficient connections are defined in the connection pool.
CR052102	In certain configurations, loading the user interface for action plug-ins from within the WebLogic Integration Studio sometimes fails due to different versions of serialVersionUID of javax.swing.text.JTextComponent for JDK 1.3.0.
CR055321	The zeroweight (formerly lightweight) client API throws a null pointer exception if isExistMailbox() is not called. When a mailbox is created, if the isExistMailbox() method is not called, any attempt to add a message throws a null pointer exception.
CR055751	User notification should occur when the wlcsystem user is assigned different passwords in the configuration file and the repository (such as the password and wlcsystem passwords, respectively).
CR055780	The documentation needs to provide additional clarification about how to configure WebLogic Integration for a clustered environment.
CR055832	The entry for com.bea.wlpi.admin.Admin.getTemplate() in Javadoc should be updated to the method's specified design.
CR056602	Format Tester's translate functionality fails if an MFL document is created in Format Builder with either an MFL or Field Codepage of Shift_JIS.
CR056858	Users who use Admin.getTasks() to produce a list of tasks often want to retrieve an InstanceInfo associated with each task. A new getInstanceInfo method in the Admin bean, available in Release 2.1 SP1, enables them to do so.
CR057621	An SQL exception may be thrown when data is being exported from the WebLogic Integration B2B Console. Resolution: In config.xml, the setting for JDBCConnectionPool should include a MaxCapacity setting of 80 or greater to avoid this exception while a connection is being established.
CR058834	A java.lang.NullPointerException exception can be thrown when the Test hyperlink for a service on the application view summary page for application views with Japanese names contains complex characters.
CR059193	A known issue with Microsoft SQL Server 7.0, where it loses the default value setting of database columns while copying, can impact the WebLogic Integration server, which relies on these default value settings, with an SQL exception being thrown. Resolution: When you need to copy a Microsoft SQL Server 7.0 database, for instance, when migrating a WebLogic Integration database, manually ensure that the default values are identical with the original values.
CR059362	An incomplete import operation occurs during the import of a workflow that contains an asynchronous application integration service call and an asynchronous response event to capture the service response. Before the workflow is started, the service is removed from the application view. When the workflow is executed, errors occur and a NullPointerException is thrown.
CR059429	During the import of a template in which the value of the start organization is set to a nonexistent organization, the first organization is selected.
CR059430	When a workflow is being imported, the Start Org (in the start node for a timed or event-started workflow) may not exist.
CR059725	If multiple timed events are concurrently scheduled, the system will re-execute the original timed event multiple times, because it is not being deleted from the database before the system reschedules the next timed event.
CR059933	Pathnames used by the MDBGenerator are incorrect.
CR059972	The encoding Cp037 is no longer defined as a valid Codepage value in Format Builder. An exception is thrown if you try to open an MFL document that contains a field with the Cp037 encoding. Resolution: Manually change the encoding to IBM037 in the field codepage specification, as follows. Change: <FieldFormat name='delim1' type='String' codepage='Cp037' length='2'/> to <FieldFormat name='delim1' type='String' codepage='IBM037' length='2'/>
CR060005	The WebLogic Integration B2B Console prevents updating a trading partner even when that trading partner has been made inactive.
CR060143	Invoking an undeployed application view service using the application integration plug-in puts the application view into an unstable state. Resolution: To return your application view to a stable state, test the service from the Application View Console or restart your WebLogic Server.
CR060156	The WebLogic Integration workflow instance ID is incorrectly persisted in certain circumstances.
CR060171	If you run a workflow developed with WebLogic Process Integrator 1.2 or 1.2.1 on a WebLogic Integration 2.0 or 2.1 system, your workflow loses its ability to retain references to stateless session beans.
CR060174	The MDBGenerator utility does not create deployment descriptors that correspond to WebLogic Server 6.1 required descriptors.
CR060202	If you create an Invoke Error Handler action in a workflow without creating an XML document (by leaving the editor blank), save the workflow, and then attempt to reopen it, an error message is displayed.
CR060239	The XSL Transform action cannot successfully produce a nonXML result (such as HTML output).
CR060412	Internationalization functions cannot use the XML editor to create XML messages or load existing XML files in the WebLogic Integration Studio because the encoding of the instance editor is hardcoded as UTF-8.
CR060421	After the server crashes, timed events and time-triggered start nodes that the user assumes can be rescheduled cannot be recovered as expected. Resolution: When you are defining a workflow template, you can indicate that you want a timed workflow or event to be recoverable, by selecting a new Recoverable check box in the Start Properties dialog box.
CR060600	The EDI adapter fails if WebLogic Integration is running on a DHCP machine and Power.Server! is running on a different machine that is configured statically or dynamically. Resolution: Use either of the following approaches to correct this problem: Collocate both Power.Server! and WebLogic Integration on the same machine. This machine can have either a static IP address or be DHCP. If Power.Server! and WebLogic Integration are running on separate machines, the machine on which WebLogic Integration is running must have a static IP address.
CR060824	It is no longer possible to assign the value of an XML variable to a string variable, because the XML variable value is now returned as a byte[] array, whereas the string variable contains code to convert a DOM node to a string.
CR061557	UNIX platform-specific issues exist for the migration script for WebLogic Integration 2.1.
CR061777	The Studio does not recognize case-sensitive template definition names.
CR062163	The document tree displayed in the XML Editor tree should be fully expandable when you are working in read-only mode.
CR062263	If you want to dequeue messages transactionally, you must have one of the following versions of WebLogic Server installed: WebLogic Server 6.1 SP1 + two rolling patches: CR057387_610sp1.jar and CR061378_610sp1.jar WebLogic Server 6.1 SP2 If you are using WebLogic Server 6.1 SP2 as your platform, contact BEA Customer Support for information about obtaining the latest patches. Note: If your platform is either WebLogic Server 6.1 or WebLogic Server 6.1 with SP1, and you try to remove a stateless session bean that is enlisted in a transaction that has not yet been completed, your instance of WebLogic Server will throw exceptions.
CR062265	Server crashes with complaint that PIPInput is null.
CR062268	Multiple threads execute a single workflow instance simultaneously.
CR062283	The error recovery message store is not being restored properly.
CR062301	Problems occurred with numeric parsing in different locales.
CR062303	Unexpected behavior occurs after a Workflow Changed dialog box is canceled.
CR062344	The ~config/bpmdomain/startWeblogic script is not working as expected on UNIX platforms.
CR062346, CR062347	Messages addressed to a nonexistent template instance should be deleted.
CR062406	Variable renaming was not working as expected during operations involving "null."
CR062472	EventAttribute produces inconsistent behavior when used on a missing JMS Property.
CR062633	Although it behaves as documented, the fact that ToInteger returns 0 for floating point arguments is unsatisfactory. In this release, ToInteger has been modified so that it never returns 0. If invalid data is passed to it, it throws an exception.
CR062903	The Admin.checkForTemplateInstances() method returns true if there are instances that have not completed yet. Request for clarification in documentation about the fact that this description refers to running instances.
CR062998, CR066034	Addressed messages sent to the same event node can fire multiple times.
CR063011	The problem that was caused by making multiple calls to the WebLogic Integration API from within a session bean has been fixed.
CR063066	An unexpected namespace error occurs during schema validation in a RosettaNet 2.0 conversation when a namespace is defined as an attribute of the root node of an XML document.
CR063124	Format Builder incorrectly processes large binary files.
CR063135	An exception is generated if you use the WebLogic Integration Studio after adding a new folder to the WLAI.Namespace.Root folder in the XML repository. Resolution: Do not add any custom folders to the WLAI.Namespace.Root folder in the XML repository.
CR063189	The Format Builder popup context menus are not accessible when the navigation tree is in certain states.
CR063403	In the Start workflow dialog box the same workflow is listed repeatedly for different effective dates, and it is impossible to differentiate between listings.
CR063458, CR063609	For RosettaNet RNIF 1.1 and RNIF 2.0, an exception was logged if you set the template variable retryCount to a value of 0.
CR063595	The ADK did not provide adequate support for radio buttons in Release 2.1.
CR063885	WebLogic Integration provides application integration functionality that allows you to create an application view with invalid characters.

Change Request Number

Description

CR051037

The bulkloader command cannot be run with the initialize option.

CR051410

A deadlock situation can occur if insufficient connections are defined in the connection pool.

CR052102

In certain configurations, loading the user interface for action plug-ins from within the WebLogic Integration Studio sometimes fails due to different versions of serialVersionUID of javax.swing.text.JTextComponent for JDK 1.3.0.

CR055321

The zeroweight (formerly lightweight) client API throws a null pointer exception if isExistMailbox() is not called. When a mailbox is created, if the isExistMailbox() method is not called, any attempt to add a message throws a null pointer exception.

CR055751

User notification should occur when the wlcsystem user is assigned different passwords in the configuration file and the repository (such as the password and wlcsystem passwords, respectively).

CR055780

The documentation needs to provide additional clarification about how to configure WebLogic Integration for a clustered environment.

CR055832

The entry for com.bea.wlpi.admin.Admin.getTemplate() in Javadoc should be updated to the method's specified design.

CR056602

Format Tester's translate functionality fails if an MFL document is created in Format Builder with either an MFL or Field Codepage of Shift_JIS.

CR056858

Users who use Admin.getTasks() to produce a list of tasks often want to retrieve an InstanceInfo associated with each task. A new getInstanceInfo method in the Admin bean, available in Release 2.1 SP1, enables them to do so.

CR057621

An SQL exception may be thrown when data is being exported from the WebLogic Integration B2B Console.

Resolution: In config.xml, the setting for JDBCConnectionPool should include a MaxCapacity setting of 80 or greater to avoid this exception while a connection is being established.

CR058834

A java.lang.NullPointerException exception can be thrown when the Test hyperlink for a service on the application view summary page for application views with Japanese names contains complex characters.

CR059193

A known issue with Microsoft SQL Server 7.0, where it loses the default value setting of database columns while copying, can impact the WebLogic Integration server, which relies on these default value settings, with an SQL exception being thrown.

Resolution: When you need to copy a Microsoft SQL Server 7.0 database, for instance, when migrating a WebLogic Integration database, manually ensure that the default values are identical with the original values.

CR059362

An incomplete import operation occurs during the import of a workflow that contains an asynchronous application integration service call and an asynchronous response event to capture the service response. Before the workflow is started, the service is removed from the application view. When the workflow is executed, errors occur and a NullPointerException is thrown.

CR059429

During the import of a template in which the value of the start organization is set to a nonexistent organization, the first organization is selected.

CR059430

When a workflow is being imported, the Start Org (in the start node for a timed or event-started workflow) may not exist.

CR059725

If multiple timed events are concurrently scheduled, the system will re-execute the original timed event multiple times, because it is not being deleted from the database before the system reschedules the next timed event.

CR059933

Pathnames used by the MDBGenerator are incorrect.

CR059972

The encoding Cp037 is no longer defined as a valid Codepage value in Format Builder. An exception is thrown if you try to open an MFL document that contains a field with the Cp037 encoding.

Resolution: Manually change the encoding to IBM037 in the field codepage specification, as follows. Change:

CR060005

The WebLogic Integration B2B Console prevents updating a trading partner even when that trading partner has been made inactive.

CR060143

Invoking an undeployed application view service using the application integration plug-in puts the application view into an unstable state.

Resolution: To return your application view to a stable state, test the service from the Application View Console or restart your WebLogic Server.

CR060156

The WebLogic Integration workflow instance ID is incorrectly persisted in certain circumstances.

CR060171

If you run a workflow developed with WebLogic Process Integrator 1.2 or 1.2.1 on a WebLogic Integration 2.0 or 2.1 system, your workflow loses its ability to retain references to stateless session beans.

CR060174

The MDBGenerator utility does not create deployment descriptors that correspond to WebLogic Server 6.1 required descriptors.

CR060202

If you create an Invoke Error Handler action in a workflow without creating an XML document (by leaving the editor blank), save the workflow, and then attempt to reopen it, an error message is displayed.

CR060239

The XSL Transform action cannot successfully produce a nonXML result (such as HTML output).

CR060412

Internationalization functions cannot use the XML editor to create XML messages or load existing XML files in the WebLogic Integration Studio because the encoding of the instance editor is hardcoded as UTF-8.

CR060421

After the server crashes, timed events and time-triggered start nodes that the user assumes can be rescheduled cannot be recovered as expected.

Resolution: When you are defining a workflow template, you can indicate that you want a timed workflow or event to be recoverable, by selecting a new Recoverable check box in the Start Properties dialog box.

CR060600

The EDI adapter fails if WebLogic Integration is running on a DHCP machine and Power.Server! is running on a different machine that is configured statically or dynamically.

Resolution: Use either of the following approaches to correct this problem:

Collocate both Power.Server! and WebLogic Integration on the same machine. This machine can have either a static IP address or be DHCP.
If Power.Server! and WebLogic Integration are running on separate machines, the machine on which WebLogic Integration is running must have a static IP address.

CR060824

It is no longer possible to assign the value of an XML variable to a string variable, because the XML variable value is now returned as a byte[] array, whereas the string variable contains code to convert a DOM node to a string.

CR061557

UNIX platform-specific issues exist for the migration script for WebLogic Integration 2.1.

CR061777

The Studio does not recognize case-sensitive template definition names.

CR062163

The document tree displayed in the XML Editor tree should be fully expandable when you are working in read-only mode.

CR062263

If you want to dequeue messages transactionally, you must have one of the following versions of WebLogic Server installed:

WebLogic Server 6.1 SP1 + two rolling patches: CR057387_610sp1.jar and CR061378_610sp1.jar
WebLogic Server 6.1 SP2

If you are using WebLogic Server 6.1 SP2 as your platform, contact BEA Customer Support for information about obtaining the latest patches.

Note: If your platform is either WebLogic Server 6.1 or WebLogic Server 6.1 with SP1, and you try to remove a stateless session bean that is enlisted in a transaction that has not yet been completed, your instance of WebLogic Server will throw exceptions.

CR062265

Server crashes with complaint that PIPInput is null.

CR062268

Multiple threads execute a single workflow instance simultaneously.

CR062283

The error recovery message store is not being restored properly.

CR062301

Problems occurred with numeric parsing in different locales.

CR062303

Unexpected behavior occurs after a Workflow Changed dialog box is canceled.

CR062344

The ~config/bpmdomain/startWeblogic script is not working as expected on UNIX platforms.

CR062346, CR062347

Messages addressed to a nonexistent template instance should be deleted.

CR062406

Variable renaming was not working as expected during operations involving "null."

CR062472

EventAttribute produces inconsistent behavior when used on a missing JMS Property.

CR062633

Although it behaves as documented, the fact that ToInteger returns 0 for floating point arguments is unsatisfactory. In this release, ToInteger has been modified so that it never returns 0. If invalid data is passed to it, it throws an exception.

CR062903

The Admin.checkForTemplateInstances() method returns true if there are instances that have not completed yet. Request for clarification in documentation about the fact that this description refers to running instances.

CR062998, CR066034

Addressed messages sent to the same event node can fire multiple times.

CR063011

The problem that was caused by making multiple calls to the WebLogic Integration API from within a session bean has been fixed.

CR063066

An unexpected namespace error occurs during schema validation in a RosettaNet 2.0 conversation when a namespace is defined as an attribute of the root node of an XML document.

CR063124

Format Builder incorrectly processes large binary files.

CR063135

An exception is generated if you use the WebLogic Integration Studio after adding a new folder to the WLAI.Namespace.Root folder in the XML repository.

Resolution: Do not add any custom folders to the WLAI.Namespace.Root folder in the XML repository.

CR063189

The Format Builder popup context menus are not accessible when the navigation tree is in certain states.

CR063403

In the Start workflow dialog box the same workflow is listed repeatedly for different effective dates, and it is impossible to differentiate between listings.

CR063458, CR063609

For RosettaNet RNIF 1.1 and RNIF 2.0, an exception was logged if you set the template variable retryCount to a value of 0.

CR063595

The ADK did not provide adequate support for radio buttons in Release 2.1.

CR063885

WebLogic Integration provides application integration functionality that allows you to create an application view with invalid characters.

1	CR036730
	Problem	In the WebLogic Integration Studio, OR joins can be triggered only once, and they cannot be inserted in loops.
	Platforms	All
	Workaround	None
2	CR037903
	Problem	When updating a user's properties in the WebLogic Integration Studio, you cannot modify the user's password.
	Platforms	All
	Workaround	Use the WebLogic Server Administration Console to update the user's password. See Starting, Stopping, and Customizing BEA WebLogic Integration for more information.
3	CR045158
	Problem	WebLogic Integration user and password information is exposed in the wlai.properties file. The user name and password associated with the host address are used by the event router to authenticate itself when posting events. This information is not available to the ApplicationViewDeployer when the Application View is deployed. The extra information is available in wlai.properties.
	Platforms	All
	Workaround	None, however we recommend selecting a user name other than system.
4	CR047229
	Problem	The user cannot scroll through text that is longer than the length of the text field in application integration plug-in event and start conditions.
	Platforms	All
	Workaround	Open the expression builder to build or view a condition for which the text is longer than the length of the condition text field.
5	CR048110
	Problem	When a data integration user tries to enter values on a tab in a binary window, the text being typed is not inserted at the location indicated by the cursor.
	Platforms	Windows NT and 2000
	Workaround	Enter your text changes in the text portion of the hex tab of Format Tester.
6	CR048606
	Problem	When the WebLogic Integration Studio is used on a UNIX system, spaces are displayed as special characters in application integration Plug-In View Definition dialog boxes for viewing schema definitions of event documents and service requests and responses.
	Platforms	UNIX platforms (Solaris and HP)
	Workaround	None
7	CR048918
	Problem	Login user names for the Worklist client are case-sensitive. Tasks assigned to a user may not be listed in a Worklist application if the user logs in to the application with a name spelled in a different case.
	Platforms	All
	Workaround	In the Worklist application, choose View—>Refresh.
8	CR049068
	Problem	If you shut down the B2B engine abnormally and subsequently try to use the Bulk Loader utility, you get an error message, indicating that the B2B engine is still running or was shut down abnormally.
	Platforms	All
	Workaround	Shut down the B2B engine from the WebLogic Integration B2B Console. Do not use Ctrl-C to shut down the B2B engine. For recommended ways to shut down the B2B engine, see Monitoring B2B Integration in Administering B2B Integration.
9	CR050074
	Problem	If your application startup class is called before the B2B engine startup, the application startup tries to access a noninitialized instance of the B2B engine, causing an error such as the following: ERROR: Collaboration Agreement CXMLsupplierConversation\|1.1\|cxml\|ACSNHub\|AN01000033621-T is not yet registered in runtime. This error occurs if the Server is not initialized properly or the Collaboration Agreement is not registered in runtime by the WebLogic Integration B2B Console.
	Platforms	All
	Workaround	If your application uses a startup class, you must deploy that class before deploying the B2B integration startup class.
10	CR050226
	Problem	Under the following conditions, WebLogic Integration can start the wrong workflow on receipt of a business message: The same endpoint URI is assigned for different business protocols or different versions of the same business protocol. The repository contains two collaboration agreements between the same trading partners. Those collaboration agreements define the same roles and parties, but are associated with different business protocols (or different versions of the same business protocol).
	Platforms	All
	Workaround	Assign different endpoint URIs for each business protocol (or for each version of a business protocol). For example, if one collaboration agreement references RosettaNet 1.1 and the other references RosettaNet 2.0 (through the trading partner delivery channels), you must assign one endpoint URI for RosettaNet 1.1 and another for RosettaNet 2.0.
11	CR050432
	Problem	In the Studio, run-time exceptions occur when variable names begin with numeric characters.
	Platforms	All
	Workaround	Begin variable names with alphabetic characters.
12	CR051059
	Problem	You cannot update the data for parties in a collaboration agreement in the WebLogic Integration B2B Console.
	Platforms	All
	Workaround	If you create a party for a collaboration agreement, and subsequently want to modify any of the attributes associated with it (such as trading partner name, party identifier, role name, or delivery channel), you must delete the party, and then create a new one with the desired attributes.
13	CR051469
	Problem	When you use a proxy server and do not set your system to bypass local addresses, you get the following error when running the Hello Partner sample: ERROR> The requested URL could not be retrieved
	Platforms	All
	Workaround	To bypass local addresses, change your Web browser configurations as follows: Internet Explorer: Choose Tools—>Internet Options —>Connections —>LAN Settings—> Bypass proxy server for local addresses. Netscape: Choose Edit—>Preferences—>Advanced—>Proxies—>View. Add your localhost to Exceptions.
14	CR052680
	Problem	Apache's ant command is not internationalized. The ant command is used to build application integration adapters. When an error occurs during the build process, the error text may not be displayed properly in Windows environments in which the natural language used in not English. For example, in a Japanese Windows environment you might see the following: [java] ...\jsp_servlet\_addevent.java:20: 'class' ?????? 'interface' ?????????????B
	Platforms	All
	Workaround	None
15	CR052994
	Problem	The WebLogic Integration software does not currently provide methods or properties for specifying use of the Japanese character set for sending messages and for the contentType of the mail header (for example, Content-Type: text/plain; charset="ISO-2022-JP").
	Platforms	All
	Workaround	Email adapter code is provided with WebLogic Integration. Japanese users are free to alter this code to allow for the specification of character sets. Keep in mind, however, that the sample email adapter does not support multibyte characters.
16	CR053242
	Problem	The WebLogic Integration Studio does not handle time zones correctly. For example, the client may send a local date/time string to the server, which then parses the string in its own time zone. This procedure creates ambiguities when the server and client are in different time zones. The following areas are affected: Any entity associated with a date value expressed as a string in which the time zone is implicit (for example, workload and statistics queries, and the effective and expiration dates for a template definition). Any date/time value that the client rounds up or down (for example, task reroutes and the effective and expiration dates for a template definition).
	Platforms	All
	Workaround	Use GMT for all time values when clients and server span multiple time zones.
17	CR055188
	Problem	Once an Oracle database account is used and a createDB operation is performed, if you invoke createDB again, you must drop the current username and password (using an Oracle script or Enterprise Manager) and then recreate the account. Otherwise, when attempting to bulk load data, the database returns an invalid operation error or an error similar to the following: <Aug 20, 2001 11:06:59 AM PDT> <Error> <WLC> <<BulkLoader> ERROR: WLC is still running or was shut down abnormally.> ERROR: WLC is still running or was shut down abnormally. <Aug 20, 2001 11:07:01 AM PDT> <Error> <WLC> <<BulkLoader> ERROR: WLC is still running or was shut down abnormally.> This problem most often occurs when you install a new version of WebLogic Integration but continue to use an existing Oracle database account. This error message is also displayed when you invoke createDB once but repeatedly bulk load data.
	Platforms	All
	Workaround	Ensure that the server is stopped. Use the Bulk Loader -force option. Caution: The Bulk Loader force option should not be used if the server is running.
18	CR055652
	Problem	The Application View connection values for initial and maximum cannot be the same number due to a limitation in WebLogic JCA.
	Platforms	All
	Workaround	None
19	CR055967
	Problem	If you log off from one server and log on to another, the following JMSException is thrown. The topic session for the notifier is not released during logoff. The server was unable to complete your request. JMSException: Connection not found Start server side stack trace: weblogic.jms.common.JMSException: Connection not found
	Platforms	All
	Workaround	None
20	CR057163
	Problem	Attempt to connect fails because of a license-related exception resulting from the absence, from the classpath, of the license.bea file. The pathname may be too long for the system to read it. (It is possible that after repeated executions of the setenv program, BEA_HOME (D:\bea\), the directory in which the license.bea file resides, is no longer included in the classpath.)
	Platforms	Windows (on Intel)
	Workaround	Open a new DOS prompt window and try again.
21	CR057562
	Problem	The names of the roles used in the PIP3A2 template have been changed from Buyer and Seller to Customer and Product Supplier.
	Platforms	All
	Workaround	If you have private workflows that call the 3A2 private workflows (in a pre-SP1 release of WebLogic Integration), you must update the roles in your private workflows.
22	CR057771
	Problem	The documentation that explains how to define workflow templates in the Studio does not warn you that unless you state that a variable is of type input, that variable is not assigned when you instantiate a workflow from the API.
	Platforms	All
	Workaround	None.
23	CR058127, CR058732
	Problem	When the RosettaNet 2.0 protocol is used, the name of a trading partner may not include Chinese or Japanese characters. A trading partner with such a name cannot exchange business messages.
	Platforms	All.
	Workaround	None.
24	CR058307
	Problem	The shutdown of a spoke which might have initiated conversations blocks if WebLogic Server is shutting down at the same time.
	Platforms	All
	Workaround	Always explicitly shut down the B2B engine independently of WebLogic Server using the WebLogic Integration B2B Console. If business process management functions are running, shut down the process engine first using WebLogic Integration Studio. Next shut down the B2B engine, using the WebLogic Integration B2B Console. If shutdown of the B2B engine is invoked with the TERMINATE mode, an underlying WebLogic Server, listening for incoming requests, is required.
25	CR058949
	Problem	The Format Builder is unable to open palettes other than the default palette.mfl file.
	Platforms	All
	Workaround	Close the Format Builder and rename the file required to be displayed in the palette to palette.mfl, then restart the Format Builder.
26	CR059332 CR058852
	Problem	Problems have occurred when running WebLogic Integration samples on Windows 2000 Advanced Server systems over an MSSQL 2000 database.
	Platforms	Windows 2000 Advanced Server / MSSQL 2000
	Workaround	The row-locking mechanism has changed between the Microsoft SQL 7.0 and 2000 databases. A solution is in progress and will be available in a future release.
27	CR059475
	Problem	Application integration plug-ins do not detect the status of a wlai-ejb-server when the server is down at design time. A message similar to the following is displayed: The server was unable to complete your request. Unknown error: NameNotFoundException: Unable to resolve com.bea.wlpi.Admin. Resolved: 'com.bea.wlpi' Unresolved:'Admin'
	Platforms	All
	Workaround	None
28	CR059746, CR062984
	Problem	The introduction of milliseconds as a unit of time broke backward compatibility for timed-triggered workflows and for TimedEvent Actions.
	Platforms	All
	Workaround	If you have created workflows with an earlier release of WebLogic Integration (or any release of BEA WebLogic Process Integrator), then you must manually reset the correct time units in the Start nodes (for timed-triggered workflows) and in all TimedEvent Actions.
29	CR060313
	Problem	You cannot uninstall Power.Enterprise! Server or Client software if you try to do so from the Windows NT (or Windows 2000) Add/Remove Programs dialog box. The uninstall program looks for the jre in the directory from which the Power.Enterprise! software was initially installed.
	Platforms	Windows
	Workaround	Select the Uninstall item from the PowerIt program group on the Start menu. At the end of the uninstall procedure, you may need to remove the installation directory manually.
30	CR060335
	Problem	WebLogic Integration fails to create an extended property for a trading partner on UNIX systems. An exception similar to the following is displayed: <Oct 16, 2001 7:11:50 PM GMT-08:00> <Error> <B2B> <<Repository> ERROR: In SQLExecutor.doUpdate, a SQL Exception was caught while executing a SQL Statement: java.sql.SQLException: ORA-01400: cannot insert NULL into ("BOB"."XML_NODE"."NAME")
	Platforms	UNIX
	Workaround	Manually edit the exported XML file to add the extended property. For example, to add an extended property for the trading partner named TPSpoke: From the WebLogic Integration B2B Console, choose B2B—>Config—>Export. Select trading partner TPSpoke for export without exporting all referenced entities. Edit the exported XML file to add the extended property. Shut down the B2B engine from the WebLogic Integration B2B Console. Import the modified XML file. Restart the B2B engine.
31	CR060401
	Problem	Creating a B2B entity using the WebLogic Integration B2B Console sometimes takes several minutes and results in an exception similar to the following: <Oct 17, 2001 10:58:08 AM PDT> <Error> <B2B> <<Repository> ERROR: Error getting a Connection from the DataSource "WLCHub.DS" in Repository Session - SQLException: WLCHub.DS>
	Platforms	All.
	Workaround	Edit config.xml to increase the default MaxCapacity setting for the JDBCConnectionPool from 36 to 80.
32	CR062137
	Problem	Task and workflow comments are being truncated. Note: Workflow and task comments are limited to a maximum of 254 characters. Comments exceeding this limit are truncated and no exception is thrown.
	Platforms	All
	Workaround	Do not include more than 254 characters in your task and workflow comments.
33	CR062442
	Problem	When the fromDUNS is set to a value in the customer's private workflow, and that value is not declared as a business ID of the party identifier in the repository, the customer's public workflow throws a null pointer exception.
	Platforms	All
	Workaround	None
34	CR062634
	Problem	The SendXMLToClient dialog box returns text that does not match the text you selected in that box. For example, if you select OK, the word yes is displayed in the XML reply (instead of OK).
	Platforms	All
	Workaround	None
35	CR062846
	Problem	While trying to start WebLogic Server, the RunSamples script (in $BEA_HOME/wlintegration2.1/samples/bin) gives a syntax error about an unexpected elif. This problem is caused by a script called usejdbc2 written in Korn shell syntax.
	Platform	Solaris with DB2
	Workaround	Replace the Korn shell syntax in the usejdbc2 script (in $DB2_HOME/java12) with Bourne shell syntax: Replace if [[ ... ]]then with if [ ... ]; then. Replace elif [[ ... ]] then with elif [ ... ]; then. Run setenv.sh. Run the RunSamples script again.
36	CR062855
	Problem	An event that follows a Start node immediately is not activated unless the flow enters a quiescent state before reaching that event.
	Platforms	All
	Workaround	Place a timed event before the Event node.
37	CR063114, CR066059
	Problem	Format Builder stops responding after saving an MFL document. Format Builder uses an XSL style sheet to create DTD and XML Schema from the MFL documents after it is saved. Certain field combinations within an MFL document cause the Xalan to hang when a DTD or XML Schema document is being created.When this problem occurs you must terminate the Format Builder process. Do not hesitate to do so; you will not lose your MFL document. A DTD and or Schema will not be created, however. The default output setting of Format Builder automatically creates a DTD on save.
	Platforms	All
	Workaround	To turn off automatic DTD and XML Schema creation, make sure the check boxes in the Tools / Options . . . dialog box are not selected.
38	CR063709
	Problem	The RosettaNet Security Sample throws an exception when a single database is used for two peers and the database tables for peer1 are overwritten by peer2. (When peer1 is booted, it cannot add the certificate and key for the appropriate users. Because the database tables have been overwritten, the system boot cannot even pick the correct certificate names for which to search in the startup script.)
	Platforms	All
	Workaround	If possible, use different databases for different peers. For example, have peer1 use MSSQL and peer2, Oracle. If you must run two peers on one machine and both peers use the same database server, make sure that: With MSSQL—A different database name is used for each peer, such as WLIDB for peer1 and WLIDB2 for peer2. With Oracle—A different Oracle user account is used for each peer, such as kevin/kevin for peer1 and nina/nina for peer2. Specify every database you use for this sample on the RunRN2Security command line, as follows: RunRN2Security database_for_peer1 database_for_peer2 setDBVars and setDBVarsExt for the two peers are set appropriately for two databases and users, as follows: /bea/wlintegration2.1/config/samples/RN2Security/config/ peer1/dbInfo/database /bea/wlintegration2.1/config/samples/RN2Security/config/ peer2/dbInfo/database
39	CR064277
	Problem	Exporting a workflow that contains a task that uses the invoke workflow exception handler action will cause a SAX parser error and may cause the workflow to become corrupted, losing variables, nodes, and exception handlers defined.
	Platforms	All
	Workaround	Avoid using the invoke exception handler case.
40	CR064443
	Problem	The first window displayed by both the full uninstaller and the service pack upgrade uninstaller contains the following message: "This will completely remove all components installed by InstallAnywhere. It will not remove files and folders created after the installation."
	Platforms	All
	Workaround	This message is imprecise. It should say, instead, that the uninstall process will remove the upgrade and return the software to its pre-upgrade state.
41	CR064564
	Problem	The organization view in the WebLogic Integration Worklist is not updated when you add a new organization through the following procedure: Log in to the Studio and the Worklist with the same user account (such as joe). In the Studio, add an organization. Select the new organization from the Organization drop-down list. Add yourself (joe) as a user to the new organization. In the Worklist, look for the new organization in the drop-down list. The problem is that the new organization is not listed. Even if you refresh the Worklist (by choosing View—>Refresh), the organization is still not listed.
	Platforms	All
	Workaround	Log off from the Worklist and then log on again.
42	CR064686
	Problem	The calendar feature is broken.
	Platforms	All
	Workaround	The timezone of the calendar must match the timezone of the machine on which the server is running. Make sure you use the correct timezone.
43	CR064716
	Problem	The WebLogic Integration source code checks the PRODUCTNAME column of the master.dbo.spt_mda table, and it relies on finding the following string: Sybase SQL Server. If, instead of this string, the source code finds a variable, @@version, which is set to Adaptive Server Enterprise, then users get the following com.sybase.jdbc.SybSQLException: SET CHAINED command not allowed within multi-statement transaction.
	Platforms	Sybase 11.9.2
	Workaround	jConnect implements the JDBC method getDatabaseProductName by calling the sp_mda stored procedure that is set up by the installjconnect script. This script populates the master..spt_mda table with information to be returned by metadata access methods. If the PRODUCTNAME column of the master.dbo.spt_mda table contains the @@version variable, then you must change the variable to Sybase SQL Server by running the following SQL statements: update master.dbo.spt_mda set query = 'Sybase SQL Server' where mdinfo = `PRODUCTNAME' querytype = 6 update master.dbo.spt_mad set query = 'select ''Sybase SQL Server''' where mdinfo = `PRODUCTNAME' querytype = 2
44	CR065136
	Problem	The upgrade installer does not provide an option migrating the Cloudscape database.
	Platforms	All
	Workaround	None required. Cloudscape is not supported for production environments.
45	CR065220
	Problem	When you use two XSLTs in two different tasks in a workflow, the XML event starts the workflow. The XML file that starts the workflow is the input XML for the first XSLTransform in Task1. The output of the first XSLT is input for the second XSLTransform in another Task2. The user tried sending the XML files to the BPM process to start the workflow. Only one particular XML file is causing the problem.
	Platforms	All.
	Workaround	Install the following patch file for WebLogic Server 6.1 SP1: CR065345_610sp2.jar. To obtain this patch, contact BEA Customer Support.
46	CR065392
	Problem	An exception is thrown when a large (over 20 MB) binary file is received from WebLogic Integration - Business Connect.
	Platforms	All
	Workaround	Use the following tuning parameters: StartWebLogic: Increase the heap size to 512MB. Database: Make the database large (up to 300MB). Increase the Transaction Log space (or rollback segment) to 100MB. Turn off the database shrinking. WebLogic Integration [formerly WLPI] EJBs: Edit the deployment descriptors of wlpi-ejb.jar and wlpi-ejb-mdb.jar. Edit ejb-jar.xml from wlpi-ejb-mdb.jar. Look for all 90-second transaction timeouts and raise each one to 1090. Edit weblogic-ejb-jar.xml from the wlpi-ejb.jar file and raise all 90-second timeouts to 1090.
47	CR065397
	Problem	When I go to the party tab for a particular collaboration agreement and select Enable and Register this Collaboration Agreement, the b2b.log file seems to indicate that the enable-and-register operation is successful, but the B2B Console continues to wait for the operation to finish.
	Platforms	Windows (Intel)
	Workaround	Execute the same operation (that is, enable and register the specified collaboration agreement) from the monitoring tab, instead.
48	CR065456
	Problem	There is no ebXML plug-in online help from the Studio help menu.
	Platforms	All
	Workaround	None
49	CR065631	On a WinNT or Win2000 machine, the installation fails at the Choose Install Set window if you are using a version of the JDK that is earlier than 1.3.x. Note: The JDK 1.3.1 is shipped with WebLogic Server 6.1, so you should have it installed on your system.
	Problem	If the user has not installed the JDK on a new Windows NT or Windows 2000 system, then the installer fails when the Choose Install Set window is displayed, instead of proceeding to give the user the option of selecting or creating a directory to serve as BEA_HOME.
	Platforms	Windows 2000 and Windows NT
	Workaround	Install the JDK 1.3.1 on the target machine and start the installation again.
50	CR065852
	Problem	If you run RunSamples.cmd more than once, an exception may be generated and captured in the config\samples\logs\samples.log file. (The problem does not occur the first time you run RunSamples.cmd.)
	Platforms
	Workaround	This exception is benign; you can ignore it.
51	CR065878
	Problem	The B2B plug-in to the WebLogic Integration Studio does not set Sender Name correctly with XOCP SSL.
	Platforms	All
	Workaround	Change the workflow so it does not send the message to the sender name.
52	CR066179
	Problem	Using ebXML messaging may hang the server with high load and low ThreadCount settings.
	Platforms	All
	Workaround	Increase the server threadcount to approximately half the number of concurrent users expected.

Limits on Length of Database Character Strings
Entity	Oracle	MSSQL	Cloudscape	Sybase	DB2
TradingPartner	256	256	256	255	254
DeliveryChannel	252	128	256	128	254

Error initializing plugin:
com.bea.wlpi.tour.po.plugin.SamplePluginBeanHomeImpl@175d46
java.rmi.RemoteException: Exception in ejbCreate(); nested
exception is: java.lang.InternalError: Can't connect to x11 window
server using " as the value of the DISPLAY variable.
java.lang.InternalError: Can't connect to X11 window server using
" as the value of the DISPLAY variable.

Version	Patch ID	Note	See Footnotes	Description
2.6 (5.6)	107733-06	Required	—	Linker Patch
2.6 (5.6)	105568-17	Required	—	Libthread Patch
2.6 (5.6)	105210-27	Required	—	LibC Patch
2.6 (5.6)	106040-13	Required	—	X Input & Output Method Patch
2.6 (5.6)	105633-38	Required	1, 4, 5	OpenWindows 3.6: Xsun Patch
2.6 (5.6)	106409-01	Required	2	Fixes the Chinese TrueType fonts
2.6 (5.6)	108091-03	Required	3	SunOS 5.6: fatal error in ISO8859-01 Locales
2.6 (5.6)	106842-09	Required	4	Euro currency support
2.6 (5.6)	106841-01	Required	4	Keytables Patch
2.6 (5.6)	105181-20	Required	—	Kernel Update (socket close/hang)
2.6 (5.6)	105669-10	Recommended	—	CDE 1.2: libDTSvc Patch (dtmail)
2.6 (5.6)	105284-33	Recommended	—	Motif 1.2.7: Run-time library patch
2.6 (5.6)	105591-09	Required	—	C++ shared library patch
2.6 (5.6)	106125-09	Required	—	Patch for patchadd and patchrm
7 (5.7)	106980-10	Required	—	Libthread Patch
7 (5.7)	107636-03	Required	—	X Input & Output Method Patch
7 (5.7)	108376-07	Required	1,5	OpenWindows 3.6.1 Xsun Patch
7 (5.7)	107153-01	Required	1	Replaces bad font in zh.GBK locale
7 (5.7)	106541-11	Required	—	Kernel update
7 (5.7)	107544-03	Required	—	To be used with Kernel update patch
7 (5.7)	109104-01	Required	—	To be used with Kernel update patch
7 (5.7)	106950-09	Required	—	Linker Patch
7 (5.7)	106327-08	Required	—	Shared library patch for C++
7 (5.7)	106300-09	Required	—	Patch for C++
7 (5.7)	107081-20	Required	—	Motif 1.2 and Motif 2.1 patch
8 (5.8)	108940-07	Required	—	Motif 2.1 patch available soon from SunSolve

Version

Patch ID

Note

See Footnotes

Description

2.6 (5.6)

107733-06

Required

—

Linker Patch

2.6 (5.6)

105568-17

Required

—

Libthread Patch

2.6 (5.6)

105210-27

Required

—

LibC Patch

2.6 (5.6)

106040-13

Required

—

X Input & Output Method Patch

2.6 (5.6)

105633-38

Required

1, 4, 5

OpenWindows 3.6: Xsun Patch

2.6 (5.6)

106409-01

Required

Fixes the Chinese TrueType fonts

2.6 (5.6)

108091-03

Required

SunOS 5.6: fatal error in ISO8859-01 Locales

2.6 (5.6)

106842-09

Required

Euro currency support

2.6 (5.6)

106841-01

Required

Keytables Patch

2.6 (5.6)

105181-20

Required

—

Kernel Update (socket close/hang)

2.6 (5.6)

105669-10

Recommended

—

CDE 1.2: libDTSvc Patch (dtmail)

2.6 (5.6)

105284-33

Recommended

—

Motif 1.2.7: Run-time library patch

2.6 (5.6)

105591-09

Required

—

C++ shared library patch

2.6 (5.6)

106125-09

Required

—

Patch for patchadd and patchrm

7 (5.7)

106980-10

Required

—

Libthread Patch

7 (5.7)

107636-03

Required

—

X Input & Output Method Patch

7 (5.7)

108376-07

Required

1,5

OpenWindows 3.6.1 Xsun Patch

7 (5.7)

107153-01

Required

Replaces bad font in zh.GBK locale

7 (5.7)

106541-11

Required

—

Kernel update

7 (5.7)

107544-03

Required

—

To be used with Kernel update patch

7 (5.7)

109104-01

Required

—

To be used with Kernel update patch

7 (5.7)

106950-09

Required

—

Linker Patch

7 (5.7)

106327-08

Required

—

Shared library patch for C++

7 (5.7)

106300-09

Required

—

Patch for C++

7 (5.7)

107081-20

Required

—

Motif 1.2 and Motif 2.1 patch

8 (5.8)

108940-07

Required

—

Motif 2.1 patch available soon from SunSolve

Microsoft Windows NT 4.0 with Service Pack 6 or later Microsoft Windows 2000 Professional Microsoft Windows 2000 Advanced
WebLogic Server Platform	BEA WebLogic Server 6.1 with Service Pack 1 or higher Note: If you plan to use ebXML functionality, which is available with WebLogic Integration 2.1 SP1, then you must install WebLogic Server 6.1 SP2.
JDK	JDK 1.3.1 is provided automatically with WebLogic Server; you do not need to install a Java 2 SDK separately.
Hardware and Software Requirements	Intel Pentium II processor or later 400 MHz recommended 100 MB free disk space Network connection 256-MB RAM minimum (512 MB recommended) Note: The 256-MB RAM recommendation is valid for one instance of WebLogic Server on which WebLogic Integration 2.1 SP1 is running. You may need more memory if you run two instances of WebLogic Server.
Databases	One of the following: Cloudscape 3.5.1 (for development only), Oracle 8.1.6, Oracle 8.1.7, Microsoft SQL Server 7.0 (Service Pack 3) or 2000, or Sybase System 11.9.2. (See Database Support.)
Sun Solaris 7 (formerly referred to as 2.7) Sun Solaris 8 (formerly referred to as 2.8)
WebLogic Server Platform	BEA WebLogic Server 6.1 with Service Pack 1 or higher Note: If you plan to use ebXML functionality, which is available with WebLogic Integration 2.1 SP1, then you must install WebLogic Server 6.1 SP2.
JDK	JDK 1.3.1 is provided automatically with WebLogic Server; you do not need to install a Java 2 SDK separately. The Solaris operating system patches for Java 2 JDK, including the Solaris OpenWindows Motif patches, are required if you install the software using the GUI-based installation procedure. The patches are available at the following URL: http://java.sun.com/j2se/1.3/install-solaris-patches.html
Hardware and Software Requirements	UltraSparc 5 or later Sparc 168 MHz or faster 100 MB free disk space Network connection 256-MB RAM minimum (512 MB recommended) Note: The 256-MB RAM recommendation is valid for one instance of WebLogic Server on which WebLogic Integration 2.1 SP1 is running. You may need more memory if you run two instances of WebLogic Server.
Databases	One of the following: Oracle 8.1.6, Oracle 8.1.7, Microsoft SQL Server 7.0 or 2000 using jDriver, Sybase System 11.9.2, or DB2 UDB 7.2 (See Database Support.)
Hewlett-Packard HP-UX 11.0
WebLogic Server Platform	BEA WebLogic Server 6.1 with Service Pack 1 or higher Note: If you plan to use ebXML functionality, which is available with WebLogic Integration 2.1 SP1, then you must install WebLogic Server 6.1 SP2.
JDK	JDK 1.3.1 is provided automatically with WebLogic Server; you do not need to install a Java 2 SDK separately.
Hardware and Software Requirements	HP 9000 PA RISC 100 MHz or higher 100 MB free disk space Network connection 256-MB RAM minimum (512 MB recommended) Note: The 256-MB RAM recommendation is valid for one instance of WebLogic Server on which WebLogic Integration 2.1 SP1 is running. You may need more memory if you run two instances of WebLogic Server. For information about platform-specific configuration settings, see Settings Required for Running WebLogic Integration on HP-UX 11.0.
Databases	One of the following databases: Oracle 8.1.6, Oracle 8.1.7, Microsoft SQL Server 7.0, Microsoft SQL Server 2000, or Sybase Server 11.9.2. (See Database Support.)
IBM AIX 4.3.3 IBM AIX 5.1 with maintenance level 1
WebLogic Server Platform	BEA WebLogic Server 6.1 with Service Pack 1 or higher Note: If you plan to use ebXML functionality, which is available with WebLogic Integration 2.1 SP1, then you must install WebLogic Server 6.1 SP2.
JDK	JDK 1.3.1 is provided automatically with WebLogic Server; you do not need to install a Java 2 SDK separately.
Hardware and Software Requirements	RS/6000 PowerPC-604 or higher 200 MHz or faster 280 MB free disk space 256-MB RAM minimum (512 MB recommended) Network connection
Databases	One of the following databases: Oracle 8.1.7 or DB2 UDB 7.2 (See Database Support.)
Red Hat Linux 7.2
WebLogic Server Platform	BEA WebLogic Server 6.1 with Service Pack 1 or higher Note: If you plan to use ebXML functionality, which is available with WebLogic Integration 2.1 SP1, then you must install WebLogic Server 6.1 SP2.
JDK	The JDK required for use with Red Hat Linux is not provided with WebLogic Server. Download and install Sun Microsystems JDK 1.3.1_01 separately before installing WebLogic Server. After installing the JDK, specify JAVA_HOME as described in Specifying JAVA_HOME for Red Hat Linux.
Hardware and Software Requirements	Intel Pentium II processor or higher 400 MHz or faster 100 MB free disk space 256-MB RAM minimum (512 MB recommended) Network connection
Databases	Oracle 8.1.7 (See Database Support.)

Java	1.3.0
AIX	version 4.3.3
LPP Name	Java_dev2
Installation directory	/usr/java_dev2
Latest update	PTF 7 IY12075 (ca130-20001124)

PHCO_19666	PHKL_22589	PHSS_21959
PHCO_22314	PHSS_17535	PHNE_22086
PHCO_22314	PHSS_17535	PHNE_22086
PHKL_18543	PHSS_21982	PHSS_20863
PHKL_20016	PHSS_22341


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

WebLogic Integration Doc Home \| Release Notes \| Previous Topic \| Next Topic \| Contents \| View as PDF