SOAPUI Request to BO Session Web Service - Login Method

Hi,
I added a new project in SoapUI using the following WSDL --> http://ms240rmdbi01:8080/dswsbobje/services/Session?wsdl

I am trying to use the method Login which has the following Soap request

<soapenv:Envelope xmlns:soapenv=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:ns=“http://session.dsws.businessobjects.com/2007/06/01”>
soapenv:Header/
soapenv:Body
ns:login
ns:credential/

ns:version?</ns:version>
</ns:login>
</soapenv:Body>
</soapenv:Envelope>

What attributes i need to specify in ns:credential/ so that i get the response back. I have tried multiple options and all i get its the following error

S2 login exception (Error: WSE 99998)

MY OBJECTIVE:

We are trying to do a POC for scheduling BOE Crystal reports using Bi Platform web services schedule method. To access any Bi Platform service we need to have a session ID generated by Session web service. Please let me know how i can achieve this.


arunnura17 (BOB member since 2007-03-30)

Not a direct answer to your question, but could you just do the POC using the web services SDK? If memory serves me correctly, there is even a working code sample to do exactly what you’re looking for in the developer guide. You could also trace the traffic to see the contents of the SOAP exchange.


BoB LoblaW :us: (BOB member since 2007-10-23)

Thanks BoB LoblaW,

I have an SDK code which is scheduling my report using web services. How do i trace the web service and capture the SOAP messages?

Please let me know.

Thanks
Arun


arunnura17 (BOB member since 2007-03-30)

You will have to use a debugging proxy like Fiddler or Charles Debugger to capture traffic between the client and server.

If you have the code to schedule via web services, why do you need to capture the traffic? Isn’t scheduling your end goal? For the record, SAP will only support code using the pre-generated JAR files or .NET assemblies. If you don’t want to use the predefined stuff for whatever reason, you can always generate your own based on the WSDL for use in your client applications.


BoB LoblaW :us: (BOB member since 2007-10-23)

You have to change ns:credential/ with


<ns:credential Login="<USER>" Password="<PASSWORD>" Domain="<DOMAIN>" />

Regards


kakarno :it: (BOB member since 2006-03-02)