System and sample applications

Edit online

Learn about the various types of system process apps and discover tips to avoid issues.

The following process apps are system applications:
  • Ad-hoc Reports (ADHOC) - a hidden internal application
  • Performance (SYSPERFDB) - used for performance dashboards features. For more information, see Traditional: Discovering and managing database performance issues by using the Performance Dashboard.
  • Process Portal (SYSRP) - used for part of the Process Portal application, this process application is the primary UI that business users can use to perform their work when using process solutions developed using IBM® Business Automation Workflow from either a desktop or mobile device browser. The Process Portal process app is implemented entirely from coaches and coach views. Some of the features provided by Process Portal can be modified to better suit the needs of business users. For more information, see Getting started with Process Portal, Administering Process Portal, and Customizing Process Portal.
  • Heritage Process Portal (TWP) - used for part of the Heritage Process Portal application, this process app is the older version of the Process Portal process app, which was used by default with IBM Business Process Manager V8.5.6 and earlier versions. This process app provides the Team Performance, Processes, and Process Performance dashboards, which the Process Portal process app refers to and are made available to users accessing Process Portal. For more information, see Customizing Heritage Process Portal and Customizing the IBM Business Automation Workflow dashboards.
The following samples are of business process management applications. For more information, see the Tutorials.
  • Hiring Sample (HSS)
  • Hiring Sample Advanced (HSAV1)
  • Procurement Sample (STPPS1)
  • Discover UI Sample (DBPMUIS)

Tips to avoid issues

Important: For system applications
  • Don't modify any of system applications or toolkits (except as documented like for Process Portal customization).
  • Don't edit the project or snapshot properties, like changing the names or acronyms for a system application or toolkit, because it will cause issues for upgrade commands.
  • Don't deactivate, archive, or delete system snapshots or you might experience issues while upgrading or using Business Automation Workflow features.
Important: For sample applications
  • You can modify the sample applications to perform testing or learn about the product.
  • You can deactivate, archive, or delete the sample applications, although upgrading the product will cause the application to be updated or redeployed if it was removed.
  • Don't edit the project or snapshot properties to change the names or acronyms because it will cause issues for upgrade commands.

If you archive or modify names or acronyms for these applications, ensure that you undo the changes before you try to upgrade. If you upgrade and experience issues, you might have to roll back the upgrade before you can correct the problem.

In most cases, if you delete a system toolkit you just need to run the bootstrapProcessServerData command to reinstall the system toolkit. For more information, see Loading the database with system information in a network deployment environment on Windows.