BEA WebLogic Integration Release Notes

Date	Summary of Changes
January 31, 2002	Added support for Linux for S/390 and zSeries and DB2. For details, see Platform Support and Hardware and Software Requirements. For installation instructions, see Installing WebLogic Integration on AIX or Linux for S/390 and zSeries.
December 7, 2001	Added support for AIX and DB2. For details, see Platform Support and Hardware and Software Requirements. For installation instructions, see Installing WebLogic Integration on AIX or Linux for S/390 and zSeries.
November 30, 2001	Revised "Deploying EJBs and Java Classes for Business Operations" in Chapter 3, "Customizing WebLogic Integration," in Starting, Stopping, and Customizing BEA WebLogic Integration. The revised chapter includes information on how to deploy an EJB by manually editing the config.xml file based on CR061478, CR061980 and CR062010. The revised document can be found at the following URL: http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/config/custom.htm Revised Migrating to BEA WebLogic Integration Release 2.1 to include additional migration information (instructions on running the migration tool on UNIX systems, information on running migration scripts, and information concerning environment requirements for migration) based on CR061583, CR061557, and CR061589. The revised document can be found at the following URL: http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/migrate/index.htm Revised Chapter 4, "Tuning Performance," in Deploying BEA WebLogic Integration Solutions to include additional information on tuning the performance of your WebLogic Integration deployment. The updated chapter can be found at the following URL: http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/deploy/tune.htm
November 2, 2001	Updated the description of the EDI sample contained in Using EDI with WebLogic Integration to make the map name and service name consistent throughout the procedure, as described in CR060957 and CR060961. The updated sample can be found at the following URL: http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/edi/sample.htm Added Appendix B, "WebLogic Integration Commands," to Starting, Stopping, and Customizing BEA WebLogic Integration. This appendix provides developers and system administrators with a reference for key WebLogic Integration commands, and can be found at the following URL: http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/config/keycmd.htm
October 2001	Initial Release

Date

Summary of Changes

January 31, 2002

Added support for Linux for S/390 and zSeries and DB2. For details, see Platform Support and Hardware and Software Requirements. For installation instructions, see Installing WebLogic Integration on AIX or Linux for S/390 and zSeries.

December 7, 2001

Added support for AIX and DB2. For details, see Platform Support and Hardware and Software Requirements. For installation instructions, see Installing WebLogic Integration on AIX or Linux for S/390 and zSeries.

November 30, 2001

Revised "Deploying EJBs and Java Classes for Business Operations" in Chapter 3, "Customizing WebLogic Integration," in Starting, Stopping, and Customizing BEA WebLogic Integration. The revised chapter includes information on how to deploy an EJB by manually editing the config.xml file based on CR061478, CR061980 and CR062010. The revised document can be found at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/config/custom.htm
Revised Migrating to BEA WebLogic Integration Release 2.1 to include additional migration information (instructions on running the migration tool on UNIX systems, information on running migration scripts, and information concerning environment requirements for migration) based on CR061583, CR061557, and CR061589. The revised document can be found at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/migrate/index.htm
Revised Chapter 4, "Tuning Performance," in Deploying BEA WebLogic Integration Solutions to include additional information on tuning the performance of your WebLogic Integration deployment. The updated chapter can be found at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/deploy/tune.htm

November 2, 2001

Updated the description of the EDI sample contained in Using EDI with WebLogic Integration to make the map name and service name consistent throughout the procedure, as described in CR060957 and CR060961. The updated sample can be found at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/edi/sample.htm
Added Appendix B, "WebLogic Integration Commands," to Starting, Stopping, and Customizing BEA WebLogic Integration. This appendix provides developers and system administrators with a reference for key WebLogic Integration commands, and can be found at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/config/keycmd.htm

October 2001

Initial Release

Platform	Version	Database
Microsoft Windows NT	4.0 with Service Pack 6	Oracle 8.1.6 Oracle 8.1.7 Cloudscape 3.5.1 SQL Server 7 SP3 SQL Server 2000 Sybase System 11.9.2
Microsoft Windows 2000	Professional Advanced	Oracle 8.1.6 Oracle 8.1.7 Cloudscape 3.5.1 SQL Server 7 SP3 SQL Server 2000 Sybase System 11.9.2
Sun Solaris	7 (formerly referred to as 2.7) 8 (formerly referred to as 2.8)	Oracle 8.1.6 Oracle 8.1.7 SQL Server 7 SP3 SQL Server 2000 Sybase System 11.9.2
Hewlett-Packard HP-UX	11.0	Oracle 8.1.6 Oracle 8.1.7 SQL Server 7 SP3 SQL Server 2000 Sybase System 11.9.2
IBM AIX	4.3.3 with Performance Pack	DB2 V7.2
Linux for S/390 and zSeries	SuSE Linux Enterprise Server 7 for S/390 and zSeries	DB2 V7.2

Platform

Version

Database

Microsoft Windows NT

4.0 with Service Pack 6

Oracle 8.1.6
Oracle 8.1.7
Cloudscape 3.5.1
SQL Server 7 SP3
SQL Server 2000
Sybase System 11.9.2

Microsoft Windows 2000

Professional

Advanced

Oracle 8.1.6
Oracle 8.1.7
Cloudscape 3.5.1
SQL Server 7 SP3
SQL Server 2000
Sybase System 11.9.2

Sun Solaris

7 (formerly referred to as 2.7)

8 (formerly referred to as 2.8)

Oracle 8.1.6
Oracle 8.1.7
SQL Server 7 SP3
SQL Server 2000
Sybase System 11.9.2

Hewlett-Packard HP-UX

11.0

Oracle 8.1.6
Oracle 8.1.7
SQL Server 7 SP3
SQL Server 2000
Sybase System 11.9.2

IBM AIX

4.3.3 with Performance Pack

DB2 V7.2

Linux for S/390 and zSeries

SuSE Linux Enterprise Server 7 for S/390 and zSeries

DB2 V7.2

This section describes known limitations in WebLogic Integration, and recommended workarounds for them.

1	CR033753
	Problem	When using the WebLogic Integration Studio for instance monitoring, only tasks are highlighted in the graphical representation of the workflow status.
	Platform	All
	Workaround	None
2	CR036730
	Problem	When using the WebLogic Integration Studio, OR joins can be triggered only once, and they cannot be inserted in loops.
	Platform	All
	Workaround	None
3	CR037903
	Problem	When updating a user's properties in the WebLogic Integration Studio, you cannot modify the user's password.
	Platform	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.
4	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.
	Platform	All
	Workaround	None, however we recommend selecting a user name other than system.
5	CR045361
	Problem	For Cloudscape, Microsoft SQL Server, Sybase, and DB2, the DBMS adapter triggers support only insert, update, or delete operations that affect a single row. There is no known workaround other than altering the code. The source code is provided in case you need to alter the code to get around this limitation.
	Platform	All
	Workaround	None
6	CR047116
	Problem	If a JAR for an adapter is not included in the WebLogic Integration classpath, the adapter developer gets ClassNotFound exceptions when trying to test an event or service from a Web application.
	Platforms	All
	Workaround	Include the required adapter classes in the WebLogic Integration classpath. We recommend adding JAR files to the end of the CMNCP environment variable in the SetdomainData.cmd/sh file for your domain. For example, for the wlidomain, there is a file called SetWlidomainData.cmd/sh. Adapter developers must include their JAR files in the WebLogic Integration classpath, even if they include those JAR files in the EAR file for the adapter.
7	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.
8	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. This problem occurs when you perform the following steps: Create a new format with three NULL-terminated string fields. Open the tester and click the text tab of the binary window. Right-click in this window and select generate. You will see three fields, separated by nonprintable block characters. Place the cursor before the N in the third field and start typing any string of characters. The characters you type are displayed a few characters after the N (rather than before the N).
	Platform	Windows NT and 2000
	Workaround	None. This bug was introduced in the JTextArea swing control with Java2 v1.3, and it is registered as Sun Bug ID 4398837.
9	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 view schema definitions of event documents and service requests and responses.
	Platform	UNIX platforms (Solaris and HP)
	Workaround	None
10	CR048620
	Problem	When you log in to the WebLogic Integration Studio on an AIX system, the left pane of the Studio window is blank.
	Platform	AIX platforms
	Workaround	From the menu bar in the Studio, choose View—>Look and feel—>Metal, then View—>Look and feel—>CDE/Motif. The contents of the left pane should then be displayed normally.
11	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.
	Platform	All
	Workaround	In the Worklist application, choose View—>Refresh.
12	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.
13	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.
14	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.
15	CR050432
	Problem	In the Studio, run-time exceptions occur when variable names begin with numeric characters.
	Platform	All
	Workaround	Begin variable names with alphabetic characters.
16	CR051037
	Problem	The bulkloader command cannot be run with the initialize option.
	Platforms	All
	Workaround	Run the createDB command to recreate the database schema.
17	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.
18	CR051410
	Problem	Addressed message reapers can deadlock each other if sufficient connections are not defined in the connection pool. In the case of a deadlock, a message similar to the following is displayed: Notice> <WebLogicServer> <Started WebLogic Admin Server "myserver" for domain "bpmdomain" running in Production Mode> java.sql.SQLException: Your transaction (process ID #8) was deadlocked with another process and has been chosen as the deadlock victim. Rerun your transaction.
	Platform	All
	Workaround	Increment the number of connections defined in the connection pool.
19	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.
20	CR052479
	Problem	The Start node properties dialog box in the Studio is not resized properly when a workflow triggering method is being selected. As a result, only part of the dialog box is displayed.
	Platforms	AIX platforms
	Workaround	Select the option for the desired triggering method two or more times. The complete dialog box should be displayed.
21	CR052680
	Problem	When an error occurs after the command ant.cmd is issued, the system attempts to display an error message in a Japanese Windows environment, but Japanese characters are not displayed correctly. For example: [java] ...\jsp_servlet\_addevent.java:20: 'class' ?????? 'interface' ?????????????B This is a limitation of Ant and requires a fix from Apache.
	Platform	All
	Workaround	None
22	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").
	Platform	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.
23	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. Rounding the date and time to the nearest day is intrinsically unsound if the system encompasses multiple time zones, because the date component depends on the time zone in which the rounding is performed. Different time zones can yield different rounded dates. 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).
	Platform	All
	Workaround	Formatted time values should always be expressed in GMT when sent over a network or stored in the database. Time values should always be displayed in local time. Calendar control must include the time.
24	CR054120
	Problem	In the WebLogic Integration DBMS Adapter, update events do not properly fill in New elements; only Old elements are filled in. This is because the update trigger includes only the column data that has actually changed. The schema should indicate that all old fields are minOccurs=1 (required) and all new fields are minOccurs=0 (optional). The DbmsEventGeneratorWorker should add only elements that actually exist in the EVENT_DATA table (elements that were updated).
	Platform	All
	Workaround	Alter the code in com.bea.adapter.dbms.utils.triggers.* to fix this problem as required.
25	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.
26	CR055321
	Problem	The lightweight client API throws a null pointer exception. When a mailbox is created, if the isExistMailbox() method is not called, any attempt to add a message throws a null pointer exception.
	Platform	All
	Workaround	None
27	CR055652
	Problem	The Application View connection values for initial and maximum cannot be the same number due to a limitation in WebLogic JCA.
	Platform	All
	Workaround	None
28	CR055751
	Problem	If the wlcsystem user is assigned different passwords in the config file and the repository, for example, if the passwords are password and wlcsystem respectively, then the system displays a warning, switches the user to the wlcsystem password, and continues operation.
	Platforms	All
	Workaround	None
29	CR055832
	Problem	The com.bea.wlpi.admin.Admin.getTemplate() Javadoc needs to be corrected and/or enhanced as follows: The includeContent and parsePluginData parameters should be removed from the list of valid parameters. The description needs to explain that if a template does not exist, then a WorkflowException is thrown. In addition, the entire BPM Javadoc set needs to better distinguish between the templateID and templateDefinitionID parameters.
	Platform	All
	Workaround	None
30	CR055967
	Problem	If you log off from one server and log on to another, the following JMSException is thrown. It appears that 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
	Platform	All
	Workaround	None
31	CR056602
	Problem	If an MFL document is created in the data integration Format Builder with either an MFL or Field Codepage of Shift_JIS, the Format Tester's translate functionality fails.
	Platform	All
	Workaround	If possible, use MS_Kanji or EUC_JP in place of Shift_JIS.
32	CR057621
	Problem	When data is being exported from the WebLogic Integration B2B Console, an SQL exception similar to the following may be thrown: <Notice> <WebLogicServer> <Started WebLogic Admin Server "myserver" for domain "mydomain" running in Development Mode> <Sep 21, 2001 6:40:09 PM PDT> <Error> <B2B> <<Repository> ERROR: In SQLExecutor. executeQueryWithSQLCreator, a SQL Exception was caught while executing a SQL Statement: java.sql.SQLException: Protocol violation>
	Platform	All
	Workaround	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.
33	CR057715
	Problem	The BPM plug-in framework requires the X server on UNIX platforms in order to display GUI panels.
	Platform	UNIX
	Workaround	None
34	CR058127
	Problem	Japanese characters contained in RosettaNet 2.0-based business messages received by a trading partner are corrupted.
	Platform	All.
	Workaround	None.
35	CR058307
	Problem	The shutdown of a spoke which might have initiated conversations blocks if WebLogic Server is shutting down at the same time.
	Platform	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.
36	CR058732
	Problem	In the RosettaNet 2.0 protocol, a trading partner name cannot be specified as a string containing Chinese characters. A trading partner with such a name cannot exchange business messages.
	Platform	All.
	Workaround	None.
37	CR058834
	Problem	The Test hyperlink for a service on the application view summary page for application views with Japanese names containing complex characters generates a java.lang.NullPointerException exception. This prevents you from testing the service from the design-time Web application. Note that the service can still be used from the business process management (BPM) component.
	Platform	All.
	Workaround	None.
38	CR058949
	Problem	The Format Builder is unable to open palettes other than the default palette.mfl file.
	Platform	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.
39	CR059191
	Problem	Several system tests result in a time out exception when they are run over a period of time. A message similar to the following is displayed: <B2B-BPM-Plugin> ERROR: Cannot get variable for workflow instance 3098 > weblogic.transaction.internal.TimedOutException: Transaction timed out after 93 seconds
	Platform	All
	Workaround	None
40	CR059193
	Problem	There is a known issue with Microsoft SQL Server 7.0 whereby it loses the default value setting of database columns while copying (exporting/importing) a database. This issue causes the associated WebLogic Integration server, which relies on these default value settings, to fail. A typical error message is as follows: java.sql.SQLException: Cannot insert the value NULL into column 'VALIDATED'.
	Platform	All
	Workaround	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.
41	CR059332
	Problem	Problems have occurred when running WebLogic Integration samples on Windows 2000 Advanced Server systems over an MSSQL 2000 database.
	Platform	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.
42	CR059362
	Problem	Problems occur during the importing 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.
	Platform	All
	Workaround	None
43	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'
	Platform	All
	Workaround	None
44	CR059972
	Problem	The encoding Cp037 is no longer defined as a valid Codepage value in the data integration Format Builder. An exception is thrown if you try to open an MFL document that contains a field with the Cp037 encoding.
	Platform	All
	Workaround	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'/>
45	CR060005
	Problem	After a user inactivates a trading partner in order to update it, the WebLogic Integration B2B Console shows it as inactive, but the following message is displayed when the trading partner is updated: <Error> <B2B> <<Admin> ERROR: Update failed because Trading Partner: testHub is active>
	Platform	All
	Workaround	None
46	CR060143
	Problem	Invoking an undeployed application view service using the application integration plug-in puts the application view into an unstable state. When you invoke the undeployed service asynchronously, an exception similar to the following is displayed: System error: Error in "WLAIPlugin" plugin: "java.lang.IllegalStateException: Async service invocation has not been enabled for this application view. Change the asyncEnabled attribute in the ApplicationView Deployment Descriptor to 'true', or use invokeService instead." When you invoke the undeployed service synchronously, an exception similar to the following is displayed: System error: Error in "WLAIPlugin" plugin: "com.bea.wlai.client.ApplicationViewException: Could not setup resources in ApplicationView 'myAppView'". After you deploy your application view and invoking the service again, an exception similar to the following is displayed: java.rmi.RemoteException: EJB Exception: ; nested exception is: java.lang.NullPointerException java.lang.NullPointerException at com.bea.wlai.client.bean.ApplicationViewBean. verifyAppViewName( ApplicationViewBean.java:137)
	Platform	All
	Workaround	To return your application view to a stable state, test the service from the Application View console or restart your Weblogic Server.
47	CR060174
	Problem	The MDBGenerator utility does not create deployment descriptors that correspond with WebLogic Server 6.1 required descriptors. It still uses elements found in WebLogic Server 6.0. This limitation prevents any generated MDBs from being deployed unless you edit the XML files by hand.
	Platform	All
	Workaround	Edit the following elements in the ejb-jar.xml file of the generated MDB file: jms-acknowledge-mode becomes acknowledge-mode jms-destination-type becomes destination-type run-as-specified-identity becomes run-as Save the file and rerun the utility to generate a deployable MDB.
48	CR060202
	Problem	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. The SAX parser incorrectly assumes that there is a root element in the document.
	Platform	All
	Workaround	Always add at least one element in the editor. Also, the invoked error handler can ignore the XML if desired.
49	CR060239
	Problem	The XSL Transform action cannot successfully produce a nonXML result (such as HTML output). It is limited to producing XML documents.
	Platform	All
	Workaround	None
50	CR060313
	Problem	Uninstallation of Power.Enterprise! Server or Client software does not work if the uninstallation is performed from the Windows NT (or Windows 2000) Add/Remove Programs dialog box. The uninstallation looks for the jre on the directory from which the Power.Enterprise! software was initially installed.
	Platform	Windows
	Workaround	Select the Uninstall item from the PowerIt program group on the Start menu. At the end of uninstallation, you may need to manually remove the installation directory.
51	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")
	Platform	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.
52	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>
	Platform
	Workaround	Edit config.xml to increase the default MaxCapacity setting for the JDBCConnectionPool from 36 to 80.
53	CR060600
	Problem	The EDI adapter fails to work if WebLogic Integration is running on a DHCP machine and Power.Server! is running on a different machine that is configured statically or dynamically.
	Platform	All.
	Workaround	Either of the following workarounds 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.
54	CR063330
	Problem	When you define or edit an Application View for the DBMS Adapter from the Application View console, and try to add or edit an Event or Service in the Application View, you see a "Browse DBMS ..." link. Clicking this link causes a pop-up window to open and display available schemas in the database. However, you may only see a Close Window button, and the schema names may or may not be displayed. If this occurs, the DB2 driver on your platform is missing two required JDBC functions.
	Platform	Linux for S/390 and zSeries
	Workaround	Close the pop-up window and fill in the associated text field or text area with a fully qualified table name, SCHEMA.TABLENAME.

####<Dec 17, 2001 8:47:09 PM CST> <Error> <HTTP> <etplx60> <myserver> <ExecuteThread: '9' for queue: 'default'> <> <> <101083> <Connection failure>
java.net.SocketException: Error in poll for fd: '128', revents: '24'
at weblogic.socket.PosixSocketMuxer.deliverBadNews(PosixSocketMuxer.java(Compiled Code))
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java(Compiled Code))
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java(Compiled Code))
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java(Compiled Code))

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

Limits on Length of Database Character Strings

Entity

Oracle

MSSQL

Cloudscape

Sybase

DB2

TradingPartner

256

255

254

DeliveryChannel

252

128

256

128

254

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
JDK	JDK 1.3.1 is provided automatically on 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 256-MB RAM minimum (512 MB recommended) Network connection Access to a CD reader (if installing from CD)
Databases	One of the following: Cloudscape 3.5.1, 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
JDK	JDK 1.3.1 is provided automatically on 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 256-MB RAM minimum (512 MB recommended) Network connection Access to a CD reader (if installing from CD)
Databases	One of the following: Oracle 8.1.6, Oracle 8.1.7, Microsoft SQL Server 7.0 or 2000 using jDriver, or Sybase System 11.9.2. (See Database Support.)
Hewlett-Packard HP-UX 11.0
WebLogic Server Platform	BEA WebLogic Server 6.1 with Service Pack 1
JDK	JDK 1.3.1 is provided automatically on 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 256-MB RAM minimum (512 MB recommended) Network connection Access to a CD reader (if installing from CD) For information on 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 with Performance Pack
WebLogic Server Platform	BEA WebLogic Server 6.1 with Service Pack 1
JDK	JDK 1.3.0 (Classic VM with JIT enabled) is provided automatically on 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	DB2 V7.2 using JDBC 2.0 driver
SuSE Linux Enterprise Server 7 for S/390 and zSeries
WebLogic Server Platform	BEA WebLogic Server 6.1 with Service Pack 1
JDK	JDK 1.3.0 (Classic VM with JIT enabled; build cx390130-20020111 or later). The required JDK is not included with the WebLogic Server installation. You must install the JDK separately.
Hardware and Software Requirements	S/390 or zSeries Architecture 280 MB free disk space 256-MB RAM minimum (512 MB recommended) Network connection
Databases	DB2 V7.2 using JDBC 2.0 driver


	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

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