Routing of OSB

Similar Questions

• OSB 12 & dynamic route: $operation is empty

  I'm migrating a project of OSB 11 g to 12 c and encountered a problem.

  The project has a part where a proxy call another proxy via a DR.

  For example:

  Proxy entry:

  1. service of routing XML forms, for example:

  < = xmlns:ctx ctx:route' http://www.BEA.com/WLI/SB/context '>

  < ctx:service proxy = "true" > DR-with-operation/Destination < / ctx:service >

  {$operation} < ctx:operation > < / ctx:operation >

  < / ctx:route >

  2 call the local proxy of destination.

  Destination proxy:

  1 read the $operation and executes an action based on its value.

  Now, the question: proxies use the same WSDL and WSDL has the same top element for all applications. Therefore, the selection of the operation of SOAP - env:Body is not possible. The selector is set to SOAPAction, which is NOT right - nobody sent SOAPAction to the second proxy - but it works in OSB 11 because $operation in the second proxy corresponds to the value set in ctx:route by the first proxy.

  No more the OSB 12. The OSB 12 the $operation is empty. Thus the code fails.

  Here is a minimal test project to reproduce the case: http://genericparallel.com/wp-content/uploads/2014/07/DR-With-Operation.zip

  Of course, I could pass through the head of a transport operation, but my example is a simplification of the actual design. The first proxy in my case is a shared code that is used to call hundreds of different proxy servers. I don't want to inject everything with a transport header arbitrary that they do not need. Ideally, I'd like that the $operation is filled in the same way as before.

  Does anyone have an idea about this problem?

  Vlad

  < signature link removed by the moderator, as directed by the OTN FAQ >

  Try this for your case

  DR-with-operation/Destination

  {$operation}

  Greg

• OSB 11 g dynamic routing number

  Hello
  
  I'm going crazy for not being able to get DynamicRouting to work. I use the DynamicRouting option in RouteNode and in the * variable Panel service of this action, I have the following:
  
  < ctx:route >
  < ctx:service proxy = "false" > /MyProject/Services/BusinessServices/MyBizService.biz < / ctx:service >
  {$operation} < ctx:operation > < / ctx:operation >
  < / ctx:route >
  
  The Sales Department is here and the path is correct. $Operation is checked to ensure that the correct value.
  The installation is I have a proxy service based on a WSDL and in the node of the road I am trying to dynamically deliver to a business service.
  
  I get the following error:
  The invocation was an error:
  .
  < soapenv:Envelope = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv >
  < soapenv:Body >
  < soapenv:Fault >
  soapenv:Server < faultcode > < / faultcode >
  < faultstring > BEA-382612: error prepare the message for shipping < / faultstring >
  < detail >
  < con xmlns:con: fault = "http://www.bea.com/wli/sb/context" >
  < con: errorCode > BEA-382612 < / con: errorCode >
  message preparation < con: reason > error for shipping < / con: reason >
  < con: location >
  < con: node > RoutingToDataServices < / con: node >
  request pipeline - < con: path > < / con: path >
  < / con: location >
  < / con: fault >
  < / details >
  < / soapenv:Fault >
  < / soapenv:Body >
  < / soapenv:Envelope >
  
  If just use the Table routing or action of the road, there is no error and flow works very well.
  
  Everyone encountered problems with dynamic routing in this nature?
  
  Thanks in advance,
  
  Mani

  I use the web console for my development OSB and when I click on the business service the path appears as "Back/BusinessService/CreditRatingTemplate" (based on the example downloaded from the link given by me)

  I guess you are using the Eclipse/workshop for development and therefore find the below:

  * / * NGWS/Services/BusinessServices/NGWS_http.*biz*

  Can you replace it without the front / at the beginning of the URL and see if it works.

  Thank you
  Patrick

• How to use "Routing Table" option in the Proxy in OSB service?

  Hello
  
  I created business services and Proxy in my console of OSB. I used the "Custom Query" option when creating the database adapter and I am passing a parameter to the query. My input parameter is 'name '.
  
  Based on the input for this parameter values, I spend a values corresponding to the query. By example, if I pass the following values to the input parameter "Name" (India) I need to spend "Value1" to my request.
  
  The India-> value1
  China-> value2
  America-> value3
  
  To achieve this requirement, I used option "Routing Table". I specified the values as follows: -.
  
  Expression - $body / fet:FetchCustDataInput / fet:Name
  Operator - '='
  Compare the value - India
  Service - "my Webservice.
  Operaton-"my Service operation.
  
  In the "application of Actions:" I added the 'add an Action-> processing e-mail-> replace' and provided the following values.
  
  Replace < XPath > = $body / fet:FetchCustDataInput / fet:Name
  Variable = 'name '.
  with the Expression = xs:string('Value1')
  and the "Replace the content of the node" option selected.
  
  No validation error I encountered. I created the routing table in the Proxy service. But when I try to run the service proxy in my Test Console, I get the following error
  «The call resulted in an error: an unknown error during the processing of the message of service ProxyService OSBQueryService/FetchByCustomQuery/FetchByCustomQueryPS.»
  
  I even activated "Direct call" and 'Include Tracing' options as well. The message in "Tracing" give "(echo request)
  Routed service. No Service has been invoked, echoed the demand. ».
  
  Can someone please help me solve this problem.
  
  Thanks in advance,
  Udaya

  Hi Marion,.

  Replace = $body / fet:FetchCustDataInput / fet:Name
  Variable = 'name '.
  with the Expression = xs:string('Value1')
  and the "Replace the content of the node" option selected.

  Above replace the action is wrong. It should be like -

  Replace = $body / fet:FetchCustDataInput / fet:Name
  Variable = body
  with the Expression = xs:string('Value1')
  and the "Replace the content of the node" option selected.

  Kind regards
  Anuj

• OSB - detection of address of endpoint of a route in the request action

  Hi all
  
  I need to detect the address of endpoint of a routing inside the pipeline of action demand that routing to send it to a legend of Java. Can someone help me how to detect?
  
  Note: I tried to access it from two $outbound and $inbound variable transport paths. Both return null in the pipeline of action queries. Either way, version of the OSB is 10gR 3.
  
  Thanks in advance.
  
  Published by: Serhat Dirik May 13, 2010 12:41 AM

  I'm not aware of any "routing endpoint address. I think that you can define service and exploitation at the action of routing, and you cannot set the end point it. So I guess that you are referring to the URI of a business service that you define for the routing.

  If this is the case, then Yes, you can not read URI (or end point if you wish) of this service of the company at run time. I have addressed a service request Oracle support a few months ago. They confirmed that it was currently impossible for this use case and arranged an enhancement request.

• OSB - How select variable used in the routing for buss request message. serv.

  I have "modeling of a stream of messages to a proxy service.
  According to the content of the incoming request message, a (conditional) branch is selected. The message must be routed to a business service in this branch.
  This service of the company has a different message definition requires that the proxy service. A kind of transformation is probably necessary. (not yet implemented)
  Question is how to choose what variable structure (I created a variable of Interface Service for business) that will be used during the call to the sales department.
  Only thing that I can choose, the service and operation.
  
  How to continue?

  The payload for the service of the company must be in the * variable $body. There are also other variables pre-defined as $header and $attachments that could make sense if your need to send SOAP headers or accessories for business service.

• jms OSB 12 c security question

  Hello

  I am preparing a demo and played with the settings of transaction in osb12c on jms queues.

  installation program:

  a proxy incoming jms that reads inputQ (with a factory connections XA)

  a business service database of jca that insert a record into a database

  a business of jms service that publishes an account in outputQ (with a factory connections XA)

  This proxy-request pipeline - I add an action to publish (with qos: exactly - once)

  in the routing node, I call the "database business service".

  pipeline parameters: transaction required = N and 'same deal for answer' = N

  testscenarios:

  1.

  I run a first test: every success: a record added to the database and a record in the outputQ.

  2.

  I run the same test again; This translates into an error of violation of unique key in the database; so no record is added in the database = OK

  I think (considering the two parameters of transaction in the pipeline have the value 'n') that my record would be released in my outputQ, but it is published in the errorQ.

  Why is this happening?  Why isn't - this report not published in the outputQ, there is no specified local transaction.

  and when I change this setting to 'Y' it would be published in the errorQ, because it's all in the same local transaction.

  Or it has something to do with the 'global' operation in osb?  And if so, what is the meaning of this definition "required transaction?

  What Miss me?

  I founded this test on this video: https://www.youtube.com/watch?v=KtUXaXeoUVU (as you can see this video shows other then my results)

  Since the transaction is started in the pipeline, the delivery of the message to jms proxy is outside the transaction, in case of error/rollback if you want the message to be redistributed or redirected use xa jms connectionfactory

• Concern for Rollback transaction OSB (11.1.1.7)

  Hi all.

  I'm working on a usecase where service OSB dequeue the message AQAdapter (XA datasource) and routes to business (BPEL way).

  My problem is, whenever there is a BPEL downwards, the transaction get rollback in queue and try again for some many times.

  Then, I activated "Same transaction for answer" property on proxy and Manager of additional error at the level of the road with error recovery (or response I tried with failure).

  I am able to roll back the transaction and do try again when ever anything BPEL down, but the real problem is, it's a very new attempt BPEL is launched, even if the bpel is up and running, it's yet another attempt (able to see the BPEL instances).

  He only restores when it comes to active 'Same operation for the response', if I do not clear so there is no retry.

  I tried options like

  • adjustment of Qos in routing to only once.
  • respond successfully in the pipeline of response (when BPEL is upward).
  • allowing the transaction required so even operation for the answer.

  nothing has really changed anything

  Can someone help?

  (I know that there are similar posts on this topic in this forum, each of them tried, but they did not work)

  Thank you

  NReddy

  Problem has been resolved, could be useful to someone

  The solution is:

  • Enabled the transaction required on the proxy service property.
  • Published in BS the request pipeline
  • Used exactly once Options QoS routing
  • Add error handler with error recovery on the level of the stage (which is to be published in it)

  (even if I tried to trigger the error on the pipeline to answer, is not even trigger errors.) So, basically, he won't have to answer pipeline)

• OSB, avoid variable $body is deleted?

  Hello world.

  I have a proxy in OSB and on my proxy, I have a ROUTING that receives an HTML in response, but my variable body is removed because they get the HTML and contains special promotions of characters. How can I avoid that variable body are removed?

  Thank you

  In the stream of osb proxy use a legend of service instead of a route. Legends of service does not replace the body variable.

• Legend of pair pipeline with route service

  OSB 12 C

  I'm doing a legend of service that gets a sessionID to the sessionID response in the cookie header to the original body sent via the proxy to the service of the company.

  I have the proxy service and business service based on wsdl even.  This method works.  I then put a pair of pipeline once the proxy service and a legend in the pair of pipeline service request action.  This legend of service works.  In pair legend pipeline response I get the sessionID of the header and put it in a variable $sessionID using 'assign '.  This method works.  After the pipe, I have a node of the route. I have the operation path set to "use an inbound operation for outgoing" since my service proxy and business are based on the same WSDL.  In the action request routing, I use a "transport header" to set the $sessionID as cookie.  It seems to work. However, the body of the message that I sent to the proxy service does not seem to happen on the crux of the road as a business service request?

  Your $body might get replaced by the legend of service if you are using $body as the input and output variable. Connect your $body in the pipeline to route request to see the content. As soon as the message is received in the Pipeline pair i, e before calling assign legend of service $body to some as $intialbody v ariable, after the award of legend service $initialbody to the body.

• SOA 12 c-to-end (e2e) tutorial: Error executing OSB confirm payment

  23:43:44.797 - ServerSession (1576216129)--file:/scratch/ababchak/fmwhome12/soa/soa/modules/oracle.soa.fabric_11.1.1/tracking-fabric.jar_soa_audit_persistence_unit successful login

  < com.bea.alsb.common.catalog.CatalogLogger > < CatalogLogger > < log > < OSB-382191 >

  com.bea.wli.sb.pipeline.PipelineException: Transport error (error code = OSB-380001): Internal Server Error

  at com.bea.wli.sb.pipeline.components.Node.processMessage(Node.java:94)

  at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:905)

  at com.bea.wli.sb.pipeline.components.Router.processMessage(Router.java:205)

  at com.bea.wli.sb.pipeline.MessageProcessor.processResponse(MessageProcessor.java:228)

  at com.bea.wli.sb.pipeline.RouterCallback.handleFault(RouterCallback.java:167)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.OutboundResponseMetadataHandler.handleFault(OutboundResponseMetadataHandler.java:66)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.OutboundMessageContentHandler.handleFault(OutboundMessageContentHandler.java:116)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.LoadBalanceFailover$ LoadBalanceFailoverHelper.handleFault (LoadBalanceFailover.java:572)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.UpdateOutboundStatistics.handleFault(UpdateOutboundStatistics.java:105)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.EndpointManagementHandler.handleFault(EndpointManagementHandler.java:160)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  to com.bea.wli.sb.service.handlerchain.handlers.TransportProviderInvoker$ ServiceTransportListener.onError (TransportProviderInvoker.java:317)

  to com.bea.wli.sb.transports.http.wls.HttpOutboundMessageContextWls$ RetrieveHttpResponseWork.handleResponse (HttpOutboundMessageContextWls.java:131)

  to weblogic.net.http.AsyncResponseHandler$ MuxableSocketHTTPAsyncResponse$ RunnableCallback.run (AsyncResponseHandler.java:549)

  at weblogic.work.ContextWrap.run(ContextWrap.java:40)

  to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:548)

  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)

  at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)

  < BaseCubeSessionBean > < BaseCubeSessionBean > < logError > < BPELFault:faultName unhandled: {{http://docs.oasis-open.org/wsbpel/2.0/process/executable} selectionFailure}

  messageType: {{http://schemas.oracle.com/bpel/extension} RuntimeFaultMessage}

  Cikey = 10004, FlowId = 10002, key of the current activity = 10004-BpAss0 - BpSeq0.3 - 2, current name of activity = setCreditCardNumber, ComponentDN=default/ValidatePayment!1.0*soa_013b3a7d-7a7f-4b7a-8b6a-ee1de9e99da3/validatePaymentProcess >

  < com.bea.alsb.common.catalog.CatalogLogger > < CatalogLogger > < log > < OSB-382191 >

  com.bea.wli.sb.pipeline.PipelineException: Transport error (error code = OSB-380001): Internal Server Error

  at com.bea.wli.sb.pipeline.components.Node.processMessage(Node.java:94)

  at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:905)

  at com.bea.wli.sb.pipeline.components.Router.processMessage(Router.java:205)

  at com.bea.wli.sb.pipeline.MessageProcessor.processResponse(MessageProcessor.java:228)

  at com.bea.wli.sb.pipeline.RouterCallback.handleFault(RouterCallback.java:167)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.OutboundResponseMetadataHandler.handleFault(OutboundResponseMetadataHandler.java:66)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.OutboundMessageContentHandler.handleFault(OutboundMessageContentHandler.java:116)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.LoadBalanceFailover$ LoadBalanceFailoverHelper.handleFault (LoadBalanceFailover.java:572)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.UpdateOutboundStatistics.handleFault(UpdateOutboundStatistics.java:105)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.EndpointManagementHandler.handleFault(EndpointManagementHandler.java:160)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  to com.bea.wli.sb.service.handlerchain.handlers.TransportProviderInvoker$ ServiceTransportListener.onError (TransportProviderInvoker.java:317)

  to com.bea.wli.sb.transports.http.wls.HttpOutboundMessageContextWls$ RetrieveHttpResponseWork.handleResponse (HttpOutboundMessageContextWls.java:131)

  to weblogic.net.http.AsyncResponseHandler$ MuxableSocketHTTPAsyncResponse$ RunnableCallback.run (AsyncResponseHandler.java:549)

  at weblogic.work.ContextWrap.run(ContextWrap.java:40)

  to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:548)

  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)

  at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)

  < BaseCubeSessionBean > < BaseCubeSessionBean > < logError > < BPELFault:faultName unhandled: {{http://docs.oasis-open.org/wsbpel/2.0/process/executable} selectionFailure}

  messageType: {{http://schemas.oracle.com/bpel/extension} RuntimeFaultMessage}

  Cikey = 10006, FlowId = 10003, key of the current activity = 10006-BpAss0 - BpSeq0.3 - 2, current name of activity = setCreditCardNumber, ComponentDN=default/ValidatePayment!1.0*soa_013b3a7d-7a7f-4b7a-8b6a-ee1de9e99da3/validatePaymentProcess >

  < com.bea.alsb.common.catalog.CatalogLogger > < CatalogLogger > < log > < OSB-382191 >

  com.bea.wli.sb.pipeline.PipelineException: Transport error (error code = OSB-380001): Internal Server Error

  at com.bea.wli.sb.pipeline.components.Node.processMessage(Node.java:94)

  at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:905)

  at com.bea.wli.sb.pipeline.components.Router.processMessage(Router.java:205)

  at com.bea.wli.sb.pipeline.MessageProcessor.processResponse(MessageProcessor.java:228)

  at com.bea.wli.sb.pipeline.RouterCallback.handleFault(RouterCallback.java:167)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.OutboundResponseMetadataHandler.handleFault(OutboundResponseMetadataHandler.java:66)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.OutboundMessageContentHandler.handleFault(OutboundMessageContentHandler.java:116)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  to com.bea.wli.sb.service.handlerchain.handlers.LoadBalanceFailover$ LoadBalanceFailoverHelper.handleFault (LoadBalanceFailover.java:572)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.UpdateOutboundStatistics.handleFault(UpdateOutboundStatistics.java:105)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.handleFault(AbstractHandler.java:147)

  at com.bea.wli.sb.service.handlerchain.handlers.EndpointManagementHandler.handleFault(EndpointManagementHandler.java:160)

  to com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler$ 1.handleFault(AbstractHandler.java:336)

  to com.bea.wli.sb.service.handlerchain.handlers.TransportProviderInvoker$ ServiceTransportListener.onError (TransportProviderInvoker.java:317)

  to com.bea.wli.sb.transports.http.wls.HttpOutboundMessageContextWls$ RetrieveHttpResponseWork.handleResponse (HttpOutboundMessageContextWls.java:131)

  to weblogic.net.http.AsyncResponseHandler$ MuxableSocketHTTPAsyncResponse$ RunnableCallback.run (AsyncResponseHandler.java:549)

  at weblogic.work.ContextWrap.run(ContextWrap.java:40)

  to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:548)

  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)

  at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)

  I solved the problem, the solution seems weird, but it worked, I have not changed anything inside the Application of OSB or Composite associates.

  EM, I activated the ServiceBus tab followed for these services to OSB deployed operation, and he began to accept my service request.

• Consume message JMS work through proxy OSB service unit

  Hello

  Someone knows how to consume a unit of work (UOW) JMS message using a type of OSB Proxy Service of JMS?

  I can present a work unit JMS message (which is composed of several constituent messages) using a combination of service OSB proxy & business and defining the UOW transport headers properly. I can also separately produce and consume Java objects via a JMS queue where consumption is made via the proxy OSB (of type java request message), but these are not messages UOW.

  Apparently, as soon as it is a message of the UOW then consumed message is ObjectMessage ArrayList and we use the type of 'Java' request for the proxy consumer JMS message, but I'm not sure of how to create the jar of simultaneous customers for use in the transport configuration of the proxy service same JMS for output ObjectMessage ArrayList (message UOW).

  Ideally I would like to consume a single UOW XML message via a proxy OSB JMS service.

  Pointers would be appreciated.

  R

  Finally got this working!

  For posterity: necessary to insert messages JMS Java object on the side of the producer (Business Service) OSB JMS with UOW correct jms header set in the node of the transport route. Then consume the message of working group on the other side via the proxy service of jms with "java" request message type, with appropriate jar containing the class of the object as the 'Customer' jar in Transport JMS configuration. In the same JMS consumer proxy I had to make a legend of java, by transmitting the contents of $body, using java.util.ArrayList and javax.jms.ObjectMessage as entry in a method (.. decodeJavaMessage (ArrayList ...)). In this legend of java class, you can get to each ObjectMessage individual via the cast method get() on Arraylist to (ObjectMessage) and then just catalogued the getObject() on this Objectmessage in your original Java class (the same as what you have inserted initially on the queue).

  I hope someone saves some time in the future!

• Message access control in the OSB proxy service when the Service Type is the Any SOAP Service

  Hello

  We have a proxy OSB service where the Service Type is 'no matter what SOAP Service'. We use Auth.xml to authenticate messages to achieve this proxy service.

  It is, ca we apply Message this proxy access control so that only user A is allowed to sent message has and only user B is allowed to message sent B?

  Us know if the proxy OSB service is based on a wsdl, then we can apply access control message for each operation in the Security tab - and thus specify which user can access the operation. But unfortunately, we have not a wsdl, because this service proxy is a proxy gateway and must accept any SOAP message reaches.

  For example, if the user name in the SOAP header is msgAUser, get is accepted.

  "< soapenv:Envelope xmlns:soapenv ="http://schemas.xmlsoap.org/soap/envelope/">"

  < soapenv:Header >

  "< xmlns:wsse wsse: Security ="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">."

  < wsse: UsernameToken >

  < wsse:Username >msgAUser< / wsse:Username >

  < wsse:Password >msgApwd< / wsse:Password >

  < / wsse: UsernameToken >

  < / wsse: Security >

  < / soapenv:Header >

  < soapenv:Body >

  <Get>

  ...

  < /Get>

  < / soapenv:Body >

  < / soapenv:Envelope >

  If the user name in the SOAP header is msgBUser, then MessageB is accepted.

  "< soapenv:Envelope xmlns:soapenv ="http://schemas.xmlsoap.org/soap/envelope/">"

  < soapenv:Header >

  "< xmlns:wsse wsse: Security ="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">."

  < wsse: UsernameToken >

  < wsse:Username >msgBUser< / wsse:Username >

  < wsse:Password >msgBpwd< / wsse:Password >

  < / wsse: UsernameToken >

  < / wsse: Security >

  < / soapenv:Header >

  < soapenv:Body >

  <MessageB>

  ...

  < /MessageB>

  < / soapenv:Body >

  < / soapenv:Envelope >

  Any suggestions please?

  Understood.

  My current client, we have faced the same problem and implemented a similar design which nevertheless has important benefits.

  The problem with proxy input all SOAP is not only in the complexities of authentication. Most important, resources fine grain (thread) management becomes impossible: proxy entry has a workmanager, one constraint of son max. If any single service behind entered proxy knows an influx of requests (because of a peak or a misconfigured customer), he eats the workmanager dry and the rest of the services become too inadmissible.

  In this spirit, we have implemented the following diagram. It's a little more complicated, but it serves us well for a few years already:

  EntryProxy 1-> Interceptor entering Proxy-> Proxy 1

  EntryProxy 2-> Interceptor entering Proxy-> Proxy 2

  ...

  Enter proxy doesn't do Nothing but shall forward the request for interception of incoming traffic. Power of Attorney of the entry, however, has its own WSDL, authentication and the workmanager which allows precise control.

  Another important aspect of a proxy of the entry, it is that it passes a custom header containing the name of the destination of the interceptor, e.g. TargetURI = "ProxyService/Paypal/Paypal.

  Incoming Interceptor Proxy performs all recording, the error handling and other common tasks.

  Then, according to the last header, the proxy of the interceptor makes a dynamic call to route to the specified destination.

  Yes, this design has an additional moving part - a proxy entry - but he a) works b) guard control all in our hands. The entry proxy is a very small point; When I need to make a new one, I just copy an existing one and replace the WSDL file and the value of the TargetURI - 30 seconds of work.

  Hope that helps.

  Vlad

  http://vladimirdyuzhev.com

• can we use service legend to dynamically call business service in OSB

  My requirement is: contact service issue. moments of for - each loop in OSB. Node road that we cannot use in the foreach loop.

  can we use service legend to call business several times? and how can we pass endpoint url to business service using the legend of service.

  Please help me.

  Yes you can use routing options to override the legend service endpoint url. See

  http://docs.Oracle.com/CD/E23943_01/admin.1111/e15867/proxy_actions.htm#i1315299

  The action of routing Options can be used when the context variable $outbound is valid. It can be added to the following actions:

  • Publish
  • Dynamic publishing
  • Publish the Table
  • Legend of service
  • Routing
  • Dynamic routing
  • Routing table

• POST URL using OSB

  Hello

  I have a requirement to hit a URL that will give me an answer.

  I created a proxy service that sends the URL by using the routing action at the service of business and commercial services using the POST method to call the URL.

  I specified the xsd answer in business. The URL is accessible from the browser but when I test my OSB I get following error.

  < con: errorCode > BEA-382502 < / con: errorCode >

  < con: reason >

  OSB services legend action received an error response

  < / con: reason >

  < con: details >

  " < = xmlns:con1 con1:ErrorResponseDetail ' http://www.BEA.com/WLI/SB/stages/transform/config ">

  < con1:detail >

  & lt; Response = xmlns:i'http://www.w3.org/2001/XMLSchema-instance"> ".

  & lt; Code >-7 & lt; / Code >

  & lt; Message > Bad request & lt; / Message >

  & lt; Result > 0 & lt; / result >

  & lt; / answer >

  < / con1:detail >

  < con1:http - response-code > 400 < / con1:http - response-code >

  < / con1:ErrorResponseDetail >

  Can someone please make me if there is nothing wrong with my approach?

  The server does not understand the request.

  Pointers are highly appreciated.

  With respect,

  Hard

  This is resolved. I had to call the GET method and do not clearly POST to get the answer.

  Stupid mistake.

  With respect,

  Hard