Skip to main content

Connections for Integrations

The JAMS Connection Store lets you save connection information for certain integrations. You can then specify the Connection in the Job.

You can configure connections for the following:

Adding a Connection for Amazon EC2​

You can create a Connection Store item for connecting to an EC2 instance. Before you create the Connection, ensure you have the following:

  • The Instance ID
  • The Region
  • A Credential in JAMS to store the Access Key ID and Secret Access Key from AWS Identity and Access Management (IAM) for the user associated with the EC2 instance. See Credentials for more information.

You can then use this connection in the Job properties of a Job created from the AmazonEC2 Execution Method. See Amazon EC2 for more information.

  1. Click Execution from the main menu.
  2. Click Connections.
  3. Click Add.
  4. In the Connection Name field, enter a name for the connection.
  5. In the Connection Type field, select Amazon EC2.
  6. Click Save and Continue to Edit.
  7. Click the Properties tab.
  8. In the Amazon EC2 Credential field, select the JAMS Credential that has the information to authenticate with the EC2 instance.
  9. In the Amazon EC2 Instance Id field, enter ID of the EC2 instance you want to connect to.
  10. In the Amazon EC2 Region field, enter the region, such as us-east-2, for the EC2 instance.
  11. Click Save.

Adding a Connection for Apache Airflow​

You can create a Connection Store item for connecting to Apache Airflow. Before you create the Connection, ensure you have the following:

  • Log in credentials for Apache Airflow.
  • The name or IP address of the Apache Airflow server.
  • The port your Apache Airflow server is using for the REST API. The default is 8080.

Before you create this Connection, create a Credential in JAMS to store the username and password for Apache Airflow. The Logon As field stores the username and the two password fields save the password. See Credentials for more information. You can then use this connection in the Job properties of a Job created from the Airflow Execution Method.

  1. Click Execution from the main menu.
  2. Click Connections.
  3. Click Add.
  4. In the Connection Name field, enter a name for the connection.
  5. In the Connection Type field, select Airflow.
  6. Click Save and Continue to Edit.
  7. Click the Properties tab.
  8. In the Server Name field, enter the name or IP address of the Airflow server.
  9. In the Airflow Credential field, select the JAMS Credential that has the username and password logging in to Airflow.
  10. In the Airflow Port field, enter the port that is used for the Airflow REST API. The default is 8080.
  11. Click Save.

Adding a Connection for an Azure Blob​

You can create a Connection Store item for connecting to an Azure Blob. You will need the following from Azure:

  • Tenant ID
  • Client ID
  • Client Secret
  • Storage Account Name

You can then use this connection in the Job properties of a Job created from the AzureBlob Execution Method.

Before you create this Connection, create a Credential in JAMS to store the Client Secret value from Azure in the Password fields. The Logon As field can be left empty. See Credentials for more information.

  1. Click Execution from the main menu.
  2. Click Connections.
  3. Click Add.
  4. In the Connection Name field, enter a name for the connection.
  5. In the Connection Type field, select Azure Blob.
  6. Click Save and Continue to Edit.
  7. Click the Properties tab.
  8. In the Client Id (Application ID) field, enter the Client Id of your registered application in Azure.
  9. In the Storage Account Name field, enter the name of the storage account.
  10. In the Tenant Id field, enter the Tenant Id to identify your Azure instance.
  11. In the Azure Credential field, select the JAMS Credential that has the password-like key (client secret) used to authenticate to Azure.
  12. Click Save.

Adding a Connection for Azure Data Factory​

You can create a Connection Store item for connecting to Azure Data Factory. You will need the following information from Azure:

  • Tenant ID
  • Client ID
  • Client Secret
  • Subscription ID

You can then use this connection in the Job properties of a Job created from the ADFPipelineRuns Execution Method to run Azure Data Factory Pipelines.

Before you create this Connection, create a Credential in JAMS to store the Client Secret value from Azure in the Password fields. The Logon As field can be left empty. See Credentials for more information.

  1. Click Execution from the main menu.
  2. Click Connections.
  3. Click Add.
  4. In the Connection Name field, enter a name for the connection.
  5. In the Connection Type field, select Azure Data Factory.
  6. Click Save and Continue to Edit.
  7. Click the Properties tab.
  8. In the Client Id (Application ID) field, enter the Client Id of your registered application in Azure Active Directory.
  9. In the Subscription Id field, enter the Azure subscription where the Azure Data Factory resides.
  10. In the Tenant Id field, enter the Tenant Id to identify your Azure Active Directory instance.
  11. In the Azure Credential field, select the JAMS Credential that has the password-like key (client secret) generated when registering the application.
  12. Click Save.

Adding a Connection to an Oracle Database Server​

This option is available only if the Oracle Integration has been installed.

Ensure you have created a Credential within JAMS that contains the credentials for connecting to the Oracle database.

  1. Click Execution from the main menu.
  2. Click Connections.
  3. Click Add.
  4. In the Connection Name field, enter the name, such as OraDatabase.
  5. In the Connection Type field, select Oracle.
  6. In the Description field, enter a description.
  7. Click Save and Continue to Edit.
  8. Prepare your Oracle Connection String to the Oracle Database. Within the following string, replace the following:

    HOST with the Banner/Oracle database host name.
    SID with the Banner/Oracle database service name.
    Orac(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <HOST>)(PORT = 1521))(CONNECT_DATA = (SERVICE_NAME = <SID>)));
note

After updating the HOST and SID, copy the Connection String because you need this to update the Connection String field. Use tnsnames.ora as the reference to look up the required values for the Connection String.

  1. Click the Properties tab.
  2. Under Oracle, click the Connection String field and paste the Connection String.
note

Do not include Data Source = in the Connection String as JAMS automatically inserts it.

  1. In the Credential field, select a Credential in JAMS.
  2. Click Save.

Adding an SAP Connection​

Creating a Connection for SAP lets you configure the details once and reuse the connection within multiple Jobs and Sequence Tasks. Two connection options are available for SAP.

note

The SAP Integration Pack must be installed from the JAMS Installer before you can set up the SAP Group/Server or SAP Custom Application Server connections below.

Adding a Connection for SAP (Group/Server Selection)​

Select the SAP (Group/Server Selection) option if your site has two or more servers and you are using load balancing.

Before adding an SAP Connection, ensure a credential has been configured within JAMS that contains the information SAP username and password for connecting to the SAP Server.

  1. Click Execution from the main menu.
  2. Click Connections.
  3. Click Add.
  4. In the Connection Name field, enter the name, such as SAP.
  5. In the Connection Type field, select SAP (Group/Server Selection).
  6. In the Description field, enter a description.
  7. Click Save and Continue to Edit.
  8. Click the Properties tab.
  9. In the Credentials field, enter the SAP credential that was created in JAMS.
  10. In the Client ID field, enter the three-character ID. The values can be between 000 and 999.
  11. In the Group/Server field, enter the appropriate server.
  12. In the Instance Number field, enter the two-character ID. The values can be between 00 and 99.
  13. In the Logon Language field, enter the two-letter language code to be used for connecting to SAP.
  14. In the Message Server field, enter the appropriate server.
  15. In the Message Server Service field, enter the appropriate server service.
  16. In the SAP XBP Version field, enter the version of XBP that SAP is using. By default, version 3.0 is used. Setting this field allows JAMS to connect to older versions of SAP that use version 2.0.
  17. In the SAProuter String field, enter the SAP router string.
  18. In the System ID field, enter the three-character SAP system ID that was defined during SAP installation.
  19. In the XMI Audit Level, field enter the number for the Audit Level. This determines the level of detail logged in SAP.
  20. Click Save.

Adding a Connection for SAP (Custom Application Server)​

Select the SAP (Custom Application Server) option if the connection to your SAP system will be done through the Gateway Server. Before adding an SAP Connection, ensure a credential has been configured within JAMS that contains the username and password for connecting to the SAP Server.

  1. Click Execution from the main menu.
  2. Click Connections.
  3. Click Add.
  4. In the Connection Name field, enter the name, such as SAPCustomApplication.
  5. In the Connection Type field, select SAP (Custom Application Server).
  6. In the Description field, enter a description.
  7. Click Save and Continue to Edit.
  8. Click the Properties tab.
  9. In the Credentials field, enter the SAP credential that was created in JAMS.
  10. In the Application Server field, enter the name of the SAP server that will be used for the connection.
  11. In the Client ID field, enter the three-character ID. The values can be between 000 and 999.
  12. In the Instance Number field, enter the two-character ID. The values can be between 00 and 99.
  13. In the Logon Language field, enter the two-letter language code to be used for connecting to SAP.
  14. In the SAP XBP Version field, enter the version of XBP that SAP is using. By default, version 3.0 is used. Setting this field allows JAMS to connect to older versions of SAP that use version 2.0.
  15. In the SAProuter String field, enter the SAP router string.
  16. In the System ID field, enter the three-character SAP system ID that was defined during SAP installation.
  17. In the XMI Audit Level field, enter the number for the Audit Level. This determines the level of detail logged in SAP.
  18. Click Save.