Custom Message Throttling and Interface Management – Oracle BPEL

Custom Message Throttling and Interface Management – Oracle BPEL

This post explain the details on Custom Message Throttling and Interface Management – Oracle BPEL/Oracle SOA Suite 11g



Custom Message Throttling and Interface Management.pdf

Approaches to integrate Oracle SOA Suite with SalesForce.com

Approaches to integrate Oracle SOA Suite with SalesForce.com

This post explain the different Approaches to integrate Oracle SOA Suite with SalesForce.com.



Integrate Oracle SOA With SalesForce.pdf

Modifying the Request Headers of a OSB Business Service

Modifying the Request Headers of a OSB Business Service

Sometimes we may required to change the request header values eg. Content-Type and Accept etc for OSB Business Service request dynamically, this post will explain the steps to modify the header values for a Business Service request.

Steps to modify the header values for a Business Service request

Login to sbconsole,Create the session and open the message flow of Proxy Service.

Edit the Route to Business Service and Click on add Request Action

Dynamic endpoint configuration for OSB Business services

Dynamic endpoint configuration for OSB Business services

Sometimes we may required to change the OSB Business service endpoint dynamically.

Steps to change the Business Service endpoints dynamically

The following are the steps to change the Business Service endpoints dynamically.

Login to sbconsole and create the session.

Open the Proxy Service Message Flow.

Click on the RouteTo_BusinessService and click on Edit Route

Test the REST services using Chrome

Test the REST services using Chrome

This post will explain you how to test the REST services using chrome.

Steps to test the REST services using Chrome

Install the REST Console Extension to Chrome.

Open REST Console

Here, i am invoking the REST enabled salesforce login service with OAuth.

Provide the Request URI, Content-Type and Language.
Select the Content-Type of Content Headers as application/x-www-form-urlencoded and provide the request payload.We can also add Authorization, Attachment and Headers to the request.

Creating JCA Adapters with Abstract WSDL - Oracle OSB

Creating JCA Adapters with Abstract WSDL - Oracle OSB

Oracle OSB provides the option to create JCA adapters to connect to different resources through Proxy Services and Business Services.

The JCA adapter needs to be created through JDevelper, JDeveloper creats a Abstract WSDL and a JCA adapter file.

When creating Busines Service through eclipse, eclipse provides the option to generating the service by right clicking the JCA file.

But through OSB console, we will not be able to generate the Business Service with the Abstract WSDL(WSDL Web Service)  because it will not have any binding or service defined.

If we are adding the binding/service to the abstract wsdl and creating the Business servive the following exception will be thrown

Weblogic Managed server status struck in STARTING

Weblogic Managed server status struck in STARTING

We faced the issue while starting the weblogic managed server, the status of the server struck in STARTING.

W could not able to find a valid error messages in the log files

Managed Server Log File:

<30-Oct-2013 11:13:29 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> 

No logs are getting printed after this.

Node Manager Log File:

<30-Oct-2013 11:09:44> <INFO> <SOACoreDomain> <MS1> <Server failed during startup so will not be restarted>

<30-Oct-2013 11:09:44> <WARNING> <Exception while starting server 'MS1'>

java.io.IOException: Server failed to start up. See server output log for more details.

      at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)

      at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)

      at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)

      at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)

      at weblogic.nodemanager.server.Handler.run(Handler.java:71)

      at java.lang.Thread.run(Thread.java:662)

The root cause of this issue is somehow the ldap directory of the server got corrupted.

To resolve this issue:

•  Kill the managed server 
•  Remove the ldap folder from the following location  <<DOMAIN_HOME>>/servers/<<Managed Server>>, this file will be auto generated while restarting the server.
• Restart the server