...
It assumes you already have performed all required prePre-installation proceduresInstallation Procedure:
- Determined space requirements Determining Space Requirements
- Installed all prerequisites Installing Universal Controller Prerequisites.
- Downloaded a Universal Controller distribution file Downloading Universal Controller Software.
Anchor | ||||
---|---|---|---|---|
|
...
The Controller installation process writes the values for some command line switches to the Universal Controller startStart-up Properties (opswise.properties file), 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 Universal Controller startStart-up Properties (uc.properties file), 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 | 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 |
...
Step 1 | Start Tomcat as follows:
| ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| During this initial startup, the Controller builds the database tables, a process that takes several minutes. You can view details in the Tomcat window or monitor the Controller log, as described below:
| ||||||||||||
Step 3 | When you see the following, the Controller is ready:
|
...
Follow this procedure to change two default values in the Universal Controller startStart-up Properties (uc.properties file), uc.properties
, which is read by the Controller.
...
To make sure the Controller is installed, running, and communication with Universal Agent and Universal Message Service (OMS):
Step 1 | Start the Starting and Stopping Universal Controller. | ||
---|---|---|---|
Step 2 | From your browser, access the Universal Controller user interface.
| ||
Step 3 | Log in with user | ||
Step 4 | Enter a password in the New Password and Confirm New Password fields (the Current Password field should remain empty) and click Change Password. The Universal Controller Home Dashboard displays. | ||
Step 5 | |||
Step 6 | From the Agents and Connections navigation pane, select Agents > All Agents or Agents > <type of Agent>. You will see a list similar to the following example. Make sure the Status of the Agent is Active. | ||
Step 7 | From the Agents and Connections navigation pane, select System > OMS Servers. You will see a list similar to the following example. Make sure the Status of the OMS Servers are Connected. | ||
Step 8 | For more information about these components in the Universal Controller user interface, see: |
...
in the Universal Controller user interface, see: |
Anchor | ||||
---|---|---|---|---|
|
Apply the License Key
Although you do not normally need to enter a license key immediately after installation, at some point you will need to follow these steps to enter your key:
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 Widget 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 license violations and expirations. System Notifications for License Violations and Expirations |
Anchor | ||||
---|---|---|---|---|
|
...
The License field in the System Details widget (view the system-defined Home Dashboard or, on the Reporting navigation pane, click Widgets) identifies license information for:
...
In order to log in to the Controller using LDAP credentials Credentials for Running Tasks Authentication, you must set the LDAP Synchronization Enabled Universal Controller System property (Administration > Configuration > Properties in the Controller user interface) to true.
...
System Notifications are emails sent to one or more Universal Controller system administrators based on either:
- Licensing issues (license violations, expired licenses, invalid licenses)
- Status of a system operation associated with a task instance.
- Data backup / purge operations.
System Notifications for License Violations and Expirations - Status of a System Notification for System Operations
- System Notification for Data Backup / Purge Operations
Note | ||
---|---|---|
| ||
System Notifications are not the same as Email Notifications. Please refer to the following sections for explicitly defining Email Notifications.
|
In order for a system administrator to receive system notifications, you must configure the Controller for system notifications:
Step 1 | Select an email connection Email Connections on which the notifications will be sent and enable the 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 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 System Identifier Universal Controller system property. |
...
The License field in the System Details widget (view the system-defined Home Dashboard or, on the Reporting navigation pane, click Widgets) identifies these maximum numbers (see License Information, above).
Anchor | ||||
---|---|---|---|---|
|
...
- 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 License Expiration message also displays on the Console when you log in to the Controller if the license will expire within the week and when the license already has expired. |
...
For detailed information on how to set up these system notifications, see System Operation Actions.
Anchor | ||||
---|---|---|---|---|
|
...
For detailed information on how to set up system notifications for Data Backup / Purge operations, see Data Backup / - Purge.