In interactive mode, you install the server by typing configuration
information on the command line.
Before you begin
- Make sure that you have a license server with available licenses.
See License management.
- Ensure that a supported version of a Java™ Runtime
Environment (JRE) or Java Development Kit (JDK) is
installed on the computer on which you are installing IBM UrbanCode Deploy. For more information, see System requirements. Supported JREs are included with the installation
files.
- Set the JAVA_HOME system variable to the location of
the JRE or JDK that you are using.
- If you are installing the server to be compliant with Federal Information Processing
Standards (FIPS), the computer must use a supported version of an IBM JRE or JDK.
- Ensure that the IBM JRE or JDK is a supported version and supported service refresh (SR) level.
For more information, see System requirements.
- If you are installing the server in a production environment, install and configure the
server database before you install the server. See Installing the server database. If you
are not installing in a production environment, you can install an instance of Apache
Derby during the installation steps. You can migrate the database to a different database
system later, as described in Migrating the server database.
- If you are using a database other than Apache Derby for the server, place the JAR file
for the database driver in the lib/ext folder of the installation
program.
- If you are installing on AIX®, the
unzip program is required.
- Make sure that your networks and firewalls allow communication
on the required ports. See Firewall and communication configuration.
- To install and run the server on Linux as a non-root user, create a user to use when you install and run the server. Also, ensure that the user has read and write permission to the folder to which you are installing the server.
- Ensure that there is no limit on the maximum memory size and virtual memory
size. For example, on most Linux systems, you can run the commands ulimit
-m and ulimit -v and ensure that they both return the value
unlimited. To find out how to remove the limit on the maximum memory
size and virtual memory size, see the documentation for the operating system.
If you are adding the server to a high-availability cluster, including as a cold standby server:
- Configure the high-availability cluster; see Setting up high-availability clusters.
- Ensure that the system on which you are installing the new server has a connection to
the cluster network storage and that the system can connect to the database that the
cluster is using.
- Each server in the cluster must run the same version of IBM UrbanCode Deploy.
- IBM UrbanCode Deploy is supported on Linux, but not on z/Linux.
For information about high-availability clusters, see
High availability and failover. For information
about cold standby, see
Adding cold standby servers.
About this task
The properties that are set during installation are recorded
in the file server_install/conf/server/installed.properties on
the server.
What to do next
To start the server, see
Starting and stopping the server.
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 import component versions, including built artifacts, you must
use an agent, and the server requires that you specify a default agent
for this purpose. 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 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 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.
On Windows, if you see "Out of memory" errors, increase the amount of memory that is available to the
IBM UrbanCode Deploy service. To increase the memory for the server on Windows for a non-service installation, follow these steps:
- Stop the server.
- In the bin/set_env.cmd file, increase the
memory in the JAVA_OPTS parameter.
- Restart the server.
For servers that are running as a service on Windows, see the following technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21698228.
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:
- 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.
- 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";
- Run the installation program again.