The Assisted MIGration Offering (AMIGO) checklist provides the steps needed to install/upgrade TrueSight Presentation Server, Atrium Single Sign On, TrueSight Infrastructure Management, and the Integration Service Node.

The checklist is comprised of material gathered from multiple resources, such as documentation, knowledge articles, webinars, and feedback from other customers.  The result is a definitive list of steps needed to efficiently and successfully install/upgrade TrueSight. 

 Preinstallation, Planning, and Requirements
 How & what to download

To download the TrueSight 10.7 components, go here.

In the "Filter Products" field, type in "TrueSight Infrastructure", without the quotes
Click the Go button
In the right side pane, click TrueSight Infrastructure Management
Note: If you don't see TrueSight Infrastructure Management, then contact your Account Manager.

The version in the drop-down menu will default to the latest version, 10.7.00
Click the Products tab

Get the following components corresponding to your operating system:
  •TrueSight Infrastructure Management Version 10.7.00 - Core Components
  •Infrastructure Management Base Monitoring Installation Repository Version 10.7.00 - March 2017
  •Infrastructure Management Extended Monitoring Installation Repository Version 10.7.00 - March 2017

Close the window and go back to the main EPD screen.

In the "Filter Products" field, type in "TrueSight Presentation", without the quotes
Click the Go button
In the right side pane, click TrueSight Presentation Server
Note: If you don't see TrueSight Presentation Server, then contact your Account Manager.

The version in the drop-down menu will default to the latest version, 10.7.00
Click the Products tab

Get the following component corresponding to your operating system:

  •TrueSight Presentation Server Version 10.7.00

 

If you are upgrading from a previous version of TrueSight, you may already have Atrium Single Sign On 9.0.00 Patch 01 or Patch 02.
  •To check, open your Atrium SSO configuration window (https://hostname:8443/atriumsso/atsso/console/login/Login.html) and the version will be displayed on the login screen.

If you don't have Atrium Single Sign On 9.0.00 Patch 01 or 02, in the "Filter Products" field, type in "Atrium Single", without the quotes
Click the Go button
In the right side pane, click BMC Atrium Single Sign On
The version in the drop-down menu will default to the latest version, 9.0.00
Click the Patches tab
Get the following component corresponding to your operating system:
  •BMC Atrium Single Sign On Version 9.0.00 Patch 002

Note that TrueSight requires all of the components listed above (e.g. Presentation Server, Atrium SSO, etc.).
If you need more detail on the above steps, go here

Note: The Infrastructure Management component should be on a dedicated machine (e.g. Do not share the server with an Integration Service, Presentation Server, etc.)
The recommended configuration is to have the Presentation Server and Atrium SSO on one box and TrueSight Infrastructure Management on another.
Putting all TrueSight Operations Management components on a single server is possible only for a proof-of-concept or as a test, not for production. Go here for details.

When downloading the files, save the files to a local directory on the server where the files will be installed. BMC Software recommends that you install TrueSight from a local copy of the installation image and not from a network drive. Installing from a network drive can cause delays in completing the installation.

 Windows environment planning

Note that you will need a minimum of two boxes for TrueSight Operations Management:
  a) One box to host Presentation Server and Atrium SSO
  b) Another box to host Infrastructure Manager

Since Atrium SSO and Presentation Server can be installed on the same box, you may want to select an OS which is supported by both applications.

 Atrium SSO

 Atrium SSO hardware & OS requirements
  •Windows Server 2012 (only from BMC Atrium Single Sign-On 9.0.00 Patch 1+ (9.0.00.01+))
  •Windows Server 2008 R2
  •Windows Server 2003
  •11Gb disk space

Update Terminal Services configuration options:
Start --> Run -> regedit
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
Change:
PerSessionTempDir to 0
and DeleteTempDirsOnExit to 0

If you are using the Data Execution Prevention (DEP) feature in Windows, configure DEP for executable programs:
0. Extract the AtriumSSO installation file
1. Start --> Control Panel -> (System and Security) -> System
2.Click the Advanced tab (or Advanced System Settings)
3.In the Performance area, click Settings.
4.On the Data Execution Prevention tab, verify if the "Turn on DEP for all programs and services except those I select" option is selected.
If the "Turn on DEP for essential Windows programs and services only" option is selected, no configuration is required. 
5.If the "Turn on DEP for all programs and services except for those I select" option is selected, click Add.
6.Browse to the executable, and then click Open.
The installation program appears in the DEP program area.
7.Click Apply; then click OK.

If you made changes to the Registry and/or to DEP settings, reboot the computer.

Click here to go to the Atrium SSO requirements documentation, if needed.
Click here regarding the Terminal Services and DEP steps, if needed.

 TrueSight Presentation Server

Presentation Server hardware & OS requirements

  •Windows 2016 64 bit, Standard or Datacenter Edition
  •Windows 2012 R2 64 bit, Standard or Datacenter Edition
  •Windows 2012 64 bit, Standard or Datacenter Edition
  •Windows 2008 R2 64 bit, Standard, Datacenter, or Enterprise Edition
  •RAM: 8Gb for Small environments / 24Gb for Medium environments / 32Gb for Large environments
  •Disk space: 200Gb for Small environments / 300Gb for Medium environments / 500Gb for Large environments (15,000 RPM drive or a tier 1 SAN storage with 2–4 GBps SAN dedicated channel for Medium and Large sizes)
  •CPU: 4 vCPU for Small & Medium environments / 8 vCPU for Large environments (2.2 GHz for all sizes)

Click here to determine the size of your Presentation Server.

The hardware requirements are the same for physical or virtual machines.

Parallel CPUs usually improves user response time better than a single CPU with a higher clock speed.

 TrueSight Infrastructure Management server

TrueSight Infrastructure Management server hardware & OS requirements

  •Windows 2016 64 bit, Standard or Datacenter Edition
  •Windows 2012 R2 64 bit, Standard or Datacenter Edition
  •Windows 2012 64 bit, Standard or Datacenter Edition
  •Windows 2008 R2 64 bit
  •RAM: 8Gb for Small environments / 16Gb for Medium environments / 32Gb for Large environments
  •Disk space for TSIM bundled with Sybase DB: 200Gb for Small environments / 300Gb for Medium environments / 600Gb for Large environments
  •Disk space for TSIM server only (Oracle info on next line): 30Gb for Small environments / 50Gb for Medium environments / 100Gb for Large environments
  •Disk space for TSIM's Oracle DB: 170Gb for Small environments / 250Gb for Medium environments / 500Gb for Large environments
  •15000 RPM drive or Tier 1 SAN storage (2-4 GBps SAN dedicated channel)
  •CPU: For Small & Medium environments: Intel Core i7 CPU: 4 vCPU, Frequency: 2.2GHz, Threads :16 (For Large TSIM servers use Intel Core i7 CPU: 8 vCPU, Frequency: 2.2GHz Threads :16)
  •Pagefile: Pagefile size should be Microsoft Windows Recommended

For more detail on the above requirements, go here and here

Veritas file systems are not recommended for large deployments due to performance problems.

Use RAID 10 or 01 on larger TrueSight installations to better satisfy the higher demands on write I/O operations. BMC does not recommend using RAID 5.
Use a larger number of physical disk drives (spindle count) instead of larger capacity disks. Because disk drive throughput performance has not increased at the same rate as disk capacity, you can achieve better performance with smaller disks.

Parallel CPUs usually improves user response time better than a single CPU with a higher clock speed.

Configure Terminal Services to save log files:
  1. Open the Registry Editor and navigate to the following registry:
  HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server
  2. Verify that the following registry keys in the Terminal Server registry have the appropriate settings:
    •DeleteTempDirsOnExit (REG_DWORD) = 0
    •PerSessionTempDir (REG_DWORD) = 0
    •FlatTempDir (REG_SZ) = 1 (Note that this key may not exist. There is no need to create it if it isn't seen.)

Ensure that the value is 2 for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation

If you made any change to the registry, reboot the computer.

Disable Data Execution Prevention on setup.exe:
On Windows 2008:
  0. Extract the TrueSight Infrastructure Management installation file
  1. From the Start menu, click Control Panel > System and Security > System > Advanced system settings.
  The System Properties dialog box is displayed.
  2. On the Advanced tab, under Performance, click Settings.
  The Performance Options dialog box is displayed.
  3. On the Data Execution Prevention tab, click Add.
  4. Browse the localDirectory\TrueSightServer\Disk1 directory, and select the setup.exe file, and click Open.
  5. Click Apply.
  6. Click OK
On Windows 2012:
  1. Open the Start screen, right click the My PC (Computer) tile and click Properties.
  2. Click Advanced system settings in the left pane, go to the Advanced tab and click Settings in the Performance section.
  3. Next in the Performance Options window, go to the Data Execution Prevention tab, and click Add.
  4. Browse the localDirectory\TrueSightServer\Disk1 directory, and select the setup.exe file, and click Open.
  5. Click Apply.
  6. Click OK

If you are installing the Infrastructure Management Server on Windows 2016, the Defender Service removes some of the installation files during installation. To avoid this, perform any of the following:

  •  Add an exception rule in the Defender Service to recognize all files in the Infrastructure Management Server installation directory as valid files.
  • Disable the Defender Service.

 

Clean the following directories:
  •the temporary folder in your home folder
  •%Temp%
  •%Tmp%
  •C:\WINNT\Temp (if it exists)
  •C:\Windows\Temp (if it exists)
You might not be able to delete all the files, but BMC recommends that you remove any files or directories that match "Infrastructure Management*" or "TrueSight*".

Note: Windows installation accounts no longer needs to be a direct member of the Administrators group. (But the CLI and pwtray.exe presently still require direct membership to the Administrator's group.)

Ensure that the Windows Firewall service is running (Start -> Run -> services.msc)

For more detail on the above steps, go here

If you want to integrate TrueSight with SCOM, ensure that .NET Framework version 3.0 is installed. Use the Role Management tool to accomplish this. For more information about how to install the .NET Framework, visit microsoft.com.

BMC recommends that you remove all the files or folders named "Program" or those that begin with "Program" from the drive where TrueSight is installed (with the exception of "Program Files" or "Program Files (x86)"). For example, if TrueSight is installed under C:\Program Files, but another folder C:\Program exists on the same drive, the upgrade may fail. (This recommendation holds true when you install hotfixes also.)

Ensure that the target computer has the most recent patch level for supported Windows operating systems. If it does not, use Microsoft Update (or Windows Update) to update it.

User Access Control (UAC) must be disabled.

If you are using the Remote Desktop Connection (RDC) to install the product, then the RDC must be in console mode.

The following ports should be available on the TrueSight Infrastructure Management server:
7, 80, 443, 1099, 1100, 1827, 1828, 1851, 2638, 3084, 3115, 3182, 3183, 8005, 8008, 8009, 8093, 8080, 9149, 12123, 12124, 12126, 12130, 12134, 12141, 15000, and 45000.

Perl must not be installed on the target computer where TrueSight Infrastructure Management is being installed.

 TrueSight Integration Service

TrueSight IS hardware & OS requirements

  •Windows 2016 Standard or Datacenter (64 bit)
  •Windows 2012 R2 Standard or Datacenter (64 bit)
  •Windows 2012 Standard or Datacenter (64 bit)
  •Windows 2008 R2 Standard or Datacenter (64 bit)
  •Windows 2008 SP2 Standard or Datacenter (64 bit)

  •RAM for Small/Medium/Large configurations: 4Gb/8Gb/8Gb
  •50Gb of disk space

BMC recommends a maximum of three Integration Services instances running on a single Integration Service host computer.

Configure Terminal Services to save log files:
  1. Open the Registry Editor and navigate to the following registry:
  HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server
  2. Verify that the following registry keys in the Terminal Server registry have the appropriate settings:
    •DeleteTempDirsOnExit (REG_DWORD) = 0
    •PerSessionTempDir (REG_DWORD) = 0
  Reboot if you made changes to the registry

Click here for more hardware details.
Click here for more OS details.

 Linux and UNIX environment planning

Note that you will need a minimum of two boxes for TrueSight Operations Management:
  a) One box to host Presentation Server and Atrium SSO
  b) Another box to host Infrastructure Manager

Since Atrium SSO and Presentation Server can be installed on the same box, you may want to select an OS which is supported by both applications.

Ensure that both the unzip and gzip utilities are present in the $PATH.

 Atrium SSO

Atrium SSO hardware & OS requirements
  •Red Hat Enterprise Linux 5, 6 (64-bit only, for Server Editions)
  •Solaris 10 (64-bit only)
  •11Gb disk space

On Red Hat Enterprise Linux computers, the entropy level on the server must be at least 3000. Otherwise, you might experience installation issues. To check your system's entropy level:
cat /proc/sys/kernel/random/entropy_avail
If the level of entropy is less than 3000, run the following commands as root user or restart your computer. Running the command is the preferred option as it helps in maintaining the entropy level after installation.
yum install rng-tools
echo 'EXTRAOPTIONS="-i -o /dev/random -r /dev/urandom -t 10 -W 2048"' >>/etc/sysconfig/rngd
chkconfig rngd on
service rngd restart

The $TMP directory must have execute permissions. You can assign the execute permissions by removing the noexec attribute from the /tmp line in the /etc/fstab file. For example, remove the noexec entry from the following:
UUID=0aef28b9-3d11-4ab4-a0d4-d53d7b4d3aa4 /tmp ext4 defaults,noexec 1 2

Click here as a reference, if needed.

 Presentation Server

Presentation Server hardware & OS requirements
  •Red Hat Enterprise Linux versions 6.7, 6.8, 7.0, 7.1, 7.2, 7.3 (64-bit versions)
  - Run 'cat /etc/redhat-release' to get the Linux version.
  - Run 'uname -a' to get the kernel version, as certain versions are supported:
  - Supported kernel version for Red Hat Enterprise Linux versions:
  -- 6.7 (2.6.32-573)
  -- 6.8 (2.6.32-642)
  -- 7.0 (3.10.0-123)
  -- 7.1 (3.10.0-229)
  -- 7.2 (3.10.0-327)
  -- 7.3 (3.10.0-514)

  •SUSE Linux Enterprise Server 11 Service Pack 2, Service Pack 3, 12 (64-bit versions)
  - Run 'uname -a' to get the kernel version, as certain versions are supported:
  - Supported kernel version for SUSE Linux Enterprise Server versions:
  -- 11 Service Pack 2 (3.0.13-0.27)
  -- 11 Service Pack 3 (3.0.76-0.11.1)
  -- 12 (3.12.28-4.6)

  •Oracle Linux Server (with Unbreakable Enterprise Kernel (UEK) Release 4):
- 6.8
- 7.3


  •RAM: 8Gb for Small environments / 24Gb for Medium environments / 32Gb for Large environments
  •Disk space: 200Gb for Small environments / 300Gb for Medium environments / 500Gb for Large environments (15,000 RPM drive or a tier 1 SAN storage with 2–4 GBps SAN dedicated channel for Medium and Large sizes)
  •CPU: 4 vCPU for Small & Medium environments / 8 vCPU for Large environments (2.2 GHz for all sizes)
Click here to determine the size of your Presentation Server.

  •Character encoding: LANG=_.UTF-8, LC_ALL=_.UTF-8, LANGUAGE=_.UTF-8

The hardware requirements are the same for physical or virtual machines.

Parallel CPUs usually improves user response time better than a single CPU with a higher clock speed.

A non-root user who has modification permissions to specific directories and files is needed to install the Presentation Server. A user with root privileges cannot install the Presentation Server.

Red Hat (TSPS, TSIM, ISN): Run the following commands to install required OS libraries:
yum install libXtst.i686 libXtst.x86_64 libXtst-1.0.1-3.1 libX11-devel-1.0.3-11.el5
yum install glibc.i686 glibc.x86_64 glibc-2.12.x86_64 glibc-2.12-1.107.el6.i686 glibc-devel-2.5-65
yum install libstdc++.i686 libstdc++.x86_64 
yum install compat-libstdc++-33.i686 compat-libstdc++-33.x86_64 compat-libstdc++-33-3.2.3-69.e16.i686
yum install compat-libstdc++-296.i686
yum install pam.i686 pam.x86_64 pam-1.1.1-13.e16.i686
yum install libgtk-x11-2.0.so.0
yum groupinstall 'X Window System'

The 'yum install' commands require a Red Hat subscription. Register the system by clicking System >Administration > Red Hat Subscription Manager in the menu on the server itself.
Note: The above commands will install both 32 bit and 64 bit libraries on the 64 bit system, which is intentional.
If an error occurs while installing a 32 bit library, try re-running the 'yum install' command with both 32-bit and 64-bit versions. For example:
yum install pam.i686 pam.x86_64
If the "No package <package name> name available" message is seen, run the command again without specifying the version. For example:
"No package libX11-devel-1.0.3-11.el5 available."
"Error: Nothing to do"
# yum install libX11-devel

SUSE: Click here for the commands to install the required OS libraries.

 TrueSight Infrastructure Management server

TrueSight Infrastructure Management server hardware & OS requirements
  •Red Hat Enterprise Linux versions 6.7a, 6.8a, 7.0b, 7.1b, 7.2b, 7.3c (64-bit versions)
  - Run 'cat /etc/redhat-release' to get the Linux version.
  - Run 'uname -a' to get the kernel version, as certain versions are supported:
  - aSupported kernel version for Red Hat Enterprise Linux versions 6.7 - 6.8 is 2.6.32.
  - bSupported kernel version for Red Hat Enterprise Linux versions 7.0 - 7.2 is 3.10.0.
  - cSupported kernel version for Red Hat Enterprise Linux versions 7.3 is 3.10.0-514.
  •SUSE Linux Enterprise Server 11 Service Pack 2, 11 Service Pack 3, and 12
  - Run 'uname -a' to get the kernel version, as certain versions are supported:
  - Supported kernel version support for SUSE:
   --11 Service Pack 2 = 3.0.13
   --11 Service Pack 3 = 3.0.76
   --12 = 3.12.28
  •Oracle Linux Server versions 6.8, 7.3 


  •RAM: 8Gb for Small environments / 16Gb for Medium environments / 32Gb for Large environments
  •Disk space for Small/Medium/Large configurations with Sybase DB:200Gb/300Gb/600Gb
  •Disk space for Small/Medium/Large configurations with Oracle DB:30Gb for TrueSight Infrastructure Management server & 170Gb for DB / 50Gb for TrueSight Infrastructure Management server & 250Gb for DB / 100Gb for TrueSight Infrastructure Management server & 500Gb for DB
  •15000 RPM drive or Tier 1 SAN storage (2-4 GBps SAN dedicated channel)
  •File descriptors (ulimit -n): 4096
  •Ports for Linux: The following ports should be available in listen mode:
7, 80, 443, 1099, 1100, 1827, 1828, 1851, 2638, 3084, 3115, 3182, 3183, 8005, 8008, 8009, 8080, 8093, 9149, 12123, 12124, 12126, 12134, 12141, 15000, 45000.

Veritas file systems are not recommended for large deployments due to performance problems.

Use RAID 10 or 01 on larger TrueSight installations to better satisfy the higher demands on write I/O operations. BMC does not recommend using RAID 5.
Use a larger number of physical disk drives (spindle count) instead of larger capacity disks. Because disk drive throughput performance has not increased at the same rate as disk capacity, you can achieve better performance with smaller disks.

Parallel CPUs usually improves user response time better than a single CPU with a higher clock speed.

Red Hat (TSPS, TSIM, ISN): Run the following commands to install required OS libraries:
yum install libXtst.i686 libXtst.x86_64 libXtst-1.0.1-3.1 libX11-devel-1.0.3-11.el5
yum install glibc.i686 glibc.x86_64 glibc-2.12.x86_64 glibc-2.12-1.107.el6.i686 glibc-devel-2.5-65
yum install libstdc++.i686 libstdc++.x86_64 
yum install compat-libstdc++-33.i686 compat-libstdc++-33.x86_64 compat-libstdc++-33-3.2.3-69.e16.i686
yum install compat-libstdc++-296.i686 compat-libstdc++-296.x86_64
yum install pam.i686 pam.x86_64 pam-1.1.1-13.e16.i686
yum install libgtk-x11-2.0.so.0
yum install libfreebl3.so
yum groupinstall 'X Window System'

The 'yum install' commands require a Red Hat subscription. Register the system by clicking System >Administration > Red Hat Subscription Manager in the menu on the server itself.
Note: The above commands will install both 32 bit and 64 bit libraries on the 64 bit system, which is intentional.
If an error occurs while installing a 32 bit library, try re-running the 'yum install' command with both 32-bit and 64-bit versions. For example:
yum install pam.i686 pam.x86_64
If the "No package <package name> name available" message is seen, run the command again without specifying the version. For example:
"No package libX11-devel-1.0.3-11.el5 available."
"Error: Nothing to do"
# yum install libX11-devel

SuSE (TrueSight IS): Run these commands to install required OS libraries prior to installing TSIM.

The 'umask' command should return 022

You must have write permissions in the /etc, /opt, and /tmp directories.

1Gb of free space is required in /tmp (in addition to 3Gb free in swap overall), with read and write permissions to /tmp.

The directory where TrueSight is installed and all its parent directories must have 755 permissions and must be owned by root, as well as the other group. Without these permissions and ownership, you will not be able to log into TrueSight.

Disable X Windows access control by using the xhost command.

Ensure that the nobody user account and the nobody group exist on the target computer.

The installation directory name cannot contain spaces

Ensure that you have root permissions for the computer on which you want to install TrueSight.
If desired, it is possible to install TrueSight Infrastructure Management Server to run as a non-root user. Go here for non-root details

Ensure that you install the csh and tcsh shells.

BMC highly recommends that you use MobaXterm as the UI to install TrueSight on Linux systems. Other X emulators, such as eXceed, may not allow the GUI to launch, while allowing other X utilities to do so.

Click here for more hardware details.
Click here for OS details.
Click here for Small/Medium/Large definitions.
Click here for preinstallation checks.

 TrueSight Integration Service

TrueSight IS hardware & OS requirements
  •Red Hat Enterprise Linux 6.7, 6.8, 7.0, 7.1, 7.2, 7.3 (64 bit)
  •SUSE Linux 11 SP2, 11 SP3, 12
  •Oracle Linux Server 6.8, 7.3
  •RAM for Small/Medium/Large configurations: 4Gb/8Gb/8Gb

Red Hat (TSPS, TSIM, ISN): Run the following commands to install required OS libraries:
yum install libXtst.i686 libXtst.x86_64 libXtst-1.0.1-3.1 libX11-devel-1.0.3-11.el5
yum install glibc.i686 glibc.x86_64 glibc-2.12.x86_64 glibc-2.12-1.107.el6.i686 glibc-devel-2.5-65
yum install libstdc++.i686 libstdc++.x86_64 
yum install compat-libstdc++-33.i686 compat-libstdc++-33.x86_64 compat-libstdc++-33-3.2.3-69.e16.i686
yum install compat-libstdc++-296.i686 compat-libstdc++-296.x86_64
yum install pam.i686 pam.x86_64 pam-1.1.1-13.e16.i686
yum install libgtk-x11-2.0.so.0
yum install libfreebl3.so

The 'yum install' commands require a Red Hat subscription. Register the system by clicking System >Administration > Red Hat Subscription Manager in the menu on the server itself.
Note: The above commands will install both 32 bit and 64 bit libraries on the 64 bit system, which is intentional.
If an error occurs while installing a 32 bit library, try re-running the 'yum install' command with both 32-bit and 64-bit versions. For example:
yum install pam.i686 pam.x86_64
If the "No package <package name> name available" message is seen, run the command again without specifying the version. For example:
"No package libX11-devel-1.0.3-11.el5 available."
"Error: Nothing to do"
# yum install libX11-devel

SuSE (TrueSight IS): Run these commands to install required OS libraries prior to installing TrueSight IS.

Clean your temporary directories (e.g. /tmp and /var/tmp). You may not be able to delete all the files, but BMC recommends that you remove any files or directories that match "*ProactiveNet*" and "TrueSight*".

The 'umask' command should return 022

It is possible to install the Integration Service as non-root. Go here for non-root details

 VMware environment planning

Consider the following VMware best practices:
  •To prevent performance problems when deploying on VMware, ensure that you enable the Unlimited memory setting for the VM.
  •CPU and memory resources should be dedicated to the VM on which TrueSight or any of its components are running. You must also ensure that you do not use the shared option.
  •The Integration Service node(s) should be excluded from VMware HA if you are using the out-of-the-box active/active configuration, because PATROL Agents will automatically switch to their secondary location if the primary location is interrupted for any period of time
  •You must use the Thick Provision Eager Zeroed disk type for the Infrastructure Management server. The Thick Provision Eager Zeroed disk provides the advantages of clustering features such as fault tolerance.
  •Use only two to three virtual machine snapshots in a chain. BMC recommends that you avoid using the single snapshot for more than 72 hours. You can either delete the snapshot or consolidate it. For more information, see http://kb.vmware.com/kb/1009402 
  •Enable NIC teaming.
  •Use a VMware paravirtual NIC adapter for optimized performance
  •For ESX storage, ensure that you use dedicated disk storage all virtual machines; avoid sharing disk storage.
  •Configure Jumbo frames for the storage adapter.
  •Reserve the resources that are allocated for the virtual machine on which the BMC applications are installed.
Click here for more details on the above points

The hardware requirements are the same for physical or virtual machines.

 Information for all operating systems

If deciding between the pre-packaged Sybase DB or the customer-provided Oracle DB go here.

If using Oracle for TrueSight's database:
  •Use Oracle versions 11.2.0.2.0, 11.2.0.3.0, 11.2.0.4, 12.1.0.1.0, 12.1.0.2.0 (Standard and Enterprise)
  •Make sure that Oracle has been installed on a separate box than the TrueSight Infrastructure Management server
  •Ensure that you dedicate one Oracle database instance exclusively only to BMC TrueSight Infrastructure Management Servers.
  •You can install multiple BMC TrueSight Infrastructure Manager servers and configure them to run on a single instance of the Oracle database. Click here for details.
  •Create an instance with the proper character sets
  -Database Character Set—AL32UTF8
  -NLS_LENGTH_SEMANTICS—BYTE
  -National Character Set—AL16UTF16
 
  •If NLS_LENGTH_SEMANTICS has been set to BYTE, as recommended by BMC, also set the DB_BLOCK_SIZE value to 8192. If you set the NLS_LENGTH_SEMANTICS value to CHAR, ensure that you set the DB_BLOCK_SIZE value to 16384
  •Set the Oracle database instance on the Oracle server to run in ARCHIVELOG mode.
  •Create at least two sets of redo log files with a minimum of 500 MB each on the Oracle database instance. 
  - Click here for details.
  •Ensure that you set the Oracle database system parameters before running the TrueSight application server installer. For information about setting Oracle database system parameters click here.

BMC TrueSight has been tested on localized operating system platforms in these languages:
  •English
  •Simplified Chinese
  •German
  •Japanese
  •Korean
  •French
For more detail on the above points, go here

For Chinese, Korean, and Japanese installations, ensure that the system default locale is a UTF-8 locale. This enables the Input Method feature in the BMC TrueSight Administration Console.

For a list of third party integrations & their versions, go here

For a list of BMC Software integrations & their versions, go here

Deploy the Integration Service strategically so that the connections from Patrol Agents to the Integration Service do not span network boundaries or firewalls.

Pagefile/swap space minimum is 3 GB (4 GB is recommended).

Free disk space on system root should be 4GB or greater.

Disable any anti-virus software on each host computer on which you are installing a component, or exclude the BMC TrueSight installation directory from virus scanning. Virus scanners can block the SMTP port and lock files that the installation program needs to configure the mail server and perform the installation. You can enable the virus scanning programs after the installation is completed.

TrueSight automatically configures Windows firewall from installer, but third party firewalls need manual intervention. Disable third party firewall protection programs, such as McAfee Host Intrusion Prevention Service (HIPS). HIPS can block access to ports that are used by the installation program during installation and by TrueSight at run time. You must leave HIPS disabled after the installation is completed. You must reboot the computer after you disable the service.

Ensure that the host name or cluster name does not contain an underscore (_).

Java must not be installed on the target computer where TrueSight Infrastructure Management is being installed.

The BMC TrueSight Infrastructure Management Server 10.7 can simultaneously interoperate with Integration Service versions 10.7, 10.5, 10.0.500, 10.0, 9.6, and 9.5
A server can host both earlier and the new Integration Service processes if you set the ports so that they do not conflict and you provide proper resources (CPU, memory, disk, and so on).

The supported Integration Service versions can only communicate with PATROL Agent versions 9.5.00 or later.

For more details on Interoperability, go here.

If setting up a Disaster Recovery environment, go here.

If setting up a multiple TrueSight Infrastructure Management server environment (Central and Child servers), go here.

 Upgrade-specific information

If possible, consider installing a new installation of TrueSight rather than upgrading from a previous version. This minimizes monitoring downtime and allows for a easier and less stressful experience. Go here for details.

For known and corrected issues, click here.

To determine whether you can upgrade an earlier version to the desired version directly (or if you have to plan for an incremental upgrade from the earlier versions), get your current version information:

Run "pw viewhistory" on the TSIM/BPPM server to determine the current version

Run "pw remote list" on the TSIM/BPPM server to determine the build numbers of the ISNs.

You can directly upgrade to TSIM 10.7 from TSIM 10.0.500, or 10.5 (regardless of any Fix Packs/patches)
You can upgrade to TSIM 10.7 from previous versions after upgrading to an intermediate stage. Go here for details.

On Solaris and Linux, you cannot migrate BEM and IM to TSIM 10.7. You have to uninstall BMC Event and Impact Management prior to installing TSIM 10.7.
On Windows, you can migrate from BMC Event and Impact Management 7.1, 7.2, 7.3.xx, or 7.4 to TSIM 10.7, click here for the steps.

Backup your TSIM database prior to upgrading. For details, go here
Or, better yet, backup the entire installation: Stop TrueSight processes "pw system stop", then backup (zip/tar) the entire TrueSight directory. Note that if you are using Oracle as your TSIM database, this will need to be backed up separately.

If your current version of ProactiveNet is 9.0 and below, run the StaleCleaner utility. If you don't have a copy, download it here.

Review .\pw\pronto\logs\pruner.log and proactivenetpruner.log (if exists) for errors (e.g. search for "fail" and "error").

If upgrading from ProactiveNet, truncate the table ITEMCFG_DTLSLOG to speed up the upgrade:
  •Bring up database: 'pw process start dbsrv'
  •Confirm table size: 'runjava scripts.runsqli “select count(*) from ITEMCFG_DTLSLOG”'
  •Truncate the table: 'runjava scripts.runsqli “truncate table ITEMCFG_DTLSLOG”'
  •Confirm new size (should be 0): 'runjava scripts.runsqli “select count(*) from ITEMCFG_DTLSLOG”'
  •Bring down the database: 'pw process end dbsrv'

Ensure that you have merged any customized KBs. Go here for details.

Close all the BMC related application windows that are opened before launching the upgrade.
Note: During the upgrade to TSIM 10.7, you will receive a system reboot prompt if any of the existing BMC files were locked. You must set all the BMC services to manual mode (or disable any rc scripts, if the issue is seen in Linux), restart the server, and launch the upgrade process again. An alternative for Windows is to download Process Explorer (https://technet.microsoft.com/en-us/sysinternals/bb896653), run it, then:
Find -> Find Handle or DLL -> enter the path for TrueSight (e.g. C:\Program Files\BMC Software\TrueSight) -> Search
Kill whatever processes are returned. Complete the installation. 

You must disable any Pn* Scheduled Tasks (or /usr/pw/pronto/bin cron jobs) and any custom schedulers that access BMC installation files before starting the upgrade process. After completing the upgrade process, you can enable them again.

Disconnect all the Integration Services that are connected to the Infrastructure Management server from the Configuration > Managed Devices page in the TrueSight console.

Ensure that there are no Integration Services installed on the computer where the TrueSight Infrastructure Management Server will be installed.

Upgrade the TrueSight Infrastructure Manager before upgrading the TrueSight Integration Services.

To upgrade TSIM on Linux, reserve at least 4 GB of space in the /tmp directory.
Note that a TSIM upgrade requires 4 GB of space whereas an initial installation of TSIM only needs 1 Gb of space in /tmp.

Before upgrading the TSIM or TSPS with a non-root user, delete the Utilities directory from the /var/tmp directory.

If an installation of BMC Atrium Single Sign-On already exists on the target computer, the installer will not allow another installation. Uninstall the existing version.

 Installation
 Installing TrueSight Operations Management on Windows

Prior to installing/upgrading in a production environment, BMC recommends performing that in a test/dev/QA environment.

 Atrium SSO

Extract the Atrium SSO file
Go to BMCAtriumSSO\Disk1
Double click on setup.exe

Click here for the steps.

Most customers will select the following options:
Install BMC Atrium Single Sign-On 9.0.00.01 or 02
Non-clustered
Install New Tomcat
Cookie domain: yourcompanydomainname.com (e.g. bmc.com)

The amadmin user is the default administrator user for BMC Atrium Single Sign-on. You can use the amadmin user only for accessing the BMC Atrium SSO Admin Console. You cannot log on to your authenticating BMC applications by using the amadmin user.

Click here for configuration steps.

To verify the installation:
The URL to open the BMC Atrium SSO Admin Console is:
https://<ssoserver>.<domain>:<port>/atriumsso
For example: https://ssoserver.bmc.com:8443/atriumsso

Note: If you are using FireFox and see "SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange", then you can disable Diffie-Hellman cypher keys here:
https://addons.mozilla.org/en-us/firefox/addon/disable-dhe/ 
When you are prompted that you are connecting to an insecure or untrusted connection, add the exception and then continue.

Log on with the SSO administrator name (for example, amadmin) and password.

 TrueSight Presentation Server

Extract the TrueSight Presentation Server file

As an account with Administrative privileges, go to Disk1
Double click setup.exe

The path for the installation directory cannot exceed 125 characters
Ensure that the directory is empty

If the Presentation Server cannot connect to Atrium SSO during the installation, an error will be thrown. Make sure that the hostname can be resolved.

To verify the installation:
Navigate to the TrueSightPServer\truesightpserver\bin directory and enter the following command:
tssh server status
A list of Presentation Server processes is displayed that is similar to the following sample:
Process status
================================
Core Server Running (13176)
Index Server Running (11028)
Database Server Running (6052)

If errors occur, restart the Presentation Server by running the following command:
tssh server start
Note that when logging into the TrueSight Presentation Server website as the admin user, use the password admin12345

Click here for the steps.

 TrueSight Infrastructure Manager

Extract the TrueSight Infrastructure Manager file on a dedicated box

Login as a direct member of the Administrators group.

Extract the TrueSight Infrastructure Manager file on a dedicated box
Go to .\Windows\TSIMServer\Disk1
It is recommended to start the installation via command line with the Run as administrator option as follows:
install.cmd -J PERFORM_SERVER_PARAMETER_TUNING=true

The PERFORM_SERVER_PARAMETER_TUNING allows the MaxHeap values to be set according to the hardware resources on the server.

If you don't want MaxHeap to be set for you, then just double-click install.cmd

Do not install TrueSight in a root directory (for example C: or D: ), on a shared drive, or in the Documents and Settings folder.
While installing TrueSight on a 64-bit Windows computer, ensure that you do not install it in the Program Files (x86) directory path.

After the installation, an error specifying "addDeviceOrMonitor.bat" may be seen. BMC is investigating this via CRE-1548 tracked here.
Manually run the command after the installation. The failed command is printed in the installation log file. You can copy the command from the log file and run it from a command prompt.

Click here for the steps and screenshots during the installation wizard

If using an Oracle database for TrueSight, click here for details.

Steps to perform a silent/unattended installation are available here.

To verify the installation, run the following commands to verify that all processes are running:
pw system status

A list of pw server processes is displayed.
Review the output for errors.
  •Processes that are not running properly are denoted by a numbered error message, such as 961 > max 1. 
  •Processes that are not running at all are denoted by !Not Running!.

If errors occur, restart TrueSight Infrastructure Manager by running the following command:
pw system start

During installation, the installation log files are saved in the following locations:
tsim_server_install_log.txt and TrueSight_server_install.log can be located in the %temp% folder. After installation, the log files are copied to the installationDirectory\pw\pronto\logs folder.

Details about the installation log are here here.

 Installing TrueSight Integration Service

To download the Integration Service software:
  1. Log on to TrueSight Presentation Server.
  2. Click on the Action menu (4 white stacked lines in the upper left corner)
  3. Configuration -> Managed Devices -> Click the 3 dots next to your TSIM -> Download Integration Service/Administrator Console
  4. Select the file for a specified operating system, and save the file to the computer on which you want to install the Integration Service.
  or
  Go to the TSIM server & find it at: C:\Program Files\BMC Software\TrueSight\pw\pronto\web\html\download

If you want to install both cell and Integration Service on the same computer on which you have installed only the cell, then you should provide a different location for installing Cell and Integration Service. If you provide the same location where you installed the Cell (C:\ProgramFiles\BMC Software\TrueSightAgent), then the Cell entries are removed from the system.

To install multiple Integration Services on a single computer click here.

Save the TSIMAgent.zip file on your drive and extract its contents. Open the install.cmd file with the Run as administrator option.

After the Integration Service has been installed, do not install an earlier version of the Integration Service on the same computer.

To determine the ISN version, open .\pronto\bin\AGENT_VERSION

For information showing Patrol Agent version compatibility with the Integration Service, click here.

If you need more help with the IS upgrade/install, click here.

Steps to perform a silent/unattended installation are available here.

 Installing TrueSight Operations Management on Linux

Prior to installing/upgrading in a production environment, BMC recommends testing the same in a test/dev/QA environment

 Atrium SSO

Extract the Atrium SSO file
You can be any user. However, root privileges are required to set up auto-startup of the services.
At the command prompt, run the following commands:
DISPLAY=targetHostName:0.0
export DISPLAY
xhost
cd BMCAtriumSSO
chmod -R 755 Disk1
cd Disk1
./setup.sh

Click here for the steps.

Most customers will select the following options:
Install BMC Atrium Single Sign-On 9.0.00.01 or 02
Non-clustered
Install New Tomcat
Cookie domain: yourcompanydomainname.com (e.g. bmc.com)

The amadmin user is the default administrator user for BMC Atrium Single Sign-on. You can use the amadmin user only for accessing the BMC Atrium SSO Admin Console. You cannot log on to your authenticating BMC applications by using the amadmin user.

Click here for configuration steps.

To verify the installation:
The URL to open the BMC Atrium SSO Admin Console is:
https://<ssoserver>.<domain>:<port>/atriumsso
For example: https://ssoserver.bmc.com:8443/atriumsso

Note: If you are using FireFox and see "SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange", then you can disable Diffie-Hellman cypher keys here:
https://addons.mozilla.org/en-us/firefox/addon/disable-dhe/ When you are prompted that you are connecting to an insecure or untrusted connection, add the exception and then continue.

Log on with the SSO administrator name (for example, amadmin) and password.

 TrueSight Presentation Server

Extract the TrueSight Presentation Server file

Log on as a root user. (This is done to set permissions & ownership, not to install)
chmod -R 755 <installationDirectoryFolderName>
chown -R <nonrootuser> <installationDirectoryFolderName>
  <installationDirectoryFolderName> is the name of the directory that contains all the installation files
  <nonrootuser>; is the name of the non-root user which will perform the TSPS installation
  For example:
  chmod -R 755 /data1/TSPS/Linux/Disk1
  chown -R sboulette /data1/TSPS/Linux/Disk1

Make sure that <nonrootuser> can write to:
/opt/bmc
/tmp
/etc

Login as a non-root user (root cannot install Presentation Server)
At the command prompt, run the following commands:
DISPLAY=targetHostName:0.0
export DISPLAY
xhost
cd ./Linux/Disk1
./setup.bin

The path for the installation directory cannot exceed 125 characters
Ensure that the directory is empty
BMC recommends installing to the default installation directory of /opt/bmc/TrueSightPServer

If the Presentation Server cannot connect to Atrium SSO during the installation, an error will be thrown. Make sure that the hostname can be resolved.

To verify the installation:
Navigate to the ./TrueSightPServer/truesightpserver/bin directory and enter the following command:
./tssh server status
A list of Presentation Server processes is displayed that is similar to the following sample:
Process status
================================
Core Server Running (13176)
Index Server Running (11028)
Database Server Running (6052)
If errors occur, restart the Presentation Server by running the following command:
./tssh server start
Note that when logging into the TrueSight Presentation Server website as the admin user, use the password admin12345

Click here for details & post installation steps.

 TrueSight Infrastructure Manager

Extract the TrueSight Infrastructure Manager file on a dedicated box

chmod -R 755 Disk1
cd Disk1
It is recommended to start the installation as follows:
./install.sh -J PERFORM_SERVER_PARAMETER_TUNING=true

The PERFORM_SERVER_PARAMETER_TUNING allows the MaxHeap values to be set according to the hardware resources on the server.

If you don't want MaxHeap to be set for you, then just run:

./install.sh

Click here for the steps and screenshots during the installation wizard

Do not install TrueSight in /usr or in a root directory.

If using an Oracle database for TrueSight, click here for details.

To verify the installation, run the following commands to verify that all processes are running:
. /opt/bmc/TrueSight/pw/pronto/bin/.tmprofile
pw system status

A list of pw server processes is displayed.
Review the output for errors.
  •Processes that are not running properly are denoted by a numbered error message, such as 961 > max 1. 
  •Processes that are not running at all are denoted by !Not Running!.

If errors occur, restart TrueSight Infrastructure Manager by running the following command:
pw system start

During installation, the installation log files are saved in the following locations:
tsim_server_install_log.txt and tsim_server_install.log are saved in the /tmp or the /var/tmp folder depending on the operating system's temp directory settings.
After installation, the log files are copied to the installationDirectory/pw/pronto/logs folder.

Details about the installation log are here.

Steps to perform a silent/unattended installation are available here.

 Installing TrueSight Integration Service

To download the Integration Service software:
  1. Log on to TrueSight Presentation Server.
  2. Click on the Action menu (4 white stacked lines in the upper left corner)
  3. Configuration -> Managed Devices -> Click the 3 dots next to your TSIM -> Download Integration Service/Administrator Console
  4. Select the file for a specified operating system, and save the file to the computer on which you want to install the Integration Service.
  or
  Go to the TSIM server & find it at: /opt/bmc/TrueSight/pw/pronto/web/html/download

If you want to install both the cell and Integration Service on the same computer on which you have installed only the TrueSight cell, then you should provide a different location for installing the cell and the Integration Service. If you provide the same location where you installed the cell, then the cell entries are removed from the system.

BMC recommends running the ISN installation as root:
DISPLAY=targetHostName:0.0
export DISPLAY
chmod -R 755 installationDirectoryName
./install.sh

To install as a non-root user, perform the following steps:
  1. Log on as a root user.
  2. Use the useradd command to create a user account. Assign a password to this user account.
  3. Open the /etc/sudoers file.
  4. At the end of the file, add the line <NON_ROOT_USER> ALL=(ALL) PASSWD:ALL, where <NON_ROOT_USER> is the user account you created.
  5. Save the file and exit from root.
  6. Log on to the computer using the non-root user account you created.
  7. Enter:
DISPLAY=targetHostName:0.0
export DISPLAY
  8. Save the TSIMAgent.zip file on your drive and extract its contents.
  9. Run 'sudo install.sh'. Enter the non-root account password when prompted.

To install multiple Integration Services on a single computer click here.

After the TrueSight Integration Service has been installed, do not install an earlier version of the Integration Service on the same computer.

To verify the installation:
Navigate to the installation directory (e.g. ./pw/pronto/bin/) and run the 'pw agent status' command. Verify that the pronet_agent process is listed.
If the pronet_agent process is not listed, run the 'pw agent start' command.

For information showing Patrol Agent version compatibility with the Integration Service, click here.

If you need more help with the IS upgrade/install, click here.

Additional details are here.

Steps to perform a silent/unattended installation are available here.

If you have questions which aren't covered in the checklist, please open a case with BMC Customer Support and provide:
  - "AMIGO Starter" in the Subject line
  - Your questions
  - Essential background information, such as your current version, intended version, OS, etc.

BMC Customer Support will also review your plan when you've finished it.  For this, open a new case and provide:
   - "AMIGO Review" in the Subject line
   - Your plan
   - The expected date & time of the installation/upgrade

Was this page helpful? Yes No Submitting... Thank you
© Copyright 2013-2017 BMC Software, Inc.
© Copyright 2013-2017 BladeLogic, Inc.
Legal notices