11g Fault Policy Java Handler/Where to add custom classes and jars

Im trying to use fault policies in 11g and in fault policies want to catch the remote faults and pass it to a custom java handler.
in Custom Handler use IFaultRecoveryJavaClass and also BPELFaultRecoveryContextImpl , i want to pick fault information
and pass store it in DB...


i placed the client jar file in \user_projects\domains\base_domain\lib





Duuring runtime the server is able to Pick the IFaultRecoveryJavaClass but not BPELFaultRecoveryContextImpl
is there anything im missing ?

*********************************************

*********************************************

To have your custom classes access to the classes in orabpel.jar you have to do the following steps.


1. Go To /soa/soa/modules/oracle.soa.bpel_11.1.1
2. Take a backup of oracle.soa.bpel.jar and Un Jar it.
3. It will have only the MANIFEST.MF which has all the classes needed for BPEL Engine
4. Edit the Class-Path Attribute in the Manifest file to have your custom Jar as Below
Class-Path: ./bpel1-1-xbeans.jar ./orabpel-common.jar ./orabpel.jar ./
bpel_coherence_config.jar ./orabpel-exts.jar ./thirdparty.jar ./bpm-a
nalytics.jar ./orabpel-thirdparty.jar ./wsif-binding.jar ./orabpel-va
lidator.jar ./../../../../../Custom/lib/SoaExtensions.jar (*It should be relative path to the jar file*)
5. Jar it again with only the MANIFEST.MF in it. (Command: jar -cvfm oracle.soa.bpel.jar ./META-INF/MANIFEST.MF)
6. Restarting Managed Server alone will do, But to be Kind enough restart Admin and Managed Servers.

Then your classes are loaded by the same classloader.

************************************************************

Our method of using this fix is to "drop" the custom compiled jar into the same directory and just add the ./$compiledLibraryName.jar to the manifest classpath

************************************************************

As an altenative apporach to the above, a simpler approach can be adopted to save having to unjar / manually edit SOA jar files. A SOA Extension library has been provided in /soa/modules/oracle.soa.ext_11.1.1 to allow for custom jars and classes to be loaded. This is documented in http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10224/bp_java.htm (Section 13.3 - Adding Custom Classes and JAR Files)

To implement this approach:

1) cd to /soa/modules/oracle.soa.ext_11.1.1
2) Copy in your custom fault handler jar file
3) run ant against this directory. This will run the build.xml file located in teh above directory
4) Restart the Server

A "readme" file, within the above directory, provides the instructions that will add the custom jar to manifest of oracle.soa.ext.jar that is picked up the class loader for all user defined custom jars.

********************************************************************

SOA Suite 11g – Using Spring Component to mimic Http Binding and integrate RESTful services

In an earlier post, I showed for the Oracle SOA Suite 11g how we can use the Mediator's Java Callout functionality to integrate RESTful services into our SOA Composite applications, even though we currently have no Http Binding Service nor WSIF support (SOAP Java Binding) at our disposal in the SOA Suite – link to article.  In SOA Suite 11g PS1 – released in November 2009 – is the preview (not yet officially supported and only available for PoC and early trials – of Spring components. This feature provides another way of integrating Java classes into our SOA Composite applications.This article demonstrates how we can use the Spring component to bind our SOA Composite Application to the RESTful Translation service provided by Google.






Note:
In order to use this preview feature in SOA Suite 11g PS1, you must first enable preview mode. Go to $JDeveloper_HOME/integration/seed/soa/configuration and open soa-config.xml. Search for ${SPRING_COMPONENT_NAME_L} and remove the xml comments () around it. After you've saved the file, restart JDeveloper.

Steps for creating the SOA Composite with integrated RESTful Translation Service

1. Create SOA application – with Mediator (Translator)
2. Create Java Interface ITranslator

package nl.amis.soasuite11g.spring;

public interface ITranslator {

  public  String translate(String sourceString, String sourceLanguage, String targetLanguage);
}

3. Create implementation class TranslatorImpl

package nl.amis.soasuite11g.spring;

public class TranslatorImpl implements ITranslator {

  public String translate(String sourceString, String sourceLanguage,
                          String targetLanguage) {
    return extractTranslationFromJSON(translateString(sourceString, sourceLanguage, targetLanguage));
  }

    private static String googleTranslationService =
      "http://ajax.googleapis.com/ajax/services/language/translate";

    private static String extractTranslationFromJSON(String response) {
      final JSONObject jsonObj = (JSONObject)JSONValue.parse(response);
      String translation=null;
      if (jsonObj != null && jsonObj.containsKey("responseData")) {
        final JSONObject responseData = (JSONObject)jsonObj.get("responseData");
        translation=  responseData.get("translatedText").toString();
      }
      return translation;
    }

 private static String translateString(String sourceString,
                                          String sourceLanguage,
                                          String targetLanguage) {
      HttpURLConnection connection = null;
      OutputStreamWriter wr = null;
      BufferedReader rd  = null;
      StringBuilder sb = null;
      String line = null;

      URL serverAddress = null;

      try {
          serverAddress = new URL(googleTranslationService +"?v=1.0&&q="+sourceString.replace(' ', '+')+"&&langpair="+sourceLanguage+"%7C"+targetLanguage);
          //set up out communications stuff
          connection = null;

          //Set up the initial connection
          connection = (HttpURLConnection)serverAddress.openConnection();
          connection.setRequestMethod("GET");

          connection.setDoOutput(true);
          connection.setReadTimeout(10000);

          connection.connect();

          //read the result from the server
          rd  = new BufferedReader(new InputStreamReader(connection.getInputStream()));
          sb = new StringBuilder();

          while ((line = rd.readLine()) != null)
          {
              sb.append(line + '\n');
          }

          return(sb.toString());

      } catch (MalformedURLException e) {
          e.printStackTrace();
      } catch (ProtocolException e) {
          e.printStackTrace();
      } catch (IOException e) {
          e.printStackTrace();
      }
      finally
      {
          //close the connection, set all objects to null
          connection.disconnect();
          rd = null;
          sb = null;
          wr = null;
          connection = null;
      }
      return null;
    }
  }

4. Create Spring Context using the Spring 2.5.6 node under Business Tier in the New Gallery:

Call the Spring Content restful-beans.xml. For example. Or something else.

5. Configure bean translator in the restful-beans.xml Spring context, based on the TranslatorImpl class

<bean  name="translator"
        class="nl.amis.soasuite11g.spring.TranslatorImpl"  />

6. Configure an sca-service translationService in the restful-beans.xml Spring context,based on the bean translator

<sca:service name="translationService" target="translator"
             type="nl.amis.soasuite11g.spring.ITranslator"/>

The Spring Context is immediately added to the composite.xml

8. Create an XSD for the elements used for the request into and response from the Translation Service:

<schema attributeFormDefault="unqualified"
 elementFormDefault="qualified"
 targetNamespace="http://nl.amis/translation"
 xmlns="http://www.w3.org/2001/XMLSchema">
 <element name="translationResult">
  <complexType>
   <sequence>
    <element name="result" type="string"/>
   </sequence>
  </complexType>
 </element>
 <element name="translationSource">
  <complexType>
   <sequence>
    <element name="input" type="string"/>
    <element name="sourceLanguage" type="string"/>
    <element name="targetLanguage" type="string"/>
   </sequence>
  </complexType>
 </element> 

</schema>

9. Create the WSDL for Mediator based on this XSD
Go to the Mediator editor and click on the green plus sign behind the prompt WSDL URL. In the Define Service dialog, click on the generate WSDL icon to create the WSDL based on element definitions in the XSD. Select translationSource for the request message and translationResult for the response.

10. Wire Spring Component restful-beans to Mediator TranslationService in the composite editor:

this causes the Spring Component's WSDL to be generated based on the Java Interface definition.

11. Create transformations between Mediator and Spring Component

12. Expose Mediator Service as Composite level Service
13. Deploy the Composite application to the SOA Suite
14. Test the Translation Service

The response returned:

The Message Flow Trace:

Resources

JDeveloper 11g (11.1.1.2) Application: HttpBindingUsingSpringComponentSOAApp.zip.

The Oracle SOA Suite 11g HttpBinding or another way to call from SOA Composite Applications

I wanted to take a quick look at REST(ful) WebServices and see how those can be integrated into the SCA based SOA Composite Applications that we create with the Oracle SOA Suite. Currently, it does not have the HTTP binding that the 10.1.3 release of the SOA Suite used to have. So what are the alternatives?

In this article, I want to demonstrate a way of calling RESTful (simple http request based) services into a SOA Composite application. I show one way of doing so using the Google Translation Service, a RESTful service described at http://code.google.com/apis/ajaxlanguage/documentation/ and to be accessed at http://ajax.googleapis.com/ajax/services/language/translate?v=1.0&q=hello%20world&langpair=en%7Cit. This service takes a string to translate and an indication of a source and a destination language. Though maybe not formally resource oriented enough to be called REST-style (or RESTful) service by some, it is a service that does not require SOAP or WS* but simply a HTTP Get request. So at least quite restful.

Working with business events troubleshooting

SELECT ENQUEUE_ENABLED, DEQUEUE_ENABLED

 FROM all_queues

WHERE NAME LIKE  ''

Also check the status of the queue from

SELECT ENQUEUE_ENABLED, DEQUEUE_ENABLED

 FROM all_queues

WHERE NAME LIKE  ''

If the values are NO .. then start the queue

--To start the queue

BEGIN

DBMS_AQADM.Start_Queue (queue_name => '');

END;

--To stop the queue

BEGIN

DBMS_AQADM.STOP_QUEUE

         (queue_name => '',

          enqueue    => TRUE,

          dequeue    => TRUE,

          wait       => TRUE);

            END;

Did you check the status of the message in the Queue??

There is a status (STATE) column in the queue, having values 0, 1, 2…

Similarly u can find the view for your queue (view name starts AQ$)… check the status (MSG_STATE) of the message from this view. It will give the exact status of the message (like, is it ready, waiting, etc..)

SELECT *

FROM all_queues

WHERE NAME LIKE  '%ALERT%' --- QNAME

SELECT MSG_STATE ------- CHECK THE VALUE IN THIS COLUMN FOR THE EVENT

    FROM AQ$WF_BPEL_QTAB

Checking available subscription :--

select * from wf_event_subscriptions where event_filter_guid in(
select guid from wf_events where name = 'oracle.apps.wsh.trip.gen.shipconfirmed')
and out_agent_guid in ( select guid from wf_agents where name = 'WF_BPEL_QAGENT');

If there are no subscriptions for the business events or if there are multiple subscriptions in subscription list pointing to the same system, then drop all and recreate the subscriptions.

       The drop and create sql files are automatically created when Oracle Apps adapter is configured.One can find these files in project folder.

Working with business events(Oracle Application Adapters)

Business Events Concepts

Event

A business event is an occurrence in an Internet or intranet application or program that might be significant to other objects in a system or to external agents. For instance, the creation of a purchase order is an example of a business event in a purchasing application.

Event Key

A string that uniquely identifies an instance of an event. Together, the event name, event key, and event data fully communicate what occurred in the event.

Event Message

A standard Workflow structure for communicating business events, defined by the datatype WF_EVENT_T. The event message contains the event data as well as several header properties, including the event name, event key, addressing attributes, and error information.

Event Activity

A business event modeled as an activity so that it can be included in a workflow process.

Event Data

A set of additional details describing an event. The event data can be structured as an XML document. Together, the event name, event key, and event data fully communicate what occurred in the event.

Event Subscription

A registration indicating that a particular event is significant to a system and specifying the processing to perform when the triggering event occurs. Subscription processing can include calling custom code, sending the event message to a workflow process, or sending the event message to an agent.

Deferred Subscription Processing

If you do not want subscriptions for an event to be executed immediately when the event occurs, you can defer the subscriptions. In this way you can return control more quickly to the calling application and let the Event Manager execute any costly subscription processing at a later time.

Agent

An agent is a named point of communication within a system. Communication within and between systems is accomplished by sending a message from one agent to another. A single system can have several different agents representing different communication alternatives. For example, a system may have different agents to support inbound and outbound communication, communication by different protocols, different propagation frequencies, or other alternatives.

Prerequisites to Configure Outbound Business Events

·         The agentListener must be running on WF_Deferred queue.

·         The event should be enabled for BPEL to subscribe to it. The event should not be in the disabled mode.