Property | Description |
|---|---|
Name | Required. Unique name for the Google BigQuery V2 connection that identifies it in the Process Designer. The name must start with an alphabet and can contain only alphabets, numbers, and hyphens (-). |
Location | Required. The location of the project or folder where you want to save the connection. Click Browse to select a location. If the Explore page is currently active and a project or folder is selected, the default location for the connection is the selected project or folder. Otherwise, the default location is the location of the most recently saved asset. |
Description | A description of the connection. |
Type | Required. The type of connection you want to use for the connector or service connector. Select Google BigQuery V2. |
Runtime Environment | Required. The runtime environment for the connection. Select the Secure Agent group or the Secure Agent machine where the connection must run. |
Connection Test | Displays the result of the last connection test. |
OData-Enabled | Specifies whether OData feeds are enabled for the connection. Select Yes to enable OData feeds. If you select Yes, you must specify either the allowed users or the allowed groups that can access the connection at design time. Default is No. |
Use Secret Vault | Stores sensitive credentials for this connection in the secrets manager that is configured for your organization. This property appears only if secrets manager is set up for your organization. When you enable the secret vault in the connection, you can select the credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured. For information about how to configure and use a secrets manager, see "Secrets manager configuration" in the Administrator help. |
OData Cloud Access Enabled | Specifies whether you can access data from the OData service by using the Cloud endpoint URLs or the Secure Agent endpoint URLs. If you enable OData and configure the connection to run on a Secure Agent machine or a Secure Agent group, you can choose to disable access to the Cloud endpoint URLs for security purposes. Select No to disable access to the Cloud endpoint URLs. If you select No, you cannot access data from the OData service by using the Cloud endpoint URLs. You can access data only by using the Secure Agent endpoint URLs. Select Yes to access data from the OData service by using both the Cloud endpoint URLs and the Secure Agent endpoint URLs. Default is Yes. Note: If you set the OData-Enabled option to No, the value that you set for the OData Cloud Access Enabled option does not apply because Application Integration does not generate the OData endpoint URLs. For more information, see Endpoint URLs for OData-Enabled Connections. |
Allowed Users for OData | The users that have access to the connection at design time. You can specify more than one user. After you specify the first value, press the Enter key or the Comma key, and then specify the next value. |
Allowed Groups for OData | The user groups that have access to the connection at design time. You can specify more than one user group. After you specify the first value, press the Enter key or the Comma key, and then specify the next value. |
Enable CORS for Domains | The additional allowed domains from which API consumers can invoke the associated APls. API consumers running a web application running at one origin can access selected resources from origins that you mention in the Enable CORS for Domains field. Enter the wildcard character ( * ) to enable CORS for all domains. Enter a comma-separated list of domains to enable CORS for specific domains. For example, enter the following phrase to enable CORS for the abc.domain.com and xyz.domain.com domains: abc.domain.com, xyz.domain.com |
Enable CORS for Verbs | The allowed verbs that API consumers can use to invoke the APIs from the domains that you specified in the Enable CORS for Domains field. Enter a comma-separated list of verbs to enable CORS for specific verbs. For example, enter the following phrase to enable CORS for the POST, PUT, and GET verbs: POST, PUT, GET Default is all verbs. |