Share This:

In this post I will describe the flow and validations BMC Cloud Lifecycle Management-eZDeploy uses to import ZipKits.


By taking a closer look at how this works, you can troubleshoot any eZDeploy Import ZipKit issues on your own.


BMC ZipKits for Cloud are designed for the BMC Cloud Lifecycle Management solution. BMC ZipKits provide out-of-the-box content that you can use to create services that deploy specialized platforms such as operating systems with specific applications for your cloud end users.


Download the eZDeploy utility from here.


The eZDeploy utility is a command line-based interface utility that is used to export and import BMC Cloud Lifecycle Management service blueprints.


Refer to Configuring environment for the eZDeploy utility to configure your environment and profile before using eZDeploy utility.


The eZDeploy Import command initializes “ImportBlueprint” thread, which reads attributes from eZDeploy profile (<installDir>/bmc/bladelogic/eZDeploy-2.1-Linux/profiles) and starts parsing *.eZ file, used as an input.


Here is a sample of the import command:


import -name "/u01/bmc/bladelogic/eZDeploy-2.1-Linux/eZfiles/CLM 4.0-SQL Server 2012 on Windows 2008 R2.eZ" -profile arai41eZDeploy -prefix AR41


“BLDeployParser readSoftwares” parses the bldeploy file and prompts you to input the deploy file path for unbundled software.


It’s recommended to copy unbundled software to a common location that is accessible to the BMC Server Automation Server and the Virtual Center (VC).


eZDeploy prompts with the following message:  Enter path for unbundled softwares separated by (;)


For examples:


  • (Microsoft Windows) You can enter the path or URL on eZDeploy as a network path://host/pathIncludingInstallerFile.


Note: Ensure that the software is in a shared location and is accessible or eZDeploy will not accept the network path while importing a blueprint.


  • (Linux) You can provide mounted path if you are using eZDeploy Linux version: //eZdeploy/Sample Path




mount -t cifs -o username=administrator,password=bmcAdm1n //<Servername, which holds the unbundled software>/zipkits /mnt


Importing unbundled software flow validates Depot and Job folder and replaces the “depot id”, present in BLDeploy xml, with the actual ids.


eZDeploy uses the following blcli command to list all available templates at vCenter If you select an option to create a new VGP:


$BLCLI Virtualization listAllVirtualGuestPackagesByType $VGP_TYPE > $VGP_LIST_FILE


eZDeploy uses the following blcli command to list available vCenter before it start to create a virtual guest job:


$BLCLI Virtualization listVirtualEntityManagers VMWareVirtualCenter > $VC_LIST_FILE

where BLCLI="blcli -v $PROFILE_NAME -r BLAdmins"


Note: Acquire the credentials before running the blcli command. Use the following command to acquire the credentials:


blcred cred -acquire -profile $PROFILE_NAME -username $BSAUSERNAME -password $BSAPASSWORD



eZDeploy uses the following blcli command to fetch the datastore once you select vCenter:


$BLCLI Virtualization listVirtualEntitiesByEntityManagerServerIdAndEntityType $VC_ID VMwareDataStore > $DATASTORE_LIST_FILE


eZDeploy uses the following blcli command to get the list of VM templates available on the vCenter server


$BLCLI Virtualization listVirtualEntitiesByEntityManagerServerNameAndEntityType $VC_NAME VirtualMachineTemplates > $TEMP_LIST_FILE


eZDeploy replaces sample “Product Catalog ID” with actuals, once it creates the new virtual Guest Package. Finally eZDeploy imports the package with these information.


I have consolidated all the steps, involved during import and created a flowchart to help you understand the mechanism used by ezDeploy Imports flow:



I hope this information is useful to understand the flow and validations BMC Cloud Lifecycle Management-eZDeploy uses to import ZipKits.


Other References


Refer to Using eZDeploy import for more information.


Link to download zipkits


KA417764 - BLPackage job ran successfully but application did not install on target server or Error: Application Software creation failed - No such file or directory


KA415487 - [WARNING] Either the path is not accessible or software is not found at the given location.


KA418005 - Does eZDeploy 2.0 compatible with BMC CLM 4.1?


KA419379 - ezDeploy zipkit export fail with Service Offering - nullis associated with deleted deployment model


KA419417 - eZDeploy zipkit import fail with [ERROR] Error occurred while getting Authentication-Token.The parameter seedText cannot be null or empty


KA415491 - Error: Platform manager profile missing


You can also join the Customer Support Community to learn about and provide feedback on ways Customer Support can enable your success.
Visit CLM Blogs.You can share the links with others if you find these useful.


Please rate this blog, regarding the usefulness of the shared information, by clicking below option.