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.