Importing assets

Import assets from one instance of webMethods B2B Integration to another.

Before you begin

You must use a compressed file to import assets.
If the asset file contains only skipped assets, then the importing of the asset file fails.
The size of each asset file that is exported from cloud instance must not exceed 4 MB. If your asset file is larger than the allowed limit, export them again in smaller file sizes in a dependency order and then try to import them again.
If you do not follow the dependency order, it results in missing dependencies. For example, you cannot import a processing rule without importing a partner profile. The following list shows dependency order:
1. Partner profile
2. Field groups
3. Queues
4. Document attributes
5. Business documents
6. Processing rules
7. Agreements
If the export file is within the maximum size limit and has too many assets, import them in the dependency order.

Procedure

To import assets from another instance in webMethods B2B Integration, from the side navigation menu, click Asset movements > Import.
On the Import assets page, click Import from compressed file .

Select the assets to import from the asset type tabs.

Referred by shows the list of assets where the current asset is being used. Refers to show the list of dependent assets.

The following table shows the asset categories:


Asset category	Description
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 perform a force import action, then the status is Updated.
Ignored	System assets that are not supported in webMethods B2B Integration are categorized as Ignored.
Missing dependencies	Some assets require other assets. For example, the processing rule depends on partner profiles and document types, and document type depends on document attributes. For moved assets to work properly, the dependent assets must also move to the target instance, if they are not already present. When you select an asset to import it, 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 are listed as Missing dependencies. For example, if a processing rule refers to a partner profile that does not exist in both the target instance or the import file, it is a Missing dependency. Click Include dependencies to include all the dependent assets. This option is enabled only when the dependent asset is present in the import file, but you did not select it.
Conflicts	When an asset already 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. For example, if a partner profile already exists in the target system and is also available in the import file, it is a conflict. To avoid such conflicts, you must import the assets, using the Force import option. Click Clear conflicts to remove the conflicted assets from import.
Critical	Assets 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 options before importing the assets:


Option	Description
Force import	To overwrite assets that might already exist in the target instance. For more information, see Overwriting of existing assets.
Attach import summary with activity log	To view the import activity in the activity logs.

Click Proceed.

On the Import assets page, review the asset list that you have imported.
If you have more assets to import, click Start new import.

What to do next

Default assets in the environment such as channels, partner users, purge or archive schedules, and runtime transaction data, tasks, and the entries recorded in the Course of transaction.

The following table lists the actions that you must take after you complete the import activity.


Asset type	Action to take
Functional permissions	Create the relevant users and permissions for each user. See Managing User Roles and Permissions.
Partner profiles	As the Delivery settings are ignored partner profiles are imported, 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 while the importing processing rule is ignored. You must 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	Re-create the communication credential in the partner profiles. See Adding communication credential and Associating a communication credential with a partner.

To see the complete list of skipped assets, ignored asset properties, and system-generated assets, see Reference Information For Asset Movement.

After you import the assets into your target instance, do the following activities:

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.

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 exported from Trading Networks, the associated partner certificates are not included. You must 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.