Managing BMC AMI Ops user interface
The following topic provide instructions that can help you manage the BMC AMI Ops User Interface (BMC AMI Ops User Interface) server.
Starting and stopping the BMC AMI Ops User Interface server
The BMC AMI Ops User Interface server is a web server that is installed on the mainframe as part of the BMC AMI Ops Infrastructure standard installation.
The default procedure name is MUXTCJCL. Replace the name with the procedure name you specified when you installed the component.
- To start the BMC AMI Ops User Interface server, in the spool (SDSF), use the /S MUXTCJCL command.
- To stop the BMC AMI Ops User Interface server, in the spool (SDSF), use the /P MUXTCJCL command.
Modifying the BMC AMI Ops UI properties
The application.properties file, located on the BMC AMI Ops User Interface server in the installationDirectory/amiops/config directory, contains properties that you can modify to better fit your organization's needs
After you change a property value, you must restart the BMC AMI Ops User Interface server.
Property | Default value | Description |
|---|---|---|
request.timeout | 60 | Number of seconds before a request from the server to the service times out The value must be less than the client.request.timeout value. |
token.timeout | 15 | Number of minutes before the access token times out and the user must log in again The value must be 5 minutes or higher. |
timeout | 60 | For internal use only, request timeout in seconds |
client.request.timeout | 75 | Number of seconds before a client request to the server times out The value must be greater than the request.timeout value. |
workDir | Not applicable | User-defined file path for the config directory BMC AMI Ops User Interface configurations, such as dashboards and user preferences, are saved in this directory. |
ami.ops.ui.log.level | INFO | Logging level for the server Valid values are ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, and OFF |
secure.cookie | true | Whether the browser cookie is sent only over HTTPS If set to false, the cookie can also be sent over HTTP. For more information, see To enable BMC AMI Ops UI use with HTTP in the "Configuring the BMC AMI Ops user interface" topic. |
idle.timeout and idle.timeout.username | -1 and Not applicable | The idle.timeout and idle.timeout.username properties must be used together. You might want to use these properties, for example, when dashboards and alarms are displayed on a large screen in a control room. The idle.timeout property is the number of minutes before the session times out and the user must log in again A value of -1 means the session never times out. Otherwise, the value must be 5 minutes or higher. The idle.timeout.username property is the user name of one user for which the idle.timeout applies. |