Engineering Lifecycle Management Wiki - Deployment

TWiki > Deployment Web > DeploymentTroubleshooting > IntegrationsTroubleshooting > IntegrationsTroubleshootingRationalAdapterForJIRA > GeneralTroubleshootingRationalAdapterForJIRA
Revision 3 - 2015-02-25 - 17:12:33 - Main.dmmckinn

General Troubleshooting Rational Adapter for JIRA

Authors: IntegrationsTroubleshootingTeam
Build basis: Rational Adapter for JIRA Standard Edition v1.1, Rational Collaborative Lifecycle Management version 4.0, 4.0.1, 4.0.2, 4.0.3

This page provides general troubleshooting information for IBM Rational Adapter for JIRA Standard Edition v1.1.

Turning on Logging

The administrator needs to add a file in {JIRA-install-root}/conf called 'oslc_log4j.properties'.

For example:

On Microsoft Windows: c:\Program Files (x86)\Atlassian\JIRA\conf\oslc_log4j.properties

On Linux: /opt/Atlassian/JIRA/conf/oslc_log4j.properties

Information on how to enable logging can be found at: Using JIRA logging with the JIRA adapter

Using the IBM Support Assistant Lite (ISALite) utility to collect diagnostic information

  • ISALite can be used to collect information about your JIRA Adapter environment.
  • It is bundled with JIRA adapter plugin and can be found in {JIRA-adapter-install-directory}/support/ directory.
  • Steps to run ISALite and collect the output can be found at:

Related topics: Deployment web home

External links:

Additional contributors: KotTontranakwong

Questions and comments:

Warning: Can't find topic Deployment.GeneralTroubleshootingRationalAdapterForHPALMComments

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r3 < r2 < r1 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.