SOA Fault Handling

A BPEL fault has a fault name called a Qname (name qualified with a namespace) and a possible messageType. There are two categories of BPEL faults:

• Business faults

• Run-time faults

(1)Business faults: Business faults are application-specific faults that are generated when there is a problem with the information being processed

(2)Run-time faults: Run-time faults are the result of problems within the running of the BPEL process or Web service. Binding fault and remote Fault are the main types of run time faults

 targetNamespace="http://schemas.oracle.com/bpel/extension"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns="http://schemas.xmlsoap.org/wsdl/">

 
  
  
  
 

1. bindingFault : A bindingFault is thrown inside an activity if the preparation of the invocation fails. For example, the WSDL of the process fails to load. A bindingFault is not retryable. This type of fault usually must be fixed by human intervention

2. remoteFault : A remoteFault is also thrown inside an activity. It is thrown because the invocation fails. For example, a SOAP fault is returned by the remote service. A remoteFault can be configured to be retried

For More Information refer to: http://download.oracle.com/docs/cd/E11036_01/integrate.1013/b28981/faults.htm

Changing ORABPEL /ORAESB schema password

Step 1: Change ORABPEL Schema Password: Execute the following steps,

$ sqlplus /nolog

SQL> CONNECT / AS SYSDBA

SQL> ALTER USER orabpel IDENTIFIED BY

E.g. ALTER USER orabpel IDENTIFIED BY welcome1 Step 2: Manually change password in Oracle Internet Directory (OID): Login as (root) orcladmin in Oracle Directory Manager

Navigate to OrclResourceName=ORABPEL,orclReferenceName=SERVICE_NAME,cn=IAS

Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext in the System Objects Frame In the properties frame, input the new password across the orclpasswordattribute and click ‘Apply’ Step 3: Change OC4J JDBC Datasources in OC4J_SOA

Login to Application Server Console as ‘oc4jadmin’ and navigate to OC4J_SOA. Click on Administration Tab -> JDBC Resources

Click on BPELPM_CONNECTION_POOL link. In the credentials, provide this new password after clicking on ‘Use Cleartext Password’ radio button.

Making connections to Oracle lite Database

If you have done a basic installation of SOA Suite 10.1.3.3 or 10.1.3.4 version, it installs a default Olite database with orabpel, oraesb and orawsm schemas. Here is the solution to connect to these schemas through sql/Jdev Using msql, Mobile SQL Client ($ORACLE_HOME\Mobile\Sdk\BIN\msql.exe): Conencting to orabpel schema: >msql system/manager@jdbc:polite:orabpel Conencting to oraesb schema: >msql system/any@jdbc:polite:oraesb Using Jdev Making connections to Orabpel schema: Connection Type: Olite DB User id/ Password: system/ manager Host name: localhost or your SOA server name Port: 1531 Sid: orabpel Making Conenctiosn to Oraesb schema: Connection Type: Olite DB User id/ Password: system/ any Host name: localhost or your SOA server name Port: 1531 Sid: oraesb For ESB schema connection you to select the driver path located at SOA_HOME/Integration/esb/lib/olite40.jar. This has to be added to your class path

Long break..back to Blog again

Back to blogging again after a hectic 2 month busy schedule.

I love this picture, its the picture of Champagne Pool, Waiotapu Thermal Area located in North Island, New Zealand. I have never been there in that place but plan to be there someday.

Loose Control...

Atlast found some time to relax after a hectic schedule over the past week. Still have 2 more days of fun!. Practically i can say i have nothing to do for these 2 days (wait a minute , dont reach conclusion that i am lazy etc..etc..i have things to do but for the moment they can wait for 2 days). ..Loose control, freak out Baby.

Wow! Finally into blogging world

I have been thinking since a long time to start my own blog but never found the right time for it. Atlast today i found some time to do this. Here it is. I made it.