Java embedding activity is a means of embedding Java and J2EE code directly inside Oracle BPEL process. Even though java embedding can provide enhanced functionality (since you can plug in any java code here!!), this should be avoided as much as possible – since the code would be harder to manage and will not be “SOA” like. Since this is an Oracle extension, it is not part of BPEL standard spec – hence won’t be portable!!
SOA Suite 11g benefits from OPSS (Oracle Platform Security Services) to externalize application security. OPSS provides a unified security layer to Oracle Fusion Middleware products like Weblogic Server, SOA Suite, Webcenter, ADF etc., The major advantage is the single centralized security framework that can be used for both Oracle and non-Oracle environments thus reducing maintenance and integration costs.
In this example, we are going to explore how to secure BPEL process using an authentication and encryption policy: “oracle/wss10_username_token_with_message_protection_service_policy”.
Steps to implement this example:
- Create key stores for client and server.
- Import server key store into Weblogic server.
This tutorial explains how to create custom XPATH functions that can be used across all SOA Suite components. You can learn how to implement IXPathFuction interface, create appropriate configuration files, update JDeveloper to use the plugin in design time, make the library available to SOA Server’s runtime and finally use it in a simple BPEL program.
Please complete part1 of this example before continuing …
- Create an SOA project and name it “OrderSDOProcess”. Select Empty Composite from next screen and click Finish.
- Make a note of OrderSDO service WSDL we created in previous step. In my case, it is http://192.168.0.5:7001/OrderBCServices/OrderSDOService?WSDL.
- Drag and drop a BPEL Process component on to components section of composite.xml. Name it “OrderSDOProcess”. Select “Base on a WSDL” as template.