Invoking From The Command Line - IBM E02HRLL-G - WebSphere Partner Gateway Express Administration Manual

Administration guide

Table of Contents

a .zip file holding an XML file. The XML must conform to the XML schema

bcgMigrationExport.xsd located in migration utility root/schemas directory.

Note: Ensure that the dependency requirements between export types are met.

These dependencies are outlined further in the topic Migrating configuration type

dependencies.

4. If you are importing data, you must have data to import. The import file can be

produced by exporting data, or you can write your own that contains

definitions you want to load into a system. After exporting, the exported data

is contained in a .zip file. The .zip file includes an XML file that conforms to

the XML schema bcgMigrationImport.xsd located in migration utility

root/schemas directory. This XML file includes data that can be used by the

import code to re-create the configuration types you exported.

The .zip file also includes these files:

v The exported validation, transformation, and FA maps

v RoutingObjects.zip containing the internal representations of the exported

routing objects (packages, protocols, and document types).

Follow these steps to write your own import file:

v Create an XML file that conforms to bcgMigrationImport.xsd.

You must be sure that the dependency requirements between import types

are met. For more information regarding dependencies see, Configuration

type dependencies.

v If any maps or routing objects are described in the import XML, create a .zip

file with the XML file in the root directory for the .zip file.

The directories are as follows:

– The routing objects are in a file called RoutingObjects.zip within the

RoutingObjects directory in the root.

– The transformation maps are in the TransformationMaps directory in the

root.

– The validation maps are in the ValidationMaps directory in the root.

– The FA maps are in the FAMaps directory in the root.

Note: If you are importing any file directory receivers, the receiver system

cannot already have the file directory used by the receiver in its file system.

Be sure to delete any such directories before importing.

5. The migration utility has to log on to the console that you are using. The

WebSphere Partner Gateway user account must have permission to export or

import configurations. The hub administrator user has this permission. If you

want to use an account other than hub administrator or a user who is a

member of the Hubadmin group, you must enable the permission to use the

migration module for the user. By default this permission is disabled.