Gathering information for support
In case you need to contact AR System support to troubleshoot issues with the product, it will help to have the following diagnostic information.
General information
Have the following general information available for all the components:
- Hardware details.
- Operating system vendor and version.
- AR System server version.
- Server locale.
- Available memory for the system.
- Database vendor and version.
In addition,
Export configurations for the required component from the CCS form. Refer the knowledge article Remedy - Server - How can I export all my Centralized Configuration data into a single document? .
- Use the the information given in the Collecting diagnostics in a zip file topic to zip the configs and logs.
Collecting AR System server information
AR System server information | Log files stored in the | Configuration files |
---|---|---|
|
The log files are stored in the <Install Directory>\BMC Software\ARSystem\Arserver\Db folder. |
|
Collecting Mid Tier information
Mid Tier server |
---|
|
Have the config.properties file available if Support needs it to analyze your issues. |
Collecting Email Engine information
If you have an issue with the
Email Engine
, prepare information for the AR System server as well.
- Email details
- Details of Email Engine logs located at install directory/aremail/logs/email.log.
- Details of Email Engine logs located at install directory/aremail/logs/email.log.
- Configuration details
- Incoming mailboxes
- Outgoing mailboxes
- Export data from AR system email mailbox configuration form.
- Mail server details for example, exchange server and its version.
- Export data from AR System Service Failover Ranking.
Have the following files available if support needs them to analyze your issues:
- Log files
- Registry export (found in: HKEY_LOCAL_MACHINE\SOFTWARE\Remedy)
- emaildaemon.properties
Collecting Assignment Engine information
Have the following information available for the Assignment Engine:
- Information of the server used for installing the Assignment Engine.
- Assignment log files can help you identify functionality issues that might be encountered because the rules are not set up correctly or the processes are not configured correctly.
- For more information on enabling Assignment Engine logs, see Configuring-the-Assignment-Engine-server-settings.
Collecting Approval Server information
Have the following information available for the Approval Server:
- Information of the server used for installing the Approval Server.
- Approval Server version displayed in Share:Application properties.
- Ranking if used in a server group.
- Is the Approval Server on same machine as the AR System server?
Have the following Approval Server files available if support needs them to analyze your issues:
- Log file for Approval Server debug logging (To turn on this log, go to the AP:Administrator form, and click the Server Settings link, and select Approval Debug Mode check box.)
- Dispatcher log files if the requests are not been processed (To turn on dispatcher logging, add the Dispatch-Log-File parameter to the [ar.cfg (ar.conf)] file with the file name that you want to use.)
Collecting Data Import Tool information
Have the following information available for the Data Import Tool:
- Information of the server used for installing the Data Import Tool
- Java version
- Import log files
- Information about the AR System server used with the Data Import Tool
- JVM memory settings
Collecting BMC Atrium CMDB information
Servers used for BMC Helix CMDB data import and reconciliation
- AR System version
- Mid Tier version
- Java version
- AR System multi-server license
- AR System Next Request ID Block Size
- Number of configuration items planned
- Additional virtual memory available
- Additional database tablespace available