JSM_BINDSCRIPT

This activity executes a LANSA Integrator JSM binding script.  JSM binding scripts may be executed to perform many varied tasks, such as:

• Calling a SOAP web service
• Reading and writing JSON-formatted documents

 

JSM_BINDSCRIPT is an iterator activity.  The Processing Sequence directives nested beneath the activity are repeated each time that a Perform iteration directive is encountered in the JSM binding script.  This affords the Processing Sequence an opportunity to:

• Receive and process the values of Processing Sequence variables set by the last script "iteration", and/or
• Set the values of Processing Sequence variables that will be used in the next script "iteration", and/or
• Control the flow of execution of the script by setting the values of the ITERATIONPROCEED and/or ITERATIONBRANCHTO parameters.

 

Note that no iterations will be performed if the script does not contain or encounter a Perform iteration directive.

Note that a Processing Sequence that uses the JSM_BINDSCRIPT activity must use the same variable and variable list names defined in the JSM Binding Script to exchange data with the script.  You may refer to the Variables Used tab of the JSM Binding Script definition to identify the processing sequence variable and variable list names that are referenced by a JSM Binding Script.

JSM Binding Scripts are an advanced feature of LANSA Composer.  For more detailed information on designing solutions that make use of JSM Binding Scripts, refer to the following:

JSM Binding Script Configuration

 

INPUT Parameters:

JSMBINDCONFIG: Required

This parameter must specify the name of a JSM Binding Script Configuration.  The configuration specifies the LANSA Integrator binding solution to execute and includes definitions of how data items are passed to and from the solution using processing sequence variables.

OUTPUT Parameters:

ITERATIONLABEL: Optional

Each time that a Perform iteration directive is encountered in the JSM binding script, the Processing Sequence directives nested beneath the activity are executed.  Because there can be more than one Perform iteration directive in the JSM binding script, the activity sets this output parameter to the line label (if any) associated with the current Perform iteration directive.  This enables the Processing Sequence to perform different actions upon each iteration according to the ITERATIONLABEL value.

INPUT and OUTPUT Parameters:

ITERATIONPROCEED: Optional

Each time that a Perform iteration directive is encountered in the JSM binding script, the Processing Sequence directives nested beneath the activity are executed.  Your solution can set the value of this parameter to 'N' (no) if further iterations are not required – for example, if it has processed all the available data for the JSM binding script.  In this case, the JSM_BINDSCRIPT activity will branch to the On nil result label associated with the Perform iteration directive that caused the iteration.

ITERATIONBRANCHTO: Optional

Each time that a Perform iteration directive is encountered in the JSM binding script, the Processing Sequence directives nested beneath the activity are executed.  By default, the JSM Binding Script execution continues with the next script line when the iteration processing is completed.  However your Processing Sequence can set the ITERATIONBRANCHTO parameter value to specify the Line label of another line to which the JSM binding script will branch.  If you use this feature, you must set this parameter value to a Line label that is defined in the script, or you can use one of the special values *END, *NEXT or *ERROR.

Note that the value of the ITERATIONBRANCHTO paramer is only used if the ITERATIONPROCEED parameter is NOT set to 'N' (no).

The ITERATIONBRANCHTO parameter is intended for use in more advanced solutions.  If you are using ITERATIONBRANCHTO, you probably do not need to also set the value of ITERATIONPROCEED.