Chapter 6. Administering partner migration
The configuration migration utility enables you to selectively export and import
WebSphere Partner Gateway configuration data. This differs from other
data-moving options like database backup and restore because data is selectively
extracted when it is exported with the utility and a database backup is not
normally selective. The configuration migration utility enables you to import
configuration without overwriting configuration that is already present on a
system, while database restoration from a backup typically overwrites existing
data.
The configuration migration utility exports selected partner and system definitions
into an XML file and a set of supporting files. You can subsequently import these
files into another system, moving the configuration across systems.
Note:
When transferring data from one system to another, both systems must use
the same version of WebSphere Partner Gateway.
The migration utility is used primarily to move configuration data from a
development and testing system to a production system, but you can also load
configuration data from an XML file that you create based on the XML schema
provided.
There are two options available for running the migration utility:
1.
A command line interface is provided so the migration utility can be started
using a script.
2.
An API is provided so user-written Java programs can invoke the migration
utility. See the
WebSphere Partner Gateway Programming Guide
for more
information about using the API.
The migration utility is implemented as a standalone Java application that calls
WebSphere Partner Gateway remotely. The utility is packaged in a .zip file named
BCGMigrationUtil.zip
. This file is installed by the hub installer in this directory:
hub installation
/console/support
.
Using the migration utility from the command line
About this task
Before you can use the migration utility, you must extract the
BCGMigrationUtil.zip
file on the workstation where you will run the utility. After
the utility files are extracted to your local file system, perform the following
prerequisite steps:
1.
The console component for the WebSphere Partner Gateway system that you
will export from or import into must be running. Note that the utility can be
run on a different workstation than where the console component is installed.
This is because the utility accesses the console using the IIOP (EJB) protocol
over a network. Connectivity between the workstations is required, and the
IIOP port (typically 58809) of the console has to be available from the
workstation where the utility runs.
2.
You must have Java 5 available on the workstation where the utility will run.
In your machine install JDK1.5.
© Copyright IBM Corp. 2007, 2008
61
Summary of Contents for E02HRLL-G - WebSphere Partner Gateway Express
Page 20: ...14 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 66: ...60 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 80: ...74 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 86: ...80 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 90: ...84 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 134: ...128 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 154: ...148 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 194: ...188 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 228: ...222 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 258: ...252 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 267: ......
Page 268: ... Printed in USA ...