Unsupported content

 

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Verifying Cloud Portal AR Extensions installation

You can verify that the Cloud Portal AR System extensions were installed successfully by using the following procedures.

To review installation log files

  1. If you just completed the installation and the installer prompts you to view the installation log, perform the following steps:
    1. Click View Log.
    2. Check the log file for SEVERE errors and import failures.
    3. Proceed to step 4.
  2. Log on to the server that hosts enterprise AR System.
  3. Navigate to each directory listed in the following table and check the specified log files for the errors described in the Action column.
    Within the path names specified in the table:
    • On Windows, the installation path is C:\Program Files\BMC Software\BMCCloudLifeCycleManagement
    • On Linux, the installation path is /opt/bmc/BMCCloudLifeCycleManagement

      Directory

      Log file

      Action

      Windows:
      C:\Windows\Temp

      Linux:
      /tmp

      bmcclm_install_log.txt

      Verify that no SEVERE errors are reported in the log file.

      Windows:
      installPath\logs

      Linux:
      installPath/logs

      All log files in the directory

      Verify that no import failures are reported in the log files.

  4. If no errors were reported, the installation is successful. You can skip the procedures documented in this topic.
  5. For all error, (including SEVERE) messages, perform the following procedures:
  6. If a SEVERE error message was reported, additionally perform the steps documented in the Resolving product installation issues on target hosts topic.

To verify that the required services are running

  1. Log on to the server that hosts BMC Remedy AR System Server & IT Service Mgt. Suite.
  2. Verify that the javaplugin service or process is running:
    • Windows:
      1. Navigate to the following directory:
        C:\Program Files\BMC Software\ARSystem\Arserver\Db
      2. Open the armonitor.log file in a text editor and verify that the javaplugin for the Cloud Portal service is running.
    • Linux:
      1. At a command prompt, type the following command:
        ps -ef | grep Cloud_Portal
      2. In the resulting filtered output, look for the javaplugin process.

To verify entries in the SHARE:Application_Properties form

  1. In a web browser, enter the following URL: http://hostName:8080/arsys/forms/serverName/SHARE:Application_Properties
    • hostName represents the fully qualified name of the mid tier server.
    • serverName represents the name of the enterprise AR System server.
  2. Log on with the default user name, Demo, which does not require a password.
  3. Click New Search.
  4. Populate the following fields:
    • Property Name: Enter Name.
    • Property Value: Enter BMC.
  5. Click Search.
    The matching entries are displayed, as shown in the following figure:

    A product entry might appear multiple times if you have installed multiple versions of the same product installed in your environment.

  6. Verify that the following entries appear in the SHARE:Application_Properties form:
    • BMC Cloud Service Management - Public Schema Extension
    • BMC Cloud Management Foundation
    • BMC Cloud Management Administrator

    • BMC Cloud Management User

    • BMC Cloud Lifecycle Management

  7. If the form does not contain the required entries, contact BMC Support.

To verify entries in the CMF:PluginConfiguration form

  1. In a web browser, enter the following URL:  http://hostName:8080/arsys/forms/serverName/CMF:PluginConfiguration
    • hostName represents the fully qualified name of the mid tier server.
    • serverName represents the name of the Enterprise AR System server.
  2. Log on with the default user name, Demo, which does not require a password.
  3. Click Search.
    All entries in the form are displayed.
  4. Verify that the following entries are populated correctly:

    Name

    Description

    Root URL

    Platform Manager host name

    CallBackURI

    Mid tier callback URI

    FIELD_AO_HOST

    BMC Atrium Orchestrator host name

  5. If the form does not contain the required entries, contact BMC Support.

To verify entries in the SHARE:Application_Interface form

  1. In a web browser, enter the following URL: http://hostName:8080/arsys/forms/serverName/SHARE:Application_Interface
    • hostName represents the fully qualified name of the server that hosts enterprise AR System.
    • serverName represents the name of the AR System server.
  2. Log on with the default user name, Demo, which does not require a password.
  3. Click New Search.
  4. In the Consuming Application Name field, enter BMC Cloud Management Foundation.
  5. Click Search.
    The matching entries in the form are displayed.
  6. Verify that the following entries appear in the form:

    Consuming Application Name

    Providing Application Name

    Consuming Application ID

    Providing Application ID

    BMC Cloud Management Foundation

    BMC Remedy Change Management

    ID005056B5170Dv
    e6bTA06RsuAvCMB

    ID00C04F651D063
    b42125a0454854d

    BMC Cloud Management Foundation

    BMC Remedy Asset Management

    ID005056B5170Dv
    e6bTA06RsuAvCMB

    ID00C04F651D063
    b42125a04548561

  7. If the form does not contain the required entries, contact BMC Support.

To verify that you can log on to the console

  1. In a web browser, enter the following URL:
    http://hostName:8080/arsys
    hostName represents the fully qualified name of the server that hosts enterprise AR System.
  2. Log on to the BMC Cloud Lifecycle Management Administration Console with the Cloud Administrator (clmadmin) and password that you created during installation.
    For more information, see Accessing the console.

Note

If you cannot log on to the console, contact BMC Support.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments