Invoked Service Tab

(Medium/output Connector)

In this tab, you have the following options:

WSDL data

Load WSDL from
- File
  
  Enter the path of the WSDL file if it is available in a file system. Alternatively, you can click the button in order to navigate to the WSD file.
- URL
  
  Enter the URL of the WSDL file if it is available via a URL.
  
  In the group Web Service in the same dialog, activate in parallel the Authentication required option in order to attach authentication information to the WSDL request.
- SSL
  
  Opens a dialog, where you enter data for a secure connection.
- Show published services
  
  Opens the website displaying all active web services provided by the INUBIT Process Engine.
Load WSDL file

A click on the button loads the given WSDL into the Connector and displays it in the WSDL area.

WSDL

In this area, the loaded WSDL file is displayed. You can edit, store and search the WSDL file.

Web Service

Service/port

Name and port of the Web Service that is to be invoked and was selected from the list.
Address

One WSDL file can contain more than one address. Select the address at which the Web service is to be called.
SSL button

Opens the dialog in which you configure the secure connection settings.

Refer to Dialog SSL Configuration
Invocation is an asynchronous response (callback)

Activate this option, if you want to use this Web Service Connector instead of a Reply module in a workflow containing an asynchronous Web Service for returning the response to a callback listener. If this option is activated, the address is taken over from the variable WSReplyTo.

Refer to Offering an Asynchronous Web Service

Authentication required

Activate this option, if the server on which the Web service is published requires an authentication.

If this option is activated, the authentication information is used for both the Web service call and for loading the WSDL.

Method

Select the desired method for HTTP authentication. Basic Authentication is the default method. If the option Automatic (Digest/NTLM/Basic Authentication) is selected, the authentication method must be determined by message exchange between the connector and the target server.
Domain (Only for method Automatic)

Enter the Windows domain for the NTLM method.

User credentials

Use static login data
- Login name/Password
  
  If the server requires an authentication, enter the username and password.
Select from Credentials Manager

For authentication, you can also use credentials managed by the Credentials Manager.

Refer to Using the Credentials Manager for Authentication

Authorization

(only for medium and output connector)

Use OAuth2 Authorization

Activate this option to use the OAuth2 authorization.

If the Use OAuth2 Authorization option is selected, OAuth2 authorization will have priority over the settings in the Authentication required section.

Grant Type
- Client Credentials: Recommended for INUBIT because no user interaction is required.
- Password Credentials
- Custom: Select this option to configure any other grant type (e.g. refresh token flow, implicit flow)
Access Token URL

Insert the URL of the OAuth server. In addition, you can specify whether HTTP request should be sent via GET or POST.

Parameters

Add the parameters the selected grant type requires. You can find out which of these are in the documentation of the OAuth server you are using.

The parameter table can hold any number of entries.

All parameters configured in the module wizard are available as module properties with the prefix OAUTH_PROPERTY for use in the variable mapping. Variable mapping can only be used to overwrite properties that were previously set in the wizard. If further parameters are to be set via variable mapping, they must first be entered in the table via the module wizard (with empty or placeholder value).

Receive response asynchronously/send separate reply address

Activate this option if the response of the invoked Web Service should be sent asynchronously to a callback listener connector.

Reply URL (wsa:ReplyTo)

This field is preset with a URL containing the connector’s name you are just creating and the suffix Callback.

This URL is needed for the communication between the invoking module and the callback listener. It corresponds to the service URL of the callback listener module. You need to adjust the URL manually if the service URL of the callback listener module has changed.