Using the Connector is very simple from the MBPM side. You need to create a
form in your process named "IOut***", and another named "IIn***" where *** is
anything you like. The replacement for *** in the "In" and "Out" forms must be
identical, and the name of the "Out" form must be used in the script call to the
Connector.
You must publish the supplied "eworkConnectorLib.elb" and add it to your
procedure. (This adds an integration Wizard item we will use to build the call to
the Connector). The next step is to enter the Partnership name you set up
previously, the "Out" form name, the SAP Service Name (please not also that the
sending and receiving name do not seem important; e.g. we left them as e- Work
and SAP). We left the ID empty and set the trace level to 3 (1, or even 0, is
recommended for production systems).
We added the required fields to the relevant forms:-
These forms are not usually seen by the user, and the relevant variables will be
shown on other forms as required.
The documentation states that you can include sub-tables (effectively 'fill' grids) as
well. To do this you will need some SQL skills. (Please note that we have not had
the opportunity to test this yet).
POINTS TO NOTE
The documentation states that you should assign the return from this call to
%Category, but we are uncertain if this is a requirement (we believe it used to
be). The IW item supplied forces the assignment to %Category, which is a
restriction which seems to be obsolete. The IW item does not allow you to select
the relevant form, and this must be typed in manually, however this can be easily
remedied by updating the supplied Collection.
USING THE PROCESS
Select the start action:-
Enter the Job Number:-
The result is displayed:-
If an error occurs, the error message is displayed in the SAPMessage memo
field:-
CALLING FROM SAP
To make a call from SAP, nothing more is required on the MBPM side than to
expose an Action as a Web Service. This is in itself very simple:-
You select the process, and if not a blank form, the Action, and a name for the
WSDL file, (where it will go) and the Web Server (host) name. You can then use
the WSDL file it created in the specified location from the SAP side of the
Connector as described in the Developer's Guide.
1. Background
