This documentation supports the 9.0 version of BMC Remedy ITSM Deployment.

To view the latest version, select the version from the Product version menu.

Postinstallation checks

Starting with the BMC Remedy AR System 7.6.03 release, post-installation checks were added. After the installation of BMC Remedy AR System and its components is complete, post-installation checks are automatically run for the components that you have selected during the installation. Sample data is run as part of the post-installation check, to verify that the component is installed and is working correctly.

Note

The status of the postinstallation checks is displayed on the Installation Summary screen.

You can also run the post-installation checks through the BMC Remedy AR System Maintenance Tool using the Health Check tab. With this tab, you can run these checks on the components selected during the installation any number of times after the installation is complete.

For more information, see Collecting logs, diagnostics and performing system health check using the Maintenance Tool.

BMC Remedy AR System server postinstallation check

After you install BMC Remedy AR System, the following items are checked to make sure that the BMC Remedy AR System server is installed and is working correctly:

  • The connections to the database instance have been created successfully.
  • The basic BMC Remedy AR System operations such as create and set entries, and create and set forms, are working correctly.
  • The plug-ins are installed and are able to connect, and the plug-in server is working correctly.

If the checks fail, the following error messages are displayed on the Installation Summary window of the installer or on the Health Check Summary window of the Maintenance Tool:

  • If the sample form cannot connect to the BMC Remedy AR System: Failed to connect to AR Server
  • If the sample form create operation fails: Sample form creation check failed
  • If the sample field create operation fails: Sample field creation check failed
  • If the create entry operation on sample form fails: Sample entry creation check failed
  • If the modify entry operation on sample form fails: Sample entry modification check failed
  • If the delete entry operation on sample form fails: Sample entry deletion check failed
  • If the modify sample form operation fails: Sample form modification check failed
  • If the delete sample form operation fails: Sample form deletion check failed
  • If there is any problem connecting to the BMC Remedy AR System server: AR Server post installation check failed
  • If the communication to the plug-in server fails: Sample plugin call check failed

Note

If all the BMC Remedy AR System postinstallation checks are successful, the AR Server post installation check passed message is displayed.

BMC Remedy Assignment Engine postinstallation check

After you install BMC Remedy AR System, a sample application is created for the Assignment Engine, which contains:

  • Forms — DAssignee, DRequest
  • Assignment Process — DProcess
  • Assignment Rule — select driver
  • Filter — DRequest_trigger_assignment

Note

The data created on the sample forms is deleted after the check is executed successfully.


The sample application, that is, the forms, filter, process, and rules are created only once and re-used later. 

The Assignment Engine postinstallation check does the following to verify that the Assignment Engine is installed and is working correctly:

  • Verifies that the Assignment Engine process is running.
  • Creates a request in the DRequest sample form.
  • Verifies that the sample form is getting assigned to the sample assignee.

If the check fails, the following error messages are displayed on the Installation Summary screen of the installer or on the Health Check Summary screen of the Maintenance tool:

  • If the Assignment Engine process is not executing correctly: Assignment Engine process is down
  • If the Assignment Engine process on the sample form is not working: Assignment Engine is not functioning properly
  • If there is a problem communicating with the BMC Remedy AR System server: Assignment Engine post installation check failed

Note

If the Assignment Engine is working correctly, the Assignment Engine post installation check passed message is displayed.

BMC Remedy Distributed Server Option postinstallation check

After you install BMC Remedy AR System, a sample application is created to verify that the Distributed Server Option (DSO) is installed and is working correctly. This sample application contains:

  • Forms — DSO-Sample:Source, DSO-Sample:Destination
  • Distributed Mapping — DSO-Sample:Mapping
  • Filter — DSO-Sample: DSO Transfer

Note

The data created on the sample forms is deleted after the check is executed successfully. 

The sample application—that is, the forms, filter, process, and rules—are created only once and reused later. 

The DSO post-installation check does the following to verify that the DSO is installed and is working correctly:

  • Verifies that the DSO process is running.
  • Creates a request in the sample form, DSO-Sample:Source.
  • Verifies that the sample form is transferred to the sample destination form, DSO-Sample:Destination.

If the check fails, the following error messages are displayed on the Installation Summary screen of the installer or on the Health Check Summary screen of the Maintenance tool:

  • If the DSO process is not running: DSO process is down
  • If the DSO process is not running due to the absence of a DSO license: AR Distributed Server license is not applied
  • If the DSO process is not running because the DSO process entry is commented in the armonitor.cfg file: DSO process is commented in armonitor.cfg file
  • If the default distributed pool of DSO is configured in polling mode: Default distributed pool is configured as polling thread, hence can not perform DSO post install check
  • If the DSO is not working correctly: DSO is not functioning properly
  • If the DSO transfer operation on the sample form, DSO-Sample:Source is not working correctly: Sample DSO Transfer operation check failed
  • If the DSO update operation on the sample form, DSO-Sample:Source is not working correctly: Sample DSO Update operation check failed
  • If the DSO delete operation on the sample form, DSO-Sample:Source is not working correctly: Sample DSO Delete operation check failed
  • If there is any error while communicating with the BMC Remedy AR System server: DSO post installation check failed

Note

If all DSO operations on the sample forms are working correctly, the DSO post installation check passed message is displayed.

BMC Remedy Approval Server postinstallation check

After you install BMC Remedy AR System, the Approval Server post-installation check does the following to verify that the Approval Server is installed and is working correctly:

  • Verifies that the Approval Server process is running.
  • Creates a sample data on the AP-Sample2:Get Agreement form.

Note

The data created on the sample forms is deleted after the check is executed successfully.

If the check fails, the following error messages are displayed on the Installation Summary screen of the installer or on the Health Check Summary screen of the Maintenance tool:

  • If the Approval Server is not working correctly or if any failure occurs during execution: Approval Server post installation check failed
  • If the Approval Server process is down: Approval Server service is not running

Note

When the Approval Server is working correctly, the Approval Server post installation check passed message is displayed. 

BMC Remedy Email Engine postinstallation check

After you install BMC Remedy AR System, the Email Engine postinstallation check does the following to verify that the Email Engine is installed and is working correctly:

  • Verifies that the Email Engine process is running.
  • Creates a sample data on the AR System Email Messages form.

Note

The data created on the sample forms is deleted after the check is executed successfully.

If the check fails, the following error messages are displayed on the Installation Summary screen of the installer or on the Health Check Summary screen of the Maintenance tool:

  • If the Email Engine process is down: Email Engine process is down
  • If the Email Engine is not working correctly: Email Engine is not functioning properly
  • If the Email Engine is not configured: Email Engine is not configured
  • If the mailbox polling interval is in minutes, the Email Engine post-installation check is skipped: Email Engine is not configured for post install check execution
  • If any failure occurs during the working of the Email Engine: Email Engine post installation check failed

Note

When the Email Engine is working correctly, the Email Engine post installation check passed message is displayed. The Email Engine postinstallation check also verifies remote Email Engine installation.

BMC Remedy Migrator postinstallation check

After you install BMC Remedy AR System, the Migrator postinstallation check does the following to verify that the Migrator is installed and is working correctly:

  • Verifies that the Sample::Enrollments sample form is available on the BMC Remedy AR System server.
  • Collects the BMC Remedy AR System server logon credentials from the user to verify that the BMC Remedy AR System server is running.
  • Executes the Run MigratorCli command for migrating the sample form from the BMC Remedy AR System server to a temporary migrator file created in the directory where migratorcli.exe exists. A temporary log file is also generated here.

On successfully performing the preceding operations, the sample form is migrated from the migrator file back to the BMC Remedy AR System server.

Note

The data created on the sample forms is deleted after the check is run successfully.

If the check fails, the following error messages are displayed on the Installation Summary screen of the installer or on the Health Check Summary screen of the Maintenance tool:

  • If the Migrator license is not available on the target server: Migrator CLI run command failed
  • If the Sample::Enrollments sample form is not available on the target server: Migrator CLI run command failed
  • If the temporary log file is not generated: MigratorCli tmp log file not found

Note

When the Migrator is working correctly, the Migrator post installation check passedmessage is displayed.
Was this page helpful? Yes No Submitting... Thank you

Comments