Wednesday 10 April 2013

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 :)





Tuesday 19 February 2013

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.


Friday 8 February 2013

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.

Wednesday 30 January 2013

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.

Tuesday 13 November 2012

Oracle SOA: DB Adapter Singleton behaviour in High Availabilit...

Oracle SOA: DB Adapter Singleton behaviour in High Availabilit...: There was a problem which one can face in high availability environment (clustered) . We had one Integration between Oracle Ebiz a...

DB Adapter Singleton behaviour in High Availability Environment

There was a problem which one can face in high availability environment (clustered) . 

We had one Integration between Oracle Ebiz and third party system in which we get data from Oracle Ebiz and send them to third party application. This integration was running fine till the time our server environment upgraded for high availability means clustered ones...
We had two clustered which were configured to be synchronous to idealised HA situation. But this causes one design issue in that Integration. 

The issue starts coming in our DB Adapter that now the DB Adapter starting polling Staging table(OEBS)  in parallel with the initialised interval. Cluster1 and Cluster2 starts initiating DB Adapter instances in parallel and if we increase the clusters form 2 to 3. The same way three instances of pooling components started. Which leads to a situation in which if we increase the clusters in future from 2 to 50 then in parallel 50 instances of pooling component will be created in parallel and will hit the third party application in parallel. This could be a problem for a target system if it doesn't supports parallel processing.

The solution to this problem was that we need a concept of singleton pattern in our pooling component / DB Adapter.

There's a property of Inbound endpoint lifecycle support within Adapters called Singleton.
To enable this feature for high availability environment for a given inbound adapter endpoint, one must add the singleton JCA service binding property in the composite.xml within the <binding.jca> element and set it to a value of true as shows.


Singleton Property in composite.xml

    <binding.jca config="bindin_file.jca">
        <property name="singleton">true</property>
    </binding.jca> 
 
This was our finding to the problem we faced in clustered environment.

I hope this helps others as well.

 
 

Wednesday 18 July 2012

AIA Artifacts reference problem in JDeveloper using oramds

After finishing up with AIA 3.0 Installation when I starts building my component in JDeveloper on compilation I got errors which were pointing to my bpelprocess.wsdl and from there I come to know that one import is not proper which is actually pointing to AIA Artifact.

<wsdl:import namespace="http://schemas.oracle.com/bpel/extension"
              location="oramds/apps/AIAMetaData/AIAComponents/UtilityArtifacts/RuntimeFault.wsdl"/>

Solution

1.Check if the connection to MDS repositery is Created and if not then create a database connection to connect to the repository with either DEV_MDS or equivalent user.

2. Check if you have already created SOA-MDS connection (from resource palette) If not then create a new SOA-MDS connection. Make sure it uses the DB connection in step1 and also the partition is soa_infra. as by default its not soa_infra.

3. Now check for successful connection and installation of AIA Components by browsing AIAComponent files from MDS. These will be shown under /Apps/MetaData.

4. The last and very important step is to update adf-config.xml file in application home of your Jdeveloper(directory where .jws file exists). This will be used at design time to access files from MDS using oramds protocol. This is located in directory named %APPLICATION_HOME%/.adf/META-INF.
    
Add following line in adf-config.xml

      <metadata-namespaces>
          <namespace metadata-store-usage="mstore-usage_3" path="/apps" />
      </metadata-namespaces>

     <metadata-store-usage id="mstore-usage_3">
        <metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
         <property value="DEV_MDS" name="jdbc-userid" />
         <property value="welcome1" name="jdbc-password" />
         <property value="jdbc:oracle:thin:@hostname:port:sid" name="jdbc-url" />
         <property value="soa-infra" name="partition-name" />
     </metadata-store>
     </metadata-store-usage>

After updating file now you can recompile and this time you will surely end up with no errors.
You can now start accessing the artifacts like WSDLs, XSDs etc using oramds. 
eg:oramds/apps/AIAMetaData/AIAComponents/UtilityArtifacts/RuntimeFault.wsdl

Friday 8 June 2012

Error Starting Weblogic Admin Server: Could not reserve enough spacefor object heap

Error

"Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine. "


Reason for this error is when we make changes memory variable and assign more memory and we don't have enough memory available... server startup is failed with this error.

Solution

You can remove this error while decreasing heap size in setSOADomainEnvt.cmd

%ORACLE_HOME%\user_projects\domains\DOMAIN\BIN\setSOADomainEnvt.cmd

set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
set PORT_MEM_ARGS=-Xms768m -Xmx1536m
set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=128m -XX:MaxPermSize=512m
set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m

Tuesday 29 May 2012

Step by Step Installation Guide for SOA 11g

Download all the software to get started.

  1. Oracle Database OracleXEUniv.exe
  2. WebLogic Server  wls1035_oepe111172_win32.exe
  3. Repository Creation Utility  ofm_rcu_win_11.1.1.5.0_disk1_1of1.zip
  4. SOA Suite  ofm_soa_generic_11.1.1.5.0_disk1_1of2.zip, ofm_soa_generic_11.1.1.5.0_disk1_2of2.zip
  5. OSB  ofm_osb_generic_11.1.1.5.0_disk1_1of1.zip

Oracle Database Setup


This is the first step towards Installation of SOA Suite.

For this you need to have anyone of following versions but I will be using Oracle XE Universal database version 10.2.0.1 as it is already installed on my machine  
                   i. Oracle XE Universal database version 10.2.0.1
                  ii. Oracle 10g database version 10.2.0.4+
                 iii. Oracle 11g database version 11.1.0.7+  


Note: You can not use any other database version in 11gR1 (certification of additional database is on the road map). Specifically, you cannot use XE Standard, It must be Universal.  


Note: When you are using XE, you will see a warning when you install the database schema that this database version is too old. You can safely Ignore this warning as it applies only to production environments.

Once you are done with Installation of Oracle XE, you must update database parameters.
Set the processes parameter to >=500 using the following instructions.
Login to sqlplus with sysdba and run following commands

sqlplus connect sys as sysdba
SQL> show parameter session
SQL> show parameter processes
SQL> alter system reset sessions scope=spfile sid='*';
SQL> alter system set processes=500 scope=spfile;
SQL> shutdown immediate
SQL> startup
SQL> show parameter session


SQL> show parameter processes

Schema Configuration 

Note: If you want to use Oracle XE as your database, you need to set the RCU_JDBC_TRIM_BLOCKS environment variable to TRUE *prior* to running RCU

1. To create the new schema, unzip ofm_rcu_win_11.1.1.5.0_disk1_1of1.zip navigate to rcuHome\bin and open a command window and run rcu.bat

2. The bat command returns to the prompt immediately and, after a few seconds, the Repository Creation Utility opens (if you just ran the utility to drop the schema, it opens the second time much more quickly).

3. On the Welcome screen, click on Next..
4. Select Create and click on Next.
5. Enter the database information.
6. Click on Next.
7. If you are using XE, you will see a warning at this point that this version is too old. You can safely ignore this warning as it applies only to production environments.

Monday 14 May 2012

Root cause of ServletException java.lang.AssertionError: CurrencyKey not preserved


After finishing up with the installation of AIA on SOA 11g when I access AIA home I was disappointed to see empty tabs of AIA including Project Life Cycle, CAVA, ect. When I check server log file I found following big error log.. which says....

Referer: http://localhost:7001/AIA/faces/oracle/apps/aia/home/ui/page/Home.jspx?_afrWindowMode=0&_afrLoop=8046694499161&_adf.ctrl-state=1b2migk5rh_9
Cookie: JSESSIONID=82k3PwvbRfLGCv3hGL5rK2sHQPJlzsWyBSmylvLLRptRhcmjS1T2!273321565; ADMINCONSOLESESSION=LMKjPwnCf10njbLYhNKwbPFGHX7cW2L94zgT7TC1jyYhJrJpyMyM!273321565
Content-Type: application/x-www-form-urlencoded
Content-Length: 263

]] Root cause of ServletException.
java.lang.AssertionError: CurrencyKey not preserved
    at org.apache.myfaces.trinidad.component.UIXCollection.encodeEnd(UIXCollection.java:540)
    at javax.faces.component.UIComponent.encodeAll(UIComponent.java:937)
    at org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:399)
    at oracle.adf.view.rich.render.RichRenderer.encodeChild(RichRenderer.java:2633)
    at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer.encodeCenterFacet(PanelStretchLayoutRenderer.java:769)
    at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer._encodeCenterPane(PanelStretchLayoutRenderer.java:1140)
    at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer._encodeMiddlePanes(PanelStretchLayoutRenderer.java:348)
    at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer.encodeAll(PanelStretchLayoutRenderer.java:313)
    at oracle.adf.view.rich.render.RichRenderer.encodeAll(RichRenderer.java:1396)
    at org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:335)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:767)
    at javax.faces.component.UIComponent.encodeAll(UIComponent.java:937)
    at org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:399)
    at oracle.adf.view.rich.render.RichRenderer.encodeChild(RichRenderer.java:2633)
    at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer.encodeTopFacet(PanelStretchLayoutRenderer.java:781)

Solution
For this we need to update your Environment file which is available at following location
  
  <MiddlwareHome>/user_projects/domains/<Domainname>/bin/setSOADomainEnv.cmd  
                                                               OR
<MiddlwareHome>/user_projects/domains/<Domainname>/bin/setSOADomainEnv.sh 



set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -da:org.apache.myfaces.trinidad.component.UIXCollection
 
and restart the server... 
Now tabs will be successfully visible with no error

Sunday 13 May 2012

Node Manager not reachable for machine "Local Machine", please ensure node manager service is running and port 5556

 While running Installer for Oracle AIA on local machine I faced following error
"Node Manager not reachable for machine "Local Machine", please ensure node manager service is running and port 5556". Because I forget to start Node manager ....




Solution

To start the nodemanager, you need to browse to MiddlewareHOME\wlserver_10.3\server\bin and execute "startNodeManager.cmd".

"nodemanager.properties" will get created under "MiddlewareHOME\wlserver_10.3\common\nodemanager\" once you start the nodemanager as shown in following GUI dump




You can also check the status of nodemanager from weblogic console.
  1. Login to weblogic console.
  2. Browse to Environment -> Machines in the Domain Structure panel (located left side)
  3. Click on "LocalMachine".
  4. Click on "Monitoring" tab to know the status of nodemanager.

Wednesday 9 May 2012

MDS-01330: unable to load MDS configuration document

After successful installation  of SOA(11g) 11.1.1.5 on Oracle XE when I started the managed server I faced following exception which makes me worried.... and kept on thinking for few minutes ....do I need to reinstall everything but thanks God I got a solution.
I hope this helps to all who faced such an issue.

Exception
oracle.mds.lcm.exception.MDSLCMException: MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "soa-infra-store" is invalid.
ORA-04063: package body "DEV_MDS.MDS_INTERNAL_SHREDDED" has errors
ORA-06508: PL/SQL: could not find program unit being called: "DEV_MDS.MDS_INTERNAL_SHREDDED"
ORA-06512: at line 1.....



Solution   

  1. First  of all drop SOA Suite schemas and associated tablespaces using RUC. 
  2. Then go to command line (cmd) and set environment variable RCU_JDBC_TRIM_BLOCKS=TRUE
  3. Run RCU again to re-create the SOA Suite schemas and tablespace

Now restart  server and this time there will be no error associated with "MDS-01330: unable to load MDS configuration document"