JMS Bridge failed to Start Up

WLS Messaging Bridge failed to start up

A WebLogic messaging bridge is a forwarding mechanism between any two messaging products. Message bridge is use to provide interoperability between separate implementations of WebLogic JMS, or between WebLogic JMS and another messaging product

There was a scenario in which we have to create a bridge but after configuring the message bridge when I check its monitoring tab it was showing following warning message

WARN: failed to look up the source adapter

Bridge was in In Active state.

After checking the documentation I found its a known and very common problem which one face while bridge configuration.

In my case the resolution was bit different. I was creating a Bridge on SOA Cluster and everything seems to be fine with rest of the bridges created for OSB Cluster but same things were not fine in case of SOA.

After a lot of efforts one of my colleague told me to check if everything is fine with my JMS-XA-ADP jar file deployed on my admin server.

When I check that resource deployment I noticed it was missing SOA as a target. After assigning SOA Cluster in a target Bridge start working fine and messages were picked from my queue by that bridge and forwarded to destination queues on another Server. ( which was WLS in my case).

I hope this helps to the readers as well :)

Step by Step Guide to Create Transaction in Oracle BTM

End to End Monitoring is becoming a must have solution for now a days application. As business transaction needs to be monitored in complex scenarios where we're navigating from one systems to another and wants to manage if information is propagated to end systems successfully. 

I will not go into the details here as its very well written on other places on internet.

Here I will explain how to create one simple  BTM Transaction.

Our Test service is simple one.. BTM HelloWorld. it takes one parameter and calls another service BTM Consumer Service on some other location where BTM Observer is not installed.

Now we're going to monitor this using BTM.

First Step is to login to BTM UI and click on Create Transaction link from top left corner of BTM UI as shown in following figure

 Then following screen will come up.

Then we need to select add Operation button as shown highlighted in following  gui

browse the service in our case it is BTM Hello world.

On next tab select the logging options as shown in following screen.

After finishing with the transaction creation control will goes back to main screen which will be showing the transaction detail as following.

Now we will give call to our BTM Hello World Service either from SOAPUI or from em console. And will come back to see if the transaction is logged in BTM.

We can see the transaction details like throughput, completed transactions etc along with the message logs as shown in following screen short.

 Following screen shows the Analysis for our BTM Trans 1

Following screen shows the conditions for our BTM Trans 1

Following screen shows the policies for our BTM Trans 1

Following screen shows the Summary for our BTM Trans 1

 Following screen shows the Instances for our BTM Trans 1

This was the simplest good to start of creating transactions on BTM. But I am still exploring it and will come up with more stuff in future.

Oracle Apps Adapter in SOA 11g vs Apps Adapter in SOA 10 g

Once migrating our integrations from oracle Soa 10 g to 11g we faced issue while calling oracle APIs using Oracle apps adapter. Everything looks fine at OEBS side. Because integration from SOA 10g was still working perfect and when we try to execute migrated interface from SOA 11g fails...

We had checked the JCA settings several times. Responsibility and user were correctly assigned as the same values were working fine for 10g.

After investigating a lot we decided to debug the Apps Adapter jar file deployed on SOA 11g as it's version was different on SOA 10g. We got a solution from there as there were few SQL queries this apps adapter calls before executing the Apis and our user don't had access to query those tables.

In my next post I wi try to share the details of it.

But it's quite strange that this information or clue for such problem was not available or I was not able to find it over the Internet nor at oracle support.

Apps Adapter Fails due to invalid Apps Context

While calling API from Oracle SOA 11g using OracleApps Adapter. BPEL Process which was calling API of OEBS fails and give error that  Invalid Apps Context.

Fault Thrown by SOA Component

2012-11-29T07:54:53.629+01:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-17] [userId: <anonymous>] [ecid: 75f494dcfdf9a2f6:12e9d78e:13b46f8f54b:-8000-00000000000078df,1:23847] [APP: soa-infra] failed to handle message[[
com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'APPS_AP_VENDOR_SITES_PKG_INSERT_NEW' failed due to: Apps Context Error.
Error occurred while setting up Apps Context.
Context parameters should be valid.
Contact oracle support if error is not fixable.
".
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
,detail=<detail>ORA-00942: table or view does not exist
</detail>
,code=<code>EBzA-057</code>}

Solution

 There could be more then one causes of the above problem.

1. User and responsibility in JCA file is not properly defined.

<jca:binding />
<operation name="APPS_AP_VENDOR_SITES_PKG_INSERT_NEW">
<jca:operation
IRepInternalName="PLSQL:AP_VENDOR_SITES_PKG:INSERT_ROW"
SchemaName="SYS_USER"
PackageName="AP_VENDOR_SITES_PKG"
ProcedureName="INSERT_ROW"
InteractionSpec="oracle.tip.adapter.apps.AppsStoredProcedureInteractionSpec"
Username="sysadmin"
Responsibility="System Administrator" >
</jca:operation>

 
2. User mentioned in JCA properties do not have access\correct responsibility assigned in OEBS setup

Following properties should be correctly mentioned in JCA file as well as in OEBS setup.

Username="sysadmin"
Responsibility="System Administrator" 


3. User in jdbc datasource doesn't have enough rights to execute the API.

In my case problem was with the datasource user which was configured in WLS console doen't had enough rights. I provide with super user or apps user to access or execute the Apps Adapter from SOA plateform and my problem was resolved.

I hope this solution helps.