Oracle SOA Enable or Disable endpoint test of web service

Sometimes it is required to disable testing of web service through the browser. This can be achieved by setting "Endpoint Test Enabled " to False from the Enterprise manager.

1.Login to the Enterprise Manager and open the composite.

2.From the context menu of the project navigate to Service/Reference properties and then the service.This will open the properties tab of the composite.

3.Change the "Endpoint Test Enabled " to False.

4.Click Apply. Now you should be getting 403 forbidden error if the web service URL is opened in the browser.

Getting JCA header property while invoking DB Adapter from Spring Bean

We had a requirement of calling a DB Adapter from the spring bean. Also the DB adapter should connect to different databases that had same table structure and the database to connect will be manipulated at the run time. If we are invoking DB adapter from BPEL we could have achieved this by setting the  header property of invoke activity as below.

When we are calling DB adapter from Spring Bean this need to be set in invoke activity of the bean and Oracle SOA Suite provides  predefined spring beans to get the values in the bean.

headerHelperBean  -- For getting and setting header properties
instanceHelperBean --  For getting the information of running instance like id & DN


The following properties need to be injected through the spring context file.

<property name="headerHelper" ref="headerHelperBean"/><property name="instanceHelper" ref="instanceHelperBean"/>

And the value can be set in the spring bean as follows.

headerHelper.setHeaderProperty("jca.db.XADataSourceName",arr[3]);

Unable to login to OAM 11g Console after LDAP Authentication Module Is Changed To Use a New Identity Store

We were unable  login to the OAM console  after changing the identity store used by the LDAP authenication scheme. In our case it was IdentityStore1  and got changed to ADStore. So we had to revert the values in oam-config.xml to login to the console  again.

Weblogic server maintains multiple back ups of the file in the below location.

DOMAIN_HOME/config/fmwconfig/oam-config.xml

We found there was a backup file existing  before the change happened. So by restoring the file and restarting the servers we were able to login to the console.

If you cannot find the any backup of the file in the folder just edit the oam-config.xml and setting the correct ldap id. For example,

 <Setting Name="ldapid" Type="xsd:string">UserIdentityStore</Setting>