![IBM E02HRLL-G - WebSphere Partner Gateway... Administration Manual Download Page 79](http://html1.mh-extra.com/html/ibm/e02hrll-g-websphere-partner-gateway/e02hrll-g-websphere-partner-gateway_administration-manual_3350282079.webp)
BCG and DIS Import
BCG migration utility also imports maps and routing objects. When the production
system has maps and routing objects imported through DIS tool, the BCG
migration utility will overwrite, if overwrite option is enabled. If you import the
run time environment (maps and routing objects) through DIS client, DIS import
must be performed after BCG Import, so that the target production system will
have the configuration required at run time.
Non-migratable configurations
The following configuration data are not migrated:
v
CPA
The Community Partner Agreement (CPA) is meant only for production system.
It does not exist on the test system.
v
Reports and logs are not migrated. They are not configuration items.
v
Also, EDI Map data and related information is not migrated.
Limitations of the migration utilities
v
If any error occurs during migration, the transactions are not rolled back. In case
of import, errors occur due to the following reasons:
–
The exported file is edited manually and the required information is
removed.
– The manually created import file does not have all the required information
for each object.
– The newly configurable item is created when the utility is executed.
– An existing configurable item is updated when the utility is executed
v
Only partner migrations and connections can be migrated selectively. All other
migrations must be migrated as a whole.
v
If an export is made from a source system that uses a different file system type
than the receiver system, the XML document contained in the exported output
requires manual updates to correct any file-system specific
<
targetURL
>
elements. These elements must be corrected to match the receiver file system
environment before the import is performed.
Forward proxy migration
Forward proxies are used by HTTP/S destinations, as a placeholder during the
import process. The production environment (receiver system) might not have the
same proxies as those of the test environment (source system). After the import,
the administrator might have to change the proxy related information to reflect
that of the production environment. If the test environment is same as that of
production environment, the administrator need not make changes.
Note:
The overwrite option is disabled for forward proxies. So if a forward proxy
exists on the receiver system, the import utility will not change it.
Chapter 6. Administering partner migration
73
Summary of Contents for E02HRLL-G - WebSphere Partner Gateway...
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...