Installation and Configuration Checklist

Step

Action

1: Installation

• Install the products you plan to use in the suite and apply licenses to the products as needed.

See Serena Release Manager Installation for details.

2: User Interface Shell

Put the user interface shell files into the SBM database to ensure Serena Release Control elements appear as designed.

See Installing the UI Shell files for details.

3: Process Apps

Import the Serena Release Control SBM solution and promote the snapshots of the process apps.

• Import the Serena Release Control solution, which contains a snapshot of each of the process apps.

• Create a new application server environment for the process apps if needed.

• Promote each of the snapshots, creating and selecting endpoints as needed. Use Security Token authentication for the endpoints.

• Configure hostname in each of the ZMF deployment task form Web page widgets.

• SBM 10.1.1.1 only: Select the SSO Authentication option in forms with RESTgrid widgets.

• Publish and deploy the process apps to upgrade the structure of the RESTGrid widgets.

See Importing and Promoting Serena Release Control for details.

4: Release Control Configuration

Configure required objects in Serena Release Control as follows:

• Create an administrative user and set all privileges for that user to the Serena Release Control objects, such as projects, reports, and auxiliary tables. For example, rlmadmin.

• Enable roles for Serena Release Control projects and verify that Serena Release Control is activated.

• Configure the Dashboard page as needed.

See Configuring Required Objects in Serena Release Control for details.

5: Client Connections

Configure the connections to each of the integrating clients using the Serena Release Manager Configurator. This information is stored in stored in the client connection properties files in the common Tomcat Web server webapps\rlm\WEB-INF\classes folder. For example, the Dimensions CM client connection file is dm-client-connections.properties.

Select the corresponding tab and fill out the form to specify connection information for each of the following:

• ALF

• SBM

• BCR

• RFC

• Dimensions CM

• Release Automation

• ZMF

See Configuring Connections using the Release Manager Configurator.

6: Dimensions CM Communication

Configure communication with Dimensions CM (Windows/UNIX systems release vault). For an overview of the integration, see Dimensions CM Communication Configuration Overview.

1. Configure Dimensions CM communication on the Dimensions CM server.

   • Specify ALF event configuration information in the dm.cfg file.

   • Specify selection criteria for the Dimensions CM events and objects by updating the ALF event configuration file, ALF_EVENTS_CONFIG.XML. Specify your Dimensions CM database name, project name, baseline type, and deploy event.

   See Configuring Communication on the Dimensions CM Server for details.

2. Configure Dimensions CM communication in Serena Release Manager.

• Specify the connection information. You should have already done this through the Serena Release Manager Configurator Dimensions CM page.

• Specify Dimensions CM client-specific information in the common Tomcat Web server webapps\rlm\WEB-INF\classes folder dm-client.properties file.

See Configuring Dimensions CM Communication in Release Manager for details.

7: ChangeMan ZMF Communication

Configure communication with ChangeMan ZMF (z/OS systems release vault). For an overview of the integration, see ZMF Communication Configuration Overview.

1. Configure ChangeMan ZMF communication on the z/OS mainframe.

   • Configure the NTFYURL; this is the URL Serena Release Manager uses to send information to SERNET through the server.

   • Configure the SERNET HTTP server; this is the server Serena Release Manager uses to populate the UI widgets with ZMF information.

   • Configure a proxy user ID for each mainframe host, or LPAR, that Serena Release Manager uses to log in to ChangeMan ZMF.

   • Configure TSO user IDs that match the SBM user IDs.

   • Configure approvers.

   See Configuring ZMF Communication on the Mainframe for details.

2. Configure ChangeMan ZMF communication in Serena Release Manager.

• Specify the connection information. You should have already done this through the Serena Release Manager Configurator ZMF page.

• Specify ALF event manager information for ChangeMan ZMF in the Serena Release Manager common Tomcat Web server webapps\almzmfalf\WEB-INF\conf folder alfzmf_resource.properties file.

• Specify other ZMF client-specific information in the Serena Release Manager common Tomcat Web server classes folder zmf-client.properties file.

See Configuring ZMF Communication in Release Manager for details.

8: Release Automation Communication

Configure communication with Serena Release Automation. For an overview of the integration, see Serena Release Automation Communication Configuration Overview.

1. Configure Serena Release Automation communication on the Serena Release Automation server.

   • Specify the Serena Release Automation server to notify when an event occurs in the Serena Release Automation rest.integration.properties file. If the file does not exist, create it.

   • Update the Serena Release Automation environment notifications for each application to tell Serena Release Automation the events about which to notify Serena Release Manager.

   See Configuring Communication on the Release Automation Server  for details.

2. Configure Serena Release Automation communication in Serena Release Manager.

• Update the Serena Release Automation ALF sign-on credentials. You should have already done this through the Serena Release Manager Configurator ALF page.

• Specify the Serena Release Automation client-specific information in the Serena Release Manager common Tomcat Web server classes folder nolio-client.properties file.

• Specify the Serena Release Automation client query information in the Serena Release Manager common Tomcat Web server classes folder nolio-client-queries.properties.properties file.

See Configuring Release Automation Communication in Release Manager for details.

9: Integrating objects

Configure the integrating application objects that are accessed by or provided to Serena Release Manager during the release management process. These may include but aren’t limited to the following:

• Release Control (SBM) users, general reports, Dashboard page, and notifications

• SBM projects (to provide BCRs or DCRs, for example)

• Applications and environments (servers) (specific to your organization; add to the respective auxiliary tables)

• Dimensions CM process model (GSL), projects and streams, baselines, and requests

• ChangeMan ZMF applications, sites, promotion levels, approvals, and change packages

• Release Automation environments, applications, processes, and servers

• Serena Service Manager projects and change requests (to provide RFCs, for example)

See Configuration and Administration of the Integrating Objects for details.

10: Provider properties

Configure the provider properties as needed in the common Tomcat Web server webapps\rlm\WEB-INF\classes folder. These may include but aren’t limited to the following:

• Serena Service Manager (SSM) request for change (RFC) properties (for example: itsm.properties and providers.properties)

• Serena Business Manager (SBM) business change request (BCR) properties (for example: bcr.properties and providers.properties)

• Serena Business Manager (SBM) development change request (DCR) properties (for example: sbm-issues.properties and providers.properties)

• Dimensions CM deployment unit (DU) properties (for example: dm_qlarius.properties and providers.properties)

• ChangeMan ZMF deployment unit (DU) properties (for example: zmf_packages.properties and providers.properties)

See Provider Configuration for details.

11: Customization

Complete customization and additional configuration as needed.

See Serena Release Manager Customization for details.