Importing the SAP systems ZipKit

After you have downloaded the files for the ZipKit, use the eZDeploy toolkit to import the SAP blueprint, catalog, and software packages and make it available for use by BMC Cloud Lifecycle Management. This topic contains the following section:

• • Before you begin
  • Creating parameters in BMC Server Automation
  • Creating the folder structure in BMC Server Automation
  • Importing the content using eZDeploy
  • Import example
  • Importing post-deployment actions
  • Verifying the imports
  • Where to go next

Before you begin

• Request the SAP systems ZipKit from one of the listed contacts on the BMC Communities SAP systems ZipKit page.
• Download and configure the eZDeploy utility  on the BMC Server Automation system.

Creating parameters in BMC Server Automation

You must create a number of parameters in BMC Server Automation for use by BMC Cloud Lifecycle Management during the provisioning process.

1. Open the BMC Server Automation console
2. Click Configuration
3. Click the Property Dictionary view and expand it.
4. Expand Built-in Property Class.
5. Expand Deployed Package.

6. Click the Add icon  to add a new property. The Add Property window is displayed.
   

   Note

   With the exception of the RFC_PASSWORD and DDIC_PASSWORD properties, which are encrypted strings, all of the properties used in the BL Packages for SAP are strings.

7. Create the parameters listed in the following table:
   
8. Verify that all of the above parameters are created properly before creating the folder structure.

Creating the folder structure in BMC Server Automation

The ezDeploy utility imports not just the BL software packages in BMC Server Automation but also the blueprints and catalogs. Therefore, you must create a standard folder structure so that those packages can be imported to the correct location. Folders must be created under in the /Bladelogic/Depot /Bladelogic/Jobs folder.

Create the folders shown in the following table:

Importing the content using eZDeploy

Once the .eZ files are downloaded, import them into the target environment, as described in the "To import an eZDeploy package in interactive mode" section in Importing-service-blueprints-and-service-catalog-using-eZDeploy. You can use the the import example as a model.

The eZDeploy utility 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.

When imported, the following blueprints and its respective catalogs will be available in the environment.

Import example

Consider the following example:

• You want to import the Solution Manager blueprint.
• The .eZ file path is C:/ezdeploy-01112013/ezdeploy/export/SAP_SOLMAN71_SR1_NW702_DUAL_RHEL64_ORA11203_v1.0.eZ.
• The profile name is Target.

The command to import the Solution Manager blueprint would be:

Importing post-deployment actions

Not all of the SAP content is built on blueprints. The System Refresh, System Rename, Starting and Stopping the SAP Landscape, and the SAP backup are post-deployment actions which are not exported as part of eZDeploy. You must manually import the actions into the BMC Server Automation (target) environment.

Before you begin

Before you import the actions, ensure that you have a folder structure in place in BMC Server Automation. For example, if you have the System Refresh packages downloaded on your server, the folder would look like the following:

Importing the actions to BMC Server Automation

1. Log on to BMC Server Automation console
2. Browse to the folder structure you have created under Bladelogic > SAP_Packages > SAP_ERP_SYSREFRESH_v1.0.
3. Select the folder and click File > Import.
4. Browse to the path where the packages are placed.
5. Select the package you want to import.
6. Click Next.
7. Following the authorizations panel, click Finish.
8. This step imports package into BMC Server Automation and place it into appropriate folder.
9. Right-click the package and create a Deploy Job under the CSM_Applications folder. Click here to view instructions in BMC Server Automation online technical documentation.
10. Ensure that the Product Manufacturer, Product Version, and Product Name are entered correctly.
11. Run the Publish Product Catalog job. This job makes the package available in BMC Cloud Lifecycle Management.

Once you have finished importing  the post-deployment action scripts, configure the actions in BMC Cloud Lifecycle Management. 

Verifying the imports

Once you have completed the imports, verify that the import was successful, as described in Validating-import-and-export-actions-in-eZDeploy.

Once you are finished, you have ready-to-use blueprints and catalogs can can create service request definitions. 

Where to go next

Requesting SAP services