IBM E02HRLL-G Administration Guide - Page 75

Considerations when creating your own import data If you decide to create your own import file or to edit an import file that was created by the export utility, there are several things that you must consider. Not only does your XML file need to conform to the XML schema for an import file, but there are rules about the content of the file that are not controlled by the schema. Manual validation of the import file If you invoke your migration utility from the command line using the partner migration script, your data is not validated as it is not using the console. For instance, it is possible to create an incorrect partner ID using a migration script whereas this is not possible using the console. Data entered into the console is validated by the console. For example, you may enter a DUNS ID containing alphabetic characters from the command line, but this is not possible from the console because a DUNS ID must contain numeric characters only. Remember: It is important to manually validate all of your data before you enter it from the command line. Migration configuration type dependencies Configurable items can be broadly classified into three sections based on dependencies, namely Independent Items, First level dependent items, and Complex dependent items. Some configuration types have no dependencies. For example, a partner definition can be created without referring to any other configured entity in the system. Independent items are the configurable items that do not have any dependency before importing them into the target system. Other configuration types cannot exist by themselves because they depend on other entities in the system. For example, a destination is associated with a partner, so it cannot exist unless the partner also exists. To ensure that dependency items are always available, the content and ordering of the items in export and import files are important. When an export is performed, any item that has dependencies must be exported after any dependency items. The XML file reflects this ordering. Using the same logic, when the import is performed, the dependency items are imported before the dependent items. If you selectively export configuration types, you must ensure that you specify dependency types for all dependent types. It is also important if you create an import file using the schema definition. The schema enforces the ordering, but not the content. So if you define an import file incorrectly, for example, you forget to provide a dependency item or incorrectly defining a dependency item, that item will fail when you attempt an import of it. Independent configuration items The following configurable types are independent. Other configuration types depend on these items, but these items do not directly depend on other system items. v Enveloper Scheduling v Event codes v Transport types v Destination types v Envelope profiles v Connection Profiles Chapter 6. Administering partner migration 69