TimeXtender Internal Gateway

Internal Gateway is a configuration of the TimeXtender gateway that causes the gateway to not connect to the cloud environment for executions*. Instead, an internal gateway is set up to communicate through an External gateway on the same domain** through TCP communication and the External gateway handles communication to the cloud environment.

Installing Internal Gateway 

1. Installing on a new machine
   1. Download TimeXtender Gateway from the web
   2. Use the TimeXtender MSI to install the gateway
2. Installing on the same machine as External Gateway
   1. Copy and paste the folder "C:\Program Files (x86)\exMon Gateway" to for example "C:\Program Files (x86)\exMon Internal Gateway"
   2. Execute the batch file ResetConfiguration.bat as an administrator

Configure Internal Gateway

Configuring Internal Gateway is the same whether you install it on a new machine or the same as hosts an External Gateway.

1. Open the Gateway Desktop Client
2. Authenticate and select your service if applicable
3. Select Internal Gateway in the wizard that pops up
4. Connect to an external gateway using the machine name and port(default 8522) of the external machine
5. Select port name for your internal gateway. If it is on the same machine as external, default 8522 is likely taken so you need to change to another port like 8521

Setting up Data Providers in Internal Gateway

Internal Gateway is not able to communicate to the cloud in any way, so when you set up a Data Provider or enable Execution connection on the internal gateway nothing happens in the cloud environment of TimeXtender O&DQ.

What does happen however is that these objects become available for the External Gateway that you connected to, so when you have set up your objects in the Internal Gateway you can now switch to your External Gateway.

In your External Gateway, you can now switch from objects using Local Gateway to using your Internal Gateway, and for Data Providers you can now select Data Providers on your Internal Gateway.

You need to configure the Execution Connection on your External Gateway to run on the Internal Gateway instead of Local.

What is now happening behind the scenes is that TimeXtender can use the objects in External Gateway to execute through the Internal Gateway.

* The Gateway Desktop client does still contact login.exmon.com to authenticate the user when he logs in to configure Data Provider connections

** This can even be an External Gateway on the same machine. This allows the user to set up different Windows users for different UATs