Specifying a Different JDK/JRE Location
The installation of Universal Messaging, when performed using the Software AG Installer, includes the installation of a version of the JDK.
If you already have a JDK installed, you can change the Universal Messaging configuration to use your own installed JDK. Since Universal Messaging only requires the JRE component of the JDK, you can instead configure Universal Messaging to use your own installed JRE.
The JDK/JRE used by Universal Messaging is configured in the following configuration files. If you change the setup for the JDK/JRE in any of these files, you must make the same change in the other files also.
<Software_AG_directory>/UniversalMessaging/server/
<instanceName>/bin/Server_Tools_Common.conf
<Software_AG_directory>/UniversalMessaging/server/
<instanceName>/bin/Server_Common.conf
<Software_AG_directory>/UniversalMessaging/server/
<instanceName>/bin/ Custom_Server_Common.conf
Where present, this file is included by Server_Common.conf. Properties defined in Custom_Server_Common.conf override properties of the same name in Server_Common.conf. The purpose of Custom_Server_Common.conf is to allow you to add a layer of additional safety when changing system properties files.
If Custom_Server_Common.conf is not present or defines no properties, only the properties in Server_Common.conf will be used.
<Software_AG_directory>/UniversalMessaging/java/
<instanceName>/bin/Admin_Tools_Common.conf
<Software_AG_directory>/UniversalMessaging/java/
<instanceName>/bin/Samples_Common.conf
where <Software_AG_directory> is the default location for the installation of products using the Software AG Installer, and <instanceName> is the name of your Universal Messaging server. During the installation, a default server called "umserver" is created, so configuration files exist for this server.
In all cases, the setting to be updated is "wrapper.java.command=". To make the change, proceed as follows:
1. Open the configuration file in a text editor.
2. Locate the line that begins with "wrapper.java.command=". This line points to the current location of the JDK/JRE, for example:
wrapper.java.command=C:\SoftwareAG\jvm\jvm\bin\java.exe
3. Change the location to the location of your own installed JDK/JRE, for example:
wrapper.java.command=C:\MyWorkArea\MySetup\jvm\jvm\bin\java.exe
4. Save and close the file.
5. Make the same change in the other configuration files.
6. Stop and restart Universal Messaging.
You can use the Instance Manager to create a new instance of the Universal Messaging server. Each time you create a new instance, the following templates are used to create configuration files for the new instance. Therefore, if you wish to use your own installed JDK/JRE for all future instances of the server, you should modify the setting of wrapper.java.command in these templates:
<Software_AG_directory>/UniversalMessaging/server/templates/Server_Tools_Common.conf
<Software_AG_directory>/UniversalMessaging/server/templates/Server_Common.conf
<Software_AG_directory>/UniversalMessaging/server/
<instanceName>/bin/ Custom_Server_Common.conf
Where present, this file is included by Server_Common.conf. See the description earlier in this section for more details of Custom_Server_Common.conf.
<Software_AG_directory>/UniversalMessaging/java/EMtemplates>/Admin_Tools_Common.conf
<Software_AG_directory>/UniversalMessaging/java/templates/Samples_Common.conf
Note: Even if you use your own JDK/JRE, you should NOT remove the JDK that is installed with Universal Messaging; this JDK is required to run the Software AG Uninstaller, regardless of any other JDK/JRE you use.