After you set up the Initial Gateway (See Topic 3.3.2), you must configure it. This includes adding credentials for access to Workflow Server which is the first level of authentication.

Prerequisites:

• Before provisioning a repository, ensure that the Galaxy security is set.
• After you configure the Gateway Object and use it for creating events, do not change its name.

To configure the Gateway:

1. Double-click the instance that you created while setting up the initial gateway.

   For example, double-click WorkflowGateway_001 in the Deployment section.

2. In the Gateway Configuration tab that opens, enter the values for the following fields:
   • Unique Environment Name: The server is capable of communicating with multiple Galaxies in a single process. In a multi-Galaxy environment, you cannot ensure the uniqueness of the Galaxy name. An Unique Environment Name is used as work around for this.
     
     In an environment with a single Galaxy, or multiple Galaxies with unique names, the Unique Environment Name can be the same as the Galaxy name.
     
     In an environment with multiple Galaxies where different Galaxy environments share the same name, each separate Galaxy environment needs to be provided with an unique name while connecting to the server. An unique name is required to avoid naming conflicts.
   • Server Address: Address of the server.
   • Authentication User Domain: User domain of the server.
   • Authentication User Id: User ID of the server.
   • Authentication User Password: Password for the user name of the server.
     
     
     
     
     
3. Click Test Connection to verify the authentication.
   • If Test Connection is successful, the Repository Name field is populated with the available repositories.
   • If authentication is not successful, verify the credentials.
4. In the Repository Name field, select the workflow repository to connect to. The Provision window appears.
5. Add credentials to access the workflow repository which is the second level of authentication. To authorize and provision access of and mapping to the workflow repository, perform the following steps:

   Workflow Repository Authentication Info

   1. In the Providers field, select Active Directory or AVEVA Workflow Management List based on the provider for which the workflow repository is created.
   2. Enter the user name and password details based on the user provider. For the default user name and password, contact the technical support team or refer the Get Started Guide in the ISO file of AVEVA Workflow Management.

      The user must have administrator rights on the workflow repository.

   3. Select Use AD Provider same as Repository to leverage Active Directory users instead of Galaxy users.

      

6. For Inbound Connection Authentication Info, enter the credentials of GR Node in the Authentication User Domain, Authentication User Id, and Authentication User Password fields.
7. Click Authorize & Provision.

   The repository is now provisioned to be connected to the Galaxy. The repository and galaxy are now connected.

The Use Active Directory Service Provision check box appears only if all the following conditions are satisfied:

1. The Galaxy User security is Operating System user or Operating System group.
2. The repository to provision is created using the Active Directory authentication.
3. The Galaxy user and repository user domain are same.

The details that you enter in the Inbound Connection Info tab is the same as the General inbound tab as shown in the following image:

Using the Advanced Tabs

Advanced tabs are available for Inbound and Outbound Connection settings, for more control on the Gateway configuration.

Outbound Connection Info: Advanced Options

The following image shows the fields of the Outbound Connection Info tab.

The Outbound Connection Info tab contains the following fields:

• Outbound Connector Port: This field can be edited after you provision the workflow repository for the Galaxy.
• Outbound Connector Binding: Binding protocol for the connection, preferably used when Workflow Server is within the same network. Choose from the following options:
  • TCP: Default binding protocol for the connection, preferably used when Workflow Server is within the same network.
  • HTTPS: Secure connectivity over the Internet.
• Operation Timeout: Time period after which the request made to the Workflow server does end if not connected.
• Connection Life Time: The duration for which the of the connection between the Galaxy and the Workflow Server lasts.
• User Provider Name: Repository user provider, either Active Directory or Skelta List.
• Theme: Theme of the repository.
• Enterprise Console Site URL: The URL used to access the workflow repository from the Workflow Server.
• Repository Auth User Id: Captured during and displayed during provisioning.
• Repository Auth User Password: Captured during provisioning.

Inbound Connection Info: Advanced Options

The following image shows the fields of the Inbound Connection Info tab.

The Inbound Connection Info tab contains the following fields:

• Inbound Connector Host: Default runtime node where the Gateway object is deployed.
• Inbound Connector Port: Connection Port by AVEVA Workflow Management to fetch any data from Galaxy.
• Inbound Connector Binding: Binding protocol for the connection, preferably used when Workflow Server is within the same network. Choose from the following options:
  • TCP: Default binding protocol for the connection, preferably used when Workflow Server is within the same network.
  • HTTPS. Secure connectivity over the Internet.
• Operation Timeout: Time period after which the request made from the Workflow server to the Galaxy will end, if not connected.
• Connection Life Time: Time period that the connection will last between the Workflow Server and the Galaxy.
• Throttling, Max Concurrent Calls: Connector service properties, the maximum number of messages that can actively be processed. Each client channel can have one pending message that does not count against this total until the service begins to process it. Increase this value if you want your service to process a larger message load.
• Throttling, Max Concurrent Instances: Connector service properties, the maximum number of InstanceContext objects in a service that can be executed in a single instance.
• Throttling, Max Concurrent Sessions: The maximum number of sessions that a service can accept at one time.

Sync Security Info: Advanced Options

Use this tab to synchronize users, roles, and security groups to the Workflow Server. Set the refresh interval for automatic synchronization in a specific time-frame. To synchronize, click Synchronize.

After changing the Advanced options, you save the object. You can now access the Enterprise Console functionality from the Workflow Toolbox.