Workflow: Creating Applications Based on Process Blueprints

3-4 Modeling and Implementation Guide for Oracle Business Process Management Process Developer, and the third is labeled Deployment Process DeveloperBusiness Administrator On the divider between the Modeling and Implementation sections, there is a rectangle numbered 1, 2, and 3, and labeled BPM Studio. From the BPM Studio rectangle, an arrow extends to an oval on the divider between Implementation and Deployment. The oval is numbered 4 and labeled MDS. An arrow extends from this oval to a rectangle in the Deployment section labeled BPM Runtime. The following steps describe each stage of this workflow: 1. Create blueprints using Business Process Composer process analyst 2. Publish the project containing the process blueprint to MDS process analyst 3. Open the project in Oracle BPM Studio process developer 4. Implement the project as part of a process-based business application. process developer 5. Deploy the project to runtime or save as a project template a. Deploy the process to runtime process developer, business administrator, or b. Save the application as a project template process developer c. Export the project as a SAR file process analyst, which is then deployed to Oracle BPM run time business administrator

3.2.4 Workflow: Creating Project Templates

Figure 3–1 shows a typical workflow for using Oracle BPM Studio at the beginning of the workflow to create process templates which are then edited by process analysts using Business Process Composer. Figure 3–3 Using BPM Studio to Create Project Templates Introduction to Oracle BPM Studio 3-5 This graphic is a rectangle divided into three sections. The first section is labeled Modeling Process Analyst, the second is labeled Implementation Process Developer, and the third is labeled Deployment Process DeveloperBusiness Administrator In the Modeling section, there is a rectangle numbered 1 and Business Process Composer . From this rectangle, an arrow extends to an oval on the divider between the Modeling and Implementation sections. The oval is numbered 2 and labeled MDS. From the oval labeled MDS, an arrow extends to a rectangle in the Implementation section numbered 3 and 4 and labeled BPM Studio. From the BPM Studio rectangle, an arrow extends to an oval on the divider between Implementation and Deployment. This oval is numbered 5a and labeled MDS. From this second MDS oval, two arrows extend. The first arrow, numbered 5b, extends back to the Business Process Composer rectangle in the Modeling section. The second arrow extends to a rectangle in the Deployment section labeled BPM Runtime. The following steps describe each stage of this workflow: 1. Create a project template using Oracle BPM Studio process developer. 2. Publish the template to MDS process developer. 3. Create a new project based on the project template using Business Process Composer. process analyst. 4. Edit the processes within the project based on the edit policies defined by the template process analyst. 5. Validate the project process analyst. 6. Deploy the project or return the project to the process developer by republishing to MDS. a. Deploy the process directly to Oracle BPM run time process analyst, business administrator. This may require an approval workflow. b. Republish the project to the Oracle BPM MDS partition. process analyst Republishing the project enables you to share it with other process analysts or with process developers who are responsible for implementing your business processes within an overall application. c. Export the project as an SAR file process analyst. This file can be deployed to Oracle BPM run time process administrators.

3.2.5 Workflow: Integration between the Oracle BPM Suite and Oracle BPA

Figure 3–4 shows a typical workflow for creating process models using the Oracle BPA Suite, then using Oracle BPM Studio to create and deploy process-based business applications.