ESB SOAP service endpoint properties cacheConnections

Hi all,
Has any body used cacheConnections, end point property.? how does it effect ESB SOAP service response.

Similar Messages

SOAP Service Endpoint properties configuration

hi
i have an ESB SOAP service, invoking a web service which is working fine.but i need to do the same process using Location variable in endpoint properties and also can anyone explain me how to configure Location(URL Format and delimiters), Retrycount and RetryInterval of endpoint prop. can i use the endpoint to redirect my request from one URL location to another baserd on retryinterval.
thanks in advance
Thirumal

hi
iam getting the following error when i set a service url for Location variable in SOAP Service endpoint property.
oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: exception during SOAP invoke: Caught exception while handling request: unrecognized operation: {http://serviceone1/types/}getDecodedStringElement; nested exception is: javax.xml.rpc.soap.SOAPFaultException: Caught exception while handling request: unrecognized operation: {http://serviceone1/types/}getDecodedStringElement at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.populateFaultMessage(WSIFOperation_JaxRpc.java:2978) at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1714) at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1463) at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.executeRequestResponseOperation(WSIFOperation_JaxRpc.java:1185) at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:507) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:430) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:447) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:184) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:112) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:106) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:85) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1416) at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:105) at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:273) at oracle.tip.esb.s

Unable to change ESB Soap Service endpoint

Hi people , i have a problem,
after creating a soap service , register de esb service on DefaultSystem, i want to call externally using
"http://host:port/esb/wsil/DefaultSystem/<name of soap service>?wsdl
everithing works ok , but when i try to change from Jdeveloper the enpoint URL , ESB seems to keep using the old URL in :
http://host:port/event/DefaultSystem/<name of soap service>?WSDL ..
If i check on esb control i can se the new "WSDL URL" on the Definition tab of this soap service. But internally in the WSDL generated by the ESB endpoint it keeps using the OLD URL
causing obviously a:
"SOAPException: Message send failed: Connection refused"
if i make that resource unavailable after the change
The question is .. why i cant change the endpoint url ????
theres is any WSDL cache or something like in Oracle BPEL PM ??
i need to restart (i dont try yet )
please ill wait for any suggestions
PS: im using ESB 10.1.3.3.0 Build:PCBPEL_10.1.3.3.0_GENERIC_070615.0525

Hi
I have similar problems and nobody seems to know the solution. Changing the virtual host and port in ESB console does not resolve the problem thoroughly. It's changing the end point entry but living the namespace URL of the WSDL with old value, for instance my address was: http://localhost.localdomain:8889/ .....servicename?WSDL.
This prevents it from proper invoking by external clients, you can reach the end point and use the test page but you can't read its wsdl file without adjusting its address by hand.
I found one solution, it's reinstalling the OAS from scratch and pass the proper name of the server when prompted but what the kind of solution is that? This is obviously deployment problem, the original wsdl file prepared in JDeveloper is used to generate the final wsdl file exposed to external clients but which is the configuration file responsible for that and why the esb console don't change the namespace url too while changing end point?
This is the bug indeed because it's impossible to resolve from console level.

ESB SOAP Service invoke

Hi,
I would like to know how to invoke a ESB SOAP service from an external web service, which in turn need to interact with the Routing Service ?
Thanks,
OracleExpert

I'm getting the feeling that you're mixing some things up and that you're comparing things that can't be compared.
In ESB you create integration patterns with adapters, routing services and so on. When you deploy your integration pattern you'll end up with several webservices. E.g. a ESB integration pattern IS a webservice and all the components within a integration pattern are webservices as well.
If you want to start / call this ESB pattern you can do it in several ways. Its a webservice so calling it is standarized. You can call the webservice from BPEL, from another ESB project, from a Java app, from PL/SQL and even from cobol!
whether you get a reply from your integration pattern is the matter of how you implement your integration pattern ( synchronous vs asynchronous etc ).
If you want to test this e.g. want examples please take a look at the examples provided by Oracle on OTN. These samples can then be called / tested externaly by e.g. using a free program called SOAPUI.
HTH.
Martin

Invoke remote SOAP Servlet using ESB SOAP Service component

Hello
I am new to ESB and JDeveloper as well, have been working with Eclipse since now. I have the following problem I can not solve at this time.
I have a SOAP Servlet running on Apache Tomcat 5, which I can call from simple JAVA code using the URL http://localhost:8080/omar/registry/soap
The servlet is defined/described within Tomcat using the web.xml file like:
<servlet>
<servlet-name>
ebxmlrr-soap-receiver-servlet
</servlet-name>
<servlet-class>
org.freebxml.omar.server.interfaces.soap.RegistrySOAPServlet
</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
I have already made a web service, which I have deployed on Oracle Application Server (using the SOA suite). In the web service I have wrapped a simple JAVA class which uses the SOAPConnection class to connect to http://localhost:8080/omar/registry/soap and sends a simple SOAP message successfully.
My question is, can I use the http://localhost:8080/omar/registry/soap URL directly from an ESB SOAP Service to send messages to the SOAP Servlet (not to use the web service in Oracle Application Server, but to connect directly to the SOAP Servlet on Tomcat) ?
Regards
Zolt

I have found a WSDL file provided to test the SOAP service I have mentioned before.
The content of the WSDL looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://omarebxmlrrwsdlnew/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" name="StandaloneTestService" targetNamespace="http://omarebxmlrrwsdlnew/">
     <types/>
     <message name="StandaloneTest_sendMessage">
          <part name="Message" type="xsd:string"/>
     </message>
     <message name="StandaloneTest_sendResponse">
          <part name="Response" type="xsd:string"/>
     </message>
     <portType name="StandaloneTestPortType">
          <operation name="sendMessage" parameterOrder="Message">
               <input message="tns:StandaloneTest_sendMessage"/>
               <output message="tns:StandaloneTest_sendResponse"/>
          </operation>
     </portType>
     <binding name="StandaloneTestBinding" type="tns:StandaloneTestPortType">
          <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="sendMessage">
               <soap:operation/>
               <input>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://omarebxmlrrwsdlnew/"/>
               </input>
               <output>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://omarebxmlrrwsdlnew/"/>
               </output>
          </operation>
     </binding>
     <service name="StandaloneTestService">
          <port name="StandaloneTestPort" binding="tns:StandaloneTestBinding">
               <soap:address location="http://localhost:8080/omar/registry/soap"/>
          </port>
     </service>
</definitions>
Where the address specifies the address of the SOAP service
When I try to use this WSDL inside an ESB SOAP Service I get the following error:
The selected porttype is using a message that is invalid for ESB because it is multi-part or has a simple type.
The message StandaloneTest_sendMessage in operation sendMessage of porttype StandaloneTestPortType is invalid.
Please select another porttype or fix the wsdl.
How can I get pass by this error, what is wrong with the WSDL file ?

ESB SOAP Service Error - Mutiple levels of SOAP invocation.

Hi,
Does anyone have a solution to this problem,
We are on SOA 10.1.3.1.
I am trying to design hierarchial invocation of services, where one ESB service calling another ESB service and so on...
Example There are 3 ESB Projects A, B and C. Project A calls B; B calls C.
A -> B -> C
In project B, I added SOAP service to directly reference/invoke service C which is already deployed. On execution, service B is successfully able to call service C. No issues.
I did similar execise, In project A, I added SOAP service to directly invoke service B (which is internally calling service C). Deployment is successfully. On execution from service A, I am getting following error.
Does anyone have a solution to this problem ?
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>env:Server</faultcode><faultstring>oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "java.util.NoSuchElementException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:790)
at java.util.HashMap$ValueIterator.next(HashMap.java:817)
at oracle.tip.esb.server.common.wsif.WSIFInvokerResponse.getFirstFaultElement(Unknown Source)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.handleFault(Unknown Source)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(Unknown Source)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source)
at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source)
at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.util.NoSuchElementException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:790)
at java.util.HashMap$ValueIterator.next(HashMap.java:817)
at oracle.tip.esb.server.common.wsif.WSIFInvokerResponse.getFirstFaultElement(Unknown Source)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.handleFault(Unknown Source)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(Unknown Source)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
... 20 more
</faultstring><faultactor></faultactor></env:Fault></env:Body></env:Envelope>

Your usecase should be no problem. The error java.util.NoSuchElementException seems to indicate you are refering a non existing element somewhere. Are you sure the service gets invoked with the correct message content? From the enterprise manager website you can increase the logging of esb. Go to your esb oc4j container, administration, Logger Configuration. Search for soap loggers and increase the log level. You should now see the entire xml soap messages in the log.xml file.
Kind Regards,
Andre Jochems

ESB Soap Service invoking mutiple operations of a WSDL

Hi,
we have a requirement where in we have to call mutiple opeartions of a WSDL.
We tried developing this using ESB, where in we used many soap services invoking different operations of thw WSDL and a routing service which will decide on which SOAP service (Opeartion of WSDL) to invoke.
But we just want to check if there any way that we can call many operations of the same WSDL using the same soap service.
Any pointers on this.
Thanks in advance.
santu

Your usecase should be no problem. The error java.util.NoSuchElementException seems to indicate you are refering a non existing element somewhere. Are you sure the service gets invoked with the correct message content? From the enterprise manager website you can increase the logging of esb. Go to your esb oc4j container, administration, Logger Configuration. Search for soap loggers and increase the log level. You should now see the entire xml soap messages in the log.xml file.
Kind Regards,
Andre Jochems

ESB -- SOAP Service Security

I have a SOAP Web Service secured with a Basic Authentication.
I've wrapped this SOAP service with an ESB service.
Should I be able to pass the Basic Authentication credentials through the ESB service to the underlying SOAP service? I see "support for SOAP Headers" is the docs as a preview feature.

Take a look at the following thread regarding SOAP headers:
Re: Custom SOAPAction for Oracle ESB?
Or did you manage to get through this use case because I'm trying to create a generic 'authenticationService' which receives a username/password and needs to check against an ldap environment if this user exists

Help with ESB as external SOAP service proxy

We are trying to leverage ESB in the first steps of implementing an SOA solution for our organization.
We have an external SOAP service that we would like to register with Oracle ESB. In turn, are internal programs
would then call the service through the ESB using a SOAP interface. This allows us to hide the external
SOAP service definition from our internal programs, allowing us to modify the external SOAP service or add extra routing
where necessary without affecting the calling client.
CLIENT -> (SOAP) ESB -> (SOAP) EXTERNAL SERVICE
Is this the correct use of ESB?
We are having a couple of issues when trying to use the WSDL ESB creates within our client code. One being Oracle APEX.
We can create forms against the external soap service WSDL, but when we try to hit the WSDL ESB creates, it gives back
"The WSDL document could not be understood by the rendering engine. Click Create Web Service Reference Manually to continue creating a reference for this service."
Any ideas?

I was able to get the virtual service running through EM by changing the <hostname>
http://<hostname>:8888/event/CustomerData/IdentitySOAPService
Would the url on the test page be the wsdl url we would hand out to the clients? I am curious as to what the context /event/ is?
Also, if I were doing straight service virtualization, would it be correct to just create a SOAP service hitting the external service? Or is it better to have a routing service exposed to the client?
Client -> ESB [ (Routing Service) -> (Soap Service) ] -> External Service
or
Client -> ESB [ (Soap Service) ] -> External Service

Soap Service RetryInterval in ESB

Hi,
Can you tell me whether the endpoint properties RetryInterval and RetryCount work on Soap Services also. I have a Siebel Web Service (synchronous) registered with the ESB.
I want to be able to retry 5 times at an interval of 5 seconds in case Siebel is down.
What are the steps that I need to take? The process needs to be automated.
Kindly advice. Also, kindly explain what exactly is retried by specifying this interval? Does this retry occur in case of all exceptions?

I tried applying the patch, but it gives the following error:
OPatch detects your platform as 207 while this patch 6133448 supports platforms:
0 (Generic Platform)
This patch is not suitable for this operating system.
Please contact support for the correct patch.
ERROR: OPatch failed during pre-reqs check.
OPatch returns with error code = 150
I downloaded for the OS I am on, but always the generic patch downloads; i guess this generic one should work for all platforms. Opatch version is 1.0.0.0.56.

Deployment of ESB for 10.1.3.4 (trying to amend Endpoint properties)

I have downloaded the new deployment code (esbdeploymentautomation) to enable you to deploy an ESB between environments.
I am deplying an ESB process from Dev to Systest.
I have amended the build_tst.properties file to include all the relevant info and the build.properties.
At the bottom of this file I have added
# Values required for replace tasks.
code_dir=C:\Project\Client\jdev\jdev\mywork\dii\esbInt110Flow
search_text=/u01/esb/out/XX/int110_01
replace_text=/u01/esb/XX/INT110/out
These lines are trying to change the Endpoint property of a FileAdapter where the directories are different in the new environment.
I run extract.sh and it successfully creates a deploymentPlan_tst.xml. Great!!
I can then successfully run the deploy.sh and it deploys my ESB into the new environment but it doesn't change the Endpoint property.
When you look at the log files generated it doesn't even appear to try and run the replaceToken process.
Any ideas if this replaceTokens actually works?
When the extract.sh is run it also generates logging which seems to suggest the replaceTokens runs after the DeployESBSuitcase:
*Build sequence for target(s) `ExtractESBDeploymentPlan' is [ExtractESBDeploymentPlan]*
*Complete build sequence is [ExtractESBDeploymentPlan, DeployESBSuitcase, replaceTokens, usage, UndeployESBEntities, ]*
But from what I can see when you finally run the deploy.sh it only runs the DeployESBSuitcase process and nothing else.
The only reason for using this automaytion process is so that we can amend Endpoint properties and URLs as we deploy but this is the part that doesn't seem to work....
Help!!
Regards
Stuart

You need to run the replaceToken before the deployESBSuitecase.
Here is my example, it does a find and replace on host name
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<project name="ESBDeploymentProject" default="usage">

<property environment="env"/>
<property name="esbProjectToDeploy" value="${basedir}/deployment"/>
<property name="deploymentPlanFilename" value="${esbProjectToDeploy}/deploymentPlan.xml"/>
<property name="ImportFilename" value="${env.ORACLE_HOME}/Deployment/deploy/lib/ESBMetadataMigrationTaskdefs.xml"/>

<echo>Property Files ${env.ORACLE_HOME}/Deployment/deploy/resources/esb.${env.paramtarget}.properties</echo>
<property file="${env.ORACLE_HOME}/Deployment/deploy/resources/esb.${env.paramtarget}.properties" />
<property name="targetDeploymentPlanFilename" value="${esbProjectToDeploy}/${esb.deployTargetPlan}"/>
<target name="param-target-chk" unless="env.paramtarget">
<fail message="Target deployment environment parameter not set" />
</target>

<echo>Import ${ImportFilename}</echo>
<import file="${ImportFilename}"/>

<target name="DeployESBProject" depends="param-target-chk">
<deployESBProjects
esbMetadataServerHostname="${soa.suite.hostname}"
esbMetadataServerPort="${soa.suite.port}"
userName="${soa.suite.admin.username}"
password="${env.soapassword}">
<esbProject directory="${basedir}"/>
</deployESBProjects>
</target>

<target name="UndeployESBEntities" depends="param-target-chk">
<undeployESBEntities
esbMetadataServerHostname="${soa.suite.hostname}"
esbMetadataServerPort="${soa.suite.port}"
userName="${soa.suite.admin.username}"
password="${env.soapassword}">
<system guid="ED8243D1B9A211DCAF33D38D99DD8682"/>
<service guid="63085310B9A311DCAF33D38D99DD8682"/>
</undeployESBEntities>
</target>

<target name="ExtractESBDeploymentPlan">
<mkdir dir="${esbProjectToDeploy}"/>
<delete file="${deploymentPlanFilename}" verbose="true"/>
<extractESBDeploymentPlan
sourceDir="${basedir}"
deploymentPlanFile="${deploymentPlanFilename}"/>
</target>
<target name="ModifyESBDeploymentPlan" depends="param-target-chk">

<copy file="${deploymentPlanFilename}" tofile="${targetDeploymentPlanFilename}"/>
<replaceregexp file="${targetDeploymentPlanFilename}"
match="http://[^/]*/"
replace="http://${soa.suite.hostname}:${soa.suite.port}/"
byline="true" />
</target>
<target name="DeployESBSuitcase"
depends="param-target-chk, ExtractESBDeploymentPlan, ModifyESBDeploymentPlan">
<deployESBSuitcase
esbMetadataServerHostname="${soa.suite.hostname}"
esbMetadataServerPort="${soa.suite.port}"
sourceDirectory="${basedir}"
deploymentPlanFilename="${targetDeploymentPlanFilename}"
forcedDeployment="true"/>
</target>

<target name="usage">
<echo>
======== Environment =====================================================
SOA_DA_HOME = ${env.SOA_DA_HOME}
CLASSPATH = ${env.CLASSPATH}
ANT_HOME = ${env.ANT_HOME}
ENVIRONMENT = ${env.paramtarget}
======== Properties =====================================================
basedir = ${basedir}
SOA Suite server = ${soa.suite.hostname}:${soa.suite.port}
OC4J instance = ${soa.suite.oc4j.instancename}
==============================================================================
</echo>
<exec executable="ant" dir="${basedir}" vmlauncher="false">
<arg value="-projecthelp"/>
</exec>
</target>
</project>
cheers
James

ESB Endpoint Properties

I noticed in ESB you can now setup Endpoint Properties. I'm interested in using them for error handling, specifically rejectedMessageHandlers. I found some documentation on using that as a property, but can't seem to get it to work. I've tried setting up the property to use file, AQ, and BPEL, none of which seemed to work, I followed the documentation and a post on this forum. Has anyone gotten this to work properly? Is there somewhere in the app server log that I could see the output of endpoint properties? I'm kind of stuck.
Thanks for any direction.

I am on 10.1.3.3
I am seeing the following exception in $J2EE_HOME/log/oc*/oc*/log.xml file
<MSG_TEXT>JCA: Rejection handler failed
Error while trying to hand off bad message to Rejection handler bpel://default:D0978108040F48D060880D888301C27EDDC048307AFA162A|JCARejectionHandler|han
dleRejection|message due to: java.lang.Exception: Failed to create "ejb/collaxa/system/DeliveryBean" bean; exception reported is: "javax.naming.NameNot
FoundException: ejb/collaxa/system/DeliveryBean not found
at com.evermind.server.rmi.RMIServerContext.lookup(RMIServerContext.java:207)
at com.evermind.server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:257)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:197)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.oracle.bpel.client.util.BeanRegistry.lookupDeliveryBean(BeanRegistry.java:279)
at com.oracle.bpel.client.delivery.DeliveryService.getDeliveryBean(DeliveryService.java:250)
at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:174)
at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:149)
at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.invokeBpelProcess(AdapterFrameworkListenerBase.java:1209)
at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.invokeBpelProcess(AdapterFrameworkListenerBase.java:1247)
at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.invokeBpelProcess(AdapterFrameworkListenerBase.java:1266)
at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.handleUndeliverableRequestMessage(AdapterFrameworkListenerBase.java:1522)
at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.sendRejectedMessageToExceptionHandler(AdapterFrameworkListenerBase.java:1394)
at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onReject(ESBListenerImpl.java:536)
at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onReject(ESBListenerImpl.java:633)
at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onReject(MessageEndpointImpl.java:361)
at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.handleRejections(AQActivationSpecDequeuer.java:110)
at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.doRaise(AQActivationSpecDequeuer.java:409)
at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.raiseInboundInteraction(AQActivationSpecDequeuer.java:314)
at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.raise(AQActivationSpecDequeuer.java:246)
at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:225)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
Where are the Marc Kelderman instr?
Regards,
Rajesh

Add username token to SOAP Service in ESB

I know how to add the username token to a partnerlink in a bpel process but how can I configure the same soap headers in a SOAP Service in ESB?
Another question about the configuration of a bpel process when invoking a secure web service: I need to add 3 parameters to the partnerlink to be able to send the username/password credentials to the service but this isn't very flexible.
How can you configure to use file authentication or ldap authentication when invoking the secure web service?

Hi.
I found some info related to passing username token in ESB.
You go to ESB home page:
http://www.oracle.com/technology/products/integration/esb/index.html
and download esb samples:
http://www.oracle.com/technology/products/integration/esb/files/esbsamples.zip
There you'll find a SOAP Headers project (under OTN Samples) which has an example of how to pass WS-Security usename credentials.
Here is a sample, in a XSLT:
<xsl:variable name="setUsername"
select="ehdr:setOutboundHeader('/wsse1:Security/wsse1:UsernameToken/wsse1:Username','oc4jadmin','wsse1=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;')"/>
<xsl:variable name="setPassword"
select="ehdr:setOutboundHeader('/wsse1:Security/wsse1:UsernameToken/wsse1:Password','welcome1','wsse1=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;')"/>
<xsl:template match="/">
<ns1:ReceiveCustElement>
<ns1:customer>
<xsl:value-of select="/inp1:InputElement/InputString"/>
</ns1:customer>
</ns1:ReceiveCustElement>
</xsl:template>
</xsl:stylesheet>
Denis

How to generate a Web Service Proxy for an ESB Routing Service?

Hi,
I have a SOAP service behind an ESB Routing Service. I am aware that i can call this ESB Service at the SOAP endpoint which can be found at the ESB Console after registration.
But, i want to invoke this service using a Web Service Proxy. My understanding is that, i need to use the WSDL generated for the ESB Routing Service to generate the proxy. The WSDL which can be seen in JDeveloper does not have any soap bindings and hence the tool does not allow me to generate any proxy.
Also, the two WSDLs whose URLs can be found at the ESB Console do not have the soap endpoint properties.
Can someone help me out on the same?
Thanks and regards,
Priya.

Priya,
Just take the SOAP endpoint and suffix it with a ?wsdl
Even the Concrete WSDL endpoint should be having a SOAP endpoint.
HTH
Uday

ESB Routing Service Byte Order Mark error

Hi,
I have a esb routing service to accept soap messages from an external system. The external system sents messages with a Byte Order Mark for UTF8 at the start. If i look at the tcp messages i see the following:
POST /event/DefaultSystem/CaseVerhuizing/EsbStuf0204Service HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
Protocol 2.0.50727.42)
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://www.egem.nl/StUF"
Host: ux920:7777
Content-Length: 2382
Expect: 100-continue
Connection: Keep-Alive
HTTP/1.1 100 Continue
...<?xml version="1.0" encoding="utf-8"?><soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
The three dots signify the hexadecimal value EF BB BF which is for UTF8. This raises an error however in iAS:
HTTP/1.1 400 Bad Request
Date: Mon, 16 Jul 2007 14:41:32 GMT
Server: Oracle-Application-Server-10g/10.1.3.1.0 Oracle-HTTP-Server
Content-Length: 158
Connection: close
Content-Type: text/html; charset=ISO-8859-1
Bad Request
Error parsing envelope: (1, 1) Start of root element
expected
It seems the esb routing service is trying to parse the Byte Order Mark as xml and therfore can not find the soap envelope tag? Any help is appreciated!
Kind Regards,
Andre Jochems
Message was edited by:
ajochems

Hi Andre,
We got exactly the same error as you did. Your analysis is also correct; the first 3 bytes of the reply are not interpreted by BPEL/ESB as a BOM, but as 'real' characters.
The problem is due to the fact that the UTF-8 BOM is actually optional in the specifications, and obligatory for UTF-16. The UTF-8 BOM practically has no meaning, and is never used in most SOA applications. However the guys that made the webservice you need to consume are (wrongly) convinced that the UTF-8 BOM is supposed to be there according to the OASIS/W3C specs. Which is not true btw...
For more info on BOMs, check: http://en.wikipedia.org/wiki/Byte_Order_Mark
Unfortunately I don't have the code for our 'proxy' service anymore. I remember that we simply made a little servlet, that uses input- and outputstreams. The inputstream then filters the BOM. Remember to also proxy the WSDL to 'rewrite' the endpoint ;-)
HTH,
Bas

ESB SOAP service endpoint properties cacheConnections

Similar Messages

Maybe you are looking for