Date: Tue, 19 Mar 2024 02:57:08 -0500 (CDT) Message-ID: <2018296568.63164.1710835028416@bmc1-rhel-confprod1.managed.contegix.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_63163_1913076532.1710835028415" ------=_Part_63163_1913076532.1710835028415 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The core of the three-tier architecture in BMC Server Automation= is the Application Server. Controlling communication between clients and s= ervers as well as access to database, file, and mail servers, the Applicati= on Server can be adjusted to scale a system and to fine tune its performanc= e.
Note
The Application Server and the RCP client (BMC Server Automation Console= ) must be located on the same Local Area Network (LAN). Remote users can us= e the console through either remote desktop protocol (RDP) or Citrix from a= remote machine to the machine where the console resides.
There are two general configurations for Application Servers in the BMC = Server Automation environment:
The following topics provide instructions for configuring the Applicatio= n Server:
Warning
Any directory or file that has the same name as an Application Server in= stance could interfere with launching Application Servers. Avoid creating a= ny files or directories in the /opt/bmc/bladelogic/NSH/br/= directory with the same name as an Application Server instance. For exampl= e, creating a file with the name "default" in the /opt/bmc/bladelog= ic/NSH/br/ directory will cause problems launching the Application= Server and blocks the Application Server from starting the required servic= es. As a general rule, avoid placing any files in the directories that the = Application Server uses for its own storage, such as the /opt/bmc/b= ladelogic/NSH/br/ directory.