Configuring Release Manager

In the Release Manager dialog box, you configure Release Automation settings for Release Manager. Select the Configure Release Manager check box to begin configuring these settings. If you do not plan to use Serena Release Manager and you only want to use Serena Service Manager, do not select this check box.

Note: For distributed installations, you configure these settings directly on the server that hosts SBM Common Services.

In the Release Manager Settings sub-tab, you select which Release Automation instance you plan to use with Release Manager.

Select one of the following options:

Use native Release Automation instance – Select this option if you are installing Release Manager for the first time. Release Manager will use the version of Release Automation that is locally installed on the SBM Common Services server and powered by Serena Common JBoss.
Use standalone Release Automation instance – Select this option if you have previously installed a standalone version of Release Automation, and you want to use it with Release Manager.

Important: The ZMF plugin requires a Tomcat application server. This means that if you intend to use the ZMF plugin with Release Manager, you must use a standalone Release Automation instance (because the native instance only runs under JBoss).

Configuring Standalone Release Automation Settings

If you select the standalone version, enter the following information in order for Release Manager to connect to your existing Release Automation instance:

Field Name	Description
Application container	Select the application container that is used by your Release Automation instance in the drop-down list. If your existing instance uses something other than JBoss or Tomcat, select Other.
Host	Enter the host name of the server that hosts your Release Automation instance. Click Test Connection to verify that a connection can be made to the server.
Use HTTP port	Enter the HTTP port number that is used to connect to your Release Automation instance. The default HTTP port is 8080.
Use HTTPS port	Enter the HTTPS port number that is used to connect to your Release Automation instance if you use secure connections. The default HTTPS port is 8443.
AJP13 port	Select the AJP13 port. The default port for Tomcat is 8409. The default for JBoss is 6009. The default value changes automatically for you depending on the application container you select.

Configuring Native Release Automation Settings

The Native Release Automation Settings sub-tab appears if you select Use native Release Automation instance. In the Native Release Automation Settings sub-tab, you configure administrative settings and database connection settings.

Important: The native Release Automation settings cannot be changed using SBM Configurator after they have been applied the first time. If you need to change these settings later, refer to the Serena Release Manager - Release Automation User's Guide for assistance.

Configure the following:

Field Name	Description
Profile location	Enter the code station path where your artifacts will be stored. Consider using a dedicated partition to store the physical files in order to save operating disk space for SBM.
Agent mutual authentication	Select this option for agents to use SSL mutual authentication. If not selected, agents will use unauthenticated mode; communication is encrypted but users do not have to authenticate or verify their credentials. For more information, refer to the Serena Release Manager - Release Automation User's Guide.
Agent port	Enter the port to use for JMS-based server/agent communication. This is the port on which the Release Automation agents that you install will make JMS connections to this server.
Skip database install	Select this check box if you need to skip the database initialization process. For example, if you have clustered SBM Common Services, clear this check box on the first node that you configure (which initializes the database), and then select this check box on all remaining nodes in order to prevent the creation of multiple databases.
Administrator user	Enter an administrator user name. This is the user name that is required to log into the server the first time.
Password	Enter the administrator's password.
Confirm password	Enter the password again to confirm it.

In the Database type drop-down list, select the type of DBMS (SQL Server or Oracle) that will host the Release Automation database, configure the following settings (depending on the DBMS that you select).

Table 1. SQL Server Database Settings

Field Name	Description
Host	Enter the host name of your database server.
Instance	The name of the SQL Server instance. Provide an instance name if more than one instance exists in SQL Server.
Port	Enter the database server port number. The default SQL Server port is 1433.
Database name	Enter the name of the database. For example `serena_ra`.
User	Enter the name of a privileged DBMS user account. Note: For SQL Server databases, enter a SQL Server user account, not a Windows user account.
Password	Enter the user's password.
Confirm password	Enter the password again to confirm.

Table 2. Oracle Database Settings

Field Name	Description
Host	Enter the host name of your database server.
Service name	Enter the Oracle Service Name. This identifies the service name that hosts your Oracle schema.
Port	Enter the database server port number. The default SQL Server port is 1433. The default Oracle port is 1521.
Schema/User (Oracle only)	Enter the Oracle schema name. (The default is `serena_ra`.)
Password	Enter the user's password.
Confirm password	Enter the password again to confirm.

Click Create Database, and then use an administrator account (such as "sa" for SQL Server or "system" for Oracle) to create the Release Automation database in your DBMS. If successful, the database is created using the database name and user specified above.