---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Get started with connections

# Get started with connections {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 30. Juni 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Use the connections table to set up a Basic, JMS, JDBC, or HTTP(s) connection to a
target host.

## Connection Table {#connection-information__section_ljx_qgw_2bb}

The Connection table (sys_connection) is the base table for all connection tables. You can set up connections for the following protocols:

* Basic connection for PowerShell and SSH
* JDBC
* JMS
* HTTP(s)

{#connection-information__ul_u4c_ryb_hbb}The connection table references the connection alias table, which couples the connection alias to connection information. Every connection records the following information:{#connection-information__table_dng_wyb_hbb__entry__2}

| Field | Description |
|-|-|
| Name | Name of the connection. This field must be unique on the table. |
| Credential | Specify the credential to use with this connection. This is optional. |
| Connection alias | The connection alias resolves your connection and credentials at run time. Only one connection is active per Connection alias at any one time. |
| Active | Check to make the current connection active. |
| Domain | Domain to which the connection belongs. |
[Tabelle : 1. Base connection properties]

{#connection-information__table_dng_wyb_hbb}

Credential is unique across active connections, if not empty.

## Upgrading connection information {#connection-information__section_q4x_5pd_fbb}

* The JDBC connection \[jdbc_connection\] and JMS connection \[orch_jms_ds\] tables are existing Orchestration connection tables that now extend from the Connection \[sys_connection\] table. The tables originally extended from sys_metadata. The sys_metadata related data is removed.
* The tables move from the Orchestration run time plugin \[com.snc.runbook_automation.runtime\] to the Credentials \& Connections plugin.
* The upgrade process obtains JDBC and JMS connection information and creates corresponding connection aliases and assigns the alias to its corresponding connection.
* JDBC field name changes:
  * JDBC server is renamed to host
  * Database port is renamed to port
  * Data of the JDBC server and database migrates to host and port during the upgrade
  {#connection-information__ul_j3j_rzb_hbb}
{#connection-information__ul_vzv_x5d_ybb}
* **[Create a basic connection for PowerShell and SSH](https://servicenow-prod.fluidtopics.net/1qVnaiqmcX6ld7UG8sxvhw)**   
  Configure connection information to use with a custom activity or action that uses the PowerShell or Secure Shell (SSH) protocol.
* **[Create an HTTP(s) connection](https://servicenow-prod.fluidtopics.net/lCOrTJrPSDa5Yvp7oBVrig)**   
  The HTTP(s) connection provides the information custom HTTP(s) actions or activities use to connect.
* **[Create a JDBC connection](https://servicenow-prod.fluidtopics.net/10TZF1hIGYiTsLo6IFc26A)**   
  The JDBC Connection provides the information custom JDBC actions or activities use to connect to various target databases.
* **[Create a JMS connection](https://servicenow-prod.fluidtopics.net/pInluTrF1cKt_5cfj50rWA)**   
  Configure your system to use Java Messaging Service (JMS) with a custom JMS activity or action.
* **[Create connection attributes for IntegrationHub](https://servicenow-prod.fluidtopics.net/fPTd2VGu6B_WVXWufIvafw)**   
  Define connection-specific variables that you can use in Integration Hub integration steps.