Figure: Recovering the Stardust Runtime Environment
The administrative actions provided are:
Please refer to section Configuration recommended for Cleanup Operations and Database Backup and Recovery for additional information on cleanup operations and database backup.
If an EJB server crashes, it may leave non-interactive activities in an uncompleted state. Their branch in an activity-transition-network "hangs". Stardust users can always restart interactive activities.
Also, it is possible that non-interactive activities, as well as some interactive ones, fail to be completed due to unexpected errors, either because of programming errors or invalid state of the application, in which case the activities are marked as interrupted.
In both cases, to "reanimate" the problematic activities you may manually invoke the option Recovery.
Figure: Recovering the Stardust Runtime Environment
A dialog opens to confirm the start of the recovery process.
Figure: Confirm the Recovery Process
The audit trail database stores all process information on every piece of work that has been performed via the Stardust Process Engine. It also stores the model information, on the base of which processes are instantiated and their activities performed.
The administrator has full control over the database, so that both, the audit trail and the model information, can be deleted. This should never be done after the model has gone into production! Deleting the audit trail means deleting all the log entries defined in the Stardust runtime environment. The Retain Users and Departments option gives choice to keep the users and their departments. Deselecting the Retain Users and Departments checkbox would delete all the users and departments from audit trail.
To clean the audit trail database, choose Cleanup Audit Trail Database. Note that if any views of Workflow Execution or Administration or Business Control Center perspectives are open, the following error is displayed.
Figure: Error - Close all Open Views
You need to close all open views before proceeding for audit trail cleanup operation.
Once you close all the open views, click Cleanup
Audit Trail Database link. A dialog to confirm the deletion get displayed.
Figure: Performing a Cleanup of the Audit Trail
Database
After the completion of cleanup operation, you are logged out of the Stardust Portal.
To clean up the audit trail and the model database, choose Cleanup Audit Trail And Model Database: Note that if any views of Workflow Execution or Administration or Business Control Center perspectives are open, the following error is displayed.
Figure: Error - Close all Open Views
You need to close all open views before proceeding for audit trail and model database cleanup operation.
Figure: Performing a Cleanup of the Audit Trail
and Model Database
After the completion of cleanup operation, you are logged out of the Stardust Portal.
The cleanup of an audit trail database may take some time and requires a significant amount of rollback space in the database. In case the data should be cleaned up in your environment, it is recommended to perform this cleanup via the command line by creating a new schema and performing a new deployment of the model as this is the simplest and quickest way. Please refer to the chapter The Sysconsole Command of the Stardust Online Documentation - Operation Guide The Sysconsole Command for detailed information on the appropriate commands provided by Stardust.
Should the cleanup be performed in the Administration Perspective, please take care of the right settings for the transactions. Please note that in that case the settings remain for the whole productive operation on the application server and the database. The transaction time (for the database or the application server) should be increased for the operation. Inside the database there could exist limits as well. Here the number of objects to be deleted could be set as a limitation for the cleanup command. Please find the according hints for these settings in the documentation of the specific database you are using.
The Stardust runtime environment does not use any other
persistent and/or transactional resource beside the audit trail
database. The only backup task for the runtime environment is the backup
of the audit trail database. If Stardust is
used to implicitly access other transactional resources than the audit
trail database (e.g. via Entity Beans), Stardust attempts to use JTA/JTS
(Java Transaction API/Java Transaction Services) to synchronize the
access. Recovery is then performed according to the current transaction
monitor.