BMC Atrium Core preinstallation procedures

The BMC Atrium Core installer prompts you to enter information about the BMC Remedy Action Request (AR) System server. The following steps will help you prepare your system to install the BMC Atrium Core features on the BMC Remedy AR System server.

Ensure that the AR System server is correctly licensed. BMC Atrium Core requires an AR System server with a multiserver license.
If you want to install the BMC Remedy IT Service Management (ITSM) Suite applications, and if you are using a different user, ensure that the BMC Atrium Core user is a member of the Administrator group in the BMC Remedy AR System User form.
Temporarily disable the escalations on the AR System server. Ensure that BMC Remedy AR System is set to Disable Escalations. The BMC Atrium Core installation may not complete successfully if BMC Remedy AR System is not set to Disable Escalations.
1. Log on to the AR System server.
2. Select System > General > Centralized Configuration.
3. In the AR System Configuration Generic UI form, from the Component Name list, select the com.bmc.arsys.server.shared setting.
4. Add the Disable-Escalations-Global setting and specify the setting value as T.
5. Click Apply.
Temporarily disable AR System server encryption.
Installation of BMC Atrium Core on an encrypted AR System server is not supported. You can enable encryption after installation.
1. Log on to the AR System server.
2. Open the AR System Administration Console.
3. Select System > General > Centralized Configuration.
4. In the AR System Configuration Generic UI form, from the Component Name list, select the com.bmc.arsys.server setting.
5. Add the Encrypt-Security-Policy setting and specify the value as 2.
6. Click Apply.
7. Restart the AR System server.
Note
Re-enable escalations and encryption after you finish installing all BMC applications.
Set the Next Request ID Block Size parameter to 100.
Best practice
To improve performance when creating entries on an AR System server configured for multithreading, we recommend that you set the Next Request ID Block Size parameter to 100. This includes creating instances in BMC Atrium CMDB, such as during bulk data load from a discovery application or a reconciliation merge or copy activity.
Warning
If you have a custom workflow that depends on consecutive request IDs, a Next Request ID Block Size greater than 1 causes inconsistent results.
1. Open the AR System Application Console.
2. Select System > General > Server Information.
3. Click the Platform tab.
4. Enter Server Name Alias, and click Apply to retrieve the server information.
5. Click the Configuration tab.
6. In the Next Request ID Block Size field, type 100.
7. Click OK.
Set the size limit for the AR System database.
If you do not set size limits correctly, the database size limit might be reached.
To prevent BMC Remedy AR System from reaching the size limit of the database, perform the following changes:
- (Microsoft Windows using SQL Server) Open SQL Server Enterprise Manager and select the Automatically Grow File option for your AR System database.
- (UNIX using Oracle) Run the following SQL statement as the system user:
  ALTER DATABASE DATAFILE 'OracleHome/DATABASE/ARSYS' AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED;
  Note
  You do not need to commit or restart the server after you make the changes.
Set the JVM heap size for the Apache Tomcat server.
Best practice
If you use an existing Tomcat server instance, we recommend that you set the JVM heap size of Tomcat servers to a minimum value of 1024 MB and a permanent generation size of 256 MB. Otherwise, you might experience OutOfMemory errors and a failure to publish web services to the BMC Atrium Core Registry.
- Setting the JVM heap size for a Windows computer:
  1. Stop the Tomcat server.
  2. Run the tomcat7w application to open the Apache Tomcat Tomcat7 Properties dialog box. You can find tomcat7w.exe in the C:\Program Files \Apache Software Foundation\Tomcat7.0\bin folder.
  3. Click the Java tab.
  4. Set Maximum Memory Pool to 2048 MB or higher.
  5. In the Java Options list, set XX:MaxPermSize to 256 MB or higher.
  6. Click Apply and then click OK.
  7. Start the Tomcat server.
- Setting the JVM heap size for a UNIX computer:
  1. Stop the Tomcat server.
  2. Locate the catalina.sh file in the tomcat\bin directory.
  3. Export the following parameter in the catalina.sh file:
    export CATALINA_OPTS="-Xms1536m -Xmx2048m -XX:PermSize=128m -XX:MaxPermSize=256m"
  4. Start the Tomcat server.
Disable applications running on port 12333.
(UNIX only) Verify that the bc utility is present on UNIX.
When you begin to install BMC Atrium Core, the installer verifies that the bc utility exists in your environment. You will not be able to continue with the installation if the utility is not present.
For improved performance if you are using the BMC Remedy ITSM Suite applications with the BMC Atrium CMDB, run your BMC Remedy AR System server on a private RPC socket with the following values:
- Windows
  - RE-RPC-Socket 390698 (for the Reconciliation Engine)
  - Private-RPC-Socket 390698 10 10 (for the BMC Remedy AR System Server)
- UNIX
  - RE-RPC-Socket 390698 (for the Reconciliation Engine)
  - Private-RPC-Socket 390698 6 6 (for the AR System server)
    Note
    You can use port number 390699, but the port numbers for the BMC Remedy Reconciliation Engine and the AR System server must match.
If you changed the BMC Remedy AR System tcp port, update the port number in ar.cfg and ARSystemInstalledConfiguration.xml.
Disable the Object Modification log before performing the installation.
Before installing BMC Atrium Integrator on a server, check if the Windows Defender Antivirus is enabled on the server. If Windows Defender Antivirus is enabled, you must exclude the following folders from Windows defender configuration before installing Atrium Integrator:
- C:\Program Files\BMC Software
- C:\Users\Administrator\AppData\Local\Temp\Utilities

BMC Atrium Core preinstallation procedures

On this page