Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Importing the ZipKit for Trac-Bug tracking tool on RHEL 5.9

After you have downloaded the files for the ZipKit, use the eZDeploy toolkit to import the content and make it available for use by BMC Cloud Lifecycle Management. 

Before you begin

Ensure that you have completed the following tasks:

Importing the ZipKit

To import the ZipKit:

  1. Locate the folder to which you downloaded the ZipKit.
  2. Open a command prompt window and navigate to the folder to which you downloaded the ZipKit.
  3. Execute the eZDeploy toolkit by issuing the following command:
eZDeploy> import –name C:/ezdeploy/export/Trac_on_RHEL5.9.eZ -profile <eZDeploy target eZDeployProfile Name>

The toolkit extracts the blueprint and the BMC Server Automation objects (packages and scripts) and makes them available for the BMC Cloud Lifecycle Management. See Using the eZDeploy toolkit for more information.

To configure network tags for blueprints

After eZDeploy toolkit makes the blueprint available for the BMC Cloud Lifecycle Management, you need to configure the Network tags that were imported with the blueprint according to your environment.

When defining network resources (for example, Network Interface Card details), you can tag the NIC and then use the policies to match tags on networks in the container.

  1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Service Blueprints.
  2. Open the service blueprint you imported in BMC Cloud Lifecycle Management, select the Service Deployment Definition.
  3. Select Resource set and click Edit.
  4. Click the Network Resources tab.
  5. In Network Select Method, select a tag (for example, Blueprint[Web] or Blueprint[DB]). The NIC tag is used to select the network to which the NIC should be attached (or routed).
  6. If you select Use Network Policies, the NIC tags are used to place the NIC on the network. The Service Governor selects the network based on a matching tag group and tag. See Tagging recommendations and examples for more details.

Ensure that you disable NAT settings for the Blueprint[DB] tag.


Where to go next 

Creating a Trac-Bug tracking tool on RHEL 5.9 service offering

Was this page helpful? Yes No Submitting... Thank you

Comments