×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.
BMC Cloud Lifecycle Management 3.1 ... Planning System requirements

Permissions required for Linux installations

This topic provides a comprehensive list of the permissions required to install the Linux products in BMC Cloud Lifecycle Management. It provides useful links to other help topics that describe how to perform a specific task, for example, configuring a trust relationship. 

These permissions apply to BMC Cloud Lifecycle Management installer host and all target hosts.

The following information is provided:

Installer host permissions

You need root user credentials to the target host servers only to perform the RSCD Agent installation.

Target host permissions

BMC recommends that you install the BMC Cloud Lifecycle Management product as a root user. If you install as a non-root user, you can encounter potential problems with upgrades, for example, re-applying post-installation modifications to individual products so that they can run as the required user. For more information on non-root installations of the AR System server, see Preparing the UNIX environment (in the BMC Remedy documentation portal).

The following target host permissions are required when installing specific products:

ProductPermissions required
All productsMake sure that you have root access to all target hosts.
NSH and RSCD Agent

Domain credentials (even though they have admin permissions) are not supported during the RSCD installation using the BMC Cloud Lifecycle Management installer.

Oracle database requirements
  • You must have database administrator (DBA) credentials to create the tablespace and users for the pre-created database and installer-created database option.
  • You must give read and execute permission to the database client directory for the user (for example, root) with which AR Server installation is going to be performed. Specifically, you must give permissions to database client directory and all its subdirectory and files. 
  • The DBA group is used with installations that has permissions to the file systems containing Oracle clients and libraries. In effect, you are giving permissions to file systems, not to database. These permissions are valid on for the client machine and not for the database server. DBA permissions are not the same as the DBA role. What is needed during installation are DBA permissions, not the DBA role.
  • To use the pre-created tablespace option, you must have required system user and password credentials.
  • BMC Remedy AR System & IT Service Management Suite – Primary (Enterprise AR)
  • BMC Remedy AR System and BMC Remedy IT Service Management Suite – Secondary (Optional)
When installing the application on UNIX, BMC recommends performing the installation as a root user. However, you can perform the installation as a non-root user. If you choose to install the application as a non-root user, you must log on to the UNIX system under the same UNIX user ID that was used to install BMC Remedy AR System.
  • BMC Remedy AR System – Cloud Database Primary
  • BMC Remedy AR System – Cloud Database Secondary (Optional)
When installing the application on UNIX, BMC recommends performing the installation as a root user. However, you can perform the installation as a non-root user. If you choose to install the application as a non-root user, you must log on to the UNIX system under the same UNIX user ID that was used to install BMC Remedy AR System.
BMC Remedy Mid TierCan be installed as non-root user.
BMC Atrium Core Web Registry Components

Can be installed as non-root user.

BMC Server Automation – File Server (Optional)Install as root.
BMC Server Automation – Application Server and ConsoleInstall as root.
BMC Server Automation – Application Server (MAS)Install as root.
  • BMC Atrium Orchestrator Server
  • BMC Atrium Orchestrator – Configuration Distribution Peer (HA) (Optional)
 
BMC Network AutomationYou must create a user account (for example, bcan) when installing the BMC Network Automation product. This account is referred to as the BCAN_USER account. The user account cannot be an administrator account and must have privileges to log on locally.
BMC Atrium Core Web Registry 
  • BMC ProactiveNet Central Server (Optional)
  • BMC ProactiveNet Server (Optional)
  • BMC ProactiveNet Data Collection Host (Optional)

Install as root.

Ensure that you can log on to the BMC Server Automation application server and that you can access the BMC Server Automation web services.

Cloud Database Extensions 
Cloud Platform Manager 
  • Cloud Portal AR Extensions – Primary
  • Cloud Portal AR Extensions – Secondary (Optional)
 
PXE Server 
BMC Server Automation – Advanced Repeater (Optional) 
BMC Network Automation – Device Agent (Optional) 

Where to go from here

End-to-end installation flow

Related topics

Linux installer host requirements

Was this page helpful? Yes No Submitting... Thank you
Last modified by John Stamps on Aug 22, 2014

Comments

Log in or register to comment.

Permissions required for Windows installations
Supported browsers
© Copyright 2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.