BDT Containers
A container is the connection and encoding information for the input or destination associated with a BDT policy. Containers can point to databases, CSV files, or fixed length files, and they can be created as standalone entities or on-the-fly during BDT policy creation. Whichever method you use, CipherTrust Manager adds the container to the list of available containers for all BDT policies, so make sure you use a descriptive name so that the container can be easily identified in the list.
If you want to create a container during the creation of a BDT policy, click Create Container on the Add Source or Add Destination page of the Create BDT Policy wizard, then see the appropriate section below based on the type of container you want to create.
If you want to create a container as a standalone entity, do the following:
Log on to the CipherTrust Manager as an administrator.
In the left pane, click Data Protection > Containers.
Click Create Container.
Refer to one of the following sections depending on the type of container you want to create.
Creating a Database Container
Enter a user-defined name for the container in the Name field. This name must be unique, and it should be descriptive enough that you can easily find this container in the list of available containers.
In the Type field, select one of the following:
DB2
ORACLE
SQL_SERVER
MYSQL
HANA
Enter the following connection information for the database:
Field Description Connection URL The URL BDT should use to access the database. For example, jdbc:mysql://localhost:3306/world
Username The user name BDT should use to access the database. Password The password for the user account. Driverclass The JDBC connection driver class, for example, com.mysql.jdbc.Driver
Click Create.
Creating a CSV Container
Enter a user-defined name for the container in the Name field. This name must be unique, and it should be descriptive enough that you can easily find this container in the list of available containers.
In the Type field, select CSV_FILE.
Enter the following information for the CSV file:
Field Description Delimiter The character that is used to divide one column from the next in the input file. Any prinatble ASCII character (except for backslash \
) can be used as a delimiter, in addition to space ( ), tab, and Ctrl-A.
NOTE: The delimiter and qualifier characters cannot be the same.Qualifier (Optional) The character to enclose fields that contain a delimiter character. Any printable ASCII character (except for backslash \
) can be used as a qualifier.
NOTE: The delimiter and qualifier characters cannot be the same.File Path The filepath relative to the inputDir or outputDir path in the BDT config file. The BDT config file resides on the local host where BDT will be running. Encoding Used to set character encoding, for example, to enable IBM’s EBCDIC. If this container is used as the input source, the encoding type must match the input file. If this container is used as a destination, this is the encoding method BDT will use for the output and failed record files.
• If you are using IBM's EBCDIC encoding, set encoding to ibm500.
• If you are encrypting ASCII files, set the encoding to ASCII.
For a complete list of supported encoding options, see Oracle Documentation.Column Count The total number of columns in the input file.
This count should include all columns in the input file, regardless of whether the column has a transform rule defined for it or not.Has Header Row If you enable this check box, BDT will treat the first row as header row. Values from this row will be treated as column names. The same column names should be mentioned in the transformation action. Unescape Input If you enable this check box, BDT will consider delimiter and qualifier characters in the input preceded by a backslash ( \
) as normal characters and part of the input data.
If you are using the BDT output file as input to another process, enable this option.
Creating a Fixed Length File Container
Enter a user-defined name for the container in the Name field. This name must be unique, and it should be descriptive enough that you can easily find this container in the list of available containers.
In the Type field, select FIXED_LENGTH_FILE.
Enter the following information for the fixed length file:
Field | Description |
---|---|
File Path | The filepath relative to the inputDir or outputDir path in the BDT configuration file. The BDT configuration file resides on the local host where BDT will be running. |
Encoding | Used to set character encoding, for example, to enable IBM EBCDIC. If this container is used as the input source, the encoding type must match the input file. If this container is used as a destination, this is the encoding method BDT will use for the output and failed record files. • If you are using IBM's EBCDIC encoding, set encoding to ibm500. • If you are encrypting ASCII files, set the encoding to ASCII. For a complete list of supported encoding options, see Oracle Documentation. |
Column Count | The total number of columns in the file. This count should include all columns in the input file, regardless of whether the column has a transform rule defined for it or not. |
Has Header Row | If you enable this option, BDT will treat the first row as header row. Values from this row will be treated as column names. The same column names should be used in the transformation action. |
Unescape Input | If you enable this check box, BDT will consider delimiter and qualifier characters in the input preceded by a backslash (\ ) as normal characters and part of the input data.If you are using the BDT output file as input to another process, enable this option. |
Line Separator | If you enable this option, BDT assumes that the records in the input data are separated by a line separator. |
Record Length | The length of one full row in the fixed length file. |
Column Position Info | The position of the columns that you want to transform with this BDT policy. For each column, use the following format:[{"column":"n","startIndex":"x","endIndex":"y"}] Multiple column definitions should be separated with a comma. For example, to specify column 0 with a starting index of 0 and an ending index of 10 along with column 1 with a starting index of 10 and an ending index of 26, you would enter: [{"column":0,"startIndex":0,"endIndex":10},{"column":1,"startIndex":10,"endIndex":26}] If the column definitions are valid, CipherTrust Manager displays a green triangle with a white check mark int he corner of this field. If the definitions are not valid, the icon changes to a red triangle with a black X. You cannot save the container until the column definitions are valid. |