ALSB Proxy Service

Hi all,
We are not able to invoke ALSB proxy service from BPEL ? Please help me on this issue.
Thanks & Regards,
Bharathy.

Can u make me clear , how to use business service in OSB pipeline ?http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/concepts/wwimages/msgflow_layers.gif
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/concepts/wwimages/msgprocess.gif
1)Client ----->2)Transport End Point -------->3)Pipeline---4) ServiceCallout/Publish/Route-----5) BS--------->6)Transport End Point----7) Service
2&3 combined is Proxy definition; BS is abstraction of the actual end-point outside of OSB. BS cannot be directly invoked. BS can only be invoked from the pipeline.
How to invoke this proxy service from BPEL ? Depending on your use-case. Simplest would be to use http transport. Get some WSDL, create proxy using the wsdl. From this proxy create get an effective WSDL
http://HOSTNAME:7001/websvctestproject/cmplx_proxy_svc?wsdl. Use this WSDL to invoke the proxy. You can also use BPEL transport or any other transport JMS, ftp etc

Similar Messages

Remove SOAP Header Element from ALSB Proxy Service Response

I've got a client of one of my ALSB Proxy services that needs the SOAP header element removed from the response. I'm struggling to find a way to do that with a WSDL-based proxy service. Do I need to change my service to an Any XML Service or is there an easier way?

At the same time, could you please also tell me how do i convert a XML Response from a business service to a SOAP Response in Proxy Service.
My client is expecting a soap response and the backend gives back only the XML Response
Thanks in advance!!
~Swagat

ALSB Proxy Service error calling Business service

I have an external webservice on Weblogic 8.1 SP5, and I configured Business Service in ALSB 2.6, that is able to invoke the external webservice. But When I create Proxy Service based on the existing Business service and try to invoke the proxy service I get "no SOAP Action Header" error in WebLogic 8.1 SP5 External webservice.
AxisFault
faultCode: {http://xml.apache.org/axis/}Client.NoSOAPAction
faultSubcode:
faultString: no SOAPAction header!
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:no SOAPAction header!
at org.apache.axis.transport.http.AxisServlet.getSoapAction(AxisServlet.java:1004)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
{http://xml.apache.org/axis/}hostname:ossinv1d
no SOAPAction header!
at org.apache.axis.transport.http.AxisServlet.getSoapAction(AxisServlet.java:1004)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Also I get
com.bea.wli.sb.pipeline.PipelineException in the ALSB.
Is it a known issue ?

The back end service basically complains the SOAPAction http header was not included in the request. Typically this header is added automatically by ALSB if the proxy is of type SOAP and the wsdl contain the SOAPAction value for the operation invoked.
Alternatively you can force the SOAPAction header to be set to the correct value by adding a transport header action in the request part of the routing node.
Gregory Haardt
ALSB Prg. Manager
[email protected]

ALSB Proxy services deployment management

Hi all,
I have a problem now.
We have many proxies services running in a ALSB domain.
Some of them need to transfer hundreds MB XML data very frequently. They are listening to a JMS queue. And when they are working, they will cause the whole system too heavy-loaded to work.
So we want to add a new server into this ALSB domain to run the data transfer proxy services.
Because the data transfer proxy services have too much dependencies to separate, our thought is to deploy the all the projects to the new server and control the data transfer proxies only run on the new server.
Is it possible? Can I specify some JMS proxy services only running on server1 and other proxy services running on server2 (server1 and server2 are in the same domain) in ALSB?
Thanks in advance.
Garriot Zhang

Is it possible? Can I specify some JMS proxy services only running on server1 and other proxy services running on server2 (server1 and server2 are in the same domain) in ALSB?No. When a proxy is deployed it gets deployed to all servers. OSB does not give explicit control on which server a proxy should be deployed.
Manoj

How to invoke ALSB proxy service externaly

Hello,
I.m trying to understand the ALSB and stumble across an issue and hope one of you guys (from BEA) can help out?
I've created the services from the Mortgage services tutorial successfully and now I'm trying to invoke the proxy services externally. By externally I mean as a partner link from within Oracle BPEL. So far this does not work. The error message states a missing protocol in the service URL. I checked this and it is true: the wsdl of the proxy service contains only a relative path (/loan/gateway1), so the protocol and server name and port are missing. Further, I tried to change the URI of the proxy service, but ALSB does only allow a relative URI.
My question is: what am I missing so the proxy service can be invoked externally?
I am on the right solution path to invoke a proxy service instead of a business service, right!?
Thank in advance.
Regards,
Harm Verschuren

I tracked down the problem. The proxy service and the business service it routes to use rpc encoded. The RPC encoded message comes to the proxy service from BPEL which transmits it without modification to the business service. The WLS web service that impements the business service is unable to decode the message persumably because it did not like the way BPEL encoded the message. Below is the message part that BPEL sent: All the xsitype attributes are part of RPC encoding.If you use the alsb test console to pass this message directly to the business service, you will see the decoding error thrown by wls.
<loanRequest xmlns:pns0="java:normal.client"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns0="http://example.org"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<pns0:Name xsi:type="xsd:string">Joe</pns0:Name>
<pns0:SSN xsi:type="xsd:string">123456789</pns0:SSN>
<pns0:Rate xsi:type="xsd:double">3</pns0:Rate>
<pns0:Amount xsi:type="xsd:long">50000</pns0:Amount>
<pns0:NumOfYear xsi:type="xsd:int">20</pns0:NumOfYear>
<pns0:Notes xsi:type="xsd:string">test</pns0:Notes>
</loanRequest>

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

Dynamic orchestration using multiple proxy services

The project I am currently on is using ALSB for service orchestration. For a given orchestration, we would have one orchestration proxy (the control center), that synchronously calls a sequence of alsb proxy services.
Each proxy service in this second level fronts one or more business service calls to perform a specific operation ("Create Account", "Create User", etc.).
So far so good, all this can work just fine (and much of it is already working in production). The trick that I am trying to make happen currently, is to dynamically load the list of second-level proxies and loop through the list to trigger calls.
Loading a list of proxy paths/names is no problem, I have many options there. It's when I try to take that list and loop through it, calling each proxy on the list that I am stuck.
Unfortunately, it appears I could have three routing choices and none of them work:
1. Service Callouts only work with a static service name, not a dynamic one (so even if I had a for-each loop around a Service Callout action, it doesn't do me any good).
2. Dynamic Publish actions are asynchronous only
3. Dynamic Routing actions inside Route nodes work, except that only one can exist per proxy service.
Am I missing anything? Is there some way to get ALSB to accept dynamic synchronous invocation of multiple proxy services from one orchestration proxy service?
Meghan Pietila
Granite Consulting, Inc.
Minnesota

A way of Invoking a dynamically chosen proxy service (PS) synchronously could be the following.
Service Callout actions are synchronous, so ALSB will block in PS2 (PS=proxy service) when it does the invocation of PS1.
Assuming the following very simple scenario (I hope to have understood correctly your case):
OPS = orchestration proxy service
case1: OPS -> PS1 -> PS3 -> ...
case2: OPS -> PS1 -> PS2 -> ...
where each PSi calls one or more business service (I suppose that the business services called in each PSi are called in a predefined order), so what is changing from one case to another is the sequence of PSi to be called.
I've setup the following ALSB project:
- OPS proxy services
- PS1 .. PS4 proxy services
- a proxy called 'step'
- a xquery called 'routing'
The idea is to call, from OPS, another proxy (the 'step' proxy) in a synch way (service callout) passing the information of what proxy should be called dynamically.
In the 'step' proxy then I create the <route><service> XML fragment, for the Dynamic Route action. This <route><service> XML fragment will point to the configuration of yet another proxy service (PSx), that is the PSx that I want to call.
One limitation is that I assume that your OPS always calls for example 2 proxies which name is resolved dynamically.
About the xquery:
<routing>
<case name="1">
<node>PS1</node>
<node>PS3</node>
</case>
<case name="2">
<node>PS1</node>
<node>PS2</node>
</case>
</routing>
OPS performs the following steps:
- chooses what is the case: 1 or 2
- does 2 service callout to the proxy called 'step' passing each time the correct node to be called
$routing/case[@name=data($case)]/node[1]
$routing/case[@name=data($case)]/node[2]
In the 'step' proxy I do a dynamic publish to desidered PS:
<route xmlns="http://www.bea.com/wli/sb/context">
<service isProxy="true">{ $proxyToBeInvoked }</service>
</route>
where the proxyToBeInvoked variable is built from the node received by the caller.
I've used this approach in a solution currently under development but I've found some problems when I want to receive back in OPS the error raised by any PSi: I'm able to catch the error but I'm not able to receive back the detailed error like in an usual stack trace.
I hope that could be useful.
Regards
ferp

How to be able to view the proxy service's WSDL in the browser

Hello, I created a ALSB proxy service that I have been able to successfully access from a SOAP client. I exported the WSDL from the Project Explorer, Resources Block, Actions column, and it gave me this URL to hit the proxy service:
http://mymachine:7001/OneProxyServiceToOneBusinessService/DoubleItWSFromWL_PRSRV
No problem here. But when I try to access the WSDL from the browser (helpful for SOAP clients in generating the JAX-WS artifacts), using this URL:
http://mymachine:7001/OneProxyServiceToOneBusinessService/DoubleItWSFromWL_PRSRV?wsdl
I get this error HTML message back as a response:
"Error 405--Method Not Allowed
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.6 405 Method Not Allowed
The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource"
(Same error message if I omit the "?wsdl" at the end, BTW.)
I don't understand this message--what do I need to do to be able to view the proxy service's WSDL from the browser, or does ALSB not provide that option?
Thanks,
Glen

Click on the Proxy Service in your ALSB project to go to Proxy Service Configuration page. On this page, you will see an endpoint URI, something like /myservice. To get the wsdl in browser, use the URL like http://mymachine:7001/myservice?wsdl

ALSB 3.0 - Form of URL to obtain Proxy Service WSDL changed?

A quick 'technical' question that seems too dumb to raise as a support call, but cant find any discussion or details in docs, release notes etc.
There might be some subtle default which has changed or I've done some thing different and I just can't find it - likely:).
QUESTION: Has the way in which the WSDL is requested from a (Proxy) Web Service changed.
IN ALSB 2.6 and earlier:
http://localhost:7501/service/EchoStringService?WSDL
would return WSDL
IN ALSB 3.0
the same (or similar form after recreating the above service in ALSB 3.0 ) returns:
Error 405--Method Not Allowed
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.6 405 Method Not Allowed
The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.
Any advice would be appreciated
Thanks
Jim Nicolson

Sorry, found the answer but forgot to update this thread.
The ?WSDL mechanism fails if Enforce WS-I Interoperability is true for the Proxy Service.
While BEA support (and the docs relating to this flag) say this is by design (Only POST not GET is supported by WS-I) personally it seems to me that this rule should apply to operation invocation not a metadata inquiry but there you go...

ALSB 3.0: Problem with Nested Policies in Proxy Service WSDL

Hello,
I'm trying to implement client applications that consume Web Services.
In ALSB, i imported the WSDLs of the services, created business and proxy Services.
Creating web references in .NET and Netbeans is working well, as long as there is no security policy attached to the WSDLs of the proxy services.
When attaching a policy, ALSB nests it inside the WSDL:
<s0:Policy s1:Id="signMessage">
<wssp:Integrity SignToken="false">
<wssp:SignatureAlgorithm URI="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<wssp:CanonicalizationAlgorithm URI="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<wssp:Target>
and references it, where i want it to have. in this case it's in the request of the service:
<s2:input>
<s4:body use="literal"/>
<wsp:Policy>
<wsp:PolicyReference URI="#signMessage"/>
</wsp:Policy>
</s2:input>
The problem is, that neither .Net (C#) nor Netbeans (Java) correctly import and handle these policies. .Net even mentions in the generated code that the "Policy" element was not handled. So when running my applications, i logically get exceptions that no credentials/tokens or else were delivered from the client side. In general the mentioned IDEs that i'm using support the configuration of those security issues. But when not correctly parsing the WSDL from the Service Bus, they don't work.
I tried many ways to dodge this problem, but without success.
Manually writing policy Statements into the WSDL files is not what i'm searching for as a solution. I want it dynamically.
I hope i could describe my problem clear enough and to get a possible solution.
Thanks

Sorry, found the answer but forgot to update this thread.
The ?WSDL mechanism fails if Enforce WS-I Interoperability is true for the Proxy Service.
While BEA support (and the docs relating to this flag) say this is by design (Only POST not GET is supported by WS-I) personally it seems to me that this rule should apply to operation invocation not a metadata inquiry but there you go...

[ALSB] turning on/off logging/tracing for proxy services

Hi all,
do you have any snippet for turning on/off logging/tracing for proxy services using WLST or JMX ?
I've seen a previous thread about Enable/Disable Proxy Service using JMX and I'm looking for something similar.
Regards
ferp

Thanks, but I mean using WLST or JMX code and not by ALSB console
regards
ferp

Stuck Thread - JMS Business proxy Service (ALSB 2.5)

Hi All,
We are having a jms proxy service which uses a JMS Business Service to send messages to a jms queue on weblogic 8.1 sp6. The alsb domain runs on weblogic 9.2.The jms proxy service is made single threaded by configuring a suitable work manager.
Now and then, we get a stuck thread issue in production and the proxy service stops consuming the messaging off the jms queue in wls 9.2. These are the errors in the logs:
<[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1235437298516> <BEA-000337> <[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "695" seconds working on the request "weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl@5321caf", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-70 "[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, waiting, priority=1, DAEMON> {
-- Waiting for notification on: weblogic.rjvm.ResponseImpl@51961a5[fat lock]
jrockit.vm.Threads.waitForSignal(Native Method)
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Native Method)
weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:73)
^-- Lock released while waiting: weblogic.rjvm.ResponseImpl@51961a5[fat lock]
weblogic.rjvm.ResponseImpl.getTxContext(ResponseImpl.java:100)
weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
weblogic.jms.dispatcher.DispatcherImpl_816_WLStub.dispatchSyncTranFuture(Unknown Source)
weblogic.jms.dispatcher.DispatcherInteropAdapter.dispatchSyncTranFuture(DispatcherInteropAdapter.java:80)
weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:230)
weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncTran(DispatcherAdapter.java:51)
weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1047)
weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:670)
weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:455)
weblogic.jms.client.JMSProducer.send(JMSProducer.java:352)
weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:1009)
weblogic.deployment.jms.WrappedMessageProducer.send(WrappedMessageProducer.java:157)
com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:795)
com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:500)
com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:612)
jrockit.reflect.CompiledMethodInvoker.invoke0(Unknown Source)
jrockit.reflect.CompiledMethodInvoker.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
com.bea.wli.sb.transports.Util$1.invoke(Util.java:241)
$Proxy39.sendMessageAsync(Unknown Source)
com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:137)
com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:437)
com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:328)
com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:503)
com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:415)
stages.publish.runtime.PublishRuntimeStep.processMessage(PublishRuntimeStep.java:106)
com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:327)
com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:100)
com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:771)
com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:73)
com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:771)
com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:47)
com.bea.wli.sb.pipeline.Node.processMessage(Node.java:57)
com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:771)
com.bea.wli.sb.pipeline.Router.processMessage(Router.java:141)
com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:75)
com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:646)
com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:645)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:627)
com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:264)
com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.java:108)
weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:292)
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4060)
weblogic.jms.client.JMSSession.execute(JMSSession.java:4012)
weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4467)
weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
jrockit.vm.RNI.c2java(Native Method)
Any one know the root cause of this issue or ways to prevent this?
Also Is there a way to make the proxy service to reconsume messages off the queue without a server restart?
Thanks,
Atheek

Hi atheek, did you find the solution??
I already got the same/identic issue, do you mind giving me an aid?
Really thanks
Regards,
Mr.K

Schedule a Proxy Service in ALSB

Hi Dear,
<BR><BR>
I want to schedule my proxy service in ALSB.
It should run once in a day automatically.
<BR><BR>
Can I do this in ALSB????

I think that would be the responsability of the application invoking your proxy service. This could be useful:
http://e-docs.bea.com/wls/docs92/commonj/commonj.html

ALSB Business Service Call through corporate proxy

I would like to define an ALSB Business Service to make a http web service call to a business partner over the public internet. No problem normally we would just specify the appropriate URI in the Business Service.
This time, however, we need to go through a corporate proxy in the DMZ. How do I direct the Business Service to use the proxy? Can I use -Dhttp.proxyHost in the weblogic setDomainEnv.sh?

In the advances settings of your businiess service, you can define a proxy-server.
Or you can set the proxy server at JVM level
PROXY_HOST
PROXY_PORT
NON_PROXY_HOST
Marc
http://orasoa.blogspot.com

Question related to ALSB configuration of Proxy Service in ALBPM

Hi,
I happened to find "Proxy Service" as one of the supported types under "Oracle Service Bus" external resource configuration. However, I wasn't able to find any documentation related to this type.
I configured it hoping that this automatically create a proxy service for my Business Service.However, it doesn't seem to do so.
Can somebody explain where this feature could be used ?
Rudraksh

Rudraksh,
I'll try to explain better what I said about external resources.
Let's say you have a process and you need to invoke two services already published in your service bus. You can catalog (introspect) those services directly from the service bus. You'd go to a module in your catalog, select catalog component and choose 'service bus' as the type. This will connect to your service bus and show you the available projects and the available proxy services in each project. There you can choose the one you want to invoke and when the introspection is done you'll have some BPM Objects in your catalog to invoke that service. If you look under external resources you'll see two new definitions, a server definition (ip, port, etc.) and a service definition (endpoint URI).
Now imagine you've finished the development of your project and you want to test it in your test environment. You would export your project and publish it in a BPM Enterprise server. But in this environment you have another service bus for testing, and you want to use this one and not the one you used for development. You need to tell your process to invoke those services instead of the services in your development environment (maybe your own PC). One way to do this is to introspect each service again, recompile your project, export it and publish it again. But it's not very flexible and it's time consuming. This is why you have external resources. Once you've deployed a project in BPM Enterprise, you can go to the 'Process Administrator' web application and modify the definitions of your external resources. So in this example you'd simply look for your server definition and change the IP address and port to point to the service bus in your test environment. If the service has a different URI you can modify it in the service definition. You restart your engine and that's it, now your process will invoke the services in the service bus for testing. Something analogous to having your application's configuration in a properties file instead of hard-coded in your code.
Now about the 'Proxy Service' external resource, I think I got it wrong. My guess is that it's for the OBPM transport. There is a new 'native' transport for the BPM in the service bus. It has some advantages like speed, transaction propagation, etc. I understand it's based on RMI so this would be the way of specifying the URL and credentials for the 'initial context factory'. Maybe someone else can confirm this.
Cheers

ALSB Proxy Service

Similar Messages

Maybe you are looking for