Validate and test

this section explains how to test and validate that jpos is integrated with the {{vectera}} hsm before starting this section, install and configure jpos template per your specific requirements check out supported commands docid\ hxcf2plmevmhd88lsu6ok if you would like to see a table of commands supported by the excryptadapter if you would like to see some working java code examples of common operations, check out common operations docid\ ugnpsrmilhoopfxyi2xcz q2 overview q2 is the jpos runtime environment that runs and manages jpos' services called qbeans when you start q2, it reads configuration files in the deploy/ directory, loads the corresponding java classes, and keeps them running for hsm integration, q2 starts the excryptadapter qbean defined in 20 excrypt xml , connects it to the hsm, and manages its lifecycle q2 also supports hot‑deployment — if you add or modify a qbean xml in deploy/ , it loads or updates the service without restarting the runtime jpos connection validation to test the installation, in the directory where you built the jpos template, run the following command /gradlew q2 while the service is running, look for a log entry similar to this \<log realm="" at="2021 02 19t14 16 38 837" lifespan="1296ms"> \<send> \ request \<message command='echo'> \<token id='ag' value=''/> \</message> \[aoecho;ag;] data received \[aoecho;bc6 5 3 22ck;ag;] \ response \<message command='echo'> \<token id='bc' value='6 5 3 22ck'/> \<token id='ag' value=''/> \</message> socket disconnected \</send> \</log> if that log entry is found, jpos successfully communicated with the {{vectera}} if not, troubleshoot by verifying the connection settings in 20 excrypt xml to ensure they match your hsm’s configuration cli commands the library provides a set of cli commands that help with troubleshooting and configuration tasks please see section 7 1 1 in the jpos programmer's guide for further information on the jpos command line interface encrypt encrypts the text provided useful when used in combination with the hsm prefix to secure sensitive configuration values such as encryption keys or passwords format excrypt> encrypt \<some text> example q2> excrypt excrypt> encrypt "this is a test " hsm b7faa125c4ab3eee00fd809fc1ae65ce1c43a75699925a57 excrypt> genkcv calculates the check digits for the given key format excrypt> genkcv 64|128|192 \<key > example q2> excrypt excrypt> genkcv 128 a468c24c386b3b9d5b0102976b865b89 kcv eba8 excrypt> genkey generates a new random key encrypted under the lmk format excrypt> genkey example q2> excrypt excrypt> genkey key cryptogram 61cdeffe674f29f22a0231675d3d4319 kcv 3d35 excrypt> genwkey generates a new working key format excrypt> genwkey \<kek> \<key type> example q2> excrypt excrypt> genwkey 042faedf91fe6ed67f97982ce545401c kek key under mfk d13cadc8112880702b239ab0992611b0 key under kek 66227a59f6eb9320cee3ce2239b595a3 kcv 9fe3 excrypt> version shows the hsm version format excrypt> version example q2> excrypt excrypt> version version 6 5 3 22ck excrypt>