This chapter contains information on how to upgrade the application source using the Import Wizard. It also gives an insight into the upgrade process. It contains the following sections:
This tutorial does not include validation of all the aspects of the sample application. It helps you upgrade the 8.1 application source and view it in the WebLogic Integration 9.2 environment.
Application Overview
This application used in this tutorial creates a business process that meets the following requirements:
Receives Request for Quote messages from clients
Starts the business process on receipt of the Request for Quote
Validates and processes the request
Sends the status of the Request for Quote to the client
Importing the Application Source
This section provides detailed step-by-step instructions on how to upgrade your WebLogic Integration 8.1 Service Pack 4 or 5 application source for use in the Workshop for WebLogic Platform 9.2 environment.
Start Workshop for WebLogic Platform by selecting Start All Programs BEA ProductsWorkshop for WebLogic Platform 9.2 from the Start menu. This will display the Workspace Launcher dialog box as shown in Figure 2-1.
Figure 2-1 Setting the Workspace for the Upgraded Application
Specify the desired location for the upgraded application in the Workspace field as shown in Figure 2-1. For this tutorial use the upgrade workspace, under the WebLogic Platform installation directory, as shown below:
$BEA_HOME\user_projects\w4WP_workspaces\upgrade
Note:
The $BEA_HOME used throughout this tutorial is F:\bea\platform92_for_Beta\ where WebLogic Platform 9.2 is installed.
Click OK to proceed, and the BEA Workshop for WebLogic Platform IDE is launched, as shown in Figure 2-2.
Figure 2-2 Workshop for WebLogic Platform (IDE)
Start the import procedure by selecting the FileImport... menu option. This will display the Import Source dialog box as shown in Figure 2-3.
Figure 2-3 Selecting the Application Source to be Imported
Select the Workshop 8.1 Application option as the application source type, as shown in Figure 2-3, and click Next to proceed. The Application Import dialog box appears as shown in Figure 2-4.
Figure 2-4 Selecting the Application to be Imported
Click Browse to navigate through the directory structure and select the sampleApp.work file that you created in 8.1 SP5. For more information, see Creating the Source 8.1 Application. As shown in Figure 2-4, the sampleApp.work file for this tutorial is located in:
After selecting the sample application from the 8.1 install, a list of projects in that application are displayed in the dialog box. You have the option of choosing the projects to import and upgrade by clicking on the check boxes adjacent to them. However, it is advisable to include all the projects, as most of them have inter-dependencies.
Click Next to proceed and the Upgrade preference selection dialog box is displayed, as shown in Figure 2-5.
Figure 2-5 Setting the Upgrade Preferences
You can configure your preference by selecting the various options displayed in the dialog box. These options are available under specific categories, as listed below, depending on their function.
General - You can set the error handling options and the kind of content you would like to record. Use the default value for both the properties as described in Table 2-1.
Table 2-1 Setting General Preferences
Property
Description
Error Handling
Determines how the errors are handled and the subsequent action you would like to implement. Error messages are always recorded in a log file, but your selection here determines how they are delivered to you. There are three options for this field, namely:
Log errors and continue upgrade (default option)
Log errors but abort upgrade
Display dialog on errors
Message Verbosity
Determines the type of messages that will be captured during the upgrade process. There are three types of messages that are captured: information, warning, and error. These three message types are reflected in the three options for this field, namely:
Include informational comments (default option) - All three message types
Include warning comments - Only warning and error type messages
Include error comments - Only error messages
NetUI Project Upgrader options - Selecting the Use WebLogic J2EE Shared Libraries option enables you to use the WebLogic J2EE shared libraries, without having to duplicate runtime .jar files across projects. You can ignore this option as it usually does not impact the WebLogic Integration applications. By default, this option is selected for upgrade.
Properties file upgrader options - The Delete copied resource bundle files from the web content folder option removes any unnecessary .properties files. If none of the JSP pages in the web content folder require .properties files, they can be deleted. You can ignore this option as it usually does not impact the WebLogic Integration applications. By default, this option is not selected for upgrade.
JPD Document Upgrader options - Select the Upgrade XQ2002 to XQ2004 option as it converts XQuery statements from XQuery 2002 draft version to XQuery 2004 draft version. This enables the JPD node editor to parse through the inline XQuery statements and convert them to 2004 version. By default, this option is not selected for upgrade.
Ensure you select the Upgrade XQ2002 to XQ2004 option.
JSP File Migrator options - When selected, the Replace BEA NetUI tags with Apache Beehive tags option will upgrade the WebLogic Integration 8.1 supported NetUI tags with Apache Beehive compatible NetUI tags. You can ignore this option as it usually does not impact the WebLogic Integration applications. By default, this option is not selected for upgrade.
Note:
You can convert projects or selective JSPs to use Apache Beehive compatible NetUI tags even after the upgrade exercise. However, all new projects created in 9.2 use the Apache Beehive compatible NetUI tags.
Click Next to proceed with the upgrade, and the Progress Information dialog box is displayed, as shown in Figure 2-6. At this step, the application being upgraded is assessed and a detailed list of upgrade tasks that need to be performed (and not performed) is generated.
Figure 2-6 Tracking Upgrade Progress
After completing the upgrade process, the Upgrade Preview dialog box is displayed, as shown in Figure 2-7. The preview dialog box provides a summary of changes that will be implemented during the upgrade task.
Figure 2-7 Preview of the Upgrade Actions
Click Finish when you are satisfied with the items listed for upgrade, and those that do not require to be upgraded. The Upgrade Preview dialog box is refreshed and displays the upgrade progress status at the bottom of the dialog box, as shown in Figure 2-8.
Figure 2-8 Upgrade Progress Indicator
After the upgrade is complete, Workshop builds the workspace for the application in the IDE. A log of the import process is displayed in the Problems pane at the bottom of the dialog box; while a log of the upgrade process is displayed in the Upgrade pane, as shown in Figure 2-9. You can customize the type of information that is displayed by making the appropriate changes in the Upgrade Preferences dialog box. For more information on the type of error messages to be displayed, see Figure 2-5.
Figure 2-9 Import and Upgrade Progress Log in the BEA Workshop for WebLogic Platform IDE
Note:
For the purpose of this tutorial, you can ignore the warning and information type error messages displayed in the Problems pane.
With this, you have successfully completed the process of importing the application into the 9.2 workspace. The following sections will help you validate the application in the 9.2 environment. The tasks include deploying and running the application in a WebLogic Integration domain.
Validating the Upgraded Application
This section describes the steps involved in validating the upgraded application in the 9.2 environment. The task involves deploying the application on the server, publishing it, and subsequently running the application with some test values.
Deploying and Publishing the Application
Perform the following tasks to deploy the application after a successful upgrade.
In the Package Explorer pane, navigate through the directory structure to view the sampleAppWebsrcrequestquoteRequestQuote.java file, as shown in Figure 2-10.
Figure 2-10 Selecting the RequestQuote.java File
Right-click the RequestQuote.java file and select Run As1 Run On Server menu option. The Run on Server dialog box appears, as shown in Figure 2-11.
Figure 2-11 Defining a New Server to Deploy the Application
Select the Manually define a new server check box and fill up the form as displayed in Figure 2-11.
Click Next to proceed. The Run On Server dialog box is refreshed with the Define a WebLogic Server page, as shown in Figure 2-12.
Figure 2-12 Defining a WebLogic Server
In following section, you will create a new WebLogic Integration domain in the WebLogic Server.
Creating a WebLogic Integration Domain Using the Configuration Wizard
Perform the following steps to setup the WebLogic Integration domain in order to deploy the sampleApp application.
Select the Click here to launch Configuration Wizard to create a new domain option in Run On Server dialog box, to start the BEA WebLogic Configuration Wizard. As shown in Figure 2-13.
Figure 2-13 Creating a New WebLogic Domain
Select the Create a new WebLogic domain option and click Next. This will display the Select Domain Source page.
Select the Workshop for WebLogic Platform and the WebLogic Integration options and click Next. This will display the Configure Administrator Username and Password page.
Enter weblogic in the User name, User password, and the Confirm user password fields, and click Next. This will display the Configure Server Start Mode and JDK page.
In the WebLogic Domain Startup Mode pane, select Development Mode. In the JDK Selection pane, select Sun SDK 1.5.0_04 @ F:\bea\platform92_for_Beta\jdk150_04 and click Next to proceed. This will display the Customize Environment and Service Settings page.
Select Yes and click Next to proceed. This will display the Configure the Administrator Server page. Click Next to proceed without making any changes.
Similarly, do not make any changes in subsequent Configure Managed Servers, Configure Machines, and Configure the JDBC Data Source pages. Just click Next and skip to the Run Database Scripts page, as shown in Figure 2-14.
Figure 2-14 Running Database Scripts
From the list of Available JDBC Data Sources, select the p13nDataSource option, as shown in Figure 2-14 and click Run Scripts. On successful execution, the Results pane will display Database Load Successful!.
Again, from the list of Available JDBC Data Sources, scroll down and select cgDataSource-nonXA and click Run Scripts again. On successful execution, the Results pane will display Database Load Successful!.
Click Next to proceed. This will display the Configure JMS File Stores page, do not make any changes and click Next to proceed. This will display the Review WebLogic Domain page, Figure 2-15, which summarizes the contents of the domain, and reflects the options you have selected.
Figure 2-15 Review the Domain Configuration Settings
Click Next to proceed without making any changes. This will display the Create WebLogic Domain page.
Provide a name in the Domain Name field, for example sample_wli_domain, and click Create. This will start the domain creation process and on successful creation, the Create Domain dialog box will appears as shown in Figure 2-16.
Figure 2-16 Successful Creation of a Domain
Click Done to conclude the Domain creation process. You now need to publish the application on the server with the domain you just created.
After creating the Domain using the Configuration Wizard, return to the Run On Server dialog box as shown in Figure 2-12.
Click Browse and navigate to the folder where the new WebLogic Integration Domain sample_wli_domain was created and select it. As shown in Figure 2-16, the new Domain location for this tutorial is:
Click Next on the Run On Server dialog box to display the Add and Remove Projects page. Ensure the sampleApp project is listed in the Configured projects column.
Click Finish to publish the Application. You can view the progress of the build and publish tasks in the Progress tab, as shown in Figure 2-17. This process may take some time if you are starting the server for the first time.
Figure 2-17 Deploy and Publish Status
After successfully deploying and publishing the Application, a browser pane is opened in the IDE, displaying the Overview tab of RequestQuote.jpd Process.
Click the Test Form tab in the browser pane, as shown in Figure 2-18.
Figure 2-18 Published Application Ready for Validation
The Application is now ready for the final validation process, running it. Details are provided in the following section.
Running the Application
This section describes the tasks that need to be performed to run the Application. This is the final step in validating the upgraded Application, and the 8.x to 9.2 upgrade procedure. The primary task of this section is to provide a set of test values to execute the Application, and to verify the results.
Locate the QuoteRequest.xml file that contains the test values required to validate the upgraded Application. The file is under the WebContent folder in the Package Explorer pane, as shown in Figure 2-19.
Figure 2-19 Locating the XML Document for Validation
Right click the QuoteRequest.xml file and select Open WithText Editor to display its contents in the IDE browser, as shown in Figure 2-20.
Figure 2-20 Test Values for Validation
Copy all the contents of the source file and close it.
Paste the contents in the xml requestXML field of the Test Form tab, as shown in Figure 2-21.
Another way to provide the test values is to click Browse in the Test Form tab of the browser pane, as shown in Figure 2-18. Subsequently, select the F:\bea\platform92_for_Beta\user_projects\w4WP_workspaces\upgrade\sampleAppWeb\WebContent\requestquote\testxml\QuoteRequest.xml file and click Open.
Figure 2-21 Providing the Test Values for Validation
Click quoteRequest to start the process. On successful completion of the process, the Test Form tab is refreshed as shown in Figure 2-22.
Figure 2-22 Successful Execution
You have now successfully imported, published, and validated an 8.1 Application in the 9.2 workspace.
Summarize the WebLogic Integration Upgrade Process
This section briefly summarizes the post-upgrade WebLogic Integration source artifacts.
The following source file types are renamed to have a .java file extension:
DTF: Data Transformation File
JPD: Java Process Definition file
JCS: Java control source file
JCX: Java control extensions file
The 8.1 XQuery files are updated with a comment indicating they belong to the XQuery version 2002. This helps differentiate the XQuery files as the 9.2 release uses the XQuery version 2004 as the default.
All controls, WebLogic Integration included, are converted to use Apache Beehive with a .java file extension.
The 8.1 channel files are moved to the 9.2 Utility projects, though they are not modified in any manner.
The upgraded application is adapted to the 9.2 workspace, with an additional project that is created during upgrade. This additional EAR project combines the other projects into a J2EE application.
All Programs 
