Resetting the test environment

You can use the Case Builder Reset Test Environment feature to remove the deployed solutions and other data from the development environment project area.

Before you begin

Ask your system administrator to temporarily increase the timeout values for the WebSphere® Application Server transaction service, ORB service, and target object store data source connection pools for both the IBM® Business Automation Workflow and Content Platform Engine application servers. The optimal timeout values depend on the speed and complexity of the system. For example, 1200 seconds is appropriate for most systems. In addition, reset the initial and maximum heap size for the same application servers as needed, according to the number of applications that are running on the servers. For example, set the initial heap size to 512 MB and set the maximum heap size to 1024 MB or a size that is consistent with the available RAM on the server.

After the reset actions complete, the system administrator can reset the timeout values and heap sizes to the previous values.

About this task

Over time, you might need to reset the development environment to provide a clean environment for further development and testing. Resetting the test environment returns the project area in the case management object store to the same state as just after you completed the configuration tasks. The target object store and the connection point that is associated with the project area are reinitialized, and all process configuration information is removed.

Because you might have several people working in the development environment on multiple projects, you can define project areas to limit the effects of resetting the test environment. For example, you can group users that are working on related solutions in the same project area. Therefore, when you reset the test environment, only the solutions and artifacts in one project area are removed. The entire design object store is not affected, and other Case Builder users can continue working without interruption.

Important: Resetting the test environment removes all of the data from the project area in the development environment, including any FileNet® P8 assets that you copied from your production environment and any assets you defined outside of Case Builder to extend the solution design, such as reused class definitions or property templates. If your environment reuses existing FileNet P8 assets to provision the development environment, certain assets can be automatically restored by the reset test environment operation if the development environment was prepared as described.

You might need to reset the environment in the following situations where modifications can only be applied to a fresh development target object store:

  • Some changes are not allowed as part of solution redeployment.
  • Artifacts from deployed solutions cannot be deleted by using Case Builder. For example, any documents that were defined in the object store must be removed by using other tools.
  • The development environment target object store might exceed the underlying database table limitations.
Tip: If your solutions are already deployed to a production object store, review the topic Redeployment restrictions for modifying a solution before you modify and redeploy a solution.

Procedure

To reset the test environment:

  1. Ensure that other applications, such as Case Client or Administration Console for Content Platform Engine, are not making changes to the target object store or querying the project area.
    Attention: Skipping this step can cause the reset operation to fail.
  2. Save user-defined assets from the target object store.
    You might have to ask a system administrator to save the assets.
  3. In Case Builder, click Actions > Reset Test Environment on the Manage Solutions page.
  4. If you are using Case Analyzer, use the Reset database option of the Case Analyzer Process Task Manager to initialize the Case Analyzer database.