wm.tn.admin:importData
Imports data into the Trading Networks database.
Input Parameters
force | String If the keys in the data variable match the keys in the database, this variable indicates whether the rows in the database should be overwritten. Valid values are: true - Overwrite rows in the database if the keys from the data variable match. false - Do not overwrite rows in the database if the keys from the data variable match. |
overwriteRules | String (optional) Indicates whether the ProcessingRules from the supplied data should replace the list of ProcessingRules in the database. Valid values are: true - Replace all the ProcessingRules in the database with those in data. false - Default. Append the ProcessingRules in data to the rules in the database. |
data | Document The data to import into the Trading Networks database. The document contains the following keys: version Document Version information from the Trading Networks database. The document has the following keys. major String The major Trading Networks release number. minor String The minor Trading Networks release number. force String If the values for major or minor differ from the major and minor version in the database. Force indicates whether to overwrite the version information in the database. Valid values are: true - Overwrite version false - Do not overwrite version |
| attribs Document (optional) A set of attributes to import. For each attribute, the key is the attributeId in a string and the value is a com.wm.app.tn.doc.BizDocAttribute. types Document (optional) A set of TN document types to import. For each type, the key is the bizdocTypeId in a string and the value is a com.wm.app.tn.doc.BizDocType. |
| rules Object (optional) A set of processing rules to import. Specify a com.wm.app.tn.route.RoutingRuleList for rules. This is the complete set of processing rules for Trading Networks. If you set overwriteRules to false and the database already has processing rules, this service does not import the data specified in rules. fldgrps Document (optional) A set of field groups. For each field group, the key is the group description in a string and the value is the group code in a short. |
| flddefs Object (optional) A java.util.Vector. This is a set of profile field definitions to import. Each field definition is a com.wm.app.tn.profile.ProfileFieldMetaData. profiles Object (optional) A java.util.Vector. This is a set of partner profiles to import. Each profile is a com.wm.app.tn.profile.Profile. idTypes Document (optional) A set of ID types. For each ID type, the key is the type description in a string and the value is the type code in an integer. contactTypes Document (optional) A set of contact types. For each contact type, the key is the type description in a string and the value is the type code in an integer. binaryTypes Document (optional) A set of binary types to import. For each binary type, the key is the type description in a string and the value is the type code in an integer. tpas Object (optional) A java.util.Vector. This is a set of trading partner agreements to import. Each trading partner agreement is a com.wm.app.tn.tpa.TPA. |
| extflds Object (optional) A java.util.Vector. This is a set of extended fields to import. profileGroups Object (optional) A java.util.Vector. This is a set of partner profile groups. securityData Object (optional) A java.util.Vector. This is security data set. |
Output Parameters
errors | Document Exceptions that occur while importing the contents of data are returned in errors. The document contains the keys: attribs Document (optional) Exceptions with importing document attributes. For each exception, the key is the attributeId and the value is an IS document (IData object). types Document (optional) Exceptions with importing TN document attributes. For each exception, the key is the bizdocTypeId and the value is an IS document (IData object). Note: | If using an OEM version of Trading Networks, you cannot add or import new TN document types. |
|
| rules Document (optional) Exceptions with importing processing rules. The key is rules and the value is an IS document (IData object). fldgrps Document (optional) Exceptions with importing field groups. For each exception, the key is the field group description and the value is an IS document (IData object). |
| flddefs Document (optional) Exceptions with importing profile field definitions. For each exception, the key is the profileFieldID and the value is an IS document (IData object). profiles Document (optional) Exceptions with importing partner profiles. For each exception, the key is the partnerId and the value is an IS document (IData object). |
| idTypes Document (optional) Exceptions with importing ID types. For each exception, the key is the ID type description and the value is an IS document (IData object). contactTypes Document (optional) Exceptions encountered importing contact types. For each exception, the key is the contact type description and the value is an IS document (IData object). |
| binaryTypes Document (optional) Exceptions with importing binary types. For each exception, the key is the binary type description and the value is an IS document (IData object). |
| queues Document (optional) Exceptions with importing queues. For each exception, the key is the ID of the queue and the value is an IS document (IData object). tpas Document (optional) Exceptions with importing TPAs. For each exception, the key is the TPA ID and the value is an IS document (IData object). |
| extflds Document (optional) Exceptions with importing extended fields. For each exception, the key and the value is an IS document (IData object). profileGroups Document (optional) Exceptions with importing the partner profile groups. For each exception, the key is the ID of the profile group and the value is an IS document (IData object). securityData Document (optional) Exceptions with importing the security data. For each exception, the key is the ID of the security data and the value is an IS document (IData object). |
Usage Notes
![*](bullet.gif)
Use the
wm.tn.admin:exportData and
wm.tn.admin:exportData services to transfer data from one
Trading Networks database to another. You cannot transfer
all data in the database using these services. To transfer
all data, use the appropriate database vendor-supplied utility. The
wm.tn.admin:exportData and
wm.tn.admin:exportData services are useful for copying configuration data, such as, TN document types, attributes, processing rules, and profile field definitions. You cannot use the services to copy operational data, such as, document instances and activity log entries.
![*](bullet.gif)
If you are using an OEM version of the
Trading Networks, you cannot import new TN document types. This service will fail in an OEM environment.