If an EMS was configured with an activation URL through a YAML custom configuration during EMS provisioning, instead of through the Dataplane configuration UI, and are transitioning to a dataplane configured activation file then removing the helm ems.activationUrl key is required.

Prerequisites:

1. Controlplane UI access

2. For secret verification, dataplane kubernetes access will also be needed

3. Create a customconfig.yaml on the machine that will run the redeploy in the Instructions below.

customconfig.yaml:

ems:
  activationUrl: ""
 
Verify license file secret:

1. If switching to a license file, ensure the license file is already connected to the dataplane via the “Data Plane Configuration” → “Activation” menu.

2. kubectl get secrets -n <Dataplane namespace>
   a.Ensure the “cp-license-file-secret” secret exists. This contains the license file.

3. kubectl get secret/cp-license-file-secret -o yaml
   a. Ensure license-file.bin is not empty.

Instructions:

1. In the UI, select the EMS capability to open GEMS. Navigate to “Server” then “Redeploy”. 
    Note: Redeploy will restart each of the EMS pods in the expected order.

2. Check the “Use Custom Config” checkbox on the “Server Configuration” page for the Redeploy and attach the customconfig.yaml.

3. Redeploy

Verification:

Note: These commands are ran from the dataplane Kubernetes cluster

kubectl logs pod/<ems pods>

Check logging for a message with “Using license source” and ensure the desired license source is used. For a license file the expected output is “Using license source file:///boot-activation/license-file.bin.”

How to remove values.ems.activationUrl for TIBCO Platform EMS