> Upgrade Guide > Upgrading Business Processes and Control Files for Use with WebLogic Integration 9.2

Upgrade Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Upgrading Business Processes and Control Files for Use with WebLogic Integration 9.2

The following sections describe updates required to Business Processes and Control files before they can be used with WebLogic Integration 9.2.

 

Upgrading Business Processes (JPDs)

In the WebLogic Integration 9.2 environment, all JPD files are given a .java extension rather than their proprietary extension of .jpd. All WebLogic Integration JPD 8.1 annotations are upgraded to JSR 175-based annotations. All the JPD 8.1 or 8.5 annotations are categorized into: common, control and JPD annotations.

In WebLogic Integration 8.1.x and 8.5.x, jpdContext within a JPD was annotated with @common:context. However, in WebLogic Integration 9.2, jpdContext is upgraded to @com.bea.wli.jpd.Context().

For example, a WebLogic Integration 8.x JPD Business Process Annotation is as follows: 

/**
* @jpd:process process::
* <process name="EchoAsync">
*   <clientRequest name="Client Request" method="clientRequest"/>
*   <perform name="Perform" method="perform"/>
*   <controlSend name="start" method="myTimerStart"/>
*   <clientCallback name="Client Response" method="clientResponseCallbackHandler"/>
*   <transaction name="Commit"/>
* </process>::
*/

After the JPD is upgraded to WebLogic Integration 9.2, the annotation is as follows: 

@Process(
	process="<process name=\"EchoAsync\">\n" +
	"  <clientRequest name=\"Client Request\"
	method=\"clientRequest\"/>\n" +
	"  <perform name=\"Perform\" method=\"perform\"/>\n" +
	"  <controlSend name=\"start\" method=\"myTimerStart\"/>\n" +
	"  <clientCallback name=\"Client Response\" 
	method=\"clientResponseCallbackHandler\"/>\n" +
	"  <transaction name=\"Commit\"/>\n" +
"</process>"
)
Note: WliTimerControl is the default WebLogic Integration timer control for JPDs.
Note: JMS transport was supported in WebLogic Integration 8.1 using jws.queue for use by BEA Workshop for WebLogic Platform based artifacts (such as business processes and JWS). In WebLogic Integration 9.2, JWS uses weblogic.wsee.DefaultQueue as the default queue for JMS transport whereas business processes still require jws.queue. Also note that even though WebLogic Integration 9.2 allows you to specify any JMS queue for JMS transport, you must not use jws.queue for new JWS applications as that causes conflict in the WebLogic Integration enabled domain. Do not use jws.queue or customize the queue name (using jws.properties) with JWS applications in WebLogic Integration 9.2.

Table 3-1 provides WebLogic Integration JPD 8.1.x or 8.5.x to 9.2 JPD annotation upgrade information.

Table 3-1 JPD Annotations
8.1 Annotation
Attribute
9.2 Annotation
Attribute
Comments
jpd:ebxml
 
Ebxml
 
Specifies the ebXML parameters for a process.
ebxml-action-mode
 
ebxmlActionMode
 
ebxml-service-name
 
ebxmlServiceName
 
protocol-name
 
protocolName
 
jpd:ebxml-method
 
EbXMLMethod
 
Specifies the ebXML parameters for a method.
envelope
 
envelope
 
jpd:mb-static-subscription
 
MessageBroker.StaticSubscription
 
Specifies the subscription parameters for a business process.
channel-name
 
channelName
 
xquery
 
xquery
 
filter-value-match
 
filterValueMatch
 
message-metadata
 
messageMetaData
 
message-body
 
messageBody
 
suppressible
 
suppressible
 
jpd:process
 
Process
 
Specifies settings for a business process.
binding
 
binding
 
name
 
name
 
freezeOnFailure
 
freezeOnFailure
 
onSyncFailure
 
onSyncFailure
 
retryCount
 
retryCount
 
retryDelay
 
retryDelay
 
stateless
 
isStateless
 
process
 
process
 
jpd:rosettanet
 
RosettaNet
 
Specifies the Rosettnet properties for a process.
protocol-name
 
protocolName
 
protocol-version
 
protocolVersion
 
pip-name
     
pip-version
 
pipVersion
 
pip-role
 
pipRole
 
jpd:selector
 
Selector
 
Precedes an XQuery definition in a business process (JPD) file.
xquery
 
xquery
 
jpd:transform
 
Transform
 
Annotates a transformation control instance, which is instantiated automatically at run time.
jpd:unexpected-message
 
UnexpectedMessage
 
Specifies settings that allow a business process to ignore a message received before the process flow encounters the node at which the message is expected.
action
 
action
 
jpd:version
 
Version
 
Specifies how to invoke subprocesses when different versions of the parent process exist.
strategy
 
strategy
 
jpd:xml-list
 
XmlList
 
Annotates business process variable of Untyped XML - XmlObjectList.
jpd:xquery
 
Xquery
 
Precedes the global XQuery definitions in a JPD file.
version
 
version
Represents the version of XQuery language specification.
prologue
 
prologue
 
jpd:input-message
 
InputMessage
 
Validates the typed XBean parameter at run time.
validate
 
validate
 

 

Upgrading JCX or WebLogic Integration Control Files

After the upgrade to WebLogic Integration 9.2:

For example, if a WebLogic Integration 8.1 JCX contains the following annotation:

/**

* @jc:task-create

* name="{name}"

*/

In WebLogic Integration 9.2 it is upgraded to: 

@TaskCreate(name = "{name}", 
taskTypeId.path = "/Worklist/Compatibility 8.1.x",
taskTypeId.version = 9.0f,
taskTypeId.worklistHostApplicationId = "worklist-ejbs-81x"
)

Other useful references are:

 

Upgrading JCS Control Files

After the upgrade to WebLogic Integration 9.2, JCS control files are renamed with a .java extension. The JCS control files that contain WebLogic Integration control annotations are upgraded.

Table 3-2 provides information on upgrades to WebLogic Integration 8.1 to 9.2 JSC annotations.

Table 3-2 JCS Annotations
8.1 Annotation
Attribute
9.2 Annotation
Attribute
Comments
common:xmlns
 
XmlNamespaces.Entry
 
All annotations will be child node of XMLNamespace.
prefix
 
prefix
 
namespace
 
namespace
 
common:target-namespace
 
TargetNamespace
   
namespace
 
value
 
common:security
 
Security
 
All annotations will be child nodes of schemas.
roles-allowed
 
rolesAllowed
 
roles-referenced
 
rolesReferenced
 
run-as
 
runAs
 
run-as-principal
 
runAsPrincipal
 
single-principal
 
singlePrincipal
 
callback-roles-allowed
 
callbackRolesAllowed
 
jcs:jc-jar
 
<none>
 
Primarily used in WebLogic Workshop 8.1. It is no longer used in WebLogic Workshop for Platform 9.2.
common:schema
 
Schemas.Entry
 
All annotations will be child nodes of schemas.
file
 
file
 
inline
 
inline
 
common:message-buffer
 
MessageBuffer
   
enable
 
enable
 
retry-count
 
retryCount
 
retry-delay
 
retryDelay
 
editor-info:code-gen
     
Primarily used in WebLogic Workshop 8.1. It is no longer used in WebLogic Workshop for Platform 9.2.
jcs:control-tags
 
<none>
 
Primarily used in WebLogic Workshop 8.1. It is no longer used in WebLogic Workshop for Platform 9.2.
common:control
 
Control
 
The standard Beehive annotation.
common:operation
 
<none>
 
No longer needed, because Apache Beehive control framework handles it.
jcs:ide
 
<none>
 
Not handled as this annotation belong to WebLogic Workshop 8.1.x
jc:conversation
 
Conversation
 
This annotation is identical to jws:conversation annotation
phase
 
value
 
jcs:suppress-common-tags
 
<none>
 
Primarily used in WebLogic Workshop 8.1. It is no longer used in WebLogic Workshop for Platform 9.2.


  Back to Top       Previous  Next