PAM comes with an integrated subversion source control system for version management of BPM assets and can be integrated with OPSS for security and can reference the MDS for run-time artifacts.
So let’s see the lifecycle of PAM from the two different interfaces, starting with the Process Composer.
For the needs of this tutorial I have created a sample Hello BPM project with a synchronous process.
The new workspace has been enhanced with the introduction of roles and priviledges assigned at the space level. The 12c version supports three personas, the Owner which maps to the Process Architect, the Viewer which maps to the Process Business Analyst and the Editor which maps to the Process Business Developer.
Furthermore, for each space, you can create multiple projects (BA and BPM projects) which helps in organizing all the processes in business relevant projects.
Start the integrated JDeveloper Weblogic Server instance and if this is the first time you are starting the integrated Weblogic Server you will be asked to provide the admin credentials and listening address for your integrated Weblogic Server.
To share and make a BPM project available in Composer, right click your BPM project and from the context menu select “Save to PAM”. This will bring up the “Select Connection” window. If this is the first time you are publishing to PAM you will have to create a new PAM connection by clicking on the green “Add” icon (and going through the wizard).
Click “OK” and in the “Save Project to PAM” window you can optionally define some comments and click “OK” to publish to PAM.
Go to BPM Process Composer (http://<hostname:<port>/bpm/componser) and login as weblogic to see your published BPM project.
The Composer has been enhanced with some really nice new features, especially around the area of Business Architecture that I will elaborate further in a subsequent post.
When you edit a BPM project in BPM Composer, PAM will lock the BPM project, meaning that other Composer users will not be able to work it but just view the project.
To publish you changes to PAM and the SCC (Source Code Control) you need to click on the “Publish” button (second button in the screenshot above).
When you click on the “Publish” button you will be prompted with the “Publish Project” window where you have to provide a comment to explain what your changes are about and optionally release the lock and make a snapshot which is nothing more than an SVN tag on your BPM project.
To do so, open the “Process Asset Manager Navigator”, expand your connection name (in my case it is l”ocal-PAM”), space name (in my case it is “Hello World Space”) and right click on the project name (in my case it is “HelloWorldBPM”) and from the context menu select “Check Out”.
Click “OK” to check out the BPM project.
To get the latest changes from PAM you can do an “Update” using the project’s context menu.
In case of conflicts there is a visual “Diff-Merge” editor to resolve the conflicts.