Log Window Documentation Window

Part II Using Oracle BPM Studio This part describes how to create and use Oracle BPM projects and project templates. It also describes how to create processes and use the process editor. This part contains the following chapters: ■ Chapter 4, Working with Projects and Project Templates ■ Chapter 5, Working with Processes and the Process Editor Working with Projects and Project Templates 4-1 4 Working with Projects and Project Templates This chapter describes how to create and use projects using Oracle BPM Studio. This chapter includes the following sections: ■ Section 4.1, Introduction to Oracle BPM Projects ■ Section 4.2, Creating and Working with Projects ■ Section 4.3, Introduction to Project Templates ■ Section 4.4, Working with Project Templates ■ Section 4.5, Using the Oracle BPM Metadata Service MDS Repository

4.1 Introduction to Oracle BPM Projects

A BPM project is a container for the resources used to create and support business applications created using Oracle BPM. Oracle BPM projects are based on SOA projects but they include additional functionality of the Oracle BPM Suite, including BPMN processes. You can create new projects directly in Business Process Composer or you can create and edit projects based on project templates. Projects can be shared between Business Process Composer and Oracle BPM Studio or deployed to BPM runtime. See Section 3.2, Overview of the Application Development Life Cycle for information on how projects are used within the development life-cycle.

4.1.1 Introduction to Project Resources

Each BPM project contains one or more business process and may include other resources used by the business processes or overall application. This can include other reusable resources that allow you to connect your application to other applications and systems. The following are the key resources of an Oracle BPM project: ■ Processes: can include both BPM and BPEL processes. ■ Activity Guide: includes project milestones defined for each BPMN process. ■ Organization: includes the organization elements used to mimic the organizational structure of your organization within BPMN process models. ■ Business Catalog: includes reusable services including services, adapters, and human tasks. 4-2 Modeling and Implementation Guide for Oracle Business Process Management ■ Simulations: includes the simulations models defined for a project and individual BPMN processes. ■ Resources: contain the XML transformations define for your project. Each of these resources are accessible from the BPM Project Navigator. Additional application resources are accessible from the Application Navigator.

4.1.2 Sharing Projects Between Oracle BPM Users

Oracle BPM uses the Oracle MDS repository to share projects and project templates between other Oracle BPM Studio and Business Process Composer users. See Section 3.2, Overview of the Application Development Life Cycle for more information on how projects and project templates are shared between BPM Studio and Business Process Composer. See Section 4.5, Using the Oracle BPM Metadata Service MDS Repository for more information on the Oracle BPM MDS repository.

4.2 Creating and Working with Projects

The following section describes how to create new Oracle BPM projects and perform other project-related tasks. See Section 4.5, Using the Oracle BPM Metadata Service MDS Repository for information on working with projects in Oracle BPM MDS.

4.2.1 How to Create a New Project

Oracle BPM projects are created in the same way as other types of SOA composite application components. To create a new Oracle BPM project: 1. From the File menu, select New. 2. Under Categories, select BPM Tier, then select BPM Project. 3. Click OK. 4. Enter a name for your project.

5. Ensure that BPM and SOA appear in the Selected column.

6. Click Finish.

The new project is created and appears in the project navigator. After creating the project, the New Process Wizard starts automatically. You can choose to create a new process or cancel the wizard. See Section 5.1.2, How to Create a New Business Process for more information on creating a new BPMN process.

4.2.2 How to Open a Project from the File System

You can open an Oracle BPM project directly from the file system. This is generally used to open local projects that you have previously closed. Projects that are shared with other users are imported from an exported Oracle BPM project or using Oracle BPM MDS. Working with Projects and Project Templates 4-3 To open a project: 1. Select File, then Open. 2. Browse to the location of your project folder. 3. Select the Java Project .jpr file for your project

4. Click Open.

The project appears in the project navigator.

4.2.3 How to Export a Project

Exported projects enable you to share projects with other Oracle BPM Studio users. This is useful when it is not feasible to share projects by publishing them to Oracle BPM MDS. To export a project: 1. Select Export from the File menu. 2. Select Export as BPM Project, then click OK. 3. Provide a name for your project, the browse to the location where you want to export the project.

4. Click Next

5. Click Next, then Click Finish.

4.2.4 How to Import a Previously Exported Project

After you export an Oracle BPM project from Oracle BPM Studio or Oracle Business Business Process Composer, you can import it back to Oracle BPM Studio. This enables you to share projects directly from a file system instead of using Oracle BPM MDS. To import a project 1. From the File menu, select Import. 2. Select Import BPM Project, then click OK. 3. Browse to the location of the .exp file of the exported project, the click Open. 4. Select a project root folder, then click Next. 5. Provide a project name, then click Next. 6. Click Next, then Finish.

4.2.5 How to Edit Project Preferences

You can edit project preferences to configure the behavior of an Oracle BPM project, including the following: ■ Configure sampling points and Process Analytics. ■ Configure general process properties. Note: When you open a project from the file system, the project remains in its original location. It is not copied to the Oracle Jdeveloper working directory.