Installing the server in silent mode

In silent mode, you specify the installation properties in a text file and then run the installation without command-line prompts.

Before you begin

About this task

You specify the installation properties in the install.properties file, which is located in the root folder of the installation files. During the installation process, the server stores these properties in the installed.properties file, which is in the conf/server folder of the server installation files. If you have an already existing installation, you can use its installed.properties file as an example of the properties.

Procedure

  1. Download and extract the installation files for IBM UrbanCode Deploy. These files are available for download from the IBM Passport Advantage® website. See the IBM UrbanCode Deploy download document.
  2. If you are using a database other than Apache Derby, place the JAR file for the database in the lib/ext folder of the installation files.
  3. In the installation files, open the install.properties file in a text editor and add the following line of code to the end of the file:
    nonInteractive=true
    The file looks similar to the following example:
    component.name=IBM UrbanCode Deploy
    component.directory=ibm-ucd/server
    version=6.0.0.0.123456
    nonInteractive=true
  4. Customize the installation by specifying the properties in the following table. If you do not specify a property, the default value is used. These properties are copied to the installed.properties file of the completed installation.
    Table 1. Installation properties
    Property Default value Description
    database.derby.port 11377 The port for the Derby database. This property is used only for Derby databases.
    database.type
    derby
    The type of database. Valid values are derby, mysql, oracle, sqlserver, postgres, and db2.
    Warning: Derby is for evaluation purposes only; do not use Derby on a production server.
    encryption.keystore ../conf/encryption.keystore The path to the encryption key store.
    encryption.keystore.alias desedekeyuniqueID The encryption key store alias.
    hibernate.connection.driver_class The default value depends on the type of database. The class name of the database driver, such as com.ibm.db2.jcc.DB2Driver for DB2 or org.apache.derby.jdbc.ClientDriver for Derby.
    hibernate.connection.password password The password for the database connection. This password is encrypted during the installation process.
    hibernate.connection.url jdbc:derby://localhost:11377/data The connection URL for the database. For more information on building a database connection string, refer to documentation from your database provider.
    hibernate.connection.username ibm_ucd The user name for the database connection. Unless skip.db.install is set to Y, this user must have permission to create tables in the database.
    hibernate.default_schema None. The name of the database schema. This property is required only for Oracle databases on Windows.
    install.java.home The value of the JAVA_HOME system variable The location of the installation of Java to use.
    install.server.dir
    /opt/ibm-ucd-6.0/server
    (Linux) or
    C:\Program Files\ibm-ucd\server
    (Windows)
    The installation directory for the server.
    install.server.web.always.secure Y Specify Y to always use secure connections to the server. Specify N to allow non-secure connections.
    install server.web.host The host name of the server. If you are installing a stand-alone server, specify the host name of the computer that hosts the server. If you are installing a stand-alone server in a production environment, consider using a host name that is not tied to the physical computer, so you can expand the server to a high-availability system later. If you are installing a server in a cluster, specify the host name of the load balancer for the cluster.
    install.server.web.https.port 8443 Specify the HTTPS port for the server. The default value is 8443. If you are installing IBM UrbanCode Deploy and IBM UrbanCode Release, be sure to use a different port for each product.
    install.server.web.ip 0.0.0.0 The IP address that the server listens on.
    install.server.web.port 8080 Specify the HTTP port for the server. The default value is 8080.If you are installing IBM UrbanCode Deploy and IBM UrbanCode Release, be sure to use a different port for each product.
    rcl.server.url None. Specify the connection information for the license server. You can specify the port and host name or IP address for the license server, such as 27000@RCLServer.example.com. To avoid problems when a license server is not available, you can specify multiple license servers. In this case, separate each address with colons on Linux and UNIX or semicolons on Windows, as in the following example: 27000@RCLServer.example.com;27000@backupRCLServer.example.com . For more complicated license server scenarios, see this document: http://pic.dhe.ibm.com/infocenter/rational/v0r0m0/index.jsp?topic=/com.ibm.rational.license.doc/topics/r_specify_lic_servers.html

    For more information about licensing, see Managing licenses.

    server.jms.mutualAuth false Specify true to require mutual authentication between servers and agents. See Configuring mutual authentication.
    server.jms.port 7918 Specify the port that agents use to contact the server. The default value is 7918.
    server.keystore None. The path to the key store.
    server.keystore.password changeit The password for the key store. This password is encrypted during the installation process.
    skip.db.install N If the value is Y or yes, the installation process does not create the database schema. For example, you skip creating the schema if you have a pre-populated database, such as if you are adding a server to a cluster. In this case, you must still provide the database connection information in the other properties such as hibernate.connection.url.
    The file looks similar to the following example:
    component.name=IBM UrbanCode Deploy
    component.directory=ibm-ucd/server
    version=6.0.0.0.123456
    nonInteractive=true
    
    install.server.dir=/opt/ibm-ucd/server
    install.java.home=/opt/IBM/ibm-java-i386-60
    install.server.web.always.secure=Y
    install.server.web.host=myserver.example.com
    install.server.web.https.port=8443
    install.server.web.ip=0.0.0.0
    install.server.web.port=8080
    database.type=derby
    hibernate.connection.username=ibm_ucd
    hibernate.connection.password=password
    hibernate.connection.url=jdbc:derby://localhost:11377/data
    database.derby.port=11377
    rcl.server.url=27000@RCLServer.example.com
  5. Save the file.
  6. Run the installation file with the command install-server.bat on Windows or the command ./install-server.sh on Linux.

Results

The installation program installs the server.

What to do next

To start the server, see Running the server.
If you are using Derby, you might see the following error in the results of the installation program:
[echo]     waiting for db to start - 6 seconds remaining
[echo]     waiting for db to start - 3 seconds remaining
[echo] Could not start database
[echo] Stopping embedded database ...
[java] Tue Feb 04 09:11:25 EST 2014 : Could not connect 
  to Derby Network Server on host localhost, port 11377: 
  Connection refused
If you see this error, you must change the default security settings for the Java installation on the server:
  1. Open the Java security policy file in a text editor. If you are using a Java Runtime Environment (JRE), this file is at the location JAVA_HOME/lib/security/java.policy, where JAVA_HOME is the base folder of the Java installation. If you are using a Java Development Kit (JDK), the file is at the location JAVA_HOME/jre/lib/security/java.policy.
  2. In the java.policy file, in the section that is labeled // default permissions granted to all domains, within the grant{} block, add the following code:
    permission java.net.SocketPermission "localhost:11377", "listen";
  3. Run the installation program again.
When you run the server for the first time, you might see an error message that says that no agent or tag is configured to import new component versions. To make this error go away, you must specify a default agent or agent tag to use when importing component versions. You can override this default setting when you create a component. Follow these steps to specify a default agent or agent tag:
  • To specify a default agent, click System > System Settings and under General Settings, clear the Use Agent Tag For Integration check box. Then, select an agent in the Agent for Version Imports list. Then, at the bottom of the page, click Save.
  • To specify a default agent tag, click System > System Settings and under General Settings, clear the Use Agent Tag For Integration check box. Then, select an agent tag in the Agent Tag for version imports list. Then, at the bottom of the page, click Save. If no tags are listed add a tag to one or more agents on the server.

Feedback