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: 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.

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

See Importing and Promoting Serena Release Control for details.

3: Release Control Configuration

Configure required objects in Serena Release Control as follows:

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

• 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.

4: Dimensions CM Communication

Configure communication with Dimensions CM (Windows/UNIX systems release vault).

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 Dimensions CM endpoints and user IDs in the common Tomcat Web server webapps\rlm\WEB-INF\classes folder dimensions.properties file.

See Configuring Dimensions CM Communication in Release Manager for details.

5: ChangeMan ZMF Communication

Configure communication with ChangeMan ZMF (z/OS systems release vault).

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 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 z/OS Mainframe      for details.

2. Configure ChangeMan ZMF communication in Serena Release Manager.

• Specify sign-on information in the common Tomcat Web server webapps\rlm\WEB-INF\classes folder zmf.properties file.

• Specify ALF event manager connection information in the common Tomcat Web server webapps\zmfalf\WEB-INF\conf folder alfzmf_resources.properties file.

• Specify selection criteria for ZMF events and objects in the common Tomcat Web server webapps\rlm\WEB-INF\classes folder zmf_packages.properties file.

See Configuring ChangeMan ZMF Communication in Release Manager for details.

6: Release Automation Communication

Configure communication with Serena Release Automation.

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 sign-on credentials in the common Tomcat Web server webapps\rlm\WEB-INF\classes folder alf.properties file.

• Specify the Serena Release Automation connection information in the common Tomcat Web server webapps\rlm\WEB-INF\classes folder nolio-client.properties file.

See Configuring Release Automation Communication in Release Manager for details.

7: 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

See Configuration and Administration of the Integrating Objects for details.

8: 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: 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.

9: Customization

Complete customization and additional configuration as needed.

See Serena Release Manager Customization for details.