Web services
Every web service client that is imported to an iCore system also generates Workflow activities that are needed to call the operations of the web services. To use these activities in a Workflow, a reference must be added from the Workflow to the web service. Once the reference has been added, the activities representing the operations of the web service are added to the Toolbox.
If the web service operations use any complex types, the classes that have been generated for these are included in the Workflow when adding the reference. All types are defined in a namespace consisting of the web service target namespace combined with the web service version (with periods(.) replaced by underscores(_), for example MyService_1_1_0_32).
A web service consumer activity has fixed arguments as listed below. In addition to the fixed arguments, an argument for each of the input and output parameters of the webservice method is created.
Arguments
| Name | Type | Description |
|---|---|---|
| Endpoint address | Uri | Specifies the address of the endpoint on which to call the web service. If this argument is left empty, the default address will be used (i.e. the address that was retrieved when the web service entity was created) |
| Endpoint | Endpoint | Available for SOAP Web services only. Specifies the endpoint to send messages to along with binding configuration. |
| Credentials | ClientCredentials | Available for SOAP Web services only. Specifies the security configuration which the activity will use for the request. ClientCredentials can be created using VB expression or with the Create SOAP Client Security Configuration activity. |
| SecurityConfiguration | ISecurityConfiguration | Available for REST Web services only. Specifies the security configuration which the activity will make for the request. ISecurityConfiguration is created using the Create Rest Client Security Configuration activity. |
Remarks
When you use an activity provided by a SOAP Web service client, the template in the Workflow is a Sequence containing two activities:
- A Create Endpoint from Configuration activity.
- A generated Web service client activity.
In the first activity, an Endpoint can be configured with a configuration editor. This Endpoint can then be used in the provided Web service client activity. Alternatively, it is possible to specify the Endpoint directly in the Web service client activity via a VB expression.
The following example shows what a VB expression looks like when a binding is created with a BasicHttpBinding:
New System.ServiceModel.Endpoint() With {.Binding = New System.ServiceModel.BasicHttpBinding(), .AddressUri = New System.Uri("http://localhost:1337/Math.asmx")}
For more information on the binding types that can be used in an Endpoint, see Binding.
See Also
Workflow Designer
Workflow activities
Create REST Client Security Configuration
Create SOAP Client Security Configuration
Create Endpoint From Configuration