Reconfiguring Server Settings

If you need to reconfigure server settings for any reason, you can reconfigure them using the following procedure. For example, you may need to use this procedure if you specified the wrong connection information when you installed Deployment Automation, either through the SBM Configurator for the Release Manager installation or in the Deployment Automation standalone installer.

To reconfigure the server settings:

Stop the application server where Deployment Automation is installed.
Navigate to the directory or folder where the web application is installed. For example:
if you are using a JBoss application server, the typical location is:

..\program files\serena\SBM\Common\jboss405\server\default\deploy\serena_ra.war\conf

or

if you are using a Tomcat application server, the typical location is:

..\program files\serena\common\tomcat\7.0\webapps\serena_ra\conf
Backup the contents of the following file:
installed.properties
Edit the installed.properties file installLocation line to delete the path that follows the equal sign. You should have just the following on that line.
installLocation=

CAUTION:
There is another installed.properties file in the profile directory, so make sure you are only changing the one in the web application server directory structure.
Save the file.
Start the application server.
Enter the URL for the Deployment Automation web application. For example:
for Tomcat http://serverName:8080/serena_ra

or

for JBoss http://serverName:8085/serena_ra

The configuration panel should appear instead of the login page.

Enter the server settings as follows:

Setting	Description
Install Location	The path to the program installation location. For example, for native Release Manager installations: C:\Program Files\Serena\SBM\Automation Engine\ for standalone installations: (Windows) `C:\Users\<username>\.serena\ra` (UNIX/Linux) `/opt/serena/sra`
External Web URL	Specify the URL on which agents will be able to reach the server.
Agent Port	Specify the port on which agents will make JMS connections to the server.
Agent Mutual Authentication	Specify whether to use agent mutual authentication.
Skip DB Install	Do not install the database schema or seed data as part of the install. Select this is installing to a second or more server in a clustered installation.
Database Vendor	Select the database vendor. For example, Derby. Note: For example settings for all supported database selections, see the example settings used in Silent Mode Agent Installation.
Derby Port	The port that Derby should use for database connections
Database User	The user name to use to connect to the database
Database Password	The password to use to connect to the database
Confirm Database Password	Confirm the password to be used by the Deployment Automation administrator
Administrator User	The user name to be used by the Deployment Automation administrator
Administrator Password	The password to be used by the Deployment Automation administrator
Confirm Administrator Password	Confirm the password to be used by the Deployment Automation administrator

Click Install.

After you have saved the configuration settings, Deployment Automation detects that the configuration file exists and does not prompt you for them when the web application is invoked.