...
Script | Description and Links | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Exports all current record definitions, without versions, when migrating data to a new Universal Controller deployment. | |||||||||||
| Exports all current Activity data from multiple Universal Controller database tables.
| |||||||||||
| Exports all current Audit records when migrating data to a new Universal Controller deployment. | |||||||||||
| Exports all current History records when migrating data to a new Universal Controller deployment. | |||||||||||
| Exports all current records along with older (non-current) versions of record definitions when migrating data to updated software (see Upgrading Universal Controller from 5.2.0). | |||||||||||
| Imports all data from an exported file when migrating data to updated software (see Upgrading Universal Controller from 5.2.0). | |||||||||||
| Clears the internal server cache. You can use this operation if you are experiencing unexpected behavior with the Controller system. For example, Technical Support may ask you to first run this operation to clear the server cache, then clear your browser cache. | |||||||||||
| Displays the following information for the Controller database:
| |||||||||||
| Displays the following information for Universal Controller database tables:
See Universal Controller Database Tables, below, for a description of all tables. | |||||||||||
| Disables normalization of Business Service membership for all:
All previously normalized Business Service membership records will not be removed until they qualify for Activity or History purge. Also, the Task Instance Normalize Business Service Membership property will be set to Disabled. | |||||||||||
| Commence normalization of Business Service membership for all existing Task Instance and History records, and begin normalizing Business Service membership for all new Task Instance and History records.
| |||||||||||
| For use only by Technical Support personnel or when you are requested to run it by Technical Support. | |||||||||||
| Displays information about the current instance of the Controller. | |||||||||||
| For use only by Technical Support personnel or when you are requested to run it by Technical Support. | |||||||||||
| Limits the number of events displayed by the Inspect Events server operation. The events will display with the latest events first; that is, ordered by created time descending. Default is 1000. | |||||||||||
| For use only by Technical Support personnel or when you are requested to run it by Technical Support. | |||||||||||
| For use only by Technical Support personnel or when you are requested to run it by Technical Support. | |||||||||||
| For use only by Technical Support personnel or when you are requested to run it by Technical Support. | |||||||||||
| If LDAP is configured for this installation, it refreshes every 24 hours. This server operation forces a refresh. The refresh writes all Controller log entries to the user interface as well as to the Controller log, and the response will not be returned until the process completes. If you estimate the refresh could take a considerable amount of time, we recommend you use 20381848 LDAP Refresh (Asynchronous). | |||||||||||
| If LDAP is configured for this installation, it refreshes every 24 hours. This server operation forces a refresh. The refresh is performed in the background and sends Controller log entries to the Controller log. | |||||||||||
| Lists (and optionally lets you download) any existing UC log files for the Controller node that this operation is executed on.
(You also can select / deselect all log files by clicking the Name checkbox at the top of the list.) | |||||||||||
| Loads base demonstration data into your database (for example: workflows, tasks, triggers). | |||||||||||
| Displays a summary of Controller memory usage. | |||||||||||
| Deletes any overdue timers, as listed by the 20381848 Overdue Timers List operation. | |||||||||||
| Lists any timers that are overdue (normally, no timers should be overdue). | |||||||||||
| Pauses the Controller, which prevents it from processing tasks and events. If an event or task is already running when you run this operation, the event or task will complete. The Controller remains in a paused state until you run the 20381848 Resume Cluster Node operation. | |||||||||||
| Purges all non-default Users and Groups and their associated data. There is one default User: Administrator (ops.admin). There are two default Groups: Administrator Group and Everything Group.
The following is recommended before running this server operation:
| |||||||||||
| Purges all records from the History table (ops_history).
| |||||||||||
| Purges everything in the All Task Instances table (ops_exec), which contains all system activity, including task instances in any status (including end statuses). Records in the All Task Instances table (ops_exec) remain there until they are purged.
| |||||||||||
| Sends a request to all active Agents to purge their logs and cache. | |||||||||||
| Purges versions of records in excess of the maximum specified by the System Default Maximum Versions Universal Controller system property. | |||||||||||
| For Controller upgrades only; resets system defaults list layouts. | |||||||||||
| Resets the current number of tasks currently being run by all Agent clusters to 0 (see Resetting the Current Task Count). | |||||||||||
| Resets the current number of tasks currently being run by all Agents to 0 (see Resetting the Current Task Count). | |||||||||||
| Stops and restarts the Controller within the running Tomcat server. The Controller is effectively shut down and started up without stopping and starting Tomcat.
| |||||||||||
| Restores all lists to their default layouts. | |||||||||||
| Resumes the Controller after it has been paused using the 20381848 Pause Cluster Node operation, or paused by the Start Server Paused Universal Controller property on startup. | |||||||||||
| Renames the existing log to a timestamped log and opens a new log file. | |||||||||||
| Runs the "garbage collector." The gc method suggests that the Java Virtual Machine expend effort toward recycling unused objects in order to make the memory they currently occupy available for quick re-use. When control returns from the method call, the Java Virtual Machine has made a best effort to reclaim space from all discarded objects. | |||||||||||
| Displays the following categories of information about the Universal Controller server:
| |||||||||||
| Displays all properties of the operating system on which the Controller is running. | |||||||||||
| Allows for the temporary setting of specific Universal Controller properties to be used for diagnosing problems. This operation and setting of properties should be performed only under the guidance of Stonebranch support. | |||||||||||
| Captures information about internal Controller system processes. | |||||||||||
| Captures information about internal Controller system processes. | |||||||||||
| Captures information about internal Controller system processes. |
...
The following table identifies and describes all Universal Controller database tables, which are listed if you run the 20381848 Database Table Counts server operation, above.
The tables are in alphabetical order according to Table Name.
...