Documentation:HTCC:Dep:InstallingAndDeploying:9.0.0DRAFT

Deployment of Web Services and Applications

Important: This content is restricted and not viewable without a login supplied by Genesys. The information contained in this documentation is not considered final and is managed under the terms and conditions found in the Pre-release Agreement. This documentation provides the most up-to-date reference information available for this pre-release version and is restricted for use by those who have signed the Pre-release Agreement with Genesys to acquire an early version of the software.

Hardware recommendations

The solution can be deployed at a Kubernetes cluster with a minimal size of 3 nodes with an overall amount of 96 GB RAM. Recommended hardware requirements for each Kubernetes node:

• CPU: 4 - 8 cores
• RAM: 32 GB
• HDD: 500 GB

Prerequisites

1. Kubernetes cluster deployed and available. The following Kubernetes distributions are currently supported:
   • Red Hat Openshift Enterprise
   • Openshift Kubernetes Deployment
   • Rancher Kubernetes Deployment
   • Google Kubernetes Engine
   • Amazon Elastic Kubernetes Service
2. Client-side utilities installed at deployment host:
   • Kubectl tool
   • Helm client, Tiller is not required.
   • gcloud utility (for GKE deployments)
3. Valid credentials for your Kubernetes cluster.
4. The gws-microservices.tgz package downloaded from Genesys FTP to the deployment host.
5. Docker images of GWS components uploaded into a registry available from the target Kubernetes instance.

Configuring the Web Services applications

To install Web Services, set up the two application objects in the Genesys configuration environment using Genesys Administrator

• An application of type Genesys Generic Server that is called the GWS Server Application.
• An application of type Genesys Generic Client that is called the GWS Client Application.

Creating and importing the application templates

Web Services and Applications package includes a template for Genesys Generic Server (Web_Services_and_Applications_900), but you must create a new template for Genesys Generic Client.

1. To create the Genesys Generic Client template, navigate to PROVISIONING > Environment> Application Templates.
2. Select New... and configure the properties of the template as shown below:
   • Name: GWS_App
   • Type: Genesys Generic Client
   • Version: 9.0
   • State: Enabled
3. Click Save & Close.
4. To import the Genesys Generic Server template, click Upload Template in the Tasks panel. The Click 'Add' and choose application template (APD) file to import dialog opens.
5. Click Add and navigate to the templates folder in your installation package.
6. Select the Web_Services_and_Applications_900 template file and click Open.
7. Click Save & Close.

Creating the GWS Server Application

1. Navigate to PROVISIONING > Environment > Application and click New....
2. In the General section, configure the properties of the application as shown below:

1. • Name: GWS
   • Template: Web_Services_and_Applications_900
   • State: Enabled

1. Add the following connections:

1. • Configuration Server
   • SIP Server (if supporting voice)
   • Interaction Server (if supporting multimedia)
   • Universal Contact Server
   • Stat Server

For each connection added, configure the location. In the Advanced tab of Connection Info in Application parameters set the region, e.g.: locations=/USW2.

1. In the Server Info section, select a Tenant:

1. • Click Add.
   • Choose the Environment tenant (or any other tenant that has a connection to your Configuration Server).
   • Click OK.

1. Choose a Host object.
2. Add a default Listening Port:

1. • Click Add.
   • Enter the application's Port. For instance, 7000.
   • Click OK.

1. Add a "." to the Working Directory,Command Line, and Command Line Arguments fields. These values are mandatory for all applications and must be entered to save the application object. Web Services does not use these values, so the "." is used as a placeholder.

For information on configuring Workspace Web Edition, see Configuration Guide for WWE.

Creating the GWS Client Application

1. Navigate to PROVISIONING > Environment > Application and click New....
2. In the General section, configure the properties of the application as shown below:
   • Name: GWS_App
   • Template: GWS_App
   • State: Enabled
3. Add the following connections:
   • GWS Server application that was configured in the previous procedure.
4. Click Save & Close.

Deployment Steps

1. Validate your Kubernetes credentials:
   • Follow the registration web-UI steps. and type gcloud container clusters list command to see all GKE clusters available to you, if any.

1. • 1. Unpack the gws-microservices.tgz file with the following command:
        

tar -zxf gws-microservices.tgz

1. Go to the kubernetes directory:
   cd gws-microservices/kubernetes

1. Modify the <ToBeChanged: …'''> values defined in the configurations files with the actual values required by deployment.

1. • the conf/gke.env file for GKE deployments
   • the conf/openshift.env file for OpenShift deployments

1. Apply the modified configuration file to the current bash session:
   source conf/gke.env for GKE deployments
   source conf/openshift.env for OpenShift deployments

1. Deploy the monitoring stack using gws-monitoring-deploy.sh script. The script will deploy Prometheus and Grafana solutions at your Kubernetes cluster.
2. Deploy GWS infrastructure using gws-infra-deploy.sh script. The script will deploy GWS dependency servers - ElasticSearch, Redis, Consul, etc., at your Kubernetes cluster.
3. Deploy GWS microservices using gws-app-deploy.sh script.
4. Initialize GWS using gws-postinstall.sh script. The script uses GWS REST API to provision environment, contact center, and authentication client.

Upgrade Procedure

1. Download new version of gws-microservices.tgz package from Genesys FTP to the deployment host.
2. Unpack the gws-microservices.tgz file with the following command:
   tar -zxf gws-microservices.tgz
3. Go to the kubernetes directory:
   cd gws-microservices/kubernetes
4. Modify the <ToBeChanged: …> values defined in the conf/gke.env file with the actual values required by deployment. Refer to the file used in deployment.
5. Apply the modified configuration file to the current bash session:
   source conf/gke.env
6. Upgrade GWS microservices using gws-app-deploy.sh script.