ActiveVOS Server Console Help
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 |
|
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
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
Scheduled Maintenance
Use the Storage page to specify when and how often to delete items from the database.
|
Maintenance Schedule |
|
|
Frequency |
|
|
Every |
|
|
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.) If you do not select this setting, only completed/faulted processes can be deleted. |
|
Delete Completed and Faulted Processes |
Select this setting to delete old processes. If you do not select this setting, only inactive plans can be deleted. |
|
Default Process Retention Days |
Enter a number of days 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 days is set to 30, 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 Days 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 schedule and run it. Any changes you make to the schedule do not take effect unless you select Update.
Copyright (c) 2004-2009 Active Endpoints, Inc.