Current State

The operational state of the EPM server.

The options are:

• Booting: The EPM server is in the process of restarting and is not yet ready to take new requests.

• Degraded: The EPM server is running but it is not functioning at full capacity.

• Error: The EPM server has encountered a severe problem and cannot recover.

• Halted: The EPM server is no longer responding to heartbeats because it received a Halt command.

• Halting: The EPM server is responding to heartbeats but is not taking new requests.

• Need configuration: An Email or SMS processor residing on the EPM server has not yet been configured.

• Need connections: No connections (SMPP or HTTP) have been configured or assigned to an Email/SMS processor residing on the EPM server.

• Never used: The EPM server has never successfully responded to a heartbeat request.

• Not installed: The EPM server is missing files required for heartbeat requests to occur.

• Not responding: The EPM server is not responding to heartbeat requests and it has not received a Restart or Halt command.

• Partially Running: The EPM server is in the process of starting up, and not all individual components of the service, such as Tomcat, SL, ActiveMQ, have come up yet.

• Rebooting: The EPM server is responding to heartbeats but is not taking new requests.

• Recovering: The EPM server has encountered a problem and is attempting to recover.

• Restart Needed: This state is most often reached when the EPM server has encountered a problem that it cannot recover from and it requires a manual restart.

• Running: The EPM server is responding to heartbeat requests and is accepting new requests.

• Starting: The EPM server is responding to heartbeats but not taking new requests because it is transitioning from the Stopped state to the Running state.

• Stopped: The EPM server is responding to heartbeats but is not taking new requests. The EPM server enters this state while it initializes after it restarts or when a Stop command is received.

• Stopping: The EPM server is responding to heartbeats but is not taking new requests.

• Unknown: The EPM server is in the Offline mode.

Requested State

If the EPM is in the process of changing states, this field shows the state that the user requested and the time at which the request was made.

Current Mode

The operational mode of the EPM server.

The options are:

• Online: The EPM server is available.

• Offline: The EPM server is unavailable.

Current

The current number of conversations in the database.

Peak

The overall maximum number of conversations that existed in the database at any given time.

Maximum

The maximum number of conversations that can be created.

Partition that contains

The partitions for the Avaya Experience Portal directory that contain the root folder, Avaya Home, Application Server, and Database.

Disk Usage (%)

The percentage of hard disk utilization for the partitions that contain the root folder, Avaya Home, Application Server, and Database respectively

Database Version

The version number of the postgres database.

Database Size

The postgres database size in bytes.

Show Top Ten

Shows the top 10 postgres database tables and the corresponding size, in bytes.

This link is displayed only if Show All is selected.

Show All

Shows all the postgres database tables and the corresponding size, in bytes.

This link is displayed only if Show Top Ten is selected.

Table Name

The names of the database tables.

Size (bytes)

The size of the database tables, in bytes.