To monitor the availability of web services, create an End User Experience Monitoring (EEMon) script to simulate SOAP requests.
A script wizard allows you to generate HTTP messages that send SOAP requests over HTTP. The wizard imports a WSDL file from the file system, and displays the web service methods it contains. Select one or more of the methods. For each of them, the POST body of the SOAP message is generated. For input parameters, placeholders, that can be updated in the XML stream that is displayed, are generated.
You have installed a full Java SDK (32 bit). JRE is not sufficient.
Perform the following steps:
In the SAP Solution Manager Configuration work center, choose
.In the Global Settings
step, download the EEM script editor.
For more information about the EEMon editor, see the End User Experience Monitoring Script Editor
documentation on SAP Service Marketplace, under .
Create an empty HTTP script, or open an existing one.
Note
If you start with an empty script, remove the initial generated dummy message.
To launch the Web Services Wizard, in the EEMon script editor, choose
.Select the Generate Web Service Messages
wizard.
To select a WSDL file, choose the Browse
pushbutton.
Note
WSDL files that are available via URL must be downloaded first.
If the WSDL is zipped (as generated by the SAP J2EE wsnavigator, for example), unzip the file and select the top-level WSDL.
A list of Web service methods in the WSDL is displayed.
Select the Web service methods to include in the script.
The POST bodies are generated. The input parameters for the web service methods are populated with sample data. For request parameters, two elements are created by default, if the cardinality allows.
Review the data and replace default values with data which is useful in the SOAP request.
Note
The wizard allows you to process only simple input data. If it fails, for example due to complex data structures or special data types, contact SAP support and submit the WSDL file in an OSS message.
Optional: To handle authentication automatically, activate automatic authentication message retry:
Open the script configuration.
Under Executor Type
to xmlretry.
Recommendation
If the EEMon script editor fails to detect the JDK, try the following:
Ensure the PATH
environment variable contains the folder containing javac.exe
.
To ensure the avac compiler bundled with the JDK is detected, configure the EEMon script editor to launch with a specified JDK, by adding the following parameter to EemEditor.ini
: -vm c:/<full path>/javaw.exe.
Add the following JVM parameter to EemEditor.ini
: -DExternalCompiler=c:/<full path>/javaw.exe (C:\soft\jdk1.6\bin\javac.exe, for example), and restart the EEMon script editor.
In the EEMon script editor, choose
A dialog box appears.
In the hierarchy, choose
.Select the Interface Channel Monitoring
checkbox.
Upload the EEMon script to SAP Solution Manager.
Select the EEM script to upload to SAP Solution Manager.
In the context menu, choose Export to EEM Repository
.
Choose OK
to confirm.
For more information, in the End User Experience Monitoring Script Editor
documentation, see the “Upload EEM Scripts and Trust Store to SAP Solution Manager” chapter.
Note
EEMon scripts for ICMon are scheduled and controlled via the MAI infrastructure, not directly by the EEMon agelet, so several configuration parameters are not effective for ICMon scripts and must not be maintained:
Schedule settings
Work mode settings
Threshold values