Performing a distributed installation
Performing a distributed installation of ArcGIS Server for the Java Platform installs ArcGIS Server on multiple machines, to provide better performance and scalability.
In this installation scenario, the server object manager (SOM) will be installed on one machine and the server object container (SOC) will be installed on one or more additional machines.
Installation guidelines
- ArcGIS Server cannot be installed to the same location as any other ArcGIS product.
- No other ArcGIS product can be installed as the ArcGIS Server user.
- If ArcGIS Server is installed on a machine, you will only be able to install another ArcGIS product in single user mode (not in multiuser mode).
How to prepare to install ArcGIS Server for the Java Platform
- Obtain an authorization file for each of the machines you will be installing the ArcGIS Server server object container on.
- Verify that your site meets the system requirements. For system requirement information, see Step 1: Verify system requirements.
- You are required to install ArcGIS Server as root; however, you will be given an opportunity during the installation process to assign the files to the ArcGIS Server user. The user that you assign the files to must have full permissions to the ArcGIS Server installation directory. Group users and all others must have at least execute permissions to the ArcGIS Server installation directory.
- Insert the ArcGIS Server for the Java Platform media into the
appropriate drive.
Linux users: It is recommended that you install ArcGIS Server for the Java Platform to a mounted drive. If you do not, some files will be left after uninstallation.
Installation location: The name of the installation directory should be in lowercase letters. The samples and data installed require the data path to be lowercased.
ArcGIS Server authorization
The ArcGIS Server server object container requires an authorization file. Each machine installing this feature will require a valid authorization file. See To obtain an authorization file for more information.
If you installed the server object container, the installation configures your machine using the authorization file you received from ESRI Customer Service.
How to perform a distributed installation of ArcGIS Server for the Java Platform
- Install the SOM component on machine1 as user1/passwd1. See Installing Server Object Manager for instructions on installing SOM. During the setup, the installation prompts for the user name that will have ownership of the SOM files and process. Provide user1 as the SOM user, and provide passwd1 if necessary.
- In ArcGIS Server Manager on machine1, accessible at http://<machine1>:8099, navigate to GIS Server > Users and add user1/passwd1 to the user list.
- Install the SOC component on machine2 as user2/passwd2. See Installing Server Object Container for instructions on installing SOC. During the setup, the installation prompts for the fully qualified domain name of the SOM machine that this SOC machine will connect to. Provide the FQDN of machine1 as the SOM machine. The installation also prompts for the user name that will have ownership of the SOC files and processes. Provide user2 as the SOC user, and provide passwd2 if necessary.
- In ArcGIS Server Manager on machine1, accessible at http://<machine1>:8099, navigate to GIS Server > Users and add user2/passwd2 to the user list.
- In ArcGIS Server Manager on machine1, accessible at
http://<machine1>:8099, navigate to GIS Server > Host
Machines (SOC) and add machine2 to the machine list.
Add user1 and user2 to the user list before adding machine2 to the SOC machine list.
- Configure log, cache, output, and jobs directories on machine1.
The default log folder on machine1 is located at <ArcGIS Server Installation Location>/server/user/log. It must be accessible by user2 on machine2.
You can change the log folder in ArcGIS Server Manager by navigating to GIS Server > Log Files > Log Properties.
Navigate to GIS Server > Server Directories to add cache, output, and jobs directory. For detailed information about how to add server directories, see the ArcGIS Server Manager help content on "Creating a server directory (Manager)."
On Linux/Solaris, the default directory of each type is created if both SOM and SOC components are installed. The default location is <ArcGIS Server Installation Directory>/server/serverdir.
- For the SOM only install, you can manually create arcgisoutput, arcgiscache, and arcgisjobs directories under <ArcGIS Server Installation Directory>/server/serverdir on machine1. Add these folders to the virtual directory through ArcGIS Server Manager.
- The virtual directories must be accessible by user2 from machine2.
- Run <SOC Installation Location>/scripts/stopserver and <SOC
Installation Location>/scripts/startserver to restart ArcGIS Server
on machine2.
When stopping and immediately restarting ArcGIS Server, allow 25–30 seconds after stopping the server before running the startserver script. This will ensure that all the processes are properly shut down before restarting.
- Run <SOM Installation Location>/scripts/stopserver and <SOM
Installation Location>/scripts/startserver to restart ArcGIS Server
on machine1.
- When stopping and immediately restarting ArcGIS Server, allow 25–30 seconds after stopping the server before running the startserver script. This will ensure that all the processes are properly shut down before restarting.
- The data and resources used in creating services must be accessible by user2 on machine2.
If you are installing SOCs on more than one machine, configure them using the same procedure described for machine2 (steps 3–8).
If you are installing SOM on an additional machine for failover in case the primary SOM machine goes down, configure it using the same procedure described for machine1. Each SOC machine will need to be configured to connect to the secondary SOM machine if the primary SOM machine is unavailable. On each SOC machine, run <SOC Installation Location>/servercore/tools/failover/addIdentityServer.sh as the SOC user for that machine. Enter the fully qualified domain name of the secondary SOM machine.