CT-V Package Details
Extracting the CT-V zip file creates the directory structure as shown below:
The below section lists the content of the CT-V directory. Followed by the content are the two notes, one for the CADP JCE directory, and one for the Tokenization directory:
Note
Be sure to explore the samples directory! Thales includes many items in the SafeNetTokenization/Tokenization/Samples directory to simplify the installation, build, and preparation of the samples. For details, see the notes at the end of this listing of the directory contents.
Notes on CADP JCE (JCE Provider) subdirectories and files
The IngrianJCE/documentation directory contains the javadoc for our JCE Provider, which gives a complete description of all of its public classes and methods.
The IngrianJCE/lib/ext directory contains the following files:
| Filename | Description |
|---|---|
| commonscollections4- 4.1.jar | Apache Commons reusable Java components. Extends or augments the Java Collections Framework. |
| Ingrianlog4j-api- 2.10.0.jar | Thales log4j logging application. Required for all installations. |
| Ingrianlog4j-core- 2.10.0.jar | Thales' log4j logging application. Required for all installations. |
| commons-lang3- 3.1.jar | Apache Commons reusable Java components. Lang provides methods for manipulation of core classes in the standard Java library, utilities for the java.lang API, and helps with building methods, such as hashCode to String and equals. |
| gson-2.1.jar | A java library to convert JSON to Java objects and vice versa. |
| guava-20.0.jar | Library used for key caching. |
| IngrianNAE- 8.12.2.000.jar | The Java components of the CADP JCE Provider. Required for all installations. |
| IngrianNAE.properties | Contains the parameters used by the CADP JCE Provider. Controls logging level, log file location, communication with the Key Manager, among other features. |
Notes on Tokenization Subdirectories and Files
The Tokenization/doc directory contains the javadoc for our CT-V, which gives a complete description of all of its public classes and methods.
The Tokenization/lib/ext directory contains the following files:
| Filename | Description |
|---|---|
| c3p0-0.9.5.4.jar | Library used to augment jdbc drivers with JNDI-bindable DataSources, including DataSources that implement connection and statement pooling. Required for all installations. |
| detokenization.proper ties | Contains the parameters used to set up the bulk detokenization feature without using the token vault. |
| migration.properties | Contains the parameters used to set up the bulk migration feature using the token vault. |
| masking.properties | Contains the parameters used to set up the bulk migration feature without using the token vault |
| MultiSite.properties | Contains the parameters used to configure the multi-site feature. |
| mysql-connector- java-5.1.42-bin.jar | The MySQL JDBC driver. Required when the token vault resides on a MySQL database and CT-V Java runtime environment version is 7. |
| mysql-connector- java-5.1.48.jar | The MySQL JDBC driver. Required when a token vault resides on MySQL database and CT-V Java runtime environment version is 8 or above. |
| ojdbc7.jar | The Oracle JDBC driver. Required when the token vault resides on an Oracle database. |
| SafeNetToken.properties | Contains the parameters used by the CT-V. Required for all installations. |
| SafeNetTokenService-8.12.4.000.jar | The Java components of the CT-V. Required for all installations. |
| services.xml | The services.xml file for Axis2. |
| SfntDbp.properties | Contains the following database connection pooling parameters used by c3p0 for local database settings. Required for all installations. • com.mchange.v2.log.MLog. • com.mchange.v2.log.FallbackMLog.DEFAULT_CUTOFF_LEVEL. • c3p0.initialPoolSize • c3p0.maxStatementsPerConnection • c3p0.acquireRetryAttempts. • c3p0.checkoutTimeout • ^breakAfterAcquireFailure • ^testConnectionOnCheckin • *c3p0.minPoolSize • *c3p0.maxPoolSize • *c3p0.maxIdleTime Please find details of the C3p0 settings available at the following link: http://www.mchange.com/projects/c3p0/#configuration_properties Notes: • ^When these parameters are enabled the DatabaseRetryTime parameter of SafeNetToken.properties file gets enabled, which allows the CT-V to retry the connection to a database server only after 120seconds of first failure. • *These properties have been moved from the SafeNetToken.properties file. • Applying any property, other than the ones mentioned above, are ignored. • c3p0 logging related property (com.mchange.v2.log) can be set only once. |
| SilentInstallation.prop erties | Contains the parameters used to configure the silent installation of CT-V for Java API and Web Services. |
| sqljdbc41.jar | The SQL Server JDBC driver. Requires when the token vault resides on an MS SQL Server database. |
| TokenizationInstaller-8.12.4.000.jar | The installation program for the CT-V. Required for all installations. (But not required after installation.) |
| TVMMySQL.jar | Contains classes needed to communicate with MySQL database. |
| TVMOracle.jar | Contains the classes needed to communicate with Oracle database. |
| TVMSQLServer.jar | Contains the classes needed to communicate with SQL Server database. |
| TVMInformix.jar | Contains the classes needed to communicate with Informix database. |
| unicode.properties | Contains the parameters used by CT-V to recognize and apply Unicode characters. |
| TMService.zip | Contains SAP related binaries. |
| install_sap_tm.bat | Script to install SAPTM. |
| Utility.properties | Contains the properties to run the SearchPurgeUtility. |
The Tokenization/samples directory contains the class and java files for multiple sample applications, including:
An example of single-threaded API usage, and two examples of multi-threaded API usage.
SafeNetTokenStub-8.12.4.000.jar simplifies the sample installation process.
Unicode samples for both Java and .Net developers. These show how to use a Unicode Customization File to define custom character sets to be used in tokenization. Specified sets of Unicode input characters can be recognized and converted during tokenization processing into other specified sets of Unicode characters.
Three Web Service samples now come pre-compiled. A batch file (wsbuild.bat for Windows, wsbuild.sh for Unix-like) assists in building them.
wsrun.bat prompts for parameters.
wsrun.sh prompts for parameters.
Java files for two web service examples (WSTokenSample and WSTokenSampleOneOperation), both of which are now compiled as part of the build process.
Note
For more information on the Web service samples, refer to [Web Service Examples for Java Developers].
Class and java files for a .jsp sample utility (epcc_jsp_sample). This enables an administrator to set up a vendor to tokenize credit card numbers at the end point (e.g., at a customer website). To use this sample utility, you must run the TokenServiceAuth utility to create a token service user.
SAPTM contains Advanced Business Application Programming (ABAP) samples to invoke CT-V related operations on SAP. Refer to CT-V SAP Integration User Guide for integration task.
You must compile some samples yourself. Instructions are included in this document.
