Configuring the cbt command

This explains how to configure the cbt command. The cbt command is installed on your SA core servers in the following directory:

/opt/opsware/cbt/bin

To run the cbt command outside the SA Core, see Configuring the cbt command.

The cbt command can be run on any Unix computer with network access to an SA mesh. Although the cbt command is not supported on the Windows platform, it does support import and export of Windows content.

The cbt command is written in Java and uses OWL and RDF for its schema definition and persistent store. It imports and exports SA content by using SA APIs to extract both configuration and large binary content, such as packages and scripts.

1. To verify that you can run the cbt command, enter the following commands:
   % cd <cbt_install_directory>/bin
% ./cbt -v
   
   The -v option displays the command’s version string.
   
   On some servers, the cbt command displays the following error:
   Error occurred during initialization of VM
Could not reserve enough space for object heap
   
   If this error occurs, then edit the cbt script, changing the value of the -Xmx option in jargs to a lower value, for example: -Xmx512m.
2. Perform the following steps for each mesh that you will be importing into or exporting from:

   1. Set up the needed cryptographic data. This step is optional if you are running cbt from the server where the SA Command Center core component is installed:

      • Log in to the SA core server as root and execute the following command: /opt/opsware/bin/python –m opsware_common.crypto.bundle –r spog –c opsware –b <zip_bundle_name>

      • Copy the generated .zip file and extract it in a location of your choice. Set this location as the value for an environment variable named CRYPTO_PATH.

   2. Obtain the Web Services Data Access Engine (twist) user name and password from your SA administrator. This is set during the Web Services Data Access Engine (twist) installation.

   3. Create a target mesh configuration file containing the location and identity information required to access the SA mesh components. For details on this task, see the following section.