INUBIT IS Connector

Usage

The INUBIT IS Connector supports remote workflow execution.

The remote workflow execution can be achieved by creating one or more of the following INUBIT IS Connector modules.

On the source Process Engine: Configure a medium INUBIT IS Connector and provide the details in the Connection data dialog.

An INUBIT IS Connector is restricted to call only another INUBIT IS Connector.
On the target Process Engine: Configure an INUBIT IS Connector as input listener.

Dialog Descriptions

Dialog Function

In this dialog, you define the connector’s function. The available functions depend on the connector’s configuration:

Input listener connector: Listener connector which can be called from a remote INUBIT IS Connector
Medium connector: Execute a workflow
Output listener connector: Save as file
Output connector:
- Execute a workflow: Data is sent and directly processed by a workflow.

Dialog Authentication

(For Input Listener Connectors only)

The dialog for the configuration of input listener connectors queries the access data for the INUBIT Process Engine with which a client has to authenticate itself in order to be able to send data to the INUBIT IS Connector.

Settings

Use static login data

Enter Login name 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.

To use credentials managed by the Credentials Manager, click the choose icon and choose an alias.
Check credentials

Static login data

An error message is displayed if no login name is given or if the passwords differ from each other. Otherwise, a success message is displayed.

Password Manager

It is checked whether a value is entered in the Alias field.

Dialog Connection Data

(For medium connectors only)

In this dialog you enter the access data for the remote INUBIT Process Engine from which the INUBIT IS connector is to fetch data.

Base configuration

Server URL

Replace localhost with the name or IP address of the INUBIT Process Engine.
SSL

For the client and/or server authentication. Refer to Dialog SSL Configuration.

Authentication

Use static login data

Authentication for the INUBIT Process Engine. Enter Login name 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.

Connection test

Test connection

For testing whether the connection can be successfully established using your configuration.

Workflow

Name: Name of the workflow with which the connection is to be established.
System connector: Name of the system connector.

Test Workflow

Check workflow and module

For validating the workflow and module in the target IS:
- Validate if the workflow and module exist in the target IS.
- Validate if the workflow and module are active.
- Validate whether the module belongs to the specified workflow.
  
  When validation is complete, appropriate messages are displayed.

Dialog Output File/Files

(Output listener connector)

You use the dialog to configure the writing of files.

Output file(s)

Directory

Name of the directory from which the connector is to receive files.
File name(s)

Name of the files or files that the connector is to receive. You can use wildcards when specifying the file name. Example: /Inputdata/*.xml.
Use wildcard content of the preceding file or FTP connector

If selected, the wildcard content generated by a previously executed file or FTP connector is used.

Example: Test*.xml was specified in the File name field in the configuration of a previously executed file connector. The file connector forwarded a file with the name Test5.xml as the output message. In this case, the wildcard content is the digit 5. If you have also specified a wildcard in the current connector (for example, Output*.xml), the digit 5 is entered in the position of the wildcard.
Use the file name of the previously executed file connector

If selected, the file name used by a previously executed file connector is used. Example: Test.xml was specified in the Directory and file name field in the configuration of a previously executed file connector. The file connector forwards a file called Test.xml as the output message. This file name is also used here.
Add data to file

If you select this option, the specified file is not overwritten each time the output connector is executed. Instead, the output message is appended to the file with each execution. This can be useful if you want to log cumulative log data in a file.
Overwrite possible existing file

This option is selected by default. If a file with the same name exists, it is overwritten.
Set input message additionally to output message

If selected, the input file is forwarded to the subsequent module. Depending on the size of the input files, selecting this option can affect the performance of your system.