OSB- Any Soap type Proxy service URL issue.

Hi,
There is an issue which i am facing and stuggling with it for sometime :(
Requirement - Using OSB 11g i had created 12 different services based on WSDLs provided by the client and all of them are working fine.However the client wanted a OSB router service on top of these 12 services which wil search for a string in the input xml and then route it to the required Proxy service (amongst the 12 services developed).
Problem- I was able to create the router Proxy service which was a Any Soap type of proxy service as i didnot have a WSDL for the router service.The router service is working fine when we test it from the OSB console.
When We tried to test the flow from SOAPUI (we used the WSDL of one of the 12 webservices developed and modified the uri to the uri of the router service ie. http://hostname:port/router/routerProxy) and it does not work.
The error returned is ERROR 404 nothing found by this name.
As The router proxy is a Any Soap kind of service i do not have the option of providing the client with the WSDL.
I would want to know how to i call this router service from an external source like SOAPUI so that the client is able to hit it.Also what would be the end point uri of this router service ?
Kindly Help
Thanks
Pranav Shah

Hi anuj,
Here you have the configuration
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:con="http://www.bea.com/wli/sb/pipeline/config" xmlns:con1="http://www.bea.com/wli/sb/stages/routing/config" xmlns:con2="http://www.bea.com/wli/sb/stages/config" xmlns:con3="http://www.bea.com/wli/sb/stages/transform/config">
<ser:coreEntry isProxy="true" isEnabled="false" isAutoPublish="false" isTracingEnabled="false">
<ser:description/>
<ser:binding type="abstract SOAP" xsi:type="con:AnySoapBindingType" isSoap12="false" xmlns:con="http://www.bea.com/wli/sb/services/bindings/config"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
<ser:pipelineMonitoringLevel>Pipeline</ser:pipelineMonitoringLevel>
</ser:monitoring>
<ser:reporting>true</ser:reporting>
<ser:logging isEnabled="true">
<ser:logLevel>debug</ser:logLevel>
</ser:logging>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
<ser:pipeline-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:pipeline-alerting>
<ser:ws-policy>
<ser:binding-mode>service-policy-bindings</ser:binding-mode>
<ser:policies/>
</ser:ws-policy>
<ser:throttling enabled="false">
<ser:capacity>0</ser:capacity>
<ser:maxQueueLength>0</ser:maxQueueLength>
<ser:timeToLive>0</ser:timeToLive>
</ser:throttling>
<ser:messageTracing enabled="false">
<ser:detailsLevel>Terse</ser:detailsLevel>
<ser:maxSize>8192</ser:maxSize>
</ser:messageTracing>
<ser:pageAttachments isEnabled="false"/>
<ser:transactions isRequired="false" sameTxForResponse="false"/>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>http</tran:provider-id>
<tran:inbound>true</tran:inbound>
<tran:URI>
<env:value>/testRouter/test</env:value>
</tran:URI>
<tran:inbound-properties/>
<tran:all-headers>true</tran:all-headers>
<tran:provider-specific xsi:type="http:HttpEndPointConfiguration" xmlns:http="http://www.bea.com/wli/sb/transports/http">
<http:inbound-properties/>
</tran:provider-specific>
</ser:endpointConfig>
<ser:router>
<con:flow>
<con:route-node name="RouteNode1">
<con:context/>
<con:actions>
<con3:ifThenElse>
<con2:id>_ActionId-9110389481588294027-8fc6726.12c833ed7e1.-7c90</con2:id>
<con3:case>
<con3:condition>
<con:xqueryText xmlns:con="http://www.bea.com/wli/sb/stages/config">fn:contains(fn-bea:serialize($body), 'ImsersoSiebelContactInsert')</con:xqueryText>
</con3:condition>
<con3:actions>
<con1:route>
<con2:id>_ActionId-9110389481588294027-8fc6726.12c833ed7e1.-7c8f</con2:id>
<con1:service ref="ServiWebEntrada/AltaExpediente/ProxyService/AltaExpedienteProxyService" xsi:type="ref:ProxyRef" xmlns:ref="http://www.bea.com/wli/sb/reference"/>
<con1:operation>ImsersoSiebelContactInsert</con1:operation>
<con1:outboundTransform/>
<con1:responseTransform/>
</con1:route>
</con3:actions>
</con3:case>
<con3:case>
<con3:condition>
<con:xqueryText xmlns:con="http://www.bea.com/wli/sb/stages/config">fn:contains(fn-bea:serialize($body), 'CreaContacto')</con:xqueryText>
</con3:condition>
<con3:actions>
<con1:route>
<con2:id>_ActionId-9110389481588294027-8fc6726.12c833ed7e1.-7c8b</con2:id>
<con1:service ref="ServiWebEntrada/CuidContact/ProxyService/CuidContactProxyService" xsi:type="ref:ProxyRef" xmlns:ref="http://www.bea.com/wli/sb/reference"/>
<con1:operation>CreaContacto</con1:operation>
<con1:outboundTransform/>
<con1:responseTransform/>
</con1:route>
</con3:actions>
</con3:case>
</con3:ifThenElse>
</con:actions>
</con:route-node>
</con:flow>
</ser:router>
</xml-fragment>
Regards
Pranav

Similar Messages

  • How to get server name and port of OSB server in a proxy service ?

    I need to get the server name and port of the OSB server inside a proxy service. How can I get this?

    You may use java callout for this purpose -
    How to get ServerName and ApplicationName in OSB (ALSB) ?
    Regards,
    Anuj

  • OSB: Text to SOAP in Proxy Service

    Hi All,
    I am trying to transform incoming text from a proxy service to SOAP business service. Is there a simple way to do it ? I am trying to use Replace and that does not seem to work and I have looked into MFL Transform, but that looks kind of complicated.
    Is there a way I can specify the incoming proxy request, $body and transform that to an element of a SOAP message?
    Any help would be great, thanks!
    --ML                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    Hi Patrick,
    Thanks for your reply. Currently I have a proxy service set as text for my request message type, I am trying to create a service that accepts HTTP POST and just receive some text in the body. I want to get the request and transform data in the body and pass that to a business service that receives a SOAP message.
    Can I still use xquery for that, any help on the configuration would be great, thanks!
    --ML                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • OSB: Retrieve list of proxy service/business service operations via OSB API

    Hi,
    I would like to retrieve the list of proxy service/business service operations using OSB API. I was able to retrieve References to all services on given server using examples from documentation (http://docs.oracle.com/cd/E13159_01/osb/docs10gr3/javadoc/com/bea/wli/sb/management/configuration/ALSBConfigurationMBean.html). I'm also able to retrieve the Reference to any given service I want.
    My problem is - what do I do next? I've read here[http://www.theserverlabs.com/blog/2012/03/14/alsbosb-customization-using-wlst/] , that one can use ServiceConfigurationMBean.
    But when I execute this code:
              ServiceConfigurationMBean servConfMBean = (ServiceConfigurationMBean) domainService
              .findService(
                        ServiceConfigurationMBean.NAME + "." + sessionName,
                        ServiceConfigurationMBean.TYPE,null);
    The servConfMBean object is null.
    I know that there might be some useful info in the statistics, but my proxys are enabled for monitoring, and therefore I'm unable to obtain statistics programatically.
    I've also learned that thereis a TransportManagerHelper.getWsdlDescription(ref) method. But it throws null pointer exception. I dont understand how to use it.
    Any help would be greatly appreciated.
    Veronica
    Edited by: Veronica on Apr 11, 2012 2:33 AM

    There is an API change from the OSB release 11.1.1.3 and later....
    There is a solution, but this is based on Java & JMX:
    See support on this note:
    WLST scripting needed for note [ID 1431254.1]

  • OSB -11g - Calling JMS Proxy Service in a stage

    Hi,
    When we createa JMS based proxy service, the proxy service keeps on polling the JMS Queue for any new messages arriving in the queue. But I do not want the proxy service to keep on polling the Queue. Instead I want to call the JMS Proxy Service in any stage (of any other Proxy Service) using a service callout. It means that I do not want the Queue to be polled always, instead the queue should be polled only when this JMS Proxy Service is invoked.
    Is it possible to do? If so, how?
    Thanks,
    Sanjay

    Hi Anuj,
    Following is my requirement:
    The producer wants to interact with us using Web Services. The input payload has some more values (username and password) apart from the HL7 data (base64 encoded) itself. I have to receive the input payload, authenticate the call and convert the HL7 encoded message into an XML and send it to the consumer.
    What have I done till now:
    1) I have created two Proxy Services PS1 and PS2
    2) Proxy Service (PS1) will be invoked by the producer.
    3) Then I get the username, password and data from the payload
    4) Populate the username and password in the SOAP Header and HL7 data in SOAP Body
    5) Call PS2 from PS1
    6) In PS2 I have configured Message Level Security to authenticate with the username and password
    7) After authentication I make a Java Callout to decode the base64 encoded HL7 data
    8) I now have written my own HL7 sender (Java code) which wraps the decoded HL7 data with MLLP requirements and then send it to the B2B server using a Socket (TCP connection). I do a Java Callout to this Java class.
    9) In B2B I have configured a RTP (Remote Trading Partner) which has a MLLP channel.
    10) I created a ADT message document and a ACK document
    11) I created two agreements between HTP and RTP (one agreement receives the HL7 data from the TRP using MLLP and another which sends the ACK to the RTP using MLLP channel)
    12) In the receiveing agreement I have configured a JMS channel (on the HTP side) becuase of which B2B receives the HL7 Pipe delimited data and translates it and then pushes the XML data into the JMS queue (which needs to be transformed to producer XML)
    13) I have also configured a JMS channel for the RTP which I am using in second agreement to get the acknowledgement. Because of this the ACK is placed in a JMS queue.
    I need to poll this JMS queue in order to send the ACK back to the producer (which I have to do in the response pipeline of PS2). Hence I wanted to pop the message from the JMS queue in the response pipeline and then send that message.
    Please advice if my approach is correct.
    Thanks,
    Sanjay
    Edited by: Sanjay Bharatiya on 17-Mar-2011 12:06 PM

  • How to access (any) soap / rest web services from widget

    Hi all,
    Is there an API, javascript library etc, which allows accessing (any) soap / rest webservices from widgets?
    I know I can access web services from sap j2ee with widget foundation, but I'm still not sure how to access "outside"
    web services.
    A blog entry about this topic would be greatly appreciated I think, not only by me.
    Regards,
    Ladislav

    As promised, below is the js lib source code. I did not see the attachement option, so you can just create a text file and save it with .js extension.
              function getHdrData( FuncName ) {
                return '<?xml version="1.0" encoding="UTF-8" ?>' +
                          '<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" ' +
                                             'xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ' +
                                             'xmlns:xs="http://www.w3.org/2001/XMLSchema">' +
                          '<SOAP-ENV:Header><sapsess:Session ' +
                                    'xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/">' +
                                    '<enableSession>true</enableSession></sapsess:Session>'+
                          '</SOAP-ENV:Header><SOAP-ENV:Body><ns1:' +
                          FuncName +
                          ' xmlns:ns1=\'urn:sap-com:document:sap:soap:functions:mc-style\'>';
              function addVar ( VarName, VarValue ) {
                return '<' + VarName + '>' + VarValue  + '</' + VarName + '>';
              function getFtrData( FuncName ) {
              return '</ns1:' + FuncName + '></SOAP-ENV:Body></SOAP-ENV:Envelope>';
              function setTable ( TblName, TblType) {
                   return '<' + TblName + ' xsi:type=\'ns1:' + TblType + '\'>';
              function closeTable ( TblName) {
                   return '</' + TblName + '>';
              function startEntry( ) {
                   return '<item>';
              function endEntry( ) {
                   return '</item>';
    So the following is the basic on how to use this library:
    * Set up SOAP envelope
    * Get the header data
    getHdrData( SOAP operation name )
    * If the web service set up the table and record start tags
    setTable( variable name, table type ) - Optional
    Set new record tag: startEntry() ? Optional
    * Set up the fieldname or variable name
    addVar( variable name, variable value )
    * Set up the table and record end tags
    endEntry() ? Optional
    closeTable( variable name ) ? Optional
    * Set up the footer SOAP envelope
    Set footer data: getFtrData(SOAP operation name )
    So hopefully that will help you consume SAP Published web services.

  • OSB: How to get proxy service name

    Hi all,
    Could anyone please tell me the way to get the proxy service name inside the message flow of OSB.
    Regards,
    Rakesh Ranjan.
    Edited by: Rakesh Ranjan on Oct 1, 2010 2:27 PM

    Inound context variable ($inbound) holds the value of service name and operation name being invoked. Use expression $inbound/@name to get service name and expression $inbound/ctx:service/ctx:operation/text() to get operation name being invoked.
    Remember that opeartion name will be there only for services which have operations (like a WSDL based service)
    Regards,
    Anuj

  • Custom tool error: Unable to import WebService/Schema. The object 'Settings' already contains a property 'Default' not of type Web Service Url

    Getting this error while  converting application from framework 3.5 to 4.0

    Why not just export the whole site ? Then import.
    example:
    You want all lists from http://sharepoint.ms.com/sites/it to be imported to http://sharepoint.ms.com/sites/it2
    Export the whole sites/it then import to sites/it2
    AJ MCTS: SP 2010 Configuration MCSA: Windows 7 If you find this post useful kindly please mark it as an answer :) TY

  • Calling a business service based on operation-soap action in Proxy service

    Hi,
    I have a requirement in which I have to call a business service based on operation-soap action defined in Proxy service wsdl.
    Like in below mentioned wsdl GetPartCostDelta and GetCurrencyList operations are there.But which ever operation I select,It just goes to one business service.
    Is there any way,I can route to some another business service based on the soap action
    proxy service WSDL
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:ewopcd="urn:com:gm:gpd:schema:ewopartcostdelta" xmlns:gen="urn:com:gm:gpd:schema:genericfault" xmlns:tns="urn:com:gm:gpd:services:ewopartcostdeltaservice" targetNamespace="urn:com:gm:gpd:services:ewopartcostdeltaservice">
         <wsdl:types>
              <xs:schema>
                   <xs:import namespace="urn:com:gm:gpd:schema:ewopartcostdelta" schemaLocation="ewocostdelta.xsd"/>
                   <xs:import namespace="urn:com:gm:gpd:schema:genericfault" schemaLocation="servicefault.xsd"/>
              </xs:schema>
         </wsdl:types>
         <wsdl:message name="EWOCurrencyListRequest">
              <wsdl:part name="CurrencyListRequest" element="ewopcd:EWOCostDeltaInput"/>
         </wsdl:message>     
         <wsdl:message name="EWOCurrencyListResponse">
              <wsdl:part name="CurrencyListResponse" element="ewopcd:EWOCurrencyList"/>
         </wsdl:message>     
         <wsdl:message name="EWOPartCostDeltaRequest">
              <wsdl:part name="PartCostDeltaRequest" element="ewopcd:EWOCostDeltaInput"/>
         </wsdl:message>
         <wsdl:message name="EWOPartCostDeltaResponse">
              <wsdl:part name="PartCostDeltaResponse" element="ewopcd:EWOCostDeltaResult"/>
         </wsdl:message>
         <wsdl:message name="EWOPartCostDeltaServiceFault">
              <wsdl:part name="PartCostDeltaServiceFault" element="gen:ServiceFault"/>
         </wsdl:message>
         <wsdl:portType name="EWOPartCostDeltaPortType">
              <wsdl:operation name="GetCurrencyList">
                   <wsdl:input name="EWOCurrencyListRequest" message="tns:EWOCurrencyListRequest"/>
                   <wsdl:output name="EWOCurrencyListResponse" message="tns:EWOCurrencyListResponse"/>
                   <wsdl:fault name="EWOPartCostDeltaServiceFault" message="tns:EWOPartCostDeltaServiceFault"/>
              </wsdl:operation>
              <wsdl:operation name="GetPartCostDelta">
                   <wsdl:input name="EWOPartCostDeltaRequest" message="tns:EWOPartCostDeltaRequest"/>
                   <wsdl:output name="EWOPartCostDeltaResponse" message="tns:EWOPartCostDeltaResponse"/>
                   <wsdl:fault name="EWOPartCostDeltaServiceFault" message="tns:EWOPartCostDeltaServiceFault"/>
              </wsdl:operation>          
         </wsdl:portType>
         <wsdl:binding name="EWOPartCostDeltaBinding" type="tns:EWOPartCostDeltaPortType">
              <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="GetCurrencyList">
                   <soap:operation soapAction="GetCurrencyList" style="document"/>
                   <wsdl:input>
                        <soap:body use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <soap:body use="literal"/>
                   </wsdl:output>
                   <wsdl:fault name="EWOPartCostDeltaServiceFault">
                        <soap:fault name="EWOCostDeltaServiceFault" use="literal"/>
                   </wsdl:fault>
              </wsdl:operation>
                        <wsdl:operation name="GetPartCostDelta">
                   <soap:operation soapAction="GetPartCostDelta" style="document"/>
                   <wsdl:input>
                        <soap:body use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <soap:body use="literal"/>
                   </wsdl:output>
                   <wsdl:fault name="EWOPartCostDeltaServiceFault">
                        <soap:fault name="EWOCostDeltaServiceFault" use="literal"/>
                   </wsdl:fault>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="EWOPartCostDeltaService">
              <wsdl:port name="EWOPartCostDeltaPort" binding="tns:EWOPartCostDeltaBinding">
                   <soap:address location="https://localhost/EWOPartCostDelta"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>

    Did you try using the Operational branching node of OSB?
    You have copy the operation name from the inbound variable and populate the SOAP Header with that value into the SOAPAction tag.I think this will work.
    Thanks,
    Prabu

  • OSB Proxy service accessible from client?

    Are non SOAP/WSDL OSB business services accessible from outside the OSB? Or are these only accessible from other services within the OSB?
    Thanks
    Edited by: magic1007 on Mar 18, 2010 7:50 AM

    Thanks!!
    Now, I Know I'm near, because using the proxy service URL:
    http://localhost:7001/PROJECT/ProxyServices/CompraDivisas_FIX
    I have an answer from the explorer and other from de console, both of them are asking me for the request message... So, how should I send that request?? I have 2 cases:
    1) I need to send as request a FIX string:
    8=HeaderBeginID9=40386842735=MTB1128=5.0SP149=PROJECT56=TargetCompanyID91=CandadoSeguridad34=795538142=525557=TargetSubID143=TargetLocID116=NONE144=0129=043=N52=20090311-17:06:16.720213=XML_DATA369=118219457811=11=CPADIVI581=144=12.0015=EUR55=USD54=160=20090411-14:35:4238=1152=1516=10040=1432=20100210-17:06:16.72010=PJVVHFdsicvr8f16
    2) My request is an XML:
    <?xml version="1.0" encoding="UTF-8"?>
    <QuoteRequestIM>
         <BeginString>BeginString</BeginString>
         <BodyLength>604607687</BodyLength>
         <MsgType>R</MsgType>
         <SenderCompID>SenderID</SenderCompID>
         <TargetCompID>PROJECT_ID</TargetCompID>
         <MsgSeqNum>1</MsgSeqNum>
         <SendingTime>2010-01-27T14:35:42</SendingTime>
         <QuoteReqID>QuoteRequestID</QuoteReqID>
         <RelatedSym>
              <Symbol>EUR/USD</Symbol>
              <Currency>EUR</Currency>
              <Legs>
                   <LegSymbol>EUR/USD</LegSymbol>
                   <LegQty>1000000.0</LegQty>
                   <LegSettlType>0</LegSettlType>
                   <LegSettlDate>2010-01-30</LegSettlDate>
                   <LegRefID>A0001</LegRefID>
              </Legs>
              <Legs>
                   <LegSymbol>EUR/USD</LegSymbol>
                   <LegQty>1000000.0</LegQty>
                   <LegSettlType>6</LegSettlType>
                   <LegSettlDate>2010-02-28</LegSettlDate>
                   <LegRefID>A0002</LegRefID>
              </Legs>
              <ExpireTime>2006-01-27T14:35:42</ExpireTime>
         </RelatedSym>
         <CheckSum>QBp0r7s7J_nsKe3p</CheckSum>
    </QuoteRequestIM>
    How, when & where can I introduce this request to my proxy service??
    Thanks a lot Anuj!!!
    WaLeX

  • OSB Proxy Service - ignore XML processing instructions (PIs)

    Hello,
    I've got a proxy service in OSB that takes any XML, transforms it, and passes it through to a business service. i.e. it just has a simple routing node containing something like:
    Route to [ BusinessServiceDB ] invoking [ merge ]
    Replace [ node contents ] of [  undefined XPath  ] in [ body ] with [ XQuery Resource... ]
    This works fine until the XML contains a processing instruction other than the standard XML version one; <?XML...?>. So if the first line (or first line after the XML version, if present) contains a PI (e.g. <?some-app-specific-instruction?>), then the proxy service passes nothing through to the Business Service.
    Well, I guess it assumes that the <?some-app-specific-instruction?> is the entire node contents, and so effectively passes through nothing that matches in the XQuery code...
    Is there a setting or easy way to make OSB globally ignore PIs? Or will I have to do something with the Replace, e.g. define the XPath or variable bindings differently?
    Cheers...

    Thanks, I will do that...once I've found out what our support ID is.
    The problem is easily repeatable in less than five minutes - all you have to do is create an 'Any XML' JMS proxy service (with all settings as defauts), and just have an empty route node in the message flow.
    Then all you do is try the test console with something like "<blah>test</blah>" as the payload; on the results you will see the correct XML inside the soapenv body when you expand: receiving request > Initial Message Context > $body. Then repeat the test with"<?something?><blah>test</blah>", which will only pass through the soapenv:Body tag with no contents.
    I presume this is not expected behaviour? i.e. OSB isn't meant to try the processing instruction, then pass through the results of that? I can't imagine it would...
    Anyway, as I say, I will raise the support request...but if anyone that is on a version above 10.3.1 has time to quickly run this test and let me know the results, I'd be really grateful.

  • Regarding proxy service

    Hi,
    Can a proxy service with "wsdl web service" as the service type be routed to a proxy service with "any xml" as the service type. In other words, can a proxy service based on wsdl be routed to any xml based proxy service?
    Another doubt : Is "any xml" proxy service same as local transport proxy service.

    This is possible. I am not sure if the message will keep the soap-envelope or not when sent to the business service.
    Gregory Haardt
    ALSB Prg. Manager
    [email protected]

  • OSB: Issue while testing OSB proxy service using SOAPUI

    Hi,
    I am trying to test an OSB proxy service using SOAPUI.
    The below are the steps i have followed in SOAPUI:
    1. File->New SOAPUI project
    2. Opens the dialog to create REST service
    3. Given service endpoint as: http://<osb servername>:<port>
    4. Opens dialog to create a REST resource
    5. Resource Path/EndPoint is the OSB proxy service end point.
    6. HTTP method = POST
    The proxy service accepts 'text' input so i have given Media Type as 'text/plain'
    But, when i give the request message and run the request. The request is not running. I am not seeing the processing symbol at the bottom right of the SOAP UI request. Whereas i am able to run other services.
    Kindly help me resolve this issue.
    Thanks,
    Kalpana.

    your problem:
    Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
    Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
    Loader: oracle.bpel.common:10.1.3
    Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
    Configuration: <code-source> in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    It happens when server is custom installed, try to reinstall it as full version and problem should disappear otherwise your need another full installation to retrieve and replace orabpel.jar file from (or maybe more)

  • OBPM BPM Studio support for SOAP 1.2 based Proxy services (OSB)

    Hi,
    I tried to import proxy services from OSB (as external resource). The proxy service is based on the SOAP 1.2 WSDL standard. When BPM studio introspective SOAP1.2 based proxy services, it is givng the following warninigs. Bacause of this i am unable to create a service object. Please help.
    Regards,
    Pandu
    Introspecting...
    downloading /sbresource?PROXY/RoutingAndMessagingService/proxy/OnRampService
    parsing /sbresource?PROXY/RoutingAndMessagingService/proxy/OnRampService
    [Warning] unknown tag 'header' from 'http://schemas.xmlsoap.org/wsdl/soap12/'.
    [Warning] unknown tag 'header' from 'http://schemas.xmlsoap.org/wsdl/soap12/'.
    checking /sbresource?PROXY/RoutingAndMessagingService/proxy/OnRampService
    parsing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdlmessages%2Futilityservices%2Froutingandmessagingservice%2FRoute
    analyzing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdlmessages%2Futilityservices%2Froutingandmessagingservice%2FRoute
    parsing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdlheaders%2FHeaderSchema
    analyzing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdlheaders%2FHeaderSchema
    parsing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdltypes%2Fcommon%2FHeaderTypes
    analyzing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdltypes%2Fcommon%2FHeaderTypes
    parsing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdltypes%2Fcommon%2FSimpleTypes
    analyzing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdltypes%2Fcommon%2FSimpleTypes
    http://www.michaelpage.com/wsdltypes/common/SimpleTypesv1.0 compiled
    http://www.michaelpage.com/wsdltypes/common/HeaderTypesv1.0 compiled
    http://www.michaelpage.com/wsdlheaders/Headerv1.0 compiled
    http://www.michaelpage.com/wsdlmessages/utilityservices/Routev1.0 compiled
    [Warning] The binding 'OnRampServiceSOAP' with type 's2:OnRampServicePort'is unsupported. Components will not be generaded for this binding..
    'http://www.michaelpage.com/wsdl/utilityservices/routingandmessagingservice/OnRampServicev1.0/' was parsed.
    Analyzing dependecies for module 'WS.OnRampService'...
    Analyzing dependecies for module 'WS.OnRampService'...
    Analyzing Components
    Storing Instrospected Types
    Introspection completed. Errors: 0, Warnings: 3.

    Pandu,
    OBPM 10g doesn't support SOAP 1.2 binding.
    Edited by: 4dyomi on Nov 20, 2009 11:41 AM
    Edited by: 4dyomi on Nov 20, 2009 11:42 AM

  • OSB Delete Entire Node (SOAP:header) in Proxy service

    Hi
    I am wanting to delete the SOAP:header node in the response in the SOAP proxy service.
    I am using the Delete action with the following settings
    Xpath: .
    In Variable: header
    All this is doing is deleting the contents of the "Header" node when I want to Delete the entire node.
    What am I doing wrong?
    Thanks in advance
    Edited by: cool.br33ze on 05-Feb-2013 01:40

    The reason for why I need to get rid of the SOAP:header is because the consuming application, SAP, is unable to handle a SOAP:header.If the consuming application is a SOAP client then there is no reason why it cannot handle it. If consuming application is not a SOAP client then better change the type of your proxy service to Any XML service or Messaging Type Service (with request and response type as XML)
    Regards,
    Anuj

Maybe you are looking for