Producing JSR 168 Portlets Directly From ADF Task Flows with Oracle WebCenter 11g

While working with different customers, I'm getting questions about how to expose ADF Task Flows to third party Portals. Its especially important for those companies who are developing their own products based on Oracle Fusion Middleware 11g. You need to ensure that your product will be pluggable and compatible with different environment. Just imagine, in Oracle ADF 11g with WebCenter 11g you can expose your ADF Task Flows through portlet bridge as standard JSR 168 portlets and plug them into different Portals.

I continue series of posts related to integration area with new sample application - ADFIntegration7.zip. I will describe how you can expose ADF Task Flow as portlet, and then how to consume this portlet from WebCenter 11g application. Developed sample contains one ADF Task Flow with region:

I will define portlet bridge for this ADF Task Flow, and will expose available fragment:

First Part: Exposing ADF Task Flow as portlet

Its enough to right click ADF Task Flow and select Create Portlet Entry option:

Complete wizard steps, and you are done - portlet bridge is defined. Now define WAR deployment profile, we will use it to deploy portlet to WebLogic server:

For test purpose, I will use JDeveloper 11g embedded WebLogic server instance, you can start it directly from JDeveloper 11g:

Right click ViewController project and select - Deploy:

While deployment process running, you will be asked to proceed with JSR 168 portlet deployment:

From deployment log you will see application URL:

Open this URL in your browser, you can test WSDL URL from there:

Second Part: Consuming portlet in WebCenter 11g application

In Resource Palette define new WSRP Producer Connection:

You will need to specify portlet WSDL URL:

Portlet should become visible in Resource Palette, you can drag and drop it from there directly on your page, same as any other component:

Let's drag and drop it on JSPX page available in another application:

On runtime, Employees Editing portlet will be loaded, and user will see it same as it would be usual ADF application. In this case both - Query Criteria and results table are coming through consumed portlet: