OneContact 3.6 installation

OneContact 3.6 relies on runtime databases to be more effective and faster. On this article you have the walk-through for an installation. Keep in mind that a system must be configured all in http or https (do not mix them).

Note: Further configurations might be required depending on your Contact Center context.

 

For a OneContact installation the following steps are required:

 

 

Databases deployer

  1. Run deploydatabasesetup (3.6.174).
  2. Select Create new system and click Next.
    001_dd.png
  3. Click on the System Database Name's checkbox and click Next.
    002_dd.png
  4. Insert the database desired location, users and respective passwords and click Next to proceed.
    011_DBdeployer.png
    Note: Database Admin User (referred to, from now on, as sa) and OneContact Database User (referred to, from now on, as OneContactUser) are the key users and are used along the installation process. It is important not to mix one with the other (and their passwords) as some components require one and other components require the other. Make sure that both users have passwords that comply with Collab's password policies.
  5. Click Next to proceed.
    012_DBdeployer.png
  6. Click Close to finish the deployment.
    013_DBdeployer.png
  7. Run the OneProxydatabasedeployer.
  8. Select Create new system and click Next.
    003_dd.png
  9. Click on the OneProxyProvisioning Database Name's checkbox and click Next.
    004_dd.png
  10. Insert the database desired location, users and respective passwords and click Next to proceed.
    005_dd.png
  11. Click Next to proceed.
    006_dd.png
  12. Click Close to finish the deployment.
    007_dd.png

  

 

OneSetup installation

  1. Open OneSetup.
  2. Make sure you have an updated version of OneSetup.
  3. Make sure you have GA selected for the NuGet Package Repository.
  4. Select Install New Instance (selected by default) and click Next to proceed.
    008_OneSetup.png
  5. Insert an instance name (it can be left blank) and click Next to proceed.
    000a_onesetup.png
    Note: If you don't insert an Instance name, the default instance will be used. The instance name can't match any existing instance.
  6. Select 3.6.4 from the filter's drop-down menu.
  7. Select BaseService (4.8.19) and click Next to proceed.
    009_OneSetup.png
  8. Check the default paths. Change them if you need to and click Next to proceed.
    010_OneSetup.png
  9. On Windows Service, check the component's startup type and the logon type. Change them if you need to and click Next to proceed.
    011_OneSetup.png
  10. On System Database, insert the database desired location, insert the password for your OneContactUser and click Next to proceed.
    012_OneSetup.png
  11. On Runtime Databaseinsert the database desired location, insert the password for your OneContactUser and click Next to proceed.
    013_OneSetup.png
  12. On Base Service, check the default BaseService port. Change it if you need to and click Next to proceed.
    014_OneSetup.png
  13. heck if your system meets all the requirements and click Next to proceed (or Fix All in case any requirement is not met).
    015_OneSetup.png
    Note: To know more about the Check Requirements window, click here.
  14. On Ready to Install, click on the Deploy Database checkbox, insert the password for your sa and click next to proceed.
    016_OneSetup.png
  15. The package downloading and installation starts.
    017_OneSetup.png
  16. After the BaseService is installed, open the Windows Services application.
  17. Select OneContactBaseService, from the service's list and click Start.
    017a_OneSetup.png
  18. Go back to OneSetup (click Do more, if it is still open or re-open OneSetup).
  19. Select Upgrade or Repair Instance and click Next to proceed.
    018_OneSetup.png
  20. Select 3.6.4 from the filter's drop-down menu, select the desired components and click Next to proceed.
    019_OneSetup.png
  21. Check the default paths. Change them if you need to and click Next to proceed.
    000c_onesetup.png
  22. On Windows Service, check the component's startup type and the logon type. Change them if you need to and click Next to proceed.
    011_OneSetup.png
  23. On Application Pool, check the Application Pool authentication type, change it if you need to and click Next to proceed.
    020_OneSetup.png
  24. On System Database, check the information provided on the BaseService installation and click Next to proceed.
    021_OneSetup.png
  25. On Runtime Databaseinsert the database desired location, insert the password for your OneContactUser and click Next to proceed.
    022_OneSetup.png
  26. On REST API Databaseinsert the database desired location, insert the password for your sa and click Next to proceed. 
    023_OneSetup.png
  27. On OneFlow Databaseinsert the database desired location, insert the password for your sa and click Next to proceed.
    024_OneSetup.png
  28. On SipConnector Databaseinsert the database desired location, insert the password for your OneContactUser and click Next to proceed.
    025_OneSetup.png
  29. On Identity Databaseinsert the database desired location, insert the password for your sa and click Next to proceed.
    026_OneSetup.png
  30. On Portal Databaseinsert the database desired location, insert the password for your sa and click Next to proceed.
    027_OneSetup.png
  31. On SipConnector Databaseinsert the database desired location, insert the password for your OneContactUser and click Next to proceed.
    028_OneSetup.png
  32. On Identity, insert the Identity URL , the Identity Authority URL, the Identity Provisioning URL, the Logout URL, the Cookie Domain and Click Next to proceed.
    029_OneSetup.png
    Note: Keep in mind that if you are installing your system on localhost, it is required to use http, as https will not work.
  33. On Base Service, check and configure (if needed) the paths or ports and click Next to proceed.
    030_OneSetup.png
  34. Check if your system meets all the requirements and click Next to proceed (or Fix All in case any requirement is not met).
    031_OneSetup.png
  35. On Ready to Upgrade, click on the Deploy Database checkbox, to deploy all available databases, insert the required sa password and click Next to start the installation.
    032_OneSetup.png
  36. On the Complete screen you can see the information on the component installation status. To know more about the Complete page, click hereClick Finish to end the installation.

 

Configuration files:

Check and configure all required appsettings (Identity paths, Provisioning and Portal versions):

ContactManagement API:
"URL": "https://localhost/PortalAPI",
"Version": "1.0" (change to 1.14)

Discovery Service:
"DiscoveryService": "Data Source=[Domain];Initial Catalog=[Name]OneDiscoveryService;User ID=[sa]; Password=[password]", (insert the required information)
"DiscoveryServiceMiddleware": "Data Source=[domain];Initial Catalog=[name]OneContactRestAPI;User ID=[sa]; Password=[password]", (insert the required information)

IdentityProvisioning:
"OneIdentityServerConfiguration": {
"Authority": "[IdentityUrl]" (insert the Identity path)

OneAdmin:
<add key="NubitalkApiVersion" value="1.0" /> (change to 1.14)
<add key="NubitalkUsername" value="sysadmin" />
<add key="NubitalkPassword" value="sysadmin" /> (insert the proper sysadmin password)
<add key="NubitalkTenant" value="nubitalk" /> (change "nubitalk" to "system")

OneAgentWeb:
"agent_api" (change to "oneagent_api")
"ApiName": "agent_api" (change to  "ApiName": "oneagent_api")

OneSupervisor:
<add key="OneSupervisorConnector" value="http://hive.collab.intra/onesupervisorconnector/" /> (insert the path)
<add key="OneProvisioning" value="http://hive.collab.intra/identityprovisioning/" /> (insert the path)
<add key="OneProvisioningApiVersion" value="1.0" /> (change to 3.2)
<add key="OneIdentity" value="http://hive.collab.intra/identity/" /> (insert the path)

Portal:
Remove  "onemeeting_provisioning_api"

"DiscoveryService": "http://[domain]/DiscoveryService", (insert the path)

PortalAPI:
"DiscoveryService": "http://localhost/DiscoveryService", (insert the path)
"SystemId": "1",
"AppSettings": {
"LocalStoragePath": "C:\\Collab\\Temp/",
"UserDB": "OneContactUser", (insert the user)
"UserPassword": "#password37", (insert the password)

ProvisioningAPI:
"NubitalkSettings": {
"URL": "https://localhost/PortalAPI",
"Version": "1.11" (change to 1.14)

ReportingAPI:
"OneProvisioningSettings": {
"Url": "http://auth.collab.intra/identityprovisioning", (change to [domain]/)
"ApiVersion": "1.0", (change to 3.2)
"Scope": "provisioning_api"
},
"NubitalkSettings": {
"URL": "http://hive.collab.intra/PortalAPI", (change to [domain]/)
"Version": "1.8" (change to 1.14)
},
"Location": {
"OneSupervisorAPI": "http://hive.collab.intra/ProvisioningAPI",  (change to [domain]/)
"APIVersion": "3.5"

StorageService:
"IdentityProvisioningVersion": "1.0", (change to 3.2)
"PortalApiVersion": "1.0", (change to 1.14)

 

  

GlobalStorage and certification

  1. Create a GlobalStorage folder on C:\Collab\ and place there:
    • The branding default folder (copy the Default folder from the identity installation folder).
    • The certificate olidsrvr (located on the identity installation folder).
      Warning: The identity certificate has to be installed as the server administrator and that user has to be inserted on the Identity AppPool, with the Load User Profile set to True.
  2. Install the certificate:
    1. Double-click on the certificate.
    2. Select Current User and click Next:
      CertImport01.png
    3. Confirm that the certificate path is correct and click Next to proceed.
      CertImport01a.png
    4. Insert the password (collab03).
    5. Select Include all extended properties and click Next to proceed.
      CertImport02.png
    6. Select Place all certificates in the following store.
    7. Select Personal, as the certificate store and click Next to proceed.
      CertImport03.png
    8. Review all the information and click Finish to proceed.
      CertImport04.png
    9. Click OK to close the pop-up window.
      CertImport05.png
Warning: Make sure the certificate is installed or the databases will not be deployed.

 

  1. The Identity AppPool requires a user with storage access, with Load User Profile set to True (it is possible to use Azure Storage, by configuring it on the database):
    1. Open Internet Information Services (IIS) Manager.
    2. Select Applications Pools:
      AppPool.png
    3. Select IdentityAppPool:
      AppPool_identity.png
    4. Edit the IdentityAppPool:
      AppPool_identity_edit.png
    5. Select Identity and click on AppPool_identity_edit_identity.png to edit:
      AppPool_identity_edit2.png
    6. Select Custom account and click on Set:
      AppPool_identity_edit3.png
    7. Insert the user name and password (confirm password) and click OK.
    8. Select Load User Profile and set it to True.
    9. Click OK to confirm and proceed.
      Note: If there is a WebDavModule on IIS modules, remove it.

 

Create the databases

  1. Open the http://[machine]/identityprovisioning/swagger, on a browser, to create the Identity database.
    1. Click Authorize, insert the client_id and the client_secret, click on the provisioning_api scopes checkbox and click Authorize to proceed.
    2. On Select a spec, select 3.2, from the drop-down menu.
    3. Create a Tenant: 
      1. Click on Tenant > post /api/tenants.
      2. Click on Try it out.
      3. On Example Value, insert:
        {
        "name": "system",
        "email": "[your_email]",
        "advanced": true,
        }
      4. Select 3.2 on Api Version, from the drop down menu.
      5. Click Execute to proceed.
    4. Create a User:
      1. Click on User.
      2. Click on POST/api/tenants/{TenantId}/users.
      3. Click on Try it out.
      4. Insert, on Example Value:
        {
        "userName": "sysadmin",
        "password": "#password37",
        "allowSMSLogin": false,
        "name": "sysadmin",
        "isFirstLogin": false
        }
      5. Change the API Version to 3.2.
      6. Insert system as TenantId.
      7. Click Execute to proceed.
      8. Copy the created userId.
    5. Create a Role:
      1. Click on Role.
      2. Click on POST/api/tenants/{TenantId}/application/{ApplicationName}/roles.
      3. Click on Try it out.
      4. Insert nubitalk on ApplicationName.
      5. Insert on the example value:
        {
        "name": "admin",
        "displayName": "admin"
        }
      6. Insert system on TenantId.
      7. Click Execute.
    6. Assign the role to the user:
      1. Click on Users.
      2. Click on POST/api/tenants/{TenantId}/users/{UserId}/Role/{ApplicationName}/{RoleName}.
      3. Click on Try it out.
      4. On UserId, paste the copied UseriD.
      5. On ApplicationName, insert nubitalk.
      6. On RoleName, insert admin.
      7. On TenantId, insert system.
      8. Change the API Version to 3.2.
      9. Click Execute to proceed.
    7. Assign the user on the Portal database:
      1. On MSSMS, select the portal database > tables > dbo.users.
      2. Click on Edit top 200.
      3. Insert the UserId on IdentityUserId.
      4. Edit the  dbo.tenants table.
      5. Make sure that the RessellerID has the value 1 inserted.
  2. Open https://[machine]/Portalapi/swagger, on a browser (required the sa user).
  3. Open http://[machine]/discoveryservice/swagger, on a browser
Warning: Once created the databases, to edit any configuration, it must be done on the Identity's database ConfigurationParameter.

 

 

Databases configuration

  1. Insert manually the ScriptProcedures (get it here):
    1. Extract the files from the archived folder to C:\inetpub\wwwroot\PortalAPI\Migrations.
    2. Double-click on ProcedureScripts.sql to open the file in MSSMS.
    3. Select Portal from the drop-down menu (the default is master):
      SPs01.png
    4. Click F5.
  2. Configure OneContactSystem and OneContactPBXSystem on the portal database (to reach all the required APIs, BaseService and databases):
    1. On MSSMS go to Database > Portal > Tables > OneContactSystem.
    2. Right-Click and click Edit.
    3. Fill the first line with ID 0 (after that OneAdmin points to OneContactSystem 0):
      Note: Several OneContact systems, with different IDs, can be created on the same Portal database.
      1. Copy the file (get it here) to your machine. Double-click to open in MSSMS.
      2. Edit the file to insert your information:
        016a_editonecontactsystem.png
      3. Press Ctrl+S and F5.
      4. Click on dbo.OneContactSystem to confirm that it is filled with the proper information:
        OneContactSystem2.png
  3. Configure SystemConfig on the Portal database:
    1. Edit dbo.SystemConfig:
      017a_dbo.systemconfig.png
      Note: For Azure storage configuration, there are two keys to configure: AzureStorageKey and GlobalStorageMode.

 

 

OneAdmin configuration

  1. Go to OneAdmin.
  2. Configure the instance on OneAdmin:
    1. 021_admin.png
    2. 22_admin.png
    3. 23_admin.png
    4. 23a_admin.png
    5. 024_admin.png
    6. 025_admin.png
    7. Go to License Control.
    8. Click Import and select your license file.
    9. Boot the system.
    10. Create an instance, using the wizard.
    11. Boot the instance.

 

IDs configuration

  1. Go to C:\inetpub\wwwroot\Portal.
  2. Open appsettings.
  3. Check and copy the ClientID.
  4. Go to C:\inetpub\wwwroot\OneAgetWeb.
  5. Open appsettings.
  6. Check and copy the ClientID.
  7. On MSSMS go to identity > tables > dbo.clients.
  8. Edit the dbo.clients.
  9. Check the ID that matches the Client ID:
    026_ClientID.png
  10. Go to dbo.ClientRedirectURIs and click Edit.
  11. Insert the ID and on RedirectUri insert https://*/signin-oidc.
  12. Insert another row with http://*/signin-oidc.
    027_ClientRedirectUris.png
  13. Add oneagent scope:
  14. Go to OneAgentWeb's appsettings file.
  15. Replace agent_api by oneagent_api.
  16. Edit Identity > dbo.ClientScopes table.
  17. Add the scope oneagent_api and provisioning_api to OneAgentWeb ClientID:
    34_scopeagent_api.png
    Note: invalid oneagent_api scope retunrs the following error:
    33_scopeagent_api.png

 

 

OneFlow configuration

One flow can be configured on Portal or on OneSupervisor:

  • Portal:
    1. Create an user, with a tenant administrator role.
    2. Edit the user table, on the instance's provisioning database (on MMSSM).
    3. Insert 0 on UserAuthenticationTypeID for the created user.
    4. Edit the OneFlowAPI appsetings and insert the username and password of the created user (admin by default).
  • OneSupervisor:
    1. Create an administrator with OneContact as authentication type.
    2. Insert the username and password of the created administrator on the OneFlowAPI appsettings.

 

 

 

 

 

Was this article helpful?
1 out of 1 found this helpful