Make the internal 10.1.3 ESB jms queues persistent

Standard are the internal esb queues jms memory queues. This is perfect for normal use but if you want to make an oracle esb cluster or make your own esb error handling then you can better make the esb queues database persistent. In this blog I will explain what to do.
I installed the 10.1.3.1 soa suite and upgrade this to 10.1.3.3. Then I apply patch 10.1.3.3.1. (patchset 6492514). You have to apply this patch if you want to use the esb_error queue.
First step is to update parameters of the esb repository so it uses the new jms database queues. Login with sqlplus to the oraesb schema and run the following script

delete esb_parameter where param_name = 'PROP_NAME_DEFERRED_TOPIC_JNDI';
delete esb_parameter where param_name = 'PROP_NAME_INITIAL_CONTEXT_FACTORY';
delete esb_parameter where param_name = 'ACT_ID_RANGE';
insert into esb_parameter values('PROP_NAME_DEFERRED_TOPIC_JNDI','ESBTopics/Topics/ESB_JAVA_DEFERRED');
insert into esb_parameter values('PROP_NAME_INITIAL_CONTEXT_FACTORY', 'com.evermind.server.rmi.RMIInitialContextFactory');
insert into esb_parameter values('ACT_ID_RANGE', '400');
update esb_parameter set param_value ='OracleOJMS/TCF' where param_name = 'PROP_NAME_DEFERRED_TCF_JNDI';
update esb_parameter set param_value ='OracleOJMS/XATCF' where param_name = 'PROP_NAME_DEFERRED_XATCF_JNDI';
update esb_parameter set param_value ='ESBTopics/Topics/ESB_CONTROL' where param_name = 'PROP_NAME_CONTROL_TOPIC_JNDI';
update esb_parameter set param_value ='OracleOJMS/XATCF' where param_name = 'PROP_NAME_CONTROL_TCF_JNDI';
update esb_parameter set param_value ='ESBTopics/Topics/ESB_ERROR' where param_name = 'PROP_NAME_ERROR_TOPIC_JNDI';
update esb_parameter set param_value ='OracleOJMS/TCF' where param_name = 'PROP_NAME_ERROR_TCF_JNDI';
update esb_parameter set param_value ='OracleOJMS/XATCF' where param_name = 'PROP_NAME_ERROR_XATCF_JNDI';
update esb_parameter set param_value ='ESBTopics/Topics/ESB_ERROR_RETRY' where param_name = 'PROP_NAME_ERROR_RETRY_JNDI';
update esb_parameter set param_value ='OracleOJMS/XATCF' where param_name = 'PROP_NAME_ERROR_RETRY_TCF_JNDI';
update esb_parameter set param_value ='ESBTopics/Topics/ESB_MONITOR' where param_name = 'PROP_NAME_MONITOR_TOPIC_JNDI';
update esb_parameter set param_value ='OracleOJMS/TCF' where param_name = 'PROP_NAME_MONITOR_TCF_JNDI';
update wf_agents set tcf_jndi='OracleOJMS/XATCF' where queue_type='DEFERRED';
update wf_agents set name ='ESBTopics/Topics/ESB_JAVA_DEFERRED' where queue_type='DEFERRED';
update wf_agents set queue_name ='ESBTopics/Topics/ESB_JAVA_DEFERRED' where queue_type='DEFERRED';
commit;
select * from esb_parameter;
select tcf_jndi, name, queue_type from wf_agents; 

Make sure that you enable enqueue / dequeue on the esb queues

Second step we have configure the oc4j server
We have to make a new OracleOJMS resource provider
1. Go to the Administration tab, Enterprise Messaging Service, then Database Persistence.
2. On the Database Persistence configuration page, click Deploy.
The Deploy Database Persistence Provider screen appears.
3. Make the following entries and selections:
Resource Adapter Module Name: OracleOJMS
Select Add a new resource provider to be used by this connector
Resource Provider Name: esbRP
Datasource JNDI Location: jdbc/esbaqdatasource

restart the soa suite server

1. Click the default application, Now you see the adapter, click on the OracleOJMS Resource Adapter Module
2. Click Create to create a connection factory.
Select javax.jms.XATopicConnectionFactory from the Connection Factory and click Continue.
3. The Create Connection Factory screen appears.
In the JNDI Location field, enter OracleOJMS/XATCF. Click Finish.
4. Click Create to create a connection factory.
Select javax.jms.TopicConnectionFactory from the Connection Factory and click Continue.
5. The Create Connection Factory screen appears.
In the JNDI Location field, enter OracleOJMS/TCF. Click Finish.
6. Click the Administered Objects tab and click Create.
Select oracle.j2ee.ra.jms.generic.AdminObjectTopicImpl and click Continue.
In the JNDI Location field, enter ESBTopics and in the resourceProviderName field enter esbRP
Now you can query the esb queue tables for errors.

re-use components with ADF Taskflow

With ADF Taskflow you can make page fragments or pages with navigation and re-use this many times in your own applications. Build ones and implement many times. Oracle is doing this too with the webcenter components. These webcenter taskflows are isolated litte programs with its own page fragements and model. If you want to make your own re-usable taskflows then you have to know some things. In this blog I will explain the things you should know. First you have to create a fusion web application. You can ignore the adfc-config.xml this is an unbounded taskflow. Unbounded taskflow don't have a fixed beginning and ending, so it can't be used for the ADF library jar. You have to create a bounded taskflow. There are three different bounded taskflows. The first is the page fragments option. You can use page fragments to add functionality to your page. For example you make a customer info page fragment and include this on the order page or in your marketing application. The others two bounded taskflows are a bit different. This is the train taskflow ( A train is a wizard to help the user to complete the transaction ) and the other is the normal taskflow with pages and methods like a logon flow or a order entry flow. With these two options you have to leave your page and the taskflow pages are shown and when you are ready then you can return to your page.
First we create a bounded taskflow with page fragments. We open this taskflow and add a view from the taskflow menu. Create a page fragment on this view.

<?xml version="1.0" encoding="windows-1252" ?>
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
  <task-flow-definition id="page1">
    <default-activity>page1</default-activity>
    <view id="page1">
      <page>/page1.jsff</page>
    </view>
    <use-page-fragments/>
  </task-flow-definition>
</adfc-config>

The next step is to create a bounded taskflow without the option page fragements.
Here we also can create a view but now we create a page and we also create a taskflow return. Between the view and the return we add a flowcase with the name return.

<?xml version="1.0" encoding="windows-1252" ?>
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
  <task-flow-definition id="page">
    <default-activity>startpage</default-activity>
    <input-parameter-definition>
      <name>param1</name>
      <value>#{pageFlowScope.inputParam1}</value>
      <class>java.lang.String</class>
    </input-parameter-definition>
    <view id="startpage">
      <page>/page.jspx</page>
    </view>
    <task-flow-return id="return">
      <outcome>
        <name>return</name>
      </outcome>
    </task-flow-return>
    <control-flow-rule>
      <from-activity-id>startpage</from-activity-id>
      <control-flow-case>
        <from-outcome>return</from-outcome>
        <to-activity-id>return</to-activity-id>
      </control-flow-case>
    </control-flow-rule>
  </task-flow-definition>
</adfc-config>

Open the jsf page and add a button with an action "return" else we can't go back to original page. To make this more interesting we add an input parameter to this taskflow and display the parameter on the jsf page.
It is very important to give the page, taskflow and the package name unique names else you can get errors that it finds for example two datacontrols in the same package location or it uses the wrong page.
The last step is to create an ADF library jar deployment profile. This deployment profile add all the bounded taskflows to the jar. This jar you can add as library to other fusion web applications. When you do this and you create or open a jsf page then in the component panel your new taskflow are displayed.

Now you see there are two types. Taskflow and Regions, Regions are the taskflows with the page fragments option.
When you drag one of your region taskflows on the jsf page is gives you the option to create a (dynamic) region. You see the page fragment on your page. Jdeveloper adds the following code to the jsf page
<af:region value="#{bindings.page11.regionModel}" id="page11"/>
and this code to the pagedef
<executables>
<taskFlow id="page11"
taskFlowId="/WEB-INF/page1-task-flow-definition.xml#page1"
xmlns="http://xmlns.oracle.com/adf/controller/binding"/>
</executables>
You can also drag your own taskflow to the page. What now happens depends if the jsf page is part of an unbounded taskflow or not. If so then jdeveloper create a button with an action <af:commandButton text="page" action="page1"/> and update the unbounded taskflow. It adds a taskflow call and a control flow case.

<?xml version="1.0" encoding="windows-1252" ?>
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
  <view id="portal">
    <page>/portal.jspx</page>
  </view>
  <task-flow-call id="page1">
    <task-flow-reference>
      <document>/WEB-INF/page-task-flow-definition.xml</document>
      <id>page</id>
    </task-flow-reference>
    <input-parameter>
      <name>param1</name>
      <value>#{'hello'}</value>
    </input-parameter>
  </task-flow-call>
  <control-flow-rule>
    <from-activity-id>portal</from-activity-id>
    <control-flow-case>
      <from-outcome>page1</from-outcome>
      <to-activity-id>page1</to-activity-id>
    </control-flow-case>
  </control-flow-rule>
</adfc-config>

JDeveloper automatically detects the input parameters.
If you don't use the unbounded taskflow (adfc-config.xml) then jdeveloper create a gobutton with a destination. The value is adf.task-flow?_id=page&_document=/WEB-INF/page-task-flow-definition.xml . If you want to add parameters to this url you have to add param1=hello param1 is the parameter of my taskflow. You can also add a return url by adding _return-url. Here an example of the gobutton. <af:goButton text="page" destination="adf.task-flow?_id=page&amp;_document=/WEB-INF/page-task-flow-definition.xml&amp;param1=hello&amp;_return-url=/webcenter_portal-ViewController-context-root/faces/portal2.jspx"/>
That's all

Dynamic jsf page with ShowDetailFrames

The 11g webcenter edition add customizable panels and Show Detail frames to jdeveloper. In this blog I use these frames to add some data to the header and right side of the page (like a homepage). I generate these frames from a backing bean. This ShowDetailFrame component is like a portlet window. You can drag these, re-order these panels or close them. You can use this for example to display some text from the database. This is how it looks.

This is how I did it. First I create a jsf page where I add Panel Stretch Layout then I add a Customizable Panel to the top which has horizontal layout and one on the end which has a vertical layout. In the beforePhase of the view I add the init method which adds the ShowDetailFrames to the Customizable Panels.

<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0"
          xmlns:h="http://java.sun.com/jsf/html"
          xmlns:f="http://java.sun.com/jsf/core"
          xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
          xmlns:cust="http://xmlns.oracle.com/adf/faces/customizable"
          xmlns:pe="http://xmlns.oracle.com/adf/pageeditor">
  <jsp:directive.page contentType="text/html;charset=windows-1252"/>
  <f:view beforePhase="#{PortalBean.initPage}">
    <af:document customizationId="document70">
      <af:form id="form">
        <af:panelStretchLayout inlineStyle="width:642px; height:487px;" topHeight="120px"
                               endWidth="250px">
          <f:facet name="center">
            <af:activeOutputText value="Main Window"/>
          </f:facet>
          <f:facet name="top">
            <cust:panelCustomizable id="panelCustomizableHorizontal"
                                    layout="horizontal"
                                    displayScrollBar="true"/>
          </f:facet>
          <f:facet name="end">
            <cust:panelCustomizable id="panelCustomizableVertical"
                                    layout="vertical" displayScrollBar="true"/>
          </f:facet>
        </af:panelStretchLayout>
      </af:form>
    </af:document>
  </f:view>
</jsp:root>

Now we can create the backing bean

package nl.ordina.backing;

import javax.faces.component.UIComponent;
import javax.faces.context.FacesContext;
import javax.faces.event.PhaseEvent;
import oracle.adf.view.rich.component.customizable.PanelCustomizable;
import oracle.adf.view.rich.component.customizable.ShowDetailFrame;
import oracle.adf.view.rich.component.rich.output.RichOutputText;

public class Portal {
  
    PanelCustomizable  panelHorizontal = (PanelCustomizable) getUIComponent("panelCustomizableHorizontal" );
    PanelCustomizable  panelVertical = (PanelCustomizable) getUIComponent("panelCustomizableVertical" );

    public Portal() {
    }

    public String initPage(PhaseEvent phaseEvent) {
        ShowDetailFrame  window = null;
        
        for ( int i = 1 ; i < 7 ; i++ ) {
            if ( i % 2  == 0 ) {
                window = addWindow ("horizontal_dynamic"+i,panelHorizontal);  
                addText("horizontal is great" ,window);
            } else {
                window = addWindow ("vertical_dynamic"+i,panelVertical); 
                addText("vertical is the best" ,window);
            }
        }   
        return null;
    }
    private void addText (String text,ShowDetailFrame frame) {
        RichOutputText output = new RichOutputText();
        output.setValue(text);
        output.setId("out1"); 
        frame.getChildren().add(output);
    }
  
    private ShowDetailFrame addWindow (String name,PanelCustomizable panel) {
        ShowDetailFrame window = new ShowDetailFrame();
        window.setId(name);
        window.setText(name);
        window.setDisplayShadow(true);
        panel.getChildren().add(window);
        return window;
    }
    
    private UIComponent getUIComponent(String name) {
      FacesContext facesCtx = FacesContext.getCurrentInstance();
      return facesCtx.getViewRoot().findComponent(name) ;
    }
}

Now we only have to add the bean to the adfc-config.xml

  <managed-bean>
    <managed-bean-name>PortalBean</managed-bean-name>
    <managed-bean-class>nl.ordina.backing.Portal</managed-bean-class>
    <managed-bean-scope>request</managed-bean-scope>
  </managed-bean>