Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

SOAP Calls

This functionality is available as of EEM 7.1 SP05

Using this functionality requires a full Java SDK (32 bit). Using only the JRE is not sufficient in this case.

Overview

A new script wizard allows to generate http messages that send SOAP requests over HTTP. The wizard imports a WSDL file from the file system and then displays a list of web service methods found in the WSDL. You select one or more of the methods. For each of them the POST body of the SOAP message is generated. For input parameters placeholders are generated that can be updated in the XML stream that is displayed.

Instruction

Open a HTTP Script

Create an empty http script or open an exisiting one.

Launch the Web Services Wizard

Menu: Script --> Script Wizard or corresponding tool bar button. Select the wizard Generate Web service messages and hit Next.

Open WSDL

Click the Browse button to select a WSDL file. WSDL files that are available via URL must be downloaded first. If the WSDL is zipped, as generated by the SAP J2EE wsnavigator the file must be unzipped first and the top-level WSDL should be selected.

Hit Next to load the WSDL.

Select SOAP Methods

On the next screen you get a list of web service methods found in the WSDL. Check the ones that you want to include in the script and hit Next again. At this point the POST bodies will be generated. This will only succeed if a full JDK is used to run the editor.

Inspect POST Bodies

You get the final screen of the wizard that displays all selectec web service methods - see screenshot. Input parameters to the web service methods are populated with example data. For collections typically two elements are created if the cardinality allows to do so. You will most likely have to review / change the default values to useful data in the context of the call.

This part of the wizard works for simple input data. It may fail, however, for arbitrarily complex data structures or for special data types. In such a case please submit the WSDL via an OSS message to review the problem.

Finish / review script

Click Finish to populate the messages into the script.

To handle authentication automatically it may be useful to activate automatic retry of the authentication message. For this purpose, open the script configuration. In section Common / Script Execution switch Executor type to xmlretry.

If you have started with an empty script it may be required to remove the initial dummy message that was generated.Labels parameters

Troubleshooting

JDK/JRE Problems

If the EEM editor has problems to detect the JDK correctly, you can try these options:

  • Adapt your PATH environment variable to contain the folder with javac.exe.
  • Configure the EemEditor explicitly to launch with a specified JDK. It will then pick the javac compiler bundled with the JDK. For this purpose, add this parameter to EemEditor.ini:
    -vm c:/full/path/to/javaw.exe
  • Add this JVM parameter to EemEditor.ini: -DExternalCompiler=C:\soft\jdk1.6\bin\javac.exe (replacing the example path given here with the full path to your javac.exe) and then restart the EEM Editor.
  • No labels