After you create the Google Calendar Resource Sync (GCRS) database, the GCRS system setup form opens automatically. Complete the form following the instructions below.
You're on step 5 of 5
Step 1: Complete the General tab
| Field | Description & action |
|---|---|
| Status | Used to turn the GCRS sync agent on or off.
Set it to Enabled. |
| Administrator | The sync agent attempts to resolve a Google username to an HCL Notes username when it adds an event to the Notes' calendar. If the Notes name can't be found, the system adds the person named in this field as the owner of the event in Notes. |
| Domino directory filename | Enter the filename of the HCL Domino directory to use when loading resources in the Resources view. |
| Server time zone | Select a time zone for the server. |
Step 2: Authorize using a service account
Upload the JSON file
- Click Upload Key File and upload your JSON key file (created earlier).
When the upload is complete, you can view and authorize the service account's client ID and scopes at the bottom of the form.
- Copy the Client ID.
Authorize your client ID
-
Sign in to your Google Admin console.
Sign in using an account with super administrator privileges (does not end in @gmail.com).
-
In the Admin console, go to Menu
Security
Access and data control
You must be signed in as a super administrator for this task. -
Click Add new and enter your service account client ID.
You can find the ID (also known as the Unique ID) in the JSON file that you downloaded when you created the service account or in Google Cloud (click IAM & Admin
- For OAuth scopes, copy and paste the following scopes:
https://googleapis.com/auth/admin.directory.resource.calendar,
https://googleapis.com/auth/calendar,
https://googleapis.com/auth/admin.directory.user - Click Authorize.
-
Point to the new client ID, click View details, and make sure that every scope is listed.
If a scope is not listed, click Edit, enter the missing scope, and click Authorize. You can't edit the client ID.
Step 3: Choose options in the Network tab
| Field | Description & action |
|---|---|
| Delay between HTTP posts | For optimum performance, keep the value at 0.0.
If you experience HTTP locks or service-unavailable responses from Google, you can increase the value to allow a delay between requests. |
| HTTP transport | Select ServerXMLHTTP.
XMLHTTP is not supported in production environments and does not support any proxy options. |
| Proxy server |
If the Domino server connects to the web through a proxy server, enter the server's URL in the hostname:port or IP-address:port format. |
| Proxy credentials | If the proxy requires credentials, enter the username and password. |
| Network time-outs | Timeouts can occur occasionally between the Domino and Google servers and cause the system to exit early.
To ignore timeouts and allow the system to wait for the Google servers to respond, select Off. |
Step 4: Review the Advanced tab
| Field | Description & action |
|---|---|
| Detailed event logging | By default, the system logs the following events to the GCRS log database:
You can turn on detailed event logging to view event-level synchronization events including calendar conflicts for each resource. |
| Google feed page size | This is the number of events requested by the system in a single Google feed during synchronization.
If the events exceed the value specified here, the system requests additional pages until all events are processed. |
| Resource database access method | By default, GCRS matches events in the Google feed to events in Notes using the database search method. For improved performance, you can switch to a view. However, if you select the view access method, keep in mind that:
|
Next step
Configure resources for synchronization
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.
