Importing assets

Edit online

You can import assets from one webMethods B2B instance to another by using a compressed file or by applying a deployment from the list of importable deployments.

About this task

If the asset file contains only Skipped assets, then importing of the asset file fails. Use a compressed file to import assets. You cannot import the secondary certificate and System-generated assets.

The size of each asset file that is exported from cloud instance must not exceed 4 MB and from Trading Networks it must not exceed 1.5 MB. If your asset file is larger than the allowed limit, export them again in smaller file sizes in a dependency order and then import them again.

Use a compressed file to import assets from both a cloud instance, and from an on-premises Trading Networks instance.
You can import assets that are exported from Trading Networks 10.5 with Trading Networks Server 10.5 Fix 6 or higher versions, or from Trading Networks 10.7 with Trading Networks Server 10.7 Fix1 or higher versions. Export assets in binary format to reduce the file size compared to XML format.

If the export file is within the maximum size limit and contains many assets, import the assets in the dependency order. Failing to follow the dependency order leads to missing dependencies. For example, you cannot import a processing rule before importing the associated partner profile. The following list provides the required dependency order:

Partner profile
Field groups
Queues
Document attributes
Business documents
Processing rules
Agreements

If the compressed file that contains business documents from the 1.1 version of webMethods B2B, those documents do not get imported.

Procedure

In webMethods B2B, from the side navigation menu, click Asset movements and choose one of the following option:
- Import. On the Import assets page, select Import .zip file or Import deployments to import the assets.
- Deployments > Importable deployments.
  Select the deployment from the list to import in your environment, and click Next
  
  Note: Rejecting a deployment removes the deployment from the target environment and from the Importable deployments page permanently. If the deployment fails, webMethods B2B does not delete it. It is available in the Importable deployments.
Select the assets to import, from the different asset type tabs, and click Next.
The assets types that are not supported in webMethods B2B are skipped when you import them from an Trading Networks instance.

The following list describes the different statuses of assets:

Skipped

If you export assets from an Trading Networks instance, the assets that are not supported in webMethods B2B, are listed as Skipped assets. For example, data-level permissions cannot be moved to the cloud instance because it is not supported.

Added

If you import assets that are not present in the target instance, it gets added to the instance with the status as Added.

Updated

If you import assets that are existing in the target instance, and when you force import the assets, then the status is Updated.

Ignored

System assets or any of the asset properties of Trading Networks instance that are not supported in webMethods B2B are categorized as Ignored.

Missing dependencies

For assets that are moved, the dependent assets must also move to the target instance to function properly. For example, the processing rule depends on partner profiles and document types, and document type depends on document attributes. When you select an asset to import, the system scans the target instance for the presence of the dependent assets. If the dependent assets are not present in both the target instance or in the assets you selected, then those dependent assets are listed as Missing dependencies.

Conflicts

When an asset exists in the target instance, and is imported again with force as false, it causes conflicts without overwriting the asset. If assets are present on the target instance with different ID, conflicts can occur with warnings.
Select the Conflicts tab to delete the conflicted assets from the Import assets page.

Critical

Assets that are not imported for any other miscellaneous reasons are termed as Critical. For example, importing a different enterprise when the enterprise is already present in the target instance.
Click Import. Select the option to import the assets:
Force import
To overwrite assets that might exist in the target instance.
- If you import a previously nonexistent rule into a target instance, the processing rule retains the same sequence number in the target instance.
- When an existing processing rule is imported again to a target instance with the Force import option, the rule in the target instance is updated, but the sequence number is not retained. Therefore, the rule is appended to the end of the rule list. You must manually change the sequence number after you import all the processing rules.
Attach import summary with activity log

To view the import activity in the activity logs.
Click Proceed.
On the Import assets page, review the imported asset list.

What to do next

Click the Download import summary icon to view the list of success, warning, and error messages. Use the relevant message detail to rectify each error or warning that depends on the severity in the downloaded file. If you have more assets to import, click Start new import.

Assets that are native to an environment are channels, partner users, purge or archive schedules, and runtime transaction data, tasks, and the entries recorded in the Course of transaction.

Perform the following tasks after importing the assets:

Archival and purge schedules: Update the default archival schedule and create the relevant purge schedules. For more information, see Archiving and purging data.
Functional permissions: Create the relevant users and permissions for each user. For more information, see Managing User Roles and Permissions.
Partner profiles: The Delivery settings are ignored when partner profiles are imported from an on-premises Trading Networks instance. Create outbound channels and associate them with the partner profiles. For more information, see Associating an outbound channel with a partner.
Processing rule: The Execute a service action is ignored when importing processing rule from an on-premises Trading Networks instance. Create an integration in webMethods Integration and associate it in the Call an integration action. For more information, see Adding a Processing Rule.
Communication credential for each partner profile: Recreate the communication credential in the partner profiles. For more information, see Adding communication credential and Associating a communication credential with a partner.

On importing an XML document, manually associate it with the webMethods Integration project and the document type to populate the required schema.

The integration endpoint that you configured in all the processing rules must be valid when the endpoint is accessed from the target instance.

To see the complete list of skipped assets, ignored asset properties, and system-generated assets, see Reference information for asset movement.

Note:

If any EDI document depends on other assets, and during import if the dependent assets are not present in the target instance or import file, then the document import fails. The document schema is created in webMethods Integration. Later, if you try to import the same document again, the instance already has the document.

When you import a compressed XML file that is exported from Trading Networks, the associated partner certificates are not included. Add these certificates manually after the import process. If you want to include certificates along with partner profiles during import, export the file in the compressed binary format from Trading Networks.