CR302006

If you installed WebLogic Integration and opted to apply patches after successful completion of the installation, the installer automatically applies patches to WebLogic Server, Workshop for WebLogic Platform, and WebLogic Portal.

The installer does not check whether WebLogic Portal or Workshop for WebLogic Platform are installed or not. So, patches to these two products are applied even if they are not installed

If WebLogic Portal or Workshop for WebLogic Platform are installed at a later point, the installer overwrites the patches but Smart Update shows the patches as applied.

Workaround: Perform the following steps.

CR302929

FileNotFoundException when you install WebLogic Integration without Workshop.

If you do not have Workshop for WebLogic Platform installed and opt to apply patch at the end of your WebLogic Integration installation, you will encounter FileNotFoundException.

Operating System: all UNIX platforms

Workaround: Include Workshop as part of your custom installation or do not select Apply Patch, then apply WebLogic Server and Portal (if installed) patches manually via Smart Update. If the exception already occurs, you can use Smart Update to apply the remaining WebLogic Server patches.

CR301122

When deploying a Process application containing a JWS having a web method parameter of type XBean, with the XSD for the type/element defined in the <web project>/schemas folder EAR deployment fails.

Workaround: Make a copy of the XSD to the <utility project>/schemas folder as well.

CR300337

CR287765

When JWS invokes JPD, the callback to JWS from a JPD fails in a cluster.

Workaround: The com.bea.control.annotations.MessageBuffer must not be used on the callback operations of a Process control that is used to invoke a JPD from a JWS. Using the com.bea.control.annotations.MessageBuffer annotation will not work reliably in a cluster environment.

CR300140

While editing a newly created event subscriptions of a worklist instance, two Edits interfere each other.

Workaround: Delete the event subscription created, and recreate it.

CR300060

During the WebLogic Integration upgrade, in the WebLogic Server Console, when you access the deployment section, navigate to a particular application and click on the + sign to expand, the navigation section changes to "Showing 1 - 10 of 10" and previous/next links are disabled.

Workaround: Click on deployment link from left navigation and navigate to same page again.

CR299266

After application source upgrade, MFL Transformation failed with XQuery Exception (XQRLUserException).

Unlike in 8.x, the 9.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.

For example, an MFL file located at project/schemas/dir/purchase.mfl will yield XMLBeans that belong to the XML namespace: dir/purchase.

CR296394

The user portal displays default values that are actually not in the database. If you accept these values, they are inserted into the database.

At runtime, an API call for a property value does not return the value by default.

If the user properties can be:

If the user description can be edited, the User Portal shows the value at the closest level.

CR296376

The User Portal does not display the request XML when running an 8.1x upgraded application.

Workaround: None.

CR295076

You might encounter a database deadlock with Worklist applications if you have configured your domain with DB2.

Workaround: There is no known workaround at this point.

CR292434

Potential database deadlock when using Microsoft SQL.

You might encounter a database deadlock if you have configured your domain with Microsoft SQL.

Workaround: After you have created your domain, modify the datasource scripts to add the “SendStringParametersAsUnicode=false” property.

CR290980

CR295210

Issues due to WebLogic Portal 9.2 template patches.

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.

Workaround: There is no workaround for this problem.

--------------------

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.

Workaround: Select the WebLogic Portal checkbox to create the Portal domain.

--------------------

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.

--------------------

When you create a WebLogic Portal domain by extending workshop_wl.jar, p13n.jar and wlp.jar templates together, without explicitly invoking loadDB(), the resulting domain fails to start because of missing tables.

Workaround: You need to explicitly invoke loadDB().

CR293795

WebLogic Integration 9.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 you wish to create a new domain and also add backward compatibility support to that domain, you must create the WebLogic Integration domain, and then extend that domain with the wli_worklist81x extension template (using the configuration wizard).

WebLogic Integration 8.1.x domains that are upgraded to 9.2 will *automatically* have backward compatibility support added to them. No further customer action is required.

CR298397

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".

Workaround: In this case, you must target the MSG_BUFFER_QUEUE to a specific JMS Server with the following submoduletargets option to your weblogic.Deployer command:

-submoduletargets cgJMSServer@WlwRuntimeAppScopedJMS@WseeJmsServer_auto_1.

CR295076

You might encounter a database deadlock with Worklist applications if you have configured your domain with DB2.

There is no known workaround at this point.

CR290839

An error is displayed from the server console while accessing User Management from the console.

Workaround: This is a known issue, and the exception is not critical. The IllegalStateException that is displayed can be ignored.

CR291534

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'.

Workaround: You need to change the create policy and remove the <Anonymous>. By default <Anonymous> is added to the Global Task Plan Create policy. Thus, a task can be created Out of the Box by anyone.

CR289425

Warning and Debug messages are displayed while starting the Out-of-the-box Integration domain.

Workaround: The administrator, in a production mode, must set a test table depending on the chosen database - for the databases supported by WLI.

CR288712

CR288827

You will get an exception when you try to extend any portal-enabled domain with the WSRP template (wsrp-simple-producer.jar) either using the Configuration Wizard or WLST offline.

CR288966

Exception message displayed in the purging tasks of Worklist application.

Based on the permissions you have, you can perform the purge action. An exception message is displayed when the tasks are of type “Compat 8.1.x”.

<Anonymous> users can purge 8.x Compat Tasks.

CR283676

When you enter a custom User Interface page for the first time in a browser session, a blank page is displayed.

Workaround: You need to refresh your browser to view the custom User Interface page.The usage of an incorrect case in the task-ui-registry.xml entries can cause the related custom task page to appear blank for the first time, and is then displayed after the page is refreshed.

CR283190

The Managed Server does not start unless the Administration Server already running.

Workaround: None.

CR287304

Worklist database scripts for Sybase need to be ported to WebLogic Integration 9.x.

The problem has been resolved. The SQLs have been updated.

CR285577

In the Worklist console screen, the Home link does not point to the correct screen after creating a user in UserManagement.

Workaround: The user management links from the JPD console point into the worklist console. The problem is fixed and the Home button works correctly.

CR277602

JVM Memory Errors

While working on the Worklist Console, you may encounter the java.lang.OutOfMemoryError: PermGen space memory error.

Workaround: You must set the domain JVM maximum memory as -Xmx1024m and the maximum PermSize as -XX:MaxPermSize=256m in the respective Domain environment setting files.

For Windows:

domain/bin/setDomainEnv.cmd

For UNIX Platforms:

domain/bin/setDomainEnv.sh

CR272488

Exceptions are encountered in the Server Console when using the Worklist Sample Application.

While working on the Worklist Sample Application through the Worklist User Portal, you may encounter org.apache.beehive.netui.util type exceptions in the Server Console. You can ignore the exceptions displayed in the Server Console as they are not very critical.

CR268925

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.

CR267653

Worklist cursor pagination does not work when a separate transaction deletes tasks selected by the cursor.

Works as designed.

CR203350

Worklist Administration Module may throw exception traces

The Worklist Administration Module may throw exception traces instead of clean error messages after simultaneous Worklist operations on the console; the exceptions are valid.

CR180096

Security Configuration Dependency on web.xml

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. For more information, see the following:

CR156713

Result of trackdata() Call Not Recorded For Large Documents on Transaction Rollback

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 transaction that calls JpdContext.trackData(XmlObject value) or JpdContext.trackData(RawData value) is rolled back.

The document passed in is large enough to be stored in the SQL document store.

Workaround: To minimize the risk of trackData calls being affected by a process rollback, call trackData() in its own transaction (in a perform node encapsulated within an explicit transaction boundary).

CR266987

The container-managed sign-on portion of the Application Integration Security test fails.

Workaround: You need to set the desired principal map after the application redeployment.

CR266949

AI Workshop EAR project facet is required to enable AI Design-time hookup.

Workaround: You need to manually configure and maintain ai-publish.properties. The AI design-time works correctly with the Workshop 9.0 IDE assuming the ai-publish.properties file is located in EarContent/META-INF/ai-publish.properties, and is updated regularly.

CR171722

In Iterative Development Mode, Applications Deployed as EAR, JAR, WAR, or RAR files Are Not Available to Clients Such as the Application View Design Console

When the server is running in iterative development mode, only applications that are in exploded form in the Workshop Application pane may be accessed by clients such as the Application View Design Console. Applications that are packaged into a deployed EAR file are not accessible.

In other words, when you are running in iterative development mode, the following conditions must be met for an application to be available for selection in the Application View Design Console:

CR157033

Event Generator Target Changes for a Suspended Application View Only Apply to New Events (DBMS Sample Adapter)

For the DBMS sample adapter, changes to the event generator target for a suspended application view do not apply to events already in the system. Only new events (those triggered after the change) are assigned to the new event generator target. Events already in the system are processed by the previous event generator target.

CR156862

Synchronous Service Counts Multiplied By the Number of Managed Servers After a Rollback

When synchronous services are invoked and a transaction rollback occurs before the services are performed, the WebLogic Integration Administration Console displays an incorrect synchronous service count. The count displayed is the number of synchronous services in process multiplied by the number of managed servers in the cluster.

CR155711

Performance Issues When Posting Event Messages to Remote Application View Clients

Performance issues have been noted due to the time required to post event messages to JMS topics for remote application view clients.

Workaround: A new option has been added to enable or disable event delivery to remote application view clients. There are two ways to disable event delivery to remote application view clients:

The first method turns off event delivery to remote clients for all application views deployed in the server. The second method turns off event delivery to remote clients only for the application view for which the MBean method is called. With remote event delivery disabled, JMS resources are not consumed for the event topic.

CR155627

Republish Application Views to Incorporate New EJB Descriptors

The design-time EJB descriptors and the descriptors generated by the application view compiler (invoked when an application view is published) have changed for WebLogic Integration 8.1 SP2.

Workaround: You must republish your application views to ensure that the modified EJB descriptor is included in your application view EJBs.

CR155471

Set SupportsLocalTransaction to True on XA Pool for Event Connection

The SupportsLocalTransaction option must be set to true on the XA pool used for an event connection. (Otherwise, you must use a non-XA pool for the event connection.) If the option is not set correctly for an XA pool, an exception similar to the following is thrown:

java.sql.SQLException: Logical handle no longer valid

If the DBMS sample adapter uses the same database instance on which the WebLogic Integration tables reside, it is recommended that all other XA connection pools also have the SupportsLocalTransaction option set to true. If the adapter uses a separate database instance, then only the XA pool for an event connection should have the SupportsLocalTransaction option set to true.

Workaround: To set this option, use the WebLogic Server Administration Console and navigate to Services > JDBC > Connection Pools.

CR155462

Multiple Primary Event Generator Instances Result in Database Conflicts

The event generator target field is blank by default when the application is first deployed on the cluster. This implies that the event generator should not be activated on any node in the cluster. With the DBMS sample adapter in a clustered environment, multiple instances of a primary generator instance result in database conflicts and errors. Care should be taken to specify an appropriate generator instance specification for each server in the targets list, and ensure that only one server in the list contains the generator instance id '1'. For example, in a three node cluster, the following targets would properly distribute event generator instances on the nodes, with the instance on server1 being the primary instance.

Event Generator Targets: server1=[1/3],server2=[2/3],server3=[3/3]

However, the following targets would all mistakenly create duplicate primary generator instances:

Event Generator Targets: server1,server2,server3

Event Generator Targets: server1=[1/3],server2=[1/3 2/3], server3=[3/3]

In the first case, no generator instances are specified, and each server creates an instance with an ID of 1, making it the primary instance. In the second case, two servers explicitly define a primary generator instance.

If you inadvertently specify event generator targets improperly, you may see database conflicts and errors during event generation at runtime. In this case, see the workaround below.

Workaround: To reset the event generator instances:

CR138792

Asynchronous Service Counts and Suspended Async Service Counts Can Be Incorrect in Cases Where Database or EIS Failures Occur

If an XA-capable EIS being used for async service invocations fails, or if the database being used for JMS persistence fails, the transaction enclosing the work being done by an async service will be rolled back. This rolls the async service request itself back onto the AI async request queue, and allows the request to be retried. However, the transaction rollback affects only the async service request and any work it may have done against the EIS, and does not affect the suspended async service counts displayed in the WebLogic Integration Administration Console for an application view or adapter instance.

Thus, in cases where the EIS or JMS database fails after the async service count has been incremented to account for a successful async service invocation, and before the containing transaction in the async service processor MDB is committed, the async service count will be higher than the actual effective service count against the EIS (since the work done will be rolled back, but count is not decremented).

In cases where the EIS or JMS database fails after a suspended async service completes, and the suspended async service count has been decremented, and before the containing transaction in the async service processor MDB is committed, the suspended async service count will be lower than the actual effective suspended service count in the application integration async request queue (since the request was rolled back, but suspended count is not incremented).

Administrators should be watchful for failures in either a transactional EIS or database (generally they will see service failures and a suspended adapter instance and application view related to the EIS failure). After the EIS has recovered from such a failure and suspended async services have been given sufficient time to complete, the administrator should check the suspended async service count. If the count is non-zero (or even negative), the count is incorrect.

To allow administrators to force the suspended async service count back to zero in those cases that the displayed count is incorrect, the resetSuspendedAsyncServiceCounts() method has been added to the AppViewSummaryMBean interface. See the Javadoc at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wli/docs92/wli.javadoc/index.html

CR138630

Asynchronous Service Error Counts Multiplied by the Number of Servers in the Cluster

In a clustered environment, the asynchronous service error counts displayed on the WebLogic Integration Administration Console are multiplied by the number of nodes in the cluster. For example, if 5 asynchronous service invocations fail on a three-node cluster, the asynchronous service error count is shown as 15.

CR326895

A PersistenceException occurs when passing ebXML messages

A PersistenceException occurs when passing ebXML messages with binary attachments between two B2B applications, if the documentmaxinlinesize parameter in the wliconfig.properties file is set to the default value.

Workaround: Set the documentmaxinlinesize value to 2.5 times higher than the data size.

CR302072

There is a problem displaying the contents of a node editor (in-place editor) in the Process editor canvas when using large fonts on windows.

To view the problem, double click the node Double Click to Select Start Event in a newly created process file. The node editor contents appears cut-off at the bottom.

Workaround: Try setting a smaller font. You should be able to see the complete contents of the editor.

CR297730

In WLI 9.2, if a synchronous request is made to a frozen or suspended JPD, a null response is returned.

This response is confusing to the user, who may be led to believe the request was processed successfully.

Workaround: This feature works fine as expected for suspended and frozen processes, the following error is displayed:

<Nov 1, 2006 5:08:35 PM IST> <Error> <WLI> <000000>

<Failure=com.bea.wli.bpm.runtime.ProcessInstanceUnavailableException: Process instance unavailable due to status: 'Frozen'. Service URI: '/WebProject1/test/Test1.jpd'. InstanceId: '1162381060435'.>

CR298911

Endless timeout events getting displayed in Test console.

Workaround: The feature works as designed. This is a general expected behavior of all non WLI controls. The external controls are not frozen or suspended with the JPD.

CR298097

The browsing feature does not work for JPDs.

Workaround: In the EAR deployment mode, the test browser allows you to browse inside the war file. However, you cannot open or read the actual files. In the split source mode, no files are displayed as the war is empty. It is not possible to reset the status of a process from within the test browser.

CR296136

In WLI9.2, any redelivery limit greater than zero is lost when a message is either frozen, received while a process is frozen or suspended, or simply received out-of-order. This may defeat attempts by a process author to handle.

Under certain circumstances the message may be retried more than original redelivery limit due to the limited information available from the JMS subsystem about JMS messages being processed.

CR292400

In WLI9.2, while generating a Process Control and Fronting JWS, empty conversation finish method is generated.

Workaround: Works as designed. The reason, the conversation is seen when the Process Control is generated is due to the fact that there is additional node (perform) after the clientRequestWithReturn node. It is recommended to create other client visible nodes (conversation continue) after the clientRequestWithReturn node and then start the conversation annotation on the process control. Remove the perform node after the clientRequestWithReturn and the conversation start annotation on the process control is not seen. When the process control has a conversation annotation, the generated JWS will have a place holder conversationFinish method giving the client ability to finish the conversation. In this case, the client must call the conversationFinish to finish the conversation. This restriction will not be present once the JWS front end feature is enhanced so that the conversation on the JWS is finished implicitly when the JPD conversation completes.

CR287671

The package names of MFL xbean types are derived from MFL file paths, relative to the schemas directory.

For example, types for an MFL file foo/BAR.mfl would live in a package foo.bar.

But, if the MFL file contains an alphabet which occurs after a number, case of the alphabet changes to upper case. Example: a file /foo/foo2bar.mfl will result in a package name of foo.foo2Bar

This affects upgrade scenarios where the user has:

Workaround: You need to update the references to use the 9.2 style package names.

CR284937

Test console Displays Comments in the JPD

When you use the test console to test an application that you have upgraded from 8.1 to 9.2, you may see comments annotated as follows in the Test console:

"/** * @jpd:process process:: ....."

You can ignore these comments—the upgraded JPD contains the original (8.1) process annotations as comments and these are displayed in 9.2.

CR284905

In the WLI 9.2 JPD, wrong icons are used for Service Control nodes.

Workaround: None.

CR279454

Dynamically Propagate Changes in a JPD to the Control and WSDL files

Unlike in 8.1, changes made to a JPD in 9.2 are not automatically reflected in its corresponding Control or WSDL files.

Workaround: If any changes are made in a JPD, you must regenerate the Control and WSDL files to reflect these changes.

CR275878

Renaming the default Web Content folder (WebContent) in a Web Project.

Manually renaming only the default "WebContent" folder in a Web Project would cause problems when the project is compiled or run. This is because the new name does not reflect in all the settings files that reference it.

Workaround: To successfully change the Web Content folder name, you have to ensure the new name is also recorded in the following documents:

CR269354

Warning message is displayed when JPDs are redployed.

A warning is issued instead of aborting the deployment of the web application. Error messages are displayed when the deployment is aborted.

Warning: Undeploy the application and republish the JPD.

CR245676

Eclipse problems viewer which lists all the diagnostics in a JPD is displayed in the Design view.

You can use the Design view to find the source of the error.

CR206655

ProcessRuntimeMBean Failing to Retrieve Stateless Business Process Instance Information in Development Mode

The ProcessRuntimeMBean is not normally used for stateless business processes. It is usually used for stateful processes. In development mode, not production mode, on some processes, it may return the wrong information.

CR200072

Uncommitted Local Transaction when Connection Returned to Connection Pool

The local transaction is left open. To close it, in the JDBCConnectionPoolMBean, set the property RollbackLocalTxUponConnClose="true".

CR155813

Timeout Attribute not Supported on Transaction Blocks

You cannot specify a timeout property on an explicit transaction block in the WebLogic Workshop graphical design environment. This feature is deprecated in Service Pack 2. If a business process you created in an older version of WebLogic Integration contains a timeout property on a transaction block, a compiler warning is issued to indicate that the timeout value is ignored.

CR155294

The Freeze on Failure Property is Ignored for Explicit Transactions

The freeze on failure property for explicit transactions is ignored. That is, if you set the freeze on failure property on an explicit transaction block, it is ignored at run time. When this property is set on the start nodes in a business process, it operates correctly and as documented.

This feature is deprecated in Service Pack 2. If a business process you created in an older version of WebLogic Integration contains a freeze on failure property on a transaction block, a compiler warning is issued to indicate that the freeze on failure value is ignored.

CR154487

Use of @jpd:unexpected-message Annotation

Business processes often include nodes such as Control Receive or Client Request, at which the process waits for delivery of an expected message before continuing. By default, messages that arrive before they are expected—that is, before the process encounters the Control Receive or Client Request node in question—are automatically buffered and are delivered later when the process is ready to receive them. In some cases the process designer may wish to discard any such early, unexpected messages; this enables the process to ignore messages that arrived earlier yet are no longer relevant to the process. The jpd:unexpected-message annotation gives process designers the ability to control this behavior on a node-by-node basis. The annotation is available for Control Receive nodes and Client Request nodes in positions other than the Start node. The annotation can be set by switching to the Source view, clicking on the corresponding node’s method header, consulting the unexpected-message header in the Property Editor, and setting the action property from save (the default) to discard. The annotation can also be set using the annotation editor just like all the method annotations. The annotation is placed into the JPD source code, as shown in the following code segment:

/**
* @jpd:unexpected-message action="discard"
*/

CR145540

Behavior of rename-old Attribute for the File Control

If you use a File control for which the suffix-name or suffix-type attributes are not specified, but for which the create-mode attribute specifies rename-old, the create-mode attribute specification is not honored. In other words, the older file is not renamed; instead it is overwritten.

Workaround: If the create-mode attribute specifies rename-old, you must specify a value for the suffix-name.

CR138164

How to View More Events in the Test Browser

If you want to see more than 30 events (the default) in the Test Browser, before running the business process, select the Console tab of the Test Browser and enter a larger number in the Keep last number message field, where number represents the number of messages to be displayed.

CR182788

After performing JTA and JMS migrations from a failed managed server, a process instance may remain in running mode.

A repeating set of error messages similar to the following appears in db2diag.log:

Instance:DB2 Node:000

PID:3888(db2syscs.exe) TID:5400 Appid:/1721616.3366.00090031001F
data protection sqlpxTEntrySwitchIn Probe:300
Database:DBNAME
DIA8036C XA error with request type of "". Transaction was not found.
ZRC=0x80100024.

CR156912

Deploying an EAR in Cluster Configurations Causes Certain Warnings That Can Be Ignored

Specifying a cluster name as the target when you deploy an EAR file causes BEA-149055 warnings to appear in the WebLogic Server console window for the WebLogic Server that hosts the WebLogic Server Administration console (WebLogic Administration Server). These warnings include the following text:

Having multiple individual servers of a cluster as targets instead of having the entire cluster as the target can result in non-optimal load balancing and scalability.

You can ignore these messages.

CR3000356

The change in the Workshop Time control behavior from 8.1 to 9.2 causes problem when the control is used from JPD.

Workaround: WliTimerControl is the default WebLogic Integration timer control for JPDs. There is limited support for the WLW Timer Control when used from a JPD.

CR295021

9.2 Workshop Web Service Control does not support WSDL with a fault message and without any parts specified.

Workaround: Either remove the fault message or add atleast one part to the fault message.

CR292434

Potential database deadlock when using Microsoft SQL.

You may encounter a database deadlock if you have configured your domain with Microsoft SQL.

Workaround: After you have created your domain, add the SendStringParametersAsUnicode=false property to the data source scripts.

CR288927

Issues using sendRequest in TIBCO Rendezvous™ Control with Certified Messaging

When using TIBCO Rendezvous Control with Certified Messaging, the sendRequest function can return a null response. This may also cause the server process to consume close to 100% CPU.

Workaround: These issues are intermittent and do not have a solution or workaround. You can check the response message for a null value, and in the event of a 100% CPU utilization, restart the WebLogic Integration server.

CR287071

No foreign JMS destinations visible while creating JMS Controls using the Wizard.

JMS Control and Workshop JMS Control creation wizards in Workshop the Destination fields do not show foreign JMS destinations.

Workaround: Foreign JMS destinations can be added directly in the source code annotations.

CR272670

Tuxedo Control is not supported in 9.2

CR181948

http-xml Protocol Not Supported For Service Broker Control

If you use the Service Broker control to call processes, do not use http-xml attribute.

CR145542

I\Overwrite Option Does Not Work When Suffix Type Is Set To Timestamp (File Control)

If you set the suffix attribute timestamp in the File control, the create-mode=overwrite attribute is not honored. Instead, the file is renamed.

CR145540

File Override Behavior of the File Control

When using the file control, if no suffix is specified, the create-mode="rename-old" attribute is not honored. Instead the file is overwritten.

CR138481

Specified Scheme, Server Name, or Port Number in Process Control Target is Ignored

The Process control target can be specified in several ways:

This target location is relative to the application. It must not have a scheme, server name, or port number. If a scheme, server name, or port number is specified, it will be ignored.

CR289678

A SQL Exception can occur when you create an RDBMS Event Generator on a table that has LONG column(s) (Oracle Database).

Workaround: Change the table to use LOB instead of LONG.

CR288927

When using TIBCO Rendezvous Control with Certified Messaging, at times the sendRequest function returns a null response. This may also cause the server process to consume close to 100% CPU.

Workaround: These issues are intermittent and do not have a real solution or workaround. You can check the response message for a null value, and in the event of a 100% CPU utilization, restart the WebLogic Integration server.

CR276975

Creating a New TIBCORV Event Generator with a blank space through WebLogic Integration Administration Console throws javax.servlet.ServletException: jndi lookup failure for TIBCO Event Generator.

Workaround: Event Generator names should not have any spaces in between.

CR206549

CR206332

Slow Down of Sybase Database Table or Microsoft SQL Table When Using RDBMS Event Generator

When a Trigger Type event is created on a Sybase Table or Microsoft SQL Table, the RDBMS Event Generator creates a Shadow table that is a replica or subset of the User’s Table. The Trigger copies the Inserted, Deleted, and Updated rows from the User Table into the Shadow Table. As the rate at which rows are inserted, deleted, or updated into the User table increase beyond the rate at which the event generator can poll and process rows, the new rows become backlogged and cause the Poll query to slow down

Workaround: The Shadow table gets created with the same name as the Channel Rule Definition name with an _BEA_SDW suffix. To speed up polling and hence processing, a Unique Index must be created on a particular column. For example, if the Trigger Event name (Channel Rule Definition name) is hello123, the Shadow Table gets created as hello123_BEA_SDW. To workaround this problem, create a Unique Index as follows:

CREATE UNIQUE INDEX [idx_hello123] ON
schema_name.hello123_BEA_SDW(BEA_SEQ_ID)

CR206528

View All Timer Event Generators Page Does Not Refresh Status

When using a Timer Event Generator, the View All Timer Event Generators page does not refresh the status from Suspend to Running after clicking Resume.

Workaround: You must refresh the browser page to show the updated status.

CR206519

Timer Event Generator May Not Reflect Changes in Business Calendar

After making a change to the Business Calendar, the Timer Event Generator may not pick up the change in the calendar.

Workaround: In the WebLogic Integration Administration Console> Event Generators > View All File Event Generators window, select the appropriate Timer Event Generator, click Suspend, and then click Resume.

CR205996

RDBMS Event Generator Trigger Not Deleted For Certain Trigger Type Events created on Microsoft SQL Server

When creating a Trigger Type Event on a schema other than with the DBO username, the SQL Server creates the Trigger in the same schema as the User Table on which it was created. If there is an attempt to insert rows after the Event has been deleted, errors are thrown because the Trigger still exists. Creating the Trigger does not require a schema name prefix but dropping the Trigger requires a schema to be prefixed to the statement.

Workaround: After the Event is deleted, the Trigger must be dropped manually using a simple command DROP TRIGGER <user_table_schema_name>.<trigger_name>.

CR204272

Enabling Auto Commit for RDBMS Event Generators when Working with Informix Databases

If you are working with an Informix database, you should always enable the auto commit mode during an Insert, Update, or Delete event.

CR202902

Automatic Delete for Query or Post Query Events in RDBMS Events

In the case of an Query or Post Query Events query with automatic delete (nothing specified in Post Query), the Max Rows Per Poll value is ignored. This was tried with values of 1 and 10 for Max Rows per poll. But in each case, all the rows were published and deleted in one single poll instead of 1 or 10 per poll as specified in the Channel rule definition.

This case is specific to the Sybase database when using the Data Direct driver.

In Oracle 9i DB with Oracle's 9i Thin Driver, the behavior was as expected and only 1 or 10 rows were published as specified in the channel rule definition.

In DB2 and Informix, the automatic delete option is not supported.

CR201132

Creating Triggers on a Sybase Database Table

If you are working with a Sybase database, when a Trigger Event is created on a Sybase table that already has one Trigger Event of the same type, such as Insert, configured, the older Trigger is replaced. This means that the older Trigger Event stops working.

You can have one Insert, one Delete and one Update Trigger Event per Sybase Table.

CR200743

Correct Data Not Published for Informix Database Triggers with Different Data Types

Due to the fact that Informix databases have peculiar ways of retrieving the Precision and Scale of DECIMAL and MONEY data types, it is recommended that you specify the Precision and Scale in the User Table - DECIMAL(p,s).

CR200681

Restrictions on Trigger Type Events Created on Informix Databases

Trigger type events created on Informix databases have some restrictions. The value specified in the No. of Threads field and Max Rows Per Poll field must always be 1 and the value specified in the Polling Interval field must be greater than the total time it takes to publish the rows picked up in every poll.

CR200495

Creating New RDBMS Event Generator Channel Rule Definitions in Informix Databases

If you are working with an Informix database and you want to delete an existing channel rule and create a new channel rule with the same name as the one you just deleted, you must set the Statement Cache size to zero.

CR196414

File Event Generator FTP Supports Only Windows and UNIX Type FTP Servers

Only Windows and UNIX type FTP servers are supported by the File Event Generator FTP. VMS is not supported.

CR196088

Using the RDBMS Event Generator in a Cluster

To use the RDBMS Event Generator in a cluster, the managed nodes must be created with specific IP addresses and port numbers. By default, the IP addresses of the managed nodes are null. If the default settings are used, events cannot be created in RDBMS Event Generator. IP Addresses and Port Numbers of the Managed Nodes must be provided.

Additionally, the Administration server sends messages to the distributed queue, Because the distributed queue is available only on the managed nodes, the JNDI-scoped security for wli.internal.egrdbms.queue must have lookup access to the default group: Everyone. BEA recommends always using the default security policies for administrative and server resources.

CR186350

Setting Event Generator Polling Interval for Configuration Changes

The polling interval of the Event Generators may be set to a user-defined interval by using the following Java system properties:

These properties may be set on the Java command that starts the server. Each property sets the number of milliseconds between polls. For example:

-Dwli.eventgen.timer.checkConfigDelay=30000

This sets the Timer Event Generator polling for configuration changes every 30 seconds.

If not specified, the default polling interval of 10 seconds is used.

CR138802

Retrieving or Filtering on Timer Event Generator Metadata with Channel Type of XML is Not Supported

Events published by the Timer event generator with channel type of XML do not contain metadata headers, consequently, filtering or retrieving events based on metadata is not supported at this time.

CR297754

DND of Expression functions do not work on Linux

If you open an XQ file, select a target element in the Design view, select a function in the Expression Functions view, and attempt to DND a function to a valid location, the function is not applied.

Workaround: You can drag and drop the function only when the mouse pointer icon changes to indicate a droppable mouse pointer.

CR297025

Intermittent problems with mapping a source element to a target element.

Drag and Drop in the Linux IDE sometimes does not function when you try to map a source element to a target element.

Workaround: Drag and drop the source element to the target element only when the mouse pointer icon changes to indicate a droppable mouse pointer.

CR287396

Strings that include spaces are not allowed in the XQuery Condition Editors

In 8.1, you could create a condition in an XQuery Condition Editor that included a space in string values for the condition. However in 9.2, you must enclose such strings in single or double quotes.

For example, in 8.1, a Decision Node with the following variable and string selected on the left and right hand sides of the builder, respectively, created a valid condition:

(left hand side) variable: '$requestXML/ns0:shipAddress/@state'

(right-hand side) string: New Jersey

Condition Generated: data($requestXML/ns0:shipAddress/@state) = “New Jersey”

Workaround: For 9.2, the XQuery Condition Editor requires that you enclose such strings in single or double quotes—use the following syntax for a string such as the one in the right-hand side of the condition builder example above.

‘New Jersey’ or “New Jersey”

CR206671

Transformation Exception for In-Flight Processes when Shutting Down and Restarting Server

If the server is shutdown while a business process transformation is running and restarted, a transformation exception is thrown.

Workaround: Restart the business process.

CR206148

Message Format Error While Using MFL Non-XML to XML Transformation Method in Format Builder

The delimiter of Group level causes the exception in Format Builder or run time.

Workaround: Remove this delimiter.

CR182658

CR138588

Casting is Limited or Unsupported Between Some XML Schema Types and Java Types in Transformations

During run time, the casting in transformations between the following types can be limited or unsupported:

For example, the casting is limited between the XML Schema type xs:double and XML Schema type xs:integer. The casting from a source xs:double to a target xs:integer in a transformation will be successful during run time if the source double value is equal to 8 but will fail if the source double value is equal to 8.5 or even 8.0. The casting between these XML Schema types is unlike the casting done between types in the Java or C language.

The casting between the XML Schema type xs:date and the java.util.Date is unsupported and will fail during runtime because these two types are not equivalent. The XML Schema type xs:date contains only a date component and does not contain a time component while the java.util.Date Java class contains both a time and date component.

CR276691

The iterativeDevDisabled() call has been deprecated in WebLogic Integration 9.2.

Workaround: The iterativeDevDisabled() call has been replaced with the productionModeEnabled() call for Trade Partner Integration (Utils.java).

CR182302

Bulk Loader Utility is Not Compatible with XA Database Drivers

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 at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wli/docs92/manage/bulkloader.html

For information about how to load TPM data using the WebLogic Integration Administration Console, see “Importing Management Data” in Trading Partner Management in Managing WebLogic Integration Solutions at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wli/docs92/manage/tpm.html

CR175845

Extraneous Error When Deleting a Certificate

When deleting a certificate from the WebLogic Integration Administration Console, if you encounter the following error message, click Continue to dismiss it:

Certificate with name cert_name does not exist for partner partner_name.

Despite the error, when you click Continue, the certificate is deleted.

Workaround: The error message can be disregarded.

CR156555

WebLogic Administration Console Generated Client Certificates May Not Work for Two Way SSL Testing

The “self-signed” client certificates that you can generate for testing purposes through the WebLogic Integration Console may not work for two way SSL configurations when client certificates are enforced on the server-side.

Workaround: When you are testing two way SSL configurations, generate your test certificates by using other tools, such as OpenSSL.

CR155713

DOCTYPE is Not Preserved in XQuery Transformations

XQuery transformation does not preserve the DOCTYPE element.

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 available at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wli/docs92/tptutorial/rosettanet.html

CR155685

Update Older Bulkloader XML Files when Using Signature Configurations

This version of WebLogic Integration supports MD5, in addition to SHA1, as a digest algorithm option for RosettaNet. If you want to use signature configuration with older versions of bulkloader XML files, you need to add the following attribute to these files:

The signature-digest-algorithm attribute is optional. Its representation is a character string in the DBMS. If you do not specify a value when you import the older version of the XML file, the value is set to NONE.

CR155614

Trading Partner Integration API Changes

The following APIs have changed:

CR155423

The ebXML Protocol Uses the Remote Trading Partner’s Values for Retry Number, Retry Interval, and Persist Duration

When you are using the ebXML protocol for Trading Partner messaging, the values used for Retry Number, Retry Interval, and Persist Duration are always the values of the remote trading partner, not the local Trading Partner.

CR154862

The Default Trading Partners have New Trading Partner IDs

The two default trading partners that are created when you create a new WebLogic Integration domain have new default trading partner ids, as shown in Table 2-1.

If you use a new WebLogic Integration domain with any old application data, be sure to update any relevant files.

CR138262

Using Controls to Send Messages from Participant Business Processes is Not Recommended

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.

Test_TradingPartner_1

TP1-id

000000001

Test_TradingPartner_2

TP2-id

000000002

CR337692

Deployment of a WLI application with Web Service controls fails

Deployment of a WLI application fails after upgrading the WLI application with Web Service controls from 8.1.x to 9.2 MP2.

Workaround: Recreate the Web Service controls migrated to 9.2 MP2 and reference the newly created 9.2 MP2 controls in their upgraded processes to successfully deploy the upgraded application.

CR306344

If you upgrade a 9.2GA platform to 9.2 MP1 using the upgrade installer and then roll back to 9.2GA, sample domains in WebLogic Integration and WebLogic Portal will be unusable.

Therefore, you must be very sure about upgrading to 9.2 MP1. In case you do upgrade and then decide to roll back, the sample domains will be unusable.

CR300337

com.bea.control.annotations.MessageBuffer must not be used on the callback operations of a Process control that is used to invoke a JPD from a JWS. Using the com.bea.control.annotations.MessageBuffer annotation will not work reliably in a cluster environment.

CR299867

Timer control does not work in a cluster.

Workaround: When you upgrade an 8.1 application, the timer control is upgraded to the WebLogic Workshop timer control that does not work in cluster. You need to manually upgrade the application to the clustered version, if the application is to be used in clustered environment.

CR299266

After application source upgrade, MFL Transformation failed with XQuery Exception (XQRLUserException).

In 9.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.

For example, an MFL file located at project/schemas/dir/purchase.mfl will yield XMLBeans that belong to the XML namespace: dir/purchase.

CR299154

The Upgraded Work List Application throws a ControlException in the upgraded Integration domain.

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.

CR298097

The Platform application upgrade from 8.1 SP5 to 9.2 failed while building the Schemas (XML Beans).

Workaround: None

CR296186

In a COFACE Application, inline XQ upgrade does not convert XQ outside of Prolog.

Workaround: In the Source view, locate the xf: and replace with fn: for the xqueries not in prolog.

CR296260

Process libraries like jpdpublic.jar are not added to build path when a 8.x Application with multiple web projects is upgraded.

Workaround: The dependent artifacts are not added in the project as there are no WLI related classes. Therefore, you need to add the libraries manually.

CR296186

Inlined XQuery expressions that occur within process annotations are not updated after selecting the "Upgrade XQ2002 to XQ2004" option.

Even if the "Upgrade XQ2002 to XQ2004" option is selected in the Upgrade Wizard, some inlined XQuery expressions that occur within process annotations are not updated. Like, the usage of the xf: function prefix is supposed to be replaced by the fn: function prefix. So, for example:

<case name=\"Case\" value=\"xf:string($x)\"/>

should be:

<case name=\"Case\" value=\"fn:string($x)\"/>

Workaround: Manually change the function prefix in the source view.

CR295456

The upgrade process allows the synchronization receive 'method' to have a non-void return type.

The upgrade process does not check for the non-void return type, which leads to an compilation error.

Workaround: You can detect this error by parsing the process XML and checking the return type of the message. WebLogic Integration issues a warning/error message that the 8.x source is invalid.

CR295684

Aborting the upgrade process at the Upgrade Preview stage.

Clicking Cancel in the Upgrade Preview tab of the Upgrade Wizard will result in errors that may vary from one application to another. These are not application specific issues and can be ignored.

CR295612

Exception after iterative development using Workshop for Eclipse, and using JWS with MessageBuffer.

A process application is created with JWS and a MessageBuffer annotation. The application is published from Workshop and tested. A few changes are made to the web application without republishing it from Workshop. Invoking either the JWS or a JPD from the test console results in an "Unable to deploy EJB..." error

Workaround: Restart the server and publish the application after server restart to proceed.

CR294091

Insufficient memory when archiving a large web application.

A java.lang.OutOfMemoryException is seen when archiving a very large web application using Workshop generated build scripts.

Workaround: Add memoryMaximumSize="1024m" property to the <apt> task in the build.xml file of the web application.

CR293073

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";;>
<import namespace="http://schemas.xmlsoap.org/soap/encoding/";;/>
<complexType name="Aplicacion">
<sequence>
<element name="certificado" type="xsd:base64Binary"/>
<element name="descripcion" nillable="true" type="xsd:string"/>
<element name="idAplicacion" nillable="true" type="xsd:string"/>
<element name="nombre" nillable="true" type="xsd:string"/>
<element name="organismo" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
<complexType name="AplicacionArray">
<sequence>
<element name="abonadoArray" nillable="true" type="impl:ArrayOf_tns1_Aplicacion"/>
<element name="aplicacionArray" nillable="true" type="impl:ArrayOf_tns1_Aplicacion"/>
</sequence>
</complexType>
</schema>
<schema targetNamespace="http://notanot/jboss-net/services/ServicioWEBAdminNE";; xmlns="http://www.w3.org/2001/XMLSchema";;>
<import namespace="http://schemas.xmlsoap.org/soap/encoding/";;/>
<complexType name="ArrayOf_tns1_Aplicacion">
<complexContent>
<restriction base="soapenc:Array">
<attribute ref="soapenc:arrayType" wsdl:arrayType="tns1:Aplicacion[]"/>
</restriction>

CR291057

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 9.2 Upgrade Guide. The information is available at http://download.oracle.com/docs/cd/E13214_01/wli/docs92/upgrade/component.html.

CR290904

Upgraded XQuery files corresponding to transform functions returning XMLObject may fail to execute at runtime.

Workaround: Modify the XQuery function signature to specify a return value with multiple occurrence.

CR287857

BPEL Import generates Workshop Web Service Control for external services specified as partnerlinks. Workshop Web Service Control does not successfully resolve external schemas imported using relative URIs into the WSDL (associated with the Service Control).

Workaround: Copy the external schemas from the utility project to the web project. Subsequently, place the external schemas relative to the location of the WSDL in the web project.

CR285560

MBCS (multi-byte character set) characters in source files are not supported during upgrade, and appear as garbled text after upgrade.

CR282449

XmlObject[ ] is not supported as a parameter for a JWS callback operation.

CR280701

ArrayIndexofBoundException recorded in the log file during an application upgrade.

During the 8.x application upgrade to 9.2, the ArrayIndexofBoundException might be recorded in the WORKSPACE_ROOT/.metadata/.log file. This is a non fatal error that could arise if BEA_HOME/weblogic92/server/lib/webserviceclient.jar is on the build path of the upgraded application.

CR279416

JWS with callback having same JMS and HTTP transport URIs, will yield a compilation error after upgrade.

Workaround: Before compiling the upgraded JWS, ensure the URIs are unique.

CR275002

A JWS with w3c.dom.* (Document, Element and DocumentFragment) as parameter or return type is not supported.

Workaround: Operation signature and return types of JWS that used w3c.dom types will have to be changed to use SAAJ types. The internal implementation of the operations will have to be updated to translate to or from SAAJ and w3c.dom types.

CR274286

An upgraded JWS that returned an XMLBean type will not compile.

All operations on an upgraded JWS that returned an XMLBean type will have a compile error post upgrade. The message indicates that the return type doesn't match the element name defined by the XMLBean's schema.

Workaround: Remove the @WebResult annotation or change the name to match the schema type.

CR277695

While executing an 8.x application in WebLogic Integration, comment strings are displayed in the test browser console.

Workaround: Works as designed. The Upgraded JPD will have comments so they are shown on test browser. Remove the comments after you the upgrade.

CR265847

Upgrade required for Clients that use SOAP 1.2 messaging format.

Workaround: The WSDL for the Web Service changes during the upgrade to WebLogic Integration 9.2. To conform to the new specification, you need to regenerate the clients of Web Services that use the SOAP 1.2 messaging format