How to consume MII transaction as a webservice

I have the WSDL for the MII transaction
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions targetNamespace="http://www.sap.com/xMII" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.sap.com/xMII" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
- <!--  Types
  -->
- <types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://www.sap.com/xMII">
- <s:complexType name="InputParams">
  <s:sequence id="InputSequence" />
  </s:complexType>
- <s:element name="XacuteRequest">
- <s:complexType>
- <s:sequence>
  <s:element maxOccurs="1" minOccurs="0" name="LoginName" type="s:string" />
  <s:element maxOccurs="1" minOccurs="0" name="LoginPassword" type="s:string" />
  <s:element maxOccurs="1" minOccurs="0" name="InputParams" type="s0:InputParams" />
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:complexType name="Rowset">
- <s:sequence>
  <s:element maxOccurs="unbounded" minOccurs="0" name="Row" type="s0:Row" />
  </s:sequence>
  <s:attribute name="Message" type="s:string" />
  </s:complexType>
- <s:complexType name="Row">
- <s:sequence id="RowSequence">
  <s:element maxOccurs="1" minOccurs="1" name="OutputXml" type="s:string" />
  </s:sequence>
  </s:complexType>
- <s:element name="XacuteResponse">
- <s:complexType>
- <s:sequence>
  <s:element maxOccurs="1" minOccurs="0" name="Rowset" type="s0:Rowset" />
  </s:sequence>
  </s:complexType>
  </s:element>
  </s:schema>
  </types>
- <!--  Messages
  -->
- <message name="XacuteSoapIn">
  <part element="s0:XacuteRequest" name="parameters" />
  </message>
- <message name="XacuteSoapOut">
  <part element="s0:XacuteResponse" name="parameters" />
  </message>
- <!--  Ports
  -->
- <portType name="XacuteWSSoap">
- <operation name="Xacute">
  <input message="s0:XacuteSoapIn" />
  <output message="s0:XacuteSoapOut" />
  </operation>
  </portType>
- <!--  Bindings
  -->
- <binding name="XacuteWSSoap" type="s0:XacuteWSSoap">
  <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="Xacute">
  <soap:operation soapAction="http://www.sap.com/xMII" style="document" />
- <input>
  <soap:body use="literal" />
  </input>
- <output>
  <soap:body use="literal" />
  </output>
  </operation>
  </binding>
- <!--  Service mapping
  -->
- <service name="XacuteWS">
- <port binding="s0:XacuteWSSoap" name="XacuteWSSoap">
  <soap:address location="http://<server>:53000/XMII/SOAPRunner/Default/Oilandgas/ForTagQuery" />
  </port>
  </service>
  </definitions>
I tried consuming this from ABAP WebDynpro from an ERP system (set up a Logical port and an HTTP connection).
I also tried consuming it from the browser by calling the URL
http://<server>:53000/XMII/SOAPRunner/Default/Oilandgas/ForTagQuery
It complained of 'Invalid username or password' HTTP 401
So, I added
http://<server>:53000/XMII/SOAPRunner/Default/Oilandgas/ForTagQuery&XacuteRequestLoginName=<user>&XacuteRequestLoginPassword=<password>
Still didn't work 'Invalid username or password'.
Any pointers where am I going wrong?
Regards,
Harish

Take a look at this thread.  It may give you more insight and links to other messages which will help.
[WebService Calls|Re: Troubleshooting webservice call / xMII-NetWeaver processing / Data Source]
If you solve your problem, please post your results here so others can benefit.  I would also like to know more about how you set it up on the ABAP side.
Good luck,
Mike

Similar Messages

  • How to consume a webservice from sap crm

    Hi All,
    How to consume and access an external webservice from sap crm?
    Suggest me.
    Regards,
    Sanjani
    Edited by: Sanjani on Dec 6, 2010 3:09 PM
    Edited by: Sanjani on Dec 10, 2010 1:08 PM

    Please check the wiki link mentioned below. It will help you to an extent.
    http://wiki.sdn.sap.com/wiki/display/CRM/CreatingWebServiceinSAP+CRM
    Rg,
    Harshit

  • Create MII transaction & MII Web Service and consume them in ABAP

    Hi,
    there is a document from Pradip Ray (SAP Labs India) published on SDN:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/208239ac-3161-2b10-f29a-abec6754942e
    He explains how to build a transaction in MII, expose it as a web service then consume it in an ABAP program by generating a ABAP consumer proxy for this service.
    I have done this and it works but the problems started when I tried to generate a second ABAP consumer proxy for a second web service build in MII.
    In the ABAP system , transaction SE80 then display proxy class:  ( e.g. ZMIICO_XACUTE_WSSOAP )
    then go to Properties tab , under sub-screen "External key" you can see the "Name: XacuteWSSoap".
    This is the web service port type name generated at MII and is always the same for all the MII web services. When you try to generate a second proxy for a second MII web service you get the following message  "A proxy already exists for object XacuteWSSoap (namespace http://www.sap.com/xMII) "
    This can be changed by editing the WSDL file but then another problem occurs which is related to the "InputParams" complex type. This tag gets generated with the same name for all the web services in MII.  The generation of the ABAP structure with the following name: INPUT_PARAMS will override the previous one .  This means that the previous ABAP proxy will not work anymore.
    Has any one experimented this ?
    Daryoush Delgari.
    This is the generated WSDL on MII:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <definitions targetNamespace="http://www.sap.com/xMII" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.sap.com/xMII" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
    - <!--  Types
      -->
    - <types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.sap.com/xMII">
    + <s:complexType name="InputParams">
    - <s:sequence id="InputSequence">
      <s:element maxOccurs="1" minOccurs="0" name="FromDate" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="PLANT" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="ToDate" type="s:string" />
      </s:sequence>
      </s:complexType>
    - <s:element name="XacuteRequest">
    - <s:complexType>
    - <s:sequence>
      <s:element maxOccurs="1" minOccurs="0" name="LoginName" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="LoginPassword" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="InputParams" type="s0:InputParams" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:complexType name="Rowset">
    - <s:sequence>
      <s:element maxOccurs="unbounded" minOccurs="0" name="Row" type="s0:Row" />
      </s:sequence>
      <s:attribute name="Message" type="s:string" />
      </s:complexType>
    - <s:complexType name="Row">
    - <s:sequence id="RowSequence">
      <s:element maxOccurs="1" minOccurs="1" name="Day" type="s:string" />
      <s:element maxOccurs="1" minOccurs="1" name="Item" type="s:string" />
      <s:element maxOccurs="1" minOccurs="1" name="Resource" type="s:string" />
      <s:element maxOccurs="1" minOccurs="1" name="WorkCenter" type="s:string" />
      <s:element maxOccurs="1" minOccurs="1" name="ShopOrder" type="s:string" />
      <s:element maxOccurs="1" minOccurs="1" name="OrderQty" type="s:long" />
      <s:element maxOccurs="1" minOccurs="1" name="Cured" type="s:long" />
      </s:sequence>
      </s:complexType>
    - <s:element name="XacuteResponse">
    - <s:complexType>
    + <s:sequence>
      <s:element maxOccurs="1" minOccurs="0" name="Rowset" type="s0:Rowset" />
      </s:sequence>
      </s:complexType>
      </s:element>
      </s:schema>
      </types>
    - <!--  Messages
      -->
    - <message name="XacuteSoapIn">
      <part element="s0:XacuteRequest" name="parameters" />
      </message>
    - <message name="XacuteSoapOut">
      <part element="s0:XacuteResponse" name="parameters" />
      </message>
    - <!--  Ports
      -->
    - <portType name="XacuteWSSoap">
    - <operation name="Xacute">
      <input message="s0:XacuteSoapIn" />
      <output message="s0:XacuteSoapOut" />
      </operation>
      </portType>
    - <!--  Bindings
      -->
    - <binding name="XacuteWSSoap" type="s0:XacuteWSSoap">
      <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    - <operation name="Xacute">
      <soap:operation soapAction="http://www.sap.com/xMII" style="document" />
    - <input>
      <soap:body use="literal" />
      </input>
    - <output>
      <soap:body use="literal" />
      </output>
      </operation>
      </binding>
    - <!--  Service mapping
      -->
    - <service name="XacuteWS">
    - <port binding="s0:XacuteWSSoap" name="XacuteWSSoap">
      <soap:address location="http://<host>:port/XMII/SOAPRunner/Default/Amrik/Wolves/WDPro/getCuresByPeriod" />
      </port>
      </service>
      </definitions>

    Hi Daryoush,
    Little surprise for you, I got the solution ;o)
    In fact, editing the WDSL file, you can change the parameter names which will be generated in Web Dynpro. You have to change the tag <complex type ...>.
    For example :
    <s:complexType name="InputParams">
    Could become :
    <s:complexType name="*Zs1*InputParams">
    and later in the code, you should reference the element appropriately
      <s:element maxOccurs="1" minOccurs="0" name="InputParams" type="s0:InputParams"/>
    should become :
       <s:element maxOccurs="1" minOccurs="0" name="InputParams" type="s0:*Zs1*InputParams"/>
    But take care to keep name="InputParams", it's the xlm name which will be used by MII to do the matching...
    Take care also that you have to do the same for output, that means ROW and ROWSET complex type...
    So, to be concrete, here are an example with in bold everything I changed against the original MII WDL file...
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions targetNamespace="http://www.sap.com/xMII" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.sap.com/xMII" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
        <!-- Types -->
        <types>
            <s:schema elementFormDefault="qualified" targetNamespace="http://www.sap.com/xMII">
                <s:complexType name="*Zs1*InputParams">
                    <s:sequence id="InputSequence">
                      <s:element maxOccurs="1" minOccurs="0" name="inputItem" type="s:string"/>
                      <s:element maxOccurs="1" minOccurs="0" name="inputPlant" type="s:string"/>
                      <s:element maxOccurs="1" minOccurs="0" name="inputSearchBy" s:long"/>
                </s:sequence>
                </s:complexType>
                <s:element name="XacuteRequest">
                    <s:complexType>
                        <s:sequence>
                            <s:element maxOccurs="1" minOccurs="0" name="LoginName" type="s:string"/>
                            <s:element maxOccurs="1" minOccurs="0" name="LoginPassword" type="s:string"/>
                            <s:element maxOccurs="1" minOccurs="0" name="InputParams" type="s0:*Zs1*InputParams"/>
                        </s:sequence>
                    </s:complexType>
                </s:element>
                <s:complexType name="*Zs1*Rowset">
                    <s:sequence>
                        <s:element maxOccurs="unbounded" minOccurs="0" name="Row" type="s0:*Zs1*Row"/>
                    </s:sequence>
                    <s:attribute name="Message" type="s:string"/>
                </s:complexType>
                <s:complexType name="*Zs1*Row">
                    <s:sequence id="RowSequence">
                    <s:element maxOccurs="1" minOccurs="1" name="Item" type="s:string"/><s:element maxOccurs="1" minOccurs="1" name="ItemDescription" type="s:string"/></s:sequence>
                </s:complexType>
                <s:element name="XacuteResponse">
                    <s:complexType>
                        <s:sequence>
                            <s:element maxOccurs="1" minOccurs="0" name="Rowset" type="s0:*Zs1*Rowset"/>
                        </s:sequence>
                    </s:complexType>
                </s:element>
            </s:schema>
        </types>
        <!-- Messages -->
        <message name="Xacute*Zs1*In">
            <part element="s0:XacuteRequest" name="parameters"/>
        </message>
        <message name="Xacute*Zs1*Out">
            <part element="s0:XacuteResponse" name="parameters"/>
        </message>
        <!-- Ports -->
        <portType name="Xacute*MyTest*">
            <operation name="Xacute">
                <input message="s0:Xacute*Zs1*In"/>
                <output message="s0:Xacute*Zs1*Out"/>
            </operation>
        </portType>
        <!-- Bindings -->
        <binding name="Xacute*MyTest*" type="s0:Xacute*MyTest*">
            <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
            <operation name="Xacute">
                <soap:operation soapAction="http://www.sap.com/xMII" style="document"/>
                <input>
                    <soap:body use="literal"/>
                </input>
                <output>
                    <soap:body use="literal"/>
                </output>
            </operation>
        </binding>
        <!-- Service mapping -->
        <service name="XacuteWS">
            <port binding="s0:XacuteMyTest" name="XacuteMyTest">
                <soap:address location="http://host/XMII/SOAPRunner/Development/WebServices/GetItems/getItemsTrx"/>
            </port>
        </service>
    </definitions>
    If you want a demo, you can come to my desk ;o)
    Edited by: Olivier Thiry on Mar 12, 2009 1:02 PM
    Damned, the bold tag seems not to work... So all my changes are between star (..)

  • How to Consume a WebService in JSP DynPage

    Hi Friends,
    We have created a Web Service and We want to Consume that in my JSP Dyn Page.
    Please let me know how to consume the Web Services that are created.
    I am having a WSDL File and need to consume it in Enterprise Portal Applications.
    Thanks in Advance.
    Regards,
    Palani

    Hi Palani,
       Create a Portal Application and access the External Web Service (Say for example, http://api.google.com/GoogleSearch.wsdl ).  Create the Portal Application Object -> Portal Web Service -> Portal WebService from wsdl file -> Client Side -> Enter the Wsdl file as http://api.google.com/GoogleSearch.wsdl -> Select the methods to expose -> Enter the service name, Alias and package name should be a unique one. and finish.
    Create bean to set the values.
    In your JSPDynpage Component enter the following code:
    public void doInitialization(){
       YourServiceName obj=(YourServiceName) PortalRuntime.getRuntimeResources().getService(YourServiceName.KEY);
      MyBean beanObj = new MyBean();
      beanObj.setterMethod(obj.calltheMethodinWSDL());
    And in your JSP page, call the bean getter method.
      It's overview only, you can do it.
    Regards,
    Venkatesh. K

  • How to read the tag values sent by PCo to MII transaction

    Hi everybody,
    I have an Agent created inside PCo and its listening to a data server. I have also created a notification object which triggers my MII Transaction (after certain condition is getting fulfilled).
    Now, I want to pass certain values from PCo to MII using the notification object. For this I have tried 2 options:
    1. I defined one input parameter in transaction of type 'XML'. But this did not work. When I used 'Tracer' to check the received values, it showed empty.
    2. Since XML variable did not work, I tried with 'String' variable. It worked but the entire input data was in 'String' format.
    Actually I used XML_Saver to save the string and given filename as '.xml'. When I opened that xml file, it was looking like this:
    <<unable to write XML here>>
    Considering the above 2nd option, how can I extract the particular 'Tag' values from XML string. Since the string is not in the format of 'Rowset/Row/Row', I cannot specifically assign/map those tag values to any other variable inside MII transaction.
    ===========

    Hi, I was trying to post the xml string. It was not possible yesterday (because, SDN editor has converted xml part into some irregular string).
    Now, I am trying to post the string by removing the special characters. Please try to understand it.
    Now, my question is how to retrieve the CDATA value 5599999999 using xpath. Please help.
    NotificationMessage
    Body
    Values
    Expression1 type xsd string
    CDATA 5599999999
      /Expression1
      /Values
      /Body
      Faults /
      /NotificationMessage

  • How to consume json webservice in abap?

    hello  every one please help me how to consume json format webservice in abap.
    i am new in abap please help me out .
    Thanks&Regards
    ~Ahmad

    hi check this,
    First create a web service in SAP. The blog by Uwe Kunath descibes this clearly. Then create an Xcode project and use the ASIHTTPRequest wrapper to connect to the web service. Parse the response with the KissXML parser. A more out of the box solution is NetWeaver Gateway. It also let you use SAP web services but it also generates iOs code for you. SAP just released a trial version in de download section.
    Example of ASIHTTPRequest
    - (void)getFlightData:(NSString *) selectedDate {
         NSURL *url = [NSURL URLWithString:@"http://abap.sapdev.nl:8000/sap/resources/flights/from/%/to/%/date/20110128?sap-client=001"];
         ASIHTTPRequest *request = [ASIHTTPRequest requestWithURL:url];
         [request setUsername:@"BCUSER"];
         [request setPassword:@"minisap"];
         [request startSynchronous];
         NSError *error = [request error];
         if (!error) {
              NSString *response = [request responseString];
              [self parseXML:response];
    Example of KissXML
    -(void)parseXML:(NSString*)source {
         NSError *error = nil;
         DDXMLDocument *theDocument = [[DDXMLDocument alloc] initWithXMLString:source options:0 error:&error];
         NSArray *results = [theDocument nodesForXPath:@"/asx:abap/asx:values/TAB/BAPISFLDAT" error:&error];
         for (DDXMLElement *flightdetail in results) {
              NSString *airlineid =   [[flightdetail elementForName:@"AIRLINEID"] stringValue];
              NSString *airline =     [[flightdetail elementForName:@"AIRLINE"] stringValue];

  • How to consume REST WebService using Axis2 in Adobe CQ5.5

    Hi All,
        How to consume REST WebService using Axis2 in Adobe CQ5.5 ?
    Please help me with this.Thanks very much for your help.
    Thanks & Regards,
    Kumar

    We had enough trouble getting the "osgi compliant" Axis2 library to run in OSGI without spooky failures that we ended up re-writing everything utilizng JAX-WS. JAX-WS is present in the underlying JDK, you just need to create an OSGI fragment bundle that exposes these classes from the JDK. So basically a bundle that just exports:
    com.sun.xml.ws,
                                    com.sun.xml.ws.addressing,
                                    com.sun.xml.ws.addressing.model,
                                    com.sun.xml.ws.addressing.v200408,
                                    com.sun.xml.ws.api,
                                    com.sun.xml.ws.api.addressing,
                                    com.sun.xml.ws.api.client,
                                    com.sun.xml.ws.api.fastinfoset,
                                    com.sun.xml.ws.api.handler,
                                    com.sun.xml.ws.api.message,
                                    com.sun.xml.ws.api.message.stream,
                                    com.sun.xml.ws.api.model,
                                    com.sun.xml.ws.api.model.soap,
                                    com.sun.xml.ws.api.model.wsdl,
                                    com.sun.xml.ws.api.pipe,
                                    com.sun.xml.ws.api.pipe.helper,
                                    com.sun.xml.ws.api.server,
                                    com.sun.xml.ws.api.streaming,
                                    com.sun.xml.ws.api.wsdl.parser,
                                    com.sun.xml.ws.api.wsdl.writer,
                                    com.sun.xml.ws.binding,
                                    com.sun.xml.ws.client,
                                    com.sun.xml.ws.client.dispatch,
                                    com.sun.xml.ws.client.sei,
                                    com.sun.xml.ws.developer,
                                    com.sun.xml.ws.developer.servlet,
                                    com.sun.xml.ws.encoding,
                                    com.sun.xml.ws.encoding.fastinfoset,
                                    com.sun.xml.ws.encoding.soap,
                                    com.sun.xml.ws.encoding.soap.streaming,
                                    com.sun.xml.ws.encoding.xml,
                                    com.sun.xml.ws.fault,
                                    com.sun.xml.ws.handler,
                                    com.sun.xml.ws.message,
                                    com.sun.xml.ws.message.jaxb,
                                    com.sun.xml.ws.message.saaj,
                                    com.sun.xml.ws.message.source,
                                    com.sun.xml.ws.message.stream,
                                    com.sun.xml.ws.model,
                                    com.sun.xml.ws.model.soap,
                                    com.sun.xml.ws.model.wsdl,
                                    com.sun.xml.ws.org.objectweb.asm,
                                    com.sun.xml.ws.protocol.soap,
                                    com.sun.xml.ws.protocol.xml,
                                    com.sun.xml.ws.resources,
                                    com.sun.xml.ws.server,
                                    com.sun.xml.ws.server.provider,
                                    com.sun.xml.ws.server.sei,
                                    com.sun.xml.ws.server.servlet,
                                    com.sun.xml.ws.spi,
                                    com.sun.xml.ws.streaming,
                                    com.sun.xml.ws.transport,
                                    com.sun.xml.ws.transport.http,
                                    com.sun.xml.ws.transport.http.client,
                                    com.sun.xml.ws.transport.http.server,
                                    com.sun.xml.ws.transport.http.servlet,
                                    com.sun.xml.ws.util,
                                    com.sun.xml.ws.util.exception,
                                    com.sun.xml.ws.util.localization,
                                    com.sun.xml.ws.util.pipe,
                                    com.sun.xml.ws.util.xml,
                                    com.sun.xml.ws.wsdl.parser,
                                    com.sun.xml.ws.wsdl.writer,
                                    com.sun.xml.ws.wsdl.writer.document,
                                    com.sun.xml.ws.wsdl.writer.document.http,
                                    com.sun.xml.ws.wsdl.writer.document.soap,
                                    com.sun.xml.ws.wsdl.writer.document.soap12,
                                    com.sun.xml.ws.wsdl.writer.document.xsd,
                                    com.sun.xml.internal.bind,
                                    com.sun.xml.internal.bind.v2,
                                    com.sun.xml.internal.ws,
                                    com.sun.xml.internal.ws.addressing,
                                    com.sun.xml.internal.ws.addressing.model,
                                    com.sun.xml.internal.ws.addressing.v200408,
                                    com.sun.xml.internal.ws.api,
                                    com.sun.xml.internal.ws.api.addressing,
                                    com.sun.xml.internal.ws.api.client,
                                    com.sun.xml.internal.ws.api.fastinfoset,
                                    com.sun.xml.internal.ws.api.handler,
                                    com.sun.xml.internal.ws.api.message,
                                    com.sun.xml.internal.ws.api.message.stream,
                                    com.sun.xml.internal.ws.api.model,
                                    com.sun.xml.internal.ws.api.model.soap,
                                    com.sun.xml.internal.ws.api.model.wsdl,
                                    com.sun.xml.internal.ws.api.pipe,
                                    com.sun.xml.internal.ws.api.pipe.helper,
                                    com.sun.xml.internal.ws.api.server,
                                    com.sun.xml.internal.ws.api.streaming,
                                    com.sun.xml.internal.ws.api.wsdl.parser,
                                    com.sun.xml.internal.ws.api.wsdl.writer,
                                    com.sun.xml.internal.ws.binding,
                                    com.sun.xml.internal.ws.client,
                                    com.sun.xml.internal.ws.client.dispatch,
                                    com.sun.xml.internal.ws.client.sei,
                                    com.sun.xml.internal.ws.developer,
                                    com.sun.xml.internal.ws.encoding,
                                    com.sun.xml.internal.ws.encoding.fastinfoset,
                                    com.sun.xml.internal.ws.encoding.soap,
                                    com.sun.xml.internal.ws.encoding.soap.streaming,
                                    com.sun.xml.internal.ws.encoding.xml,
                                    com.sun.xml.internal.ws.fault,
                                    com.sun.xml.internal.ws.handler,
                                    com.sun.xml.internal.ws.message,
                                    com.sun.xml.internal.ws.message.jaxb,
                                    com.sun.xml.internal.ws.message.saaj,
                                    com.sun.xml.internal.ws.message.source,
                                    com.sun.xml.internal.ws.message.stream,
                                    com.sun.xml.internal.ws.model,
                                    com.sun.xml.internal.ws.model.soap,
                                    com.sun.xml.internal.ws.model.wsdl,
                                    com.sun.xml.internal.ws.org.objectweb.asm,
                                    com.sun.xml.internal.ws.protocol.soap,
                                    com.sun.xml.internal.ws.protocol.xml,
                                    com.sun.xml.internal.ws.resources,
                                    com.sun.xml.internal.ws.server,
                                    com.sun.xml.internal.ws.server.provider,
                                    com.sun.xml.internal.ws.server.sei,
                                    com.sun.xml.internal.ws.spi,
                                    com.sun.xml.internal.ws.streaming,
                                    com.sun.xml.internal.ws.transport,
                                    com.sun.xml.internal.ws.transport.http,
                                    com.sun.xml.internal.ws.transport.http.client,
                                    com.sun.xml.internal.ws.transport.http.server,
                                    com.sun.xml.internal.ws.util,
                                    com.sun.xml.internal.ws.util.exception,
                                    com.sun.xml.internal.ws.util.localization,
                                    com.sun.xml.internal.ws.util.pipe,
                                    com.sun.xml.internal.ws.util.xml,
                                    com.sun.xml.internal.ws.wsdl.parser,
                                    com.sun.xml.internal.ws.wsdl.writer,
                                    com.sun.xml.internal.ws.wsdl.writer.document,
                                    com.sun.xml.internal.ws.wsdl.writer.document.http,
                                    com.sun.xml.internal.ws.wsdl.writer.document,
                                    com.sun.xml.internal.ws.wsdl.writer.document.soap,
                                    com.sun.xml.internal.ws.wsdl.writer.document.soap12,
                                    com.sun.xml.internal.ws.wsdl.writer.document.xsd,
                                    com.sun.xml.internal.messaging.saaj.soap

  • How to consume J2EE webservice in Oracle BPEL

    Dear All,
    Can any one please tell me that how to consume J2EE web service in Oracle BPEL. What is local registry. How am able to register my web service in to the local registry. Please suggest me.
    Thanks,
    Rajesh

    Hi,
    What IDE are you using?, for example with Eclipse i used WSDL2JAVA plugin in this way i converted the WSDL in java classes easily. Depending your development environment you can use different tools that makes easier the integration using the WSDL.
    Regards.

  • How Web Services support transactions ?

    Hello,
    I have this questions:
    - Web services support statefull?
    - There is some specification about 2PhaseCommit for Web Services?
    - How Web services handle transactions (commit, rollback)?
    - How can I handle commit across multiple systems (using web services)?
    There are standards that support this topics?
    Best regards,
    Luis Carlos

    Yes and no. <a href="http://www.w3.org/Protocols/rfc2109/rfc2109.txt">rfc2109</a> . This means that cookies provide a kind of session and therefore state, which can be hold on server side.
    SAP ABAP ERP holds session:
    <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/b7/d7baaf1481a349ab723e3acd7334b3/frameset.htm">Providing and Consuming Web Services</a>
    "WSDLs - There are two kinds of WSDLs – Standard and SAP WSDL. The standard WSDL is provided for those users who will use tools from other vendors to create clients. For SAP users, there is an extended SAP WSDL. This is an extended version of WSDL and can be parsed using SAP tools (SAP Proxy Generator), thus providing information about additional Web service requirements such as authentication, session, and so on."
    for me is also the technical implementation - how is the webservice session managed on server and on client -  not totally clear. If someone can help me to find exaxct technical details. Unfortenately I also always used it (esp. with Web Dynpro) without thinking about details.

  • How to consume a web service provided by third party system from SAP system

    Hi Friends,
    Could any of you provide me a clear picture on how to consume a web service from SAP system and is provided by a third party system?
    Do we get an URL to create a client proxy for consuming the web service?
    Thanx in advance,
    Ram

    Hi Ram,
    of course you cannot supply the WSDL URL. Inside the WSDL (just view it in your browser) you find (usually but not necessary) towards the end something like
    <soap:address location="http://www.weather.gov/forecasts/xml/SOAP_server/ndfdXMLserver.php"/>
    which is the actual adress of the service.
    An example service can be found here:
    <a href="http://www.weather.gov/xml/">National Digital Forecast Database</a>
    containing the WSDL URL at
    <a href="http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl">this address</a>.
    You might also want to browse for the amazon webservices which allow you to embed queries against amazon into your application.
    have fun,
    anton

  • Error while calling MII transaction as web service from ABAP

    Hello Experts,
    I want to call a MII transaction from ABAP program, as a web service.
    Following is output of http://<<server>>:50000/XMII/SOAPRunner/TAG_TRX  (TAG_TRX is name of my transaction).
      <?xml version="1.0" encoding="UTF-8" ?>
    - <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.sap.com/xMII" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://www.sap.com/xMII">
    - <!--  Types
      -->
    - <types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.sap.com/xMII">
    - <s:complexType name="InputParams">
    - <s:sequence id="InputSequence">
      <s:element maxOccurs="1" minOccurs="0" name="WEIGHT" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="BATCHID" type="s:string" />
      </s:sequence>
      </s:complexType>
    - <s:element name="XacuteRequest">
    - <s:complexType>
    - <s:sequence>
      <s:element maxOccurs="1" minOccurs="0" name="LoginName" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="LoginPassword" type="s:string" />
      <s:element maxOccurs="1" minOccurs="0" name="InputParams" type="s0:InputParams" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:complexType name="Rowset">
    - <s:sequence>
      <s:element maxOccurs="unbounded" minOccurs="0" name="Row" type="s0:Row" />
      </s:sequence>
      <s:attribute name="Message" type="s:string" />
      </s:complexType>
    - <s:complexType name="Row">
      <s:sequence id="RowSequence" />
      </s:complexType>
    - <s:element name="XacuteResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element maxOccurs="1" minOccurs="0" name="Rowset" type="s0:Rowset" />
      </s:sequence>
      </s:complexType>
      </s:element>
      </s:schema>
      </types>
    - <!--  Messages
      -->
    - <message name="XacuteSoapIn">
      <part element="s0:XacuteRequest" name="parameters" />
      </message>
    - <message name="XacuteSoapOut">
      <part element="s0:XacuteResponse" name="parameters" />
      </message>
    - <!--  Ports
      -->
    - <portType name="XacuteWSSoap">
    - <operation name="Xacute">
      <input message="s0:XacuteSoapIn" />
      <output message="s0:XacuteSoapOut" />
      </operation>
      </portType>
    - <!--  Bindings
      -->
    - <binding name="XacuteWSSoap" type="s0:XacuteWSSoap">
      <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    - <operation name="Xacute">
      <soap:operation soapAction="http://www.sap.com/xMII" style="document" />
    - <input>
      <soap:body use="literal" />
      </input>
    - <output>
      <soap:body use="literal" />
      </output>
      </operation>
      </binding>
    - <!--  Service mapping
      -->
    - <service name="XacuteWS">
    - <port binding="s0:XacuteWSSoap" name="XacuteWSSoap">
      <soap:address location="http://<<server>>:50000/XMII/SOAPRunner/TAG_TRX" />
      </port>
      </service>
      </definitions>
    Now, when I am using http://<<server>>:50000/XMII/SOAPRunner/TAG_TRX to create a Enterprise Service in SAP (i.e. SE80 transaction-> Create Enterprise Service-> Service Consumer-> URL/HTTP Destination-> URL ... I am getting following error.
    Incorrect value: Entity "<<document>>"(5 /93 ). unexpected symbol: '<'     
    But, whenever I am using the same URL in MII BLS, it does not give any error. It correctly shows all input and output parameters.
    Please help me to resolve this issue.
    Regards
    Neeta.

    Now, I am able to create the Web Service in SAP and it is now showing the respective class, attribute and methods to execute this web service (web service to call MII transaction).
    But when I am calling it from ABAP (a simple Web Dynpro for ABAP method), it is showing me the following error:
    Error (id=GET_BUSINESS_SYSTEM_ERROR): An error occurred when determining the business system (LD_ERROR)
    Thought this error is coming from ABAP program, but I am sure that this is related to some configuration at SAP level. (Let me inform you that there are two different servers for SAP Web Dynpro ABAP and SAP MII.
    Please help.
    Thanks in advance.

  • How to consume Web Services form ABAP ?

    Hi,
    Please advise how to consume web services from ABAP Code ? is there any automatic generating proxy class in order to consume web services ?
    I am using NW 7.0 SP15
    Thank You and Best Regards
    Fernand Lesmana

    Hi Fernand,
    chk out for this link
    Consume an ABAP Webservice (WAS 620) from .Net
    Send SMS to India from ABAP
    working web service from ABAP
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a4433436-0301-0010-f2a9-9281ad574054
    Regards
    Sampath

  • How to Consume web service in Adobe live cycle

    Hi Experts,
    I created a web service from FM and trying to consume that in Adobe live cycle. My problem is:
    1. I don't know how can I test this webservice layout?
    Could you please provide me the steps on how to consume it properly and how to test it becuase for me its not giving any response back.
    I will appreciate if you can send a step by step document at tyagi.sandeep10atgmaildotcom
    Regards,
    Sandeep
    Edited by: sandeep tyagi on Oct 16, 2008 1:36 AM
    Edited by: sandeep tyagi on Oct 16, 2008 1:37 AM

    Hi Sandeep,
    Please go through this pdf. It will help you to integrate web service in adobe form.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/148ec26e-0c01-0010-e488-decaafae3b26
    Thanks & Regards
    Sagar Ingalwar
    Edited by: Sagar Ingalwar on Oct 24, 2008 9:29 AM

  • How to consume web service in Agentry in SMP 3.0

    Dear All , I am using web service in Agentry to retrive data but could not able to fetch it . I have made connection with HTTP-XML for consuming webservices. and also give proper information in Agentry.ini files Ex : [HTTPXML-2] name=HTTP-XML Back End authenticationCertificateStore=MY authenticationCertificateStorePassword= authenticationCertificateStorePasswordEncoded=false autoDequote=true ;baseURL=http://localhost:81 baseURL=http://sapes1.sapdevcenter.com:8080/sap/opu/odata/iwbep/gwdemo/ basicAuthenticationPassword=123456 basicAuthenticationPasswordEncoded=false basicAuthenticationUserID=P1466405733 constantsFile=httpxml_sd.ini enableAuthentication=false enablePreviousUserAuthentication=false httpConnectTimeout=300 httpReceiveTimeout=300 httpResolveTimeout=300 httpSendTimeout=300 listenOn= timeout=300 timeZoneName= useSSL=false xmlAllowXSLTScript=true xmlNamespaces= xmlResolveExternals=true xmlValidateOnParse=true for more information i have attached agentry XML screen shot as well . Can you please guide me how to consume web services in Agentry correct way ? Note : Currently i am using standard netweaver demo web services . Thanks & Regards ,   Kunal Varaiya
    Tags edited by: Michael Appleby

    The XML Steps URL will be added to the Agentry.ini BaseURL.  So you dont' need the full URL on the step.
    So when Agentry Runs the step to call the backend it will go:
    <BaseURL>/<Step's URL>
    This way if you need to change the base URL, IE, going from Dev to QA to Production Server you only need to change the Base, and not go into every step and update it.
    URL: This attribute contains the URL to which the Agentry Server will make a request. This value will be appended to the value configured as the base URL for the HTTP-XML system connection. This base URL is configured within the HTTP-XML system connection configuration options for the Agentry Server. Proper use of both this base URL option and the URL entered in the requests of the step definitions can support portability for the application, with the base URL being the implementation-specific portion and the step’s URL being the portion not likely to change for the same back end system from one implementation to the next.
    http://help.sap.com/saphelp_smp303sdk/helpdata/en/7c/143d5d70061014b323be16eb0b0a77/frameset.htm 
    Stephen

  • MII transaction as Web service integration

    Hi MII's transaction can be called as WS but it has its own format. We have a system to integrate and this system should call MII's transaction. However the WS interface of the system is inflexible (it cannot be change, but has a very simple structure). So I just want to know any idea how we could change MII in order to adapt to the data structure .

    Now, I am able to create the Web Service in SAP and it is now showing the respective class, attribute and methods to execute this web service (web service to call MII transaction).
    But when I am calling it from ABAP (a simple Web Dynpro for ABAP method), it is showing me the following error:
    Error (id=GET_BUSINESS_SYSTEM_ERROR): An error occurred when determining the business system (LD_ERROR)
    Thought this error is coming from ABAP program, but I am sure that this is related to some configuration at SAP level. (Let me inform you that there are two different servers for SAP Web Dynpro ABAP and SAP MII.
    Please help.
    Thanks in advance.

Maybe you are looking for

  • Convertion of Smart form to pdf and sending mail to vendor for Invoice

    Hi All... now I am getting the output form of Invoice by the T-code  VF02 here Im using Zreport & Zform... my requirment is to convert smartform output to PDF and send as an e-mail attachment on my Existing report where I  use the FM - CONVERT_OTF_2_

  • Qosmio F30-127: How to use SD card - no SD card drive icon

    Could some one tell how to use SD in F30-127. I was trying to get picture from my SD card. I inserted into slot but no Drive ICON was displayed

  • File Upload 7.0

    Dear all, I have created a planning area using BPS0. I have create da BSP page for the file upload. (new version with htmlb) When testing I get the following error: The following error text was processed in the system: An exception with the type CX_S

  • How to hide value of characteristic in CV04N

    Hi, Regarding  a characteristic connected to a class in class type 017.   The characteristic has a value with sensitive information that should not be seen by all that have access to the trx CV04N or display document. We have set up the authorisation

  • ICM_HTTP_CONNECTION_FAILED error on http receive method

    Hi, I am trying to read a XML via http. I have developed a code referencing this blog: /people/rashid.javed/blog/2007/03/11/cricket-world-cup-http-client-and-simple-transformations When http receive method is executed it gives me an error. On executi