Changing the settings of the Installed Files for the Web Application - Johnson Controls - LIT-12013270 - Software Application - Companion - 1.1

Companion Installation Guide

Brand
Johnson Controls
Product name
Companion
Document type
Installation Guide
Document number
LIT-12013270
Version
1.1
Revision date
2019-10-23
Language
English

About this task

To change the settings of the installed files for the web application, complete the following steps:

Procedure

  1. Navigate to C:\wwwcompanion\app.
  2. Open the appsettings.json file.
  3. In the Connection: Connection String section, modify the following settings:
  4. To connect to the database, replace the following information:
    • Replace [SQLServerInstance] with the SQL Server Instance name
    • Replace [DatabaseName] with Companion
    • Replace [Id] with the SQL Login user ID
    • Replace [Pwd] with the SQL Login password
  5. In the AzureAdAuthentication section, replace the following information:
    • [TenantId] – Tenant Id of the organization in Azure AD
    • [RedirectUrl]– URL of the Companion application which needs to be configured as a redirect URI in Azure AD during application registration.
    • [NativeAppClientId] – Client Id of the Companion Native Application registered in Azure Ad under the organization’s tenant account.
    • [WebApiClientId] - Client Id of the Companion Web Application registered in Azure Ad under the organization’s tenant account.
    • Web –Secret Key of the Companion Web Application registered in Azure Ad under the organization’s tenant account.
    • [WebApiResourceId] – App Id URI of the registered companion web application in Azure AD.

    For further queries, contact the Companion Support team.

  6. In the BmsConfiguration section, replace the [InternalApiIP] with the IP of the Server in which the BMS WCF Service is deployed (Refer section 3.3).
  7. In the Meeting Integration section, replace the EWSServiceEndpoint key value with the Outlook Exchange URL and replace [OutlookAdminEmail] and [OutlookAdminPassword] with the POP3 Account details.
  8. In the XmlRpcIntegration (Access Control System Integration) section, you must replace the following information:
    • P2000
      • XmlRpcServiceEndpoint – Replace [ACSIP] with the IP of the P2000 Server
      • XmlRpcUserName – Replace [OperatorUserName] with P2000 Operator User Name
      • XmlRpcPassword – Replace [Operator Password] with P2000 Operator Password
      • BaseUriInternal – Replace [InternalApiIP] with the URL of the internal APIs hosted in IIS (Refer section 3.3)
      • BadgeUrl - Replace [BadgeUrl] with RpcBadges/Internal
      • TerminalUrl – Replace [ReaderUrl] with RpcTerminals/Internal
    • CCure
      • XmlRpcServiceEndpoint – Replace [ACSIP] with the IP of the CCure Server.
      • XmlRpcUserName – Replace [OperatorUserName] with CCure Operator User Name
      • XmlRpcPassword – Replace [Operator Password] with CCure Operator Password
      • BaseUriInternal – Replace [InternalApiIP] with the URL of the internal APIs hosted in IIS (Refer section 3.3)
      • BadgeUrl - Replace [BadgeUrl] with CCure/Badge
      • TerminalUrl – Replace [ReaderUrl] with CCure/Readers
  9. In the Notification section, set SendUserCreationEmail: to true if a mail must be sent when a user is newly created in the application and replace [EndpointURL] with the Endpoint URL of the application configured in IIS.
  10. In the Business Rules section, set EnableRestrictedAccess to false to bypass badge-in for BMS control for the entire application.