Gabriel Jeremiah Campbell has a Bachelor of Science Honours Degree in Applied Mathematics and Computer Science from the National University of Science and Technology (NUST). I am a Sun Certified Java Programmer(SCJP) and Sun Certified Web Component Developer(SCWCD). I have worked as Junior Lecturer in Computer Science for 3 years. I have been actively developing software in Java for 4 years. I have also coded in C/C++. When not at a computer (or thinking about a computer) I enjoy sci-fi movies, cycling, nature walks and photography. Gabriel Jeremiah is a DZone MVB and is not an employee of DZone and has posted 9 posts at DZone. You can read more from them at their website. View Full User Profile

Securing a BPEL in WebSphere Integration Developer 7 difference over WebSphere Integration 6

  • submit to reddit

Today we look at how to add a role-based security to secure a BPEL.

In WebSphere Integration Developer(WID) 6 there was no direct way to add a role to a BPEL at assembly level.

In WID 7 we can assign a role to the whole BPEL this could not be done in WID 6. It makes security much easier.

All you have to do is open your assembly diagram as in our example project below:




Click anywhere on the assembly diagram. Then click Properties on the BPEL and then click All Qualifiers.

Expand ExtractionProcess. As you can see above the is Security Identity. Here you can place a security role:



There you have it the entire Process is secured. On deployment make sure that role is allocated to a user that should have access to the BPEL application:


That’s all there is to it! Enjoy Smile



Published at DZone with permission of Gabriel Jeremiah Campbell, author and DZone MVB.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)