Tuesday, January 24, 2012

Oracle SOA Suite 11g – Configuration files/Common Artifacts available in MDS

Oracle SOA Suite 11g – Configuration files/Common Artifacts available in MDS:

In Oracle SOA 11g most of the configurations files /common xsd‘s are stored in MDS.

All the configurations files available in MDS are read only; the configurable values can be changed through EM console or WLST script etc.



Some of the important files available in MDS.

adapter-config.xml – Global configurations for Adapters
bpel-config.xml – Configurations for BPEL Engine.
mediator-config.xml –Configurations for mediator.
soa-infra.xml – Configurations for SOA-INFRA.
folders.xml –List of available SOA partitions in the server.
workflow-config.xml, workflow-identity-config.xml and workflow-notification.xml – Configurations related to Human Workflow.
RuntimeFault.wsdl
Ws-addressing.xsd

Oracle SOA Suite Version – 11.1.1.5.0


Thursday, January 19, 2012

Unexpected error in JDeveloper 11g while creating Applications

Unexpected error in JDeveloper 11g while creating Applications

I was receiving the unexpected error as mentioned below while creating new Application or opening the existing Applications in JDeveloper and also none of the existing applications are loading.

SEVERE: Exception while updating observer[0]: [email protected]
java.lang.NullPointerException
at oracle.ide.Ide.getDefaultProject(Ide.java:487)
at oracle.bm.commonIde.ProjectObserver.update(ProjectObserver.java:57)
at oracle.ide.model.IdeSubject.notifyObservers(IdeSubject.java:98)
at oracle.ide.model.Node.notifyObservers(Node.java:786)
at oracle.ide.model.UpdateMessage.firePropertiesChanged(UpdateMessage.java:640)
at oracle.ide.model.ProjectContent$L.projectPropertiesChanged(ProjectContent.java:694)
at oracle.ide.model.Project$StorageListener.structureValuesChanged(Project.java:1097)
at oracle.javatools.data.Structure.fireStructureChangeEvent(Structure.java:455)
at oracle.javatools.data.Structure.firePlaceholderValueAdded(Structure.java:388)
at oracle.javatools.data.Structure.firePlaceholderValueAdded(Structure.java:394)
at oracle.javatools.data.Structure.firePlaceholderValueAdded(Structure.java:394)
at oracle.javatools.data.HashStructure$Impl$3.run(HashStructure.java:1970)
at oracle.javatools.data.HashStructure$Impl.putValueInKeyStruct(HashStructure.java:2021

Also, when I was trying to create new Application the below error was shown in the editor.





Monday, January 9, 2012

Synchronous composite service invocation issue with WS-Addressing enabled by default in Oracle SOA Suite 11g.

Synchronous composite service invocation issue with WS-Addressing enabled by default in Oracle SOA Suite 11g.

Issue: 

When the end system invokes the synchronous (input/output) composite service deployed in Oracle SOA Suite 11g fails to process the response.
The request reaches the SOA system and the response is sent to the end system, but the end system is not able to process the response. The same flow works fine in Oracle SOA Suite 10g without any issue.
After a little struggle we have identified that Oracle SOA Suite 11g by default adds the WS-Addressing details to the response even though the process is synchronous but in 10g the WS-Addressing details are not added by default.
Responses:
10g response without ws-addressing details:-


11g response with ws-addressing details:-




Tuesday, December 20, 2011

Invocation of One way webservice deployed in Oracle SOA Suite from SalesForce.com (SFDC)


Invocation of One way webservice deployed in Oracle SOA Suite from SalesForce.com (SFDC):

Whenever SFDC tries to consume the WSDL which has one-way operation (operation with only input) it fails with the following error –“Can’t find the output in the port type execute_ptt”.



As a solution we can specify a dummy output of type string, so that SFDC is able to consume the WSDL and create the classes related to the elements of the WSDL.



Invocation of webservices deployed in Oracle SOA Suite from SalesForce.com (SFDC)


Invocation of webservices deployed in Oracle SOA Suite from SalesForce.com (SFDC):

Whenever SFDC tries to consume the WSDL which has imports (another XSD or WSDL) it fails with the error - “The import is not recognized



How to Fix

As a solution we have to prepare a linear WSDL (wsdl without imports –coping the contents of the imported XSD/WSDL to the parent WSDL), so that SFDC is able to consume the WSDL and create the classes related to the elements of the WSDL.