- Open a command console.
-
Locate your JDK installation directory.
For example, the JDK directory may be java/bin.
-
Enter the following command:
jconsole
The JConsole New Connection window displays.
-
Double-click on the SkyVault Java process.
For Tomcat, this the Java process is usually labelled as org.apache.catalina.startup.Bootstrap start.
JConsole connects to the managed bean (or MBean) server hosting the SkyVault subsystems.
-
Select the MBeans tab.
The available managed beans display in JConsole.
-
Navigate to SkyVault >
Configuration.
The available SkyVault subsystems display in an expandable tree structure. When you select a subsystem, the Attributes and Operations display below it in the tree.
-
Select Attributes and set the required SkyVault subsystem attribute values.
Values that can be edited are shown with blue text.
When you change a configuration setting, the subsystem automatically stops.
-
Restart the SkyVault subsystem:
- Navigate to the subsystem.
- Select Operations.
- Click Start.
-
To stop the SkyVault subsystem without editing any
properties:
- Navigate to the subsystem.
- Select Operations.
- Click Stop.
-
To revert back to all the previous edits of the SkyVault subsystem and restores the default
settings:
- Navigate to the subsystem.
- Select Operations.
- Click Revert.
- Click Connection > Close.
- When a subsystem, that is currently running, is stopped, its resources are released and it stops actively listening for events. This action is like a sub-part of the server being brought down. This ‘stop’ event is broadcast across the cluster so that the subsystem is brought down simultaneously in all nodes.
- The new value for the property is persisted to the SkyVault database.
There are two ways to trigger a subsystem to start:
- The start operation
- An event that requires the subsystem