Migrating from WebLogic Collaborate 1.0/1.0.1

 

This section describes the processes required to migrate WebLogic Collaborate versions 1.0/1.0.1 to WebLogic Integration 2.1. It contains information on the following topics:

• Migration Process

• Before You Begin

• Migrating the Repository and Workflows

• Migrating Applications to the WebLogic Integration 2.1 Messaging API

 

---

Migration Process

The procedures in this section demonstrate that migrating WebLogic Collaborate 1.0/1.0.1 to WebLogic Integration 2.1 involves:

• Migrating the B2B repository from WebLogic Collaborate 1.0/1.0.1 to WebLogic Integration 2.1 format

• Migrating the necessary BPM-related entities like the security realm and workflows

• Migrating applications from the C-Enabler API of WebLogic Collaborate Releases 1.0/1.0.1 to the Messaging API of WebLogic Integration 2.1

Once WebLogic Collaborate has been migrated to WebLogic Integration 2.1, it will no longer exist as a single product; rather, it will become the Business-to-Business (or B2B) component of WebLogic Integration 2.1.

 

---

Before You Begin

Before attempting to migrate to WebLogic Integration 2.1, it is highly recommended that you back up the entire database and export all of your workflows. If migration fails due to an environmental error, you can fix the environment as necessary and remigrate. You can run the migration script as many times as necessary without causing any adverse affects.

 

---

Migrating the Repository and Workflows

WebLogic Integration 2.1 provides a utility to help you migrate repository data from a previous release of WebLogic Collaborate to the repository for WebLogic Integration 2.1. The Bulk Migrator utility converts a WebLogic Collaborate 1.0/1.0.1 repository data file to a WebLogic Integration 2.1 repository data file.

What Is Migrated?

In WebLogic Collaborate Releases 1.0/1.0.1, the configuration data is distributed among the following components:

• Repository for the c-hub

• Configuration files for the c-enablers

The following procedure for migrating repository data achieves only a partial migration; it migrates data from the c-hub repository. To modify and add data from the c-enabler configuration files and run-time data, you must use the WebLogic Integration B2B Console.

Repository Migration Procedure

To migrate repository data and workflows, use this procedure:

1. Use the Bulk Loader from WebLogic Collaborate 1.0/1.0.1 to export data from the old repository to a repository data file.

   Perform a full and long repository export. For instructions, see "Working with the Bulk Loader" in the BEA WebLogic Collaborate C-Hub Administration Guide in the documentation set for WebLogic Collaborate Release 1.0/1.0.1. You can find these documents at:

   http://download.oracle.com/docs/cd/E13208_01/wlcollab/v1_0/chubag/bulkload.htm

   or

   http://download.oracle.com/docs/cd/E13208_01/wlcollab/v1_0_1/chubag/bulkload.htm

   As an alternative to running the Bulk Loader, you can use the B2B Console to export the data. For instructions, see Configuring B2B Integration in the BEA WebLogic Integration B2B Console Online Help.

2. Start WebLogic Sever and log on to the WebLogic Integration Studio. Export all workflow templates in XML format. Note the organizations, users, template names, and business operations. This information will be required for step 10.

3. Drop the WebLogic Collaborate 1.0-based tables.

4. Install WebLogic Integration 2.1 as described in Installing BEA WebLogic Integration.

5. Run the createdb utility located in WLI_HOME/bin. Doing this creates the WebLogic Integration 2.1 database.

   Optionally, you can run createdb from the Start menu:

   1. Choose Start—>Programs—>BEA WebLogic E-Business Platform—>WebLogic Integration 2.1—>Configure.

      The BEA WebLogic Integration Database Configuration screen appears.

   2. Select Create Database and click Next.

      The Database Selection screen appears.

   3. Follow the procedures for creating a database described in "Using the Database Configuration Wizard" in Customizing WebLogic Integration in Starting, Stopping, and Customizing BEA WebLogic Integration.

6. Run the Bulk Migrator utility—located in the WLI_HOME\bin directory—by entering the following command:

   bulkmigrator.cmd prev_rep_data_file new_rep_data_file

   In this command:

   • prev_rep_data_file is the name of the repository data file that you created in step 1.

   • new_rep_data_file is the name of the new repository data file that will be created.

   The new repository data file includes a trading partner element for the old c-hub and for each trading partner that was configured in the old repository.

7. Set the end point values in the new repository data file.

   Each trading partner element in the new repository data file includes an end point value. The Bulk Migrator sets each end point value to <placeholder>. You must edit the new repository data file by setting each occurrence of <placeholder> to the correct end point value. The end point value specifies the trading partner end point. This end point is the URL for the trading partner.

   If you have access to a trading partner's c-enabler configuration file, you can get the URL from this file. The URL is the ref value for the enabler-url XML element. For information about the c-enabler configuration file, see "Configuring C-Enablers" in the BEA WebLogic Collaborate C-Enabler Administration Guide in the documentation set for WebLogic Collaborate Release 1.0/1.0.1. You can find this document at one of the following URLs:

   http://download.oracle.com/docs/cd/E13208_01/wlcollab/v1_0/cenbag/cfg.htm

   or

   http://download.oracle.com/docs/cd/E13208_01/wlcollab/v1_0_1/cenbag/cfg.htm

   The following table shows the relationships between the repository data elements for WebLogic Collaborate Releases 1.0/1.01 and the repository data elements for WebLogic Integration 2.1.

   Table 3-1 Relationships Between Repository Data Elements

   WebLogic Collaborate Releases 1.0/1.01	WebLogic Integration 2.1
   Business protocol	Transport and end point
   Business protocol definition	Business protocol definition
   C-hub	WebLogic Collaborate
   Collaborator	Collaboration agreement
   Conversation definition	Conversation definition
   C-space	Delivery channel
   Extended property set	Extended property set
   Logic plug-in	Logic plug-in
   Logic plug-in chain	Logic plug-in chain
   Role	Role
   Subscription	Party
   Trading partner	Trading partner
   Trading partner protocol	Party identifier
   XPath expression	XPath expression

8. Use the Bulk Loader in WLI_HOME/bin/ to import data from the new repository data file to the repository for WebLogic Integration 2.1.

   For instructions, see "Working with the Bulk Loader" in the BEA WebLogic Collaborate C-Hub Administration Guide in the documentation set for WebLogic Collaborate Release 1.0/1.0.1. You can find these documents at:

   http://download.oracle.com/docs/cd/E13208_01/wlcollab/v1_0/chubag/bulkload.htm

   or

   http://download.oracle.com/docs/cd/E13208_01/wlcollab/v1_0_1/chubag/bulkload.htm

   As an alternative to running the Bulk Loader, you can use the B2B Console to import the data. For instructions, see Configuring B2B Integration in the BEA WebLogic Integration B2B Console Online Help

Note: After you migrate a WebLogic Collaborate Release 1.0/1.01 c-hub, the old c-hub is displayed in the B2B Console for WebLogic Integration 2.1 as a trading partner named C-Hub.

1. Convert WebLogic Collaborate Release 1.0 workflows. Go to the directory in which the WebLogic Collaborate command scripts are located in: WLI_HOME/bin (UNIX) or WLI_HOME\bin (Windows NT). At the command prompt, enter the command appropriate for your platform:

   • If you are using Windows NT, enter:

     PIMigrator.cmd workflow-1.0.xml workflow-2.0.xml

   • If you are using UNIX, enter:

     ../PIMigrator.sh workflow-1.0.xml workflow-2.0.xml

   In the preceding command lines:

   • workflow-1.0.xml represents the full pathname of the workflow created with WebLogic Collaborate Version 1.0. workflow-1.0.xml was generated in step 2.

   • workflow-2.0.xml represents the full pathname of the workflow converted for use with WebLogic Integration 2.1.

2. Recreate organizations, users, templates, and business operations from the information saved in step 2.

3. Start WebLogic Server and log on to WebLogic Studio. From there, import the files generated in step 9.

 

---

Migrating Applications to the WebLogic Integration 2.1 Messaging API

The WebLogic Integration Messaging API has been updated in 2.1 to correctly reflect the new concepts and terminology of the B2B component of WebLogic Integration architecture. The 1.0/1.0.1 C-Enabler API is deprecated but still supported. It is recommended that you use the new Messaging API for Java applications. Please refer to Programming Messaging Applications for B2B Integration and the WebLogic Integration 2.1 Javadoc for details about the new messaging API.

The following sections describe how to migrate applications from the C-Enabler API (for WebLogic Collaborate Releases 1.0 /1.0.1) to the still-supported C-Enabler API (for WebLogic Integration 2.1). This section includes information on the following subjects:

• Introduction

• Importing XOCP Applications

• Updating the Terminology

• Supporting the WebLogic Collaborate 1.0/1.0.1 C-Enabler API

• WebLogic Collaborate 1.0/1.0.1 C-Enabler API Implementation

Introduction

Note: If you are migrating a Java messaging application that was written using the WebLogic Collaborate C-Enabler API to WebLogic Integration 2.1, the migrated application must be run in a separate JVM in nonpersistent mode.

XOCP is the default protocol used by WebLogic Integration for exchanging business messages. In WebLogic Collaborate Releases 1.0 /1.0.1, XOCP messaging applications were written using the public XOCP C-Enabler application program interface (API). A message was packaged in an XOCP message envelope and associated with various message headers that specified how to deliver and process the message. In WebLogic Integration 2.1, the c-enabler and c-hub entities have been integrated. The integrated product is known simply as B2B integration component of WebLogic Integration.

The WebLogic Integration Messaging API now supports the C-Enabler functionality, but continues to reflect the C-Enabler API run-time terminology so that XOCP applications developed using previous versions of the software will continue to work without additional customization.

The WebLogic Integration Studio gives developers a seamless, reliable method of defining and managing the messaging protocols used during WebLogic Integration business message exchanges. As a result, programming requirements can be reduced considerably. However, the WebLogic Integration Messaging API is provided for developers who want to maintain their installations using a Java program as the interface. See Programming Messaging Applications for B2B Integration.

WebLogic Integration uses the XOCP protocol to manage distributed business processes that are being passed back and forth in conversations between trading partners. When appropriately configured, a WebLogic Integration installation verifies business roles and security, providing a central management point for the collaborative conversations that are taking place.

When a business process initiates a specific task (for example, issuing a request for a quote), a central management point is created for the collaborative conversations between the trading partners, and business roles and security are verified before a message exchange takes place.

Importing XOCP Applications

The WebLogic Collaborate C-Enabler API does not support the new functionality available in WebLogic Integration 2.1; however, the C-Enabler terminology has been mapped to WebLogic Integration 2.1 functions, and XOCP functions continue to be available from the WebLogic Integration Messaging API. For a complete terminology mapping, see Table 3-2.

The WebLogic Integration Messaging API updates the C-Enabler API primarily in the following areas:

• C-enabler configuration

• Conversation management

• JavaDoc

XOCP applications that are being migrated to WebLogic Integration 2.1 must have:

• Database support

• All collaboration agreements defined in the repository

Updating the Terminology

Understanding the new terminology used in WebLogic Integration 2.1 is important when mapping the functionality in WebLogic Collaborate Releases 1.0 /1.0.1 XOCP applications for migration purposes. The configuration characteristics of your WebLogic Integration installation will determine whether functionality previously associated with the c-enabler or the c-hub is invoked. Table 3-2 summarizes how the functionality is mapped.

Table 3-2 Terminology Mappings from WebLogic Collaborate 1.0/1.0.1 to WebLogic Integration 2.1

 

Collaborate 1.0/1.0.1 Term	WebLogic Integration 2.1 Term	Definition
Attachment	Attachment	Non XML payload part of a business message; for example, a GIF file.
Business Document	Business Document	XML-based payload part of the business message.
Business Message	Business Message	A multi part MIME message, consisting of one or more payload parts. A part can be an XML document (a business document) or non XML file (an attachment).
Business Protocol Definition	Business Protocol Definition	The definition of a business transaction protocol, for example, Name=XOCP.
Collaborator	Trading Partner Session	In WebLogic Collaborate Releases 1.0/1.0.1, a collaborator is a trading partner that participates in a single c-space (delivery channel). In WebLogic Integration 2.1, a trading partner session is created to communicate with each trading partner, and its scope is bounded by a delivery channel.
Conversation	Conversation	A series of message exchanges between trading partners.
Conversation Definition	Conversation Definition	A set of roles and document definitions, for example, a purchase order.
Conversation Type	Not applicable	There is no corresponding term for conversation type in WebLogic Integration 2.1. In WebLogic Collaborate Releases 1.0 /1.0.1, conversation type defined a conversation for a trading partner. It consisted of the following properties: Conversation name (for example, purchase order) Version Role of a trading partner in that conversation (for example, buyer or seller)
C-Space	Delivery Channel	A grouping of Trading Partner, Subscription, and Business Protocol.
C-enabler Node	Spoke	A trading partner communicates with others with the help of a hub (intermediary).
C-enabler API	WebLogic Integration Messaging API	XOCP applications that used the C-enabler API can be migrated to use the WebLogic Integration Messaging API. The C-enabler API was the interface between the XOCP application and WebLogic Collaborate at run time. This API was used, for example, to start c-enabler sessions, create and participate in conversations, and send and receive business messages.
C-enabler Session	Trading Partner Session	In WebLogic Collaborate Releases 1.0 /1.0.1, a c-enabler session is a logical session between a c-enabler node and one c-hub for one particular c-space. In WebLogic Integration 2.1, a trading partner session occurs in the delivery channel.
C-hub	Intermediary	A hub is a WebLogic Server running a set of shared services. For example: Repository Administration Conversation coordination, message routing, and mediation
Message	Message	A data entity that is used to communicate between hubs and spokes. It is a multi part MIME message.
Role	Role	Each conversation has two or more roles, for example, buyer and seller. A role is defined in terms of the documents that can be sent or received by a collaborator who has assumed that role in the conversation.
Send(Publish)-Side filter	Send(Publish)-Side filter	When sending a document, this filter (X-Path) is specified by an application to determine the list of recipient trading partners. For example: //trading partner[@name= "Bea"
Trading Partner	Trading Partner	A representation of an entity, such as a company, that wants to participate in one or more delivery channels.

Supporting the WebLogic Collaborate 1.0/1.0.1 C-Enabler API

In WebLogic Integration 2.1, the configuration of a trading partner is predefined and entered in the system using the B2B Console. The trading partner retrieves a collaboration agreement from the WebLogic Integration repository.

To support migration to WebLogic Integration 2.1, a WebLogic Collaborate 1.0/1.0.1 C-Enabler application must have existing database support, and all of its trading partner collaboration agreements must be predefined in the repository. In order to collaborate in business transactions using the XOCP protocol, the application must be aligned with the WebLogic Integration Messaging API to achieve as much backward compatibility as possible. Changes are required in the following areas in order for the existing XOCP applications to migrate to the WebLogic Integration Messaging API:

• C-Enabler Configuration

• Repository

C-Enabler Configuration

In WebLogic Collaborate Releases 1.0 /1.0.1, the c-enabler configuration is retrieved from an XML file that defines the following variables:

• session name

• c-space name—Name of the intermediary delivery channel in the collaboration agreement.

• hub-url—One or more endpoint URLs of the intermediary delivery channel

• enabler-url—One or more endpoint URLs of the spoke delivery channel

• security-info—Security information in the document exchange elements of the delivery channels of both the spoke and the intermediary

  • trading partner name

  • certificate

  • role

Then the c-enabler creates (or participates in) and manages the conversations with other trading partners.

In WebLogic Integration 2.1, the identification and configuration of a trading partner is predefined and entered in the system using the B2B Console. The trading partner retrieves its collaboration agreement from the WebLogic Integration repository.

Repository

Existing XOCP applications will work with the WebLogic Integration 2.1 repository with only one change: WebLogic Integration must have a repository, and all the trading partner collaboration agreements used by the XOCP applications must be predefined in the repository. To migrate WebLogic Collaborate Release 1.0/1.0.1 data repository to WebLogic Integration 2.1, use the Bulk Migrator utility described in Migrating the Repository and Workflows.

WebLogic Collaborate 1.0/1.0.1 C-Enabler API Implementation

This section lists the WebLogic Collaborate Releases 1.0/1.0.1 public API packages, interfaces, and classes that must be reintegrated in the WebLogic Integration 2.1 run-time implementation in order to migrate XOCP applications.

Packages

• com.bea.b2bcom.bea.b2b.enabler

• com.bea.b2b.enabler.xocp

• com.bea.b2b.protocol

• com.bea.b2b.protocol.conversation

• com.bea.b2b.protocol.messaging

• com.bea.b2b.protocol.xocp.conversation.local

• com.bea.b2b.protocol.xocp.messaging

Interfaces

• com.bea.b2b.EnablerSession

• com.bea.b2b.enabler.xocp.XOCPEnablerSession

• com.bea.b2b.protocol.PlugIn

• com.bea.b2b.protocol.conversation.State

• com.bea.b2b.protocol.messaging.Message

• com.bea.b2b.protocol.messaging.PayloadPart

• com.bea.b2b.protocol.xocp.conversation.local.Conversation

• com.bea.b2b.protocol.xocp.conversation.local.ConversationHandler

Classes

• com.bea.b2b.enabler.Enabler

• com.bea.b2b.protocol.conversation.ConversationType

• com.bea.b2b.protocol.messaging.Attachment

• com.bea.b2b.protocol.messaging.BusinessDocument

• com.bea.b2b.protocol.messaging.DeliveryStatus

• com.bea.b2b.protocol.messaging.MessageBase

• com.bea.b2b.protocol.messaging.MessageEnvelope

• com.bea.b2b.protocol.messaging.MessageToken

• com.bea.b2b.protocol.messaging.MiniParser

• com.bea.b2b.protocol.xocp.messaging.Ping

• com.bea.b2b.protocol.xocp.messaging.QualityOfService

• com.bea.b2b.protocol.xocp.messaging.XOCPMessage

• com.bea.b2b.protocol.xocp.messaging.XOCPMessageToken