Purging and archiving in IBM BPM systems
This chapter describes purging and archiving an organization's IBM Business Process Manager (BPM) data. IBM BPM is a stateful product that accumulates data over time. As with any stateful product, it is essential to its ongoing health to have a strategy for purging some of that data occasionally.
In addition to describing the process of purging data from IBM BPM, this chapter also provides information about the Process Center, Process Portal, and Process Federation Server indexers, how to configure the index intervals, and how to manually run the indexers.
|
Important: Running deletion and cleanup commands for snapshots and instance data are done during the time of least activity. It is important to create a script that contains the logic on your data retention policies and run these scripts regularly.
Problems were reported in the past with the use of the BPMDeleteSnapshot and BPMSnapshotCleanup commands in IBM BPM. Therefore, check the following Flash Alert to ensure that you have all of the correct fixes for the version of IBM BPM that is being used:
|
This chapter includes the following topics:
4.1 Data retention policies
If data grows without bounds, it can lead to disk space and performance issues as database queries take ever longer.
Business processes naturally use business data in the form of variables to represent the process state and affect the process flow. However, do not consider this data a system of record (SOR). IBM BPM should always work with external systems of record to access and update data. Use the business data in a process only for that process; do not use that data as an SOR for other purposes.
An effective SOR is designed for transactional, efficient, and safe reading and writing and reporting by one or more users and producers. The business data in a process is merely a temporary stateful representation of that data to affect the process flow and user interactions. Process variables and their underlying IBM BPM persistent data store are not designed to be used outside of that process. Considering these process variables as the single source of truth for that data eventually causes issues and requests for typical transactional create, read, update, and delete access to that data that is not possible or recommended on top of the IBM BPM internal database.
A data retention policy must define policies for purging old snapshots and process instance data.
4.1.1 Snapshot and instance data deletion considerations
Deleting snapshots on the Process Center or Process Server have a different set of preconditions that must be in place for any snapshot that you want to delete. Consider the following points:
•Process Center:
– You must be a repository administrator.
– The first snapshot of an application cannot be deleted, even though it might be unnamed or archived. The first snapshot contains original information about the snapshot that is displayed in the history panel in Process Designer.
– You must archive named snapshots before you delete them.
– The snapshot must have no running instances.
•Process Server:
– The snapshot must exist.
– The snapshot must be inactive.
– The snapshot must have no running instances.
– The snapshot must not be deployed.
|
Note: Process instances cannot run on the snapshot that you want to delete. When a new snapshot is deployed, it is important to always migrate runtime process instances whenever possible.
|
4.2 Process Center
The Process Center holds projects, which are deployable process applications or reusable toolkits.
4.2.1 Disabling auto-tracking in a BPD
Auto-tracking in IBM BPM is important for many business process definitions (BPDs) because it helps gather, track, and report key business metrics. However, another cost comes with auto-tracking because these events are processed by the Performance Data Warehouse and persisted in the database.
Because of that cost, disable the default auto-tracking capability for BPDs if you do not need to track and report on their business metrics so that you can lower your costs. Also, consider creating tracking groups to track only key business events and then disable auto-tracking. This approach ensures that the events that are persisted are only those events that are required for your business metrics.
4.2.2 Marking system tasks for deletion when created
For system tasks in your BPDs, select the Delete task on completion option in the Implementation tab of the properties in IBM Process Designer. With this option selected, tasks are automatically deleted when they complete, which can save a significant amount of data from being persisted.
For user tasks in your BPDs, make a conscious decision about whether to select the Clean State option in the Implementation tab of the BPD’s properties. By default, this option is not selected. However, selecting this option automatically cleans up the context (such as variables) for the user task when it completes. If the state is not required to be persisted and this option is selected, you can save a significant about of database space and even speed the migration of snapshot instances.
4.2.3 Process applications and toolkits
Process applications and toolkits can be archived from the Manage tab of the Process Center for a project, as shown in Figure 4-1.
Figure 4-1 Archiving process applications and toolkits
Archiving a project does not delete it or reclaim its space in the database. Instead, archiving marks the project so it does not show by default in the Process Center user interface. To delete a project, select the option to show the archived projects and then delete the project (the project must be archived first), as shown in Figure 4-2.
Figure 4-2 Deleting archived process applications and toolkits
Deleting a project deletes all snapshots and process instances. It also deletes all IBM BPM Advanced content, such as associated Business Process Execution Language (BPEL) process instances, business-level applications, and enterprise applications. This deletion capability in IBM BPM is available only from the user interface. There is no scripted way to perform this deletion.
4.2.4 Snapshots in Process Center
|
Important: Do not delete the snapshots until all of the required fixes are applied as directed in the following Flash Alert:
|
When you edit a process application or toolkit by using Process Designer, you are changing a special version or snapshot of it that is named Current (or Tip). At any point, you can take a new snapshot and assign that snapshot a name. Named snapshots are deployable to Process Server, but other Current versions are not editable.
Whenever you save artifacts in Process Designer, an unnamed snapshot is created in the database. This feature is helpful to enable you to see history, but it is costly because of database growth.
You can archive individually named snapshots instead of archiving the entire project and all of its snapshots. You can perform this archiving process from the Snapshots page of the process application or toolkit by using the drop-down menu for each snapshot. This archiving does not delete the snapshot; instead, the snapshot is marked and hidden.
So, how is a snapshot deleted in Process Center? IBM BPM V8.5.0 introduced the BPMSnapshotCleanup wsadmin command, with which you can delete b named and unnamed snapshots. The named snapshots first must be archived to delete them.
For more information, see the following IBM Knowledge Center website:
|
Important: The BPMSnapshotCleanup wsadmin command also was backported to the v7.5.1.2 Fix Pack, v8.0.1.3 Fix Pack, v8.5.1.2 Fix Pack, and v8.5.6.
|
4.2.5 Unnamed snapshots in Process Center
The BPMSnapshotCleanup wsadmin command can be used to delete unnamed snapshots.
IBM BPM includes the capability to enable automatic clean-up of unnamed snapshots. You can enable this feature by adding the lines that are shown in Example 4-1 to your 100custom.xml file.
Example 4-1 Automatic Cleanup for Unnamed Snapshots in the Process Center
<unnamed-snapshots-cleanup-config>
<enabled>true</enabled>
<cleanup-start-time>23:23:59</cleanup-start-time>
<cleanup-duration-minutes>5</cleanup-duration-minutes>
<clean-after-number-named-snapshots>4</clean-after-number-named-snapshots>
</unnamed-snapshots-cleanup-config>
For more information, see Deleting unnamed snapshots, automated from a Process Center server, automated method, at the following IBM Knowledge Center website:
|
Note: Exporting a snapshot to a .twx file and reimporting it into a different Process Center is another method that can be used to delete unnamed snapshots. Unnamed snapshots are not exported.
|
4.2.6 Advanced content in Process Center
|
Important: Do not delete the snapshots until all of the required fixes are applied, as directed in the following Flash Alert:
|
If you use IBM BPM Advanced and you have process applications and toolkits that contain advanced content, such as IBM BPEL processes, you must have a strategy for deleting the business-level applications (BLA) and enterprise applications that are created in the Process Center Playback server by the existence of that content.
For every process application or toolkit in Process Center that contains a module or library (directly or inherited through a toolkit), a BLA is created for the current snapshot and for every named snapshot of toolkits and process applications that contain advanced content. The BLA is named <Acronym>-<Snapshot-name>; for example, PA1-V1.0.
Within those BLAs, every module or library produces an enterprise archive (EAR) file that is an asset within it. These BLAs are created on demand when performing a Playback from Process Designer or publishing to Process Center from Integration Designer. It remains until the process application or toolkit is deactivated.
As you create toolkits with advanced content, use those toolkits from process applications, and snapshot the toolkits and process applications, this advanced content can quickly accumulate, which affects server start time, memory consumption, and general performance.
You often need only the BLAs for the current snapshot of a process application. You can delete them from the current snapshot of any toolkits and any named snapshots of either toolkits or process applications. To delete the BLAs, you “undeploy” your snapshot. You see this option on the Snapshots page of Process Center, in the drop-down menu for the Current snapshot if that snapshot’s advanced content is deployed.
For named snapshots, you first use the Deactivate option. Then, you see the Undeploy option if there is deployed advanced content. You can always use the WebSphere administrative console or commands to manually remove the BLAs and EARs. Do not be concerned about deleting something that is needed because these BLAs are re-created on-demand, if needed.
If you are using Advanced Integration services (AIS) that are the bridge between Business Process Model and Notation (BPMN) and BPEL processes, we recommend the façade pattern to reduce the size of the EARs that are involved. For more information about this pattern, see the IBM developerWorks® article, Implementing the facade pattern using IBM Business Process Manager Advanced V7.5, which is available at this website:
4.2.7 Administering the Process Center index
The Process Center index is used to conduct searches on the Process Center repository. The index is automatically created and maintained when the server is started. After the index is created, the system updates the index at regular intervals to reflect any changes that are made to the repository.
You can configure the update interval and index location to better suit your installation. Also, commands are provided with IBM BPM for you to manually re-create or update the index.
Manually re-creating or updating the Process Center index
The Process Center index is in the file system of the machine on which the server is running. You do not need to back up the profile or the database before running the artifactIndexFullReindex or artifactIndexUpdate commands. You can run the commands when the server is running.
Re-creating the index in a network deployment environment
To re-create the index in a network deployment environment, complete the following steps:
1. From the command prompt, change to the deployment manager profile bin subdirectory where the command is located.
2. Enter the following command:
artifactIndexFullReindex -u userId -p password -host hostName -port port
where
hostName is the host name of the application cluster member on the node and port is the server SOAP port.
Updating the index in a network deployment environment
To update the index in a network deployment environment, complete the following steps:
1. From the command prompt, change to the deployment manager profile bin subdirectory where the command is located.
2. Enter the following command:
artifactIndexUpdate -u userId -p password -host hostName -port port
where
hostName is the host name of the application cluster member on the node and port is the server SOAP port.
|
Important: One index is created for each node. To update the index, you must issue the command for each node. Run the command from the deployment manager and direct it by using the -host and -port parameter to a cluster member that is running on each node of your installation. This process updates the index for each node; there is no need to run the command locally on the node.
|
Configuring the Process Center index
You can configure the indexing process to automatically update the index on a preset schedule. You can also set the index location and you can disable indexing altogether. To change the Process Center index update interval or to disable indexing, create or edit the 100Custom.xml file that is in the following directory:
•For a UNIX or Linux operating system:
<process_center_profile>/config/cells/<Cell>/nodes/<node>/servers/<server>/process-server/config/system
•For a Windows operating system:
<process_center_profile>configcells<Cell>
odes<node>servers<server>process-serverconfigsystem
The Process Center index configuration settings that can be updated in the 100Custom.xml file are listed in Table 4-1. If the process instance includes many previous tasks, reindexing these tasks might degrade the system performance.
Table 4-1 XML tags that are used to change the index configuration settings
|
XML tag
|
Description
|
|
<artifact-index-enabled>
|
This Boolean value determines whether indexing is enabled. The default value is true; if the index does not exist, it is created.
To turn off indexing, change the value to false; if the index does not exist, it is not created.
|
|
<artifact-index-update-interval>
|
This integer value specifies the time between index updates in seconds.
Restriction: The minimum update interval is 30 seconds. If you attempt to set a value of less than 30, the index defaults to 30 seconds.
|
Setting the index location
To change the Process Center index location, log in to the administrative console and select Environment → WebSphere Variables.
Setting the location for a cluster server
Edit the BPM_SEARCH_ARTIFACT_INDEX variable. For a cluster member, set the scope to the cluster level. The default is $<BPM_SEARCH_ARTIFACT_INDEX_ROOT>/<clusterName>.
Setting the location for a stand-alone server
For a stand-alone server, set the scope to the cell level. The default is $<BPM_SEARCH_ARTIFACT_INDEX_ROOT>/$<WAS_SERVER_NAME>. If the variable is not set, the location defaults to $<USER_INSTALL_ROOT>/searchIndex/artifact/$<WAS_SERVER_NAME>.
For more information, see Administering the Process Center index at the IBM Knowledge Center:
4.3 Process Server
The Process Server is where you install process application snapshots and where you run processes within the snapshots. You must consider how (in the Process Server in terms of accumulating content) to delete these installed snapshots, and how to delete processes when they complete or end.
4.3.1 Snapshots in Process Server
You install multiple snapshots of the same process application to a specific Process Server. Over time, these snapshots can accumulate and it becomes prudent to delete the snapshots that are no longer used.
For IBM BPM Advanced customers, it is important to remember that if a process application contains any advanced content (such as a module or library from Integration Designer), a business-level application with EARs is created for this process application.
Conceptually, the IBM BPM content is installed into a Process Server after which the IBM BPM Advanced content is deployed, which amounts to generating and installing the BLA and constituent EARs.
|
Important: You can remove snapshots from Process Server in IBM BPM v8.0.1 or higher only with the introduction of the BPMDeleteSnapshot wsadmin command.
|
For the BPMDeleteSnapshot wsadmin command to work, the following prerequisites must be met:
•The snapshot cannot have any running instances and cannot be the default snapshot. Use the BPMShowSnapshot command to determine whether either of these statuses is true.
•The snapshot cannot be active. Use the BPMDeactivate command to deactivate the snapshot. For IBM BPM Advanced processes, you must use the BPMStop command. These commands prevent new instances of BPMN and BPEL processes from starting and allow instances to quiesce.
•The IBM BPM Advanced content, including the BLA and EARs, must be undeployed by using the BPMUndeploy command.
|
Note: When you successfully delete a snapshot, any BPD instances for it also are deleted.
|
4.3.2 Instances in Process Server
Two types of instances should be considered: User or human task instances, and process instances for BPMN BPD processes and BPEL processes. Both task and process instances are recorded in the database, even after the task and process complete. Therefore, it is important to think about occasionally purging older instances.
When you delete process instances, task instances also are deleted. Although you can delete BPEL human task instances independently of their processes, BPD user tasks cannot be deleted as such.
To delete BPD process instances and their associated task instances, you can use the BPMProcessInstancesPurge wsadmin command. By using this command, you can identify the specific instances to delete, or the date range within which any instances that completed is deleted.
You also identify whether to delete completed, canceled, failed or all types of instances. This command also includes other parameters to specify the maximum duration time and maximum number of instances to delete, which makes it a candidate to run in a regularly scheduled cron job so you can limit its effect on the system and limit its work.
|
Important: The BPMProcessInstancesPurge command is not available on IBM BPM 8.5.6 and previous releases. For IBM BPM v8.0.1.x, v8.5.1.x, and v8.5.6.x, you can use the deprecated BPMProcessInstancesCleanup command to delete BPD process instances. In addition, the BPMProcessInstancesCleanup does not exist on IBM BPM v7.5.x, but you can use a supplied stored procedure LSW_BPD_INSTANCE_DELETE to delete explicitly identified process instances.
|
IBM BPM Advanced provides the following options for deleting Business Process Choreographer human task and process instances:
•When modeling the human tasks and BPEL processes in Integration Designer, specify to automatically delete instances when complete.
•Use the Business Process Choreographer Explorer to delete tasks or processes individually.
•Create a custom utility by using the Business Process Choreographer APIs.
•Use the supplied Jython scripts deleteCompletedTaskInstances.py or deleteCompletedProcessInstances.py to delete a batch of task or process instances by state, owning user, or completion date.
•Use the Cleanup Service in the Human Task Manager or Business Flow Manager administrative console pages to schedule jobs to automatically delete task or process instances. You can specify when to run, how long to run, how many instances to delete, and which instances to delete via state and date criteria, as shown in Figure 4-3 on page 60.
Figure 4-3 Cleanup Service scheduling for BPEL process instance purging
In IBM BPM Advanced, the following items also can be purged:
•IBM BPM process and human task templates that are no longer needed
•Audit log entries
•Failed messages that are in the hold queue
•Unused shared work items
For more information about how to delete these items, see the following resources:
•IBM Knowledge Center topic “Cleanup procedures for Business Process Choreographer”:
•IBM developerWorks series Operating a WebSphere Process Server environment:
4.3.3 Durable subscription events in Process Server
Message events in an intermediate message activity of a BPD can be made durable, which you enable by selecting the Durable Subscription option in the Properties tab, as shown in Figure 4-4.
Figure 4-4 Specifying a durable subscription for intermediate events
If specified in Process Designer, these durable messages accumulate and require occasional clean-up, even if you select the Consume Message option. Although no built-in way to perform this clean-up was available in the past, a new BPMDeleteDurableMessages wsadmin command is now available that takes the following parameters:
•olderThan: Only events older than this number of days are deleted.
•maximumDuration: The command that is run for this amount of time only.
•transactionSlide: Indicates the number of events to delete per transaction.
These parameters are shown in the following example:
BPMDeleteDurableMessages {-olderThan 30 -maximumDuration 60 -transactionSlice 100}
4.4 Performance Data Warehouse
BPD processes can support tracking, which means events are sent to the Performance Data Warehouse and logged in its database. How many events are sent is determined by whether your BPD includes auto tracking that is enabled, which was the default for new BPDs.
With auto tracking enabled, the Performance Data Warehouse can quickly accumulate much data. Unfortunately, no product was supplied and supported in the past that deletes any of this data. As a result, many customers resorted to custom SQL code that directly accesses the database to delete or move certain data according to age or state criteria.
Alternatively, all Performance Data Warehouse data can be removed by dropping and re-creating the tables. For more information, see the following resources:
•Before V7.5.0: Using twinit to re-create databases in Teamworks 7.0.x and WebSphere Lombardi Edition:
•After V7.5.0: How to clean up the Performance Data Warehouse database and the LSW_PERF_DATA_TRANSFER table for IBM BPM:
A product is now available that supports pruning selective data from the Performance Data Warehouse. It is included with 8.5.0.1, 8.0.1.2, and 7.5.1.2 fix packs. With these releases, the perfDWTool features a new option that is called Prune. By using this command, data that is beyond a specified age in days can be purged, as shown in the following example:
perfDWTool.sw –u uid –p pwd –nodeName node prune –daysOld days
The use of this command deletes all data older than the days that are specified. This command must run from an active node in the cluster and all members of the cluster should be running. Attempt to run it when the server is least busy. Its operation can be affected by three new settings that you can override in 100custom.xml, as shown in Example 4-2.
Example 4-2 Performance Data Warehouse pruning
prune-batch-size: The number of record to be deleted in a single prune operation. The default value is 1000.
prune-operation-time-box: The amount of time the operation will run, in seconds. The default is 10800 or 3 hours.
prune-operation-time-box-retry: The number of times the operation will be tried. The default is 4 such that it will retry 3 times.
4.5 Process Portal index
The Process Portal index allows process participants who are working in Process Portal in non-federated environments to search business processes for instance data. The index also is used to provide data for the charts in the Process Performance and Team Performance dashboards.
|
Important: The information in this section applies to Heritage Process Portal and Process Portal.
|
Indexing on an IBM BPM system is enabled by default. Process instances and tasks are indexed according to a time interval that you can specify. To change the indexing behavior, you must edit the 100Custom.xml configuration file. If a problem occurs with the index, commands are available for updating and rebuilding it.
Tasks and process instances are indexed in the following situations:
•Tasks:
– A task is assigned.
– A task is completed and the business data is updated.
– The due date or at-risk date of a task is changed.
– The priority of a task is changed.
•Process instances:
– An instance is started, completed, suspended, resumed, terminated, or restarted.
– An instance failed.
– The due date or at-risk date of an instance is changed.
For example, business data for a process instance that exists when a task and its corresponding process instance activity are completed is indexed with the task and instance. Process participants can find the task or instance by searching the instance business data. If a task form consists of several coach views but only one coach view is complete, the updates from this coach view are not searchable until all the coach views in the task form are complete.
By default, the previous tasks in a process instance are not indexed again when later tasks are completed and the business data for the process instance is updated. If you want the updated business data to be searchable from previously completed tasks, change the value of the <task-index-update-completed-tasks> configuration setting (see Table 4-2) to true in the 100Custom.xml file. If the process instance includes many previous tasks, reindexing these tasks might degrade the system performance.
Table 4-2 XML tags that can be used to change the index configuration settings
|
XML tag
|
Description
|
|
<task-index-enabled>
|
This Boolean value determines whether indexing is enabled. The default value is true. If the index does not exist, it is created.
To turn off indexing, change the value to false. If the index does not exist, it is not created.
Restriction: If indexing is turned off, the search field in the Process Portal user interface is hidden. The Process list, the Process Performance dashboard, and the Team Performance dashboard also do not work correctly.
|
|
<task-index-update-interval>
|
This integer value specifies the time between index updates in seconds. The specified interval determines when the state of the instance variables is captured for tasks that completed since the last index update. Only those tasks that are completed during the current interval are searchable with the latest instance data.
The default value for the update interval is 5 seconds. The minimum value is 1 second.
|
|
<task-index-update-completed-tasks>
|
This Boolean value controls whether the index is updated for previously completed tasks. The default value is false, which means that only the task that was just completed and open tasks are updated in the index.
If you change the value to true, Instance-level updates, such as business data that is updated later in the process, is propagated to completed tasks.
Although the system has more work to index completed tasks, searches on completed tasks are based on the final instance business data.
Users with many assigned tasks experience improved performance of queries on active process instances because the queries can filter out tasks from completed instances.
|
|
<task-index-store-fields>
|
This Boolean value controls whether the actual field values are stored as separate fields. The default value is false, which means that the actual field values are not stored as separate fields. You might want to change the value to true for debugging purposes because it improves the readability for people and it allows queries by other search tools.
|
|
<task-index-work-manager>
|
This string contains the JNDI name of the work manager that is used by the indexing process to manage the search index. The default value is wm/default, which is the default work manager for WebSphere Application Server.
To improve the performance of the index creation, in the administrative console you can create a dedicated work manager with a greater number of available threads. You can then use this tag to switch to the new work manager.
|
|
<task-index-include-system-tasks>
|
This Boolean value controls whether system tasks are indexed. To enable system tasks to be displayed in Gantt charts in Process Portal, ensure that the value of this tag is set to true. If the value of this tag is to false, system tasks are not displayed in Gantt charts.
|
|
<process-index-instance-completion-best-effort>
|
This Boolean value controls whether completion dates are created when instances that are migrated from previous versions of IBM BPM are indexed. The default setting is false.
If you change the value to true, the last completion date of the associated tasks is used for the instance completion date. If no associated tasks exist, the last modified time stamp of the instance is used as the completion date.
|
For more information, see Administering the Process Portal index IBM BPM 8.5.7 at the following IBM Knowledge Center website:
4.6 Process Federation Server
Federated environments consist of Process Federation Server and multiple federated IBM BPM systems. Use properties in the Process Federation Server server.xml configuration file to configure an IBM BPM system for the federated environment and configure and maintain the indexing service for the system.
4.6.1 Modifying configuration properties
You can modify all the general configuration properties in the ibmPfs_federatedSystem element for a federated IBM BPM system, except the index.number_of_shards property. You also can modify the indexer and retriever implementation properties that are specific to the system type.
4.6.2 Removing a federated IBM BPM system
To remove an IBM BPM system from the federated environment, in the server.xml file, remove or comment out the ibmPfs_federatedSystem element and the associated indexer and retriever elements for the system. The indexing service on the Process Federation Server node stops and the index is removed from federated queries. The index is still available on the node so that you can re-enable the IBM BPM system later.
To completely remove the index, stop all process federation servers and delete the corresponding index from the following directory on the Process Federation Server node:
/elasticsearch/data/federated_cluster/nodes/node_name/indices
To keep the federated IBM BPM system configured but temporarily stop the indexing service, remove or comment out the indexer element; for example, the ibmPfs_bpdIndexer element.
4.6.3 Rebuilding an index
If problems occur with the Process Federation Server index, you can rebuild it.
Complete the following steps to rebuild an index:
1. Stop all process federation servers.
2. Delete the index from the /elasticsearch directory on the file system on all process federation servers.
3. Restart all process federation servers.
The index is rebuilt.
4.6.4 Monitoring and administering an index
Elasticsearch provides an HTTP-based REST API to query, monitor, and administer the Elasticsearch service and indexes. For production environments, Process Federation Server provides forwarder applications to secure REST requests through an HTTPS secure connection. For more information, see the following resources:
•Enabling monitoring and administration of the Elasticsearch service:
•Maintaining IBM BPM systems in federated environments IBM BPM 8.5.7, at the following IBM Knowledge Center website:
4.7 Other data
Although most data accumulation comes from process, tasks, and events, other areas of accumulation must be considered over time as described in this section.
4.7.1 Document attachments
Heritage Coaches support uploading documents to an internal document store by using APIs and pre-supplied controls. Although these documents are not separately deletable, they are associated with process instances and as such, they are deleted when process instances are deleted. Alternatively, you can write your own service to delete these documents by using the JavaScript method deleteAllVersions in TWDocument.
When next generation Coaches were first introduced in V8.0.0 and V8.0.1, no equivalent built-in document attachment store capability was supplied (although there is support for accessing external enterprise content management systems).
However, this built-in attachment capability was reintroduced in V8.5.0 that uses the same Coach views that are used for external ECM systems. As with heritage Coaches, there is no explicit means of deleting these attachments, but they are deleted when their parent process instances are deleted and can be programmatically purged by using deleteAllVersions.
4.7.2 Temp directory
During installation and some operations at run time, files are placed in the system temp directory (%temp%). These files can accumulate over time, so monitor this directory and develop a policy to occasionally purge it.
4.8 IBM Business Monitor
If you use IBM Business Monitor, occasionally purge data there because it can quickly accumulate. There is mature support in IBM Business Monitor for deleting and archiving data. Business Monitor includes an event purging capability in the administrative console that you configure per monitor model, as shown in Figure 4-5.
Figure 4-5 Purging Event Console page in IBM Business Monitor
You can specify the age of the instances to be deleted, and optionally identify a directory in which to archive the purged instances as a CSV file.
|
Important: This function purges terminated instances only; it never removes in-flight instances, regardless of age.
|
This purging and archiving can be done once, as described in Purging and archiving instance data, which is available at this website:
Purging also can be scheduled to run regularly, as described in Schedule purging and archiving instance data, which is available at this website:
4.9 IBM BPM and IBM Business Monitor Purging summary
This section highlights key areas of accumulating data that you must be aware of in IBM BPM and Business Process Monitor. It also describes how to purge that data. The data types and options for purging it in various releases are listed in Table 4-3.
Table 4-3 Options for purging various types of data based on release
|
Data
|
V7.5.1.x
|
V8.0.1.x
|
V8.5.0.x
|
|
Process apps and toolkits in Process Center
|
Archive and delete with Process Center UI
|
Archive and delete with Process Center UI
|
Archive and delete with Process Center UI
|
|
Snapshots in Process Center
|
BPMSnapshotCleanup command in V7.5.1.2
|
BPMSnapshotCleanup command in V8.0.1.2
|
BPMSnapshotCleanup, plus scheduled service added in V8.5.0.1
|
|
Advanced BLA and EARs in Process Center
|
Undeploy with Process Center UI to remove BLA and EARs
|
Undeploy with Process Center UI to remove BLA and EARs
|
Undeploy with Process Center UI to remove BLA and EARs
|
|
Snapshots in Process Server
|
BPMDeleteSnapshot command in V7.5.1.2
|
BPMDeleteSnapshot command in V8.0.1.0
|
BPMDeleteSnapshot command in
|
|
BPD Process Instances
|
LSW_BPD_INSTANCE_DELETE stored procedure
|
BPMProcessInstancesCleanup command in V8.0.1.2
|
BPMProcessInstancesPurging command in V8.5.7 and
BPMProcessInstancesCleanup command, enhanced in V8.5.0.1
|
|
BPEL Process Instances
|
deleteCompletedProcessInstances.py script or Cleanup Service in BFM
|
deleteCompletedProcessInstances.py script or Cleanup Service in BFM
|
deleteCompletedProcessInstances.py script or Cleanup Service in BFM
|
|
BPD durable events
|
BPMDeleteDurableMessages command in V7.5.1.2
|
BPMDeleteDurableMessages command in V8.0.1.2
|
BPMDeleteDurableMessages
|
|
Performance Data Warehouse
|
prune command in V7.5.1.2
|
prune command in V8.0.1.2
|
prune command in V8.5.0.1
|
|
Business Monitor
|
The Purge and Archive Instance Data console action and schedulable service
|
The Purge and Archive Instance Data console action and schedulable service
|
The Purge and Archive Instance Data console action and schedulable service
|
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.