Data Gateways

Setting Up Data Gateways

By default the Data Gateway is installed together with Matrix42 Software Asset and Service Management. Therefore, it runs on the same server and has access to the network to which this server belongs.

If the Data Gateway should have access to some system or network which is not accessible to Matrix42 Software Asset and Service Management, the Data Gateway should be installed within this network. This way Matrix42 Software Asset and Service Management will be able to exchange data with corporate networks and external systems in compliance with the relevant security policy.

Step 1: Registering the Data Gateway

• In Matrix42 UUX, open the Data Gateways search page under Administration > Integration.
• Click Add Data Gateway in the toolbar to create a new Data Gateway record.
• Fill in the General page of the Data Gateway dialog:
  • Organizational Unit, Cost Center, Location: If you create a new record, you can link it to the respective organizational unit, cost center, and location. For existing configuration items, you can create a link only by clicking Change Ownership in the action pane.
  • Runs on: Select the computer where the Data Gateway application will be installed.
  • Description: Provide additional details about this Data Gateway instance.
• Click Done to save the record and close the dialog.

Step 2: Downloading the Data Gateway

• In Matrix42 UUX, open the Data Gateways search page under Administration > Integration.
• In the action pane of the respective Data Gateway, click Download Data Gateway.
• DataGateway.zip will be downloaded.  

Step 3: Deploying the Data Gateway

• Copy the Data Gateway root folder to the computer where the gateway should be deployed (it is the computer that you have specified in the Runs on field of the new Data Gateway record) and go to the ...\DataGateway folder.
• If the Data Gateway will be run under an account which is not a Matrix42 Software Asset and Service Management account, Windows authentication cannot be used. Therefore, you should make changes to the Matrix42.DataGateway.exe.config file to configure basic authentication.
• Open the Matrix42.DataGateway.exe.config file and edit the connection Strings element to disable Windows authentication and enable basic authentication:

  <connectionStrings>
  
  <!-- Windows Authentication-->
  
  <!-- <add name="M42Services" connectionString="ServerName=domain.com;SPN=domain\username;UseHttps=true;"/>-->
  
  <!-- Basic Authentication-->
  
  <add name="M42Services" connectionString="ServerName=domain.com;User=DOMAIN\USER;Password=XXXXX;"/>
  
  </connectionStrings>​

• If the password should be encrypted, run the "Matrix42.DataGateway.exe -configure" command from a Command Prompt in Windows and enter the password in the Command Prompt window. As a result, the password in the Matrix42.DataGateway.exe.config file will be encrypted.
• To test the connectivity, run the "Matrix42.DataGateway.exe -test" command from a Command Prompt in Windows. As a result, a relevant message will notify you whether the connectivity test has been successful or not.
• Install the Data Gateway as a Windows service:
• To install the Data Gateway acting as a Local Service identity, run the "Matrix42.DataGateway.exe -install" command from a Command Prompt.
• To install the Data Gateway acting as a specific identity, run the "Matrix42.DataGateway.exe -install [DOMAIN\USER] [PASSWORD]" command from a Command Prompt.
• Start the Data Gateway service by running the "Matrix42.DataGateway.exe -start" command from a Command Prompt. 

Step 4: Configuring Data Providers and Scheduling Activations

In Matrix42 Workspace Management under Administration > Integration > Data Providers, configure the required Data Providers depending on the architecture of the target corporate network or data center. For example, it can be an AD server, the virtual infrastructure managed with Citrix XenServer, etc. For more information, see Built-In Data Providers.

After configuring the relevant Data Provider, you need to set the schedule for running engine activations that launch the Data Gateway. Usually, different Data Providers have different engine activations.