Blazeds proxy service and failover

Hello everyone,
I've been using Blazeds for web services proxying. It's working great so far, but I'd like to add some failover mechanism.
here below is a bird view of my architecture
And what I'd like is to be able to support failover on business layer webservices, something like :
I don't know if it's possible or not and if it is how I can achieve it. I was thingking about some failover tag in the proxy-config.xml to set several wsdl entries (URI-master, URI-slave...) but I didn't find nothing about that in the documentation. But maybe the solution is something drastically different .Anyway I hope that there is a way to make this possible
Thank you in advance for your help.
Olivier

Hi,
Can you please share the code? See if you can find any errors
in your stdout log file of your web server. If you find any errors
and cannot fix it, please share the code and the errors from the
log file.
Hope this helps.

Similar Messages

Blazeds Proxy Service Error

Trying to call an http service through a blazeds proxy
service and getting this error
faultCode = "Client.Error.MessageSend"
faultDetail = "Channel.Connect.Failed error
NetConnection.Call.BadVersion:
anyone see this b4?

Hi,
Can you please share the code? See if you can find any errors
in your stdout log file of your web server. If you find any errors
and cannot fix it, please share the code and the errors from the
log file.
Hope this helps.

How to maintain messageId when using proxy services and mq??

Hi
I am a novice to oracle service bus and trying few transformations by configuring proxy services.
Let me explain the problem I'm facing:
I have created a business service and a proxy service and configured them in a synchronous way.
I'm using MQ as a transport protocol....and message I'm passing and transforming is in xml format.
these proxy and business services are functioning properly.....but at the another end i have created another pair of busines and proxy service which will be taking request message from earlier business service and putting it into another queue which is reference as a response queue by earlier proxy service.
my second pair is also working properly. now the problem is that it is not maintaining message Id during all the routing.
and that's why im not able to read the response message from the response queue because of message ID mismatch.
Please help!!
tell me if i have to do change any particular configuration settings to maintain the message id for my request message throughout the flow.
Thanks
Edited by: ChetakCs on Jun 14, 2010 7:19 AM

Post this in OSB forum:
SOA Suite

OSB proxy service and BPEL depedency is not established in BTM

Hi All,
I am using BTM 12.1.0.3 and I have deployed a service where an OSB proxy service is taking employee information and callling a BPEL process which writes data in some database table. The OSB proxy service and BPEL got discovered in BTM but the dependecy between OSB Proxy service and BPEL process is not established in BTM. I have used soa-dorect protocol to call the BPEL from OSB. I have also tried with using http protocol in OSB for calling a BPEL but nothing worked and the depedency is not established in BTM.
Now I want to create an end-toend transaction i.e. starting from OSB proxy to the database. For this I selected OSB proxy operation and BPEL operation but correlation is not established. How can I correlate these operation? And how can I create an end-to-end transaction for this type of service where OSB calls a BPEL?
Please guide!!
Thanks in advance!!

you can manually correlate any number of services to create an end-2-end transaction. Please see http://docs.oracle.com/cd/E24628_01/doc.121/e37014/transactions004.htm#BABDBDFI on how to manually correlate services in BTM.

How to call a ALSB Proxy Service and don't wait for his response. Publish M

Hi,
I have a Proxy Service called PS1 that will invoke and another Proxy service Called PS_ProcessingNode that invokes 10 differents webservices during the orchestration and takes about 2 minuts.
I would like that if invoke PS1 that will invokes PS_ProcessingNode (asyncronously) and immediatly PS1 will return "OK" (don't wait for the response of PS_ProcessingNode) .
For simulate this scenario I am testing with:
- PS_Processing is a WSDL without response that has a JavaCallout with a Sleeper of 10 seconds.
- PS invokes with "Publish action" to PS_ProcessingNode but is waiting for PS_Processsing finish. I don't want this beahivour.
How I can do it for PS doesn't wait for the response of the PS_ProcessingNode?
Thanks.

- PS invokes with "Publish action" to PS_ProcessingNode but is waiting for PS_Processsing finish. I don't want this behavior.
I'm glad you have a solution using JMS. But still Publish action should not wait for response. If you are seeing that behavior, you can contact Support with an SR to get it fixed.
Manoj

Pleeease help... regarding Proxy Service and Business Services

Hi,
Can somebody clarify the following? I need urgent clarifications/
1. Can Proxy service only be a Web-service, i.e. WSDL dependent?
2. What about Business Services? What are the different ways you can host your Business Service?
3. How does the client connect to Proxy Service generally?Is it using the endpoint URI or the hostname/port info or by some method call?
Finally can somebody share code samples for use cases that use already developed transport providers like TCP, File etc.? I tried to use a file as input to the Proxy Service, but how to specify XSL transformations to the XML data that are in the file, as a stage in the Proxy Service pipeline?
My e-msil ID is [email protected]
Thank you for your help.
Thanks and regards,
TV Padmanabhan (TVP)

1. No it can be any kind of request: binary, text, xml...
2. ALSB support a lot of different transport/protocols:
EMAIL, FTP, FILE, HTTP, JMS, EJB, TUXEDO. In ALSB 3.0 we will add support for ERPs: SAP, SIEBL ..., MQ native and SFTP
3. It depends on the transport. For example for file, the client drops a file in the file system, for http it opens a http connection to the URL http://host:port/address etc...
4. TCP/Socket transport is provided as a sample transport in ALSB 2.5 and 2.6. You can look in the weblogic92/samples/servicebus folder. You can also write your own transport if you like. There is a public SDK.

OSB: Proxy Service and Dispatch Policy

Hi all,
I'm trying to use OSB (10.3) proxy service with dispatch policy set to WebLogic (10.3) work manager to limit maximum number of threads allocated for request to this proxy service.
It seems to me that whole dispatch policy setting is ignored in OSB. The situation is like this: I have simple Axis based web service with wait method that just waits for few seconds (based on request parameter). I use this service for testing (hm, so far just for trying to understand) OSB dispatch policy function.
Using soapUI I created a simple load test which uses 10 threads to call wait(10) - it means "wait for 10 seconds". Time limit for the whole load test is set to 20 seconds. It is clear that the total execution count is 2 x 10 = 20. So far, so good.
Then I created simple proxy service in OSB that just routes request to business service representing my Axis service with wait method. I set a dispatch policy for the proxy service to WorkManager-2threads (see below) and I expected that running the same load test with endpoint set to OSB would result in significant lower total execution count. I expected that because WebLogic should allocate 2 threads at most for all requests to this proxy service. However, that's not the case as the result is the same as in the first (Axis only) test. Just as there was no dispatch policy settings at all ...
Where is the problem?
This is the relevant part of my WebLogic configuration regarding work manager:
<max-threads-constraint>
<name>MaxThreadsConstraint-2</name>
<target>AdminServer</target>
<count>2</count>
<connection-pool-name></connection-pool-name>
</max-threads-constraint>
<work-manager>
<name>WorkManager-2threads</name>
<target>AdminServer</target>
<max-threads-constraint>MaxThreadsConstraint-2</max-threads-constraint>
<capacity xsi:nil="true"></capacity>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>

It's same problem to me. I do pressure test by loadrunner,I deployed two separate proxy service,under same concurrent user,I get same TPS from the two proxy service.but when I add low priority concurrent user,low priority TPS up.
I set the Route option as you say,but weblogic hanged immediately,and can't be accessed by the console.

Is Response Required in Proxy Service and Business Service

Hi All,
I have made proxy service that is putting message on the Queue through a Business Service. Now I wanted to know what is the use of "Is Response Required" configuration parameter in Business as well Proxy Service. Also what is the significance of the JMSCorrelationID and JMSMessageID.
Thanks,
Anuj

Hi Anuj,
You can refer to the documentation for the information on "Is Response Required" in
Proxy Service @ http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/transport.html#wp1096236
Business Service @ http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/transport.html#wp1097863
And for the significance of JMSCorrelationID and JMSMessageID please refer to link @ http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/MsgIDPatternforJMS.html
Please do reach out to me in case you need specific information.
Thanks,
Patrick

Correlation Exception - BPEL - Proxy Service and Business Service

Hi All ,
Correlation exception
Flow - BPEL - Proxy - Business service
We are invoking a proxy service from a bpel process with a correlation set(property set as Yes)) and it works absolutely fine when the service is available But the problem occurs when the service is down or a remote fault occurs.
In the fault policy we had an action saying that retry three times but when it retries three times with the same correlation set
<Action id="ora-retry">
<retry>
<retryCount>3</retryCount>
<retryInterval>2</retryInterval>
<exponentialBackoff/>
<retryFailureAction ref="ora-human-intervention"/>
<retrySuccessAction ref="ora-terminate"/>
</retry>
</Action>
It was throwing an correleation exception.
since it was hitting the service wth same correletion set it was throwing an error. Is there any way i can retry for the same service with out exception
Thanks,
Raja
Edited by: user12893766 on Oct 1, 2010 3:30 AM

1. No it can be any kind of request: binary, text, xml...
2. ALSB support a lot of different transport/protocols:
EMAIL, FTP, FILE, HTTP, JMS, EJB, TUXEDO. In ALSB 3.0 we will add support for ERPs: SAP, SIEBL ..., MQ native and SFTP
3. It depends on the transport. For example for file, the client drops a file in the file system, for http it opens a http connection to the URL http://host:port/address etc...
4. TCP/Socket transport is provided as a sample transport in ALSB 2.5 and 2.6. You can look in the weblogic92/samples/servicebus folder. You can also write your own transport if you like. There is a public SDK.

OSB 1031: proxy service and publishing JMS messages with no duplicates

Hi all,
we have a Web Service proxy that publishes messages into a JMS queue. The queue is persistent and the related connection factory is XA enabled.
The proxy does the call to the JMS business service from a route node.
If a failure occurrs after the publishing returns successfully, the caller receives back an error and it will try again to call the web service proxy.
As the message has been published successfully and was not rollbacked by the proxy, the second call could put on the JMS queue a duplicate message.
As far as we know only with JMS proxy service, OSB starts a transaction within the pipeline or are we wrong ?
What do you suggest in order to avoid such a scenario described above ?
Thanks and regards
ferp

Try this link to depict the behavior
http://allthingsmdw.blogspot.com.au/2012/09/osb-service-callouts-and-oql-part-1.html

HTTP Basic authentication for proxy service and its wsdl?

Hello:
For some reasons I needed to configure the HTTP basic authentication on a proxy service at OSB 11g. Everything was OK until I realized that, additionally to the authentication when calling the service, the OSB also asks for credentials when I try to get that proxy wsdl file.
My requirements are to secure the proxy service when is called only, not when retrieving the wsdl.
Is this possible to configure on OSB / WLS? How?
Greetings!
Edited by: user4483647 on 02-sep-2010 12:59
Edited by: user4483647 on 02-sep-2010 13:25

If I'm not wrong, Basic authentication is Transport level feature. So passing User/Password in SOAPHeader doesn't make sense. SOAP message can only be sent when you have a HTTP Connection open. During opening of HTTP connection User/Password is required for basic authentication.
http://www.student.nada.kth.se/~d95-cro/j2eetutorial14/doc/Security7.html#wp156943
Edited by: mneelapu on Apr 2, 2009 2:09 PM

DNS SRV Proxy Lookup and Failover Mechanism / Unexpected Behavior

Group,
I came across some unexpected behavior yesterday I was wondering if someone could help shed some light on the problem. In my DNS I created this record: _sip._upd.platautofinance.com which when I do a query using MX Toolbox it is correctly reporting the following:
On the SPA504 I have programmed the SRV records into the system using the following:
So here is the issue, the phones will register correctly to the primary server but after a length of time ALL the phones will abandon ship and jump to the secondary server and stay there. I have to manually shut the secondary down, reboot the endpoints at which point they will re-register with the primary. So I think I need to understand the mechanism a bit better. Here is what I can think of:
The phones are not using the primary DNS service record providers DNS servers, we are using OpenDNS instead of Network Solutions <-- Unlikely because the SPA would not be able to resolve the SIP SRV records / servers at all with a broken DNS resolution. I can tell by dropping from the primary to the secondary that resolution is taking place on the phone because they are jumping between the right ones.
My understanding is the proxy fallback interval should have the phone register (and they should be checking periodically if the primary is available again and if so, re-register the to the lowest-weighted server) but that's not happening without a manual reboot. Once on the secondary they want to stay there.
My firewall for both the primary and secondary servers do not answer ICMP.
So the question is: why do the SPA phones think the primary is offline? What is the mechanism or criteria the SPA uses to determine a server is offline and then rolling to the secondary? Why do they want to stick around the secondary which is using only a best effort connection when we have a bonded T on the primary?
Thanks as always for your help and input group! Appreciate your time.

Hello Adam,
I believe it will be easier if you call SBSC and ask the questions directly. The questions are very good and exact. I will try to answer shortly. Assuming you use only CCA to configure the system.
1. If you have set dns for your internet connection it should work, you may try with different dns servers. Please delete the SIP trunk and recreate it.
2. Please delete the SIP trunk and recreate it.
3. If you need to configure more codecs through CCA you may send feature request using envelope button of the CCA.
I hope the above answers will be helpful although very short. If they are not helpful please contact SBSC and open a case.
Best regards,
Alex

RMI service and failover

Hi All,
I am building an RMI service (implements UnicatRemoteObject). I am using Naming.rebind to bind my service - I start RMIRegistry as a standalone process. The client performs Naming.lookup to find the handle of server object.
One of our requirements is that all our services must be highly available, with reasonable fail over.
The questions are:
1. How can I handle RMI registry automatic restart when it goes down ? Alternatively can I start multiple RMI Registries and register my service with all of them ?
2. How can i restart my RMI Service when it goes down ?
3. What about the Naming.(rebind, lookup) calls ?. Is Naming service always available ?
We are using JBOss 4.0 as our app server. Any help is highly appreciated.
Regards
Vissu
.

Hi All,
I am building an RMI service (implements UnicatRemoteObject). I am using Naming.rebind to bind my service - I start RMIRegistry as a standalone process. The client performs Naming.lookup to find the handle of server object.
One of our requirements is that all our services must be highly available, with reasonable fail over.
The questions are:
1. How can I handle RMI registry automatic restart when it goes down ? Alternatively can I start multiple RMI Registries and register my service with all of them ?
2. How can i restart my RMI Service when it goes down ?
3. What about the Naming.(rebind, lookup) calls ?. Is Naming service always available ?
We are using JBOss 4.0 as our app server. Any help is highly appreciated.
Regards
Vissu
.

When we should use JMS based proxy services and when JMS Adapter in OSB

Hi,
Can somebody explain me when we could go for JMS Adapter and when we should go for JMS based service in OSB?
The one scenerio i can think of is when my provider/consumer is using jms provider other than WLS jms provider we should use jms adapter.
Edited by: user12883209 on Jan 5, 2012 5:29 AM

I don't think there are clear guidelines available, however here is my view.
1) OSB 11gR1 is not certified with Oracle JMS Adapter. It is certified with Oracle FTP, Database, AQ and application adapters.
http://docs.oracle.com/cd/E21764_01/doc.1111/e15867/interop.htm#OSBAG1403
2) In addition of the Weblogic JMS, OSB can also integrate with following provider without using adapter.
- WebSphere MQ
- Tibco EMS
3) if you need to integrate JMS with BPEL Process or Oracle SOA suite composite, it has built in support for generic Oracle JMS adapter. Oracle generic JMS adapter can integrate with AQ JMS (JMS providers OJMS 8.1.7, 9.0.1.4, and 9.2), TIBCO JMS, IBM Websphere MQSeries (IBM MQSeries JMS 6.0), Weblogic JMS, Apache, and Active MQ
http://docs.oracle.com/cd/E14571_01/integration.1111/e10231/adptr_jms.htm
4) If you need to integrate OSB with Weblogic JMS, WebSphere MQ, Tbco EMS it does not need JMS adapter.
Hope this helps !!!
Jayesh Patel
http://jayesh-patel.blogspot.com/
http://www.yagnasys.com/

WS-Security and proxy service: Unable to add security token for identity

What the reason of "Unable to add security token for identity" fault in this situation (10.3.1):
I did simple "hello word" proxy service and tried to apply custom policy binding.
WS-Policy is next:
<wsp:Policy wsu:Id="WS-Policy-Siebel"
     xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702"
     xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
     xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
     <wssp:Identity
          xmlns:wssp="http://www.bea.com/wls90/security/policy">
          <wssp:SupportedTokens>
               <wssp:SecurityToken
                    TokenType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken">
                    <wssp:UsePassword
                         Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText" />
               </wssp:SecurityToken>
          </wssp:SupportedTokens>
     </wssp:Identity>
</wsp:Policy>
Process WS-Security is setted to "yes".
While debugging I see that all works fine - I can authenticate with defined credentials and breakpoints in proxy service flow works fine.
But at the end I get the fault:
Soap fault:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Unable to add security token for identity</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>
In console:
<09.06.2010 17:39:18 MSD> <Error> <OSB Security> <BEA-387023> <An error ocurred during web service security inbound response processing [error-code: F
ault, message-id: 1721282272521583996--57dc4ccc.1291cc2282d.-7fab, proxy: OSB Project WS-Security/WSSecurityService, operation: NewOperation]
--- Error message:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault><faultcode>env:Server</faultcode><faultstring>Un
able to add security token for identity</faultstring></env:Fault></env:Body></env:Envelope>
weblogic.xml.crypto.wss.WSSecurityException: Unable to add security token for identity
at weblogic.wsee.security.wss.SecurityPolicyDriver.processIdentity(SecurityPolicyDriver.java:175)
at weblogic.wsee.security.wss.SecurityPolicyDriver.processOutbound(SecurityPolicyDriver.java:73)
at weblogic.wsee.security.wss.SecurityPolicyDriver.processOutbound(SecurityPolicyDriver.java:64)
at weblogic.wsee.security.WssServerHandler.processOutbound(WssServerHandler.java:88)
at weblogic.wsee.security.WssServerHandler.processResponse(WssServerHandler.java:70)
Truncated. see log file for complete stacktrace
Incoming soap message is:
<soapenv:Envelope      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<wsse:Security      soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken      wsu:Id="unt_TNNp0cBwU7HyPKoq" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Username>testuser</wsse:Username>
<wsse:Password      Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">testuser</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
<soapenv:Body>
<wss:NewOperation      xmlns:wss="http://www.troika.ru/Enterprise/WSSecurityService/">
<in>string</in>
</wss:NewOperation>
</soapenv:Body>
</soapenv:Envelope>
Edited by: Andrey L. on Jun 9, 2010 5:55 PM

I thought you were getting that exception when accessing the proxy.
No. Authentification works fine. Proxy body works fine. But at the end of proxy appears the exception.
Sorry for my english - I tried to show this situation on image: http://imglink.ru/show-image.php?id=9c0e0c1719f00289faf11696c6703bc3
Are you getting this exception when routing to a business service which is configured for WS-Security ??
I don't use business service in this test project - only simple proxy service with all logic inside.
PS transformation in replace action is very simple too:
(:: pragma bea:global-element-parameter parameter="$newOperation1" element="ns0:NewOperation" location="WSSecurityService.wsdl" ::)
(:: pragma bea:global-element-return element="ns0:NewOperationResponse" location="WSSecurityService.wsdl" ::)
declare namespace ns0 = "http://www.troika.ru/Enterprise/WSSecurityService/";
declare namespace xf = "http://tempuri.org/OSB%20Project%20WS-Security/Hello/";
declare function xf:Hello($newOperation1 as element(ns0:NewOperation))
as element(ns0:NewOperationResponse) {
<ns0:NewOperationResponse>
<out>Hello, { data($newOperation1/in) }!</out>
</ns0:NewOperationResponse>
declare variable $newOperation1 as element(ns0:NewOperation) external;
xf:Hello($newOperation1)
Edited by: Andrey L. on Jun 10, 2010 12:21 PM

Blazeds proxy service and failover

Similar Messages

Maybe you are looking for