MicroStrategy Server License Update Process

The MicroStrategy server instance that runs in the container has a pre-activated key, which is required for the operation of MicroStrategy. This pre-activated temporary key with limited life is to facilitate uninterrupted deployment and testing in the production environment. The following procedure describes the steps required to update the key.

Note: You need to request for a new license key, based on the MicroStrategy version and validity of license.

If you are a new CX Insights customer or an existing customer, renewing contract or upgrading CIC version, must check for the validity of your MicroStrategy container license and request a new license key using the prescribed license ordering process. The MicroStrategy version may or may not change for CIC release. If  the MicroStrategy version change then you must raise an Activation File Request (AFR) for a new MicroStrategy version license key. For CIC and CX Insights version mapping view the below table.

CX Insights Version	EIC Release	MicroStrategy Version
1.0	2019 R4	10.11
1.0	2020 R1	10.11
2.0	2020 R2	10.11
3.0	2020 R3	2020
4.0	2020 R4	2020
4.0	2021 R1	2020
4.0	2021 R2	2020
5.0	2021 R3	2020
5.0	2021 R4	2020
6.0	2022 R1	2021

License Ordering Process

The license ordering process is taken care by the Sales Engineers for customers, so the customers must contact their account executives to initiate the process. There are two types of license key models available based on the requirements of customer, you can select the best suited model. The following are the two types of license key models available.

For Perpetual model

If you have purchased the Stock Keeping Unit (SKU)/ Part Number, but was granted with the temporary file. Then you need to submit the Activation File Request (AFR) and communicate to Genesys Licensing Team. For more information, see Request a License File.

For Subscription model

If you have the subscription file, then the file is always temporary with the end date locked on the subscription date. The requests for the subscription files should include the corresponded subscription Sales Order number or a copy of the software delivery notice that includes Sale Order number.

License Request Checklist

Scenario	Request for New License
New CX Insights Customer on boarded	Yes
Existing CX Insights Perpetual Customer	Yes
Existing Perpetual Customer, who is moving to a higher MicroStrategy version due to CIC version upgrade	Yes
Existing Perpetual Customer, who is upgrading their CIC version but has the identical MicroStrategy version in both the CIC versions	No
Existing CX Insights Subscription Customer, who is renewing the contract	Yes
Existing CX Insights Subscription Customer, who is upgrading to a higher CIC version within the contract tenure but the MicroStrategy version mapped to the future CIC version is different from the existing CIC version	Yes
Existing CX Insights Subscription Customer, who is upgrading to a higher CIC version within the contract tenure but the MicroStrategy version mapped to the future CIC version is identical as the existing CIC version	No

 

Process of Updating new License Key

Prerequisites

• Contact your Genesys PureConnect representative to obtain a new license key.

Installing a new License Key

1. Edit the GCXI configmap using the command

kubectl edit configmap pcn-cxinsights-helmcharts-gcxi-config -n pcn-cxinsights-system .

2. Update the file with the below property with the license key under the data properties as shown below and save the file.

MSTR_LICENSE: <your new license>

3. Delete the existing GCXI container using the below command.

kubectl -n pcn-cxinsights-system scale --replicas=0 deployment/pcn-cxinsights-helmcharts-gcxi

4. Create new GCXI pod using the below command and license key will be updated for newly created gcxi container. There is a down time of  minimum 5-minutes for a new container to get up and running.

 kubectl -n pcn-cxinsights-system scale --replicas=1 deployment/pcn-cxinsights-helmcharts-gcxi

License Update Verification

After the license update is done, a log file is generated. To check the log file existence do the following:

1. Type the following command to get the pods list.

Kubectl get pods -A

2. To go inside GCXI pod, we need to run the following command. For example, GCXI pod name is pcn-cxinsights-helmcharts-gcxi-7f5c78cb65-qtsn4

kubectl exec -it pcn-cxinsights-helmcharts-gcxi-7f5c78cb65-qtsn4 bash -n pcn-cxinsights-system

3. It allows you to go inside the GCXI pod and then navigate to the logging directory, using following command.

cd /mnt/log/mstr

4. To get the list of files use the following command

ls

5. Check for the log file with name (LicMgr.log). It is available only after the license key is updated.
6. Open the LicMgr.log file and check whether the newly upgraded License Key is displayed or not.