Upgrade Guide
|
 |
 |
|
|
 |
 |
This section provides information on upgrading from WebLogic Integration 2.1 SP2 and WebLogic Integration 7.0 SP2 to WebLogic Integration 8.1 SP2.
Describes guidelines for upgrading from WebLogic Integration 2.1 SP2 and WebLogic Integration 7.0 SP2 to WebLogic Integration 8.1 SP2.
The following list provides important guidelines for upgrading from WebLogic Integration 2.1 SP2 and WebLogic Integration 7.0 SP2 to WebLogic Integration 8.1:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/workshop/guide/navDevGuide.html
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/workshop/guide/getstarted/navGettingStartedWorkshop.html
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/tutorial/tutWLIProcessIntro.html
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/dttutorial/tutWLIDataTransIntro.html
Note: More information on terminology changes is available in WebLogic Platform Terminology at the following URL:
http://download.oracle.com/docs/cd/E13196_01/platform/docs81/upgrade/intro.html
WebLogic Integration 8.1 includes several utilities and an Upgrade Wizard for helping you upgrade WebLogic Integration 2.1 SP2 and WebLogic Integration 7.0 SP2 applications. The following list briefly describes these utilities:
aiExport21.cmd)—Use to export application integration (AI) repository artifacts, such as Application Views, from WebLogic Integration 2.1 SP2. It is located in the BEA_HOME\weblogic81\integration\upgrade folder.aiimportexport.cmd or aiimportexport.sh)—Use to transform and import application integration (AI) repository artifacts from WebLogic Integration 2.1 SP2 and WebLogic Integration 7.0 SP2 into WebLogic Integration 8.1. It is located in the BEA_HOME\weblogic81\integration\bin folder.aiRepackageAdapter.cmd or aiRepackageAdapter.sh)—Use to upgrade any custom or third-party adapters. It is located in the BEA_HOME\weblogic81\integration\upgrade folder.upgradeTPM.cmd)—Use for upgrading Trading Partner Management (TPM) configuration data (not run-time state data) and its associated services and profiles. It is located in the BEA_HOME\weblogic81\integration\upgrade folder.Note: For a detailed list, see What the Wizard Upgrades.
The following features are not upgraded by the Upgrade Wizard or other utilities and need to be manually upgraded:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/wfguide/wfguideRosettaNet.html
WebLogic Integration 8.1 does not include Contivo Analyst. Instead BEA provides a more powerful XQuery mapping functionality as part of WebLogic Workshop. However, if you wish to continue using Contivo, WebLogic Integration 8.1 provides run-time support for XSLT transformations. Note that when upgrading using the Upgrade Wizard, existing XSLT transformation are not converted to the new functionality, but configured to run unchanged. You continue to maintain XSLT transformations using Contivo Analyst.
To learn more about the XQuery mapper functionality, see "Transforming Data Using XQuery" in the WebLogic Workshop Help at the following URL:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/dtguide/dtguideMapper.html
This section describes how to install the Upgrade utilities and Upgrade Wizard. It contains information on the following topics:
Before upgrading, you must first install the Upgrade utilities and Upgrade Wizard. These utilities are in the Upgrade JAR, which is available on the BEA dev2dev Web site at the following URL:
http://dev2dev.bea.com/resourcelibrary/utilitiestools/upgrade.jsp#wliupgrade
After downloading the JAR file, install the utilities with the following steps:
workshop-lib directory, then copy the migration.jar file to the BEA_HOME/weblogic81/workshop/lib directory.upgrade directory to the BEA_HOME/weblogic81/integration directory.The Upgrade Wizard and upgrade utilities are now available, as shown in Figure 5-1.
Figure 5-1 Upgrade Wizard is Available
If you plan to upgrade WebLogic Integration 2.1 SP2 Application Views, you need to edit the aiExport21.cmd file. Specifically, you need to set the correct path for calling the setEnv.cmd script in your WebLogic Integration 2.1 SP2 directory. After installing the Upgrade JAR, the aiExport21.cmd file is located in the following directory:
BEA_HOME\weblogic81\integration\upgrade
In the preceding line, BEA_HOME represents the WebLogic Platform 8.1 home directory.
For example to set the path for the default installation for WebLogic Integration 2.1 SP2, you would set the path as follows:
call C:\bea\wlintegration2.1\setEnv.cmd
The Upgrade JAR file contains the following directories and files:
META-INF directory—Contains the MANIFEST.MF file, which is automatically created for the JAR file. This file is not used for upgrading.upgrade directory—Contains the upgrade utilities and wizard. For a full description of the utilities, see What Is Upgraded by the Upgrade Utilities and Wizard.workshop-lib directory—Contains the migration.jar file. This file contains the Java classes that parse the workflows when upgrading WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 to WebLogic Integration 8.1.readme.txt—Contains instructions for installing the upgrade utilities and the Upgrade Wizard.
This section provides information about each of the steps listed in the Overview of Upgrade Process. Depending on your application, the steps you use may differ from this approach.
The following is a general upgrade strategy. Depending on your application, the steps you use may differ from this approach. Details of each step are described in the remainder of this document.
.jar) file. The JAR will include workflow, XML (Extensible Markup Language), XSLT (eXtensible Stylesheet Language), and MFL (Message Format Language) files. See Exporting Package File from WebLogic Integration BPM Studio. Use steps 4 and 5 only if you are using B2B integration.
Use steps 6, 7, and 8 only if you are using application integration.
Based on requirements, you can also do the following.
Before upgrading your WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 application, create a WebLogic Integration 8.1 process application for your upgrade, as described in How Do I: Create a New Application? in the WebLogic Workshop Help at the following URL:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/howdoI/howStartNewapp.html
In the Name field, specify a name for the application, then click Create, as shown in the following figure.
A business operation Enterprise Java Bean (EJB) encapsulates business logic. Business logic is the code that fulfills the purpose of the application, such as checking inventory or ordering a part.
You can use the same business operation EJBs that you created for WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 in WebLogic Integration 8.1. In WebLogic Integration 2.1 SP2 and WebLogic Integration 7.0 SP2, the Studio was used to enable workflows to use business operation EJBs. In WebLogic Integration 8.1, you use Java and EJB controls to utilize the business logic encapsulated in your business operation EJB. EJB controls make it easy for you to use an existing, deployed EJB from within an application.
To re-deploy your business operation EJB, do the following:
To learn about deploying EJBs, see Deployment in the WebLogic Server documentation at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/deployment.html
To learn about using Java Controls, see Working with Java Controls in the WebLogic Workshop Help at the following URL:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/workshop/guide/controls/navWorkingWithJavaControls.html
To learn about using EJB Controls, see Using Integration Controls in the WebLogic Workshop Help at the following URL:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/controls/controlsIntro.html
Before upgrading your WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 applications, you must first export your workflows and other application data to a JAR file.
Note: In some instances, it may be necessary to modify the original WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 workflows. To see if this applies to any of your workflows, see Upgrade Wizard Limitations.
To export your workflows, do the following:
.jar) file. The JAR file will include workflow, XML (Extensible Markup Language), XSLT (eXtensible Stylesheet Language), and MFL (Message Format Language) files.Note: To learn about exporting a workflow package in WebLogic Integration 2.1 SP2, see Importing and Exporting Workflow Packages in Using the WebLogic Integration Studio at the following URL:
http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/studio/ch11.htm
To learn about exporting a workflow package in WebLogic Integration 7.0 SP2, see Importing and Exporting Workflow Packages in Using the WebLogic Integration Studio at the following URL:
http://download.oracle.com/docs/cd/E13214_01/wli/docs70/studio/ch11.htm
If you are upgrading B2B integration components, go to Exporting Trading Partner Management Configuration Data.
If you are upgrading application integration components, go to Exporting Application Views and other AI Repository Artifacts.
This step applies only if you are upgrading B2B integration components.
Before you can upgrade your Trading Partner Management (TPM) configuration data and its associated services and profiles from WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2, you must first export this information to an XML file.
Note: If a value does not exist for the WLPI Template Name attribute in your B2B conversation-definition roles, you may enter one (if applicable) before upgrading. If this value is missing, the new TPM data will not include the business process or control service derived from the conversation-definition role.
To learn about conversation definitions in WebLogic Integration 2.1 SP2, see Configuring Conversation Definitions in Administering B2B Integration at the following URL:
http://download.oracle.com/docs/cd/E13214_01/wlintegration/v2_1/b2badmin/cfgtasks.htm#998395
To learn about conversation definitions in WebLogic Integration 7.0 SP2, see Configuring Conversation Definitions in Administering B2B Integration at the following URL:
http://download.oracle.com/docs/cd/E13214_01/wli/docs70/b2badmin/cfgtasks.htm#1003805
To export your TPM configuration data, do the following:
The WebLogic Integration 8.1 Trading Partner Management uses the keystore to manage trading partner's certificates. (Trading Partner Management holds only the entry of the certificate in the keystore). To learn about keystores, see WebLogic B2B Security Upgrade.
Note: If you are exporting repository information from a running system using the command-line Bulk Loader utility, you must use the -force option.
WebLogic Integration 2.1 SP2: To learn about exporting repository data from this version of WebLogic Integration, see the following documents:
WebLogic Integration 7.0 SP2: To learn about exporting repository information in this version of WebLogic Integration, see the following documents:
This step applies only if you are upgrading B2B integration components.
WebLogic Integration 8.1 provides a TPM upgrade utility for upgrading Trading Partner Management (TPM) configuration data and its associated services and profiles from WebLogic Integration 2.1 SP2 and WebLogic Integration 7.0 SP2.
Note: The TPM upgrade utility upgrades configuration data, not run-time state data.
The TPM upgrade utility upgrades the following:
trading-partner and its attributes, including: name, description, notes, type, email, phone, fax, and username.addressextended-property-setebxml-bindingtransport (under the <ebxml-binding> element)authentication (under the <transport> element)rosettaNet-bindingservice—For each conversation-definition where the business-protocol is either ebxml or rosettanet, there are two roles. For each role, two service elements are generated in the upgraded WebLogic Integration 8.1 repository XML file, one for the process-type service and the other for the control-type service.service-profileThe following information is not mapped by the TPM upgrade utility:
wlc/logic-plugin, wlc/business-protocol-definition—Replaced by B2B protocol data in WebLogic Integration 8.1.wlc/trading-partner/xpath-expression—Applied to XOCP which was deprecated in WebLogic Integration 7.0 SP2.wlc/conversation-definition/role/process-implementation—Does not apply in WebLogic Integration 8.1.update-count—Does not apply in WebLogic Integration 8.1.The TPM upgrade utility has the following limitations:
As mentioned in Exporting Trading Partner Management Configuration Data, if a value does not exist for the WLPI Template Name attribute in your B2B conversation-definition role, you may enter one (if applicable) before upgrading. If this value does not exist, you will receive the following warning:
<date and time> <Error> <Upgrade> <600001>
<Missing wlpi-templateattribute in the conversation-Definition/role
element. No workflow nor control service will be generated for this role.>
You can add this information after using the TPM upgrade utility with the WebLogic Integration Administration Console. To learn about importing, see "Trading Partner Management" in Managing WebLogic Integration Solutions at the following URL:
http://download.oracle.com/docs/cd/E13214_01/wli/docs85/manage/tpm.html
Before you can use the TPM upgrade utility, you must first export this information to an XML file as described in Exporting Trading Partner Management Configuration Data.
To upgrade your TPM data using the TPM upgrade utility, do the following:
BEA_HOME/weblogic81/integration/upgrade
Table 5-1 contains the command-line parameters for the upgradeTPM utility.
After the file is successfully transformed, the following message is displayed:
<date and time> <Info> <Upgrade> <600003> <Transformation Completed Successfully>
Transformation Completed Successfully
If the file is not successfully transformed, an error message is displayed.
Table 5-1 Command-Line Parameters for the upgradeTPM Utility
|
The directory path and name of the TPM XML file to be upgraded. |
|
|
The path name of the workflow that uses the ebXML control, such as Note: If you know the workflow path, enter this parameter; otherwise, leave it blank. After the TPM data is loaded, you can add this parameter in the WebLogic Integration Administration Console http://download.oracle.com/docs/cd/E13214_01/wli/docs85/manage/tpm.html |
|
|
The package name of the ebXML Control, such as Note: If you know the control package name, enter this parameter; otherwise, leave it blank. After the TPM data is loaded, you can add this parameter using the WebLogic Integration Administration Console http://download.oracle.com/docs/cd/E13214_01/wli/docs85/manage/tpm.html |
This step applies only if you are upgrading application integration (AI) components.
Different utilities are needed to export Application Views and other AI repository artifacts from WebLogic Integration 2.1 SP2 and WebLogic Integration 7.0 SP2 to JARs that can be imported into your WebLogic Integration 8.1 upgrade application. These utilities export Application Views, connection factories schemas, and namespaces into a single JAR file. After exporting, transfer the JAR file to your target environment for the WebLogic Integration 8.1 application.
Note: Upgrading Application Views should be done only if you are using corresponding adapters in WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 and WebLogic Integration 8.1 (for example, WebLogic Adapter for RDBMS 7.1 and WebLogic Adapter for RDBMS for WebLogic Integration 8.1).
Note: If you are exporting WebLogic Integration 2.1 SP2 repository artifacts, you must edit the aiExport21.cmd file to use the correct path for the setEnv.cmd, as described in Edit aiExport21. The aiExport21 utility is included in WebLogic Integration 8.1.
To export AI Repository Artifacts, do the following:
WebLogic Integration 2.1 SP2: BEA_HOME/weblogic81/integration/upgrade
WebLogic Integration 7.0 SP2: BEA_HOME/weblogic700/integration/bin
In the preceding paragraphs, BEA_HOME represents the WebLogic Platform home directory.
aiexport21 <WLS URL> <user name> <password> <file>
[-codepage=<#>][-dump=< <namespace> | <'Root'> ] [-append]
< [-export [object name]*] >
Table 5-2 contains the command-line parameters for the aiexport21 utility.
aiimportexport<WLS URL> <user name> <password> <file>
[-codepage=<#>][-dump=< <namespace> | <'Root'> ] [-append]
< [-export [object name]*] >
Table 5-2 contains the command-line parameters for the aiimportexport and aiexport21 utilities.
Table 5-2 Command-Line Parameters for the aiExport21 and aiimportexport Utilities
To import Application Views and other AI repository artifacts, go to Importing Application Views and Other AI Repository Artifacts.
This step applies only if your are upgrading application integration (AI) components.
WebLogic Integration 8.1 provides a aiRepackageAdapter utility for upgrading WebLogic Integration 2.1 SP2 and WebLogic Integration 7.0 SP2 custom and third-party adapters. Specifically, this utility converts adapter EARs (Enterprise Archive file) to WebLogic Integration 8.1 EARs.
Note: Note, do not use the aiRepackageAdapter utility for upgrading BEA Adapters. You should use BEA WebLogic 8.1 Adapters. To learn about BEA adapters, see BEA WebLogic Adapters 8.1 at the following URL:
http://download.oracle.com/docs/cd/E13207_01/wladapters/docs81/index.html
Differences exist between the structure of WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 EAR files and WebLogic Integration 8.1 EAR files. Previous WebLogic Integration EARs contained a design-time WAR (Web Application file), a run-time RAR (Resource Adapter Archive), and an event router WAR, while the WebLogic Integration 8.1 EAR contains only a design-time WAR and a run-time RAR.
The aiRepackageAdapter utility performs the following functions:
ResourceAdapter implementation class using the init-param information from the event router WAR's web.xml and the other overview information in the run-time RAR's ra.xml file. This ResourceAdapter implementation takes the place of the event router for accepting event subscriptions and delivering events, and also acts as a container for connection factories. web.xml and weblogic.xml to refer to the new JSPs. To repackage your adapters, do the following:
BEA_Home\weblogic81\integration\upgrade
In the preceding paragraphs, parent_dir represents the parent directory of the WebLogic Integration 7.0 SP2 EAR file.
aiRackageAdapter.cmd d:\weblogic700\integration\adapters\dbms\lib BEA_WLS_DBMS_ADK
The repackaged adapter is named <adapter name>_8.1.ear and located in the parent directory.
http://download.oracle.com/docs/cd/E13214_01/wli/docs85/deploy/index.html.
Note: When you deploy, the application name should be the name of the adapter without the _81.ear suffix. If the suffix is used, the adapter cannot be used by WebLogic Integration 8.1. For example, the application name of a supplier_8.1.ear is supplier. The module (file) name can remain the same.
This step applies only if you upgrading application integration (AI) components.
WebLogic Integration 8.1 provides an import-export utility for importing Application Views and other AI repository artifacts from a WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 AI repository. This utility can be executed from the command line, or incorporated into your code with the import-export API. The output of the utility is a JAR file.
Upgrading your WebLogic Integration 7.0 SP2 AI repository is required because the WebLogic Integration 8.1 AI repository is contained in the directory structure of the application's local file system, while the repository for WebLogic Integration 7.0 SP2 is contained in a Relational DataBase Management System (RDBMS) database. Moreover, objects stored in the WebLogic Integration 8.1 repository have changed, as shown in the following list:
Shared connection factories—When an Application View that uses a shared connection factory is imported into WebLogic Integration 8.1, it will have an invalid adapter instance reference. When you are ready to test and publish the upgraded Application View, you need to correct the invalid reference. To make the correction, do the following:
Note: To learn more about testing and publishing Application Views, see "Defining an Application View" in Using the Application Integration Design Console at the following URL:
http://download.oracle.com/docs/cd/E13214_01/wli/docs85/aiuser/1usrntr.html
Namespace mismatch—Application Views upgraded to WebLogic Integration 8.1 using the import-export utility will have a namespace added to the request and response schema. If an XmlObject is used in the upgraded business process, such as in an XPath function, the upgraded files will not contain the namespace information. Subsequently, the XPath function will not work properly because of the namespace mismatch. The DTF (Data Transfer Format) file generated by the Upgrade Wizard must be edited to contain the namespace information. The DTF file is located in the HOME_BEA/weblogic81/<Upgrade Project>/<Upgrade Project>Web/process folder.
In the preceding paragraph, BEA_HOME represents the WebLogic Platform home directory.
For example, if a WebLogic Integration 7.0 SP2 document contains the following:
<RowsAffected>1</RowsAffected>
in WebLogic Integration 8.1, it is upgraded to look like this:
<ns0:RowsAffected xmlns:ns0="wlai/DemoDBMS_CreateCustomer_response"> 1 </ns0:RowsAffected>
The XPath function that is generated by the import-export utility is:
/**
* Original xpath = "/RowsAffected/text()"
* @dtf:transform xquery="string( $xmlInput/self::RowsAffected/text())"
*
*/
abstract public String xpath_2(XmlObject xmlInput);
You must manually add the namespace information so that the XPath function can work properly, as indicated by the bold text:
/**
* Original xpath = "/RowsAffected/text()"
* @dtf:transform xquery="declare namespace string( $xmlInput/self::ns0:RowsAffected/text())"
ns0='wlai/DemoDBMS_CreateCustomer_response"
*
*/
abstract public String xpath_2(XmlObject xmlInput);
To upgrade AI repository artifacts using the WebLogic Integration 8.1 import-export utility, complete the following steps:
Note: Before upgrading your repository, you must have created an application in WebLogic Workshop, as described in Creating an Application For Upgrade. By default a new application contains a project named "Schemas". If your application does not have a Schemas project, you must create one using WLI System Schemas as the project type. The project determines the location of the repository. To learn about creating a Schemas project, see How Do I: Create a Schemas Project Folder in the WebLogic Workshop Help at the following URL:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/howdoI/howSchemasCreate.html
Note: Before you can use the import-export utility, you must first export this information to a JAR file as described in Exporting Application Views and other AI Repository Artifacts.
<adapter name>-eventProps.properties.<adapter name>-eventProps.properties. The event properties file represents the properties for an event connection that will be paired with a named connection factory in a newly generated adapter instance.
The event properties file is used to configure event delivery on the newly created adapter instance that wraps the existing WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 connection factory descriptors. This is only necessary when the generated adapter instance is used to support event delivery for Application Views that use events. If you do not specify the event properties file, and the Application Views that uses that connection factory has defined events, you will need to use the Application Integration Design Console to edit the event connection being used by the Application View to allow for event delivery on that Application View.
To learn more about specifying event properties, see "Defining an Application View" in Using the Application Integration Design Console at the following URL:
http://download.oracle.com/docs/cd/E13214_01/wli/docs85/aiuser/1usrntr.html
Note: You must complete this step before upgrading your workflows, as described in Upgrading Workflows.
To learn more about testing and publishing Application Views, see "Defining an Application View" in Using the Application Integration Design Console at the following URL:
http://download.oracle.com/docs/cd/E13214_01/wli/docs85/aiuser/1usrntr.html
The usage for importing with the import-export utility is:
Usage: aiimportexport <app name> <root dir> <file> <codepage>
-import [-publish]
[-eventProps=<connection factory name>,<properties file name>]*
aiimportexport UpgradeProcesses
c:bea\weblogic81\samples\integration\UpgradeProcesses
d:bea\weblogic81\integration\70exports\appvies.jar cp437
-import -publish
-eventProps=myFactory,myAdapter-eventProps.properties
In the proceeding command, myFactory is the connection factory name within the JAR exported from the WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 repository.
Note: This usage is specific to importing JAR files that have been exported from WebLogic Integration 2.1 and WebLogic Integration 7.0 SP2 applications. For full usage, see "Importing and Exporting Application Views" in the Using the Application Integration Design Console at the following URL:
http://download.oracle.com/docs/cd/E13214_01/wli/docs85/aisuer/imp_appx.html
The following table contains the command-line parameters for the import-export utility.
|
The name of the J2EE application that receives the artifacts from the WebLogic Integration 2.1 or 7.0SP2 JAR. |
|
|
The root directory of the AI repository within the WebLogic Integration 8.1 application. Note: You only need to specify the root directory of the application, not the location of the Schemas folder. |
|
|
The JAR file exported from the WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 application. |
|
|
The codepage used when writing to console. It ensures that characters are displayed correctly. The default is Cp437 (United States).Other valid values include: The value specified must match your console's codepage. Note: On Window systems the chcp command displays the console's codepage. |
|
|
Specifies that objects contained in the JAR should be imported into the repository. |
|
|
Used only with |
|
|
Used only with If needed, you may use multiple When creating the properties file for the You need not put the following properties in If the http://download.oracle.com/docs/cd/E13214_01/wli/docs85/aiuser/2usrdef.html |
|
|
The qualified name of the connection factory that is mapped to the properties file. Defines a mapping between the qualified connection factory name and a properties file. |
|
|
The name of the properties file to which the properties from the |
The following properties are typically found in a WebLogic Integration 7.0 SP2 EventRouter web.xml file. You can safely not include them in the event properties file.
eventGeneratorClassNameRootLogContextAdditionalLogContextLogConfigFileLogLevelMessageBundleBaseLanguageCodeCountryCodeYou can invoke the import-export utility directly from the API. The class name for the import-export API is com.bea.wlai.client.ImportExport. The following code provides an example for importing.
Listing 5-1 Sample Code for Importing
String exportFilename = "myExportFile.jar";
String appName = "MyApp";
String appRootDir = "d:\\apps\\MyApp";
boolean overwrite = true;
boolean publish = true;
List errors = new LinkedList(); // List of Exception objects
Map eventPropsMap = new HashMap();
// Add properties file names (String) as the values keyed by the
// qualified names of the connection factories the properties are
// to be used with. This list can be null if you don't want any
// mappings applied.
eventPropsMap.put("Folder1.AppView1_connectionFactory",
"d:/myFiles/propsFor_Folder1.AppView1_connectionFactory");
ImportExport ie = new ImportExport(new File(exportFilename));
try
{
ie.connect(appName, appRootDir);
ie.importNamespaceObjects(overwrite, publish, eventPropsMap, errors);
}
catch (Exception e)
{
System.err.println("Fatal errors encountered:\n");
e.printStackTrace();
return;
}
if (errors.size() > 0)
{
System.err.println("Non-fatal errors encountered:\n");
int pos = 1;
Iterator i = errors.iterator();
while (i.hasNext())
{
Exception e = (Exception) i.next();
System.err.println("Error " + pos + ": " + e);
e.printStackTrace(m_out);
pos++;
}
}
WebLogic Integration 8.1 provides an Upgrade Wizard for upgrading workflows and other application information developed in WebLogic Integration 2.1 SP2 and WebLogic Integration 7.0 SP2 to WebLogic Integration 8.1. This section contains the following topics:
The Upgrade Wizard automatically upgrades most workflows, including business process templates that use Data Integration (DI), Application Integration (AI) and B2B plug-ins. Basically, the wizard takes an exported JAR file from WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 that contains workflows, business operations definitions, event keys, and data integration MFL, XSL, and XML files and transforms them into a business process file (.jpd), control files (.jcx), and extracted DI files. The Upgrade Wizard provides success, warning, error, and failure messages about the upgrade process and records this information to a log file.
The Upgrade Wizard optimizes the upgraded business processes as much as possible. However, upgraded processes may not be as optimal as if they were created in WebLogic Integration 8.1. Additionally, some processes cannot be fully upgraded, especially if they are extremely complex or improperly designed. These processes may require manual upgrading or redesign.
To learn about developing business processes, see the Guide to Building Business Processes in the WebLogic Workshop Help at the following URL:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/wfguide/wfguideIntro.html
The following list provides an overview of what the Upgrade Wizard upgrades:
As previously mentioned, the Upgrade Wizard cannot upgrade some components of particular workflows. You will need to manually upgrade these parts. The following list contains information on the Upgrade Wizard limitation and references to documents that can help you re-develop these components.
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/controls/controlsEmailConfig.html
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/dtguide/dtguideNonXML.html
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/wfguide/wfguideIntro.html
HOME_BEA/weblogic81/<upgrade_project>/WEB-INF/classes folder or, for JAR files, the WEB-INF/lib folder, where BEA_HOME represents the WebLogic Platform home directory.
sleep() function after upgrading. Before using the Upgrade Wizard, you must first export the workflows you created in WebLogic Integration 2.1 SP2 or WebLogic Integration 7.0 SP2 as described in Exporting Package File from WebLogic Integration BPM Studio.
To upgrade your workflows, do the following:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/howdoI/howStartWorkshop.html
Note: If multiple workflow template definitions exist, you must choose which template definition you want to upgrade. The Upgrade Wizard allows only a single definition to be used for creating the JPD.
Figure 5-3 Upgrade Wizard - Step 1: Select Process
Messages indicating the status of the business process upgrade are displayed in the Upgrade Wizard. These messages indicate which steps in the upgrade process succeed and which steps fail; whether or not the JPD file is generated; the number or errors, warnings, and notices; and the type of errors, warnings, and notices, as shown in the following figure:
The Upgrade message field displays the results of the upgrade. The errors, warnings, failures, and notices are also recorded in the upgrade log. To learn more about using these messages, see Viewing the Upgrade Log.
A Design View of the generated business process is displayed and the upgraded workflows (now called business processes) are saved in the directory specified the Package Path field, as shown in the following figure.
Figure 5-6 Original Workflow and Upgraded Workflow
Note: Some nodes in business processes generated by the Upgrade Wizard may not display properly in the Design View. However, these parameters are visible in the source view.
The upgrade log helps you with upgrading workflows. You can use the upgrade log to identify the workflows and parts of workflows that could not be upgraded by the Upgrade Wizard. The messages in the log provide guidance for fixing, redeveloping, and optimizing the upgraded business processes. In general, they provide the following:
The following steps will help you use the upgrade log most effectively:
upgrade.log in the Application pane. The log is in the Project/ProjectWeb/processes folder.To learn about creating and modifying business processes, see Building Integration Applications in the WebLogic Workshop Help at the following URL:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/navIntegration.html
To learn about running and testing business processes, see Running and Testing Your Business Process at the following URL:
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/wfguide/wfguideTest.html
In WebLogic Integration 7.0 SP2, if you have code in the ADK DesignTimeRequestHandler that gets the ConnectionFactoryDescriptor from the Application View descriptor such as the following:
IconnectionFactoryDescriptor cfd = avd.getConnectionFactoryDescriptor();
This code will not work in WebLogic Integration 8.1 SP2 because connection factories are now part of the adapter instance.
You will need to replace the code to initialize cfd with the following:
IAdapterDescriptor svcAD = null;
IConnectionFactoryDescriptor cfd = null;
DesignTimeHelper dthelper = getDesignTimeHelper();
//get a reference to the Service Adapter Instance
IApplicationViewDescriptor.IAdapterInstance serviceAdapter =
avd.getAdapterInstance(avd.getServiceAdapterInstanceName());
// Get a reference to the Adapter Descriptor from the AppViewDescriptor
svcAD = dthelper.getAdapterDescriptor(avd,avd.getServiceAdapterInstanceName());
if (svcAD != null)
{
//get the ConnectionFactoryDescriptor using the design time helper
//method getConnectionFactoryDescriptor
Cfd = dthelper.getConnectionFactoryDescriptor(avd,
avd.getServiceConnectionFactoryName(),svcAD);
}
In some cases, messages may fail to be sent across a JMS bridge between clustered domains. This happens when each of the clustered domains contains different versions of WebLogic Server. For information about working around this problem, see "Upgrading from WebLogic Integration 8.1 to SP2" in the WebLogic Integration 8.1 SP3 Release Notes, which is available in PDF format in a ZIP file. Go to the "Download PDF Documentation for Previous Releases of WebLogic Integration 8.1" page, at http://download.oracle.com/docs/cd/E13214_01/wli/docs85/interm/prevreleases.html, then click "All WebLogic Integration 8.1 SP3 Documents."
|
|
|