Installing Python

Before proceeding with EDI configurations in System Configurator, you'll need to install Python as instructed here. This installation includes extensions needed by the EDI framework that can't be included in the Python installation delivered in the Sinch Contact Pro package.

To install Python:

  1. Get the required Python files:

    1. Open Windows PowerShell.

    2. Change the directory using cd and navigate to the Python for CEM directory, which should be under the (../SAP/ContactCenter/install/7.0.xx.x/) directory.

    3. To download the required python files, type .\get-py.ps1 and press Enter. This will:

      • Download the Python files and libraries from the web (ensure Internet access is possible) and
      • Create content and external folders in your file system.

        The destination depends on arguments passed to the script. If no argument is passed, it will go to the subfolder contents\Python\external of the folder where the get-py.ps1 script is located. During run, the script prints the Python distribution location in the console window: Generating python at location: xxx

        Note:
        If downloading fails with the get-py.ps1 script, it's most likely is a certificate issue. The script downloads from https://www.python.org and https://files.pythonhosted.org. Both certificates are issued by CA which are not trusted by the AWS EC2 instances. You can check this by copying and pasting the URLs into your browser's address bar. The browser will show either a warning or secure connection. If there's a warning, you need to install CA root to trusted root and run the script again. For information about installing certificates, see Certificates in the Installation Guide.

  2. Go to Infrastructure Administrator (IA) and connect to HAC.

  3. Make sure IA is in Deployment Mode (Connection > Deployment Mode).

  4. Right-click on HAC Nodes and then choose Refresh all hosts.

  5. Add Python to virtual units:

    1. Create as many (empty) virtual units as you have CEM instances in your system, for example ExternalPython1 and ExternalPython2.

      To create each virtual unit:

      1. Right-click Virtual Units in the model tree.

      2. Select Add Virtual Unit... > [base installation containing the generated external python] > Empty Virtual Unit Element.

      3. Enter the name of the virtual unit and click OK.

    2. To add the Python for CEM software package to each External Python virtual unit that you created, right-click Software under the virtual unit in the model tree, select Add Software... > Python for CEM, and click OK.

    3. To create instances of each External Python virtual unit that you created:

      1. Right-click Instances under the virtual unit in the model tree and select Add Instance > [HAC node name].

      2. Repeat for each HAC node.

    4. To commit the changes, choose either Deployment > Apply Changes to Host (or Apply Changes to Local System) per every HAC node, or right-click the HAC Nodes in the model tree and choose Apply All Changes to All Hosts.

    5. Verify that Python distribution was copied to VU folder of each created virtual unit instance (for example, D:\SAP\ContactCenter\VU\ExternalPython1\Python\External).

  6. Enter the value of the variable External Python Directory under Software > CEM on all CEM virtual units. Enter the full directory path.

    Use a naming convention that clearly links ExternalPython and Core virtual units, for example ExternalPython1 – Core1, ExternalPython2 – Core2, and so on.

  7. Inactivate the updated CEM virtual units.

  8. Right-click Virtual Units in the tree and choose Synchronize Instances. From the popup window that opens, select the virtual units and click OK. This advances new changes to all HAC nodes where the changed software package has instances.

  9. To commit the changes, choose either Deployment > Apply Changes to Host (or Apply Changes to Local System) per every HAC node, or right-click the HAC Nodes in the model tree and choose Apply All Changes to All Hosts.

    Note:

    If the Standard Reports package is installed in the same virtual unit as the reporting website, upgrading the Standard Reports package fails in this step as the package requires that the web site is running. After the next step (activating the virtual units), right-click the Standard Reports package and select the Upgrade Software option.

  10. Activate the updated virtual unit(s).

    Note:
    Make sure that all instances of the upgraded VUs are in status Active or Spare.

  11. Save the system model.

  12. Set IA to Monitoring Mode to propagate the new model to all nodes.