Troubleshooting AR Migrate plug-in issues


ARSYS.ARF.ARMIGRATE is a Java-based AR System Filter API plug-in. The DEV to Prod application interacts with the AR System Migrate plug-in when a build process, validate process, deploy process or rollback process is initiated.

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 on 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 General-approach-for-troubleshooting-plug-in-issues.
  3. If you need to investigate the issue further, enable the following logs:

(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 might want to change the log level.

  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.

Related topic

AR-Migrate-plug-in-configuration

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*