Must Gather information for IBM Application Modernization Accelerator

Edit online

Must Gather information aids in problem determination and saves time to resolve cases. Collect all the necessary diagnostic and technical details for troubleshooting or resolving an issue with IBM Application Modernization Accelerator.

In all cases please get the following information:

  1. The version of Application Modernization Accelerator.

  2. The version of OpenShift that Application Modernization Accelerator is installed in.

For issues related to the discovery tool

  1. Version of the discovery tool (Version is in the extracted discovery tool folder ama-discovery-MAJOR.MINOR.PATCH).

  2. Operating system type and version where the discovery tool has been run.

  3. The type of collection being performed (e.g. WebSphere Application Server, JBoss etc.).

  4. The full command that was used to run the collector as well as any output to the console.

  5. The Java version available on that system (If collecting from a Java application server).

  6. If collection zip has been created (provided it is OK to share this data). The zip will contain the logs.

  7. If unable to share the zip file, the logs from the log directory where the collector was run.

For issues where Application Modernization Accelerator UI is not accessible and/or pods are not in a healthy state

  1. Get the state of the pods: 
    oc get pods -n <ama-project>
  2. Describe each pod 
    oc describe pod <pod-name> -n <ama-project>
  3. Get the logs for each pod 
    oc logs <pod-name> -n <ama-project>
  4. Get the route information 
    oc get routes -n <ama-project>
  5. Get the persistence being used: 
    oc get pvc -n <ama-project>
  6. Get the PersistenceVolume status 
    oc get pv <pvname>

When <pvname> is shown under the VOLUME heading when you get the pvc in the previous command.

For more information on persistence, see Prerequisites.

For issues where UI is not functioning as expected

  1. Browser type and version.

  2. The developer console output.

    • To open the developer console in Google Chrome, open the Chrome menu in the browser and select More Tools > Developer Tools. You can also use the shortcut Option + ⌘ + J (on macOS), or Shift + CTRL + J (on Windows/Linux).

    • To open the developer console in Firefox, click on the Firefox menu in the browser and select Web Developer > Browser Console. You can also use the shortcut Shift + ⌘ + J (on macOS) or Shift + CTRL + J (on Windows/Linux).

    • Before you can access the developer console in Safari, you first need to enable the Developer Menu. To do that, go into Safari preferences (Safari Menu > Preferences) and select the Advanced tab. After that menu is enabled, you will find the developer console by clicking on Develop > Show Javascript Console. You can also use the shortcut Option + ⌘ + C.