Gentrack Integration Resources

Migrating from Data Gateway to Direct Connection (Junifer)

Overview

This guide describes migrating from a Data Gateway setup to Direct Connection for Junifer. In Direct Connection mode, Junifer communicates directly with Gentrack Cloud Integration Services (GCIS) over the internet using your proxy server.

Prerequisites

Before starting, ensure:

  1. Your Junifer server has a CA-signed SSL certificate with a fully qualified domain name
  2. Your Junifer server is accessible from the internet
  3. You have administrator access to Junifer
  4. You have administrator access to the Integration Portal
  5. You know your proxy server configuration

GCIS IP Addresses

Configure firewall rules to allow inbound traffic from these GCIS IP addresses:

RegionIP Address 1IP Address 2
AU52.65.53.113.236.220.175
UK35.176.213.7518.130.141.102

Proxy Configuration

If your network requires a proxy server:

  1. Configure your proxy to allow outbound HTTPS connections to:

    • https://api-uk.integration.gentrack.cloud (UK region)
    • https://api-au.integration.gentrack.cloud (AU region)
    • https://uk.id.gentrackcloud.com (UK region)
    • https://au.id.gentrackcloud.com (AU region)
  2. Ensure the proxy does not interfere with SSL/TLS certificate validation

  3. Document your proxy settings (host, port, authentication if required) for use in Junifer configuration

Migration Steps

Step 1: Select Tenant in Integration Portal

  1. Log into the Integration Portal as a user with administrator access.

  2. In the Integration Portal, open the Tenants page from the Manage Access section.

  3. Select the tenant you want to migrate from Data Gateway to Direct Connection.

  4. Click Connect tenant button and fill out the form with the following settings:

    • Product type - Junifer
    • Core Product URL - Full URL of the Junifer API server. This URL must be accessible by GCIS over the internet.
    • Use Gentrack Cloud identity authentication - Not applicable for Junifer
    • Username and Password - The API user credential of Junifer. Leave empty if API authentication is not enforced in Junifer. You must first verify that you can use the provided user credentials to call the Junifer API directly.
    • Tenant is hosted in Gentrack Cloud - Set based on your hosting arrangement
    • Data Gateway URL - Leave empty for Direct Connection
    • Verify SSL certificate - Turn ON to verify the Junifer server’s SSL certificate
  5. Click Connect Tenant.

  6. Enable Billing under Services. Copy Client ID and Client Secret for later configuration in Junifer.

  7. Copy the Tenant Id for later configuration in Junifer.

The data you entered is validated by performing a complete trip between Gentrack Cloud and Junifer. An error will be displayed if the connection was unsuccessful. Resubmit the form once the information has been corrected.

Step 2: Create Event Subscriber in Junifer

  1. Log into Junifer as a system administrator.

  2. Navigate to the API event subscribers configuration.

  3. Create a new event subscriber with the following settings:

    • Name - Integration Services
    • GCIAM Authentication - Select this option to use GCIAM for authentication
  4. Configure the following GCIAM authentication properties:

    • gciam_endpoint - Select based on your region:
      • UK: https://uk.id.gentrackcloud.com/v1/token
      • AU: https://au.id.gentrackcloud.com/v1/token
    • gciam_tenantid - Tenant Id from Step 1
    • gciam_username - Client ID of the Billing service from Step 1
    • gciam_password - Client Secret of the Billing service from Step 1
  5. Configure the Delivery URL:

    • UK region: https://api-uk.integration.gentrack.cloud/v1/events
    • AU region: https://api-au.integration.gentrack.cloud/v1/events
  6. Add event subscriptions for all relevant events including:

    • Bill Accepted
    • Payment Accepted
    • [Add other relevant events based on your integration requirements]
  7. Save the event subscriber configuration.

Step 3: Test Event Subscriber

  1. In Junifer, use the test functionality for the event subscriber.

  2. Verify the test event is successfully delivered to GCIS.

  3. If the test fails:

    • Verify GCIAM authentication properties are correct
    • Check Delivery URL matches your region
    • Verify proxy configuration allows outbound connections
    • Check Junifer application logs for errors
    • Confirm firewall rules allow outbound HTTPS to GCIS endpoints

Step 4: Verify Connection

  1. Log into the Integration Portal as a user with administrator access.

  2. In the Integration Portal, open the Tenants page from the Manage Access section.

  3. Click the tenant to open tenant details page.

  4. Click the Test Connection button in the Connection Details section.

  5. Wait a few seconds. The connection test verifies:

    • Network connectivity from GCIS to Junifer
    • API call to Junifer using the configured credentials
  6. If the test fails, verify:

    • Junifer server is accessible from the internet
    • SSL certificate is valid and CA-signed
    • Firewall rules allow GCIS IP addresses
    • Proxy configuration is correct (if applicable)
    • API user credentials are correct (if API authentication is enabled)

Step 5: Test Event Delivery

  1. In Junifer, trigger a test event (for example, create a bill or accept a payment).

  2. Verify the event is delivered to GCIS:

    • Check Integration Portal for event activity
    • Verify connectors or integrations receive the event
  3. If events are not delivered:

    • Verify event subscriber configuration
    • Check Junifer application logs
    • Verify proxy configuration allows outbound connections
    • Confirm GCIAM authentication properties are correct
    • Verify event subscriptions are configured

Step 6: Remove Data Gateway Components

After verifying Direct Connection is working:

  1. Log into the Integration Portal.

  2. Navigate to the Tenants page.

  3. Click the tenant and verify it shows Direct Connection (not Data Gateway URL).

  4. If you have a Data Gateway server that is no longer needed:

    • Stop the Data Gateway service
    • Uninstall the Data Gateway software
    • Remove firewall rules specific to Data Gateway
    • Decommission the Data Gateway server
  5. Remove any monitoring or alerting configured for Data Gateway.

Troubleshooting

Connection Test Fails

  • Verify Junifer server URL is accessible from the internet
  • Check SSL certificate is valid and CA-signed with FQDN
  • Confirm firewall rules allow GCIS IP addresses
  • Verify proxy configuration (if applicable)
  • Check API user credentials if API authentication is enabled

Events Not Delivering

  • Verify GCIAM authentication properties are correctly configured
  • Check Delivery URL matches your region
  • Verify proxy allows outbound HTTPS to GCIS endpoints
  • Check Junifer application logs for errors
  • Confirm event subscriptions are configured for the events you expect
  • Verify event subscriber is enabled

Authentication Errors

  • Verify Client ID and Client Secret are correct
  • Check Tenant Id matches the tenant in Integration Portal
  • Verify gciam_endpoint URL matches your region
  • Confirm Billing service is enabled in Integration Portal
  • Check GCIAM endpoint is accessible from your network
Last updated on 25 Nov 2025