Key Capabilities
- Google Cloud Storage integration with OAuth authentication and automatic token refresh
- Bucket-based file organization with bidirectional file transfers
- Glob pattern filtering with optional file deletion after download and overwrite protection
- Optional caching to ensure only new or updated files are downloaded
Overview
Each Google Storage connector connects to a specific Google Storage account. Within the remote storage, you set a single bucket as the upload and/or download target. You can specify upload and download paths in the bucket, and apply filters to only send or receive specified file names and/or file extensions. Files that reach the Google Storage connector in the Arc flow are uploaded to the upload target folder, and files found in the download target folder are downloaded and entered into the Arc flow. Account authentication uses OAuth, and you must acquire OAuth credentials before connecting with the Google Storage connector. Once authentication is successfully completed with Google, the Google Storage connector handles refreshing the OAuth tokens to ensure that authentication persists over time.Connector Configuration
This section contains all of the configurable connector properties.Settings Tab
Authorization
Settings related to authorizing access to the remote storage.Google might require an OAuth callback/redirect URL when generating OAuth credentials. The Arc callback/redirect URL is the same as the address and port where the application is hosted, plus the following resource path:
src/oauthCallback.rst. For example, if Arc is hosted on ‘mydomain.com’ on port 8001, specify the following URL as the callback/redirect URL: http://mydomain.com:8001/src/oauthCallback.rst.Host Configuration
Settings related to the target storage host.Send
Settings related to uploading to the remote storage.Receive
Settings related to downloading from the remote storage.Caching
Settings related to caching and comparing files between multiple downloads.Arc automatically cleans up the resource cache. This process runs in the background during every receive cycle and removes stale cache entries for files that are no longer present on the remote server. This keeps the cache size manageable without requiring any manual action.
By default, files are retained for 30 days, but you can use the ResourceCacheRetentionDays setting in the Other Settings field on the Advanced tab to adjust it to fit your environment. For example, ResourceCacheRetentionDays=15 retains files for 15 days before removing them.
TEST.TXT and test.txt.Advanced Tab
Advanced Settings
Settings not included in the previous categories.Proxy Settings
These are a collection of settings that identify and authenticate to the proxy through which the connection should be routed. By default, this section uses the global settings on the Proxy Settings portion of the Security Settings page. Clear the checkbox to supply settings specific to your connector.
| Setting | Description |
|---|---|
| Proxy Type | The protocol used by a proxy-based firewall. |
| Proxy Host | The name or IP address of a proxy-based firewall. |
| Proxy Port | The TCP port for a proxy-based firewall. |
| Proxy User | The user name to use to authenticate with a proxy-based firewall. |
| Proxy Password | A password used to authenticate to a proxy-based firewall. |
| Authentication Scheme | Leave the default None or choose from one of the following authentication schemes: Basic, Digest, Proprietary, or NTLM. |
Logging
Settings that govern the creation and storage of logs.
| Setting | Description |
|---|---|
| Log Level | The verbosity of logs generated by the connector. When you request support, set this to Debug. |
| Log Subfolder Scheme | Instructs the connector to group files in the Logs folder according to the selected interval. The Weekly option (which is the default) instructs the connector to create a new subfolder each week and store all logs for the week in that folder. Leaving this setting blank tells the connector to save all logs directly in the Logs folder. For connectors that process many transactions, using subfolders helps keep logs organized and improves performance. |
| Log Messages | Check this to have the log entry for a processed file include a copy of the file itself. If you disable this, you might not be able to download a copy of the file from the Transactions tab. |
Miscellaneous
Miscellaneous settings are for specific use cases.
| Setting | Description |
|---|---|
| Other Settings | Enables you to configure hidden connector settings in a semicolon-separated list (for example, setting1=value1;setting2=value2). Normal connector use cases and functionality should not require the use of these settings. |
Automation Tab
Automation Settings
Settings related to the automatic processing of files by the connector.Automation Status
Performance
Settings related to the allocation of resources to the connector.
| Setting | Description |
|---|---|
| Max Workers | The maximum number of worker threads consumed from the threadpool to process files on this connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page. |
| Max Files | The maximum number of files sent by each thread assigned to the connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page. |
Alerts Tab
SLAs Tab
Establishing a Connection
OAuth credentials are required to establish a connection with the Google Storage connector. Acquire the OAuth credentials from Google via the Google Console, then specify them in the following connector fields on the Settings tab:- OAuth Client ID
- OAuth Client Secret
src/oauthCallback.rst. For example, if Arc is hosted on ‘mydomain.com’ on port 8001, specify the following URL as the callback/redirect URL: http://mydomain.com:8001/src/oauthCallback.rst.
Once authentication is successfully completed with Google, the Google Storage connector handles refreshing the OAuth tokens to ensure that authentication persists over time.