Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Creating or modifying a connection

This topic contains the following sections:

Overview of creating connections

In the service definition, you can define how one component communicates with other components.


Defining connections is optional for the basic functionality of service blueprints.

In the service definition, you can specify the source and destination components. For example, you can create a connection between the Tomcat server in one component and the Oracle database in a different component.

Connections between components are unidirectional from Source to Destination. The following figure shows that:

  • For Connection 1, Component 1 is the Source and Component 2 is the Destination
  • For Connection 2, Component 2 is the Source and Component 3 is the Destination

When you define a connection between components in different resource sets, these values pre-populate their network path. For more information, see Configuring network paths.


BMC Cloud Lifecycle Management 2.0 and 2.1 supported bidirectional connections but they were removed in the 3.0 release. You can view bidirectional connections in the 3.0 Service Blueprints Definition editor, but you cannot modify them, for example, by double-clicking them.

In addition, no pending network paths are created for bidirectional connections. To create network paths for the legacy connections, BMC recommends that you delete bidirectional connections and replace them with unidirectional connections.

To create or modify a connection

  1. In the Service Blueprints Definition editor, click the Service Definition tab.
  2. Click Connections.
  3. In the Connections column, click New .
  4. Enter a name that briefly describes the connection (for example, Apache to mySQL).
  5. Enter a helpful description (for example, Connection between Apache Server and mySQL DB).
  6. Select a protocol (for example, TCP).
  7. Specify the source component details (for example, Web Tier).
  8. Enter the port (for example, 82).
  9. Specify the target component details (for example, Application Tier).
  10. Enter the port (for example, 2002).
  11. Click OK.
    After you save the service blueprint, the connections are displayed in the Service Blueprints console.

Related topics

Creating and managing requestable services
Building service blueprints
Creating cloud services
Navigating the Service Blueprints window
Copying a service blueprint

Was this page helpful? Yes No Submitting... Thank you