...
The Controller installation process writes the values for some command line switches to the Properties#Universal Universal Controller Start-up Properties (opswise.properties), uc.properties (see the table, below). For any of those command line switches that are not required and, in fact, are not included on the command line, the Controller installation process writes their default value to uc.properties.
...
For command line switches that have their value written to the Properties#Universal Universal Controller Start-up Properties (uc.properties), uc.properties, the table also identifies the property in that file to which the value is written.
...
Command Line Switch | Description | Default | Required | Controller Property | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| For an Agent-Only deployment If | false | No | ||||||||||||||
| Full path of the Universal Controller war file ( | none | Yes | ||||||||||||||
| Universal Controller database name.
| uc | No | uc.db.name | |||||||||||||
| Database user's password. | none | Yes | uc.db.password | |||||||||||||
| JDBC connect URL.
| jdbc:mysql://localhost:3306/ | No | uc.db.url | |||||||||||||
| Database user name. | none | Yes | uc.db.user | |||||||||||||
| Used by the Universal Controller to generate a unique Cluster Node Node Id in the format of hostname:port-dbname.
| 8080 | No | uc.servlet.port | |||||||||||||
| Database type.
| mysql | No * | uc.db.rdbms | |||||||||||||
| Path to the Tomcat installation directory (contains the directories:
| none | Yes |
...
Follow this procedure to change two default values in the Properties#Universal Universal Controller Start-up Properties (uc.properties), uc.properties, which is read by the Controller.
...
Step 1 | From the Services, select Administrationation > Properties. The Properties list displays. |
|---|---|
Step 2 | Click the License Key property Value field and enter your encrypted license key. |
Step 3 | Return to the System Details Widgets and review the License field to verify that the terms of your license are correct. |
Step 4 | Optionally, configure the Controller so that your system administrator receives notifications regarding System Notifications for License Violations and Expirations |
...
In order to log in to the Controller using LDAP Settings#Credentials for Running Tasks Authentication, you must set the Properties#LDAP LDAP Synchronization Enabled Universal Controller System property (Administration > Configuration > Properties in the Controller user interface) to true.
...
| Note | ||
|---|---|---|
| ||
System Notifications are not the same as Email Notifications. Please refer to the following sections for explicitly defining Email Notifications. |
...
Step 1 | Select an Email Connections on which the notifications will be sent and enable the Email Connections#Use Use for System Notifications field.
| |||||
|---|---|---|---|---|---|---|
Step 2 | Identify the Universal Controller Administrator(s) that will receive the system notifications by entering one or more valid email addresses for those administrators in the Properties#Administrator Administrator Email Address Universal Controller system property. | |||||
Step 3 | If you want to identify the source system that is sending the system notifications in the Subject line of the emails, enter a value in the Properties#System System Identifier Universal Controller system property. |
...
- Sent daily at midnight, processed same time as midnight log rollover.
- Sent on Controller start-up (or a cluster node becoming the Active cluster node).
- Sent on License Key property change (if new license still expired).
- System paused on license expiration.
| Note | ||
|---|---|---|
| ||
A Logging In#License License Expiration message also displays on the User Interface#Console Console when you log in to the Controller if the license will expire within the week and when the license already has expired. |
...