Configuring access to Omnichannel Administration Utility

Last Updated : Mar 11, 2022 |

About this task

Use this procedure to configure access to Omnichannel Administration Utility so that you can open it by clicking the Launch OC Database Administration Client option in Avaya Control Manager.

Important:

This procedure is mandatory because it is the only supported method to open Omnichannel Administration Utility.

Before you begin

  • Install and commission Avaya Control Manager.

    For more information about how to install Avaya Control Manager, see Installing Avaya Control Manager document. For more information on commissioning Avaya Control Manager, see the earlier topics of this chapter.

  • Identify the Enterprise Certificate Authority of the Omnichannel windows server by running certutil.exe command in windows command tool.

    Note:

    The Name in the output is the Enterprise Certificate Authority.

Procedure

  1. To install Certificate Authority administrative tool, do the following:
    1. Open the Server Manager.
    2. Navigate to Manage > Add roles and features.
    3. In the left pane, click Server Roles.
    4. Select Active Directory Certificate Services.

      The application displays Add Roles and Features Wizard window.

    5. Click Add Features and click Next.
    6. Select the required Features and click Next.
    7. On the Active Directory Certificate Services (AD CS), click Next.
    8. Select the Role Services and click Next.
    9. Click Install.
  2. Log on to Avaya Control Manager.
  3. Navigate to Configuration > Avaya Oceana™ > Server Details.
  4. On the Avaya Oceana Server List page, do one of the following:

    • Double-click the UCAServer instance.

    • Select the check box for the UCAServer instance and click Edit.

  5. Click the System Properties tab.
  6. Expand Omni Channel.
  7. In the Omni Channel Database Server field, enter the FQDN of the Omnichannel Windows server.
  8. For a secure communication between Avaya Control Manager and your Omnichannel Windows server or host name of the VIP if using Omni Channel Cache mirroring HA, do the following:
    1. In the Omni Channel Database Server Port Number field, enter the port number 443.
    2. Select the Https check box.
    3. Click Save System Properties icon.
  9. Log on to the Omnichannel Database server.
  10. Generate a certificate pfx file.
    1. Create a Certificate Signing Request (CSR) file.

      See Creating a Certificate Signing Request.

    2. Click Start > Windows Administrative Tools > Certificate Authority.
    3. Right-click the Certificate Authority and navigate to All Tasks > Submit new request.
    4. Open the CSR file.
    5. Expand Certificate Authority and navigate to Pending Requests.
    6. Right-click the certificate you submitted and select All Tasks > Issue.
    7. Navigate to Issued Certificates.
    8. Double-click the certificate you issued.
    9. In the Details tab, select Copy to file.
    10. Select Base 64 encoded format and export cer file with name mmdev1.cer.
    11. Move the mmdev1.key and mmdev1.cer file to the same location.
    12. Open windows command line from the location.
    13. Run the command openssl pkcs12 -export -out mmdev1.pfx -inkey mmdev1.key -in mmdev1.cer
  11. Click Start > Windows Administrative Tools > Internet Information Services (IIS) Manager.
  12. In the navigation pane, click the node for Omnichannel Database server.
  13. In the content pane, in the IIS area, double-click Server Certificates.
  14. In the Actions pane, click Import.

    The Import Certificate window opens.

  15. In the Certificate file (.pfx) field, select the pfx file generated for the certificate file.
  16. In the Password field, provide the password used for the private key.
  17. Click OK.
  18. To export the Certificate Authority file, do the following:
    1. In the Windows Search field, enter mmc and search.
    2. Open the mmc.exe application.
    3. Navigate to File > Add/Remove Snap-in.
    4. From the Available snap-ins: list, select Certificates and click Add> to move it to the Selected snap-ins: list.
    5. On the Certificates snap-in page, select My user account.
    6. Click Finish.
    7. Expand Certificates - Current User and then Trusted Root Certificate Authority, then double-click Certificates.
    8. Locate the Enterprise Certificate Authority and right-click on it.
    9. Go to All Tasks > Export.

      The Certificate Export Wizard opens.

    10. Click Next.
    11. Choose the required option on the Certificate Export Wizard and click Next.
    12. For Export File Format, select Base-64 encoded X.509 (.CER) and click Next.
    13. For File to Export, in the File name field, browse and select the location for file export.
    14. Click Finish.
  19. Log on to Avaya Control Manager server.
  20. Navigate to Windows hosts file located at C:\Windows\System32\drivers\etc.
  21. Add the FQDN of the Cache server into the Windows hosts file.
  22. To import the Certificate Authority as a Trusted Root Certificate Authority through the mmc application, do the following:
    1. Run the mmc.exe application.
    2. Navigate to File > Add/Remove Snap-in.
    3. From the Available snap-ins: list, select Certificates and click Add> to move the snap-ins to the Selected snap-ins: list.
    4. On the Certificates snap-in page, select My user account.
    5. Click Finish.
    6. Click OK.
    7. Expand Certificates and right-click Trusted Root Certificate Authority.
    8. Navigate to All Tasks > Import.

      The Certificate Import Wizard opens.

    9. Click Next.
    10. Choose the required option on the Certificate Import Wizard and click Next.
    11. For File to Import, in the File name field, browse and select the location for file import.
    12. Click Finish.
  23. Log on to Avaya Control Manager .
  24. Navigate to Configuration  > Avaya Oceana™  > Server Details.
  25. On the Avaya Oceana Server List page, do one of the following:

    • Double-click the UCAServer instance.

    • Select the check box for the UCAServer instance and click Edit.

  26. Click the System Properties tab.
  27. Expand Omni Channel.
  28. In the Omni Channel Database Server field, enter the FQDN of the Omnichannel Windows server.
  29. For a non-secure communication between Avaya Control Manager and your Omnichannel Windows server, do the following:
    1. In the Omni Channel Database Server Port Number field, enter the port number 80.
    2. Clear the Https check box.
  30. Click Save.