Run the interactive server installer
The Deployment Automation interactive server installer uses a wizard to guide you through the process.
UNIX/Linux: The interactive server installer is available only for Linux and AIX. For other UNIX platforms, install the server manually. See Install server manually on UNIX.
To install Deployment Automation:
Download and extract the Deployment Automation server installer for your platform from the Software Licensing and Downloads portal (requires login).
Launch the installer.
As a Windows local system user, run the installer:
As a user with root privileges, run the installer:
Accept the license agreement.
Specify the path where you want to install Deployment Automation.
In the General Program Settings dialog box, select the location where settings will be saved. Click Change to select a different directory. Configure the following options:
Option Description Use existing settings Install the server using existing settings. This option maintains the current database. Skip database creation
Install on an additional server for high availability. This option does not overwrite the settings provided during the initial install.
If selected, decryption keys should be available in the DA user profile. The property skipEncKeysCreation (default value: true) is automatically added to the installed.properties file located in the DA server directory. When the server starts, random encryption keys are not created in the profile directory even if they do not exist. Hard-coded encryption keys are used instead.
To add decryption keys, copy the enc-keys directory from <existing profile location>/conf/server to <new profile location>/conf/server. Then restart the server.
JMS connection port Enter the JMS port that agents will use to connect to the server. Agent Mutual Authentication Configure increased security between agents and the server.
In the Database Selection dialog box, select a database type.
In the Database Details dialog box, edit the Database Connection String for your database.
Database Database Connection String Derby To use the built-in Derby database (for evaluation purposes only), enter a password for the database user and then click Next. SQL Server Use this format:
Oracle If you are using a service name, use the format:
If you are using an instance name, use the format:
Where da represents your Oracle SID.
Note: For Oracle databases, the schema name must be the same as the username.
PostgreSQL Use the format:
Tip: To change the database password after the installation, update the hibernate.connection.password property in the conf\server\installed.properties file. Default file location on Windows:
Then restart Common Tomcat where the Deployment Automation server is installed. If not yet encrypted, the hibernate.connection.password property will be encrypted after the server starts.
Enter the database username and password.
In the Administrator Details dialog box, enter the username and password to create a Deployment Automation administrator account. You will use this username and password to log in to Deployment Automation for the first time.
Note: Because you cannot change this account later, enter the username according to your organization's naming standards.
In the Configuration Details dialog box, enter the port number for Common Tomcat. The default port is 8080.
Windows: By default, Common Tomcat runs under the Windows System Account. To run it under a specific user, for example, when you are using network shares that Deployment Automation must have permission to access as part of its core processing, you must change the login information in the Common Tomcat service properties. The default service name is Micro Focus Common Tomcat 8. For details on changing Tomcat service properties, see the Apache Tomcat documentation.
Click Install. The installation finishes and the summary is displayed.
The properties set during the server installation are recorded in the installed.properties file stored in the profile directory.
Default location on Windows:
Deployment Automation is installed and connected to your database. You can now configure Deployment Automation by logging in to the web application using the administrator account you created.
To start configuring your system, continue with Administration.