Prepare the Classic Controller

Complete post-installation tasks for the Standalone Controller after installing AppDynamics Services.

1. Log in to the Controller database by using the following command:
   CODECopy

   <controller-home>/bin/controller.sh login-db

   <controller-home>/bin/controller.sh login-db

   Note: You must enter the root database password to connect to the MySQL database.
2. Retrieve the configured database credentials from the primary node:
   CODECopy

   # Run on the VA primary node helm secrets decrypt /var/appd/config/secrets.yaml.encrypted | yq .hybrid.mysql.dbUser helm secrets decrypt /var/appd/config/secrets.yaml.encrypted | yq .hybrid.mysql.dbPassword

   # Run on the VA primary node
   helm secrets decrypt /var/appd/config/secrets.yaml.encrypted | yq .hybrid.mysql.dbUser
   helm secrets decrypt /var/appd/config/secrets.yaml.encrypted | yq .hybrid.mysql.dbPassword

   Note: The hybrid.mysql.dbUser value is for Secure Application only. Do not change it from the default value: secureapp.
3. Create the user and grant access.
   Supply the <dbUser> value from the previous steps. Replace <dbUser> and <dbPassword> with the values you retrieved:
   CODECopy

   # Run in the database shell; substitute the exact decrypted values DROP USER IF EXISTS '<DB_USER>'@'%'; CREATE USER '<DB_USER>'@'%' IDENTIFIED BY '<DB_PASSWORD>' REQUIRE SSL; GRANT USAGE ON *.* TO '<DB_USER>'@'%'; GRANT SELECT, UPDATE ON controller.* TO '<DB_USER>'@'%';

   # Run in the database shell; substitute the exact decrypted values
   DROP USER IF EXISTS '<DB_USER>'@'%';
   CREATE USER '<DB_USER>'@'%' IDENTIFIED BY '<DB_PASSWORD>' REQUIRE SSL;
   GRANT USAGE ON *.* TO '<DB_USER>'@'%';
   GRANT SELECT, UPDATE ON controller.* TO '<DB_USER>'@'%';

   Note: Do not paste real passwords into shell history or tickets. Use your approved secret-handling procedure.
4. (Optional) Generate the hybrid configuration file to prevent multiple Controller restarts.
5. Access the Enterprise Console UI.
   1. Select the platform.
   2. Go to the Configuration tab.
   3. Navigate to Controller Settings > Appserver Configurations > JVM Options > JVM Config.
   4. In the JVM Config field, append the following content:
      Note: Replace <DNS_DOMAIN> with the value that you configured as dnsDomain in /var/appd/config/globals.yaml.gotmpl.

      CODECopy

      -Dappdynamics.auth.service.hosted.zone=-tnt-authn.<DNS_DOMAIN> -Dappdynamics.auth.service.port=443 -Dappdynamics.auth.service.ssl.access.enabled=true -Dappdynamics.auth.service.token.generation.enabled=true -Dappdynamics.controller.authentication.resource.accessible=true -Dappdynamics.auth.client.token.validation.enabled=true -Dappdynamics.mds.rbac.rest.api.enabled=true -Dappdynamics.rbac.internal.resource=true

      -Dappdynamics.auth.service.hosted.zone=-tnt-authn.<DNS_DOMAIN>
      -Dappdynamics.auth.service.port=443
      -Dappdynamics.auth.service.ssl.access.enabled=true
      -Dappdynamics.auth.service.token.generation.enabled=true
      -Dappdynamics.controller.authentication.resource.accessible=true
      -Dappdynamics.auth.client.token.validation.enabled=true
      -Dappdynamics.mds.rbac.rest.api.enabled=true
      -Dappdynamics.rbac.internal.resource=true

   5. Click Save.
      Note: Saving JVM configuration restarts the Controller. Coordinate this with the later hybrid bootstrap so you do not cause unnecessary restarts.