This section describes known limitations in the Oracle WebLogic Integration 10g Release 3 (10.3.1) release. The known limitations are grouped by the following topics:
Workaround: Create a JPD, select 'Subscribe to a Message Broker channel and start via an event', go to source view and update:
@com.bea.wli.control.broker.MessageBroker.StaticSubscription( public void subscription(org.apache.xmlbeans.XmlObject x0) {
@com.bea.wli.control.broker.MessageBroker.StaticSubscription(
public void subscription(com.bea.data.RawData x0, com.bea.wli.worklist.xml.TaskEventMetadataDocument x1) {
Save the JPD, build, and return to the Design view of message broker control, select filter, and proceed.
If you still face any issue just make sure you have the XQuery annotation in the subscription JPD as follows:
|
|||
When configuring a WLI domain with Domain Configuration Wizard and choosing MS SQL 2005 as database from the drop-down list in the Run Database Scripts window, the script for the p13nDataSource is not displayed
|
|||
When installing Oracle WebLogic Integration, WebLogic Server, Workshop for WebLogic, and WebLogic Integration need to be installed in the same BEA HOME and the default names for WebLogic Server directory, Workshop for WebLogic directory, and WebLogic Integration directory must not be changed. Otherwise the installation will not work.
Workaround: Install WebLogic Server, Workshop for WebLogic, and WebLogic Integration together in the same BEA_HOME. The WebLogic Server directory should be '%BEA_HOME%/wlserver_10.3', the Workshop for WebLogic directory should be %BEA_HOME%/workshop_10.3 and WebLogic Integration directory should be '%BEA_HOME%/wli_10.3' where BEA_HOME is the location where the product is installed.
|
|||
After application source upgrade, MFL Transformation failed with XQuery Exception (XQRLUserException).
Unlike in 8.x, the 10.2 MFL-derived XMLBeans belong to a namespace. So, the upgraded XQuery transformations that use MFL-derived XMLBeans as output types must be manually updated to yield XML with elements in the appropriate namespace. The namespace used is determined by the path of the MFL file, relative to the schema source directory.
|
|||
When you create a Platform-like by adding
wlp.jar template onto a WLI domain, with express mode or user explicitly selecting run DB script, loadDB fails when extending wlp.jar and the domain does not start.
Workaround: Using the Configuration Wizard tool, create a Platform-like domain by adding WebLogic Integration templates to a WebLogic Portal domain, or by selecting the WebLogic Portal and WebLogic Integration check-boxes.
When you create a Platform-like by adding the WebLogic Portal component onto a WebLogic Integration domain, with express mode or user explicitly selecting run DB script, loadDB fails when extending
wlp.jar and the domain does not start.
When you create a WebLogic Portal domain by extending
workshop_wl.jar , p13n.jar and wlp.jar templates, one template at a time, with express mode or user explicitly selecting run DB script, loadDB fails when extending wlp.jar and the domain does not start.
When you create a WebLogic Portal domain by extending
workshop_wl.jar , p13n.jar and wlp.jar templates, one template at a time, with loadDB() invoked each time extending a template, loadDB fails when extending wlp.jar and the domain does not start.
Workaround: Extend the required templates together and invoke loadDB() explicitly in the WLST script.
|
|||
WebLogic Integration 10.x domains take longer to start up when compared with WebLogic Integration 8.x domains.
The problem has been mitigated by removing extra backward compatibility resources from newly created WebLogic Integration domains. Newly created domains will not deploy backward compatibility resources (applications, etc.) and will thus boot more rapidly than if those resources were present in the domain.
|
|||
If your application enables message buffering on controls or web services using the annotations com.bea.control.annotations.MessageBuffer or weblogic.jws.MessageBuffer, the following error is displayed when you try to deploy it on a cluster:
"While attempting to create destination MSG_BUFFER_QUEUE in module <name_of_your_ear>!WlwRuntimeAppScopedJMS the JMSServer of name <name_of_your_cluster> could not be found".
|
|||
Any new task plan, by default does not have a create policy for any user: this has to be done explicitly through the worklist console. If this policy is not configured, then the JPDs’ that create tasks and are initiated through the JPD test console fail: This is because the JPD test console invokes the JPDs’ without any authentication and the JPD is run without any principal, thus as 'Anonymous'.
|
|||
The Pointbase database throws an error if the amount of data received exceeds the database size of 30MB.
Workaround: You can use the WLI Administration Console (System > Purge > Purge Tracking Data) to manually purge the data from the tracking table. You can alternatively reduce the tracking level for this process type, if the tracking data is not being used. For more information, see Managing Process Tracking Data in
Process Configuration in Using the WebLogic Integration Administration Console.
|
|||
Unauthorized users (users who do not have Administration/Update/Query rights, or claimant, assignee rights) can see the built-in and user-defined properties of a task. This can happen when a control callback or TaskEventListener delivers a TaskEvent containing this information.
Workaround: Asynchronous events still have user properties as
ChangedProperty instances (each containing a PropertyInstance with a name, type, and so on.) on them, but the property values equals to null. For system properties, they receive a ChangedProperty instance with a name, but the value is equal to null.
|
|||
Do not use the WebLogic Integration Administration Console to access your business process to secure SOAP-HTTP access to your business process if you have already secured your business process using the
security-constraint element in the web.xml deployment descriptor and the @common:security annotation. You will receive a security violation at run time.
|
|||
To avoid a possible problem in subsequent archiving, if both of the following conditions are met, the result of a
trackdata() call will not be recorded in the WebLogic Integration process events table.
|
|||
The XML Meta Data Cache can be used to store configuration information to be retrieved at run-time and set to a control dynamically. For more information, see
XML Meta Data Cache control.
|
|||
A BindingsCheckException is thrown from the ALSB Transport control wizard when a WSDL is used to create a ALSB Transport control.
Workaround: Update the patch profile in the IDE. For details, see
Enabling Runtime (Server) Patches.
|
|||
Attempting to load data in the TPM repository with the Bulk Loader configured to use an XA database driver fails with the following error:
No suitable driver.
Workaround: Configure the Bulk Loader to use a non-XA driver, or load the data interactively using the WebLogic Integration Administration Console.
For information about how to configure the Bulk Loader, see “Configuring the Bulk Loader Configuration File” in
Using the Trading Partner Bulk Loader in Managing WebLogic Integration Solutions.
For information about how to load TPM data using the WebLogic Integration Administration Console, see “Importing Management Data” in
Trading Partner Management in Using the WebLogic Integration Administration Console.
|
|
When deleting a certificate from the WebLogic Integration Administration Console, if you encounter the following error message, click Continue to dismiss it:
|
|
Workaround: If you need the
DOCTYPE element in further processing, add it back into your message by using the obj.documentProperties().setDoctypeSystemId in a Perform node following the transformation. An example of this is shown in the “Walkthrough of the Failure Notifier Business Process” section of the “Step 2: Open the PIP0A1: Notification of Failure Example” example under the “Tutorial Steps” heading of the
Tutorial: Building RosettaNet Solutions
|
|
In WebLogic Integration, you use Trading Partner Integration controls to send messages from the initiator business process to the participant business process. However, in the participant business process it is recommended that you use Client Response nodes to handle outgoing business messages to the initiator.
If you use controls in a participant business process, you may lose the message response signals, such as acknowledgments and error messages. If you need to use a control to send messages instead of using the recommended design pattern, place the control in a subprocess and invoke the subprocess from the participant process.
|
After application source upgrade, MFL Transformation failed with XQuery Exception (XQRLUserException).
In 10.2, MFL-derived XMLBeans belong to a namespace. In 8.x, XQuery transformations that use MFL-derived XMLBeans as output types must be manually updated to yield XML with elements in the appropriate namespace. The namespace used is determined by the path of the MFL file, relative to the schema source directory.
|
|
Workaround: The upgrade does not set the security policy when the default authenticator is used. If you use an authorization provider other than the default LDAP provider, you need to either check or set this security policy.
After you upgrade a WebLogic Integration 8.1 domain, you must set the security policies on the Compatibility 8.1.x Task Plan and allow the 'Anonymous' role in the Create Policy. Use the Worklist Administration Console (the default authorization provider) to set the Create Policy for the Compatibility 8.1.x task plan. If you are using a third-party authorizer, use the related third-party client tools to set the policy.
|
|
Inlined XQuery expressions that occur within process annotations are not updated after selecting the "Upgrade XQ2002 to XQ2004" option.
|
|
Workshop Web Service Control generated in 8.1 SP4 with types selected to Java for a complex type array with rpc/encoded mapped the complex type array to anyType[ ] instead of the concrete type array. For example:
<schema targetNamespace="urn:serviciosAdminNE" xmlns="http://www.w3.org/2001/XMLSchema";;>
|
|
public static class AplicacionArray implements java.io.Serializable
public static class anyType implements java.io.Serializable
anyType[] is not supported by 10.2 Workshop Web Service Control. Therefore, the above Service Control after upgrade will cause errors during deployment or application archive.
Workaround: After upgrade change the types in the service control to point to the concrete type. For example:
|
|
ebXML application using ebXMLControl within java custom control results in a Null Pointer Exception when ControlHandle.sendEvent is not used.
Workaround: Read the note and example to JPD and Control Callback section of the WebLogic Integration 10.2
Upgrade Guide.
|
|
As shown in the following code sample, this lack of support effects generation of Workshop Web Service Control/JWS (using JAX-RPC binding) from a WSDL with references to
xsd:schema element.
|
|
There are two known issues in wftracking/M2_ArchHelloAsync.java file and Process_Tracking_Binary.java. Remove throws Exception from helloDelay_onTimeout methods.
|
|