Programming Guides › Programming Guide for Java Connector Server › Configuration Files › Converter and Validator Plug-Ins Registration

Converter and Validator Plug-Ins Registration

You can use the connector.xml file to register validator and converter plug-ins, in addition to the system-wide library made available by the server_jcs.xml file. Both types of plug-ins are configured with the com.ca.jcs.cfg.MetaPluginConfigSuite JavaBean which ties attributes and classes to plug-ins using the following three collections:

• typeToPluginMap–A map of attributes values (such as DATE, FLEXI_STR:DN) to the AttributeValidator/AttributeConverter plug-ins you want to be triggered for them.

  Note: For more information about value strings, see the Javadoc in the CA Identity Manager bookshelf for com.ca.commons.datamodel.DataModelValue.

• propertyPluginConfigs –A list of plug-ins driven by metadata settings rather than by the simple type. Each plug-in is invoked on every attribute which mentions any of the metadata settings configured in the plug-in’s metadataPropNames trigger list. However, it is free to veto its application to each target attribute after performing further checks in its constructor. For example, by throwing a PluginNotRequiredException exception.
• classPluginConfigs–List of plug-ins driven by metadata settings, where the plug-ins work over all the attribute settings for an object at once, rather than one attribute at a time.

  Note: For examples matching your intended plug-in use case, see the server_jcs.xml file.

Note: Plug-ins can arrange to have configuration JavaBeans passed to their constructors, where they require context to configure their behavior. For an example of the required syntax matching your intended use case, see the pluginConfig setting for com.ca.jcs.converter.meta.EncyptPropertyConverter in the server_jcs.xml file.