# Configure startup arguments for Coherence servers

Specify the startup settings that Node Manager will use to start this Coherence server on a remote machine.

Note: The Coherence servers feature is deprecated and remains supported for backwards compatibility. Coherence tiers should be configured to use Managed Coherence Servers instead. See Configure and deploy Coherence deployment tiers

To configure startup options:

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
2. In the left pane of the Console, expand Environment and select Coherence Servers.
3. In the Coherence Servers table, select the name of the Coherence server you want to configure.
4. Select Configuration > Server Start.
5. Specify the following startup settings:
   1. Java Home - Specify the Java home directory (path on the machine running Node Manager) to use when starting this server. Specify the parent directory of the JDK's bin directory. For example, `c:\Oracle\Middleware\jdk1.7.0_10`.
   2. Java Vendor - Specify the Java vendor value to use when starting this server.
   3. Oracle Home - Specify the directory on the Node Manager machine under which all of Oracle's WebLogic products were installed. For example, `c:\Oracle\Middleware\`.
   4. Root Directory - Specify the directory that this server uses as its root directory. This directory must be on the computer that hosts the Node Manager. If you do not specify a Root Directory value, the domain directory is used by default.
   5. Class Path - Specify the classpath (path on the machine running Node Manager) to use when starting this server.

      The operating system determines which character you use to separate path elements. On Windows use a semicolon (;). On UNIX use a colon (:).

   6. Arguments - The arguments to use when starting this server. These are the first arguments appended immediately after `java` portion of the startup command. Separate arguments with a space.
6. Click Save.
7. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
   Not all changes take effect immediately—some require a restart (see Use the Change Center).