You are on page 1of 29

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

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

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

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

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

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

Notes Asynchronous BlExec task High file server load Lightweight Work Item Lightweight Work Item. 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. BLPackage Deploy Jobs A BLPackage is an aggregation of many types of server objects. registry keys and configurations within files. allowing for increased throughput even without populating the thread pool for lightweight work items. including. in contrast. Undo If the deployment is unsuccessful. no staging is required. if any. These server objects are packaged together for unattended deployment on multiple remote hosts. page 4. on page 4. The Commit phase. Execute Pre commands. The table shows a summary of resource usage by BLPackage Deploy Jobs. work items for the BLPackage Deploy Job’s Commit phase are implemented as Lightweight Work Items. If the package uses the agent mounts source option. on the target.1. on the target. The table shows a summary of resource usage by File Deploy Jobs. Any necessary files are copied to the target in preparation for deployment. See Asynchronous BlExec tasks.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. several phase work items have been enhanced to use asynchronous BLExec tasks for execution. Run installation commands on the target. Similarly.1 and later As of BMC BladeLogic Server Automation version 8. 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. presents almost no load to the BMC BladeLogic Server Automation infrastructure. The Commit phase. With the exception of work items for predeploy and postdeploy commands. Commit Execute Post commands. possibly by way of repeater servers. for example. as most of the work for this phase is carried out on the target hosts Page 8 . 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. See Lightweight work items. as most of the work for this phase is carried out on the target hosts. its effects are reverted on the target. presents almost no load to the BMC BladeLogic Server Automation infrastructure. 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. any Repeaters involved can experience heavy load during a File Deploy Job. in contrast. not just files. Version 8. these commands are executed on the remote target.

PATCHING JOBS In BladeLogic. from which it downloads a pre-boot kernel image. for initial booting instructions TFTP server. depending on the type of target device. containing the actual bits of the patch. the install server (the data store) bears the greatest load. Microsoft. When booting under the control of a provisioning job. Of the three functions. Adobe) are conceptualized as comprising metadata. or combined into one or two actual JumpStart servers. AIX provisioning The IBM AIX Network Installation Manager (NIM) technology uses a NIM master to control the provisioning target. Page 9 . and a payload. a Windows or Linux target contacts the following: DHCP server. Provisioning details Windows and Linux provisioning Provisioning support for Windows and Linux devices is based on the Pre-Execution Environment (PXE) standard. none of these activities impose significant computational demands on the supporting servers. but the network link between the target device and the data store server may experience substantial bandwidth usage. 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. to identify a PXE server PXE server. it requests progressive instructions from BMC BladeLogic servers and downloads boot images and operating system installation files from servers on the network.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. for operating system installation files Generally speaking. software patches released by a patch vendor (that is. while installation files are served off an NFS server (data store). describing the patch and its applicability. it requires network access to servers from which it can retrieve instructions and downloadable artifacts. Red Hat. The data store server may experience moderate to high load during provisioning. The boot server must be on the same network as the provisioning target. The device’s boot process varies. Application Server. from which it retrieves the system package Data store. then the job monitors the progress of the provisioning activity as it occurs on the target. 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. in most cases. as the target device is rebooting. As the target device reboots. 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. but in all cases. The table shows a summary of resource usage by Provision Jobs.

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

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

Application Server CPU Low Network Traffic Low Database Load Low Agent Low Page 12 . and then overwrites the user file (the file in the target’s rsc directory whose name is ‘user’) with those entries. IP address. operating system type and version.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. The table shows a summary of resource usage by Update Server Properties Jobs. Application Server CPU Low ACL Push Jobs At its core. 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. 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. etc. 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 ACL Push Jobs. an ACL Push Job computes a set of entries for the user file on each target.

Job servers Application Servers configured as job servers are responsible for the execution of BMC BladeLogic Server Automation jobs. The number and configuration of Application Servers in a deployment depends on many factors. including the number of targets to be managed and the expected job load for the system. 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. The database server or cluster should be on the same LAN as the BMC BladeLogic Server Automation Application Server. Accordingly. High latency on the link between the Application Servers and the database server can cause unacceptable performance for BladeLogic. A configuration server provides middle-tier functionality. BLCLI command line client. 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. NSH Proxy Servers NSH Proxy Servers perform a specialized role in BladeLogic installations. An Application Server can fulfill any of several distinct profiles. Page 13 . it is acceptable to run multiple Application Servers on a single physical server while still maintaining acceptable performance. This section discusses performance and other considerations for the deployment of the various BMC BladeLogic Server Automation software elements. 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. page 16. Additionally. on page 17. in a virtualized environment. Within limits. depending on its configuration. Configuration servers BMC BladeLogic Server Automation clients (rich client UI. see Adding Application Server instances.exe) connect to configuration servers to allow interaction with the BladeLogic system. do not impose excessive workload on the hardware. For more information. but. surprisingly. In many environments. Alternatively. you can run multiple job server guest VMs on the same physical server. Database server At the center of every BMC BladeLogic Server Automation installation is the BMC BladeLogic database server. or combinations of profiles. job servers are limited by internal resource contention. answering requests from BMC BladeLogic Server Automation client applications both for data and for operations on that data. bmi.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. BMC BLADELOGIC SERVER AUTOMATION COMPONENTS This section describes the components that may constitute a BMC BladeLogic Server Automation installation. as described in NSH proxies. Application Servers are tightly coupled to the database and impose significant demands on the server that hosts the database. BMC recommends the use of a dedicated physical machine or cluster to host the database server for BladeLogic.

For environments in which a population of geographically-dispersed users must all have access to the BMC BladeLogic Server Automation console. A typical practice is to configure one of the configuration Application Servers also to act as an authentication server. page 24. at least one Application Server in a BMC BladeLogic Server Automation environment must be configured as an authentication server. the authentication server verifies the identity of a BMC BladeLogic Server Automation user. PXE servers are discussed in Servers for provisioning. so that each Application Server treats the shared mount point as local storage. technically a specially configured Application Server. Servers for provisioning BMC BladeLogic Server Automation provisioning works with different provisioning technologies. It is not normally necessary to configure more than one authentication server for a single BladeLogic environment. BMC BladeLogic Server Automation consoles Communication between the BMC BladeLogic Server Automation console and Application Servers requires significant bandwidth. Page 14 . See Process Spawner considerations. page 14. In this configuration. Repeaters For environments in which deploy job performance over the WAN is a concern. 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. after which the user is allowed to interact with the BladeLogic client. 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. PXE servers A BMC BladeLogic Server Automation PXE server. Using NFS as a file server Because NFS sharing provides higher performance than NSH data transfer. but performance under that configuration may be unacceptable. a repeater serves as a staging location at each site for packages as they are deployed. BMC recommends the use of one or more repeaters at each data center. 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. Properly configured.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. Authentication servers do not normally experience a high work load. Authentication servers Although not a separate Application Server profile. localhost should be designated as the file server. Any server running an RSCD agent can be designated as the file server for the installation. This allows users who are offsite from the presentation server to run remote instances of the UI without experiencing excessive latency. As its name implies. It is possible. but not recommended. performs a specialized role in support of provisioning jobs. BMC recommends deploying consoles to servers on the same LAN as the Application Servers to which they connect. 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. BMC recommends the use of advanced repeaters whenever repeaters are deployed across a WAN. depending on the type of server being provisioned. BMC recommends running the console on a Citrix Presentation Server.

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

NSH proxies are used mainly as a security enhancement measure. 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.x and later. In BMC BladeLogic Server Automation versions 7. SOCKS proxies To access targets that are behind a firewall (because they are in a remote data center. but this practice is no longer recommended. NSH proxy servers played an important role in negotiating fire walls in large scale deployments. In this situation. for example) or otherwise not directly accessible from the Application Servers.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. Configure the Application Server to establish communications with the remote targets by using the SOCKS proxy. and Geographically-distributed installations. 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. rather than contacting the remote hosts directly. Accordingly. BMC recommends a dedicated database server or cluster to support a BMC BladeLogic Server Automation installation. usually over port 4750. You can set up a very small-scale installation using just two physical management servers to host BMC BladeLogic Server Automation. for additional considerations. 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. BMC recommends using SOCKS Proxy Servers. page 19. SIMPLE INSTALLATIONS This section describes basic considerations applicable to all BMC BladeLogic Server Automation installations. Proxies NSH proxies Historically. Page 16 . One computer is dedicated to hosting the database. To use an Ignite Master with provisioning jobs. See also Large-Scale installations on page 17. you must install an RSCD agent on the Ignite Master server.

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

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

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

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

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

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

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

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

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

This value can be significantly less than MaxNshProxyContexts. For best performance. Set this value to the maximum number of concurrent NSH connections the proxy will be expected to handle. to account for idle NSH connections. 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.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. this value should be the sum of MaxWorkerThreads and MaxNshProxyThreads. 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. AppServer MaxNshProxyThreads Number of NSH proxy threads. Database MaxClientConnections Maximum connections in the pool for client connections. BMC suggests an initial estimate of 20% of MaxNshProxyContexts. For an Application Server configured to act exclusively as an NSH proxy server. Page 26 . configure the NSH Proxy server for the anticipated number of concurrent NSH connections it will be expected to handle.

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. 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. 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.

Arbitrary port assignments can be made in all cases. ** The MinPort-MaxPort range is configurable. Repeater BMCCM Tuner Adv. File Server Notes Marimba publishing -. Server Application Server Launcher Launcher Launcher Application Server RMI Registry SSL Provisioning (user guide p. 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 -. File Server Adv. Repeater Cognos client BDSSA server BLASAdmin console Application Server Console Provisioning Client Application Server Adv.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. Application Server Application Server Auth. and so on.if the File Server and Adv. Service Auth. Page 28 . with 9850-9899 being the default for a single Application Server. 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. A second Application Server on the same host will typically have a base port of 9900. with 9800 being the default base port. 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 BDSSA server BDSSA Auth. 853.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Port 7717 Protocol TCP From File Server To Adv.

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