CONNECT data services configuration (UFL)

A general example of the CONNECT data services endpoint configuration is shown here:

EndPointType=OCS
URL=MyURL
Port=####
BaseObject=/api/v1
TenantID=5EFE43ED-EC6E-4C70-B4C0-FAFDE2E069B4
Namespace=MyNamespace
IdentityProviderURL=/identity/connect/token
ClientID=MyClientID
ClientSecret=MyClientSecret

Here are the CONNECT data services configuration parameters defined:

• EndpointType=OCS

  This line signifies the start of CONNECT data services endpoint configuration.

• URL

  The URL of the CONNECT data services endpoint where the health data will be sent.

• Port

  The Port references the port on the server that the interface listens on. The number in this configuration file will match the number specified when CONNECT data services was installed on the node.

• BaseObject

  The CONNECT data services collection in which to store OMF Health streams. For more information, see BaseObject overview.

• TenantID

  The tenant the OMF health streams belong to. For more information, see TenantID overview.

• Namespace

  The CONNECT data services namespace where the health streams are stored.

• IdentityProviderURL

  The URL of the entity that provides your identity to CONNECT data services. For example, Azure Active Directory may be used. For more information, see IdentifyProviderURL overview.

• ClientID

  The client ID set up for your CONNECT data services endpoint. This field is erased from the config file once the service is started.

• ClientSecret

  The client secret set up for your CONNECT data services endpoint. This field is erased from the config file once the service is started.