Test TimesTen for a Replicated Configuration

To test TimesTen, a test Pod is created. It runs a script that attempts to connect to a TimesTen database by using TimesTen's client/server access. If the script can connect to the database, the script then looks at internal metadata to verify that the database is functioning properly. If the test succeeds, the test Pod is deleted.

The test connects to the database as the test user. You define this test user in the testUser metadata file. This user has CONNECT privileges, but does not have any other privileges. This limits the test and the test user's access to the database. If you do not define a test user, the test fails.

The test verifies that the active standby pair of TimesTen Classic databases are up and running and that replication between them is configured.

Let's test TimesTen.

  1. Confirm the ttclassic release.
    helm list

    The output is similar to the following:

    NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
repsamplehelm   default         1               2025-01-16 14:58:40.109402333 +0000 UTC deployed        ttclassic-2211340.1.0   22.1.1.34.0

    The repsamplehelm release exists in your namespace.

  2. Test TimesTen.
    helm test repsamplehelm
    The output is similar to the following:
    NAME: repsamplehelm
LAST DEPLOYED: Thu Jan  16 14:58:40 2025
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE:     repsamplehelm-ttclassic-test
Last Started:   Thu Jan  16 15:21:45 2025
Last Completed: Thu Jan  16 15:21:49 2025
Phase:          Succeeded
NOTES:
Version 2211340.1.0 of the ttclassic chart has been installed.

This release is named "repsamplehelm".

To learn more about the release, try:

  $ helm status repsamplehelm
  $ helm get all repsamplehelm
  $ helm history repsamplehelm

To rollback to a previous version of the chart, run:

  $ helm rollback repsamplehelm <REVISION>
    - run 'helm history repsamplehelm' for a list of revisions.

    The test for the repsamplehelm release succeeded.

Congratulations! You successfully tested TimesTen. The active and standby databases are up and running and replication between them is configured.