This is usually indicative that the plugin hasn't loaded / initialised properly, or the plugin alias isn't pointing to the plugin.
If you check the plugin log in the usual logging directory (ARserver\Db\arjavaplugin.log) it should tell you if it managed to initialize the plugin and if not why not, there may also be something in arjavaplugin-stderr-<date>.log that might give you a clue if it's not starting. I'd double check the path to the jar file in pluginsvr_config.xml, also the plugin server port (that is set in pluginsvr_config.xml) has to be the same as the one used in the plugin alias in ar.conf/ar.cfg. Just looking at the plugin config in that setup document, I see <plugin> <name>MII.ARF.REGEXSPLIT</name> <classname>id.co.mii.filterplugin.SplitRegexFilterPlugin</classname> <pathelement type="location">C:/Program Files/BMC Software/ARSystem/pluginsvr/regexfilterapi-3.0.jar</pathelement> </plugin> Which I would expect to have had a few more bits in e.g. <plugin> <name>MII.ARF.REGEXSPLIT</name> <type>FilterAPI</type> <code>JAVA</code> <filename>C:/Program Files/BMC Software/ARSystem/pluginsvr/regexfilterapi-3.0.jar</filename> <classname>id.co.mii.filterplugin.SplitRegexFilterPlugin</classname> </plugin> although they may not make any difference. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
