Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure Coherence servers

To configure existing Coherence servers:

  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.

    The Coherence servers table displays all the Coherence servers defined in the domain.

  3. Select the name of the server you want to configure.
  4. On the Coherence Server Properties page, adjust the server properties values as needed.
    1. Enter the name of the server in the Name field.

      The server name is not used as part of the URL for applications that are deployed on the server. It is for your identification purposes only. The server name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the server.

    2. Select an existing Machine (WebLogic Server host computer name on which this server is meant to run) from the drop down list.

      In order to use Node Manager to start this Coherence server, you must assign the server to a machine and you configure the machine for the Node Manager. See Create and configure machines.

    3. Optional. In Cluster, enter the system-level Coherence cluster resource associated with this server.
    4. Optional. In Unicast Listen Address, enter the IP address for the cluster unicast listener. This attribute may be used to override the value of the referenced Coherence cluster.
    5. Optional. In Unicast Listen Port, enter the port for the cluster unicast listener.
    6. Optional. Use the Unicast Port Auto Adjust check box to specify whether the unicast port will be automatically incremented if the port cannot be bound because it is already in use.
    7. Optional. Use the Auto Restart Enabled check box to specify whether the Node Manager can automatically restart this server if it crashes or otherwise goes down unexpectedly.
    8. Optional. In Restart Interval, enter the number of seconds during which this server can be restarted, up to the number of times specified in Restart Maximum Tries.
    9. Optional. In Restart Maximum Tries, enter the number of times that the Node Manager can restart this server within the interval specified in Restart Interval.
    10. Optional. In Restart Delay, enter the number of seconds the Node Manager should wait before restarting this server.
    11. Optional. In Node Manager Connect Timeout, enter the timeout value in milliseconds to be used by the Node Manager when creating a socket connection to the agent.
  5. When you are finished making changes, click Save.
  6. 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).

Back to Top