Upgrading from Serena Release Manager v1.1 to v2.0

Step

Description

Actions

1

Back up files in target directories

(Optional) It is a good practice to snapshot your system or back up existing files and data before beginning the upgrade.

At minimum, you should back up as follows:

1. Copy the Serena Common Web services rlm folder, for example C:\Program Files\Serena\common\tomcat\6.0\
   webapps\rlm, to a temporary folder.

2. Copy the Serena\Solutions\Release Control folder, for example C:\Program Files\Serena\Solutions\Release Control, to a temporary folder.

3. Copy the files from the Serena Common Web services rlm\WEB-INF\classes folder, for example C:\Program Files\Serena\common\tomcat\6.0\
   webapps\rlm, to a temporary folder.

2

Copy the upgrade package to the Release Control directory

1. Delete the contents of the Serena\Solutions\Release Control folder. For example:

   C:\Program Files\Serena\Solutions\Release Control 

2. Copy the upgrade package, for example RC3.2-bbb-Win32-Upgrade.zip, to a temporary directory.

3. Extract the upgrade package to the Serena\Solutions\Release Control folder.

4. The following files should now appear under the Release Control folder:

• com.serena.rlm.sbm.shell.zip

• solution file

• RLM_Solution_Pack-2.0.m.bbb.sln, where m is maintenance release number bbb is build number

• war files

• rlm.war

• zmf.war

• zmfalf.war

• zmfws.war

• zmfalf_resource.properties

3

Configure the Web services files in the Serena Common Tomcat Web server

1. Select Start | Administrative Tools | Services and stop the Serena Common Tomcat service.

2. Navigate to the Serena Common Tomcat webapps folder. For example:

   C:\Program Files\Serena\common\tomcat\6.0\webapps

3. Delete the rlm folder.

4. Delete the rlm.war file.

5. From the Release Control folder where you extracted them in a preceding step, copy all of the war files to the Serena Common Tomcat webapps directory. For example:

   C:\Program Files\Serena\common\tomcat\6.0\webapps

6. Restart the Serena Common Tomcat service.

   This war file contents are extracted to new directories in that location. You should now see the following directories under webapps:

   rlm

   zmf

   zmfws

   zmfalf

7. From the Release Control folder where you extracted it in a preceding step, copy the alfzmf_resource.properties file to the Serena Common Tomcat webapps\zmfws\WEB-INF directory. For example:

C:\Program Files\Serena\common\tomcat\6.0\webapps\zmfws\WEB-INF

4

Install the solution file that contains the Serena Release Manager process apps and all related orchestrations, reports, and tables

1. From the Release Control folder, copy the solution pack .sln file, such as rlm_solution_pack_2_0.0.sln, to the SBM WEB-INF\solutions folder. For example:

C:\Program Files\Serena\SBM\Common\jboss405\server\
default\deploy\mashupmgr.war\WEB-INF\solutions

5

Import the Release Manager solution

1. Log into the SBM Application Repository as the SBM administrative user.

2. Navigate to the Solutions tab and import the  solution. For example:

   RLM_Solution_Pack 2.0.m.bbb,

   where m is maintenance release number and bbb is build number.

3. See Importing the Serena Release Control Solution.

6

Promote the snapshots

1. Navigate to the Process App Snapshots tab.

2. Promote the snapshots in the following order. When promoting the snapshots, make sure to select the endpoints as needed, and make sure the endpoints are authenticated with Single Sign-on.

   • Release Train

   • Application Release

   • Release Package

   • RLM_AUX

   • Deployment

   • Environment

   • ReleaseTemplate

3. Promote the following snapshots again to enable all fields to be created for two-way dependencies between process apps.

• Release Train

• Application Release

• Release Package

• RLM_AUX

• Deployment

IMPORTANT!  Make sure to check for any warnings after you have promoted the snapshots. For information on analyzing warnings or errors,, see Snapshot Promotion Errors.

For detailed instructions see Promoting the Snapshots.

7

Deploy the process apps

1. After the Serena Release Manager process apps are promoted to the correct environment, you must deploy the process apps from within SBM Composer. This validates the target endpoints prior to deployment to ensure that your environment is correctly configured.

   To redeploy the process apps:

   1. In SBM Composer, publish each of the Serena Release Manager process apps.

   2. After successfully publishing each process app, deploy each of the process apps.

NOTE  Follow the guidelines in the SBM documentation to deploy the Serena Release Manager process apps.

8

If you are changing the port on which the Serena Common Tomcat runs, reconfigure Serena Release Manager to use the new port number

1. If you are changing the port on which the Serena Common Tomcat runs, follow the instructions in Configuring Release Manager to Use a Different Port.

9

Install the shell user interface and report templates

1. Extract the com_serena_rlm_sbm_shell.zip file directly to the SBM Application Engine folder. For example:

   C:\Program Files\Serena\SBM\Application Engine\

   The files in the zip file should extract to the appropriate directory structure.

   Verify the extraction by looking at the dates of the files in the template\shell\rlm folder, for example C:\Program Files\Serena\SBM\Application Engine\template\shell\rlm. The files should have the date close to that of the upgrade package you used.

2. From SBM System Administrator, select File | Put Files Into Database. Confirm when prompted.

This puts the UI shell files into the SBM database.

10

Set privileges for the administrative user to the Serena Release Control objects, such as projects, reports, and tables

1. Set privileges for the new deployment process template objects and verify privileges are set for all other Serena Release Control objects.

See Configuring the Administrative User Privileges.

11

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

1. Enable the roles in the new Release Template project and verify that roles are enabled for all other Serena Release Control projects.

   See Enabling Serena Release Control Project Roles.

2. Verify that Serena Release Manager is activated by entering the URL in your Web browser. For example:

http://rlmhost/tmtrack/tmtrack.dll?shell=rlm

12

Configure the dashboard if needed

1. If your Dashboard page does not appear with the multi-view dashboard report, configure the dashboard. See Configuring the Dashboard Page.

13

Update the registry to ensure the proper version of Serena Release Control is registered for future reference

(Optional)

1. Manually update the key as follows:

   1. Edit the registry with a program such as Regedit.

   2. View the following key:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{F711E0DD-CAE6-4ADE-8CAA-8F54BB92214F}

   3. Modify DisplayVersion by changing the Value data entry to 3.2.0.

NOTE  This registry location has all the information that you will see in Windows Add/Remove programs and Programs and Features.

14

Update the configuration of the system, application objects, and providers as needed

1. Configure the communication and application objects as needed. See System Activation and Configuration, Configuration and Administration of the Integrating Objects, and Provider Configuration.

Changes for this release include the following:

• There are several new properties files to support the ZMF integration.

• The properties file for Serena Release Automation is now called nolio-client.properties. nolio.properties is no longer used.