![]() ![]() ![]() ![]() ![]() ![]() |
The following sections describe updates required to Business Processes and Control files before they can be used with WebLogic Integration 10g Release 3 (10.3). This chapter describes in detail the source changes that occur during Application upgrade from 8.1.x or 8.5.x to 10g Release 3 (10.3).
In the Oracle WebLogic Integration 10g Release 3 (10.3) 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 or 8.5.x, jpdContext
within a JPD used to be annotated with @common:context
. However, in WebLogic Integration 9.2 and higher, jpdContext
is upgraded to @com.bea.wli.jpd.Context()
.
For example, a WebLogic Integration 8.1.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 Oracle WebLogic Integration 10g Release 3 (10.3), the annotation is as follows:
@com.bea.wli.jpd.Process(
process="<process name=\"EchoAsync\">" +
" <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 Oracle WebLogic Integration timer control for JPDs. |
Note: | JMS transport was supported in WebLogic Integration 8.1 using jws.queue for use by Oracle Workshop for WebLogic based artifacts (such as business processes and JWS). In Oracle WebLogic Integration 10g Release 3 (10.3), JWS uses weblogic.wsee.DefaultQueue as the default queue for JMS transport whereas business processes still require jws.queue . Further, note that even though Oracle WebLogic Integration 10g Release 3 (10.3) 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 Oracle WebLogic Integration-enabled domain. Do not use jws.queue or customize the queue name (using jws.properties ) with JWS applications in Oracle WebLogic Integration 10g Release 3 (10.3). |
Table 3-1 provides WebLogic Integration JPD 8.1.x or 8.5.x to 10g Release 3 (10.3) JPD annotation upgrade information.
After the upgrade to Oracle WebLogic Integration 10g Release 3 (10.3):
.java
extension@ControlExtension
.For example, if a WebLogic Integration 8.1 JCX contains the following annotation:
In Oracle WebLogic Integration 10g Release 3 (10.3) it is upgraded to:
@TaskCreate(name = "{name}",
taskTypeId.path = "/Worklist/Compatibility 8.1.x",
taskTypeId.version = 10.0f,
taskTypeId.worklistHostApplicationId = "worklist-ejbs-81x"
)
After the upgrade to WebLogic Integration 10g Release 3 (10.3), 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 from WebLogic Integration 8.1 to 10g Release 3 (10.3) JSC annotations.
![]() ![]() ![]() |