Google Chat policy
A Google Chat policy contains the connection details that are used by a Google Chat Request node when you connect it to Google Chat.
You can use a Google Chat Request node in a message flow to connect IBM® App Connect Enterprise to Google Chat and issue requests to perform actions on objects such as members, messages, and spaces. The Google Chat policy controls, at run time, access to the Google Chat application.
The Google Chat policy is created when you configure a
connection between a Google Chat Request node and Google Chat by using the Connector Discovery wizard. During
the process of discovery, account credentials are stored in the vault and connection details are
stored in a policy. The policy is created with a type of Google Chat, and the name
of the policy is returned to the node and specified in the Connection tab, in the format
{policyProjectName}:policyName.
You can also create, update, or delete a Google Chat policy by using the Manage Discovery Connector Policies and Credentials wizard, which you can access by right-clicking the policy project in the IBM App Connect Enterprise Toolkit and then clicking .
You must deploy this policy before message flows that use the policy are started. If you redeploy a Google Chat policy, all message flows that are using the policy are stopped and restarted.
For more information about using Google Chat policies, see Using Google Chat with IBM App Connect Enterprise.
| Property | Property name in .policyxml file | Description of properties |
|---|---|---|
| Google Chat Application Type | applicationType | This property is reserved for future use and must be set to the value
online. |
| Google Chat Application Version | applicationVersion | This property is reserved for future use and must be set to the value
v1. |
| Google Chat Authentication method | authenticationMethod | This property specifies the type of authentication that is used for the
connection between IBM App Connect Enterprise and Google Chat. This property is reserved for future use and
must be set to BASIC_OAUTH. |
| Credential Name | credentialName |
The specified credential can be defined during connector discovery and stored in the vault. Alternatively, you can specify an existing credential that was configured by using the mqsicredentials command or the server.conf.yaml file, or loaded through an external credential provider. |