Migrating the integration channel

After you have installed the adapter and Ariba Buyer has been successfully migrated, you must perform a series of integration channel migration tasks. These tasks include:

  1. Running the adapter migration utility
  2. Migrating integration events
  3. Configuring the adapter and integration channel
  4. Generating metadata
  5. Creating object mappings

Running the migration utility

The adapter migration utility carries out several integration channel migration modifications in the following files:

Run the utility

To run the utility, execute this command from the <Ariba Buyer8 Server>\bin directory:

migrationHarness -tasklist <Ariba Buyer 8 Server dir>
 \channels\IBM\migration\WBIAABMigrationTaskList.xml
 

For example:

migrationHarness -tasklist 
 C:\Ariba\app\Buyer8\Server\channels\IBM\migration\WBIAABMigrationTaskList.xml
 

The actions performed by the migration utility are described below.

Create backups

The utility creates a backup of all the files that it deletes or modifies on the <Ariba Buyer 8 Server>\config directory. The backup is located at <Ariba Buyer 8 Server>\channels\IBM\migration\backups\backup<timestamp>.

Update the Parameters.table file

The utility performs these tasks on the Parameters.table file:

Update the LoadDB.txt file

The utility performs these tasks on the LoadDB.txt file:

Update the MessageConfiguration.table files

The utility performs these tasks on the MessageConfiguration.table files:

Table 24 summarizes the changes that the migration utility makes to the MessageConfiguration files.

Table 24. Values for Channel section of ERP integration events

Parameter tag Old value New value
Name MQSeries IBM
Operation Parameter tag did not exist Assigned the value of the Action parameter.
Verb Parameter tag did not exist If event is a data push, new value is Create.
If event is a data pull, new value is Retrieve.
If Subscribe, do not create parameter.
Timeout Parameter tag did not exist If event is an asynchronous data push,
set the value to the number of milliseconds to
wait before returning a timeout.

Changes to the MessageConfiguration.table files for Subscribe events

All Subscribe events should be defined in MessageConfiguration.table events at the Variant level. For example:

<Ariba Buyer 8 Server>\config\

variant\<Variantname>\IBM\MessageConfiguration.table.

For each Subscribe event, you will need to manually create a new channel parameter for EventSource and provide a value for the parameter (see the example below).

CostCenterSubscribe = {
     Channel = {
                 EventSource = "myPart1_CostCenterSubscribe"
     }
     LoggingName = CostCenter;
         TopicName = CostCenterSubscribe;
 };
 

For a detailed description of the EventSource parameter and its usage, refer to the Ariba Configuration Reference Guide.

Completing the Buyer migration tasks

Once the integration channel migration utility has successfully finished its tasks, run the migration harness using the migrationHarness command. Then complete the remaining Ariba Buyer migration tasks by issuing the command:

rr 27-29
 

Migrating integration events

The files that define integration events in Ariba Buyer 8.x differ from their counterparts in Ariba Buyer 7.x (see Table 25).

Table 25. Integration event definition files

Ariba Buyer version Integration events defined in...
Ariba Buyer 7.x
  • IntegrationEvents.table
  • IntegrationSchema.table

Ariba Buyer 8.x
  • MessageConfiguration.table
    There can be multiple tables per partition
    (one for each defined integration channel).
  • MessageDefinition.table
    There can be one table per variant.

The MessageDefinition.table files and MessageConfiguration.table files are created when you migrate Ariba Buyer from version 7.x to version 8.x (see "Migrating Ariba Buyer").

The MessageDefinition.table files are complete. However, the MessageConfiguration.table files still require some modification. These modifications include:

Each of these tasks is described below.

Transferring CSV events to the File Channel

In Ariba Buyer 7.x, the WAAB version of the adapter used a component called the CSVAdapter to load CSV file data. In Ariba Buyer 8.x, CSV file data is loaded exclusively by the Ariba Buyer File Channel adapter.

Hence, customizations made to the old IntegrationEvents.table file (see Table 25) are not automatically migrated to the new MessageConfiguration.table file. You need to:

  1. Re-apply the customizations to the MessageConfiguration.table files located in:

    <Ariba Buyer 8 dir>\config\variants\<variant name>\partitions\<partition name>\file\MessageConfiguration.table

  2. Remove all CSV event definitions located in:

    <Ariba Buyer 8 dir>\config\variants\<variant name>\partitions\<partition name>\IBM\MessageConfiguration.table

To ensure that all customizations are correctly applied, follow these steps.

  1. For each CSV event definition, compare the entries in:

    <Ariba Buyer 8 dir>\...\<partition name>\file\MessageConfiguration.table and

    <Ariba Buyer 8 dir>\...\<partition name>\file\IBMMessageConfiguration.table

  2. If there are no differences apart from those contained in the Channels sections, remove the entry from <partition name>\file\IBMMessageConfiguration.table.
  3. If there are any differences apart from those in the Channels section (such as filename and action), make the corresponding change in <partition name>\file\MessageConfiguration.table, and then remove the entry from <partition name>\file\IBMMessageConfiguration.table
  4. Once you have confirmed that all the modifications made in <partition name>\file\IBMMessageConfiguration.table have been transferred to <partition name>\file\MessageConfiguration.table, you may move <partition name>\file\IBMMessageConfiguration.table to a backup location, as this file is no longer required.
Note:
The WAAB action called LoadAndDelete is equivalent to the WebSphere Business Integration Adapter for Ariba Buyer operation "Load And Delete", and the action called UpdateAndDelete is equivalent to the operation "Update And Delete".

Converting CSV mappings to File Channel format

Ariba Buyer 8.x provides mappings for all out-of-the-box CSV integration events.

If the mapping file used by the WAAB CSVAdapter was not customized, you can proceed to the next section.

If mappings were changed or added to the mapping file used by the WAAB CSVAdapter, you must make the same changes and additions to the mapping file used by the Ariba Buyer File Channel.

For details on the format of the mapping file, IntegrationMappings.aml, refer to chapter 4 in the Ariba Buyer 8.x Customization Guide.

Configuring the adapter and integration channel

The WebSphere Business Integration Adapter for Ariba Buyer consists of two main components; the integration channel and the connector. Each component runs in its own process. The two processes communicate with each other via RMI (remote method invocation).

You need to set parameters in each component to configure this communication. For information on setting the parameters correctly, refer to "Configuring the adapter" and "Configuring the integration channel" in Chapter 2 of this guide.

Generating metadata

The WebSphere Business Integration Adapter for Ariba Buyer is metadata-driven. This means that the adapter can handle changes to the structure of the business objects that flow through it without the need for recoding and recompilation. The structure of a business object is stored as metadata.

The metadata must always match the business object structure exactly. Whenever a business object's structure is changed, new metadata must be generated for that business object.

To generate all the required metadata, follow these steps.

  1. From the <Ariba Buyer 8 Server>\bin directory, execute this command:
    initdb -reshapedb
     
    
  2. Start Ariba Buyer 8.x.
  3. Stop Ariba Buyer. 8.x

This procedure triggers Ariba Buyer to output metadata to the file system repository. The location of this repository is specified by the MetadataRepos parameter in Parameters.table.

You can verify that the metadata was generated by checking the MetadataRepos directory. The directory should contain a folder for each variant that in turn contains a file for each Ariba Buyer object defined in the variant, and it should also include a folder for each partition in the variant. This folder contains all the MessageConfiguration.table entries for the partition.

The next step is to create business object definitions from the metadata stored in the file system repository. For details, refer to Chapter 2, "Generating business object definitions" in this guide.

Creating object mappings

When you have created the business object definitions, you can use them to construct the object mappings in the broker. These object mappings replace the mappings currently being done by customer adapters or existing broker flows.

For details on creating collaborations for WebSphere InterChange Server, see WebSphere Business Integration Server: Collaboration Development Guide.

For details on creating MQ flows for WebSphere message brokers, see Implementing Adapters with WebSphere Message Brokers.

For details on creating MQ flows for WebSphere Application Server, see Implementing Adapters with WebSphere Application Server.

Copyright IBM Corp. 1997, 2003