Operational situation in OSB Proxy logging

Similar Questions

• OSB - access to the operational parameters within the Proxy Service

  Anyone know if it is possible to access the parameters of functioning within a Proxy Service?
  
  Use instead of logging case, we realize audit by inserting into a database. In some circles, we want to turn this option off. I would like to reuse the fair to decide or not to audit logging logs.
  
  If the flow of messages would have if (auditLevel = "Warning") then BusinessService legend for the audit.
  
  Doing it this way allows operations choose whether or not an audit, rather than make changes to the code in different environments to choose or not to audit.

  A few months back I was also working on a similar requirement where the customer would not have to go to the configuration for OSB change (and even update) to change the log level or beginning of audit. After searching for a bit, we have implemented the legend of java to read a property file and provide the value of the flag during the conduct of the audit. We have also created a java utility that allows to clear the cache of the server (because the server load & updates cache the file after each reboot). So whenever we need to make a change in the check indicator, we just change the value in the properties file and clear the cache of the server. This makes the new copy of the file of properties available in the cache server and java OSB legend takes up the same.

  It was quite complex, but the only one best solution we could find. Please let us know if you get something better.

  Kind regards
  Anuj

• 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

• OSB Proxy Service execution Timeout

  Dear Experts,
  
  How can I configure Oracle Service Bus proxy service timeout exactly? My scenario requires several service legend.
  
  Thanks in advance.
  Mike.Di

  Mike,

  Yes, the proxy of the OSB will continue running if it has launched its own transaction until the JTA timeout / any other service call error timeout/all occurs, whichever comes first (in this case the flow moves to the error handler). If proxy is running in the context of overall transaction that began at the source and then global transaction gets abandoned, then execution of the proxy will also get abandoned.

  I'll start proxy via the test console.

  This will fall in the first case (where OSB starts its own transaction)

  Kind regards
  Anuj

• BEA-382051 any transaction not found on the OSB Proxy Service

  Hello
  
  I have a proxy mq service and that has properties enabled for 1. Mandatory transaction 2. Same operation required for a response. Also added routing with QoS Options to "Exactly Once" actions to publish and c/o Service.
  
  MQ proxyQ-> proxy1 local-> localPS11-> localPS12-> localPS13
  MQ proxyQ-> local proxy2-> localPS21-> localPS22-> localPS23
  
  All these PS11, 12,... have publish and service a/s for various DB operations such as readBS, insertBS and updateBS.
  
  I searched a few threads in the forum, Anuj has also suggested to activate Options routing with QoS to "Exactly Once".
  What I did is I added and allowed to c/o/Publishing Service requesting this property [insertPS-> insertBS] and [updatePS-> updateBS] only.
  * NOT for [readPS-> readBS] area.*
  
  What is the cause of this error? I mean, what do I need to enable to publish them all and s. c/o actions regardless of readPS or updatePS?
  I also tried with httpProxy instead of mqProxyService service
  
  Error: BEA-382051 any transaction not found on the current Thread
  
  Your suggestion is very apprecited.
  
  Thank you
  
  Edited by: 1002815 may 6, 2013 07:59

  Yes, no need to add this legend and node of Road Service by participating in the overall transaction by default.

  Kind regards
  Anuj

• OSB: Proxy proxy publish async

  Hello
  
  PS_1 publishes data of PS_2 (PS_2 wsdl has never leaving is asynchronous)
  I googled and found following http://victor-jan.blogspot.in/2012/06/osb-publish-routing-and-service-callout.html:
  
  
  Publish: Used for the only application scenarios where you do not expect a response back. The target service, that you call will depend on the nature of the action to publish (sync or async).
  Invoke an external service thanks to a business service, then publish action with quality of Service (QoS) as 'Best Effort' (default) will work as fire and forget and wire will not get blocked (asynchronous call).
  Calling a service local proxy (proxy with transport as 'local' Protocol) another proxy to help publish the action then it would be a blocking (synchronous) call and thread will be blocked until the local proxy finishes processing.
  
  The same information on multiple threads on the forum.
  
  I changed the Protocol of PS_2 for the proxy for http and tested service by publishing of PS_1.
  Then created a company of PS_2 service and published PS_1 to BS_2.
  
  
  All in vain. So is the Proxy service in Proxy Publish service IMPOSSIBLE in OSB?
  
  Can anyone confirm?
  
  Thanks and greetings
  Patricia Kharwadkar

  Patricia,

  Publish call will block if QoS is defined as exactly - once.

  If QoS is better and endpoint target is a proxy service go simple it is a call blocking (source proxy waits for the completion of flow target proxy message) and if QoS is Best-Effort and target endpoint is a request-response proxy service, then control returns to proxy source as soon as the request message of proxy target flow pipeline ends.

  Kind regards
  Anuj

• Question about the OSB proxy service

  Hello
  
  I'm new to the world of SOA/OSB. I'm working on a POC from the OSB for our existing application. I have a question about the definition of the URL endpoint to the proxy service. It is possible to specify a generic url endpoint to a proxy service. Something like / SomeService / *. I tried and got errors. Is it possible to do somethig like that or it is a mistake on a conceptual level.
  
  Thank you

  anything you type in the uri of the endpoint of entry will be the contextroot to your service, so /SomeService should indeed be sufficient or as mentioned Pierluigi/SomeService/blabla is also valid (Betty is not a parameter query, but only a part of the contextroot)

  If you want to use a service like http rest

  / SomeService/blabla would still be the contextroot, and after that, you can use the query parameters

  / SomeService/badarou? var1 = test & var2 = test or/SomeService/blabla/employee/id/1

• OSB: Proxy Service Configuration

  If I understand the "Proxy service" called the service '' Business. ''
  When I set up the "ProxyService" so it should be a section of 'Service create existing' in the 'General Configuration '.
  
  But in my workshop, I don't see the "Create from existing Service" section.
  There is no way I can bind the Proxy and services businesses.
  
  No idea why this article is missing in my workbench and how to solve?

  But in my workshop, I don't see the "Create from existing Service" section.

  Not sure why it is not available with work table.

  There is no way I can bind the Proxy and services businesses.

  You can bind services to businesses with a proxy service yet. What you need to do, it's that configure the workflow of the proxy and mail flow messages add a node of the route. From this node, you can call the business service.

  Alternatively, you can add pipeline request and response in mail flow (before the node of the route) and you can use publish/service legend action from there to call a business service.

  Please see-

  http://download.Oracle.com/docs/CD/E13159_01/OSB/docs10gr3/Userguide/modelingmessageflow.html

  Kind regards
  Anuj

• Search for OSB proxy service

  I create a dynamic road in a proxy OSB service. Is there a way to search for a service proxy by using its 'Endpoint URI"?
  
  Thanks for any help!
  
  The f

  I think that Pascal describes the only possible way for your case.

  As far as I understand, you want to have a function that looks somehow in the current configuration. Something like getProxyByEndpoint(). Am I wrong? I had a similar need, so I filled the enhancement request in Oracle support. I encourage you to do the same. You will not get your service anytime soon, but someday maybe... :-)

  There is a huge 'thinking skills' gap in OSB. I think that we can help make OSB a better product describing our needs in an enhancement request form.

• using weblogic unit-of-order (PUA) in the osb proxy service

  Hello
  
  I have a deployed on Weblogic server JMS queue. The messages in the queue are grouped using Weblogic JMS_BEA_Unit-of-order (PUA).
  
  Now, I have an OSB 10 g of Proxy Service that reads messages from the queue. The problem is, upon receipt of a message, acknowledgement of receipt is sent immediately, thus eliminating the message from the queue and the next with the same unit-Of-Order message is ready for processing.
  
  But the business scenario is the first message to read, processed and then decide to recognise or not. The second message should not be interpreted, unless the previous message is processed successfully.
  
  Can someone help with this scenario?
  
  Thank you
  Alex
  
  Published by: user9024636 on February 11, 2010 02:57

  with PUA, you'll need to do the syschronous transaction.
  1. make transacation enable XA
  2 using the road for the sychrounous transaction
  3. use the routing options, and then select mode = request-respone
  4. If the Proxy service is based on the jms then you should also together WHAT JMS Transport-> Advance settings-> XA is required-> checked

  Kind regards
  http://SOA-Street.blogspot.com

• OSB Proxy: response with failure: not getting caught in BPEL CatchAll block

  Hello
  
  I have a scenario where the Composite SOA name PS of OSB. In the PS OSB error handler, I use a response with failure at the end, and when this happens, the flow does not block the BPEL Tote, rather than the BPEL flow is get executed successfully. I believe that when we meet with failure (code 500), the current should go to the customer error handler.
  
  Please someone confirm what is the expected behavior.
  
  Thanks in advance.

  have you tried to call in the service of soapui and check the weather, you receive an envelope of soap fault?

  You can try to replace the body in the handler service error with a fault (hardcoded) soap envelope, simply too self how the capture of bpel is on it

  http://www.xenta.nl/Blog/2010/07/17/Oracle-service-bus-11g-handling-SOAP-faults/
  Maybe one is of no use

  We use the same in our middleware implementations and catches in bpel works very well for use (response failure + failure in the SOAP body)

• OSB 12 &amp; 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

• 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!

• OSB console error messages: how to see the cause of the error

  Some of the error messages from the OSB, like the one below
  
  BEA-382612
  : Error to prepare the message for shipping
  Description
  A runtime exception has occurred during the preparation of the message out for the routing node. This occurred due to an error during the execution of the actions of the node routing request. There should be a specific error message that will point the cause of the problem
  
  How to view the cause of the error, such as described in the "BOLD" above. I'm not on the console when an error occurs.
  
  THX
  Ashwani
  
  Published by: Ashwani Kalra January 16, 2012 16:27

  Try to keep track of the message in the test console. Change the server debug logging level to see more debugging messages. Enable tracing in an operational framework of the proxy service and business.

  Most likely your proxy is not able to find the business service to route the message and it is why throw above mentioned error.

  Kind regards
  Anuj

• OSB Service post a Message in the queue JMS twice or duplicate

  Hello

  I have an adapter of the poll of OSB Proxy Service database

  Strategy of the poll: logic of delete

  Column name: status

  Read value: P

  Unread value: N

  Form #1:

  Change of status to "n" and given an end point valid URI of the JMS queue

  Success: DBAdapter > > OSBProxy > > PublishToJMSQ and the situation has changed to 'P '.

  Form #2:

  Change in status of "n" and in view of an invalid endpoint URI of the JMS queue. That is to say, remove resources from JMS queue

  Error: DBAdapter > > OSBProxy > > OSBBusinessService (@Service Error Handler) > > DBAdatper and the situation has changed to 'E '.

  Both work as expected when they are tested one by one. However, if I change #1 & 2 # Record Record and commit at the same time, the status changes to 'P' and 'E' correctly, but the message is published in the JMSQ TWICE (Duplicate) of the first disc. Please note the folder payload #1 and #2 are different.

  It is a behavior strange and unable to understand why it's happening and how it is resolved.

  The two ""required Transaction ","Same Transaction for answer"were not affected ways unchecked. "

  I took non - XA Datasources and QoS in road @Stage activity Publish Options is exactly once. And the version is 12 c

  Your help is very appreciated.

  Thank you

  Hello, the problem has been resolved by defining lines of data per Transaction on 1 in the DB adapter configuration.