BPM Composer - A Life

Role Based Development & Deployment

As BPM 11g matures, so does BPM Composer... it is becoming the default UI for BPM development, both for processes and rules, especially from a "Business User" perspective.

This blog explains how to control access to projects, and more importantly, how to secure deployment of those projects.... 

Share Project in BPM MDS 

1. Assuming that the project has been created initially in BPM Studio (JDev).

2. Save the project to BPM MDS (weblogic user).... 

3. Unlock the project, releasing it from BPM Studio control (notice the user name in the MDS navigator...."weblogic")...

Share Project Within BPM Composer 

4. Log on to BPM Composer with the same user as the BPM MDS connection (weblogic)....

5. Choose the project, it is marked as "Private"....

6. Clicking on "Private" brings up the "Share" wizard....

7. Choose the users/groups to share with, the "LoanAgentGroup"....

 8. Choose what privileges to give the group ("viewer") and "Share".... 

9. Repeat for "Editors" privilege....

10. Log into BPM Composer with a user not in any role granted privileges ("jstein" in this case)....

... can only see his projects.

12. Log into BPM Composer with user in the "Viewer" role....

... can view the project but cannot edit (no edit option available)....

Secure Deployment in BPM Composer 

13. Log into BPM Composer with user in the "Editor" role...

...can now "Edit" the project.

14. Edit the project and try to "Deploy"....

..."Deploy" option is not available (greyed out).

15. Log into BPM Composer as "Project Owner" and try clicking deploy again....

...it is possible this time. 

16. Before deploying create an Approval Workflow....


17. Choose a user (or group) who should approve the deployment....

18. Now try to deploy....

...must send for Approval....

19. Log into BPM Workspace as the deploy approver...

...and Approve...


20. Log back into BPM Composer as the project owner and browse the "Approval Workflows"....

21. Notice the deployment has been approved....

22. Select it and "Deploy"....


 23. Provide at least the necessary user/pwd and revision....

 24. And Deploy....

Comments:

Could you extend above sample with getting changes from Composer bac into JDeveloper?
Most likely the process developer wants to work in JDeveloper, while the process owner wants to work in Composer.
Topics such as: share, (un)lock, checkout, update would be great.

Posted by NIkolaj on January 31, 2013 at 02:54 AM PST #

Post a Comment:
  • HTML Syntax: NOT allowed
About


This is the blog for the Oracle FMW Architects team fondly known as the A-Team. The A-Team is the central, technical, outbound team as part of the FMW Development organization working with Oracle's largest and most important customers. We support Oracle Sales, Consulting and Support when deep technical and architectural help is needed from Oracle Development.
Primarily this blog is tailored for SOA issues (BPEL, OSB, BPM, Adapters, CEP, B2B, JCAP)that are encountered by our team. Expect real solutions to customer problems, encountered during customer engagements.
We will highlight best practices, workarounds, architectural discussions, and discuss topics that are relevant in the SOA technical space today.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today