Using eZDeploy import from an answer file

The eZDeploy import feature allows you to import a BMC Cloud Lifecycle Management business service, service offering, service blueprint, and software package in the noninteractive (using an answer file) and interactive (using command line) mode.

The following sections detail the procedures for importing eZDeploy packages from an answer file.

• Before you begin
• To use eZDeploy import in the noninteractive mode
• To import a business service
• To import a service blueprint
• To import a service offering
• To import a software package
• Where to go from here

Before you begin

Ensure that you have met the following prerequisites for importing an eZDeploy package:

• Profiles must be created in the target environment prior to importing a service blueprint or a service catalog. See Managing-eZDeploy-profiles for details.
• BMC Cloud Lifecycle Management is installed and configured.

• If you are specifying an entitlement package during import, you must have created one Global entitlement package on the BMC Cloud Lifecycle Management environment where you are importing the service catalog.

  Note

  Due to a limitation in the eZDeploy utility, you cannot fetch tenant-specific entitlement packages while importing the service catalog in your BMC Cloud Lifecycle Management environment. You need to have at least one Global entitlement package when importing the service catalog by using the eZDeploy utility.

• You have the Virtual Center (VC) server name, Virtual Center templates and the datastore name.

• You have the location details (single or multiple storage) of the software(s) to be installed.

  Tip

  • To avoid performance issues, store all software in a common single-level directory, which is accessible to the BMC Server Automation Server and the Virtual Center Server.
  • For specific information related to unbundled software packages used with the infrastructure zipkits downloaded from the BMC Communities, refer to the Where to download the Zipkit section of the individual zipkit documentation available at Configuring-infrastructure-application-ZipKits.
• BMC Server Automation console is installed on the same computer on which you would be running the eZDeploy utility.
   
• BMC Server Automation is configured:
  
  • The VC server is added and registered in BMC Server Automation.
  • You have run the Distribute Configuration Object (also known as DCO) job.
• You have created an answer file (eZOptions.xml) specifying your environment details to import a blueprint or software package in noninteractive mode.

_{Back to top}

To use eZDeploy import in the noninteractive mode

To use eZDeploy import in the noninteractive mode you must:

• Create an answer file
• Import the eZDeploy package

_{Back to top}

To create an answer file

1. Using a text editor, create an .xml file with the following sample format or use eZOptions.xml, the default XML template provided with the eZDeploy directory, and modify it as per your requirement.
   
   

   <?xml version="1.0" encoding="UTF-8"?>
   <EZOptions>
      <Blueprint>
          <BlueprintName>VMWare-BP-1</BlueprintName>
          <SoftwarePath>\\DEV-YW-3\software</SoftwarePath>
          <MountedNetworkPath></MountedNetworkPath>
          <ExistingVGP>TRUE</ExistingVGP>
          <VGPName>VMW-W2k8-64B-20GB</VGPName>
          <vCenterServer>bmcstrykerclmonbmc</vCenterServer>
          <Datastore>CLM_POD2_WT_LUN3</Datastore>
          <Template>Win2k8r2-temp</Template>
          <LicenseKey>1267e-12344-abcdf-123fr-23456</LicenseKey>
          <AdminPassword>Password</AdminPassword>
          <EntitlementPackage>azurepkg</EntitlementPackage>
          <AllowDuplicateOptionSet>TRUE</AllowDuplicateOptionSet>
      </Blueprint>
      <Blueprint>
          <BlueprintName>VM-3</BlueprintName>
          <SoftwarePath>\\DEV-YW-3\software</SoftwarePath>
          <MountedNetworkPath></MountedNetworkPath>
          <ExistingVGP>FALSE</ExistingVGP>
          <VGPName>VMW-W2</VGPName>
          <vCenterServer>bmcstrykerclmonbmc</vCenterServer>
          <Datastore>CLM_POD2_WT_LUN3</Datastore>
          <Template>Win2k8r2-temp</Template>
          <LicenseKey>1267e-12344-abcdf-123fr-23456</LicenseKey>
          <AdminPassword>Password</AdminPassword>
          <EntitlementPackage>global_package</EntitlementPackage>
          <AllowDuplicateOptionSet>TRUE</AllowDuplicateOptionSet>    
      </Blueprint>
      <Blueprint>
          <BlueprintName>Az-BP-3</BlueprintName>
          <SoftwarePath>\\eZdeploy\Sample Path;\\eZdeploy\Sample path1
          </SoftwarePath>
          <MountedNetworkPath>//eZdeploy/Sample Path
          </MountedNetworkPath>
          <ExistingVGP>TRUE</ExistingVGP>
          <VGPName>Sample VGP Name;Sample VGP Name1</VGPName>
          <vCenterServer>Sample VCenter</vCenterServer>
          <Datastore>Sample Datastore</Datastore>
          <Template>Sample Template</Template>
          <LicenseKey>1235e-12344-abcdf-123fr-23456</LicenseKey>
          <AdminPassword>Sample AdminPassword</AdminPassword>
          <EntitlementPackage>Sample Global EntitlementPackage
          </EntitlementPackage>
          <AllowDuplicateOptionSet>TRUE</AllowDuplicateOptionSet>
      </Blueprint>
      <SoftwarePackage>
          <SoftwarePackageName>7zip</SoftwarePackageName>
          <SoftwarePath>\\eZdeploy\Sample Path</SoftwarePath>
          <MountedNetworkPath>//eZdeploy/Sample Path
          </MountedNetworkPath>
      </SoftwarePackage>
      <SoftwarePackage>
          <SoftwarePackageName>JDK_Linux</SoftwarePackageName>
          <SoftwarePath>\\DEV-YW-3\software</SoftwarePath>
          <MountedNetworkPath></MountedNetworkPath>
      </SoftwarePackage>
      <SoftwarePackage>
          <SoftwarePackageName>Windows_Apache</SoftwarePackageName>
          <SoftwarePath>\\apache\Sample Path</SoftwarePath>
          <MountedNetworkPath>//eZdeploy/apache Path
          </MountedNetworkPath>
      </SoftwarePackage>
   </EZOptions>

   Complete the following import option details for your environment in the answer file:

   Parameter	Description	Value type	Sample value
   BlueprintName	Enter the name of the BMC Cloud Lifecycle Management service blueprint	String	Az-BP-3
   SoftwarePath	(Required) Enter common paths for unbundled software separated by semicolons (;). Each software path or URL can be a network path. For Linux, you can use Mounted path for software repository.	String	"C:\eZdeploy\Software1"; "C:\eZdeploy\Software2"
   MountedNetworkPath	(Optional) The mounted network path applies only for a eZDeploy Linux version	String	"//eZdeploy/Sample Path"
   ExistingVGP	(Required) Specify whether you want to use an existing VGP	Boolean	True or False
   VGPName	(Required) Provide the existing VGP name	String	eZDeploy
   vCenterServer	(Conditional; required only if you specify ExistingVGP = False.) Provide the vCenter server's IP address or host name which you have used in BSA	String	11.111.111.11
   Datastore	(Conditional; required only if you specify ExistingVGP = False.) Provide the vCenter datastore name.	String	Datastore1
   Template	(Conditional; required only if you specify ExistingVGP = False.) Provide the vCenter template name	String	Template1
   LicenseKey	(Optional) If you selected a Windows template, provide the license key	String	xxxxx-xxxxx-xxxxx -xxxxx-xxxxx
   AdminPassword	(Required) Enter the plain-text administrator password for logging onto the BMC Server Automation application installed in your environment. Note: The current release of eZDeploy does not support the password encryption feature.	String	xxxx
   EntitlementPackage	(Required) Enter the entitlement package for importing the blueprint	String	Global Entitlement Package
   AllowDuplicateOptionSet	(Required) Specify whether you want to create duplicate option choices If you select yes, and if an option is already present in the target system, new options are created with a numbered suffix when another service catalog with the same options is imported.	Boolean	True or False
   SoftwarePackageName	(Conditional; required only if you import a software package) Name of the eZDeploy package file	String	Windows_Apache

   Note

   SoftwarePath, VGPName, Datastore, and Template are case sensitive. Ensure that you provide exact values in the answer file. Do not leave any field empty.

2. Save the file.

_{Back to top}

To import a business service

To import a business service, which includes one or more service blueprints and one or more service offerings to a custom directory by using an answer file, run the following command:

The following table describes the input parameters:

_{Back to top}

To import a service blueprint

To import a service blueprint by using an answer file include the <Blueprint> tags as shown in the sample eZOptions.xml file, and then run the following command:

The following table describes the parameters:

_{Back to top}

To import a service offering

To import an individual service offering by using an answer file, run the following command:

The following table describes the parameters:

_{Back to top}

To import a software package

To import a software package by using an answer file include the <SoftwarePackageName> tags as shown in the sample eZOptions.xml file,and then run the following command:

The following table describes the parameters:

_{Back to top}

Where to go from here

Validating-the-eZDeploy-import

_{Back to top}