3.14.2 System properties file for data transformation
- Organization of this subsection
(1) Format
[csc.dt.codetablepath=storage-path-of-code-conversion-table] [csc.dt.ownCodeConverter.className=class-name-of-character-code-conversion-UOC] [csc.dt.customFuncDir=storage-path-of-JAR-files-used-for-custom-functions] [csc.dt.valueTable.conversion-table-ID=file-path-of-conversion-table-used-by-change-value-function] [csc.dt.valueTableSize=total-file-size-of-conversion-table-used-by-change-value-function] [csc.dt.encodeType.conversion-table-ID={MS932|UTF8|UTF16_BIG|UTF16_LITTLE}] [csc.dt.undefined.replace.data-transformation-type=conversion-destination-character-code] [csc.dt.sizeNode.includeSelfSize={true|false}]
(2) Function
Specifies the system properties for data transformation in Service Platform. The file that has been set up can be specified when the cscbinaryparse command, csctransform command, or cscgenbinary command is executed.
(3) File storage location
The template file is stored in the following location. Copy the template file to any directory, edit the file, and then save it with any file name.
- Location of the template file:
service-platform-installation-directory\CSCTE\template\csctransform_sys.properties
(4) Specifiable properties
csc.dt.codetablepath=storage-path-of-code-conversion-table
To use a code conversion API with the character code conversion UOC, specify the storage path of the code conversion table of Code Converter in the following format:
code-conversion-table-storage-directory-path/table
For details about how to specify this, see the manual Service Platform Basic Development Guide.
csc.dt.ownCodeConverter.className=class-name-of-character-code-conversion-UOC
Register the class name of the character code conversion UOC created in the development environment, by using a fully qualified name. You must specify this property when using this character code conversion UOC in the execution environment. For details about how to specify the settings, see the manual Service Platform Basic Development Guide.
You can also specify this property in the cscbinaryparse, csctransform, and cscgenbinary commands and their command properties files. If this property is specified in multiple commands or files, the value specified in the system properties file for data transformation overrides other values. The following shows the relevant properties and arguments.
Property file or command name |
Relevant property or argument |
---|---|
System properties file for data transformation |
csc.dt.ownCodeConverter.className |
|
csctransform.uoc.class |
|
-uocclass |
csc.dt.customFuncDir=storage-path-of-JAR-files-used-for-custom-functions
To change the storage location of the JAR files used for the custom functions, specify the path.
- Important note
-
If a directory under the service platform installation directory is specified as the JAR file storage location, the JAR files might be deleted when the service platform is uninstalled. To prevent such problems, specify a location that is not under the installation directory.
csc.dt.valueTable.conversion-table-ID=file-path-of-conversion-table-used-by-change-value-function
If the data transformation definition created in the development environment contains the change value function, specify the file path of the conversion table to be used by the change value function.
- conversion-table-ID
-
Specify the conversion table ID of the conversion table.
- file-path-of-conversion-table
-
Specify the file path of the conversion table as an absolute path.
total-file-size-of-conversion-table-used-by-change-value-function ~ <Number>((1-2097151))<<10>>
If the data transformation definition created in the development environment contains the change value function, specify the upper limit of the total file size of the conversion table (unit: KB) that can be used by the change value function. You can use positive integers.
If you omit this property, 10 is assumed. If an attempt is made to read a conversion table larger than the upper limit, a KDEC40730-E message is output to the log file of the J2EE server and the startup of the HCSC server is canceled.
csc.dt.encodeType.conversion-table-ID ={MS932|UTF8|UTF16_BIG|UTF16_LITTLE}
If the data transformation definition created in the development environment contains the change value function, specify the character code to be used by the change value function.
csc.dt.undefined.replace.data-transformation-type=conversion-destination-character-code
During conversion between binary data and Unicode characters, undefined character codes are converted to space characters by default. However, they can be converted to any characters specified in this property.
To convert undefined character codes to any characters of your choice, you must specify REPLACE in one of the following:
-
-undefinedcode argument of the csctransform command
-
csctransform.undefined.code property of the data-transformation command properties file
The property to be specified differs as follows depending on the character code to be converted and the conversion type. Specify the character after conversion by using a hexadecimal number.
-
To convert binary data to Unicode characters
Specify the conversion-destination character code by using a hexadecimal number in Unicode big endian format for the relevant system property.
The following table lists the system properties that can be specified. You can specify one of these system properties for each conversion type of input binary data.
Table 3‒2: List of system properties (for conversion from binary data to Unicode characters) No.
Key name
Conversion type
Conversion-destination Unicode character code
1
csc.dt.undefined.replace.bin2xml
Halfwidth
Unicode big endian
2
csc.dt.undefined.replace.bin2xml.full
Fullwidth
-
To convert Unicode characters to binary data
Specify the conversion character code by using a hexadecimal number for the relevant system property.
The following table lists the system properties that can be specified. You can specify one of these system properties for each character code and conversion type of conversion-destination binary data.
Table 3‒3: List of system properties (for conversion from Unicode characters to binary data) No.
Key name
Conversion type
Character code of conversion-destination binary data
1
csc.dt.undefined.replace.xml2utf16be
Halfwidth
UTF16 big endian
2
csc.dt.undefined.replace.xml2utf16be.full
Fullwidth
3
csc.dt.undefined.replace.xml2utf16le
Halfwidth
UTF16 little endian
4
csc.dt.undefined.replace.xml2utf16le.full
Fullwidth
5
csc.dt.undefined.replace.xml2utf8
Halfwidth
UTF8
6
csc.dt.undefined.replace.xml2utf8.full
Fullwidth
7
csc.dt.undefined.replace.xml2ms932
Halfwidth
MS932
8
csc.dt.undefined.replace.xml2ms932.full
Fullwidth
9
csc.dt.undefined.replace.xml2keisC
Halfwidth
KEIS + EBCDIC
10
csc.dt.undefined.replace.xml2keisC.full
Fullwidth
11
csc.dt.undefined.replace.xml2keisK
Halfwidth
KEIS + EBCDIK
12
csc.dt.undefined.replace.xml2keisK.full
Fullwidth
13
csc.dt.undefined.replace.xml2keis.full
Fullwidth
KEIS
14
csc.dt.undefined.replace.xml2ibmC.latin
Halfwidth
IBM + EBCDIC (LATIN)
15
csc.dt.undefined.replace.xml2ibmC.latin.full
Fullwidth
16
csc.dt.undefined.replace.xml2ibmC.kana
Halfwidth
IBM + EBCDIC (KANA)
17
csc.dt.undefined.replace.xml2ibmC.kana.full
Fullwidth
18
csc.dt.undefined.replace.xml2ibm.full
Fullwidth
IBM
19
csc.dt.undefined.replace.xml2jefC
Halfwidth
JEF + EBCDIC
20
csc.dt.undefined.replace.xml2jefC.full
Fullwidth
21
csc.dt.undefined.replace.xml2jefK
Halfwidth
JEF + EBCDIK
22
csc.dt.undefined.replace.xml2jefK.full
Fullwidth
23
csc.dt.undefined.replace.xml2jef.full
Fullwidth
JEF
24
csc.dt.undefined.replace.xml2jis
Halfwidth
JIS
25
csc.dt.undefined.replace.xml2jis.full
Fullwidth
26
csc.dt.undefined.replace.xml2euc
Halfwidth
EUC
27
csc.dt.undefined.replace.xml2euc.full
Fullwidth
28
csc.dt.undefined.replace.xml2euchj
Halfwidth
EUC_HJ
29
csc.dt.undefined.replace.xml2euchj.full
Fullwidth
csc.dt.sizeNode.includeSelfSize={true|false} ~ <<false>>
Specify whether to use the extended size node function.
-
true
The extended size node function is used.
-
false
The extended size node function is not used.