SOAP Services can easily be tested via their SOAP interfaces.
You can test REST services by using the E2E SOAP Test Tool resp. the E2E Analyzer on the generated SOP interface, or by using the E2E REST Test Tool. Find a comprehensive description how to do that on Testing REST Services.
Non-SOAP services, such as timer services, schedulers, HTTP services and others are supplied by a SOAP interface for testing purposes. This shadow interface and the corresponding shadow service is generated automatically when compiling the service. That means, non-SOAP services can be tested the same way as described for SOAP services.
| The generated shadow port will automatically get the same port number as the xUML service port but with a 5 as the first digit. Alternatively, to avoid port conflicts, the trace port can be set via the specification of the service deployment. |
Find below a list of all E2E Bridge service types with their corresponding generated SOAP operations.
Service Type | Generated Operation |
---|
Timer | EXECUTE_TIMER_DIAGRAM |
Scheduler | EXECUTE_SCHEDULER_DIAGRAM |
Event Observer | <name of the Event Observer operation> , <event name>
|
HTTP | <name of the HTTP operation> |
SAP RFC | <name of the SAP function> |
Java | <name of the Java callback operation> |
JMS Listener | <name of the JMS listener operation> |
Startup / Shutdown | EXECUTE_STARTUP_ACTIVITY EXECUTE_SHUTDOWN_ACTIVITY
The Startup/Shutdown service gets the name StartupShutdownService4<name of the composite> |