Profiled Service Call builder inputs for a local service

Portlet Factory, Version 6.1.2

Profiled Service Call builder inputs for a local service

This topic describes the inputs that the Profiled Service Call builder takes for a Local (model-based) service.

Table 1. Local service inputs
Input Name Description
Name Name for this builder call. The WebSphere Portlet Factory Designer displays this name in the builder call list.
Service Call Type Enable the local radio button to configure a service call to an HTTP service.
Service Call Arguments and Endpoint URL

Argument(s) named according to WSDL document The builder call editor displays the argument names for the selected operation as inputs to the Service Call.
You can use the Reference Chooser to specify an appropriate value from a model element or you can enter a text string directly. ("Type" does not apply to local services.)
WSDL Inputs

Operation (optional) Enter the service operations in by hand or use an indirect reference to point to the operations.
Local Model Inputs

Model Name Use the Model Chooser to select the model that contains the method exposed as a web service.
Note: Such a model must contain a Web Service Enable builder call.
Advanced Inputs

(optional) Log request/response Enable this check box if you want to display the SOAP request and response in the application server's console as well as log this information in WebSphere Portlet Factory's log file.
Dummy/Stub result Supply a value to be returned instead of actually calling the service.
For example, you might enable this functionality for testing purposes during application development so the model this builder is in can run without exercising the service.
Continue on Error Enable this check box to allow the model to continue to run even if this builder returns an error during runtime generation.
For example, a regen error would occur if the service was unavailable.
AutoCreate Input Vars Enable this checkbox to force the builder regen to create input variables for each of the service call inputs.
You can see these variables in the Variable section of the WebApp Tree" view after hitting Apply on the builder call, the names being in the form of, "buildername_argN_inputname".
These variables do not appear in the builder Call List, but you can get and set their values in methods and they are listed in the Reference Chooser.
Note: To preserve pre-existing values in the builder input fields, request parameter inputs with existing content do not get automatically populated with the auto created variable names To get the automatically created input variable names into the request parameter inputs clear out the current value, and then either choose the new variable with the picker for that input field, or just un-check and re-check the AutoCreate Input Vars check box. This technique allows hard coded and auto-created variables to be used in the inputs without loss of pre-existing typed in values.

Parent topic: Profiled Service Call builder

Library | Support |

Input Name	Description
Name	Name for this builder call. The WebSphere Portlet Factory Designer displays this name in the builder call list.
Service Call Type	Enable the local radio button to configure a service call to an HTTP service.
Service Call Arguments and Endpoint URL
Argument(s) named according to WSDL document	The builder call editor displays the argument names for the selected operation as inputs to the Service Call. You can use the Reference Chooser to specify an appropriate value from a model element or you can enter a text string directly. ("Type" does not apply to local services.)
WSDL Inputs
Operation (optional)	Enter the service operations in by hand or use an indirect reference to point to the operations.
Local Model Inputs
Model Name	Use the Model Chooser to select the model that contains the method exposed as a web service. Note: Such a model must contain a Web Service Enable builder call.
Advanced Inputs
(optional) Log request/response	Enable this check box if you want to display the SOAP request and response in the application server's console as well as log this information in WebSphere Portlet Factory's log file.
Dummy/Stub result	Supply a value to be returned instead of actually calling the service. For example, you might enable this functionality for testing purposes during application development so the model this builder is in can run without exercising the service.
Continue on Error	Enable this check box to allow the model to continue to run even if this builder returns an error during runtime generation. For example, a regen error would occur if the service was unavailable.
AutoCreate Input Vars	Enable this checkbox to force the builder regen to create input variables for each of the service call inputs. You can see these variables in the Variable section of the WebApp Tree" view after hitting Apply on the builder call, the names being in the form of, "buildername_argN_inputname". These variables do not appear in the builder Call List, but you can get and set their values in methods and they are listed in the Reference Chooser. Note: To preserve pre-existing values in the builder input fields, request parameter inputs with existing content do not get automatically populated with the auto created variable names To get the automatically created input variable names into the request parameter inputs clear out the current value, and then either choose the new variable with the picker for that input field, or just un-check and re-check the AutoCreate Input Vars check box. This technique allows hard coded and auto-created variables to be used in the inputs without loss of pre-existing typed in values.