WebService 4.7 / WAS 620 XSTRING BASE 64

Hi all,
I am working on WebAS 620 and have to call from ABAP side a Webservice via SOAP.
The webservice belongs to a third party tool and is placed on a different server in the internet.
This webservice contains coomlpex parameter. I will include the WSDL to this thread.
Reading the documentation it says that every webservice can be called from ABAP on WAS 602.
(but i don't know how ...)
One of the parameter is a table which can contain many pdf streams. This streams have to be
in BASE64 format
I found an example (SMS) at the forum/blogs, but i didn't found a way to manage this complex
parameter in a WebService call on 620 ...
Do you know if this is possible and how I can do it?
Method Parameters:
Name                    -Type                         -Mandatory            -Description    
*files                       FileContainer             -required                -The files to process
*FileContainer.         -base64                     -required                -The base64 encoded file
SourceFileContent 
*FileContainer.         -string [ ]                    -required                -file name of the file to
SourceFileName                                                                be processed
*FileContainer.         -int                                                        -for xyzmoSeal ONLY to manage
CustomId                                                                           attachments (see u201Cmanage                                                                               
Attachmentsu201D)
*FileContainer.         -int                                                         -for xyzmoSeal ONLY to manage
CustomRefId                                                                      attachments (see u201Cmanage                                                                               
Attachments")
*FileContainer.         -int                             -readonly              -status of this file in the response
Status                                                                               only.
*selectedWorkflow    -string [ ]                                               -selected workflow name as                                                                               
result from  Name Method x
WSDL
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://com.xyzmo.server.inputinterface.webservice/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://com.xyzmo.server.inputinterface.webservice/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
  <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">&lt;b&gt;xyzmo Webservice Advanced Interface&lt;/b&gt;&lt;br/&gt; Document is sent in for processing. Processing may be signing, verification, conversion...&lt;br/&gt;The document is processed via a predefined 'workflow' configuration.&lt;br/&gt;For example:&lt;dir&gt;com.xyzmo.server.documentworkflow._06_signSealPDF::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._06_signAdobePDF::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._06_signXMLdSIG::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._06_signPKCS7::_global.xml&lt;br/&gt;com.xyzmo.server.DocumentWorkflow._06_signSealPDF_dig2P::_global.xml&lt;br/&gt;com.xyzmo.server.DocumentWorkflow._06_dig2Pstandalone::_global.xml&lt;br/&gt;com.xyzmo.server.DocumentWorkflow._06_MimeParser::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._36_verify::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._56_convertFile2Pdf::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._96_verify_Type_02&lt;br/&gt;com.xyzmo.server.documentworkflow._96a_verify_Type_13&lt;/dir&gt;</wsdl:documentation>
  <wsdl:types>
    <s:schema elementFormDefault="qualified" targetNamespace="http://com.xyzmo.server.inputinterface.webservice/">
      <s:element name="Process">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="files" type="tns:ArrayOfFileContainer" />
            <s:element minOccurs="0" maxOccurs="1" name="selectedWorkflowName" type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:complexType name="ArrayOfFileContainer">
        <s:sequence>
          <s:element minOccurs="0" maxOccurs="unbounded" name="FileContainer" nillable="true" type="tns:FileContainer" />
        </s:sequence>
      </s:complexType>
      <s:complexType name="FileContainer">
        <s:sequence>
          <s:element minOccurs="0" maxOccurs="1" name="SourceFileContent" type="s:base64Binary" />
          <s:element minOccurs="0" maxOccurs="1" name="SourceFileName" type="s:string" />
          <s:element minOccurs="0" maxOccurs="1" name="CustomId" type="s:string" />
          <s:element minOccurs="0" maxOccurs="1" name="CustomRefId" type="s:string" />
          <s:element minOccurs="1" maxOccurs="1" name="Status" type="s:int" />
        </s:sequence>
      </s:complexType>
      <s:element name="ProcessResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="ProcessResult" type="tns:ProcessResult" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:complexType name="ProcessResult">
        <s:sequence>
          <s:element minOccurs="1" maxOccurs="1" name="ProcessingPolicyStatus" type="s:int" />
          <s:element minOccurs="0" maxOccurs="1" name="ProcessedFiles" type="tns:ArrayOfFileContainer" />
        </s:sequence>
      </s:complexType>
      <s:element name="ProcessMail">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="mimeMessage" type="tns:ArrayOfString" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:complexType name="ArrayOfString">
        <s:sequence>
          <s:element minOccurs="0" maxOccurs="unbounded" name="string" nillable="true" type="s:string" />
        </s:sequence>
      </s:complexType>
      <s:element name="ProcessMailResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="ProcessMailResult" type="tns:ArrayOfString" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="GetWorkflowList">
        <s:complexType />
      </s:element>
      <s:element name="GetWorkflowListResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="GetWorkflowListResult" type="tns:ArrayOfString" />
          </s:sequence>
        </s:complexType>
      </s:element>
    </s:schema>
  </wsdl:types>
  <wsdl:message name="ProcessSoapIn">
    <wsdl:part name="parameters" element="tns:Process" />
  </wsdl:message>
  <wsdl:message name="ProcessSoapOut">
    <wsdl:part name="parameters" element="tns:ProcessResponse" />
  </wsdl:message>
  <wsdl:message name="ProcessMailSoapIn">
    <wsdl:part name="parameters" element="tns:ProcessMail" />
  </wsdl:message>
  <wsdl:message name="ProcessMailSoapOut">
    <wsdl:part name="parameters" element="tns:ProcessMailResponse" />
  </wsdl:message>
  <wsdl:message name="GetWorkflowListSoapIn">
    <wsdl:part name="parameters" element="tns:GetWorkflowList" />
  </wsdl:message>
  <wsdl:message name="GetWorkflowListSoapOut">
    <wsdl:part name="parameters" element="tns:GetWorkflowListResponse" />
  </wsdl:message>
  <wsdl:portType name="xyzmoWebServiceSoap">
    <wsdl:operation name="Process">
      <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">Method executes the selected workflow, for each fileContainer entry.&lt;br/&gt; PARAMETER (required) FileContainer[] 'files': contains the files to be processed. At least one FileContainer is required.&lt;br/&gt; PARAMETER (optional) string 'selectedWorkflowName': holds the selected workflow name as a result from method GetWorkflowList(). If no value is given the default value in the Interface Configuration is used.</wsdl:documentation>
      <wsdl:input message="tns:ProcessSoapIn" />
      <wsdl:output message="tns:ProcessSoapOut" />
    </wsdl:operation>
    <wsdl:operation name="ProcessMail">
      <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">Method executes the 06_MimeParser workflow, for each mimeMessage entry.&lt;br/&gt;PARAMETER (required) string[] 'mimeMessage': string representation of mime message to be parsed.</wsdl:documentation>
      <wsdl:input message="tns:ProcessMailSoapIn" />
      <wsdl:output message="tns:ProcessMailSoapOut" />
    </wsdl:operation>
    <wsdl:operation name="GetWorkflowList">
      <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">Method returns all permitted workflows (as string array) for the calling URL respectively port.&lt;br/&gt;No PARAMETERS.</wsdl:documentation>
      <wsdl:input message="tns:GetWorkflowListSoapIn" />
      <wsdl:output message="tns:GetWorkflowListSoapOut" />
    </wsdl:operation>
  </wsdl:portType>
  <wsdl:binding name="xyzmoWebServiceSoap" type="tns:xyzmoWebServiceSoap">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="Process">
      <soap:operation soapAction="http://com.xyzmo.server.inputinterface.webservice/Process" style="document" />
      <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="ProcessMail">
      <soap:operation soapAction="http://com.xyzmo.server.inputinterface.webservice/ProcessMail" style="document" />
      <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="GetWorkflowList">
      <soap:operation soapAction="http://com.xyzmo.server.inputinterface.webservice/GetWorkflowList" style="document" />
      <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>
  <wsdl:binding name="xyzmoWebServiceSoap12" type="tns:xyzmoWebServiceSoap">
    <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="Process">
      <soap12:operation soapAction="http://com.xyzmo.server.inputinterface.webservice/Process" style="document" />
      <wsdl:input>
        <soap12:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap12:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="ProcessMail">
      <soap12:operation soapAction="http://com.xyzmo.server.inputinterface.webservice/ProcessMail" style="document" />
      <wsdl:input>
        <soap12:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap12:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="GetWorkflowList">
      <soap12:operation soapAction="http://com.xyzmo.server.inputinterface.webservice/GetWorkflowList" style="document" />
      <wsdl:input>
        <soap12:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap12:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>
  <wsdl:service name="xyzmoWebService">
    <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">&lt;b&gt;xyzmo Webservice Advanced Interface&lt;/b&gt;&lt;br/&gt; Document is sent in for processing. Processing may be signing, verification, conversion...&lt;br/&gt;The document is processed via a predefined 'workflow' configuration.&lt;br/&gt;For example:&lt;dir&gt;com.xyzmo.server.documentworkflow._06_signSealPDF::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._06_signAdobePDF::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._06_signXMLdSIG::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._06_signPKCS7::_global.xml&lt;br/&gt;com.xyzmo.server.DocumentWorkflow._06_signSealPDF_dig2P::_global.xml&lt;br/&gt;com.xyzmo.server.DocumentWorkflow._06_dig2Pstandalone::_global.xml&lt;br/&gt;com.xyzmo.server.DocumentWorkflow._06_MimeParser::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._36_verify::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._56_convertFile2Pdf::_global.xml&lt;br/&gt;com.xyzmo.server.documentworkflow._96_verify_Type_02&lt;br/&gt;com.xyzmo.server.documentworkflow._96a_verify_Type_13&lt;/dir&gt;</wsdl:documentation>
    <wsdl:port name="xyzmoWebServiceSoap" binding="tns:xyzmoWebServiceSoap">
      <soap:address location="http://testlab.xyzmo.com:50006/com.xyzmo.server.inputinterface.webservice.asmx" />
    </wsdl:port>
    <wsdl:port name="xyzmoWebServiceSoap12" binding="tns:xyzmoWebServiceSoap12">
      <soap12:address location="http://testlab.xyzmo.com:50006/com.xyzmo.server.inputinterface.webservice.asmx" />
    </wsdl:port>
  </wsdl:service>
</wsdl:definitions>
Best regards,
Michael Handschuh

Hi Michael,
   I have almost the same requirement. After searching a lot I found following. It might help you or may not.
If you find any other solution pls post that.
Thanks,
Santosh.
START-OF-SELECTION .
  CLEAR WF_STRING .
  CONCATENATE '<?xml version="1.0" encoding="utf-8"?>'
  '<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">'
  '<soap:Body>'
  '<ConversionRate xmlns="http://www.webserviceX.NET/">'
  '<FromCurrency>' V_FROM '</FromCurrency>'
  '<ToCurrency>' V_TO '</ToCurrency>'
  '</ConversionRate>'
  '</soap:Body>'
  '</soap:Envelope>'
  INTO WF_STRING .
  CLEAR :RLENGTH , TXLEN .
  RLENGTH = STRLEN( WF_STRING ) .
  MOVE: RLENGTH TO TXLEN .
  CLEAR: WF_PROXY, WF_PORT .
  MOVE: P_PROXY TO WF_PROXY ,
        P_PORT TO WF_PORT .
  CALL METHOD CL_HTTP_CLIENT=>CREATE
    EXPORTING
      HOST          = 'www.webservicex.net'
      SERVICE       = '80'
      SCHEME        = '1'
      PROXY_HOST    = WF_PROXY
      PROXY_SERVICE = WF_PORT
    IMPORTING
      CLIENT        = HTTP_CLIENT.
  HTTP_CLIENT->PROPERTYTYPE_LOGON_POPUP = HTTP_CLIENT->CO_DISABLED.
  WF_USER = USER .
  WF_PASSWORD = PASSWORD .
proxy server authentication
  CALL METHOD HTTP_CLIENT->AUTHENTICATE
    EXPORTING
      PROXY_AUTHENTICATION = 'X'
      USERNAME             = WF_USER
      PASSWORD             = WF_PASSWORD.
  CALL METHOD HTTP_CLIENT->REQUEST->SET_HEADER_FIELD
    EXPORTING
      NAME  = '~request_method'
      VALUE = 'POST'.
  CALL METHOD HTTP_CLIENT->REQUEST->SET_HEADER_FIELD
    EXPORTING
      NAME  = '~server_protocol'
      VALUE = 'HTTP/1.1'.
  CALL METHOD HTTP_CLIENT->REQUEST->SET_HEADER_FIELD
    EXPORTING
      NAME  = '~request_uri'
      VALUE = '/CurrencyConvertor.asmx'.
  CALL METHOD HTTP_CLIENT->REQUEST->SET_HEADER_FIELD
    EXPORTING
      NAME  = 'Content-Type'
      VALUE = 'text/xml; charset=utf-8'.
  CALL METHOD HTTP_CLIENT->REQUEST->SET_HEADER_FIELD
    EXPORTING
      NAME  = 'Content-Length'
      VALUE = TXLEN.
  CALL METHOD HTTP_CLIENT->REQUEST->SET_HEADER_FIELD
    EXPORTING
      NAME  = 'SOAPAction'
      VALUE = 'http://www.webserviceX.NET/ConversionRate'.
  CALL METHOD HTTP_CLIENT->REQUEST->SET_CDATA
    EXPORTING
      DATA   = WF_STRING
      OFFSET = 0
      LENGTH = RLENGTH.
  CALL METHOD HTTP_CLIENT->SEND
    EXCEPTIONS
      HTTP_COMMUNICATION_FAILURE = 1
      HTTP_INVALID_STATE         = 2.
  CALL METHOD HTTP_CLIENT->RECEIVE
    EXCEPTIONS
      HTTP_COMMUNICATION_FAILURE = 1
      HTTP_INVALID_STATE         = 2
      HTTP_PROCESSING_FAILED     = 3.
  CLEAR WF_STRING1 .
  WF_STRING1 = HTTP_CLIENT->RESPONSE->GET_CDATA( ).
  REPLACE ALL OCCURRENCES OF
      '&lt;' IN WF_STRING1 WITH '<' .
  REPLACE ALL OCCURRENCES OF
   '&gt;' IN WF_STRING1 WITH '>' .
  REPLACE ALL OCCURRENCES OF
   'xmlns=' IN WF_STRING1 WITH 'xmlns:xsl=' .
  TRY .
      CALL TRANSFORMATION (`Y_CURR_XML2ABAP`)
              SOURCE XML WF_STRING1
              RESULT     OUTTAB = OUTTAB.
    CATCH CX_XSLT_EXCEPTION INTO XSLT_ERR.
      DATA: S TYPE STRING.
      S = XSLT_ERR->GET_TEXT( ).
      WRITE: ': ', S.
      STOP.
  ENDTRY .

Similar Messages

  • Consuming WebService WAS 620

    Hi,
    I have a system running on WAS 620, since it this does not support client proxy generation, I am thinking to consume the web-service using http.
    How can I pass SOAP messages using http in WAS 620?
    In past I have consumed web-service by-passing SOAP on WAS 620 but sure how to get this one going.
    Or any work-around if you'll can suggest/
    Thanks & Regards,
    CD

    This is all covered extensively in the Online Documentation.
    Start [here.|http://help.sap.com/saphelp_47x200/helpdata/en/bb/ddb33d2ae46b3be10000000a114084/frameset.htm]
    Cheers
    Graham Robbo

  • How to reference complex data type when consuming web services in WAS 620?

    In WAS 620, I tried to consume a web service in ABAP. I was successful when the web service returned one or more simple data type. But when the web service is changed to return a complex data type (eg. a structure with 3 elements), the call to the web service did not return anything.
    Do any of you know how to reference the individual element in the structure of an output parameter in a web service? I use the add_parameter method of the CSoapDocument class to identify the output parameters.
    Here is part of the WSDL file:
      <?xml version="1.0" encoding="UTF-8" ?>
    - <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="urn:sap-com:document:sap:rfc:functions" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="urn:sap-com:document:sap:rfc:functions">
    - <types>
    - <xsd:schema targetNamespace="urn:sap-com:document:sap:rfc:functions">
    - <xsd:element name="Z_SRM_SOAP_TEST_COMPLEX">
    - <xsd:complexType>
    - <xsd:all>
    - <xsd:element name="INTEXT">
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="50" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
      </xsd:all>
      </xsd:complexType>
      </xsd:element>
    - <xsd:element name="Z_SRM_SOAP_TEST_COMPLEX.Response">
    - <xsd:complexType>
    - <xsd:all>
      <xsd:element name="OUTTEXT" type="s0:ZSRM_TEST_STRUCT" />
      </xsd:all>
      </xsd:complexType>
      </xsd:element>
    - <xsd:complexType name="ZSRM_TEST_STRUCT">
    - <xsd:sequence>
    - <xsd:element name="ELEMENT1" minOccurs="0">
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="50" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ELEMENT2" minOccurs="0">
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="50" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
    - <xsd:element name="ELEMENT3" minOccurs="0">
    - <xsd:simpleType>
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="50" />
      </xsd:restriction>
      </xsd:simpleType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:schema>
      </types>

    Hi,
      [email protected] is my id and one more thing u by looking at the wsdl file u can know what al the parameters we have to give to the webservice so try it out also.
    Regards,
    Sirisha.

  • Consuming a web service in WAS 620

    Hi ,
    Experts ...
    Im trying to consume a  java web service in WAS 620 ...
    there are no proxy facilities available in WAS 620 ..
    let me know the alternet way ...
    i need to tranfer ...5 table data to the Java WAS server ...
    Thanks

    Hi ,
    I had the same issue when i was trying to consume a webservice in WAS 620
    wat altenate way i have done it ... triggered the Web Service using SOAP object from R3 ...
    then using Java connection i have called an RFC in the R3 which displays all the data to the web service
    and then the web service picks up all the available data ..
    u definetly need to know Jco for this ...
    Regards
    Renu

  • WAS 620 post -installation problem

    Hi,
    We have installed WAS 620/WIN2K/SAP DB 7.3.1 with both the ABAP and the J2EE stack. After that, we did the client copy & were importing support packages for basis. We applied till support package 25 successfully. While applying 26, the system restarted.
    After bringing up the system, when we start SAP, all the workprocesses are in connect mode. The dev traces say:
    "Try to connect (DEFAULT) on connection 0...." and nothing further. The dispatcher indicator is yellow.
    We check db and found it is ok (state: WARM). No errors in knldiag too.
    On executing dpmon, all workprocesses having status Run but no other information. No logon to SAP possible.
    Did any of you encounter anything similar. Any directions or inputs would be most helpful.
    Thanks in advance,
    Siva

    Siva,
    Did you resolve this issue?  How?
    Thanks
    Tim

  • Need Help for SAP WAS 620

    Hi,
    We have installed SAP Biller Direct application on J2EE 620 engine integrated with SAP R/3 4.7 Enterprise (WAS 620). For user management security we will use ABAP stack.
    The link of this Biller Direct Application will be provided on company's web portal (not SAP Ent. Portal). Once user click on link , Biller Direct application will open it another browser window.User must create their own user id and password.Other information will also be asked like Last Name ,first name, etc) during user id and password creation. Basically user will create their own user master record. (just think of it as you are creating an email account in Yahoo portal connected to R/3)
    My question is :-
    1) What configuration I need to do on J2EE and R/3 side so that user record will be created in R/3 when user creates it's own ID and password?
    2)If I want to link LDAP with R/3,  how I can link the LDAP with R/3 (user mapping ) will it be automatic, once the user creates it user id in web portal? OR do i have manually synch LDAP and R/3
    I will appreciate your response
    Thanks

    I do not understand presentation in terms of collection and disbursement you mean from the business side of things or will i say looking at it from a business analyst perspective. I have some info if you can send an email add then i will send something which might be helpful though i am not sure, I myself i am just moving into such area as a SAP Business Analyst for Claims managment though i have an insurance background of another ERP so i might be able to help.

  • Is EOIO messaging possible using ABAP Proxy in WAS 620?

    Hello,
    I am trying to implement an outbound EOIO interface using ABAP Proxy on a SAP R/3 470 running on WAS 620. We have XI 3.0 running on WAS 640. I followed the SAP documentation available at http://help.sap.com/saphelp_nw04/helpdata/en/c9/74246d8ad2447799063d39013e9a11/frameset.htm
    I find that the interface IF_WSPROTOCOL_ASYNC_MESSAGING required in this exaple does not exist in our R/3 system. I also notice that proxy classes generated on WAS 640 have the superclass of CL_PROXY_BASIS. But the proxy object generated in WAS 620 have no superclass at all.
    Does anybody know how I can get EOIO interfaces to work on the WAS 620? Did you use these objects? Can I import / install them somehow? Or, is EOIO just not possible in WAS 620?
    Please let me know.
    Regards
    Cerish Chemparathy

    HI,
    have a look at this link to the ABAP Proxy Runtime based on WAS 6.20 (Xi 2.0) http://help.sap.com/saphelp_xi20sr1/helpdata/en/02/265c3cf311070ae10000000a114084/content.htm
    There is a help entry called Guatanteeing the Order of Asynchronous Messages. Seems that you somehow can set a queue id for this messages and as long as theses messages are all in the same queue, the order will be maintained.
    Your observations are right, there are differences between the Proxy Runtime in WAS 6.20 and in WAS 6.40 and as far as i know, there is no way to downport the 6.40 runtime to 6.20. You will need to stick with wath 6.20 offers.
    Regards
    Christine

  • How to publish and consume web services in WAS 620?

    It appears that Web Service Creation Wizard is only available in WAS 640. We only have WAS 620 installed. Do any of you know what are the steps to publish ABAP function modules as web services, as well as to consume web services?
    Thanks,
    Angela

    Hi Angela,
       If you want to expose function modules as web service, you can generate WSDL by running BSP application 'webservicebrowser'. If you want to consume a web service then it is a bit difficult but possible. Look at sample programs (rsvsoap*).
    Also look at help document http://help.sap.com/saphelp_47x200/helpdata/en/94/f8c8a2e68811d6b2dc00508b5d5211/frameset.htm
    Regards,
    Sanjeev

  • Configure PDF forms with WAS 620

    Hi,
    We are on WAS 620 and want to work with interactive pdf forms which is available with WAS 640.
    I was told that this can be done by proper config with WAS 620 also.
    Can some one confirm this and let me know where to start and any material I can refer too.

    Hi Venkat,
    As far as I know the WAS 620 only supports to output your Forms and Scripts to PDF Format but they are not interactive.
    The Adobe Interactive Forms Solution is only available from WAS 640. You can design your forms either in ABAP transaction SFP or in NWDS(Netweaver Developer Studio) Form Designer.
    You can ofcourse replace your SMART Forms with the interactive forms in ABAP. Transaction is SFP(Form Designer). This transaction is available only from ECC 5.0 which runs on WAS 640.
    Check the following links for all the information you need on PDF Forms and migration of your SMART Forms to PDF Forms. But as you see all this is available from ERP 2004 onwards which is on WAS 640.
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/4adf7ba13c4ac1b4600d4df15f8b84/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/16/a369b1800e4bdda978ee0fe3b7bd2c/frameset.htm
    Hope this is helpful.
    Regards,
    Shubham

  • GTS WAS 620 update to GTS 8.0

    Hi Guru there ,
    We now use GTS WAS620 with sp 45 ( SAPKB62045 ) on the Oracle 10.2.0.2.0 HP-UX ia64 and non-unicode .
    We plan to update to GTS 8.0.
    What is the best way to do it ?
    GTS 620  -
    > GTS ( 7.0 or 7.1 or 7.2 ) and then ---> GTS 8.0  or direct to update to GTS 8.0 ?
    and when we need to do the unicode conversion ?
    waiting for your  reply.
    Wei

    Hi , Christin,
    Thank you for your answer. I have read the SAP Note 1266675, and according to this note , GTS 3.0 WAS 620 cannot be directly upgrade to GTS 8.0 (NetWeaver 7.0 ) , it is must be use the " Substitution upgrade " method to first upgrade e.g GTS.7.2 and then to GTS 8.0.
    I got another SAP Note 1267076 , and it sounds that GTS 3.0 can directly upgrade to GTS 8.0.
    I am puzzled, which one is correct. and what should we really to do.
    By the way , our GTS 3.0 is in non-unicode mode, shall we do the unicode conversion immediately after upgrade to GTS 8.0 ?
    thank you and waiting for your early reply.
    best regards,
    Wei Wu

  • Consuming a Webservice created on WAS 6.20

    Hello,
    is it possible to generate a client proxy automatically on WAS 6.40 for a WSDL-description which is generated with the Webservicebrowser on a WAS 6.20?
    I tried to do this but when i test the proxy i receive the following fault-message:
    <ERRORTEXT>Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/</ERRORTEXT>
    When i compare a generated WSDL document on 6.40 and a generated WSDL document on 6.20 i see that these documents are different. What is the reason for this differences?
    Thanks for your help!

    Eddy,
    i created the proxy in the following way:
    Enterprise Services - Webservice Library - Context Menu - Create - Proxy Object
    I've typed in the URL from the Webservice Browser an then i followed the wizard. But when i am testing the proxy, it doesn't work! The error that i have explained in my first message occurs. Is here any special setting required in the wizard?
    Thanks for your help!

  • WAS 620 ABAP+JAVA stack

    Hi all,
    we currently running on SAP Entreprise 470x110 with SAP Basis 620 on HPUX with Oracle 9i.
    And currenly we have only ABAP stack and we would like to install the Java stack on our currently landscape.
    Can you advice me on this matter and how we should start.I would like to know what are the prerequite and also the system landscape.
    Please kindly advise.
    Thank you.
    Kah Fei

    when you use web browser,Internet comm.manager(ICM) will route your request either to ABAP stack or JAVA stack.
    The Java stack is build following J2EE standards.with in the J2EE you have EJB container and Web container.So its a structure based on J2EE standards.
    Actually i did'nt understand what you mean by "i would like to use java to support frontend internet instead of j2ee."

  • Create Web Service (outbound proxy) with WAS 620

    Hi all,
    Is it possible to create an outbound Abap proxy - using a WSDL - to consume a web service, in a 4.7 Release (Web AS 620)? Is there any restrictions on this release?
    Thanks,
    Miguel

    Hi,
    Did you check this web log?
    /people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
    Eddy

  • Exception while calling Webservice deployed in WAS 6.1

    Hi All,
    My application exposes web services and am getting below error when invoking from SOAP UI tool.
    Developed in RAD 7.5, deployed in WAS 6.1.0.21 and uses JAX-WS.
    Googling points to JAXB error when using Date, Timestamp data types. I am not using any such data types other than XMLGregorianCalendar for which the xsd data type generated was xs:anySimpleType.
    Any pointers would be of great help. Thanks in advance.
    Reference I org.apache.xml.security.signature.Reference verify Verification successful for URI "#id-2"
    SystemOut O INFO [WebContainer : 1] (WSF[5/30/10 7:14:06:346 MST] 00000030 SystemOut O INFO [WebContainer : 1] (WSF2ProviderDefaultHandler.java:280) - EXIT --> WSF2ProviderDefaultHandler.verifySignature(), time taken= 431 ms
    00000030 JAXBUtils I org.apache.axis2.jaxws.message.databinding.JAXBUtils createJAXBContextValue Both ObjectFactory & package-infoException = org.apache.axis2.AxisFault
    Source = com.ibm.ws.websvcs.transport.http.WASAxis2Servlet.doPost
    at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWrapper.java:282)
    at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:459)
    at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:265)
    at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:262)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1146)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:592)
    at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
    at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3507)
    at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:269)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
    at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:122)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
    at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
    at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
    at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)
    Caused by: javax.xml.ws.WebServiceException: java.lang.ClassCastException: com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$5 incompatible with com.sun.xml.bind.v2.model.impl.ClassInfoImpl
    at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:180)
    at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:79)
    at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:134)
    at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMinimalMethodMarshaller.demarshalRequest(DocLitWrappedMinimalMethodMarshaller.java:229)
    at org.apache.axis2.jaxws.server.dispatcher.JavaBeanDispatcher.createRequestParameters(JavaBeanDispatcher.java:262)
    at org.apache.axis2.jaxws.server.dispatcher.JavaBeanDispatcher.invoke(JavaBeanDispatcher.java:81)
    at org.apache.axis2.jaxws.server.EndpointController.invoke(EndpointController.java:100)
    at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:140)
    ... 28 more
    Caused by: java.lang.ClassCastException: com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$5 incompatible with com.sun.xml.bind.v2.model.impl.ClassInfoImpl
    at com.sun.xml.bind.v2.model.impl.ClassInfoImpl.getBaseClass(ClassInfoImpl.java:171)
    at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:61)
    at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:41)
    at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:149)
    at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:55)
    at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:41)
    at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:196)
    at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
    at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
    at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
    at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
    at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
    at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
    at java.util.AbstractList$Itr.next(AbstractList.java:437)
    at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:146)
    at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:55)
    at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
    at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
    at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
    at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
    at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
    at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
    at java.util.AbstractList$Itr.next(AbstractList.java:437)
    at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:146)
    at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:55)
    at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:41)
    at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:196)
    at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:211)
    Regards,
    Gokul

    Hi sergey,
    I think the error you got because you have binded the node incorrectly as shown in the below line of code.
    wdContext.nodeCompanyCheck().bind(new Request_CompanyServiceViDocument_filterCompany0());
    I think you should do it like the below code.
    Request_CompanyServiceViDocument_filterCompany0() testObject = new Request_CompanyServiceViDocument_filterCompany0();
    testObject.setACompanyId(contextElement.getCompanyID());
    wdContext.nodeCompanyCheck().bind(testObject);
    wdContext.nodeCompanyCheck().currentCompanyCheckElement().modelObject().execute();
    Hope this will help as the error looks as its only because of binding miss match.
    Regards
    Narendra

  • MiniSAP WAS 620 installation problem

    Dear WAS developers,
    I got 3 CD's from SAP Press to install WAS620. I'm trying to Install on Window XP Home(SP1). During installation it ask for inserting Kernel Cd first,then Data1 CD, then Data2 CD. Then again it ask for inserting Kernel CD. When I install Kernel Cd I'm getting the following error Log.
    <b>Error: ADADBREGISTER_IND_ADA ExecuteCheck 2 223
    Exit code from c:\sapdb\programs\pgm\dbmcli.exe: 2.
    Error: ADADBREGISTER_IND_ADA InternalInstallationDo 2 223
    Phase failed.
    Error: ADADBREGISTER_IND_ADA InstallationDo 2 223
    Phase failed.
    Error: Main {} 2 223
    Installation aborted.</b>
    Any help in resolving this is highly appreciated.
    Harprit

    Hi Tim,
    If you are re-installing the WAS, Please stop all SAPDB related services in your computer and restart the installation.
    regards
    Anand.M

Maybe you are looking for