Unsupported content 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.

Verifying the BMC AR System Server - Cloud Portal and Database installation

You can verify that the BMC AR System Server - Cloud Portal and Database installation was successful by using the following procedures.

To review the installation logs

  1. After each of the following products are installed, click View Log and ensure that the log file does not have any SEVERE/WARNING messages:
    • BMC Remedy AR System
    • BMC CMDB
    • Atrium Integrator
    • BMC Remedy ITSM
    • BMC Remedy SRM
    • BMC Remedy Patches
    • BMC Remedy AR Post Installation using the CLM installer
  2. In case of issues, consult the Known-and-corrected-issues or Troubleshooting-the-installation-migration-or-upgrade topics. 

To verify AR System server license

If you see SEVERE errors in the Arsystem_configuration_log.txt log file, check the AR System server license that you provided during BMC AR System Server - Cloud Portal and Database installation. You must provide a valid and permanent AR System server license.

To verify running services

  1. To ensure that the product successfully starts after installation, verify that the following services (Windows) or processes (Linux) are running on the target host.

    Tip

    To verify that services are running on Windows, go to Control Panel > Administrative Tools > Services. To verify that processes are running on Linux, type ps -ef | grep -i arsystem.

    Platform

    Service or process running

    Windows

    The services that must be running on a Windows computer are:

    • Apache Tomcat Tomcat7
    • AR System Portmapper
    • BMC Remedy Action Request System Server<hostname>
    • BMC Remedy Email Engine<hostname>
    • BMC Remedy Flashboards Server<hostname>

    Linux

    The processes that must be running on a Linux computer are:

    • tomcat for Mid-tier
    • armonitor
    • arserverd
    • arforkd
    • arsignald
    • arplugin
    • arsvcdsp
    • Arservdsd
    • arcmdbd
    • arrecond
    • apsvcae
    • AREmail
    • pluginsvr/fts

  2. If one of the services or processes is not running, start it.

    Tip

    To start or stop a service on Linux, type /opt/bmc/ARSystem/bin/arsystem start (or stop).

To perform post-installation checks

  1. For Windows computers, update the Terminal Services configuration options. 
  2. From the C:\Program Files\BMC Software\ARSystem\arsystem directory on the target host, launch ARSystemMaintenanceTool and click the Health Check tab.
  3. On the Welcome panel, click Next.
  4. Specify the AR System Server administrator name, password, TCP port number, and name alias.
  5. Click Next.
     The installation verification process begins and a progress window is displayed. 
    This page lists the check passed or check failed messages, based on the verification. If the health check returns any failed messages, contact BMC Customer Support.
  6. Close the BMC Remedy AR System Maintenance Tool. 
  7. Using the mid tier hyperlink (http://<MidTier>:<port number>/arsys, for example, http://SanJoseMidTier:8080/arsys), verify that you are able to log on as a Demo user and then as an appadmin user. The default port number is 8080.

To verify that the orchestration user is created

The orchestration user is required during configuration of BMC Remedy AR System adapter in TrueSight Orchestration web console. It is created during AR Post Installation execution using CLM Installer on Primary AR Server.

To verify this user, perform the following steps:

  1. Using BMC Remedy Mid Tier, log on to BMC AR System Server - Cloud Portal and Database.
  2. Specify the user name as orchestrationuser and password as aouser.
     If you are unable to log on with the orchestration user credentials, contact BMC Customer Support.

Installation and configuration log files

The following table lists all the installation and configuration log files for BMC AR System Server - Cloud Portal and Database:

Log file name and type

Windows location

Linux location

Installation log files

  • %temp%/ arsystem_install_log.txt
  • %temp%/ atriumcore_install_log.txt
  • %temp%/ atriumintegrator_install_log.txt
  • %temp%/ bmcremedyitsmsuite_install_log.txt
  • %temp%/ bmcservicerequestmanagement_install_log.txt
  • %windir%/temp/arsystem_configuration_log.txt

/tmp/ arsystem_install_log.txt

/tmp / atriumcore_install_log.txt

/tmp / atriumintegrator_install_log.txt

/tmp / bmcremedyitsmsuite_install_log.txt

/tmp / bmcservicerequestmanagement_install_log.txt

/tmp/arsystem_configuration_log.txt

Import logs

  • ARSystemInstallDir/Logs
  • AtriumCoreInstallDir/Logs
  • AtriumIntegratorInstallDir/Logs
  • ITSMInstallDir/Logs
  • SRMInstallDir/Logs

Ensure that there is no XXX__error.log

  • ARSystemInstallDir/Logs
  • AtriumCoreInstallDir/Logs
  • AtriumIntegratorInstallDir/Logs
  • ITSMInstallDir/Logs
  • SRMInstallDir/Logs

Ensure that there is no

Application Logs

ARSystemInstallDir/Arserver/Db

ARSystemInstallDir/db


 

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