Table of Contents
Advertisement
For a UNIX system, the invocation is similar, except you use bcgmigrate.sh instead
of bcgmigrate.bat. Once the import is completed, the logs are written to the file
BCGMigration.log. If the -r option is not specified for an import, then the output
will be placed in the directory configured in -f option. For a Windows system,
Once the import is completed, the logs are written to the file BCGMigration.log. If
the -r option is not specified for an import, then the output will be placed in the
directory configured in -f
Mapping of XML element with Console
The exported file or the file to be imported will be in XML format. The XML
elements may not depict the exact name on the console. The following table shows
the mapping between console screen and root elements in the XML file. The table
contains only the views and element names and not the individual fields on the
screen. If the element name is a link in the view, it is represented in italics.
Table 9. Map of XML element with Console
Element name in XML
EnveloperSchedulingInfo
TransportTypeInfo
DestinationTypeInfo
HandlerInfo
FixedWorkflowStepInfo
WorkflowInfo
EnvelopeProfileInfo
MapInfo
TransformMapInfo
FAMapInfo
Console view
Hub Admin > Hub Configuration > EDI >
Enveloper.
Hub Admin > Hub Configuration > Receivers >
Manage Transport Types and Account Admin >
Partner > Destinations > Manage Transport Types.
Account Admin > Partner > Destinations > create
destination . Operation Mode is represented by
DestinationTypeInfo.
Hub Admin > Hub Configuration > Handlers.
There are four more sub menus Action, Fixed
Workflow, Destination, and Receiver.
Hub Admin > Hub Configuration > Fixed
Workflow > Inbound and Hub Admin > Hub
Configuration > Fixed Workflow > Outbound.
Each step is represented as
FixedWorkflowStepInfo.
Hub Admin > Hub Configuration > Actions. Each
Action in the list page is represented as
WorkflowInfo
Hub Admin > Hub Configuration > EDI >
Envelope Profile. Each envelope profile in the list
page is represented by EnvelopeProfileInfo.
Hub Admin > Hub Configuration > Maps >
Validation Maps. Each map in the list page is
represented as MapInfo. There will be an inner tag
routingNameList. It represent the routing object
names to which the validation map is linked.
Hub Admin > Hub Configuration > Maps >
Transformation Maps. Each map in the list page is
represented as TransformMapInfo.
Hub Admin > Hub Configuration > Maps > FA
Maps. Each map in the list page is represented as
FAMapInfo. There will be an inner tag
routingNameList. It represents the routing object
names to which the FA map is linked.
Chapter 6. Administering partner migration
65
Advertisement
Table of Contents
