Deploying connectors to data centers
You can deploy a connector within the same data center or across different data centers.
Each connector has an App ID and GUID. To import and export a workflow containing a custom CLI connector, webMethods Integration uses a GUID.
App ID: App ID is the application ID of a connector and can be different for each environment or data center in which the connector is deployed. For example, if a Google Tasks connector is deployed on a development environment as well as staging environment, then the App ID for Google Tasks will be different for both environments.
GUID: GUID is the unique ID associated with a connector and always remains the same across all environments and data centers. It is important to keep the connector GUID same across all environments and data centers for successful import and export operation.
Deploying a connector across different data centers
To deploy a connector across different data centers, do as follows:
Step 1: Log in to the CLI app with your source tenant credentials.
Step 2: Run the following command:
wmio migrate {domain} {email} {developer key}
where, domain is the domain name of the destination tenant and email is the email ID associated with the destination tenant developer key is the developer key associated with the destination tenant. To obtain the developer key, login to the relevant tenant and then go to the Profile Icon > Profile option.
Deploying a connector in the same data center across different tenants
To deploy a connector in the same data center across different tenants, do as follows:
Step 1: Log in to the CLI app with the destination tenant credentials.
Step 2: Open the index.json file and remove the appid key from it.
Step 3: Run the following command:
wmio deploy