Troubleshooting AR Migrate plug-in issues

To troubleshoot AR System Migrate plug-in issues 

1. Verify the AR System Migrate plug-in configuration.
   For more information, see AR-Migrate-plug-in-configuration.
   For more information about the AR System Administration: Plugin Server Configuration form and AR System Administration: AR System Configuration Generic UI form, see Configuring Java plug-in servers and Updating-configuration-settings-by-using-the-AR-System-Configuration-Generic-UI-form.
2. Troubleshoot common plug-in-related issues.
   For more information, see the General-approach-for-troubleshooting-plug-in-issues.
3. To further investigate the issue, enable the following logs:
   
   • Server-side logs. For more information, see Enabling-server-side-AR-System-logs.
   • Plug-in specific logs. For more information, see To change the AR System Migrate plug-in log level
     
     

(Optional) To change the AR System Migrate plug-in log level

By default, the AR System Migrate plug-in logs are enabled and the default log level is INFO. The INFO logs capture debugging information at a granular level. For additional debugging, you have to change the log level as follows:

1. Open the <ARInstallationFolder>\pluginsvr\log4j_pluginsvr.xml file for editing. 

2. Modify the following line to change the log level from INFO to DEBUG:

   <logger name="com.bmc.arsys.plugins.armigrate.ARMigrateContext" additivity="false">
   <level value="INFO"/>
   </logger>

   to

   <logger name="com.bmc.arsys.plugins.armigrate.ARMigrateContext" additivity="false">
   <level value="DEBUG"/>
   </logger>
3. Restart AR System server.
   The ard2pplugin.log file generates the debug logs for the AR System Migrate plug-in that are tagged with the ARMigratePluginLog string.