BEA WebLogic Integration Release Notes Release 2.
Copyright Copyright © 2003 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy the software except as specifically allowed in the agreement.
Contents Change History.................................................................................................. 1-1 Release Note Topics .......................................................................................... 1-1 About This Release of BEA WebLogic Integration.......................................... 1-2 What Is New and Improved in This Release ..................................................... 1-3 Platform Support and System Requirements.......................................
Database Limits on Strings....................................................................... 1-46 Displaying Spaces in the Studio ............................................................... 1-47 Undeploying Application Integration EJB While Using BPM ................ 1-47 X Window Emulator and Telnet Connections to UNIX .......................... 1-47 Deploying the Plug-In Sample on UNIX Platforms................................. 1-48 Nonpersistent Mode Recommended for B2B Integration .............
BEA WebLogic Integration Release Notes BEA WebLogic Integration Release 2.1 Service Pack 2 Date: July 2002 Revised: September 2003 Change History The following table lists the changes included in BEA WebLogic Integration 2.1 Service Pack 2 since the initial release. Date Summary of Changes November 21, 2002 Added certification information for SuSE Linux. For more information, see “Platform Support and System Requirements” on page 5. September 23, 2003 Added support information.
What Is New and Improved in This Release Platform Support and System Requirements Best Practices Problems Fixed in This Release Known Limitations Installation and Migration BEA dev2dev Online Contacting BEA Customer Support For this release, only the Release Notes have been revised. Please use the information in these Release Notes in conjunction with the WebLogic Integration 2.
What Is New and Improved in This Release Business process management makes possible the development of complex e-business processes that integrate existing enterprise systems, cross-enterprise applications, and human decision makers. Application integration makes it possible to integrate existing enterprise applications with each other, and with new e-business applications.
information on these features, see “Data Integration Padding and Truncation Features” on page 65. Support for WebLogic Integration - Business Connect 7.0 WebLogic Integration - Business Connect enables you to securely exchange large volumes of documents with your trading partners. WebLogic Integration Business Connect packages documents in secure envelopes that are transmitted among trading partners according to schedules.
Platform Support and System Requirements Platform Support and System Requirements The following sections contain the platforms supported for WebLogic Integration 2.1 SP2, including the hardware and software requirements: BEA WebLogic Integration Release 2.1 Service Pack 2 as of July 2002 BEA WebLogic Integration Release 2.1 Service Pack 2 as of November 2002 BEA WebLogic Integration Release 2.
Table 1. Platform Support for WebLogic Integration 2.1 SP2 Operating System and version WebLogic Integration Version Required WebLogic Server Version Required JDK (included with WLS installation Hardware Requirements DBMS Supported1 Microsoft Windows NT 4.0 (SP6 or higher) Microsoft Windows 2000 Professional Microsoft Windows 2000 Advanced Server 2.1 SP2 6.1 SP4 6.1 SP3 6.1 SP2 1.3.1 Intel Pentium II or higher at 400 MHz (or higher) 256 MB RAM minimum (512 MB RAM recommended) Cloudscape 3.5.
Platform Support and System Requirements Table 1. Platform Support for WebLogic Integration 2.1 SP2 Operating System and version WebLogic Integration Version Required WebLogic Server Version Required JDK (included with WLS installation Hardware Requirements DBMS Supported1 Hewlett-Packard HP-UX 11.0, HP-UDX 11i4 2.1 SP2 6.1 SP4 1.3.1 HP 9000 PA RISC at 100 MHz or higher Oracle 8.1.7, 9i 6.1 SP3 6.1 SP2 2.1 SP1 6.1 SP2 6.
Table 1. Platform Support for WebLogic Integration 2.1 SP2 Operating System and version WebLogic Integration Version Required WebLogic Server Version Required JDK (included with WLS installation Hardware Requirements DBMS Supported1 IBM AIX 4.3.3 with Performance Pack 2.1 SP2 6.1 SP4 1.30 (Classic VM with JIT enabled) RS/6000 PowerPC or higher at 200 MHz or faster Oracle 8.1.7 6.1 SP3 6.1 SP2 2.1 SP1 2.1 8 6.1 SP2 256 MB RAM minimum (512 MB RAM recommended) 6.
Platform Support and System Requirements Table 1. Platform Support for WebLogic Integration 2.1 SP2 Operating System and version WebLogic Integration Version Required WebLogic Server Version Required JDK (included with WLS installation Hardware Requirements DBMS Supported1 Red Hat Linux 7.2 (on IA) 2.1 SP2 6.1 SP4 Sun JDK 1.3.1_03 (downloade d and installed separately) Intel Pentium II or higher at 400 MHz (or higher) Sybase 11.9.2 via Sybase jConnect 6.1 SP3 6.1 SP2 2.
1. Cloudscape is a pure-Java relational database management system that BEA includes with WebLogic Server to allow you to run code samples. It is supported on Windows platforms for development use only; it is not when used in a production environment. Cloudscape is not supported on UNIX platforms. Oracle connectivity is supported with the Oracle thin driver. For Microsoft SQL Server, Oracle, Sybase, or DB2, WebLogic Integration must have network access to the database server.
Best Practices Supported DBMS: DB2 7.2 and Oracle 9i/9.2 Best Practices This section contains the following usage information about WebLogic Integration components and functions: Specifying JAVA_HOME for Red Hat Linux Settings Required for Running WebLogic Integration on HP-UX 11.
WebLogic Integration looks for the JDK in BEA_HOME. Because the JDK is installed separately, choose one of the following methods to point to the correct JAVA_HOME. In both methods, JAVA_HOME is the directory in which you installed JDK 1.3.1_01. Use the following commands to point to the proper JAVA_HOME before setting your environment. cd ln $BEA_HOME -s $JAVA_HOME JAVA_HOME Use the following commands to change the definition of JAVA_HOME in $WLI_HOME/setenv.
Best Practices Oracle 9i Driver Setup for RosettaNet 2 Security Sample If you experience failures when running the RosettaNet 2 Security sample on Solaris systems using the Oracle 9i thin driver, ensure that the driver has been properly set up. Unlike the other samples which use the WLICP and WLISERVERCP values specified in the setenv script, the RosettaNet 2 Security sample refers to its own setup.
Design-Time Web Application JSP Delivery Change The following information will be added to “Migrating Adapters to WebLogic Integration 2.1” in Developing Adapters in a future release. As of WebLogic Integration 2.1 Service Pack 1, sample adapters (eMail, DBMS, and sample) no longer distribute the JSP pages in a Web application archive (WAR). Rather, the JSP pages are precompiled into Java Servlet classes. This approach eliminates the need to precompile JSP pages when WebLogic Server starts.
Best Practices Addressed Messaging Use addressed messaging whenever you want guaranteed message delivery. Nested Workflows Nested workflows must be analyzed for scalability because they can lead to transaction timeouts. The parent of a transaction timeout envelops all children. Calling Programs Using SendXMLToClient Be careful about enabling access to a shell program, such as cmd.
Deploying B2B on a Managed Server To run WebLogic Integration B2B functionality on a managed server, add the following system property to the Weblogic startup script: -Dwli.b2b.server.managedserver.deployed=true This system property was added in response to CR070619. If you are not using a managed server configuration, ensure that this system property is not present in the startup script.
Problems Fixed in This Release Problems Fixed in This Release The following table lists selected problems fixed in BEA WebLogic Integration 2.1 SP2, including a CR (Change Request) number for each problem. Most of these problems were originally documented in the Release Notes for BEA WebLogic Integration Release 2.1 or BEA WebLogic Integration Release 2.1 SP1. For a complete list of problems fixed in BEA WebLogic Integration 2.1 SP2, contact BEA Customer Support. Table 2.
Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued) Change Request Number Description CR064686 Calendar feature does not work correctly. The software now checks that timed starts are within valid calendar periods. CR064767 XML editor cannot handle repeated structures in XML schemas when minOccurs=0. CR064792 Cannot update a remote trading partner's certificate from the B2B Console. CR065049 Japanese characters not displayed correctly in B2B Console.
Problems Fixed in This Release Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued) Change Request Number Description CR067130 Set Task Due Date unreliable under load. CR067534 Locks are not released after business message is sent. CR067836 WebLogic Integration 2.1 SP1 does not work with WebLogic Server 6.1 SP1. CR068192 ebXML plug-in code is not thread safe. CR068291 Start public workflow actions are not executed when public workflow ends.
Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued) Change Request Number Description CR069378 Message Store not found if workflow is rolled back. CR069442 Multipart input stream does not contain boundary with RosettaNet 1.1 CR069519 Need to be able to export and import WebLogic Integration users and roles. A command line utility is now available to export and import the following security/user information: users, roles, organizations, business calendars, and permissions.
Problems Fixed in This Release Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued) Change Request Number Description CR070352 Escape characters in send XML to client task property do not work. For more information on handling escape characters, see “Composing XML from Sub-Documents” on page 53. CR070355 XMLTime-to-live parameter does not accept expressions. CR070361 Format Builder not padding required fields.
Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued) Change Request Number Description CR071815 Message Store not found if workflow rolls back when using RosettaNet protocol. CR072004 PIP retry results in exception regarding fromId not being set CR072097 Initial field focus on Studio and Worklist logon dialog box should be on password field CR072408 And joins cannot be fired in a loop. CR072662 Make Studio tool bar buttons sticky.
Problems Fixed in This Release Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued) Change Request Number Description CR075098 Memory leak occurs when a transaction is rolled back when using the ebXML protocol. An ErrorQListenerBean message-driven bean (MDB) was added that deletes the message store when retries on the eventQueue fail.
Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued) Change Request Number Description CR076649 Need ability to send user-defined fields as part of ebXML message from WebLogic Integration - Business Connect to WebLogic Integration B2Bi. CR076684 Messages are being stuck in the queue. CR076870 Values cannot be removed from the Proxy tab next to the Security tab in the B2B Console. CR077009 Long steady state runs result in a slow memory leak.
Problems Fixed in This Release Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued) Change Request Number Description CR078380 Entity bean collection access problem in Studio. Removed a restriction on displaying entity EJB home finder methods that return multiple objects. All entity EJB home methods are now exposed. CR078389 Studio does not allow deletes of large numbers of instances.
Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued) Change Request Number Description CR079698 XML-to- Binary and XML-to-XML transforms fail when the encoding is SJIS, Shift-JIS or MS Kanji. CR079700 Translate XML to Binary failed when encoding of XML file is EUC-JP or UTF-8. CR079701 SAXException thrown after Compose Business Message and Extract Business Message are processed. CR079794 XT hangs while attempting to save an mfl document with the IBM 037 encoding type.
Known Limitations Known Limitations This section describes known limitations in the BEA WebLogic Integration software. Change Requests The following table describes limitations that are documented in formal change requests (CRs). Whenever available, a recommended workaround is provided. 1 2 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.
3 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.
Known Limitations 6 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.
9 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.
Known Limitations 12 13 14 15 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.
16 17 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.
Known Limitations 19 20 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.
22 23 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. 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.
Known Limitations 24 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.
26 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.
Known Limitations 28 29 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. 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.
31 32 CR065456 Problem There is no ebXML plug-in online help from the Studio help menu. Platforms All Workaround None 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 33 34 35 38 This exception is benign; you can ignore it.
Known Limitations 36 CR066059 Problem There is a Xalan problem in WebLogic Server which causes Format Builder to hang after saving an MFL file. The problem occurs when creating the DTD or XML Schema after saving the MFL document. Platforms Workaround 37 38 39 Disable automatic DTD and XML Schema creation. CR076987 Problem Unable to use an XA driver with B2B. Platforms All Workaround None. CR080411 Problem There is no XA support for transactions when using an Oracle database and driver.
40 41 CR080794, CR081716 Problem Installation problems occur on Solaris 8 systems which use a JRE installation as the default Java installation. Platforms Solaris 8 Workaround Perform a full JDK installation as opposed to a JRE-only installation. This can be done either with an upgrade or a reinstallation of the JDK. CR080836 Problem Changes to the BPM time services to allow multiple workflow instances to be processed simultaneously resulted in a change in the parameters to the BPM startup class.
Known Limitations 42 CR080922 Problem The Workflow Status dialog box is not automatically refreshed when you mark a task done that has a task permission of Mark done without executing. Platforms Workaround 43 You must close and reopen the Workflow Status dialog box to display the current status. CR081112 Problem For workflows with multiple instances of the same message type trigger, an exception similar to the following is thrown for the second action: java.sql.
CR081732 Problem Using WebLogic Server 6.1 SP3 with WebLogic Integration 2.1 SP2 and the Sybase database, an exception similar to the following is thrown when starting the server: SET CHAINED command not allowed within multi-statement transaction Platforms All, with Sybase 11.9.2 database Workaround Use the following patch for WebLogic Server 6.1 SP3: CR081732_610sp3.jar. To obtain this patch, contact BEA Customer Support.
Known Limitations 49 CR081906 Problem In some cases, Oracle streaming errors are generated when loading plug-ins. By default, the plug-ins are loaded automatically. This problem may occur when you load plug-ins manually. Platforms Workaround 50 51 52 Restart the server CR081927 Problem When using the Format Builder, if the encoding specified for the Default Message Format differs from the encoding specified for the Default Field Code Page, binary generation fails.
53 CR082583 Problem All out-of-the box domains shipped in WebLogic Integration 2.1 SP2 do not have the B2B error queue configured. This causes the following warning to appear at regular intervals, which can result in large log files: #### <> <010061>
Known Limitations 55 CR082665 Problem Task and workflow comments are being truncated. Workflow and task comments are limited to a maximum of 254 characters. Comments exceeding this limit are truncated and no exception is thrown. 56 Platforms All Workaround Do not include more than 254 characters in your task and workflow comments. CR082763 Problem The client certificate is not recognized when using two-way SSL on Microsoft IIS with a WebLogic Server proxy plug-in..
XA For Transactions Not Supported There is no support for XA for transactions in this release. Related Change Requests include CR076987 and CR080411. Creating a Database on UNIX Systems Using Microsoft SQL Server Because Microsoft SQL Server is not supported on UNIX systems, you cannot use the createdb script (WLI_HOME/bin/createdb.*) to configure your Microsoft SQL Server 7.0 or Microsoft SQL Server 2000 database on UNIX.
Known Limitations Displaying Spaces in the Studio The WebLogic Integration Studio running on a Solaris system renders spaces as empty box characters. Undeploying Application Integration EJB While Using BPM If the wlai-ejb-server EJB is undeployed or goes down while you are using business process management (BPM) functionality with the application integration plug-in, an exception similar to the following may be thrown: Unknown error: NameNotFoundException: Unable to resolve com.bea.wlpi.Admin.
Deploying the Plug-In Sample on UNIX Platforms If you see the following error message when you start WebLogic Integration on UNIX platforms, you are probably running the software from a terminal with no graphics capability: 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.
Known Limitations Collaboration Agreements Between Delivery Channels for the Same Trading Partner Not Supported If you configure two XOCP delivery channels (one hub and one spoke) for a single trading partner, with a collaboration agreement between them, and you subsequently use the WebLogic Integration Studio to define the Start Public Workflow action for the workflows in the associated conversation, you get a duplicate trading partner error.
Setting the Time Zone (TZ) Environment Variable for the JavaDate Type On UNIX systems, the JavaDate type does not return a date with the appropriate time zone indicator unless the time zone variable, TZ, is set. Ensure that the TZ environment variable is set to the appropriate time zone. The following example shows how to set the TZ environment variable: TZ=US/Central export TZ The system administrator should set this variable before installing WebLogic Integration 2.1 Service Pack 1.
Known Limitations 1. Choose Start→Settings→Folder Options to display the Folder Options dialog box. Alternatively, you can double-click the My Computer icon to display the My Computer window. 2. From the main menu, choose View→Folder Options to display the Folder Options dialog box. 3. Select the File Types tab. 4. Using the scroll bar to the right of the Registered file types drop-down list, review the list of file types and select HTML Document.
In the following situation, however, the B2B Console may hang: 1. You choose Configuration→Parties. On the Parties tab the Enable and register this Collaboration Agreement check box is selected. 2. You click the Add/Apply button. To work around this limitation: 1. Deselect the check box labeled Enable and register this Collaboration Agreement, and click Add/Apply. 2. Select the Monitoring tab and click the Enable this Collaboration Agreement link. 3.
Documentation Additions, Changes, and Corrections Documentation Additions, Changes, and Corrections This section provides additions, changes, and corrections to the WebLogic Integration documentation available on the BEA documentation Web site at the following URL: http://edocs.bea.com Composing XML from Sub-Documents The following information will be added to Using the WebLogic Integration Studio in a future release. The features described were added in response to CR070352.
Figure 1 Set Workflow Variable Dialog Box 54 BEA WebLogic Integration Release Notes
Documentation Additions, Changes, and Corrections By default, this check box is selected. This means that reserved characters, such as the ampersand (&) or right angle bracket (<), are escaped in order to preserve the validity of the XML document. For example, & and < would be replaced with & and < respectively. In the above example, the variable companyXml contains PG&E.
Figure 2 Post XML Event Dialog Box with Escape XML Check Box Enabled The XML that is sent from this Post XML Event action contains:
Documentation Additions, Changes, and Corrections <sub-elem-1>value 1</sub-elem-1> <sub-elem-2> <ss-elem>value 1</ss-elem> <ss-elem>value 2</ss-elem> <ss-elem>value 3</ss-elem> <ss-elem>value 4</ss-elem> </sub-elem-2> Disabling the Escape XML reserved characters check box leaves the data as generated, as shown in Figure 3.
Figure 3 Post XML Event Dialog Box with Escape XML Check Box Disabled This results in a properly formed XML document being sent: 58 BEA WebLogic Integration Release Notes
Documentation Additions, Changes, and Corrections
Figure 4 XSL Transfor Dialog Box Used to Pass an XML Subdocument The variable contents are: xmlsub1: value 1 xmlsub2: 60 BEA WebLogic Integration Release Notes
Documentation Additions, Changes, and Corrections value value value value 1 2 3 4 The XSL Transformation contains: The res
Time Services Changes in BPM This section includes information on changes to time services in BPM. This information will be added to the BPM documentation in a future release. The BPM time services now allow multiple workflow instances to be processed simultaneously when started by a time trigger. Previously, all time actions were processed sequentially by a single instance of the Message-Driven Bean (MDB) TimeListenerBean.
Documentation Additions, Changes, and Corrections url = URL of the server that the TimeProcessor is deployed on user = the wlpisystem user pwd = wlpisystem user's password connectionFactory = JNDI name of the WLPI connection factory queue = JNDI name of the Timer queue Also, note the addition of FailureIsfatal="true".
Time processing occurs in a separate execution thread from that of the workflow. When a timer triggers, the TimeListener MDB attempts to resume processing of the workflow in which the timer was scheduled. In certain situations, it is possible for the timer to trigger prior to the workflow instance having been committed to the database, resulting in a message similar to the following: Workflow warning: com.bea.wlpi.common.
Documentation Additions, Changes, and Corrections Correct Sequence of Steps for Monitoring Running Workflows In Executing and Monitoring the Example Workflows in Learning to Use BPM with WebLogic Integration, under the section “Monitoring the Running Workflows in the Studio”, steps 15 and 16 are reversed, causing problems in properly updating variables. This problem was reported as CR080585. The correct sequence of steps is as follows: 14. Return to the Worklist window. 15.
Padding of mandatory fields Note: All prior versions to 2.02 versions of MFL are completely supported. Padding Fixed-length fields containing data with a length shorter than the length specified in the MFL definition are padded. In previous versions, padding was limited to padding fields only at the end of the field. In MFL v2.
Documentation Additions, Changes, and Corrections If the Truncate After n characters option is selected, all characters after the nth character position from the start of the field are truncated. This feature is only offered for XML-to-binary translations. You can select either option or both options. MFL v2.02 provides a two new attributes to support this feature: truncateFirst and truncateAfter. Both attributes take integer values indicating the number of characters to truncate.
Installation and Migration This section discusses WebLogic Integration 2.1 SP2 installation and migration and includes the following topics: Full Installation Upgrade Installation Migrating from WebLogic Integration 2.1 Migrating from WebLogic Integration 2.1 SP1 Full Installation WebLogic Integration 2.1 SP2 uses the standard BEA installer. No changes to the full installation procedure were made for WebLogic Integration 2.1 SP2.
Installation and Migration update which is accessible from the upgrade wizard and from the command line scripts. For a reference to relevant migration documentation, see “Migrating from WebLogic Integration 2.1” on page 69. No addition to the database is required to migrate from WebLogic Integration 2.1 SP1 to WebLogic Integration 2.1 SP2. If you are using a version of WebLogic Integration prior to release 2.1, existing methods of migrating to WebLogic Integration 2.1 are retained.
BEA dev2dev Online Visit the BEA dev2dev Online to obtain helpful resources that you might find useful when creating your WebLogic Integration applications. Additional development tools, ideas, and programming tips are continuously added to this site, which we encourage you to visit often. You can reach BEA dev2dev Online at the following URL: http://dev2dev.bea.com/index.
