After you have installed the adapter and Ariba Buyer has been successfully migrated, you must perform a series of post-migration tasks. These tasks include:
The adapter migration utility carries out several post-migration modifications that are required by the <Ariba Buyer 8 Server>\config\Parameters.table file, the <Ariba Buyer 8 Server>\config\LoadDB.txt file, and the <Ariba Buyer 8 Server>\...\<partitionName>\IBM\MessageConfiguration.table files.
Run the utility
To run the utility, execute this command from the <Ariba Buyer8 Server>\bin directory:
harness -previous <Ariba Buyer 7.x CoreServer dir> -tasklist <Ariba Buyer 8 Server dir>\channels\IBM\migration\WBIAABMigrationTaskList.xml
For example:
harness -previous C:\Ariba\Buyer7\CoreServer -tasklist C:\Ariba\app\Buyer8\Server\channels\IBM\migration\WBIAABMigrationTaskList.xml
The migration 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>.
Changes to the Parameters.table file
The utility performs these tasks on the Parameters.table file:
Changes to the LoadDB.txt file
The utility performs these tasks on the LoadDB.txt file:
Changes to the MessageConfiguration.table files
The utility performs these tasks on the MessageConfiguration.table files:
Table 29 summarizes the changes that the migration utility makes to the MessageConfiguration files.
Table 29. 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.
The files that define integration events in Ariba Buyer 8.x differ
from their counterparts in Ariba Buyer 7.x (see Table 30).
Table 30. Integration event definition files
Ariba Buyer version | Integration events defined in... |
---|---|
Ariba Buyer 7.x |
|
Ariba Buyer 8.x |
|
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.
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 30) are not automatically migrated to the new MessageConfiguration.table file. You need to:
<Ariba Buyer 8 dir>\config\variants\<variant name>\partitions\<partition name>\file\MessageConfiguration.table
<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.
<Ariba Buyer 8 dir>\...\<partition name>\file\MessageConfiguration.table and
<Ariba Buyer 8 dir>\...\<partition name>\file\IBMMessageConfiguration.table
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.
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.
The WebSphere Business Integration Adapter for Ariba Buyer is meta-data-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 meta-data.
The meta-data must always match the business object structure exactly. Whenever a business object's structure is changed, new meta-data must be generated for that business object.
To generate all the required meta-data, follow these steps.
initdb -reshapedb
This procedure triggers Ariba Buyer to output meta-data to the file system repository. The location of this repository is specified by the MetadataRepos parameter in Parameters.table.
You can verify that the meta-data 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 meta-data stored in the file system repository. For details, refer to Chapter 2, "Generating business object definitions" in this guide.
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 version 4.2.
For details on creating MQ flows for WebSphere MQ Integrator Broker, see Implementing Adapters with WebSphere MQ Integrator Broker.
For details on creating MQ flows for WebSphere Application Server, seeImplementing Adapters with WebSphere Application Server.