Storage

ActiveVOS Server Console Help

Storage

The ActiveVOS server includes persistent storage based on the database settings you configured during installation. You must configure one database before running the engine.

The Storage page displays database configuration properties and allows you to maintain the database.

The displayed properties are:

JNDI Location	The Java Naming and Directory Interface (JNDI) context that specifies where to look for the database. For example, jdbc/ActiveVOS
Database Type	The type such as `mysql`
User Name	Username, if required for ActiveVOS server’s access to the database

Note: If you need to change the user name and password for database access, we recommend that you re-run the ActiveVOS Configure and Deploy utility. This utility, located in your ActiveVOS Server installation folder, allows you to modify the database user name and password without modifying other settings.

Manual and Scheduled Database Maintenance

The ActiveVOS database stores completed processes and deployment logs. You can delete old processes and logs, as desired, either manually or on an automated schedule.

Note: The Process Deployment Descriptor (PDD) file contains an option for disabling storage for a completed process. For details see the ActiveVOS Server User’s Guide.

Manual Maintenance

Use the Manual tab on the Storage page to delete files from the database as follows.

Deleting Completed and Faulted Processes

Enter a date in the Completed/Faulted before field.
Select Delete. The number of matching processes is displayed.
Select OK.

Deleting Inactive Plans

A plan consists of a process version plus the associated disposition of running processes. An inactive plan refers to a process version and associated processes that either have reached their expiration date or have been manually expired. If you have deleted completed processes from the database, you can delete the plan associated with those processes.

This means that the process version associated with the plan will no longer be displayed on the Deployed Processes page. The associated WSDL and other resources are not deleted, nor is any Partner Definition, since these files may be associated with other plans.

If a plan is associated with a subprocess, you cannot delete it until the main process is deleted. A subprocess is a BPEL process that is invoked by another process.

Deleting Deployment Logs

Select the type of log in Log Contents.
If desired, enter dates in the Deployed between fields.
Select Delete. The number of matching logs is displayed.
Select OK.

Delete Server Log

Deletes the entire Server Log. The Server Log tracks server events such as deployments and execution errors. For details, see Server Log.

Scheduled Maintenance

Use the Storage page to specify when and how often to delete items from the database.

Delete Schedule
Frequency	None resets the engine for no scheduled maintenance Intraday, Daily, Weekly, or Monthly sets the frequency schedule
Every	For Intraday, select minutes or hours and the number. For example, select 90 minutes. For Weekly, select one or more days of the week. For example, select Monday to delete database items every Monday. Select Monday and Thursday to delete every Monday and Thursday. For Monthly, select the first, second, third, fourth, or last day of the month. For example, select Last Monday to delete items on the last Monday of the month.
Start Time	Type in a time of day, or select the Date Chooser to enter a time. In the Date Chooser, select Now to enter the current time.
Plan and Process Delete Options
Delete Inactive Plans	Select this setting to delete old process versions. (For an explanation of process versions, see the topic above, Deleting Inactive Plans.)
Delete Completed Processes Delete Faulted Processes	Select these settings to delete old processes that completed normally (Completed) and/or abnormally (Faulted).
Default Process Retention	Enter a number of days, hours, or minutes to retain completed and faulted processes in the database before deleting them. The default is one day, indicating all processes one day old can be deleted on the next scheduled maintenance. Processes are deleted on the next scheduled time after the retention days duration. For example, if process retention is set to 30 days, and scheduled deletions occur every Friday, the processes that have been in the database at least 30 days are deleted each Friday. This setting can be overridden for individual processes. See Process Instance Retention for details.
Delete Deployment Logs	Delete all deployment logs.

After you set up a maintenance schedule, select Update to save your settings.

Select Run Now to run the current schedule immediately, in addition to the regular schedule, or to select a different set of checkboxes and execute those deletions. Any changes you make to the page can be executed immediately, but do not take effect for the future unless you select Update.

When you select Run Now, the following execution occurs:

For all check boxes selected (Inactive Plans, Completed Processes, Faulted Processes, Deployment Logs), as well as Default Process Retention, deletions occur, depending on individual processes Process Retention setting
If a process was deployed with a Process Retention schedule, or modified in the ActiveVOS Console, the Default Process Retention value is ignored, and the process will not be deleted unless it has been retained in the database beyond its retention value. For details, see Process Instance Retention.