Installation notes for the Web ADF

The ArcGIS Server 10 for the Java Platform ADF includes a set of Web controls and a Web Mapping Application. The Web Mapping Application demonstrates how to use the Web controls. The following information will explain how to configure the ArcGIS Server 10 for the Java Platform ADF.

These steps assume that the ArcGIS server object manager is running and that you have created at least one MapServer object.

The following is available:

Web Mapping Application—Web application with basic map navigation capabilities

For more information on the Web Mapping Application, see the ArcGIS Server Help.

How to set up your machine to use the ADF

The following steps are required to use the ArcGIS Server 10 for the Java Platform ADF Web controls and Web Mapping Application:

1. Verify J2SE SDK is installed. See the system requirements for supported J2SE SDK versions.

2. Set the environment variables.

3. Verify that you have a supported Web server and servlet engine/application server installed. See the system requirements for supported Web servers and servlet engines. Sun Java system (formerly Sun ONE) Application Server users should review Additional steps for Sun Java system (formerly Sun ONE) Application Server users below. For WebLogic Server, ,see Additional steps for BEA WebLogic Server users below.
4. To build and deploy Web applications from the ArcGIS Server for the Java Platform ADF Web Mapping Application, follow the directions for the supported Web server/servlet engine you are using.

Instructions for performing steps 2 and 3 above are provided below. Step 1 should have already been completed.

Once these steps have been completed, Another Neat Tool (Ant) is used to build and deploy applications using the Web Mapping Application. See the ArcGIS Server Help for information.

How to set the environment variables

Add the following to your system path environment variable:

PATH=%AGSSERVERJAVA%\java\tools\ant\bin

• The environment variable %AGSSERVERJAVA% was created during the ArcGIS Server 10 for the Java Platform setup; %AGSSERVERJAVA% is the ArcGIS Server for the Java Platform installation location.

• Set the JAVA_HOME environment variable to the installation location of J2SE SDK. For example:

  JAVA_HOME=C:\j2sdk1.4.2_06

For WebSphere Application Server, set the JAVA_HOME environment variable to the J2SE SDK installed with WebSphere Application Server.

For example:

JAVA_HOME=C:\Program Files\WebSphere\AppServer\java

If you will be using the Apache Web server, append

;%JAVA_HOME%\bin

to the system path variable.

Arcgisant (the tool you will use for building Web applications) uses the J2SE SDK to encrypt the GIS server password in the Web application. Once the Web application is deployed on a Web server, the Web server will decrypt the password at run time.

Additional steps for BEA WebLogic Server users

If you are using BEA WebLogic Server, you will need to edit your commEnv.cmd file. The commEnv.cmd file is located in a similar installation location to <WebLogic installation directory>\bea\weblogic81\common\bin\commEnv.cmd. Open the commEnv.cmd file in a text editor and add the following line after the comments at the beginning of the file:

set AGS_HOME=<ArcGIS Server for the Java Platform ADF Installation Directory>\ArcGIS

For example:

set AGS_HOME=C:\Program Files\ArcGIS\Server10.0

Also, locate the WEBLOGIC_CLASSPATH variable setting and change it to the following:

set WEBLOGIC_CLASSPATH=%AGS_HOME%\java\lib\arcobjects.jar;
%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;
%WL_HOME%\server\lib\weblogic.jar;%WL_HOME%\server\lib\ojdbc14.jar

The arcobjects.jar file must be the first entry in the WebLogic class path. Restart WebLogic Server.

Additional steps for Sun Java system (Sun ONE) Application Server users

If you are using Sun Java system (Sun ONE) Application Server, you will need to edit your server.policy file. The server.policy file is located in a similar installation location to <Sun Java System (Sun ONE) Application Server installation directory>/Appserver7/domains/domain1/server1/config/server.policy (for version 7) or <Sun Java System (formerly Sun ONE) Application Server installation directory>/Appserver/domains/domain1/config/server.policy (for version 8). Open the server.policy file in a text editor and add the following lines to the end of the file:

grant {
permission java.util.logging.LoggingPermission "control", "";
permission java.lang.RuntimePermission "shutdownHooks";
permission java.lang.RuntimePermission "modifyThread";
permission java.lang.RuntimePermission "stopThread";
permission java.util.PropertyPermission 
"JINTEGRA_RELEASEALL_SHUTDOWN_HOOK", "write";
permission java.util.PropertyPermission 
"JINTEGRA_IUNKNOWN_VARIANT_OBJECTS", "write";
};

Additional steps for Tomcat users if SecurityManager is in us:

If you are using Tomcat with SecurityManager, you will need to edit your catalina.policy file. The catalina.policy file is located at %CATALINA_HOME%\conf\catalina.policy. Open the catalina.policy file in a text editor and add the following lines to the end of the file:

grant {
permission java.util.logging.LoggingPermission "control", "";
permission java.lang.RuntimePermission "shutdownHooks";
permission java.lang.RuntimePermission "modifyThread";
permission java.lang.RuntimePermission "stopThread";
permission java.util.PropertyPermission 
"JINTEGRA_RELEASEALL_SHUTDOWN_HOOK", "write";
permission java.util.PropertyPermission
"JINTEGRA_IUNKNOWN_VARIANT_OBJECTS", "write";
permission java.net.SocketPermission "<hostname>:8080", "connect,resolve";
permission java.net.SocketPermission "<hostname>:135", "connect,resolve";
permission java.net.SocketPermission "<hostname>", "connect,resolve";
permission java.io.FilePermission "C:/j2sdk1.5/jre/lib/rt.jar", "read";
}

where

<hostname> is the name of the machine Tomcat is running on.

Change the port numbers and path to the J2SE SDK as appropriate. Restart Tomcat with SecurityManager as follows:

%CATALINA_HOME%\bin\catalina start -security