Connecting SAP XI to Websphere Commerce server via SOAP

Question

Hi, I hope you can help...
I am currently attempting to connect to Websphere Commerce server 6.0.0.6 from SAP XI 3.0 using web services. Websphere Commerce has standard services for loading products that we would like to automate from SAP ECC. I have created the interface using an async/sync bridge in BPM.
Matmas IDoc (Async) --> ProcessCatalogEntry (Sync Request) --> AcknowledgeCatalogEntry (Sync Response) --> ALEAUD IDoc (Async).
This is working to an extent and I have a request and response in the message monitor
However, in the response message I am receiving an authorisation failure as the webservice requires the following in the SOAP header:
  <soapenv:Header>
  <wsse:Security soapenv:mustUnderstand="1"
    xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wsswssecurity-secext-1.0.xsd">
      <wsse:UsernameToken>
        <wsse:Username>xxxxxxxx</wsse:Username>
        <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wssusername-token-profile1.0#PasswordText">xxxxxxxx
         </wsse:Password>
       </wsse:UsernameToken>
     </wsse:Security>
   </soapenv:Header>
From reading several posts I  used the nosoap method to achieve this. I checked the "Do not use SOAP envelope"
in my receiver SOAP channel. I downloaded the SOAP Envelope XSD and added to it to include my additional header and body elements.
However, this is not working and I receive the following message in the monitor:
SOAP: Response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP Internal Server Error
I also created an XSLT to add the required SOAP header but was unsure how to use this as part of a synchronous process...
If you can, could you please advise me on how to resolve this issue...
Many thanks,
Pete
Edited by: Pete White on Feb 4, 2010 11:49 AM

Answer 1

Hello Thomas,
thanks for your answer. We are already on SP19. Starting and stopping is reacting but only with the above mentioned errors.
I think, that the classnames are OK because with a little Java JMS Testprogramm with the same parameters from the channeldefinition we can connect to the BEA Server. So this should be OK.
Kind regards
Manfred Schmidt-Voigt