Before Beginning
Before using CT-V Bulk Utility, ensure that the Key Manager and CT-V are up and running.
The following tasks must be completed to use CT-V Bulk Utility:
Configuring the CADP_for_JAVA.properties File
The following sample CADP_for_JAVA.properties file text excludes all of the descriptive text in the properties file:
Version=2.4
NAE_IP=
NAE_Port=9000
Protocol=tcp
Use_Persistent_Connections=yes
Size_of_Connection_Pool=300
Connection_Timeout=60000
Connection_Idle_Timeout=600000
Connection_Retry_Interval=600000
Cluster_Synchronization_Delay=170
#Cipher_Spec=HIGH:!ADH:!DH:!DSA:!EXPORT:RSA+RC4:RSA+DES:RSA+AES
CA_File=
Cert_File=
Key_File=
Passphrase=
Symmetric_Key_Cache_Enabled=no
Symmetric_Key_Cache_Expiry=43200
Symmetric_Key_Cache_AutoRefresh_Interval=0
Local_Cipher_Cache_Expiry=0
Log_Level=MEDIUM
Log_File=
Log_Rotation=Daily
Log_Size_Limit=100k
SysLog_IP=
SysLog_Port=
SysLog_Protocol=
Note
In the CADP_for_JAVA.properties file, consider the following:
Version must not change from “2.4”.
Specify the IP address of the NAE Server in the
NAE_IPfield.Specify the
NAE_Porton which Key Manager listens to requests. The default is 9000.While getting acquainted with CT-V Bulk Utility, it is recommended to specify “tcp” instead of “ssl” in the Protocol field. Ensure that the NAE Server is set to use TCP connections.
Storing multiple properties files in the same folder may be problematic.
Creating an AES Key
The samples in this document require an AES–256 key named token_key. This key should be used as a global key to avoid any permission restrictions.
Note
In production environments, the use of global keys is discouraged because they avoid the permission restrictions that protect the data.
Creating a Local NAE User
For the samples in this document, a local NAE user named NAE_User1 with password qwerty12345 is used. The local user must have permission to encrypt and decrypt using the AES key (which is guaranteed if the AES key is global).
