Attributes and Operations
The following sections describe the attributes and operations used in the Java Management Interface.
Attributes
Each attribute corresponds to a CentraSite parameter. The name, type, access mode (R = read-only; RW = read and write), current value, and description of each of the following attributes are output, for example, through the CentraSite Java Management console.
cache size
The size of the cache, in megabytes. If you change this attribute, the CentraSite Registry or Repository is automatically restarted to activate the new value.
max threads
The maximum number of threads used. If you change this attribute, the CentraSite Registry or Repository is automatically restarted to activate the new value.
max users
The maximum number of users that can be active concurrently. If you change this attribute, the CentraSite Registry or Repository is automatically restarted to activate the new value.
non-activity timeout
The session timeout period, in seconds. If no activity has occurred in a session for this period of time, the changes are rolled back and the session is terminated. If you change this attribute, the change takes effect immediately.
state
The current state of the CentraSite Registry or Repository. You cannot change this value.
transaction timeout
The maximum transaction duration, in seconds. If you change this attribute, the change takes effect immediately.
Registry or Repository Start and Stop Operations
The CentraSite Java Management Interface provides access to the following operations. For each operation that has one or more parameters, the name, type, and description of each parameter are output and the value of each parameter can be input. If you access the CentraSite Java Management Interface using console software (for example, a web browser), the operation is initiated when you select Invoke.
Start the
CentraSite Registry or Repository
Stop the
CentraSite Registry or Repository in normal mode
Stop the
CentraSite Registry or Repository in the specified mode
Possible termination modes are:
Code | Meaning |
0 (normal) | Terminates the server session normally and waits for the current active processing to finish. The maximum waiting time (in seconds) can be set with the attribute transaction timeout. |
1 (rollback) | Terminates the server immediately. User transactions that have not finished are rolled back. |
2 (abort) | Terminates the server session immediately. The processing is immediately stopped. Crash dump files are written. Using this option initiates an automatic repair (autorepair) the next time the server is started. |
Back up the contents of the
CentraSite Registry or Repository. Write the backup file to the default location.
Back up the contents of the
CentraSite Registry or Repository. Write the backup file to the specified location.
Back up the CentraSite Registry or Repository, writing the backup file to the default location or to the specified location. In either case, the backup identification is returned. Also, the backup is listed in the output of the list all backups operation. A backup is done to freeze the current state of the CentraSite Registry or Repository.
Restore the contents of the
CentraSite Registry or Repository from the latest backup with or without recovery.
Restore the contents of the
CentraSite Registry or Repository from the specified backup with or without recovery.
The restore operation can only be used when the CentraSite Registry or Repository is not active. It is used to restore the CentraSite Registry or Repository to the state that was stored in a previous backup. If you want to restore the most recent backup, you do not have to specify the identification of the backup.
Repository changes that occur between one backup and the next are stored in session logs. When restoring from a backup, you can optionally include (with recovery) or omit (without recovery) the session log data.
Delete the specified backup file.
A backup that is no longer required can be deleted. Deleting a backup removes the backup spaces but the associated session log data is not removed, since it may be needed if the database has to be recovered. The backup file to be deleted is specified by means of the backup identification.
List all backups.
Creates a list of CentraSite Registry or Repository backups. Each entry contains the corresponding backup identifier.
Show more information about the last operation.
Shows additional information about the most recently processed command. Additional information can be displayed for the following operations: start, stop, back-up, restore, delete backup. If an operation fails, this command can be used to find the reason for the failure.