Installing the server in evaluation mode
To explore the features of IBM™ UrbanCode™ Deploy, install the server in evaluation mode.
- The following instructions are for exploring the features of IBM UrbanCode Deploy in evaluation mode. Do not follow these instructions if you are installing a production server. For instructions on installing a production server, see Installing the server in interactive mode.
- You can evaluate the product for a trial period of up to 60 days.
- 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 for IBM®
UrbanCode Deploy.Important:
For best results, download and use the latest available version of the IBM Java Runtime Environment (JRE) for the IBM UrbanCode Deploy server and agent relays. An IBM JRE is available as a separate download. See the IBM developer kits page to get the latest version. Install the IBM JRE according to the documentation on the page. Be sure to set the JAVA_HOME system variable to the location of the IBM JRE. If you are updating or changing the JRE to the latest version, see Changing or updating the JRE of servers and Updating the JRE location for agent relays for instructions. For documentation on the IBM JRE, see IBM SDK, Java Technology Edition.
Using JREs or Java development kits other than those provided by IBM might cause unexpected results.
- Set the JAVA_HOME system variable to the location of the JRE or JDK that you are using.
- Ensure that the IBM JRE or JDK is a supported version and supported service refresh (SR) level. For more information, see System Requirements for IBM UrbanCode Deploy.
- If you are installing on AIX®, the unzip program is required.
The properties that are set during installation are recorded in the file server_install/conf/server/installed.properties on the server.
- To specify a default agent, click 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. and under
- To specify a default agent tag, click 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. and under
- Stop the server.
- In the bin/set_env.cmd file, increase the memory in the
JAVA_OPTS
parameter. - Restart the server.
[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 thegrant{}
block, add the following code:permission java.net.SocketPermission "localhost:11377", "listen";
- Run the installation program again.