BMC BladeLogic Server Automation Best Practices for Deployment and Configuration

BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration

REVISION HISTORY
Date March, 2011 Product version 8.1.00 Revisions Initial version.

Page 2

.................................................................................................................................................................. 7 Deploy Jobs ....................................................................................................................................................... 26 Appendix: TCP/UDP Port Usage..................................................................................... 22 Recommendations for Configuration servers ......................................................................................................................................................................................... 21 Recommendations for job servers .....................................................................................................................................................................................................................BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration TABLE OF CONTENTS Revision history ....................................................................................................................................................... 16 Large-Scale installations ............................................................................................................................................................................. 17 Geographically-distributed installations ............................................................................ 20 About Java memory ...... 6 NSH Script Jobs ........................................................................................................................................................................ 20 About thread pools.................................. 19 Configuration guidance .................... 21 About database connections ....................................................................................................................................... 27 Page 3 ....................................................................................................................................... 2 Understanding job behavior ..................................................................................................................................................................... 9 Virtualization Jobs........................................................................................................ 9 Patching Jobs ......................................................................................................................................................................................................................... 5 Component Discovery Jobs ............................................................................................................................................... 13 Simple installations ..................................................................................................................... 13 BMC BladeLogic Server Automation components ...................... 4 Compliance ........................................................................................ 4 Job execution framework ......................................................................................... 24 Recommendations for NSH Proxy servers . 11 Administrative jobs........................................................................................................................................................................................................... 7 Provision Jobs .............................................................. 12 Deployment guidance .................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Lightweight work items Some work items are designated as lightweight work items because their execution consumes significantly fewer server resources than does the execution of normal work items.0. Asynchronous BlExec tasks While a work item is executing. has a non-zero size). It is in the execution of work items that the job carries out its responsibilities. work items whose implementation is not asynchronous task aware still perform remote operations directly and cause their work item threads to wait for the operation to complete. corresponding to different steps or stages of the job. and some are not. A pool of threads.000 target hosts can create and schedule execution of possibly several thousand work items. Thus. all work items (lightweight and nonlightweight) are managed by the normal work item thread pool. which maintains yet another thread pool. some BMC BladeLogic Server Automation jobs are asynchronous task aware. on a target host. Asynchronous tasks are a relatively new feature of the job execution framework. Work items scheduled for execution are maintained in a work item queue in the job server. If the lightweight work item thread pool is not empty (that is. This section describes the overall operation of the framework. with emphasis on computation. A work item thread assigned to such a work item blocks while it waits. Work items are separately-schedulable units of work that are undertaken as part of the execution of a job. an asynchronous BlExec task does not consume any thread resources. Further. In addition to the work item thread pool. for example.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration UNDERSTANDING JOB BEHAVIOR This section provides a brief overview of the runtime behavior of the various job types. This can present a potential resource issue. each job server also maintains a separate thread pool for lightweight work items. A work item is almost always bound to one target host. targets. called the job thread pool. Jobs. While it waits for a response from the remote target. spend much of their time waiting for results from operations being carried out remotely. instead of performing that remote operation and waiting for a response. a work item thread is assigned exclusively to that work item. as the work item thread is not available to service other work items with more active processing needs. A work item must be explicitly written to make use of asynchronous tasks. JOB EXECUTION FRAMEWORK All BMC BladeLogic Server Automation jobs execute in the job execution framework. storage. however. having been introduced in BMC BladeLogic Server Automation version 8. Currently. or to a component on a target. dedicated to executing jobs in the job queue. and network resource requirements. but the tasks occupy a thread from the pool only when they have active processing to perform. a job that is scheduled to execute against 1. Page 4 . the work item can instead create and queue an asynchronous BlExec task to perform the operation. When a work item must perform a remote operation. threads from this pool manage lightweight work items. Some work items. Then the work item itself terminates. This resource utilization concern is addressed by the introduction of asynchronous tasks. The main work of a job is the creation and management of individual work items and their results. is maintained by each job server for the execution of work items. otherwise. A work item may or may not be executed by the same job server that is responsible for executing the job that created it. Asynchronous BlExec tasks are managed by the BlExec service. Each job server maintains a pool of threads. Like jobs. and work items The execution of a BMC BladeLogic Server Automation job begins with the job being placed in a work queue of jobs waiting to execute. known as work item threads. work items are executed by job servers. the lightweight work item thread pool. a job may generate multiple work items for each target.

if one exists.bnp file is used directly. This comparison is performed between the new .snp file is renamed to . The table shows a summary of resource usage for Snapshot Jobs. in the case of an unchanged file. The job server uses the data in the database to reconstruct a .bnp file is obtained depends on the BMC BladeLogic Server Automation version. it is then scanned and compared to the most recent prior snapshot from that target. The . Therefore. NSH Script jobs and patch analysis jobs take advantage of asynchronous BlExec tasks. On the other hand. In BMC BladeLogic Server Automation 8.bnp (baseline snapshot) representing the previous scan. the entire contents of that file must be transferred to the Application Server.6 and earlier Version 8. Application Server CPU High Network Traffic High Database Load Moderate Agent Low Page 5 . the file’s content is received as a separate file and not included in the .snp file. The exact means by which the . information about each asset is stored in a local (on the Application Server) file with a . If the . After the comparison between the two . capturing just the MD5 digest (checksum) of a file.bnp of the current snapshot of the asset and the .bnp files (that is. Snapshot Jobs Snapshot jobs collect information about assets from a target and convey that information to the Application Server. instead of the actual contents.bnp from that job run is still available on the job server.6 and earlier Version 7. When construction of the . Otherwise.0.bnp file also remains on the job server.bnp file as it would have existed following the last scan of this particular target. then the old . The lone exception to this rule is that when a file’s content is included in a snapshot.0 and later. Otherwise.0. Audit.6 and earlier Version 8. Version 7. processing steps follow this flow: Only in version 7.bnp and copied to the file server. For example. only the differences between the two versions are stored in the BMC BladeLogic Server Automation database. In BMC BladeLogic Server Automation 8.snp file. however. Version7.1 The BlExec service and asynchronous BlExec tasks are not available earlier than BMC BladeLogic Server Automation 8. the file is deleted). Version 8. As it is received by the Application Server. repeated snapshots of an asset that changes very little or not at all result in relatively little information being stored in the database. the next processing step takes place.snp (snapshot) suffix.snp file is completed on the Application Server. One . (In BMC BladeLogic Server Automation version 8. the . it is copied from the file server to the local Application Server and then used for comparison. Deploy jobs and Virtual Guest Jobs also take advantage of asynchronous BlExec tasks. and a . no additional data is recorded in the database. Files are the most common type of asset used in Snapshot and Audit Jobs. the .0. COMPLIANCE This section describes Snapshot. the next processing step takes place.snp file.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Version 7. To perform a full snapshot of a file. results in the calculation of the 128-bit MD5 digest value on the target and transmission of only that 128-bit value to the Application Server for storage in the .snp file is constructed for each component part.bnp file from the last scan of this particular target is available on the file server (see below).0 Version 8.6 and earlier If the last scan of this particular target ran on the same job server and the old .1. and rules-based Compliance Jobs.6 and earlier After the snapshot job executes.0.bnp file from the prior snapshot).

in that it involves constructing and comparing two snapshot files on the Application Server (with a . each target of the audit job is processed by first constructing a target . master .snp suffix this time). For live audits. As each requested asset arrives on the Application Server. Compliance autoremediation If a target is noncompliant and if the Compliance Job has the Allow Auto-remediation option specified.) The Compliance Job then runs a BLPackage Deploy Job against the noncompliant targets. The master . Application Server CPU High Compliance Jobs Compliance jobs. also called rule-based compliance jobs.snp files are recorded in the database.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Audit Jobs Audit Job behavior is largely similar to that of Snapshot Jobs.snp files are marked for deletion on the file server. Differences between the two . and shared among any Application Servers that run work items for the Audit Job. Each suitable target is then contacted and sufficient assets collected to perform a test of the signature condition for the target. The result (compliant. each work item operates by looping through the component parts of its assigned component. Page 6 . (Any other hosts with the same combination of failing rules will use the same remediation package. For example. noncompliant. After the master . For a snapshot-based audit.snp files for that target are discarded. the master . regardless of how many earlier audits may have detected the same difference. The table shows a summary of resource usage for Audit Jobs. master . The Compliance Job does not complete until the BLPackage Deploy Job has completed.snp file is generated from data in the database. a non-complying condition on file size causes the actual file size to be recorded in the database. the asset from the target . or noncompliant with exception) of applying each condition is recorded in the database. After each audit target is processed. a snapshot of the master target is performed and the results captured in . the specific value under test is also recorded in the database.snp file and then comparing the master and target . the target . If it does need to retrieve assets for the current component part. it decides whether or not it needs to retrieve data from the target. In the case of a noncompliant result. Upon completion of the Audit Job.snp files.snp files have been constructed. When a Compliance Job runs. the relevant conditions are applied to determine compliance. if necessary. but not the contents of the file. Application server CPU High Network Traffic Moderate – High Database Load Moderate Agent Moderate Network Traffic High Database Load Moderate Agent Low COMPONENT DISCOVERY JOBS Component Discovery Jobs first use component applicability rules to select appropriate targets from the requested list of targets. a single request is issued to collect the required information for each of the assets to be tested. and recording only the differences.snp or .bnp) on the Application Server. For each difference detected.snp files. then each rule failure selects a BLPackage to be included in a combined remediation BLPackage for that host. Compliance Jobs do not use temporary snapshot files (.snp files are always constructed as part of the job. operate by: collecting asset information on the target transferring that data back to the Application Server applying the user-specified rules to the returned data to assess the target’s compliance Unlike Audit and Snapshot jobs. for each component part.snp files are copied to the file server. The table shows a summary of resource usage by Component Discovery Jobs. The table shows a summary of resource usage for Compliance Jobs that perform autoremediation.snp file is persisted in the database. For Audit Jobs.

with the Application Server again acting as an intermediary. Use of the Process Spawner offers significant performance benefits for NSH Script jobs.1. Type 3 jobs differ from the other types in that they execute the script on the target. Version 8. BMC does not recommend using the Process Spawner in these versions. The table shows a summary of resource usage by the Process Spawner. there is no direct data transfer between the source and the target. see Asynchronous BlExec tasks on page 4. any nexec commands are executed on the target. a script then runs on each repeater to push the file to the final target. Use of the Process Spawner can significantly reduce the overhead of creating and tearing down the process used to execute the NSH script. Choosing this option causes the job to be executed using asynchronous BlExec tasks. the script running on the Application Server copies the file to one or more remote repeaters. For a direct File Deploy Job.1. For an indirect File Deploy Job. use of the Process Spawner can result in deadlocks or hangs under high workloads. Even for scripts executed on the Application Server however.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Application Server CPU Low – Moderate Network Traffic Low – Moderate Database Load Moderate Agent Low NSH SCRIPT JOBS Scripts executed by NSH Script Jobs are categorized by the four radio buttons presented in the job’s Add Script dialog: Execute the script separately against each host (Type 1) Execute the script once. Page 7 . Version 7.6 and earlier Version 8. This script runs on the Application Server. Version 8. passing the host list as a parameter to the script (Type 2) Copy and execute the script against each host separately (Type 3) Execute the script using the PERL interpreter. the script running on the Application Server copies the file from its source to each target. rather than on the Application Server. BMC recommends its use. Process Spawner NSH Script Jobs invoke the actual NSH scripts in a separate process. Issues with deadlock and hangs are resolved in release 8. That separate process can be created and managed either by the Application Server or by a separately-running application known as the Process Spawner.0.0 and later As of BMC BladeLogic Server Automation version 8.1 and later Prior to BMC BladeLogic Server Automation version 8.0. users have the option of selecting asynchronous execution for Type 3 NSH Script Jobs. The Application Server acts as an intermediary. Application server CPU Varies Network Traffic Varies Database Load Low Agent Varies DEPLOY JOBS This section describes file and package deploy jobs. passing the host list as a parameter (Type 4) From a performance perspective.nsh script to copy (push) the requested file. File Deploy Jobs A File Deploy Job arranges to deploy a file from any NSH-accessible location to one or more remote targets. A File Deploy Job operates by first constructing and then executing an .

Version 8. these commands are executed on the remote target. The table shows a summary of resource usage by File Deploy Jobs. If the package uses the agent mounts source option. as most of the work for this phase is carried out on the target hosts.1 and later As of BMC BladeLogic Server Automation version 8. Similarly. The Commit phase. as most of the work for this phase is carried out on the target hosts Page 8 . its effects are reverted on the target. Any necessary files are copied to the target in preparation for deployment. for example. work items for the BLPackage Deploy Job’s Commit phase are implemented as Lightweight Work Items. registry keys and configurations within files. if any. With the exception of work items for predeploy and postdeploy commands. Phases of the BLPackage Deploy Job BLPackage Deploy Jobs comprise a sequence of work items run in the following phases: Phase Simulate Staging Work Item Description This is a dry run or preflight phase to verify that conditions exist which should lead to a successful execution.1. These server objects are packaged together for unattended deployment on multiple remote hosts. Notes Asynchronous BlExec task High file server load Lightweight Work Item Lightweight Work Item. Asynchronous BlExec task Lightweight Work Item Asynchronous BlExec task The Staging phase has the potential to generate significant workloads on the file server (or other server providing the package source files). if any. not just files. no staging is required. Execute Pre commands. Application Server CPU Low Network Traffic High Database Load Low Agent Low The Staging phase has the potential to generate significant workloads on the file server (or other server providing the package source files. presents almost no load to the BMC BladeLogic Server Automation infrastructure. on page 4. possibly by way of repeater servers. presents almost no load to the BMC BladeLogic Server Automation infrastructure. Application Server CPU Moderate Network Traffic High Database Load Moderate Agent Moderate The server from which the files are deployed can experience heavy load during a File Deploy Job. any Repeaters involved can experience heavy load during a File Deploy Job. See Lightweight work items. page 4. Undo If the deployment is unsuccessful. BLPackage Deploy Jobs A BLPackage is an aggregation of many types of server objects. in contrast. The table shows a summary of resource usage by BLPackage Deploy Jobs. in contrast.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration When pre-commands or post-commands are specified as part of a File Deploy Job. on the target. several phase work items have been enhanced to use asynchronous BLExec tasks for execution. Commit Execute Post commands. including. The Commit phase. See Asynchronous BlExec tasks. allowing for increased throughput even without populating the thread pool for lightweight work items. on the target. Run installation commands on the target.

Adobe) are conceptualized as comprising metadata. to identify a PXE server PXE server. Microsoft. for initial booting instructions TFTP server. Page 9 . for operating system installation files Generally speaking. it requests progressive instructions from BMC BladeLogic servers and downloads boot images and operating system installation files from servers on the network. containing the actual bits of the patch. The table shows a summary of resource usage by Provision Jobs. PATCHING JOBS In BladeLogic. The boot server must be on the same network as the provisioning target. Provisioning details Windows and Linux provisioning Provisioning support for Windows and Linux devices is based on the Pre-Execution Environment (PXE) standard. from which it retrieves the system package Data store. Red Hat. then the job monitors the progress of the provisioning activity as it occurs on the target. depending on the type of target device. while installation files are served off an NFS server (data store). The data store server may experience moderate to high load during provisioning. but in all cases. AIX provisioning The IBM AIX Network Installation Manager (NIM) technology uses a NIM master to control the provisioning target. or combined into one or two actual JumpStart servers. a Windows or Linux target contacts the following: DHCP server. Of the three functions. as the target device is rebooting. software patches released by a patch vendor (that is. As the target device reboots. but the network link between the target device and the data store server may experience substantial bandwidth usage. HP-UX provisioning The HP-UX Ignite technology uses a single Ignite master to control the provisioning target and to provide the operating system installation files. the install server (the data store) bears the greatest load. When booting under the control of a provisioning job. it requires network access to servers from which it can retrieve instructions and downloadable artifacts. describing the patch and its applicability. in most cases. The device’s boot process varies. Application Server CPU Very Low Network Traffic Low Database Load Low Agent Low Provisioning servers (whatever the type) must be available to the target host being provisioned. none of these activities impose significant computational demands on the supporting servers. and a payload.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration PROVISION JOBS A Provision Job establishes the necessary network resources required for a target machine to be provisioned upon reboot. from which it downloads a pre-boot kernel image. Application Server. Solaris provisioning The Oracle JumpStart technology used for provisioning Solaris machines relies on three separate JumpStart functions: JumpStart Boot Server JumpStart Install Server JumpStart Configuration Server These functions may be provided independently.

0. the patch remediation job runs an algorithm that creates a set of BLPackages and BLPackage Deploy Jobs. For Windows and Solaris. That is.0. Catalog Update Jobs You can create Catalog Update Jobs for each type of patch repository. according to filters defined in BladeLogic. Application Server CPU High Patch Analysis Jobs On all supported platforms as of BMC BladeLogic Server Automation version 8. the Application Server must be configured to allow traffic to pass through any firewalls and web proxy servers). For example.6 and earlier Version 8. patch analysis for Solaris was performed primarily on the Application Server. Version 8. The Windows Helper Server Location is a user-defined temporary directory on a Microsoft Windows server which is used to decrypt files downloaded from the vendor site. The Application Server running a catalog update job for an online repository requires web access to these sites (that is. where it is decoded.1 and later Prior to BMC BladeLogic Server Automation version 8. without downloading the payload. Patches are organized into patch catalogs. the patch remediation job creates a single Deploy Job with BLPackages that target the servers. patch analysis for all target types now uses an asynchronous agent call. and the Application Server is running on a Linux host. Network Traffic High Database Load Moderate Agent Low The table shows a summary of resource usage by Catalog Update Jobs.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Patches are stored in a repository in the computing environment. Further. If different Page 10 . patch analysis processing takes place on the affected target. which is an NSH-accessible directory somewhere in the BladeLogic environment.0. As of BMC BladeLogic Server Automation version 8. for Solaris patch analysis. the catalog for Windows patches is separate from the catalog for Red Hat patches. the target agent then performs the necessary calculation to determine which patches to install on the target. If a repository is to include Windows patches. the relevant metadata (typically less than 5 MB) is transferred from the repository to the target agent. patch analysis for Solaris now occurs on the target. The table shows a summary of resource usage by Catalog Update Jobs. rather than on the target. you can run analysis with just the metadata. which typically mounts removable storage media onto which patch information is already loaded. above. So you can create a Windows patch catalog with all Windows 2008 patches and only download payloads of the patches that are found missing. If multiple servers have the same set of missing patches. An offline or air-gapped environment is one in which the repository does not have direct access to the internet and therefore patches cannot be directly downloaded from the vendor site to an offline repository. This can present a moderate to high work load on the Application Server. allowing greater concurrency on the Application Server. Application server CPU Low* Network Traffic Low Database Load Low Agent Moderate – High* *See version-specific notes. Offline patch catalogs are updated by transferring content from a local server. Online patch catalogs are updated by downloading additional content from vendor and/or metadata-provider websites. Based on the patch analysis results. then you must identify a Windows Helper Server Location when you create the repository. Red Hat requires a payload download. Patch Remediation Jobs A patch remediation job does the following: Runs a patch download job to download patch payloads of missing patches that have not yet been downloaded.0. Version 7. A common strategy for populating an offline repository is to transfer patch content on removable media with the help of a BMC-provided download utility.

Configuration decisions for the new virtual guest are captured in a Virtual Guest Package. The table shows a summary of resource usage by UCS Provisioning Jobs.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration servers have different patches missing. Virtual Guest Jobs require minimal Application Server resources. Virtual Guest Jobs operate as BLPackage Deploy Jobs. the patch remediation job creates a Deploy Job for each unique set of missing patches. Virtual Infrastructure Discovery Job Also called a sprawl job. a Virtual Guest Job communicates with the VCenter through a custom object (CO) that must be installed on the Virtual Center host. and storage configurations (WWNN and WWPN). This template contains server identity information (MAC address). The BLPackage Deploy Jobs are wrapped into a Batch Job. with or without an operating system. network. Application Server CPU Low – Moderate UCS Provisioning Jobs A Cisco Unified Computing System (UCS) chassis comprises a number of hardware blades which act as a pool of computing resources. for more information about the resource demands of the deploy operations. The table shows a summary of resource usage by Patch Remediation Jobs. The table shows a summary of resource usage by Virtual Infrastructure Discovery Jobs. The BladeLogic UCS custom object (CO) communicates with this hardware entity. so the behavior and resource demands of a Virtual Guest Job correspond to those of the Deploy Job. The chassis also includes a hardware entity (the Fabric Interconnect) that manages all the computing. networking configuration. Network Traffic Moderate Database Load Low – Moderate Agent Low Page 11 . from a known VCenter or other virtual infrastructure. a Virtual Infrastructure Discovery Job scans the network to identify ESX servers or other virtual hosting environments and then interrogates them to identify guests hosted by that computer. Patch resources are stored in the patch repository. applies the template to a stateless blade (so that the blade becomes a server with an identity). above. and storage connectivity resources. For some steps in its operation. or is scheduled to execute at a later time. The table shows a summary of resource usage by Virtual Guest Jobs. A UCS template is a configuration that contains settings to configure a blade to become a server. and then provisions the server. The UCS Provisioning Job takes a predefined template. The Batch Job then executes immediately (if specified). VIRTUALIZATION JOBS Virtual Guest Job A Virtual Guest Job constructs a virtual guest. Internally. which may experience heavy workload during the Staging phase of deployment. Application server CPU Low Network Traffic High Database Load Low Agent Low See BLPackage Deploy Job. Application Server CPU Very Low Network Traffic Low Database Load Low Agent Low Virtual Guest Jobs make demands on the Virtual Center host to accomplish construction of the virtual guest.

and then overwrites the user file (the file in the target’s rsc directory whose name is ‘user’) with those entries. Application Server CPU Low Network Traffic Low Database Load Low Agent Low Page 12 . an ACL Push Job computes a set of entries for the user file on each target. etc. IP address. Application Server CPU Low Network Traffic Low Database Load Low Agent Low Network Traffic Low Database Load Low Agent Low Distribute Configuration Objects Jobs The table shows a summary of resource usage by Distribute Configuration Objects Jobs. ADMINISTRATIVE JOBS Update Server Properties Job The Update Server Properties Job invokes miscellaneous remote commands to obtain server name. The table shows a summary of resource usage by Update Server Properties Jobs. operating system type and version. Application Server CPU Low ACL Push Jobs At its core. Application Server CPU Low Network Traffic Low – Moderate Database Load Low Agent Low – Moderate Decommission Configuration Object Jobs The table shows a summary of resource usage by Decommission Configuration Object Jobs. The table shows a summary of resource usage by ACL Push Jobs.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Application Server CPU Very Low Network Traffic Low Database Load Low Agent Low UCS Provisioning Jobs make demands on the UCS Fabric Interconnect to accomplish the actual construction of the virtual guest.

High latency on the link between the Application Servers and the database server can cause unacceptable performance for BladeLogic. page 16. but. see Adding Application Server instances. it may be advisable to configure multiple job servers on the same physical machine in order to make more complete use of the available hardware resources. BMC recommends the use of a dedicated physical machine or cluster to host the database server for BladeLogic.exe) connect to configuration servers to allow interaction with the BladeLogic system. job servers are limited by internal resource contention. Database server At the center of every BMC BladeLogic Server Automation installation is the BMC BladeLogic database server. An Application Server can fulfill any of several distinct profiles. NSH Proxy Servers NSH Proxy Servers perform a specialized role in BladeLogic installations. BLCLI command line client. For more information. BMC BLADELOGIC SERVER AUTOMATION COMPONENTS This section describes the components that may constitute a BMC BladeLogic Server Automation installation. The database server or cluster should be on the same LAN as the BMC BladeLogic Server Automation Application Server. A configuration (UI) server is an Application Server of type CONFIGURATION of type ALL (which includes CONFIGURATION). Application Servers A BMC BladeLogic Server Automation deployment comprises one or more Application Server (appserver) processes. The number and configuration of Application Servers in a deployment depends on many factors. as described in NSH proxies. or combinations of profiles. Alternatively. you can run multiple job server guest VMs on the same physical server. in a virtualized environment. A configuration server provides middle-tier functionality. surprisingly. answering requests from BMC BladeLogic Server Automation client applications both for data and for operations on that data. Application Servers are tightly coupled to the database and impose significant demands on the server that hosts the database. there is anecdotal evidence that high packet loss rates on the Application-Server-to-database link may cause issues for (expose defects in) the Oracle JDBC driver. do not impose excessive workload on the hardware. bmi. Configuration servers BMC BladeLogic Server Automation clients (rich client UI. Accordingly. This section discusses performance and other considerations for the deployment of the various BMC BladeLogic Server Automation software elements. Additionally. Page 13 . depending on its configuration. it is acceptable to run multiple Application Servers on a single physical server while still maintaining acceptable performance. Job servers Application Servers configured as job servers are responsible for the execution of BMC BladeLogic Server Automation jobs. Within limits. on page 17.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration DEPLOYMENT GUIDANCE A BMC BladeLogic Server Automation deployment typically involves a large number of individual software elements arrayed across a number of physical servers deployed around the environment. In many environments. including the number of targets to be managed and the expected job load for the system.

Any server running an RSCD agent can be designated as the file server for the installation. but performance under that configuration may be unacceptable. depending on the type of server being provisioned. BMC recommends the use of advanced repeaters whenever repeaters are deployed across a WAN. Properly configured. PXE servers A BMC BladeLogic Server Automation PXE server. BMC recommends deploying consoles to servers on the same LAN as the Application Servers to which they connect. Authentication servers do not normally experience a high work load. after which the user is allowed to interact with the BladeLogic client. Both the performance of the file server and the network connection between job servers and the file server have a critical impact on Deploy Jobs. Page 14 . BMC BladeLogic Server Automation performance can be enhanced by employing an NFS-based network-attached storage (NAS) device and mounting the storage on each physical computer hosting an Application Server. localhost should be designated as the file server. As its name implies. the authentication server verifies the identity of a BMC BladeLogic Server Automation user. In this configuration. For environments in which a population of geographically-dispersed users must all have access to the BMC BladeLogic Server Automation console. BMC recommends the use of one or more repeaters at each data center. File server Every BMC BladeLogic Server Automation environment includes a server designated as the file server. for the console and Application Server to be separated by a longer network link. Using NFS as a file server Because NFS sharing provides higher performance than NSH data transfer. This allows users who are offsite from the presentation server to run remote instances of the UI without experiencing excessive latency. technically a specially configured Application Server. so that each Application Server treats the shared mount point as local storage. BMC BladeLogic Server Automation consoles Communication between the BMC BladeLogic Server Automation console and Application Servers requires significant bandwidth. page 24. PXE servers are discussed in Servers for provisioning. a repeater serves as a staging location at each site for packages as they are deployed. Servers for provisioning BMC BladeLogic Server Automation provisioning works with different provisioning technologies. at least one Application Server in a BMC BladeLogic Server Automation environment must be configured as an authentication server. Repeaters For environments in which deploy job performance over the WAN is a concern. performs a specialized role in support of provisioning jobs. Authentication servers Although not a separate Application Server profile.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Process Spawners A BladeLogic Process Spawner offers improved performance for NSH Script jobs under certain circumstances. It is not normally necessary to configure more than one authentication server for a single BladeLogic environment. See Process Spawner considerations. Advanced Repeaters An Advanced Repeater server is simply a repeater that uses BMC BladeLogic Advanced Repeater technology to enable file servers and repeater servers to store and share data more efficiently. page 14. A typical practice is to configure one of the configuration Application Servers also to act as an authentication server. BMC recommends running the console on a Citrix Presentation Server. It is possible. but not recommended.

JumpStart servers should be located on the same LAN as the Solaris servers being provisioned. but may be remote from the BMC BladeLogic Server Automation Application Server. if the provisioning target will be retrieving files from a data store. you must install an RSCD agent on the NIM Master server. and a JumpStart install server. To use a JumpStart server with provisioning jobs. Each target device needs to have access to a local PXE server. Page 15 . it is preferable that the data store be local to the provisioning target. all of which may be (and commonly are) hosted on the same physical device.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Windows and Linux provisioning PXE servers support Windows and Linux provisioning jobs by providing boot-time services to target devices. usually on the same LAN. the data volume of that communication is relatively low. AIX provisioning The IBM AIX NIM technology requires a NIM Master server on the same LAN as the AIX servers being provisioned. A provisioning target also needs access to the BladeLogic Application Server and a data store. The PXE server and the TFTP server must reside on the same physical server. It is therefore acceptable to install geographically-removed PXE servers. a JumpStart config server. so it is not necessary for the Application Server to be geographically proximate to the provisioning target. Solaris provisioning The Oracle Solaris JumpStart technology identifies a JumpStart boot server. Traffic to the Application Server is relatively light. which must communicate with the database over longer network legs. To use a NIM Master with provisioning jobs. However. you must install an RSCD agent on the JumpStart server. Although PXE servers do communicate with the database.

rather than contacting the remote hosts directly. SIMPLE INSTALLATIONS This section describes basic considerations applicable to all BMC BladeLogic Server Automation installations. NSH proxies are used mainly as a security enhancement measure. Configure the Application Server to establish communications with the remote targets by using the SOCKS proxy. Proxies NSH proxies Historically.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration HP-UX provisioning The HP-UX Ignite technology requires an Ignite Master server on the same LAN as the HP-UX servers being provisioned. SOCKS proxies To access targets that are behind a firewall (because they are in a remote data center. page 19. One computer is dedicated to hosting the database. usually over port 4750. NSH proxy servers played an important role in negotiating fire walls in large scale deployments. To use an Ignite Master with provisioning jobs. you must install an RSCD agent on the Ignite Master server. BMC recommends using SOCKS Proxy Servers. and Geographically-distributed installations. See also Large-Scale installations on page 17. while the other hosts all the essential BladeLogic components: Application Server offering: Job server Configuration (UI) server Authentication server File server Management console UI (BMC BladeLogic Server Automation console) This simple installation highlights the fact that BMC BladeLogic Server Automation makes significant use of the associated database. but this practice is no longer recommended.x and later. You can set up a very small-scale installation using just two physical management servers to host BMC BladeLogic Server Automation. establish a SOCKS Proxy Server in each remote data center and configure any intervening firewalls to allow the Application Servers to contact the SOCKS proxy over port 1080. Accordingly. Page 16 . In BMC BladeLogic Server Automation versions 7. for additional considerations. for example) or otherwise not directly accessible from the Application Servers. BMC recommends a dedicated database server or cluster to support a BMC BladeLogic Server Automation installation. A SOCKS proxy normally requires minimal computing power but can be expected to have network bandwidth demands commensurate with its role as a communication concentrator for the remotely-managed targets. In this situation.

it may also be necessary to deploy additional Configuration (UI) servers to support a larger user population.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration For demonstration or other specialized purpose. Increasing job throughput To execute more jobs against more targets in a given period of time. Adding Application Server instances To meet the demands of a larger data center. Fortunately. a typical eight-core server computer with sufficient memory can support three to four Application Servers. it is usually necessary to increase the number of work item threads (WITs) available to execute jobs. LARGE-SCALE INSTALLATIONS Most customer environments are too large to be managed by the simple 2-server infrastructure described in the previous section. you can add BMC BladeLogic Server Automation components to provide greater management capacity. adding WITs means configuring another Application Server. doing so is likely to lead to unacceptable performance in most cases. In some cases. Most commonly it is necessary to add job servers to provide support for a larger number of managed servers. Under these guidelines. In most cases. it is possible to host all the components on one machine. remember to allow memory for the operating system and for other processes running on the computer. However. In figuring required RAM for the physical server. then. The number of WITs is a configurable option of each job server. It is frequently the case that a physical server has CPU and other resources sufficient to host several times the total number of WITs that can be run in a single Application Server. See Configuration guidance on page 20 for more detailed suggestions on memory and WIT settings for job servers. it is likely that additional Application Servers will need to be deployed. but the number of WITs per job server is normally limited by the amount of memory available in a single Application Server. This section describes the use of additional infrastructure to provide greater capacity for a BMC BladeLogic Server Automation installation. including the database server. including the Application Server launcher. Page 17 . A rule of thumb is to install Application Servers on physical servers based on the assumption that each Application Server requires: Two CPU cores Physical memory sufficient for the Application Server process (4 GB for a 32-bit Application Server and 8-10 GB for a 64-bit Application Server).

scheduling jobs and work items according to availability. or spread the Application Servers across separate virtual machines.bmc. a share exported by the filer is mounted at the same mount point on each computer hosting an Application Server. for best performance. these guidelines call for one Configuration server for every 250 users. BMC typically recommends: Install one Configuration server for every 50 concurrent logged-in users. this configuration allows the use of clustered NAS servers. Further. In virtualized environments.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Support for more users For environments supporting a large user population. Limits to growth Neither Oracle nor SQL Server has a theoretical limit on the number of database connections that a database server can support. the choice naturally arises whether it is better to deploy multiple Application Servers in a single virtual machine. No additional load balancing considerations are applicable for job servers. it may be necessary to provide load balancing services to ensure that the extra resources being applied are being utilized appropriately. http://documents. of course. Scaling the file server The BMC BladeLogic Server Automation design requires a designated File Server to host the files in the BladeLogic Depot. BMC recommends deploying Application Servers in separate virtual machines. avoid allocating more vCPUs than the physical host has physical CPU cores. in the absence of additional information. In combination. In this configuration. This. and the file storage path is that on which the shared storage is mounted. If you plan to establish an extremely large BMC BladeLogic Server Automation implementation. you may need to increase the number of Configuration (UI) Servers in the installation. Load balancing In large deployments involving multiple instances of some or all BMC BladeLogic Server Automation components. a configuration offering several benefits in terms of performance and scalability. but as a starting point. In both cases. In addition. the Application Server performs best when the virtual machine hosting it is configured to have one dedicated virtual CPU (vCPU). In addition.com/supportu/documents/29/84/142984/142984. http://documents. Then work with the local DBA and database vendor to ensure that the database server is capable of supporting that load. A NAS filer using NFS or SMB can act as a kind of virtual file server. limits the total number of Application Servers a particular BMC BladeLogic Server Automation implementation can support. Job servers effectively perform their own load balancing. you should use the information in the Configuration Guidance section to estimate the total number of database connections required for the implementation.pdf. However.bmc. allowing for redundancy and higher performance. You can control the minimum and maximum number of database connections maintained by an Application Server through user-configurable settings for the various database connection pools. See BMC BladeLogic Application Server Running on VMware ESX: Performance and Scalability Best Practices. Considerations for virtualized environments When BladeLogic Application Servers are hosted in virtual (guest) machines in a virtualized environment. making the share appear to be local storage for each Application Server. the actual physical resources available on the database server impose a practical limit on the number of database connections that that particular database server can maintain.com/supportu/documents/60/54/106054/106054. and BMC BladeLogic 8.0 Application Server Running on Red Hat Xen: Performance and Scalability Best Practices.pdf . The File Server is then defined to be localhost. Expect as many as 20% of total users to be logged in at any one time. This configuration offers potentially improved performance because the NFS protocol used by the filer exhibits better performance over the network than does the NSH protocol. The File Server is simply a server running the RSCD agent. The workload required to support a user varies widely. Page 18 . in turn. the Application Servers themselves are likely running on the same physical host computer.

with at least one repeater configured in each remote data center. you can achieve a crude but effective load balancing simply by assigning different users to use different configuration servers. The BMC BladeLogic Advanced Repeater is an enhancement to the repeater architecture that provides scalable transport of data over wide-area networks. In these cases it is necessary to consider not just the scale of the BMC BladeLogic Server Automation installation but also its geographic distribution. it is usually not practical to deploy a management console (BMC BladeLogic Server Automation console) at a remote site. The firewall can be configured to route connections on port 1080 (the SOCKS proxy port) to the SOCKS Proxy Server. For more homogeneous load balancing. Repeaters You can configure repeaters as staging areas for deployment files. in addition to remote managed servers. PXE and TFTP servers. it is unusual for the largest customer environments to be entirely contained within a single data center.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Two strategies for load balancing are commonly applied for configuration (UI) servers: For cases where the user population and behaviors support it. the installation also requires access to BMC BladeLogic Server Automation for remote users. Citrix Presentation Server If. Appropriate use of repeaters in remote data centers can significantly reduce the amount of network traffic that must be carried over long (slow and/or expensive) data lines. For performance reasons. Page 19 . the RSCD agent port). due to the bandwidth and latency requirements for the console-to-configuration server link. BMC recommends the use of advanced repeaters for geographically-distributed deployments. GEOGRAPHICALLY-DISTRIBUTED INSTALLATIONS For a variety of reasons. each remote data center must provide support for one or more provisioning-related services. for example DHCP. that may be important for large-scale installations. you must add an external load balancer to the installation and use it to distribute the load across configuration servers. which then brokers a connection to the actual target server agent (on port 4750. support for provisioning targets in remote data centers must be provided from provisioning servers located in the remote data center. (This staging pushes to the repeater and then pushes from the repeater to the target. BMC recommends the use of a Citrix Presentation Server. such as bandwidth throttling and secure communications. Depending on the provisioning technology used. BMC recommends the use of a SOCKS proxy in the remote data center. SOCKS proxies For a remote data center accessible only through a firewall.) Provisioning servers As a rule. The BIG-IP product by F5 is a common choice for this purpose. This section describes additional infrastructure recommended for managing servers in remote data centers. Load balancing for authentication servers (for example. for purposes of failover) must similarly be provided by an external load balancer. Advanced repeaters also offer additional features. Deploy Jobs with targets in remote data centers should normally be configured to use indirect push staging.

Java heap. typically 50% or more larger than the 32-bit Java process. of course.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration CONFIGURATION GUIDANCE This section offers guidance on appropriate settings for the configuration parameters for a BMC BladeLogic Server Automation Application Server.ugent. In this case. 32-bit processes A process running under any 32-bit operating system is limited to 4 GB of virtual address space. To complicate matters further. especially out-of-memory errors.be/~leeckhou/papers/SPE06. Page 20 . Recommended Java heap settings This section describes recommended Java heap sizes for Application Servers running under different operating systems. Both heaps. usually by adding recommended values for the same parameter for different Application Server types. from which the operating system must reserve a significant portion for itself. you must modify the parameter recommendations. allowing an application process only 2 GB total private process space. For an example. These are recommendations only and must be adjusted in light of observed conditions. The Java heap is managed by the Java garbage collector. Process space. and other objects not managed by the Java garbage collector. Increasing the maximum size of the Java heap necessarily decreases the maximum possible size of the native heap that can fit within a certain process size. it is possible to run out of Java heap memory. file handles. Apart from some general discussion. and so is sometimes called GC heap. as well as timing effects between concurrently-operating threads. For large Java applications like Application Servers. together with the Java executable code itself. peak memory use for either the Java heap or the native heap depends on the precise work load being considered. If the maximum Java heap size is set too high. 64-bit processes A process running under a 64-bit operating system has access to a much larger virtual address space. This section provides an overview of some considerations that apply to correctly sizing Java memory for BladeLogic. Refer to the BMC BLADE L OGIC SERVER AUTOMATION ADMINISTRATION GUIDE for details on using the blasadmin tool to control the configuration parameters. An Application Server can. Compared to a 32-bit Java process performing equivalent work. see http://users. this process space limit imposes a ceiling on the number of threads that can be accommodated within a single Application Server. If the maximum Java heap size is set too low. this section organizes BMC configuration recommendations according to type for single-purpose Application Servers.pdf. it is possible to run out of native heap memory. and native heap A Java process comprises two distinct memory areas: the Java heap and the native heap. the recommendations that follow are merely that: recommendations. ABOUT JAVA MEMORY Effective operation of a large Java system like the BladeLogic Application Server depends critically on the availability of sufficient heap memory. 32-bit Windows divides the entire address space in half. be configured to provide the combined services of the single-purpose Application Server (an Application Server of type ALL). For example. The java heap contains Java objects and accounts for most of the memory required by a running Application Server. Therefore. a 64-bit Java process also requires a larger Java heap. The native heap (also sometimes called the C heap) contains thread stacks.elis. must fit within the footprint of a single process. not guarantees or absolute limits.

BMC recommends that the Java heap size be increased as indicated in the table. Each connection pool allows the configuration of a minimum and maximum number of connections. while still consuming as much memory and other resources as any other thread. This phenomenon has a mildly positive effect on overall performance as the number of threads increases. but doesn’t double it. Due to memory constraints. available process size limits the number of threads available in an Application Server. if there is sufficient physical memory to support this setting. although BMC recommends leaving the minimum value at zero for all connection pools. Java threads may also consume operating system resources such as thread handles. increasing the number of threads is subject to diminishing returns. which are not shared between threads in different processes. This effect degrades per-thread performance as the number of threads increases. because another thread is more likely to have already placed the element in the cache. sometimes sharply so. Doubling the number of threads in a pool improves performance. Each thread consumes resources. As the number of threads in a process grows. that is. Each additional thread provides a smaller and smaller net benefit. as the number of threads increases. Contention: Because some operations on some data structures require exclusive access. See operating system-specific recommendations for this value summarized in the table below. Increasing the number of threads within a single process. ABOUT DATABASE CONNECTIONS Connections between an Application Server and the database are managed in three connection pools. even when idle. While executing. especially threads within a particular thread pool. Selecting appropriate sizes for each of the various thread pools is one of the most important configuration choices for an Application Server. especially memory. especially caches. a thread consumes even more memory. Threads within the same process share certain data structures. blasadmin Setting Module AppServer Setting MaxHeapSize Description and Recommendation Specifies the maximum heap size for this Application Server.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration For 32-bit processes. the negative contention effects grow more rapidly than do the positive serendipity effects. each dedicated to a specific purpose. Max Java Heap Recommendations Operating System Windows Linux Solaris 32-bit 1024 MB 1536 MB 2048 MB 64-bit 6144 MB 6144 MB Not applicable ABOUT THREAD POOLS An Application Server maintains several thread pools. any given item request from any thread is more likely to be fulfilled from the cache. Page 21 . has two consequences: Serendipity: Because there are more threads contributing to the process-wide caches. BMC recommends operating system-specific Java heap size values according to the table below. For 64-bit processes. job servers using 32-bit processes should be configured to use no more than 50 work item threads. Regardless of additional performance considerations. with each pool devoted to a different purpose. there is a greater likelihood of one thread having to wait for another thread’s exclusive access to conclude.

1 Up through BMC BladeLogic Server Automation 8. and the best size will be different for different environments. configuring a database pool with a maximum size that is too low can degrade performance. For installations in which Deploy Jobs represent a significant fraction of the workload. for parallelism. lightweight or not. RECOMMENDATIONS FOR JOB SERVERS This section provides general recommendations for configuring Application Servers established as job servers. otherwise 0. BMC recommends a value up to 200 if Deploy Jobs are a primary use. and for large installations. Page 22 . For 64-bit Application Servers. so a job targeted at thousands of servers can be expected to result in thousands of work items being queued for processing. Configuring a larger number of work item threads risks an OutOfMemoryError under the process size limitations of 32-bit processes. Further. BMC recommends establishing additional Application Servers instead of increasing the number of work item threads. In light of these considerations. BMC recommends 50 work item threads for each of these Application Servers. The default value of 0 threads for lightweight work items uses ordinary work item threads for the execution of all work items. However. BMC recommends 50 work item threads for both 32-bit and 64-bit Application Servers. Recommendations for the lightweight work item thread pool Lightweight work item threads are of benefit primarily for Deploy Jobs.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Configuring a database pool’s maximum size to be too high wastes resources.0. as a thread requesting a database connection from an empty connection pool blocks until a connection becomes available. Recommendations for the work item thread pool The work item thread pool is the thread pool whose configuration has the greatest effect on overall job performance. The number of work item threads to configure is primarily determined by the effects of contention between work item threads. Version 8. Version 8. For 32-bit Application Servers.1. the work items themselves tend not to be CPU intensive. larger available process spaces make it possible to use a larger number of work item threads. blasadmin Setting Module AppServer Setting MaxLightweightWorkItem Threads Description and Recommended Value Number of threads that can be used to execute lightweight job parts. for parallelism. Version 7. You must also ensure that the database server has sufficient capacity to service all the connections from all the connection pools for all the Application Servers in the environment. BMC recommends working with the DBA and database vendor to ensure that you have this capacity. selecting the best size for this thread pool involves trade-offs. it is usually desirable to allocate a generous number of work item threads for a job server. Conversely. particularly for very large installations.6 and earlier. BMC suggests a value of 200 threads for lightweight work items. BMC recommends a setting of 50 work item threads. may risk exceeding the total capacity of the database server. Most jobs generate one or more work items per target host. blasadmin Setting Module AppServer Setting MaxWorkItemThreads Description and Recommended Value Number of threads that can be used to execute job parts.

BMC recommends using the default value of 20.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Recommendations for the BlExec service and thread pool An Application Server’s BlExec service maintains a pool of threads for the execution of asynchronous tasks involving communication with remote targets. The maximum number of jobs the Application Server allows to run simultaneously. remains the responsibility of the job itself. These configuration parameters do not normally require adjustment from their default values. such as creating the work items themselves. the default setting is true. a lower value reduces the demand for file descriptors. While most of the work involved in executing a job is delegated to work items. BlExec MaxSocketConnections Maximum simultaneous sockets open by the BlExec service. It is not normally necessary to change the BlExec service’s configuration settings. blasadmin Setting Module AppServer Setting EnableAsyncExecution Description and Recommended Value Enables/disables the async execution framework for jobs that allow it. when that option is selected. blasadmin Setting Module AppServer Setting MaxApprovalThreads Description Number of Approval Threads. it is the default value that appears in the UI for a job’s maximum parallelism option. this section describes some additional configuration parameters related to thread pool sizes for job servers. This parameter governs a small pool of threads used to communicate with BMC Atrium Orchestrator. Other parameters For completeness. regardless of the availability of resources to execute the jobs. JobFactory GlobalDefaultJobParallelism Global default value for Job Parallelism made available to user. and will be carried out by the job execution pool. AppServer MaxJobs Maximum number of jobs the Application Server can execute simultaneously. This parameter has no direct effect on the operation of the Application Server. Rather. Deploy Jobs. BlExec NumWorkerThreads Number of worker threads used by the BlExec service. You can set the value to true or false. for example. some of the work. Maximum size for the job execution pool. AppServer MaxJobThreads Maximum number of threads that can be used to execute a job. BMC recommends leaving async execution enabled. the default values produce good results in most cases. The job execution pool is distinct from the work item thread pool. for parallelism. Page 23 . BMC recommends using the default value of 500 in most cases. A higher value allows more simultaneous connections.

logging of output from NSH script jobs is handled with connections from the general database connection pool.6 and earlier. As an initial estimate. so too does the cost of spawning a new process directly from the Application Server. Page 24 . the benefit of using the Process Spawner increases. especially for environments that depend heavily on NSH script jobs. For BMC BladeLogic Server Automation version 8. rather than spawning them directly. the default value should be adequate. while other jobs use the job execution database connection pool.1 and beyond. BMC recommends using the Process Spawner for all job servers for BMC BladeLogic Server Automation version 8.0. BMC recommends a value of 2 * MaxWorkItemThreads.0 and earlier. As the configured size of the Application Server grows. blasadmin Setting Module ProcessSpawner Setting SpawnExternally Description and Recommendation Processes should be spawned outside the Application Server or not.1 and later. For best performance of NSH script jobs in these versions of BladeLogic. RECOMMENDATIONS FOR CONFIGURATION SERVERS Estimating client connections Parameter value settings for configuration (UI) servers should be based on the number of client connections you anticipate being made to the configuration server. BMC recommends allowing the job execution connection pool to grow up to twice the number of work item threads (MaxWorkItemThreads in AppServer module). BMC recommends setting the maximum size for the general database connection pool to twice the number of work item threads. For version 8. For NSH script jobs. Process Spawner considerations As memory size increases. Database MaxGeneralConnections Maximum connections in the pool for general thread group. BMC recommends a value that is twice the number of work item threads (MaxWorkItemThreads).BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Recommendations for database connections For best job server performance. The Process Spawner is simply a process with a small memory footprint that can spawn new processes without the penalty of the Application Server’s large memory footprint. Version 7. and is usually much more short-lived than an interactive user’s GUI session. The BLCLI client uses exactly one client connection for its execution. Version 8. BMC recommends a planning figure of 2.0 Up through BMC BladeLogic Server Automation 8. blasadmin Setting Module Database Setting MaxJobExecutionConnections Description and Recommended Value Maximum connections in the pool for job execution thread group. This value is the total of the number of client connections from UI clients (RCP) and from BLCLI clients. a job server can be configured to use a Process Spawner to spawn subprocesses. The number of client connections opened by a UI client varies over time and depends on the operations that the user is engaged in at any given moment.5 client connections for each concurrent GUI user.

In the absence of sufficient information from which to form an estimate for peak client connection demand. BMC recommends allowing the pool of database connections for client service threads to grow up to twice the number of client connection service threads (MaxWorkerThreads in AppServer module). BMC recommends estimating peak client connection demand.5 * (number of simultaneous GUI users) + (number of simultaneous BLCLI commands) If multiple configuration servers with a load balancer will be established. it is not necessary to change these parameters from their default values. and setting MaxClientContexts to this value. Recommendations for database connections Similarly. blasadmin Setting Module Database Setting MaxClientConnections Description and Recommended Value Maximum connections in the pool for client connections. BMC recommends using the default value of 200. The client connection service maintains a pool of threads for servicing client requests. Recommendations for the client connection service and thread pool The client connection service is responsible for managing connections from client processes in Application Servers acting as configuration (UI) servers.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Thus. BMC recommends a value that is twice the number of client connection threads. In most cases. the peak demand estimate for client connections for the configuration server is: 2. or approximately 5% of the value of MaxClientContexts. Page 25 . AppServer MaxWorkerThreads Number of client connection worker threads. then the total load for client connections can be divided across the number of configuration servers that will be established. for best configuration (UI) server performance. as described in the previous section. BMC recommends using the default value of 10. The following table describes the parameters that most strongly affect the performance of the client connection service. blasadmin Setting Module AppServer Setting MaxClientContexts Description and Recommended Value Number of maximum client connections to the Application Server.

this value should be the sum of MaxWorkerThreads and MaxNshProxyThreads. configure the NSH Proxy server for the anticipated number of concurrent NSH connections it will be expected to handle. BMC suggests an initial estimate of 20% of MaxNshProxyContexts. For best performance. For an Application Server configured to act exclusively as an NSH proxy server. blasadmin Setting Module AppServer Setting MaxNshProxyContexts Description and Recommended Value Maximum number of NSH proxy connections to the Application Server. this value should be the same as MaxNshProxyThreads. Page 26 . Database MaxClientConnections Maximum connections in the pool for client connections. to account for idle NSH connections.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration RECOMMENDATIONS FOR NSH PROXY SERVERS BMC recommends the use of NSH Proxy servers as a best practice for security. Set this value to the maximum number of concurrent NSH connections the proxy will be expected to handle. AppServer MaxNshProxyThreads Number of NSH proxy threads. This value can be significantly less than MaxNshProxyContexts. In the absence of usage estimates specific to the installation. For an Application Server configured to act as both a configuration server and an NSH proxy server.

used for Windows PXE Servers SOCKS Proxy protocol 5282 HTTP (TCP) Adv. used for Linux PXE Servers SNMP SNMPTRAP BDSSA server PXE Server SOCKS proxy SQL Server DB SQL Server DB SQL Server DB Oracle DB Oracle DB Oracle DB PXE Server RSCD Agent PXE discovery when co-located with DHCP Primary communication channel from Application Server to each managed host SMB. Extended DHCP response to an initial extended DHCP request 68 69 80 80 161 162 443 445 1080 1433 1433 1433 1521 1521 1521 4011 4750 DHCP (UDP) TFTP (TCP/UDP) HTTP (TCP) HTTP (TCP) SNMP (UDP) SNMP (UDP) HTTPS (TCP) SMB (TCP) TCP MS-SQL (TCP) MS-SQL (TCP) MS-SQL (TCP) TNS (TCP) TNS (TCP) TNS (TCP) DHCP (UDP) RSCD (TCP) DHCP PXE client HTTP client PXE client Application Server Application Server HTTPS client PXE client SOCKS client Application Server BDSSA server PXE Server Application Server BDSSA server PXE Server PXE client Application Server Advanced Repeater PXE client TFTP Server BDSSA server PXE Server HTTP. File Server Page 27 . PXE Server binds to 67 UDP.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration APPENDIX: TCP/UDP PORT USAGE The following table summarizes the use of TCP/UDP ports across all the elements of a BladeLogic installation: Port 25 25 67 Protocol SMTP (TCP) SMTP (TCP) DHCP (UDP) From Application Server BDSSA server PXE client To Mail Server SMTP server DHCP service Notes SMTP For emailing scheduled reports and notifications PXE boot broadcasts a DHCP request that includes PXE info. By default.

File Server Notes Marimba publishing -. File Server are not co-located usually local traffic only usually local traffic only usually local traffic only usually local traffic only Cognos report BladeLogic SSO JMX listener -. and so on. with 9800 being the default base port.if the File Server and Adv. Service Application Server NSH Proxy JMX listener for Application Server Authentication Service TCP Application Server RMI communication ports * Application Server ports are normally configured from a base port. Repeater BDSSA server BDSSA Auth. with 9850-9899 being the default for a single Application Server.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Port 7717 Protocol TCP From File Server To Adv. 853. steps 7 and 9) 9838 (base+38*) 9840 (base+40*) 9840 (base+40*) 9841 (base+41*) 9842 (base+42*) 9850-9899 (MinPortMaxPort**) TCP TCP TCP TCP TCP Jconsole Application Server RCP (Client UI) RCP (Client UI) NSH. Repeater Cognos client BDSSA server BLASAdmin console Application Server Console Provisioning Client Application Server Adv. Application Server Application Server Auth.usually local traffic only 7717 7717 7717 8080 9300 9640 9700 9701 9702 9831 9836 (base+36*) TCP TCP TCP HTTP (TCP) TCP TCP JMX (TCP) TCP TCP TCP TCP Transmitter Administrator Proxy Administrator Certificate Manager Adv. Repeater BMCCM Tuner Adv. Service Auth. A second Application Server on the same host will typically have a base port of 9900. Arbitrary port assignments can be made in all cases. Server Application Server Launcher Launcher Launcher Application Server RMI Registry SSL Provisioning (user guide p. File Server Adv. Page 28 . ** The MinPort-MaxPort range is configurable.

2010. All other BMC trademarks. All other trademarks or registered trademarks are the property of their respective owners. AIX and IBM are trademarks or registered trademarks of International Business Machines Corporation in the United States. BMC offers a comprehensive approach and unified platform that helps IT organizations cut cost.com for more information. service marks. © 2011 BMC Software. Recognized as the leader in Business Service Management. are registered with the U. and logos may be registered or pending registration in the U. mainframe. virtual and cloud environments. or in other countries.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Business runs on IT. UNIX is the registered trademark of The Open Group in the U.. BMC revenue was approximately $1. Inc. faster and stronger. Other names may be trademarks of their respective owners. Linux is the registered trademark of Linus Torvalds.S. Business thrives when IT runs smarter. BMC. Visit www.96 billion. Patent and Trademark Office.  *195833* Page 29 . reduce risk and drive business profit.bmc. For the four fiscal quarters ended September 30. and may be registered or pending registration in other countries. IT runs on BMC Software. That’s why the most demanding IT organizations in the world rely on BMC Software across distributed. Oracle and Java are registered trademarks of Oracle and/or its affiliates.S.S. and other countries. BMC Software. or both. Inc. other countries. and the BMC Software logo are the exclusive properties of BMC Software. All rights reserved.

Sign up to vote on this title
UsefulNot useful