Skip to main content
NetApp Knowledge Base

How to determine if AIQUM files failed deployment on Windows

Views:
907
Visibility:
Public
Votes:
3
Category:
oncommand-unified-manager
Specialty:
legacy
Last Updated:

Applies to

  • Active IQ Unified Manager (AIQUM) Version Independent
  • OnCommand Unified Manager (OCUM) Version Independent
  • OnCommand Performance Manager (OPM) Version Independent

Procedure

How to determine if *.war and/or *.ear files failed deployment or were actively undeployed

  1. Log in to the Windows host as an Administrator.
  2. Open an Elevated/Administrator Command Prompt.
  3. Change directory to the installation directory.
  4. List the contents
Example of using the default install path
C:\>cd "\Program Files\NetApp\essentials\jboss\standalone\deployments"

C:\Program Files\NetApp\essentials\jboss\standalone\deployments>dir
Volume in drive C has no label.
Volume Serial Number is 3E8A-7026

Directory of C:\Program Files\NetApp\essentials\jboss\standalone\deployments

01/16/2018 01:35 PM <DIR> .
01/16/2018 01:35 PM <DIR> ..
10/23/2017 09:50 AM 159,509 commons-io.jar
01/16/2018 01:35 PM 222 commons-io.jar.failed
01/16/2018 01:22 PM <DIR> datasources.war
01/16/2018 01:35 PM 222 datasources.war.failed
10/23/2017 09:50 AM 193,653,963 dfm-app.war
01/16/2018 01:35 PM 222 dfm-app.war.failed
10/23/2017 09:50 AM 352,602,041 dfm-report-app.ear
01/16/2018 01:35 PM 222 dfm-report-app.ear.failed
10/23/2017 09:50 AM 9,881,686 dfm-script-plugin.war
01/16/2018 01:35 PM 222 dfm-script-plugin.war.failed
10/23/2017 09:50 AM 4,659 keystore-manager.jar
01/16/2018 01:35 PM 222 keystore-manager.jar.failed
10/23/2017 02:22 AM 2,785,507 mega-app.ear
01/16/2018 01:35 PM 222 mega-app.ear.failed
01/16/2018 01:22 PM <DIR> mega-schema.war
01/16/2018 01:35 PM 222 mega-schema.war.failed
10/23/2017 09:50 AM 2,288 password-manager.jar
01/16/2018 01:35 PM 222 password-manager.jar.failed
08/18/2016 07:12 PM 8,870 README.txt
17 File(s) 559,100,521 bytes
4 Dir(s) 1,074,815,438,848 bytes free

C:\Program Files\NetApp\essentials\jboss\standalone\deployments>
See below articles for correction action:

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.