Oracle BPM Studio Use Cases Introduction to JDeveloper Roles

3-2 Modeling and Implementation Guide for Oracle Business Process Management Process developers who need access to the complete functionality of the Oracle BPM and SOA Suites should use the default role.

3.2 Overview of the Application Development Life Cycle

This section describes the application development life cycle from the perspective of a process developer using Oracle BPM Studio.

3.2.1 Introduction to Modeling, Implementation, and Deployment

The different workflows of the application development cycle described in the following sections are divided into the following stages: ■ Modeling ■ Implementation ■ Deployment In a real-world application development environment, the distinctions between these stages may not be clearly defined. Process developers may need to add to or change a process when creating an application. A final production application may go through several iterations of modeling and implementation before it is deployed as a working application. Additionally, applications may be deployed for testing then passed back to the modeling and implementation stages before being deployed to a production environment.

3.2.2 Workflow: Modeling, Implementing, and Deploying an Application

Figure 3–1 shows a typical workflow where all stages of application design are performed using Oracle BPM Studio. Figure 3–1 Modeling, Implementation, and Deployment from Studio 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 Introduction to Oracle BPM Studio 3-3 The Modeling Process Analyst section contains a rectangle with the number 1 and labeled Oracle BPA Suite. From this rectangle, an arrow numbered 2 extends into the Implementation section to a rectangle numbered 3 and 4, and labeled BPM Studio. From this BPM Studio rectangle in the Implementation section, two arrows extend. The first arrow extends to an oval on the divider between the Implementation and Deployment sections. The oval is numbered 5a and labeled MDS. From the oval labeled MDS, an arrow extends into the Deployment section to a rectangle labeled BPM Runtime. The second arrow from the BPM Studio rectangle extends to a rectangle on the divider between the Implementation and Deployment sections. The rectangle is numbered 5b and labeled SAR File. From the SAR File rectangle, an arrow extends to the BPM Runtime rectangle in the Deployment section mentioned earlier. The following steps describe each stage of the workflow: 1. Create process models using Oracle BPM Studio process analyst process developer. 2. Implement the required services and application resources process developer. 3. Compile the application process developer. 4. Deploy to Oracle BPM runtime process developer process administrator.

3.2.3 Workflow: Creating Applications Based on Process Blueprints

Figure 3–1 shows a typical workflow for using Business Process Composer to perform the initial stages of the application development life-cycle. Figure 3–2 Using Oracle Business Process Composer to Create Project Blueprints This graphic is a rectangle divided into three sections. The first section is labeled Modeling Process AnalystProcess Developer, the second is labeled Implementation