In interactive mode, you install the server by typing configuration
information on the command line.
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.