Troubleshooting the Deprecation plug-in

The primary purpose of the Deprecation plug-in (BMC.ARDBC.DEPRECIATION.PLUGIN) is to support the create, read, update, and delete operations on instances in the deprecated classes in BMC Helix CMDB. Sometimes, a class is deprecated by a later version of the BMC Helix CMDB. The deprecation plug-in handles BMC Helix CMDB API calls from client apps that use the deprecated classes.

Diagnosing the issue

When you enable server-side API, filter, and SQL logging, you may see the following filter log message:

The specified plug-in does not exist.
BMC.ARDBC.DEPRECATION.PLUGIN 

The message generates an ARERR 8755 error. 

Resolution

1. Verify that the AR System Administration: AR System Configuration Generic UI form has the plug-in entry:
   Server-Plugin-Alias: BMC.ARDBC.DEPRECATION.PLUGIN BMC.ARDBC.DEPRECATION.PLUGIN <server-name>:9556
2. On the server, verify that AtriumPluginServer is running and the plug-in file deputilplugin<versionNumber>.jar is in the installPath/AtriumCore/cmdb/plugins/deprecation folder.
3. Check the AtriumPluginServer.log file in the installPath/AtriumCore/Logs folder to verify if there is any exception caused by this plug-in. If there is an exception, then fix the cause of this exception and restart the server.
4. Enable logging for the Depreciation plug-in.
   1. Open the AR System Administration: Plugin Server Configuration form. 
   2. On the Plugin Server Configuration tab, change the logging level from INFO to DEBUG. See  Logging Configurations in Setting plugin server configuration optionsin Remedy Action Request System documentation.
   3. Click Apply.

Related topics

Enabling-logs-for-the-plug-ins-server

Enabling plug-ins

Configuring-core-CMDB-components-and-plug-ins