|Skip Navigation Links|
|Exit Print View|
|Oracle Java CAPS Master Index Configuration Guide Java CAPS Documentation|
You can configure the standardization engine by specifying the standardization engine to use, configuring the files that define data standardization, and plugging in custom standardization and matching rules. You only need to specify the standardization engine to use if you are using an engine other than the Master Index Standardization Engine.
Perform any of these steps to configure the standardization engine:
Oracle Java CAPS Master Index can support standardization engines from different vendors depending on the adapter configured to communicate with the engine. Default classes are provided for using the Master Index Standardization Engine. You can implement a custom standardization engine along with customized adapters. The standardization engine configuration is defined by standardizer-api and standardizer-config elements.
Note - The default adapters for the Master Index Standardization Engine are com.sun.mdm.index.matching.adapter.SbmeStandardizerAdapter and com.sun.mdm.index.matching.adapter.SbmeStandardizerAdapterConfig.
The file opens in the NetBeans XML editor.
<standardizer-api> <class-name> com.sun.mdm.index.matching.adapter.MyStandardizerAdapter </class-name> </standardizer-api>
<standardizer-config> <class-name> com.sun.mdm.index.matching.adapter.SbmeStandardizerAdapterConfig </class-name> </standardizer-config>
You can fine-tune the standardization process by modifying the standardization files. For example, you can insert additional names or terms into the normalization or lexicon files, such as giventNames.txt and givenNameNormalizatin.txt. Depending on your data requirements, you might need to modify additional standardization files. Some of the patterns files (most notably the address patterns files) are very complex and should only be modified by personnel who thoroughly understand the defined patterns and tokens. If you modify standardization files, make sure you modify them for each variant specified in mefa.xml.
You can modify the data configuration files (lexicon and normalization files), and you can also modify the process configuration files that define the data types, variants, and how data is standardized. The process files are more complex, and should only be modified by one who is familiar with standardization concepts and with the Master Index Standardization Engine. Instructions for modifying these files are not included here. For information about these files, see Oracle Java CAPS Master Index Standardization Engine Reference.
The Master Index Standardization Engine is based on a very flexible framework that allows you to define new data types and variants so you can standardize any type of data in a custom manner. You can create new data types and variants based on the finite state machine and new variants for the existing rules-based data types. You need to import the data type or variant package into NetBeans to make it available to all master index applications or only the current one.
This section only describes importing custom data types and variants after they have been created. For information about creating a custom data type or variant, see Oracle Java CAPS Master Index Standardization Engine Reference
The data type or variant is imported into the Standardization Engine node. Data types add folders just beneath the Standardization Engine node; variants add folders under the appropriate data type (as specified in the variant package).
If you add a data type or variant to a master index application in error, you can remove it from the Standardization Engine node. You can also delete any of the existing data types or variants if they are not in use. Use caution when removing variants or data types; this action cannot be undone.
Note - The default data types and variants are stored in NetBeansHome/soa2/modules/ext/mdm/standardizer/deployment.
A confirmation dialog appears.
The data type or variant is removed from the project.