|
|
|
|
|
|
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.
Release Note Topics
This document includes the following topics:
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.1 SP1 documentation set located on the BEA documentation Web site at the following URL:
http://www.oracle.com/technology/documentation/index.html
About This Release of BEA WebLogic Integration
BEA WebLogic Integration 2.1 Service Pack 2 (SP2) is a single, unified platform that provides the functionality needed to integrate business systems within an enterprise, and to link those systems in a collaborative arrangement with an organization's trading partners.
Underlying this functionality is the industry-leading J2EE application server, BEA WebLogic Server, which provides the critical infrastructure needed to develop integrated solutions that support transaction management, security, fault tolerance, persistence, and clustering.
WebLogic Integration 2.1 SP2 supports end-to-end business integration by providing functionality in the following areas:
What Is New and Improved in This Release
BEA WebLogic Integration 2.1 Service Pack 2 (SP2) delivers the following new functionality and enhancements:
WebLogic Integration 2.1 SP2 now supports WebLogic Server 6.1 SP3 in addition to WebLogic Server 6.1 SP2.
A full WebLogic Integration 2.1 SP2 installer is available. Use the full installation if you have never installed WebLogic Integration or if you have WebLogic Integration 2.0 or earlier installed.
If you already have WebLogic Integration 2.1 or WebLogic Integration 2.1 SP1 installed, and you have a BEA WebSUPPORT account, you can use the service pack upgrade installer. Information about downloading these installers is provided in Installing BEA WebLogic Integration at the following URL:
http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1sp/install/index.htm
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.
Detailed information about this component of WebLogic Integration is available at the following URL:
http://download.oracle.com/docs/cd/E13215_01/wlibc/docs70/index.html
WebLogic Integration 2.1 SP2 supports Contivo Analyst 3.5. This software extends the data transformation capabilities of your data integration environment. Refer to the documentation packaged with the Contivo Analyst software. Contivo Analyst software can be downloaded from the BEA Download Center at the following URL:
http://commerce.bea.com/downloads/weblogic_integration.jsp
Version information is now written to the server log at startup. This enhancement was added in response to CR081976. The following sample shows a portion of the output to the server log:
####<Jul 4, 2002 3:57:48 PM EDT> <Info> <WLI> <mysystem> <myserver>
<main> <system> <> <000000>
<Weblogic Integration version:
Weblogic Integration BPM MDB Generator 2.1 SP2 07/04/2002 15:35:43 EDT #21159
Weblogic Integration Studio 2.1 SP2 07/04/2002 15:35:43 EDT #21159
Weblogic Integration Worklist 2.1 SP2 07/04/2002 15:35:43 EDT #21159
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
The following table provides a list of the platforms supported for WebLogic Integration 2.1 SP2 as of July 2002.
BEA WebLogic Integration Release 2.1 Service Pack 2 as of November 2002 As of November 2002, WebLogic Integration 2.1 SP2 has been certified on the following platform:
http://download.oracle.com/docs/cd/E13222_01/wls/certifications/certifications/
suse_linux_s390.html#41429
Best Practices
This section contains the following usage information about WebLogic Integration components and functions:
Specifying JAVA_HOME for Red Hat Linux
The JDK required for use with Red Hat Linux is not provided with WebLogic Server. Download and install Sun JDK 1.3.1_01 separately before installing WebLogic Server.
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.
cd $BEA_HOME
ln -s $JAVA_HOME JAVA_HOME
cd $WLI_HOME
JAVA_HOME=JAVA_HOME
Settings Required for Running WebLogic Integration on HP-UX 11.0
Changes to default configuration settings and parameters are required to run WebLogic Integration on an HP-UX 11.0 system.
In WLI_HOME/setenv.sh, locate the following lines:
HP-UX)
JAVA=$JAVA_BIN/java
JAVAC=$JAVA_BIN/javac
JAVA_OPTIONS="-Djava.compiler=NONE -Xms128m -Xmx512m"
export JAVA JAVA_OPTIONS JAVAC
Change:
JAVA_OPTIONS="-Djava.compiler=NONE -Xms128m -Xmx512m"
to:
JAVA_OPTIONS="-hotspot -Xms256m -Xmx256m"
Also, set the max_thread_proc to 512 and max_users to 128. You must have root access to make this change.
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. Add the Oracle 9i thin driver to START_WL_CLASSPATH in the startWeblogic script for both the peer1 and peer2 domains. This issue was originally reported as CR081061.
Using the Proper JDK
Ensure that you are using JDK version 1.3.1. On a Windows NT or Windows 2000 machine, WebLogic Integration 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: JDK 1.3.1 is shipped with WebLogic Server 6.1, so it should already be installed on your system.
If you have 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 giving you the option of selecting or creating a BEA_HOME directory.
Add BEA_HOME\jdk131\bin to the Windows PATH environment variable. Install JDK 1.3.1 on the target machine and start the installation again.
This issue was originally reported as CR065631.
Support for Null Variables
WebLogic Integration 2.1 SP2 supports null values in variables through the wli.bpm.server.evaluator.supportsNull option in the startWebLogic script. When this option is set to true, all variables are initialized to a null value. When this option is set to false, all variables are initialized to their default values. The default setting for this option is false.
For details about this option, see Starting, Stopping, and Customizing BEA WebLogic Integration.
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. The Java Servlet classes are delivered in the WEB-INF\classes\jsp_servlet directory in a WAR file. Since the JSP pages are not bundled into the WAR file, the adapter developer needs to establish the mapping between a URL pattern and a specific Java Servlet class in the Web application descriptor WEB-INF/web.xml.
For each JSP page for your adapter, provide a Servlet declaration. For example,
<servlet>
<servlet-name>confconn</servlet-name>
<servlet-class>jsp_servlet.__confconn</servlet-class>
</servlet>
This declares a Servlet named confconn and associates it with a Java Servlet class jsp_servlet.__confconn. The Web application container looks for this class in the WEB-INF/classes directory in the WAR file. After declaring all Servlet classes, associate each Servlet with a URL pattern via a servlet-mapping.
<servlet-mapping>
<servlet-name>confconn</servlet-name>
<url-pattern>confconn.jsp</url-pattern>
</servlet-mapping>
This servlet-mapping associates all HTTP requests for confconn.jsp to the confconn Servlet in your Web application. The adapter developer must have a servlet-mapping for all Servlets in the Web application. See the sample adapter's web.xml file for an example of all Servlet declarations and mappings needed for an adapter.
Sample Email Adapter Deprecated
The sample Email adapter is deprecated in this release of WebLogic Integration. The Email adapter will be removed from the product in a future release.
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.exe, because doing so effectively defeats the SecurityManager, making it possible for a malicious workflow to launch anything on the client computer. For better security, list only those programs needed to execute the workflow.
WLPISec.properties contains a list (one item per line) of unqualified executable files, such as the following:
BPM Plug-Ins in a UNIX Environment
The plug-in architecture uses the Image object from the AWT library. As a result, the server needs to have the DISPLAY environment variable set in order to create this object. The plug-in simply sends the image file across the wire and allows the client to create the Image object.
When a UNIX system is used, an issue arises. Because the plug-ins make a connection to the Xwindow server, logging off can bring WebLogic Server down, as well, even if you start it with NOHUP and run it in background mode. For this reason plug-ins should never instantiate any class that needs the Xwindow server.
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. Also, when running WebLogic Integration on a managed server, do not deploy any application integration components since they cannot currently be deployed in Managed Server mode.
Improving XSLT Performance
If you frequently use XSLT, take the following actions to help improve XSLT performance:
-XX:NewSize=128m -XX:MaxNewSize=128m
These steps are recommended for all users with enough memory to do so, but they become even more important when using XSLT because of its high short-term memory usage. See Tuning Performance in Deploying BEA WebLogic Integration Solutions for further information about JVM options.
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.
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.
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. Database Limits on Strings WebLogic Integration limits the number of characters you can include in a string for a B2B integration entity. If the only consideration in determining such limits were the need to be consistent with the repository, the limit would be 256 characters. Many other factors, however, must be considered: required indexing for deadlock prevention, data integrity and constraints, indices on multiple columns (for example, MessageId and DeliveryChannel), and inherent database-specific index size limitations. Therefore, we recommend the values listed in the following table.
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: If you then deploy the wlai-ejb-server EJB from the WebLogic Server Console, the application integration plug-in for BPM cannot detect that it has been redeployed and throws an exception similar to the following: As a workaround, restart WebLogic Server after redeploying the wlai-ejb-server EJB. X Window Emulator and Telnet Connections to UNIX The GUI-based installer for WebLogic Integration (which is written in Java) is not certified to run on a UNIX system reached through an X Window emulator or Telnet connection. Instead, we recommend a direct X Window connection. You can also use the console-mode installation procedure on UNIX systems without a graphics (windowing) workstation. 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: If you are using a terminal with no graphics capability, nothing can be done about this error. The plug-in sample cannot be deployed, and you cannot run some workflows that require this plug-in. If you are using an X terminal, set the DISPLAY variable, and restart the server. The message should not appear again. Nonpersistent Mode Recommended for B2B Integration We recommend that you use the B2B integration functionality in nonpersistent mode. For details about invoking nonpersistent mode, see Configuring Persistence and Recovery in Administering B2B Integration. When using B2B in persistent mode, be sure to change the defaultdeliverymode setting for JMSConnectionFactory to non-persistence. (The default setting is persistence.) 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. To work around this problem, do not set up one trading partner with two delivery channels. Instead, set up two trading partners, each with its own delivery channel. Configure a hub delivery channel for one trading partner, and a spoke delivery channel for the other. Problems Viewing PIP Instance Variables When you attempt to list the variables of certain RosettaNet PIP instances, using the WebLogic Integration Studio, the following error may be reported: This TemplateSysVariable class is found in wlc.jar. To avoid this problem, put wlc.jar in the Studio classpath. This problem was previously recorded as CR054700. 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 The system administrator should set this variable before installing WebLogic Integration 2.1 Service Pack 1. If you experience problems with the time zone indicator on your system, contact your system administrator. When the time zone environment variable is not set, the XML returned for a JavaDate type field is specified in Greenwich Meridian Time (GMT) as follows: <Date>Wed Nov 15 10:55:37 GMT-06:00 2001</Date> When the TZ variable is set to your time zone, the XML that is returned reflects your local time zone, as shown in the following example: <Date>Wed Nov 15 4:55:37 CST 2001</Date> WebLogic Integration Studio Online Help Refresh Limitations Given certain settings for file types on your system when using Microsoft Internet Explorer as your default browser, you may encounter a limitation when refreshing HTML frames. This refresh limitation prevents online help pages from being displayed properly. For example, when you click the Help icon at the product user interface entry point, the initial online help splash page should be displayed. If, while navigating the help system, you click the Help icon again and the splash page is not reloaded as expected, the cause of the problem is probably this refresh limitation. To work around this limitation, change your system file type settings by completing the following procedure:
Unknown error: NameNotFoundException: Unable to resolve
com.bea.wlpi.Admin. Resolved: 'com.bea.wlpi' Unresolved:'Admin' The server was unable to complete your request.
NoSuchObjectException: RemoteInvokable - id: '319'
java.rmi.NoSuchObjectException: RemoteInvokable - id: '319' 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.unknown error: ClassNotFoundException: com.bea.b2b.protocol.rosettanet.businessop.TemplateSysVariable
export TZ
Viewing the Studio Online Help Using Netscape Navigator on UNIX Platforms
To view the Online Help for individual Studio dialog boxes using Netscape Navigator on UNIX platforms, open the browser first. Once the browser is open, you can click the Help button in any dialog box or press the F1 key.
B2B Console Hangs When You Enable and Register a Collaboration Agreement
The B2B Console allows you to configure collaboration agreements and make them available immediately by enabling and registering them. (For details, see "Configuring Collaboration Agreements" in the B2B Console Online Help.)
In the following situation, however, the B2B Console may hang:
To work around this limitation:
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://www.oracle.com/technology/documentation/index.html
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.
This release provides you with additional flexibility in working with XML data in the Studio. The Set Workflow Variable, Post XML Event, and Send XML to Client dialogue boxes now include a check box labeled as follows: Escape XML reserve characters in generated node values. Figure 1 shows the new Set Workflow Variable dialog box.
Figure 1 Set Workflow Variable Dialog Box
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 <name>PG&E</name>. However, consider the following example using the XML variables, as shown in Figure 2: Figure 2 Post XML Event Dialog Box with Escape XML Check Box Enabled
xmlsub1: <sub-elem-1>value 1</sub-elem-1>
xmlsub2:
<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>
The XML that is sent from this Post XML Event action contains: Disabling the Escape XML reserved characters check box leaves the data as generated, as shown in Figure 3. This is useful for creating XML documents from subdocuments. Figure 3 Post XML Event Dialog Box with Escape XML Check Box Disabled
<?xml version="1.0" encoding="UTF-8"?>
<root>
<element-1><sub-elem-1>value
1</sub-elem-1></element-1><element-2><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></element-2></root>
This results in a properly formed XML document being sent: This release also supports the ability to pass an XML subdocument as an XSL transform parameter, as shown in Figure 4: Figure 4 XSL Transfor Dialog Box Used to Pass an XML Subdocument
<?xml version="1.0" encoding="UTF-8"?>
<root>
<element-1>
<sub-elem-1>value 1</sub-elem-1>
</element-1>
<element-2>
<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>
</element-2>
</root>
The variable contents are: The XSL Transformation contains: The result of the transformation returned in xmlout is as follows: 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. Now, instead of being a singleton, TimeListenerBean is initially deployed with 5 instances. It uses the wlpiOrderKey = <instance id> message header for message selection to ensure that timer actions are processed sequentially for any given instance and different instances are processed by a different bean. Information for Deployers Users deploying applications should note that a prime number of TimeListenerBeans must be deployed to ensure that any one instance's time actions are processed by the same MDB. This preserves the sequence of time actions within an instance. Information for Administrators Administrators should update the WebLogic Server configuration file, config.xml, with the required arguments for the com.bea.wlpi.server.timeprocessor.TimeProcessor startup class. A sample follows: where: url = URL of the server that the TimeProcessor is deployed on Also, note the addition of FailureIsfatal="true". Information for Application Designers Users designing applications should note that since the instance ID is used as the message selector for the MDBs, it is possible that time actions could all get sent to the same TimeListenerBean. This occurs in situations where the instance containing the time action is always a factor of the number of deployed TimeListenerBeans. For example, if 3 TimeListenerBeans are deployed and the application has the following template definitions: Parent where the Grandchild template definition performs a time action such as Task Due Date, and then starts another instance of the Parent. This results in the instance of Grandchild always going to the same MDB because the result of the following calculation: <instance#>%3 (the remainder of <instance>/3) will always be the same, assuming these are the only workflows running). Time-Based Processing and WebLogic Time Services BPM time-based processing is now coupled more closely with WebLogic Time Services. This affects the trigger time of time-based actions in a BPM workflow. The accuracy of timers is dependent on that of the underlying WebLogic Server timers, with a resolution of milliseconds but an accuracy of plus or minus roughly one second. This means that time based actions may fire up to one second prematurely. Time-based actions should, therefore, not be used for timing-critical designs needing extreme accuracy. 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: where IID is the instance ID of the workflow. This only occurs in design patterns where a time-based action is performed in the first transaction of the workflow, and when the timer is scheduled for a period of time shorter than it takes the workflow to complete. For example, consider a workflow template definition comprised of the following nodes:
xmlsub1: <sub-elem-1>value 1</sub-elem-1>
xmlsub2:
<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><xsl:param name="testParam1"/>
<xsl:param name="testParam2"/>
<xsl:param name="testParam3"/><xsl:template match="/">
<out>
<date>
<xsl:value-of select="$testParam1"/>
</date>
<xmlsub1>
<xsl:copy-of select="$testParam2"/>
</xmlsub1>
<xmlsub2>
<xsl:copy-of select="$testParam3"/>
</xmlsub2>
</out><?xml version="1.0" encoding="UTF-8"?>
<out>
<date>Mon Mar 18 11:40:43 PST 2002</date>
<xmlsub1>
<sub-elem-1>value 1</sub-elem-1></xmlsub1>
<xmlsub2>
<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></xmlsub2>
</out><StartupClass
Arguments="url=t3://localhost:7001,user=wlpisystem,
pwd=wlpisystem,
connectionFactory=com.bea.wlpi.QueueConnectionFactory,
queue=com.bea.wlpi.Timer"
ClassName="com.bea.wlpi.server.timeprocessor.TimeProcessor"
FailureIsFatal="true" Name="TimeProcessor"
Targets="myserver"/>
user = the wlpisystem user
pwd = wlpisystem user's password
connectionFactory = JNDI name of the WLPI connection factory
queue = JNDI name of the Timer queueWorkflow warning: com.bea.wlpi.common.WorkflowException:
The system could not find the specified workflow instance:IID
Start
where:
Task1 performs a timed event action that sets the timer for 1 second
Task2 performs some simple processing
Event waits for a message and then processes it
Under normal circumstances, workflow processing starts and the timer is set in Task1 for (current_time + 1 second). The workflow processor moves to Task2 and executes its actions. The Event node is reached and the transaction is committed. The workflow is now stored in the database. The timed-based action fires and resumes processing the instance, performing those tasks in the overdue action list (canceling the event, for example) if the workflow has not completed.
In this example there is a very high probability that, if the workflow is called repeatedly, at one point the timer will fire early enough and the latency before the transaction commits will be long enough that the timer processing begins before the workflow instance has been committed to the database. In testing, we have found that the situation occurred after 249, 750, and 1122 instance have processed normally. Obviously, the probability of this occurrence increases as the time for the trigger decreases and the amount of processing prior to the workflow instance being committed to the database increases (more actions are performed prior to the first quiescent point).
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. Select the Accounting tab, and double-click the Generate Invoice task. In the Error Warning message box, enter a valid state abbreviation, such as CA.
16. Select the Shipping role tab, and double-click the Ship Order task to execute it.
17. Return to the Studio.
Workflow Status Is Not Automatically Refreshed
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. You must close and reopen the Workflow Status dialog box to display the current status. This behavior was reported in CR080922 and will be reflected in the Worklist documentation in a future release per CR080930.
Data Integration Padding and Truncation Features
This section includes information on enhancements to the data integration functionality provided by WebLogic Integration 2.1 SP1. This information will be added to Translating Data with WebLogic Integration in a future release. Specifically, it provides an enhanced version of Message Format Language, MFL Version 2.02, with three new features supported by this new version of MFL:
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.02, the padding feature offers two options for padding fixed-length fields:
You can specify either but not both of these options. Padding of fields is done when fields are translated from binary to XML and from XML to binary. MFL v2.02 provides a new attribute, padtype, which can be specified with a value of either leading or trailing.
Padding at the beginning of a field is indicated by the following:
padType="leading"
Padding at the end of a field is indicated by the following:
padType="trailing"
Truncating
In MFL v 2.02 includes a new truncation option. Using this feature, you can specify the number of characters to be truncated at the start or the end of the field data. Two truncation options are provided:
Both options require you to specify the number of characters (denoted by n).
If the Truncate First n characters option is selected, the first n number of characters are removed or truncated from the field. The value n should be an integer less than or equal to the length of the field.
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.
For example, truncateFirst="2" truncates the first 2 characters of the field. Specifying truncateAfter="3" truncates everything after 3 characters.
Padding of Mandatory Fields
This padding of mandatory fields option is provided so that mandatory groups or mandatory fields that do not have data at translation time are filled or padded if a default value is provided for the field. If no default value is specified and the field does not have data during translation, than an error is generated. This feature is useful in the case of groups occurring multiple times, where data for all fields in the group is the same. By providing default values for all the fields in the group, those group occurrences without data are padded with default values.
This feature works is only offered for XML-to-binary translations. There is no MFL change for this feature.
Bulk Loader Errors and Improper B2B Shutdown
The following information will be added to Administering B2B Integration in a future release. This information was compiled in response to CR049068.
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, similar to the following:
D:\bea\wlintegration2.0\collaborate\bin\systemData>
bulkloader BulkloadMssqlConfig.xml <May 30, 2001 2:22:10 PM PDT>
<Error> <WLC> <<BulkLoader> ERROR: Can not run bulkloader when WLC
is running.> ERROR: Can not run bulkloader when WLC is running.
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.
Installation and Migration
This section discusses WebLogic Integration 2.1 SP2 installation and migration and includes the following topics:
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.
Upgrade Installation
An upgrade installer is provided that allows you to update WebLogic Integration 2.1 SP1 to WebLogic Integration 2.1 SP2.
WebLogic Integration 2.1 SP2 uses the standard BEA upgrade installer which overlays an existing installation after backing up user-modifiable files. The upgrade installer functionality has not changed for this release. For instructions on performing a service pack upgrade, see "Installing and Uninstalling Service Pack Upgrades
" at the following URL:http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1sp/install/instupg.htm
To migrate from WebLogic Integration 2.1 to WebLogic Integration 2.1 SP2 an addition to the database is required. The ebXML feature, which was added in WebLogic Integration 2.1 SP1, requires the addition of a new table along with some new rows being added to existing system tables. There is a script that performs this 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.
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. Depending on the version of WebLogic Integration that you have installed, this may involve more than one step. You will need access to the migration utilities and scripts that are currently delivered as part of the WebLogic Integration 2.1 installation package.
Migrating from WebLogic Integration 2.1
The migration tasks required when upgrading from WebLogic Integration 2.1 to WebLogic Integration 2.1 SP2 and the same as those required when upgrading from release 2.1 to release 2.1 SP1. For a description of migration tasks, see Migrating WebLogic Integration 2.1 to WebLogic Integration 2.1 Service Pack 1 at the following location:
http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1sp/migrate/berlsp1.htm
Migrating from WebLogic Integration 2.1 SP1
There are no migration tasks required when upgrading from WebLogic Integration 2.1 SP1 to WebLogic Integration 2.1 SP2.
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.jsp
Contacting BEA Customer Support
If you have questions about this release of the WebLogic Integration software, if you encounter problems while installing and running the software, or if you need to obtain patches, contact the BEA Customer Support Center at the following URL:
You can also contact your BEA Customer Support Center by using the contact information provided on the Customer Support Card, which is included in the product package.
When contacting your BEA Customer Support Center, be prepared to provide the following information:
|
|
|
|
|
Copyright © 2002 BEA Systems, Inc. All rights reserved.
|