Where is the Proxy Service deployed?

Hi
This is about the internals of the service bus.
I want to see the deployment unit that matches the Proxy I have created.
Where is it?
Where in the CONSOLE (not the sbconsole) can i see it deployed?
kind regards
kambiz

Proxy services except of jms transport are not deployed as standard j2ee deployment units - (ear, war, rar etc). Instead these deployment units are xml config files which will be understood only by the osb product j2ee applications. You will not be able separate individual proxy services from this.
Proxy services with jms transport are deployed as MDB's under the hood and you will be able to see these deployments under wls console --> Deployments with random names.

Similar Messages

Need JAVA API to list down all the Proxy Services in OSB Console 11g

Hi,
I need a java API to List down all the Proxy Services present in OSB Console for SOA 11g (11.1.1.5). I am in a situation where I cant use python script for the same.
any help will be much appreciated.
Thanks in Advance,
Ravi
Edited by: 899443 on Oct 1, 2012 4:13 AM

AFAIK it is proprietary.
What I do in a similar situation is to form XML for the services, package them into JAR the same way as an import JAR is packaged (creating ExportInfo resource, ...) and deploy with standard WSLT script. Works for simplest services only (direct proxies mostly) but I can also form security, alerts, throttling etc etc etc -- all in one shot.
Out of sheer interest, may I ask you a question? Why do you need to create OSB services from Java?
Vlad
http://vladimirdyuzhev.com

[svn:bz-trunk] 20976: bug fix BLZ 602 IPv6 address isn' t properly resolved when used in dynamic url in the proxy service

Revision: 20976
Revision: 20976
Author:   [email protected]
Date:     2011-03-28 09:20:34 -0700 (Mon, 28 Mar 2011)
Log Message:
bug fix BLZ 602 IPv6 address isn't properly resolved when used in dynamic url in the proxy service
checkintests pass
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/messages/HTTPMessage.java

Firstly, there's no such thing as Apache 9.3, there's Apache 1 (and subversions) and Apache 2 (and subversions). Your error message -
Oracle-HTTP-Server/1.3.28Shows you're using Apache 1.3.28
Secondly, I'm confused by your comment -
I do not have Apache 9.3 or higher but I think oracle should offer this in its companion CDOracle does offer the Apache server, if you're saying you didn't get it from Oracle then where did your Apache server come from?
Thirdly, I notice from your config file -
ErrorLog "|E:\oracle\product\10.1.0\Companion\Apache\Apache\bin\rotatelogs logs/error_log 43200"That you're piping the logs through rotatelogs, are you sure the logfiles haven't just been renamed?

Error while executing the proxy service

Hi,
I have a procedure which uses a database link to access my tables. And business service will invoke this procedure through JCA.
We have created a datasource (Driver : non - XA for Service connections). However, while executing the proxy service it gives me below error.
Do i need to change the type of driver. Can anybody please help me on this.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:com1="com:gm:vehicleengineering:engineeringworkorder:ewostatus:types:ewostatusschema:1:0" xmlns:com="com:gm:common:utilities:types:servicecontrol:1:0">
<com:ServiceControl>
<com:Service>EWOStatus</com:Service>
<com:Version>1.0</com:Version>
<com:ConsumerID>CID</com:ConsumerID>
<com:MessageID>MID</com:MessageID>
<com:SentTimeStamp>2008-09-28T21:49:45</com:SentTimeStamp>
</com:ServiceControl>
</soapenv:Header>
<soapenv:Body>
<soapenv:Body>
<com:ServiceFault xmlns:com="com:gm:common:utilities:types:servicefault:1:0">
<com:FaultCode>SOAFLT-999</com:FaultCode>
<com:FaultString>GeneralError</com:FaultString>
<com:FaultActor>Server</com:FaultActor>
<com:FaultDetail>Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/VehicleEngineering/EngineeringWorkOrder/EWOStatus/V1/WSDL/jcaEWOStatus_1_0_0 [ GetEWOStatus_ptt::GetEWOStatus(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'GetEWOStatus' failed due to: Interaction processing error.
Error while processing the execution of the SP_GETEWOSTATUS API interaction.
An error occurred while processing the interaction for invoking the SP_GETEWOSTATUS API. Cause: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Internal error: Cannot obtain XAConnection java.lang.ClassCastException: oracle.jdbc.driver.T4CConnection
     at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1684)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
     at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:126)
     at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:94)
     at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
     at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:327)
     at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:295)
     at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.reconnect(DatasourceAccessor.java:558)
     at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.reconnect(DatabaseAccessor.java:1437)
     at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.incrementCallCount(DatasourceAccessor.java:303)
     at oracle.tip.adapter.db.DBConnection.getTopLinkSQLConnection(DBConnection.java:335)
     at oracle.tip.adapter.db.transaction.DBTransaction.beginInternal(DBTransaction.java:126)
     at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:93)
     at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:248)
     at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:534)
     at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:257)
     at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
     at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
     at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
     at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:572)
     at sun.reflect.GeneratedMethodAccessor771.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
     at $Proxy142.sendMessageAsync(Unknown Source)
     at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:152)
     at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:560)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:501)
     at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:128)
     at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
     at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
     at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
     at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
     at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
     at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
     at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
     at com.bea.wli.sb.transports.CoLocatedMessageContext$1.run(CoLocatedMessageContext.java:164)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.security.Security.runAs(Security.java:61)
     at com.bea.wli.sb.util.security.SecurityUtils.runAs(SecurityUtils.java:58)
     at com.bea.wli.sb.transports.CoLocatedMessageContext.send(CoLocatedMessageContext.java:157)
     at com.bea.wli.sb.transports.http.wls.HttpTransportProvider.sendMessageAsync(HttpTransportProvider.java:215)
     at sun.reflect.GeneratedMethodAccessor771.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
     at $Proxy122.sendMessageAsync(Unknown Source)
     at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:152)
     at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:560)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:501)
     at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:128)
     at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
     at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
     at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
     at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
     at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
     at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
     at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
     at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
     at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
     at com.bea.wli.sb.transports.http.generic.RequestHelperBase$1.run(RequestHelperBase.java:152)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at com.bea.wli.sb.transports.http.generic.RequestHelperBase.securedInvoke(RequestHelperBase.java:151)
     at com.bea.wli.sb.transports.http.wls.HttpTransportServlet.service(HttpTransportServlet.java:127)
     at weblogic.servlet.FutureResponseServlet.service(FutureResponseServlet.java:25)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3686)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks,
Chandana

Make sure that you are using non-xa datasources and in DBAdapter outbound connection pool configuration provide the data source JNDI in "dataSourceName" property instead of "xADataSourceName" property. Update the DBAdapter after changing configuration.
Regards,
Anuj

In OSB 10,3, a Java Callout runs in the same thread of the Proxy Service?

Hello,
a I have a Java Callout within the Proxy Service, request pipeline.
Does it runs in the same thread of the Proxy?
If NOT,
which work manager is the Java Callout pinned to?
can I set the work manager I want?
Thank you,
regards
F.Costa

Thanks a lot.
Pointer to great info.
However doesn't mention Java Callout threading, nor the documentation does.
Anybody with a YES or NO, please...
F.Costa

Creating the proxy service

When I create the proxy service and choose to be created from the WSDL, I have two options for selecting the port and binding, could you explain the difference in choosing between the port or binding?
Thanks!

Hi,
Here is the difference.
If the service is based on a binding:
If the service is generated from binding Y in the WSDL resource, the effective WSDL defines a new service and port (<bindingname>QSService and <bindingname>QSPort). None of the ports defined in the WSDL resource are included in the effective WSDL.
There may be multiple ports in that WSDL associated with that binding. Each port can use a different URL. Therefore, the effective WSDL uses the binding but generates an artificial port from the configuration on the service for that binding. All other ports will be removed.
If the service is based on a port:
If the service is generated from port X in the WSDL resource, then port X is also defined in the effective WSDL. Any other ports defined in the WSDL resource are not included. Furthermore, if you base the proxy service on a WSDL port, the effective WSDL uses that port name. The binding is determined from the port, and in turn, the port type is determined from the binding.
The effective WSDL preserves any WS-Policies associated with the port defined in the resource WSDL.
The transport address specified in the port definition in the resource WSDL is never used as the address for a proxy service in the effective WSDL:For HTTP services, you must specify a transport address when configuring the transport in the Administration Console or the plug-in. That address is used in the port definition in the effective WSDL.The URL specified as the transport address for a proxy service is always relative to a path in an Oracle Service Bus domain, because Oracle Service Bus always hosts proxy services.
For SOAP-protocol-based WSDL services, the transport URI in the SOAP binding depends on the transport implementation. For standard transports (like HTTP and JMS), this value is as per the SOAP specification or another universally accepted value. For transports for which SOAP does not define a standard value, Oracle Service Bus sets one consisting of a predefined namespace with the transport ID appended at the end: http://www.oracle.com/transport/2007/05/.
There is one service element in the effective WSDL, and the port address contains a URL whose syntax and semantic is defined by the transport selected in the binding.
thanks,
Richa

Where is the addition services in settings?

Where is the additional services in settings

It's actually in the snapchat settings, not the phone settings, if that's what you are wondering

Where is the HP Service Cemter in INDIA

Where is the HP service center in Mumbai. I have purchased a cae\rtridge #57, a color cartridge, that is not being accepter by the HP printer model 1310/1315.
I want to know whether the cartridge is OK as I have had the printer attended to by a firm called Jitu Enterprises at Ghatkopar West Mumbai.
The B&W catridge #56 is working well.
Please inform me where I may go to have this problem attended to.
Thanking you,
Yours faithfully,
Philip

Hi,
Please use one near you:
http://welcome.hp.com/country/w1/en/contact_us.html
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Where is the customer service? Can not use my subscribtion on the second computer, it does not download keeps seeying buy buy buy

Where is the customer service? Can not use my subscribtion on the second computer, it does not download keeps seeying buy buy buy

Where is the customer service? Can not use my subscribtion on the second computer, it does not download keeps seeying buy buy buy

Where can the Enterprise Service Actions be downloaded?

Where can the Enterprise Service Actions be downloaded?

Christian,
you can download the Enterprise Service Actions when you go to [this Link|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/30369f2a-0b2b-2b10-8980-dcae7dc45e9b] and then go to page 7. In Page 7 you will find a link for downloading the JAR file. Direct [Download|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10d92d24-0a2b-2b10-73ab-e30944668ab2&overridelayout=true]!!.
Regards
Pedro

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

Proxy Service Deployment in OSB

Hi
I Have a requirement where i wnat to deploy same Proxy services with deferent versions. i dont wnat this to be reflected in my service name. so what i am doing is
creating deferent folders like v1, v2 and deploying the same service in bothe thse folders having endpoint URI deference in v1, v2.
i am bit curious to know if there is any impact to run time proxy instances as bothe of them are same. i just want to confirm before hand that there are no conflicts in run time behaviour of Proxy service.
any sugestions and answeres well appriciated.
thanks in advance
mr

Hi mr,
I don't think you'll be able to do this in the same OSB instance, although I may be mistaken. If both proxy services have the same name, then OSB will try to export both of them with the same name and there won't be any way to distinguish between them. Is the interface the same between the versions? What do you expect the behavior to be, i.e., which service will get called when Tuxedo calls the service?
Regards,
Todd Little
Oracle Tuxedo Chief Architect

OSB Proxy Service deployed in cluster environment FTP issue

Hi,
I have a OSB 11g proxy service based on a FTP JCA adapter. Here are the JCA settings:
<connection-factory location="JNDI_FILE_TOKEN" UIincludeWildcard="FILENAME_TOKEN"/>
<endpoint-activation portType="Get_ptt" operation="Get">
    <activation-spec className="oracle.tip.adapter.ftp.inbound.FTPActivationSpec">
      <property name="DeleteFile" value="true"/>
      <property name="MinimumAge" value="0"/>
      <property name="PhysicalDirectory" value="FOLDER_TOKEN"/>
      <property name="Recursive" value="false"/>
      <property name="PollingFrequency" value="30"/>
      <property name="FileType" value="ascii"/>
      <property name="IncludeFiles" value="FILENAME_TOKEN"/>
    </activation-spec>
</endpoint-activation>
When I deploy this proxy in a cluster (having 2 osb nodes) and place the very first file on FTP server. Both nodes pick the file simultaneously. But after this when I place files on FTP server only one node is picking file. Could you kindly tell where is the issue ?
Thanks and Regards

Hi Mani,
Do check the configuration of ProxyService-2 that it is enabled or not.
Do check the input payload of it, that ProxyService-1 is passing the correct payload to ProxyService-2.
Redeploy the ProxyService-2
There is some issue in your proxyService-2.
Regards,
Richa

(261936172) Q general Where are the Web Service source files?

Q <general> Where are the source files for a Web Service created
with WebLogic Workshop stored? How do I deploy the Web Service
on a different WebLogic Server? Is there a way to bundle the
Web Service project files manually to distribute them?
Is there a way to configure the directory where Workshop stores
the files?
ANSWER: (by Adam Fitzgerald, [email protected]) The .jws files are stored
in the project folder. This can be located on a local system, although by default
they are in c:\bea\wlserver700b\sample\workshop\applications. The Web Service
structure is understood by WLS 7.0 so by archiving the appropriate folder you
can transfer the Web Service in its entirety from one deployment to another.

Hi Dean,
In SharePoint 2013 Designer, the help files are online. They provide tons of general information regarding SharePoint Designer 2013. You can also find help files at:
http://technet.microsoft.com/en-us/library/jj219638%28office.15%29.aspx .
And find a great set of information on SPD 2013 and the new Workflow architecture here:
http://msdn.microsoft.com/library/office/jj163986(v=office.15)
More information, please refer to the link:
http://blogs.msdn.com/b/sharepointdesigner/archive/2012/08/07/welcome-to-sharepoint-designer-2013-customer-preview.aspx
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

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

Where is the Proxy Service deployed?

Similar Messages

Maybe you are looking for