Creating an Environment for Serena Release Manager

You must create an SBM application engine server environment for your Serena Release Control process applications unless you are promoting them into an existing environment. After you create the environment, you must set up a BPEL engine and SBM event manager for that environment.

 

 

TIP  Understanding SBM: An environment describes the runtime server to which you deploy process apps. An environment requires an SBM Application Engine server.

After you create the environment, you must add other target servers (such as a BPEL engine or Event Manager server) as well as any Web service end points that are required to support the process app.

If you are putting your Serena Release Control process apps into an existing environment, continue to Promoting the Snapshots.

Create the environment and supporting target servers as follows:

Creating the Environment

To create the environment:

  1. From the SBM Application Repository Solutions content pane, click Environments.

  2. Click New.

    The New Environment dialog box appears.

  3. Fill out the form for the new environment as follows:

    1. Enter a name and description. For example, RLM Environment.

    2. In the Composer field, select Enable Deployment.

    3. Under Application Engine Server, enter a name and description. For example: RLM Application Engine Server.

    4. In the URL, change the server to the host name for your application engine server and specify the port number for the server. For example:

    http://sbmaehost:80/gsoap/gsoap_ssl.dll?sbminternalservices72

  4. Click Test Connection to test the connection.

  5. Click OK.

Specifying the BPEL Server for SBM Orchestrations

For new SBM environments, you must specify the target server for the SBM orchestrations, or BPEL engine.

To set up the target server for SBM orchestrations:

  1. Select the environment you just created and then select the Target Servers tab.

  2. Click New.

    The New Target Server dialog box appears.

  3. Fill out the form to create the BPEL server as follows:

    1. In the Type field, select BPEL Server (JBPM).

    2. Name the BPEL server. For example: SBM Orchestration Server.

    3. Enter the URL using the host name for your orchestration engine server as the hostname.

      Port 8085 is the default, unless you specified a different port in the Configurator for your JBOSS server. For example:

      http://sbmoehost:8085/jbpm-bpel/services/DeployService

       

       

      TIP  Above the URL field, click View Examples and select from the examples. In the URL field, overtype the hostname and port.

    4. Click Test Connection to test the connection.

    5. Click OK.

Specifying the SBM System Event Manager

For new SBM environments, you must specify the target server for the SBM system event manager.

To set up the SBM system event manager:

  1. Select the environment you just created and then select the Target Servers tab.

  2. Click New.

    The New Target Server dialog box appears.

  3. Fill out the form to create the event manager server as follows:

    1. In the Type field, select System Event Manager.

    2. Name the event manager server. For example: SBM Event Manager.

    3. Enter the URL using the host name for your system event server as the hostname. For example:

      http://sysevnthost:8085/eventmanager/services/ALFAdmin

    4. Click Test Connection to test the connection.

    5. Click OK.

       

       

      NOTES  

      • You do not need to create a target server for the SBM Common Services. This target server is created automatically when a process app snapshot associated with SSM or SLA is promoted.

      • SBM Common Services are not the same as the Serena Common Tomcat Services used by Serena Release Manager.