Registering validation rules

You can register the rule XML files with the application by adding a new context parameter for each rule XML file in the <runtime_sandbox>/repository/eardata/smcfs/extn/web.xml file.

Use one of the following ways to register the rule XML files with the application by adding a new context parameter for each rule XML file in the <runtime_sandbox>/repository/eardata/smcfs/extn/web.xml file.

<context-param>
   <param-name>scui-validation-rules-file-<unique-identifier></param-name>
   <param-value><file-path-inside-webapp>::<load order></param-value> 
</context-param>

<context-param>
   <param-name>scui-validation-rules-file-unique-identifier</param-name>
   <param-value>fully-qualified-name-of-the-file::load order</param-value> 
</context-param>

where load order defines the order in which the rules file must be loaded. File having the least load order will be read first. Multiple files can have same load order. If no load order is defined, system considers it as zero.

Note: You must use load order of over 500 to register the validation rule files.

For example,

<context-param>
   <param-name>scui-validation-rules-file-fwk-1</param-name>
   <param-value>/WEB-INF/rules1.xml</param-value> 
</context-param> 
<context-param>
   <param-name>scui-validation-rules-file-fwk-2</param-name>
   <param-value>/WEB-INF/rules2.xml::1</param-value> 
</context-param> 
<context-param>
   <param-name>scui-validation-rules-file-fwk-3</param-name>
   <param-value>/com/test/rules-being-used-from-datatypes.xml::2</param-value> 
</context-param>

Note: The validation rule files containing regular expressions, which are being referenced from the datatypes.xml file, must be kept inside a JAR file and the JAR file must be available in APP dynamic classpath. The regular expression files containing other rules (which are not being referenced from datatypes.xml file) must be kept inside the <runtime_sandbox>/repository directory.IBM® recommends you to keep such files inside the EARFILE/WARFILE/WEB-INF directory to make them inaccessible by http access.