You can define the expiration period of events stored in the Orchestrator database and the maximum number of workflow runs.
About this task
Each event corresponds to a change in the state of a workflow or policy and is stored in the database for a specified time period. When the specified time period expires for an event, the database deletes the event.
Each time you run a workflow, a workflow token is created in the database. This token contains all parameters related to the running of the workflow. For example, if you run a workflow three times, three workflow tokens are created. The three tokens appear in the Orchestrator client below the workflow.
- Log in to the Orchestrator configuration interface as vmware.
- On the General tab, click Advanced Configuration.
- In the Expiration days of log events text box, type an integer value for the number of days, for which you want to store events.
- Fill in the Maximum number of runs text box.
After you reach the maximum number of runs, the rollover process starts. If you do not want the rollover process to start, type 0 in this text box. If you type 0, your database continues to extend.
- (Optional) : To set the default login credentials, fill in the User name for automatic Web login and Password for automatic Web login text boxes.
This feature allows you to generate URLs that enable you to run, answer, schedule, or monitor a workflow without having to specify your credentials. Use your default operator credentials for these text boxes.
- Fill in the Web view directory text box.
This is the root folder from which development Web views are loaded. Files for each Web view must be in a separate subfolder, and the name of this subfolder must be the same as the URL folder defined in the client.
- (Optional) : To put the server in Web view development mode, select the Enable Web view development check box.
- Click Apply changes.