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
- 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.
- If you already logged off of the host on which you installed the product, perform the following steps:
- Log on to the computer on which you installed BMC AR System Server - Cloud Portal and Database.
- Open the installation and configuration log files listed in the Installation and configuration log filestable.
- 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. - For all error, (including SEVERE) messages, perform the following procedures:
- 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
To ensure that the product successfully starts after installation, verify that the following services (Windows) or processes (Linux) are running on the target host.
Platform
Service 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
If one of the services or processes is not running, start it.
To perform post-installation checks
- For Windows computers, update the Terminal Services configuration options.
- From the C:\Program Files\BMC Software\ARSystem\arsystem directory on the target host, launch ARSystemMaintenanceTool and click the Health Check tab.
- On the Welcome panel, click Next.
- Specify the AR System Server administrator name, password, TCP port number, and name alias.
- 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. - Close the BMC Remedy AR System Maintenance Tool.
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
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:
- 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 checksprocedure. - 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%\ |
|
Default log files (*.log) |
|
|
Log files generated during import of data to the | 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\Db | ARSystemInstallDir/Db/ |