Importing the ZipKit for Oracle 11g on RHEL 5.9

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

Before you begin

Ensure that you have completed the following tasks:

• Downloaded the Oracle 11g ZipKit.
• Downloaded the NSH script for post installation options.
• Downloaded Oracle dependencies packages from Red Hat Enterprise Linux 5.9 64 bit media.
• Ensure that you have an eZDeploy profile. See create an eZDeploy profile.

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:

The toolkit extracts the blueprint and the BMC Server Automation objects (packages and scripts) and makes them available for the BMC Cloud Lifecycle Management. While running eZDeploy toolkit, you need to provide the path for all .rpm and BMC Atrium Orchestrator workflow (.roar) files. See Using the eZDeploy toolkit for more information.

Importing Network Shell scripts in BMC Server Automation

For Oracle 11g post-deployment options, import NSH script in your BMC Server Automation console.

To import Network Shell (NSH) scripts:

1. Log on as an Administrator in the BMC Server Automation console.
2. Navigate to the Folders > Depot and right-click on CSM_Scripts.
3. Click Import.
4. Browse to the NSH Script repository and select the NSH Script to be imported.
5. Click Next and verify that the path is set to Depot/CSM_scripts.
6. If required, double-click and edit the path to Depot/CSM_Scripts.
7. Click Finish.

Activating BMC Atrium Orchestrator workflow

The eZDeploy toolkit makes Atrium Orchestrator workflow available for the BMC Atrium Orchestrator. You need to activate the workflow module and SSH adapter on grid.

To activate the workflow module

1. Log on to the Grid Manager.
2. Click the Manage tab, and click the Modules tab.
3. On the Modules in Repository page, select the check box corresponding to the module.
4. Click Activate. 

A message stating that the module is activated successfully is displayed.

To enable the SSH adapter

1. Click the Manage tab, and click the Peers tab.
2. From the currently defined peers for the selected grid, select the peer on which to enable the adapter, and then click Edit .
3. On the Edit a Peer Configuration page, click Enable to display the available adapters for this peer.
4. Select the adapter to enable, and then click OK.
   You can select multiple adapters by pressing the Shift or Ctrl key while selecting adapters.
5. Click OK to save the peer configuration.

To configure Network tags for blueprints

Once eZDeploy toolkit makes the blueprint available for the BMC Cloud Lifecycle Management. You need to configure network tags imported with the blueprint as per 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.

Where to go next

9 service offering