Blog Archive

Friday, June 16, 2017

SAP HCI testing with soap ui sync and async way.

Om

1. there are 3 ways of testing/ starting iflow with our interfere

1)soapy in sync
2)soap in async ( use groovy script; to add payload or custom message to monitor in log)
               def messageLog = messageLogFactory.getMessageLog(message);
3)timer in iflow ( use groovy script; to add payload or custom message to monitor in log)
               def messageLog = messageLogFactory.getMessageLog(message);

/*
import com.sap.gateway.ip.core.customdev.util.Message;
import java.util.HashMap;
def Message processData(Message message) {
    def body = message.getBody(java.lang.String) as String;
    def messageLog = messageLogFactory.getMessageLog(message);
    if(messageLog != null){
        messageLog.setStringProperty("Logging#1", body.toString());
        messageLog.addAttachmentAsString("ResponsePayload:", body, "text/plain");
     }
    return message;
}
*/


soapui[sync]  <--> SAP HCI (other systems)

( other wsdl binding will be work here, in sap pi we have option to generate wsdl by system)
but in SAP HCI , no such option.

you will get url, what about definition.
Create wsdl file from eclipse software.

step by step 
(practice one wsdl for sync, one wsdl for async scenarios)
Validate your wsdl support sync or async calls.

youtube vide more on create ,xsd/wsdl structures.



( these two options are useful at different time,



porttype and operation tag  check request and response in wsdl

3)  test with out any user involve: with having payload.
with timer.




No comments:

Post a Comment