This chapter describes how to perform administrative tasks using Oracle Business Process Composer. Users who are assigned administration privileges can perform administrative tasks including managing Oracle Business Process Composer spaces, managing projects, and enabling the process player feature.
Note:
The procedures described in this chapter can only be performed by users who have been granted the Project Administrator security role. For more information, see How to Grant Administrator Privileges to a Business Process Composer User.
This chapter includes the following sections:
Oracle Business Process Composer allows you to assign administrator privileges to a user.
When a user has administrator privileges, they have access to the Administration view accessible from the Oracle Business Process Composer application welcome page, as shown in Figure 2-1.
Figure 2-1 Oracle Business Process Composer - Administrative View
Administrators can perform the following tasks:
Configure and remove Business Process Composer spaces.
Delete projects.
Release locks on projects.
Configure administrator credentials for process player.
View and delete reports.
Administrator privileges are granted by assigning the Administrators group to an Oracle Business Process Composer user.
To grant administrator privileges:
The Oracle Business Process Composer user now has administrator privileges.
Users who have been granted administrator privileges can access the Administration view from the application welcome page.
How to access the administrator view:
Spaces enable you to define which Oracle Business Process Composer users have permission to view and edit Business Architecture (BA) and Business Process Management (BPM) projects.
Figure 2-2 Administrative View - Spaces Administration
Use the spaces administration feature to perform the following:
View the status of a BPM space.
Share a BPM space.
Delete a BPM space.
Using the Spaces Administration dialog you can define which users or groups of users can view or edit a BPM space.
To add users to a BPM space:
Use the Spaces Administration dialog to remove users from a BPM space.
To remove users from a BPM space:
Use the Administrative View to delete a BPM space from the Oracle BPM repository.
To delete a BPM space:
Note:
Deleting a BPM space deletes the space and all of the business architecture and BPM projects it contained. After deleting a BPM space, its contents cannot be recovered.
Use the Oracle Business Process Composer administrative view to manage projects.
Figure 2-3 Administrative View - Projects Administration
Administrators can release the locks on shared projects that have been locked by another user.
To release the lock on a shared project:
Administrators can delete projects.
Note:
Administrators cannot perform tasks on private projects. Only the project owner has access to private projects.
To delete a shared project:
After deleting a project, it is removed from the Oracle BPM repository.
To configure which users and groups have access to a project, you must configure sharing on the Oracle Business Process Composer space containing the project. You cannot configure sharing on a specific project. See Configuring Access to a BPM Space for more information.
Process player enables you to test the behavior of a business process at design time using Oracle Business Process Composer. You can test a process as different user IDs without having to deploy the BPM project and test the processes using Oracle Business Process Workspace.
See Using Process Player for more information.
When testing a business process, process player deploys a version of the BPM project to runtime using a special runtime partition. This allows process player to run a process using the same environment as a normally deployed BPM project.
To enable the process player feature in Oracle Business Process Composer, you must first provide the service-oriented architecture (SOA) administrator credentials. Oracle Business Process Composer uses the SOA administrator credentials to:
Deploy a version of the project at runtime.
Perform tasks on the process instance as different users.
After you provide the SOA administrator credentials, any user who has edit privileges on a project can run process player.
When starting process player, Oracle Business Process Composer deploys the project to runtime using these credentials. When the current user wants to perform an activity or task as another user, Oracle Business Process Composer also uses these credentials.
Before Oracle Business Process Composer users can access process player, you must enable it by providing the SOA administrator credentials, as shown in Figure 2-4.
To enable process player:
After enabling process player, Oracle Business Process Composer users can use it to test the behavior of their business processes. See Using Process Player to Test the Behavior of Business Processes for information.
Enabling process player makes it available to all Oracle Business Process Composer users. Any user who has edit privileges on a BPM project can run process player.
After you have enabled process player, you can disable it when necessary.
To disable process player:
Use the Administrative view information about each of the reports created within a Oracle Business Process Composer installation.
You can also use the Administrative View to delete reports.
You can use the Administrative View to view a list of reports.
To view reports:
Oracle Business Process Composer displays a list of reports in a table containing information about each report. See the Oracle Business Process Composer context-sensitive online help for information about each column in the table.
Use the Administrative View to delete a report.
To delete a report: