Trading Networks Asset Dependencies
Some assets require other assets. For example, profiles use assets such as partner groups and contact types, and document types use assets such as document attributes. For assets you migrate to work properly, these required assets must also exist on the target system.
In My webMethods, when you select an asset for export, My webMethods shows dependencies on other assets and you can choose to include those required assets in the export. When you select an asset for import, however, My webMethods shows some, but not all, of the dependencies.
If you use the command line utilities or the built-in services to migrate, you must manage asset dependencies yourself.
The table below lists all possible dependencies an asset might have. When the table instructs you to migrate an asset, see below for instructions. When the table instructs you to create an asset, see the appropriate chapter in this guide for instructions. You must use the exact same name on the target system as the source system, with the same upper and lower casing.
If you migrate... | Do this to the target system... |
Partner profile |  Migrate extended profile field definitions Migrate any custom external ID types, custom contact types, and partner groups. Migrate any public queues. Create any custom immediate delivery methods. |
Queues | Move any custom immediate and scheduled delivery services. |
Extended field definition | Migrate any custom profile field groups. The standard groups are Corporation, Address, Contact, Delivery, External ID, Custom, and EDINT (if this is installed). All groups other than these are custom groups. To know the custom groups, execute the getFieldGroups service in the wm.tn.dictionary package. Standard groups need not be migrated because they would be available in the target system. |
Document type | Migrate any custom document attributes. Move any custom services for document attribute transformation. Move any custom service for the Check for Duplicate Document pre-processing action. |
Processing rule | Move any custom services for the Check for Duplicate Document pre-processing action and the Execute a Service processing action. For the Deliver Document By action: Create any custom immediate delivery method. Migrate any services for the custom immediate delivery method and then use the wm.tn.delivery:registerService service to register the corresponding immediate delivery service using the same immediate delivery method name. Manually create queues or use the tnexport and tnimport utilities to export all public queues. Move any scheduled delivery services. Migrate partner profiles for senders and receivers used as matching criteria. Migrate document types specified as matching criteria. Migrate any custom document attributes used as extended matching criteria. |
TPA | Migrate partner profiles for the sender and receiver associated with the TPA. Move any initialization, validation, and export services. Migrate the IS document type that defines the application-specific TPA data. |
Data permissions | Migrate partner profiles, document types, and processing rules that are part of data set definitions. Migrate My webMethods roles that have permission to act on data sets. Note: | These roles are defined in the My webMethods Server database, not the Trading Networks database, so you cannot migrate them using the tnexport and tnimport command line utilities. Make sure that the target system uses the same My webMethods Server. |
Grant data permissions to act on a data set to at least one My webMethods role. |
General functional permissions | Migrate My webMethods roles that have permission to functions. See the note for Data permissions. |
Archive schedule | Migrate any partner profiles for the sender and receiver used as selection criteria for archive or deletion. Migrate any document type used as selection criteria for archive or deletion. |
If you do not export the required partner profiles and document types for data permissions, Trading Networks throws a warning when you import that says the required assets do not exist in the target system. It then continues to import the other assets.
If the export file contains the required/dependent assets for any asset, tnimport will ensure that the required assets get migrated first so that no error is thrown.
When importing document types, Trading Networks determines whether the required document attributes exist on the target system with the same name. If they do not, Trading Networks throws an error and does not import the document type.
When importing processing rules, Trading Networks determines whether the required senders, receivers, and document types exist on the target system with the same name. If they do not, Trading Networks throws an error and does not import the processing rule.
When importing partner profiles, if any of the required assets are not defined, Trading Networks throws an error and does not import the profile. For example, if the contact type is not already defined in the target system before you import a contact of that type, Trading Networks throws an error and does not import that profile.
When importing TPAs, if the associated senders and receivers do not exist in the target system with the same name, Trading Networks throws an error and does not import the TPA.
