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 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. If you just completed installing the BMC AR System Server - Cloud Portal and Database and the installer prompts you to view the installation log, click View Log and skip to step 3.
  2. If you already logged off of the host on which you installed the product, perform the following steps:
    1. Log on to the computer on which you installed BMC AR System Server - Cloud Portal and Database.
    2. Open the installation and configuration log files listed in the Installation and configuration log files table.
  3. In the log, verify whether any error messages were reported.
    If no error messages were reported, the installation was successful and you can skip the rest of the steps in this procedure and the rest of the sections in this topic.
  4. For all error, (including SEVERE) messages, perform the following procedures:
  5. If a SEVERE error message was reported, additionally perform the steps documented in the Resolving product installation issues on target hosts topic.

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.

    PlatformService or process running
    Windows

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

    • Apache Tomcat Tomcat6
    • 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
    • slmbrsvc
    • slmcollsvc
  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. After the verification is complete, the Health Check Summary page appears.

    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.

    Note

    If you want to connect to the BMC Remedy AR System - Cloud Portal and Database host immediately after its installation using mid tier, ensure that the mid tier service is running on the BMC Remedy AR System - Cloud Portal and Database host. This will enable you to connect to the BMC Remedy AR System - Cloud Portal and Database host using the local mid tier.

To verify that the orchestration user is created

After you install BMC AR System Server - Cloud Portal and Database, the AR System server post-installation configuration steps are triggered, which create the orchestration user. The orchestration user is required for enabling the BMC Remedy AR System adapter during the BMC Atrium Orchestrator installation.

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.
    For information about accessing the mid tier, see step 5 of the To perform post-installation checks procedure.
  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 file (arsystem_install_log.txt)%temp%\
  • /usr/tmp/
  • /tmp/ 
    (SUSE Linux and Red Hat Linux)
Default log files (*.log)  
Log files generated during import of data to the 
BMC Remedy AR System server database (*.log)
ARSystemInstallDir\Logs\ARSystemInstallDir/Logs/

ITSM Installation log (bmcremedyitsmsuitepreconfiguredstack_install_log.txt)

C:\Windows\Temp

/tmp

Orchestration user creation log (arsystem_configuration_log.txt)

C:\Windows\Temp

/tmp

DSO Mapping log (atriumcore_configuration_log.txt )

C:\Windows\Temp

/tmp

BMC Remedy AR System Server error file (arerror.log)

C:\Program Files\BMC Software\ARSystem\Arserver\Db

ARSystemInstallDir/Db/
Error files (ComponentName_error.log)C:\Program Files\BMC Software\ARSystem\Arserver\DbARSystemInstallDir/Db/

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