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

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Configure using SGC Central

# Configure API Service Graph Connector for Apigee X using SGC Central {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 Minuten Lesedauer

Set up scheduled import jobs to pull in Apigee X data into your CMDB.

## Vorbereitungen

Install API Service Graph Connector for Apigee X version 1.0.0 or later from the ServiceNow Store. For ServiceNow Store installation steps, see [Install a ServiceNow Store application](https://www.servicenow.com/docs/access?context=t_InstallApplications&version=australia&pubname=australia-platform-administration&ft:locale=en-US).  
Role required: The following table shows the roles required for each stage of the playbook.{#sgcc-configure-apigee-x__table_zcy_w5p_4hc__entry__2}

| Stage | Role |
|-|-|
| Prerequisites | admin |
| Setup | SGC-Admin (sn_cmdb_int_util.sgc_admin) or admin |
[Tabelle : 1. Role required for each playbook stage]

{#sgcc-configure-apigee-x__table_zcy_w5p_4hc}  
Hinweis:  
The admin user role is required to run background scripts and to provide access to global tables to the SGC-Admin user. For information about the user roles for Service Graph Connectors, see [Service Graph Connector user roles](https://servicenow-prod.fluidtopics.net/1wLEV8ubYlPM_nDUSO~F~Q#cmdb-sgc-intro__section_ett_spp_4hc).

## Warum und wann dieser Vorgang ausgeführt wird

The playbook experience for onboarding connectors is activated with SGC Central in the CMDB Workspace. To configure the SGC Central application, see [Configuring SGC Central](https://servicenow-prod.fluidtopics.net/UnQAG~FYFjoCfIHuaKAkKw "Set up the SGC Central application for onboarding and maintaining Service Graph Connectors and monitoring the errors related to connections added using Service Graph Connectors.") and for more information on how to interact with a playbook, see [Interact with Playbook](https://www.servicenow.com/docs/access?context=playbook-ui&version=australia&pubname=australia-build-workflows&ft:locale=en-US).  
Hinweis:  
Alternatively, you can configure a default connection already available from the installed or draft connections in SGC Central. Go to AllService Graph Connectors, then select Setup for the connector from the menu. To learn about installed and draft connections, see [Managing connections added for Service Graph Connectors in SGC Central](https://servicenow-prod.fluidtopics.net/AfpyKTXk3er0I3tICE7~~g "You can create and update connections added for Service Graph Connectors within the SGC Central view of the Service Graph Workspace or CMDB Workspace to ingest data into Configuration Management Database (CMDB) from third-party sources.").

## Prozedur

1. Navigate to WorkspacesCMDB Workspace.
2. In the CMDB Workspace, select SGC Central.
3. On the Overview page, select Create connection.  
   Tipp:  
   Alternatively, you can select Create connection on the All connections page.
4. On the Create connection window, select the Apigee X connector type, and then select Create connection.
5. Complete the initial prerequisites when setting up a connection for the first time using a connector.  
   Hinweis:  
   This step is required only during the first-time setup. See [Perform initial setup tasks when creating a connection in SGC Central](https://servicenow-prod.fluidtopics.net/wlOQcTjvJsvl51egxq37JQ "Complete the prerequisites for setting up a connection for the first time using a Service Graph Connector within the SGC Central view of the Service Graph Workspace or CMDB Workspace.").
6. Complete the prerequisites for setting up the Apigee X environment.
   1. Set up the Apigee X environment and create a Java KeyStore (JKS) certificate to encrypt the security certificates obtained from an Apigee X application.  
      1. In the Prerequisites stage of the playbook, select the Review setup instructions activity.
      2. Review and complete the setup instructions on the [API Service Graph connector for Apigee X - Setup Instructions \[KBB0010364\]](https://support.servicenow.com/kb_view.do?sysparm_article=KBB0010364) article in the Now Support Knowledge Base.

         You must create a service account, assign roles, bind roles to the service account, enable APIs, create a P12 file, and register it in your ServiceNow instance.{#sgcc-configure-apigee-x__create-p12}

         Make a note of the destination keystore password. You need to specify this password while importing the JKS certificate into the API Service Graph Connector for Apigee X application.
         {#sgcc-configure-apigee-x__keystorepwd}
      3. Select the I have read the setup instructions check box to confirm that you have set up the Apigee X environment according to the instructions.
      4. Select Continue.
      {#sgcc-configure-apigee-x__ol_tbw_fsn_tcc}
   2. Create an X.509 certificate to associate the Java KeyStore (JKS) certificate for the Apigee X application with the connector.  
      Hinweis:  
      You can skip this step if you're reusing a previously created certificate.
      1. In the Prerequisites stage of the playbook, select the Create X.509 certificate activity.
      2. On the form, fill in the fields.{#sgcc-configure-apigee-x__table_izn_4gd_2xb__entry__2}

         | Field | Description |
         |-|-|
         | Name | Name of the X.509 certificate. For example, `ApigeeX-509Certificate`. |
         | Key store password | Password to access the JKS certificate as noted down in the [previous step](https://servicenow-prod.fluidtopics.net/34HIKbg~yPwtGWYw6V9LpQ#sgcc-configure-apigee-x__keystorepwd). |
         | Short description | Description of the X.509 certificate. |
         [Tabelle : 2. X.509 Certificate form]

         {#sgcc-configure-apigee-x__table_izn_4gd_2xb}
      3. In the Attachments section, select Add File.
      4. Browse and select the P12 file for the JKS certificate you created in the [previous step](https://servicenow-prod.fluidtopics.net/34HIKbg~yPwtGWYw6V9LpQ#sgcc-configure-apigee-x__create-p12).
      5. On the Upload a file dialog box, select Upload.
      6. Select Continue.
      {#sgcc-configure-apigee-x__ol_omh_nsn_tcc} {#sgcc-configure-apigee-x__x509cert}
   {#sgcc-configure-apigee-x__x509cert} {#sgcc-configure-apigee-x__substeps_w4l_p4v_4cc}
7. Enter connection details and test the API connection for importing Apigee X data.
   1. In the Setup stage of the playbook, select the Create and test connection activity.
   2. On the form, fill in the fields.  
      {#sgcc-configure-apigee-x__table_ahn_xtg_rmb__entry__2}

      | Field | Description |
      |:-|:-|
      | Connection name | Name to identify the Apigee X connection record. |
      | Service account email | Email address associated with the ServiceNow service account used for authentication with Apigee X as noted in the [previous step](https://servicenow-prod.fluidtopics.net/34HIKbg~yPwtGWYw6V9LpQ#sgcc-configure-apigee-x__create-p12). |
      | X.509 certificate | Name of the X.509 certificate as noted in the [previous step](https://servicenow-prod.fluidtopics.net/34HIKbg~yPwtGWYw6V9LpQ#sgcc-configure-apigee-x__create-p12). |
      | Keystore password | Password associated with the keystore as noted in the [previous step](https://servicenow-prod.fluidtopics.net/34HIKbg~yPwtGWYw6V9LpQ#sgcc-configure-apigee-x__keystorepwd). |
      [Tabelle : 3. Configure and test connection form]

      {#sgcc-configure-apigee-x__table_ahn_xtg_rmb}
   3. Select Create and test connection.
   4. Once the connection test is complete, select Continue.
   {#sgcc-configure-apigee-x__substeps_p1l_fnb_gcc}
8. Set the configuration properties for the connection.
   1. In the Setup stage of the playbook, select the Set configuration properties activity.
   2. Enter the properties.  
      {#sgcc-configure-apigee-x__table_nn3_31v_3cc__entry__2}{#sgcc-configure-apigee-x__table_nn3_31v_3cc__entry__3}

      | Property | Description |
      | Apigee identification ||
      |-|-|
      | Apigee organization name/GCP project idOrganization id | Apigee X organization names or GCP project IDs from which data should be fetched. If left blank, data is retrieved from all permitted Apigee X organizations. For multiple values, separate them with commas. Organization within the Apigee X system to which the projects belong. |
      | Project id | Project identifier within the Apigee X environment that the connection will be linked to. For multiple project IDs, separate them with commas. |
      | Data retrieval configuration ||
      | Discovery scope | Discovery scope of the Apigee X application. The available options are: Organization :   Select Organization when the ServiceNow service account has access to data within the Apigee X organization. Projects :   Select Projects when the ServiceNow service account has access to data within Apigee X projects only. |
      | Exclude Environments | Apigee X environments that should be excluded from the connection. For multiple environments, separate them with commas. All gateways except those listed in the Exclude Environments property are fetched. If you leave this field empty, the data sources within the connector import data from all the environments. |
      | Include environments | Apigee X environments to include in the connection. For multiple environments, separate them with commas. Only API proxies in the environments listed in the Include environments property are imported. If you leave this field empty, the data sources within the connector import API proxies from all environments. |
      | Collection period (in days) | Duration in days for collecting API usage data. |
      | Collect usage data | Option to enable usage data collection to retrieve API usage data over a specified duration. |
      | Expand HTTP method types | HTTP methods including `GET`, `POST`, `PUT`, `PATCH`, `DELETE`, `OPTIONS`, `HEAD`, `CONNECT`, and `TRACE`, to consider for routes. For multiple methods, separate them with commas.If left blank, results in a single API Frontend being created with the `ALL` method, indicating support for all standard HTTP methods. |
      | GCP identification ||
      | GCP Organization id | GCP organization ID for retrieving data from GCP Organization, GCP Folder, and GCP Project data sources. |
      | Performance configuration ||
      | Page size | Number of records per page. Default is `100`, minimum is `2`. |
      | Partition size | Partition size for Apigee X managed APIs if parallel loading is enabled. Accepts a numeric value greater than zero. If left empty, the value is automatically calculated. |
      [Tabelle : 4. Service Graph Connection Properties]

      {#sgcc-configure-apigee-x__table_nn3_31v_3cc}
   3. Select Continue.
   {#sgcc-configure-apigee-x__substeps_umj_3df_gcc}
9. Configure the import schedule to import data at regular intervals.
   1. In the Setup stage of the playbook, select the Configure import schedule activity.
   2. Expand the Parent scheduled data import within the Import schedules list to select the Apigee Organization import schedule associated with your connection.  
      Hinweis:  
      The connection name is prefixed to the schedule name.
   3. In the Configure import schedule dialog box, select the Active check box, and then fill in the run schedule and time details.  
      For more information, see [Schedule a data import](https://www.servicenow.com/docs/access?context=t_ScheduleADataImport&version=australia&pubname=australia-integrate-applications&ft:locale=en-US#table_r53_5hm_xp).
   4. Select Configure import schedule.
   5. In the Configure import schedule dialog box, in the Name field, enter the Organization import schedule.
   6. Select the Active check box, and then fill in the run schedule and time details.  
      For more information, see [Schedule a data import](https://www.servicenow.com/docs/access?context=t_ScheduleADataImport&version=australia&pubname=australia-integrate-applications&ft:locale=en-US#table_r53_5hm_xp).
   7. Select Save.  
      Alternatively, select Execute Now to execute the import schedule immediately.
   8. Select Continue.
   {#sgcc-configure-apigee-x__substeps_lf4_yvw_fcc}
10. In the Setup stage of the playbook, select the Confirm connection creation activity to verify whether the connection was created.

## Nächste Maßnahme

Select View all connections to review the connection details. The configured connection appears in the Installed connections list.

You can then manage connections from the SGC Central view of the CMDB Workspace. For more information, see [Managing connections added for Service Graph Connectors in SGC Central](https://servicenow-prod.fluidtopics.net/AfpyKTXk3er0I3tICE7~~g "You can create and update connections added for Service Graph Connectors within the SGC Central view of the Service Graph Workspace or CMDB Workspace to ingest data into Configuration Management Database (CMDB) from third-party sources.").
**Zugehörige Konzepte**   

* [API Service Graph Connector for Apigee X](https://servicenow-prod.fluidtopics.net/DQ1fkwsEC3qIoOSzRReAVg "Use the ServiceNow API Service Graph Connector for Apigee X to import API proxy details from an Apigee X application into the Configuration Management Database (CMDB).")  
**Zugehörige Verweise**   

* [Target tables for storing API Service Graph Connector for Apigee X data](https://servicenow-prod.fluidtopics.net/EeIfIc27RRLhe6c2gdMyFA "When you complete setting up the connection, you can configure the integration to periodically pull data from an Apigee X application. The data is saved in tables that extend from the Configuration item [cmdb_ci] classes and other non-CMDB tables.")