Configuring Cluster Elements
This procedure enables you to manage cluster elements. You can add and remove server processes, disable a cluster element, or view and edit its settings. If you change the properties of an element, the changes will apply only to the selected dispatcher or server process of the instance.
From the tree structure on the left side, select the cluster element you want to configure.
If You Want To |
Then |
Add a server process |
... 1. Select the instance to which you want to add the server process 2. Choose Server → Add Server |
Remove a server process
|
... 1. Select the server process you want to remove 2. Choose Server → Remove |
View or edit the JVM settings for a specific element
To take the changes effect, you have to restart the instance.
|
... 1. Select General 2. In Java settings pane you can view and edit: a. Java Home – Holds the path to the JDK that the J2EE Engine works with. b. Max heap size – The maximum size of heap memory used by the JVM. c. Java parameters – Contains additional parameters to be passed to the JVM. By default, no additional java parameters are available. d. Classpath – Holds the classpath to the bootstrap launcher file for a particular cluster element. e. Parameters – Contains program arguments used for starting a cluster element process.
We recommend that you do not change these parameters. 3. Enter the new value and choose File → Apply |
View or edit the bootstrap properties for a specific element |
... 1. Select Bootstrap 2. In Java settings pane you can view and edit: a. Max heap size b. Java parameters c. Classpath d. Parameters 3. Enter the new value and choose File → Apply
|
Disable a cluster element
To run the cluster element if it has been stopped, select this indicator, and stop and start the J2EE Engine to update the status.
|
1. Select General 2. Deselect the Execute indicator This indicator is selected by default and its function is to start the specified cluster element automatically when running the J2EE Engine. 3. Choose File → Apply
|
View or edit the debug properties for a server process.
This tab is available for server processes only. When you set a server process in debug mode, first make sure that you have stopped all message-driven beans running on that server process. In case your applications contain message-driven beans, whose destination type is Topic, you also have to start the message-driven beans on another server process. For more information, see Starting and Stopping Message-Driven Beans. |
1. Select Debug 2. Enter the new value of the following settings and choose File → Apply: a. Debuggable – specifies that the selected server process is debuggable (that is, the “debug mode” feature for this server process is enabled) b. Enabled debug mode – specifies whether the server process is in debug mode c. Restricted load balance – specifies whether the server process is part of the load balancing system. d. Debug port – enables debugger clients connections. This port is opened by the virtual machine and must not be among the ports that the J2EE Engine uses. By default, it is set to 50021.
|
View and edit the logging and tracing configurations of the J2EE Engine components and deployed applications |
Select Log Configuration. For more information about working with this tab, see Log Configuration.
|