An Azure Service Bus JMS connection stores the information that Oracle GoldenGate for Distributed Applications and Analytics uses to connect to Azure Service Bus JMS.

You can use the connection with Replicat to deliver transactional changes to Azure Service Bus JMS. After you create and validate the connection, you can reuse it across multiple Oracle GoldenGate for Distributed Applications and Analytics processes.

The connection stores the Azure Service Bus JMS connection information, authentication settings, security configuration, and optional runtime settings independently of the process configuration.

Before creating an Azure Service Bus JMS connection, ensure that you have the following:

• An Oracle GoldenGate for Distributed Applications and Analytics deployment.
• Network connectivity between the Oracle GoldenGate for Distributed Applications and Analytics deployment and Azure Service Bus JMS.
• The Azure Service Bus JMS endpoint information.
• Authentication credentials required by your Azure Service Bus JMS deployment.
• JNDI configuration information if you use JNDI to obtain JMS resources.
• The required Azure Service Bus JMS client libraries. Download the supported client libraries by using the Dependency Downloader for Azure Service Bus JMS.
• Common runtime settings, such as the runtime classpath, configured to reference the downloaded client libraries.
• Proxy information if the Oracle GoldenGate for Distributed Applications and Analytics deployment accesses Azure Service Bus JMS through an HTTP proxy.

Use the Add Connection page to create an Azure Service Bus JMS connection.

Procedure

1. In the navigation menu, select DB Connections.
2. Click Add Connection.
3. In Connection Alias, enter a unique name for the connection.
4. From Technology Type, select Azure Service Bus JMS.
5. In the Technology Settings section, provide the Azure Service Bus JMS connection information.
   Configure the following technology settings:

   • Use JNDI – Specifies whether Oracle GoldenGate for Distributed Applications and Analytics uses JNDI to obtain JMS resources.
   • Connection URL – Specifies the connection URL for the Azure Service Bus JMS endpoint. Configure this field when Use JNDI is disabled.
   • Connection Factory – Specifies the JMS connection factory. Configure this field when Use JNDI is disabled.
   • Username – Specifies the user name used to authenticate with Azure Service Bus JMS.
   • Password – Specifies the password associated with the user name. This field is treated as sensitive information and is displayed as a password field.

   Note:

   When Use JNDI is enabled, Oracle GoldenGate for Distributed Applications and Analytics uses the JNDI configuration instead of the direct JMS connection settings.
6. Configure the JNDI Settings section if Use JNDI is enabled.
   Configure the following JNDI settings:

   • JNDI Connection Factory – Specifies the JNDI name of the JMS connection factory.
   • JNDI Provider URL – Specifies the URL used to contact the JNDI provider.
   • JNDI Initial Context Factory – Specifies the fully qualified Java class name that implements the initial context factory.
   • JNDI Security Principal – Specifies the principal used for JNDI authentication.
   • JNDI Security Credentials – Specifies the credentials used for JNDI authentication. This field is treated as sensitive information.
7. Configure the Security Settings section, if required.
   Configure the following security settings:

   • Security Protocol – Specifies the communication protocol. Supported values are PLAIN, TLS, and MTLS.
   • Truststore – Upload the truststore file used to validate the server certificate. Configure this field when Security Protocol is TLS or MTLS.
   • Truststore Password – Specifies the password associated with the truststore.
   • Keystore – Upload the keystore file containing the client certificate and private key. Configure this field when Security Protocol is MTLS.
   • Keystore Password – Specifies the password associated with the keystore.

   Note:

   Configure only the security properties required by the selected security protocol.
8. Configure Common Settings, if additional runtime configuration is required.

   Configure the following common settings:

   Classpath – Specifies the runtime classpath used to load the required Azure Service Bus JMS client libraries. You can use Dependency Downloader to download client libraries.

   Note:

   • Download the supported Azure Service Bus JMS client libraries by using the Dependency Downloader for Azure Service Bus JMS.
   • Configure the runtime classpath to reference the downloaded client libraries before starting the Replicat process.
9. (Optional) Configure Proxy Settings if the Oracle GoldenGate for Distributed Applications and Analytics deployment accesses Azure Service Bus JMS through an HTTP proxy.

   Configure the following proxy settings:

   • Proxy URL – Specifies the URL or host name of the proxy server used to access Azure Service Bus JMS.
   • Proxy Port – Specifies the port number of the proxy server.
   • Proxy Username – Specifies the user name for proxy authentication, if required.
   • Proxy Password – Specifies the password for proxy authentication. This field is treated as sensitive information.
   • Truststore – Specifies the Java truststore file that contains the certificate authority (CA) certificates used to validate the proxy server certificate, when required.
   • Truststore Password – Specifies the password associated with the truststore.
   • Keystore – Specifies the Java keystore file containing the client certificate and private key used for client authentication, when required.
   • Keystore Password – Specifies the password associated with the keystore.
   • SSL Key Password – Specifies the password protecting the private key stored in the keystore when it differs from the keystore password.

   Note:

   Configure the proxy and SSL settings only if the Oracle GoldenGate for Distributed Applications and Analytics deployment accesses Azure Service Bus JMS through a proxy that requires authentication or TLS. If the deployment has direct network connectivity to Azure Service Bus JMS, leave the Proxy Settings blank.
10. Click Submit.
11. On the DB Connections page, click DBLOGIN to validate the connection.

    Note:

    A successful DBLOGIN validates only the saved connection information. It does not validate the Replicat configuration or Azure Service Bus JMS Handler configuration. After successful validation, the connection is available for selection during Replicat creation.

Use the Connection with Replicat

After the Azure Service Bus JMS connection has been successfully validated:

1. Create or edit a Replicat.
2. Select Azure Service Bus JMS as the target technology.
3. Select the validated Azure Service Bus JMS connection.
4. Complete the remaining Replicat configuration.
5. Create and start the Replicat.