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

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

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

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

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

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

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

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

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

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

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

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

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

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

page 19. Accordingly. usually over port 4750. NSH proxy servers played an important role in negotiating fire walls in large scale deployments. SOCKS proxies To access targets that are behind a firewall (because they are in a remote data center. 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. See also Large-Scale installations on page 17. rather than contacting the remote hosts directly. Configure the Application Server to establish communications with the remote targets by using the SOCKS proxy. To use an Ignite Master with provisioning jobs. In BMC BladeLogic Server Automation versions 7. and Geographically-distributed installations. but this practice is no longer recommended. 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. You can set up a very small-scale installation using just two physical management servers to host BMC BladeLogic Server Automation. Page 16 . 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.x and later. SIMPLE INSTALLATIONS This section describes basic considerations applicable to all BMC BladeLogic Server Automation installations. for additional considerations. NSH proxies are used mainly as a security enhancement measure. for example) or otherwise not directly accessible from the Application Servers. In this situation. One computer is dedicated to hosting the database. BMC recommends using SOCKS Proxy Servers. you must install an RSCD agent on the Ignite Master server. 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. BMC recommends a dedicated database server or cluster to support 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. The number of WITs is a configurable option of each job server. See Configuration guidance on page 20 for more detailed suggestions on memory and WIT settings for job servers. This section describes the use of additional infrastructure to provide greater capacity for a BMC BladeLogic Server Automation installation. a typical eight-core server computer with sufficient memory can support three to four Application Servers. it may also be necessary to deploy additional Configuration (UI) servers to support a larger user population. it is possible to host all the components on one machine. In most cases. Increasing job throughput To execute more jobs against more targets in a given period of time. then. Page 17 . including the database server. but the number of WITs per job server is normally limited by the amount of memory available in a single Application Server. it is usually necessary to increase the number of work item threads (WITs) available to execute jobs. remember to allow memory for the operating system and for other processes running on the computer.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration For demonstration or other specialized purpose. it is likely that additional Application Servers will need to be deployed. adding WITs means configuring another Application Server. you can add BMC BladeLogic Server Automation components to provide greater management capacity. However. 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). In some cases. Adding Application Server instances To meet the demands of a larger data center. Most commonly it is necessary to add job servers to provide support for a larger number of managed servers. LARGE-SCALE INSTALLATIONS Most customer environments are too large to be managed by the simple 2-server infrastructure described in the previous section. doing so is likely to lead to unacceptable performance in most cases. Fortunately. Under these guidelines. In figuring required RAM for the physical server. including the Application Server launcher.

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

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

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

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

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

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

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

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

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

used for Windows PXE Servers SOCKS Proxy protocol 5282 HTTP (TCP) Adv. File Server Page 27 . By default. 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. 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. 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.

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

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

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.