Managing Asset Movement
In webMethods.io MFT, you can move the assets from one cloud instance to another using a ZIP file.
In webMethods.io MFT, you can move the assets from one cloud instance to another using a ZIP file.
To export webMethods.io MFT assets:
In webMethods.io MFT, go to Asset movement > Export Assets.
On the Export Assets page, select the assets to export from the tabs that mention the types of assets. The Include dependencies option is selected by default. Clear this option if you do not want the dependent assets to be included in the export file. Each asset specifies the number of dependencies it has. To view all the dependent assets, click the number against each asset.
After you select the assets, click Add to export list and click Next.When selecting a virtual folder, all the child virtual folders are selected by default, but not the parent virtual folder.
On the Export assets page, the assets are mentioned under their own respective tabs. Verify the final export set. Assets can be removed while verifying the final export set.
Click Next.
On the Export Assets page, specify a name for the export file. webMethods.io MFT downloads the exported assets in the form of a ZIP file. The location of the downloaded file depends on your browser configuration.
Click Finish.
webMethods.io MFT has an option to export all assets. Click the check box Export all to download all the assets.User does not get to specify the file name, while opting to use the Export all option.
Note: webMethods.io MFT does not support the export or import of Users as an asset. Users associated with virtual folders and post processing actions will not be exported or imported.
To import webMethods.io MFT assets:
In webMethods.io MFT, go to Asset movement > Import Assets.
On the Import Assets page, select the ZIP files that you want to import.
After importing the ZIP file, you can use the Filters menu to filter the assets by the asset name or you can manually select the assets that you want to import.
Resolve the errors in the analysis report to import the assets successfully.
Note: The three categories of severities are Error, Warning, and Skip.
Click Import. To overwrite assets that might already exist in the target audience, select Force import. 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.
You can export and import a group of webMethods.io MFT assets from one environment to another.
To create a deployment
In webMethods.io MFT, go to Asset movement > Deployments.
Click New deployment to navigate to the Export assets page.
On the Export Assets page, select the assets to export from the tabs that mention the types of assets.
Note: webMethods.io MFT has an option to export all assets. Click the check box Export all to download all the assets.
After you select the assets, click Add to export list and click Next.
Verify the final export set. You can remove assets while verifying the final export set.
Click Next.
On the Export Assets page, select Create a new deployment. Assign an unique deployment name and click Create.
To publish a deployment
From the Export assets page:
While creating a deployment from the Export assets page, after naming the deployment, click the check box Publish deployment to an environment.
Enter the following details and click Publish to get the deployment published in the target environment.
Field |
Description |
---|---|
Target deployment name | Name of the deployment in the target environment. |
Stage | Target cloud environment stages available to the currently logged in user (Development, Stage, Test, Production). |
Environment | Environment or Tenant ID of the target environment that the user has access to. |
From the Deployments page:
Select an existing deployment and click Publish.
Follow step 2 from the above mentioned instructions.
You can import the assets you push from a different environment to your current environment.
Prerequisite: You must have at least two environments so you can switch between them.
To import a deployment from available deployments
In webMethods.io MFT, go to Asset movement > Import assets and click Import a Deployment.
Select a deployment from the available deployment table.
Select the assets to import.
Click Next. Verify the final list of assets to apply. To remove assets that you no longer wish to import, click Delete.
Click Import, on the Import selected assets dialog box, select Force import option to overwrite assets that may already exist in your environment, and click Proceed.
If you wish to import more deployments, click Start new import.
View the details of all the deployments you create on the Deployments and Export assets page.
To view the details of a deployment
In webMethods.io MFT, go to Asset movement > Deployments.
Select the deployment to view details such as number and type of assets in the deployment. You can edit the name and description of the deployments.
The deployments you create in one environment can be published and imported to another environment.
Monitor the status of these deployments on Asset movement > Deployment log.
Search for specific deployment logs by deployment set name, associated environment name, user, type, or status.
The Deployment logs page displays the following details:
Field | Description |
---|---|
Deployment name | Name of the deployment |
Last activity log time | Timestamp when the action was performed on the deployment. |
Details | Details of the selected deployment. |
ID | ID of the deployment. |
Type | Action performed on the deployments. Some of the possible events are: |
Time | Timestamp when the action was performed on the deployment. |
Status | Displays whether the action is successful or failed. |
User | Name of the user who performed this action. |
Summary | Action performed on the deployments. Some of the possible events are: |
Publisher | Name of the user who published this deployment. |
Target user | Name of the user who can import this deployment. |
Source environment | Name of the environment from where the deployment set was published. |
Target environment | Name of the environment to which the deployment was published. |