How to Deploy a Package to a Remote Data Repository

You can deploy a package to a data repository located on a remote machine without logging in to the remote machine. This feature is useful if you need to deploy queries, views, or other UCMDB resources created on one machine to other machines running UCMDB.

1. Prerequisites

   • Verify that the Data Flow Probe is configured correctly and is connected to UCMDB.

   • Verify that the version of UCMDB running on the remote machine is version 9.02 or later.

   • Verify that the UCMDB Server on the remote machine is up and running.

   • Create the package that must be deployed to the remote machine, and deploy this package to the local UCMDB Server.

     Note By default, you cannot deploy a package that is larger than 10 MB.

   • Create an integration point on the local UCMDB Server, that uses the UCMDB 9.x/10.x adapter.

2. Change timeout - optional

   You can change the time after which UCMDB times out package deployment. If UCMDB cannot connect to the remote machine in 5 minutes, by default, the deployment is timed out.

   To change the default: Select Administration > Infrastructure Settings Manager > Integration Settings > Remote package deploy Timeout. (The refresh rate indicates when the change takes effect in UCMDB after the value is modified.)

3. Select the integration point

   In the Integration Point pane, right-click the integration point that you created in Prerequisites above. For details, see Integration Point Pane, and select Deploy Remote Package.

4. Select the package

   1. In the Deploy Remote Package dialog box, select a package from the list of packages existing on the local UCMDB Server. This is the package that you created in Prerequisites above. For details, see Deploy Package to Remote Data Repository using <Integration Point>.

   2. Click OK to deploy the package.

5. View deployment results

   Answer the message that is displayed: click OK to begin deploying the package.

   The status of the deployed package is displayed together with the status of each individual resource in the package.

   • Successful deployment: A package is successfully deployed if all its resources are successfully deployed.

   • Failed deployment: If even one resource fails, the package deployment is considered to have failed. Even if package deployment fails, all the successful resources are deployed on the remote machine.

     The reason for the failure, for example, a missing CIT, is displayed in the Deployed resources section:

     

6. View Log files

   The following table shows the locations of the log files that record any issues that might arise during deployment:

   Location	Log File Name
   Remote UCMDB machine, version 9.02 or later	ucmdb-api.log mam.packaging.log
   Data Flow Probe	probeTasks.log probe-infra.log adapters.log
   Local UCMDB machine	ucmdb-api.log

   If a resource fails to deploy, an error is displayed in the Status column as well as in the log file on the remote machine.