Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Importing the ZipKit for Apache Tomcat 8.0 on SUSE Linux Enterprise Server 11.0

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 -service "CLM 4.5-Apache Tomcat 8.0 on SUSE Linux Enterprise
Server 11.0" -path "C:/ezdeploy/export/CLM 4.5-Apache Tomcat 8.0 on SUSE
Linux Enterprise Server 11.0.eZ" -profile <eZDeploy target eZDeployProfile Name>

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

Note

Once the import is complete, ensure that you change the following entities depending on your BMC Cloud Lifecycle Management environment:

  • blueprint tags
  • tenant mappings
  • entitlement package mappings
  • version of the blueprint selected in the service catalog; if the blueprint was modified, select the latest version

Also, in the Network Placement Details section of the blueprint, ensure that the IP address is set to Dynamic. If the IP address is set to Static, make sure that the target server is reachable.

To configure network tags for blueprints

After the eZDeploy toolkit makes the blueprint available for BMC Cloud Lifecycle Management, you need to configure the 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 Designer.
  2. Open the service blueprint you imported in BMC Cloud Lifecycle Management, and open one of the Networks taggable object.
  3. Click either the Tags field or the Add icon plus_icon.gif next to the Tags field.
  4. In the Tags menu, click the tag you want to add (for example, Blueprint[Web] or Blueprint[DB]). The tag is used to select the network to which the NIC should be attached (or routed).

See  Tagging recommendations and examples for more details.

Note

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

Where to go next

Creating-an-Apache-Tomcat-8-0-on-SUSE-Linux-Enterprise-Server-11-0-service-offering

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*