Page tree
Skip to end of metadata
Go to start of metadata

Before installing the the Presentation Server, ensure that your environment is ready for the installation of the Presentation Server by reviewing and completing the following tasks.


Preinstallation tasks for the Presentation Server

  • Atrium Single Sign-On must be installed and configured. The TrueSight Presentation Server will not operate without Atrium Single Sign-On.
    • Atrium Single Sign-On can be installed on the same computer as the Presentation Server. Review scalability information for the TrueSight Presentation Server and Atrium Single Sign-On.
    • When configuring Atrium Single Sign-On for high availability, you must complete the high-availability configuration tasks before installing the TrueSight Presentation Server.
    • Atrium Single Sign-On does not have to be installed as a standalone instance to work with the Presentation Server. A single Atrium Single Sign-On can support one or more Presentation Servers. You can also use the existing Single Sign-On that is integrated with other BMC products while installing the Presentation Server.
  • Confirm that the target computer meets the system requirements for the TrueSight Presentation Server.
  • Ensure that the user who is installing the TrueSight Presentation Server has the following privileges:
    • (Windows) Administrator privileges.

    • (Linux) A non-root user with modification permissions to the following directories and files. A user with root privileges cannot install the Presentation Server.

      PermissionFile or Directory
      Execution/Linux/Disk1/setup.bin
      Read/Write and Execution
      • Presentation Server installation directory
      • /tmp directories.
      Mount with exec option

      Verify the filesystem that the /tmp directory resides in is mounted with exec option by running the findmnt command. If it shows noexec for /tmp, remount it with exec option. For example, mount -o remount,exec /tmp.

      Read/Write and Execution/opt/bmc
      The ProductRegistry.xml file is created in the /opt/bmc directory. Therefore, the /opt/bmc directory requires read/write and execution permissions. If the bmc directory does not exist, create the bmc directory with read/write execute permission.
  • Complete or review the installation planning worksheets.
  • Review known and corrected issues.
  • If you are installing the Presentation Server on the same computer where an earlier installation existed, make sure that you completely uninstall the earlier installation. Make sure that any installed security software does not hamper the deletion of any *.war files.
  • Ensure that you delete all files from the temporary directory. 
    • (Windows%temp%
    • (Linux/tmp 
  • If you are installing the Presentation Server on an IPv6 Windows host, ensure that the IP helper service is started.
  • Ensure that the system default locale is a UTF-8 locale.
  • If you are installing the Presentation Server with the Atrium Single Sign-On custom certificate, ensure that java is installed and the java -version command should return the version as java 1.6 and later. 

Preinstallation resources

System requirements for Presentation Server 

Atrium Single Sign-On 9.0 installation

Sizing considerations for the Presentation Server

Planning worksheets for Operations Management

Known and corrected issues

Uninstalling the Presentation Server

Load balancer requirements and guidelines for Atrium Single Sign-On high availability 1

Adding and restoring permissions for silent installation with a non-root user

If you are silently installing the Presentation Server as a non-root user on Linux, you must add some permissions for the non-root user. After the installation is successful, you can restore the original permissions for the non-root user.

Note

The path of some directories might be different for different versions on Linux.

To add permissions:

  1. Create the installation directory and change the owner to the default account.
  2. Log in as a root user, and use the following command to change the owner to the non-root user:
    chown -R <nonRootUser>:<non-RootGroup> /opt/bmc/TrueSight
  3. Run the following commands:

    setfacl -m u: <nonRootUser>:rwx /usr 

    setfacl -m u: <nonRootUser>:rwx /usr/bin 

    setfacl -m u: <nonRootUser>:rwx /etc 

    setfacl -m u:<nonRootUser>:rwx /opt/bmc 

    setfacl -m u:<nonRootUser>:rwx /etc/rc.d/init.d 

    setfacl -m u:<nonRootUser>:rwx /etc/rc.d/rc0.d 

    setfacl -m u:<nonRootUser>:rwx /etc/rc.d/rc1.d 

    setfacl -m u:<nonRootUser>:rwx /etc/rc.d/rc3.d 

    setfacl -m u:<nonRootUser>:rwx /etc/rc.d/rc5.d 

    setfacl -m u:<nonRootUser>:rwx /etc/profile 

    setfacl -m u:<nonRootUser>:rwx /etc/csh.cshrc

    /tmp

    No Change

    /var/tmp

    No Change

To restore permissions:

  1. Create the installation directory and change the owner to the default account.
  2. Log in as a root user, and use the following command to change the owner to the non-root user:
    chown -R <nonRootUser>:<non-RootGroup> /opt/bmc/TrueSight
  3. Run the following commands:

    setfacl -x u:<nonRootUser>:rwx /usr

    setfacl -x u:<nonRootUser>:rwx /usr/bin 

    setfacl -x u:<nonRootUser>:rwx /etc 

    setfacl -x u:<nonRootUser>:rwx /opt/bmc 

    setfacl -x u:<nonRootUser>:rwx /etc/rc.d/init.d 

    setfacl -x u:<nonRootUser>:rwx /etc/rc.d/rc0.d 

    setfacl -x u:<nonRootUser>:rwx /etc/rc.d/rc1.d 

    setfacl -x u:<nonRootUser>:rwx /etc/rc.d/rc3.d 

    setfacl -x u:<nonRootUser>:rwx /etc/rc.d/rc5.d 

    setfacl -x u:<nonRootUser>:rwx /etc/profile 

    setfacl -x u:<nonRootUser>:rwx /etc/csh.cshrc


To configure the required Terminal Server options

On a Windows operating system, to run the installation utility through a Terminal Services connection or a remote desktop session, configure the Terminal Server options that pertain to temporary folders.

  1. On the host computer, open the Local Group Policy Editor by selecting Start > Run and typing gpedit.msc.
  2. Expand the following folder: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folders.
  3. Double-click the following options to set each to Enabled:
    • Do not delete temp folder upon exit
    • Do not use temporary folders per session
  4. Restart the computer.

Troubleshooting tip

If you receive a notification about Terminal Server configuration when you run the installation, perform the following steps to back up the registry and adjust the registry key values as follows:

  1. On the host computer, open the Registry Editor by selecting Start > Run and typing regedit.
  2. Expand the following folder: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
  3. Set the value for PerSessionTempDir and DeleteTempDirsOnExit to 0.
  4. Restart the computer.

Note

You can revert these changes after you complete the installation process. You might need to restart the computer.

Where to go from here

Select one of the following installation methods:


 

 

 

2 Comments

  1. Andreas Heitz

    Hello Andreas,

    We received a comment from you on this page that is unfortunately not visible right now. Here are the details about the comment:

    Comment added on the following extract:

    The ProductRegistry.xml file is created in the /opt/bmc directory. Therefore, the /opt/bmc directory requires read/write and execution permissions. If the bmc directory does not exist, create the bmc directory with read/write execute permission.

    Comment:
    Hello, i still can not see that the /etc on Linux has to be writable for the Installation user on this page....

    The ProductRegistry.xml file is created in the /opt/bmc directory. It is not created in the /etc directory. Therefore, we have not mentioned a write permission to the /etc directory.

    Does this help? Do let us know if you need more information.

    Thanks and regards,
    Mukta

    1. Hello Mutka,

      please have a look at this page of the Documentation:

      Performing the Presentation Server installation

      There is written that the /etc has to be writeable too.That is confusing (sad)


      And there is an other question:

      Please define a little bit clearer what in the /etc has to be writable for the installation user. Make /etc world writable can result in high security risks. Please accept that customers have sometimes high security restrictions. 


      Greetings


      Andreas