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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

bmc.com/supportu/documents/60/54/106054/106054. limits the total number of Application Servers a particular BMC BladeLogic Server Automation implementation can support. for best performance.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Support for more users For environments supporting a large user population. A NAS filer using NFS or SMB can act as a kind of virtual file server. 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. but as a starting point. in turn.pdf . This. you should use the information in the Configuration Guidance section to estimate the total number of database connections required for the implementation. BMC recommends deploying Application Servers in separate virtual machines. a share exported by the filer is mounted at the same mount point on each computer hosting an Application Server. Job servers effectively perform their own load balancing. Load balancing In large deployments involving multiple instances of some or all BMC BladeLogic Server Automation components. In this configuration. allowing for redundancy and higher performance. this configuration allows the use of clustered NAS servers. avoid allocating more vCPUs than the physical host has physical CPU cores. in the absence of additional information. Further. 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. If you plan to establish an extremely large BMC BladeLogic Server Automation implementation. http://documents. and BMC BladeLogic 8. 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. However. Expect as many as 20% of total users to be logged in at any one time.bmc. a configuration offering several benefits in terms of performance and scalability. you may need to increase the number of Configuration (UI) Servers in the installation. and the file storage path is that on which the shared storage is mounted. 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. the Application Servers themselves are likely running on the same physical host computer.pdf. Page 18 . The File Server is then defined to be localhost. No additional load balancing considerations are applicable for job servers. the Application Server performs best when the virtual machine hosting it is configured to have one dedicated virtual CPU (vCPU). scheduling jobs and work items according to availability. Considerations for virtualized environments When BladeLogic Application Servers are hosted in virtual (guest) machines in a virtualized environment. In addition. of course. BMC typically recommends: Install one Configuration server for every 50 concurrent logged-in users.0 Application Server Running on Red Hat Xen: Performance and Scalability Best Practices. making the share appear to be local storage for each Application Server. it may be necessary to provide load balancing services to ensure that the extra resources being applied are being utilized appropriately. In virtualized environments. Then work with the local DBA and database vendor to ensure that the database server is capable of supporting that load. or spread the Application Servers across separate virtual machines. In combination. Limits to growth Neither Oracle nor SQL Server has a theoretical limit on the number of database connections that a database server can support. http://documents. these guidelines call for one Configuration server for every 250 users. The File Server is simply a server running the RSCD agent. See BMC BladeLogic Application Server Running on VMware ESX: Performance and Scalability Best Practices. In both cases. The workload required to support a user varies widely.com/supportu/documents/29/84/142984/142984. 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. it is unusual for the largest customer environments to be entirely contained within a single data center. In these cases it is necessary to consider not just the scale of the BMC BladeLogic Server Automation installation but also its geographic distribution. each remote data center must provide support for one or more provisioning-related services. which then brokers a connection to the actual target server agent (on port 4750. Deploy Jobs with targets in remote data centers should normally be configured to use indirect push staging.) Provisioning servers As a rule. Repeaters You can configure repeaters as staging areas for deployment files. Citrix Presentation Server If. BMC recommends the use of a SOCKS proxy in the remote data center. For performance reasons. the installation also requires access to BMC BladeLogic Server Automation for remote users. the RSCD agent port). in addition to remote managed servers. Advanced repeaters also offer additional features. for purposes of failover) must similarly be provided by an external load balancer. BMC recommends the use of a Citrix Presentation Server. Depending on the provisioning technology used. SOCKS proxies For a remote data center accessible only through a firewall. Page 19 . 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. with at least one repeater configured in each remote data center. GEOGRAPHICALLY-DISTRIBUTED INSTALLATIONS For a variety of reasons. it is usually not practical to deploy a management console (BMC BladeLogic Server Automation console) at a remote site.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. you must add an external load balancer to the installation and use it to distribute the load across configuration servers. for example DHCP. that may be important for large-scale installations. Load balancing for authentication servers (for example. you can achieve a crude but effective load balancing simply by assigning different users to use different configuration servers. such as bandwidth throttling and secure communications. support for provisioning targets in remote data centers must be provided from provisioning servers located in the remote data center. due to the bandwidth and latency requirements for the console-to-configuration server link. The BIG-IP product by F5 is a common choice for this purpose. PXE and TFTP servers. BMC recommends the use of advanced repeaters for geographically-distributed deployments. For more homogeneous load balancing. The BMC BladeLogic Advanced Repeater is an enhancement to the repeater architecture that provides scalable transport of data over wide-area networks. This section describes additional infrastructure recommended for managing servers in remote data centers.

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

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

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

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

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

as described in the previous section. for best configuration (UI) server performance. the peak demand estimate for client connections for the configuration server is: 2. The client connection service maintains a pool of threads for servicing client requests. Recommendations for database connections Similarly. BMC recommends using the default value of 200. AppServer MaxWorkerThreads Number of client connection worker threads. BMC recommends a value that is twice the number of client connection threads. In the absence of sufficient information from which to form an estimate for peak client connection demand.5 * (number of simultaneous GUI users) + (number of simultaneous BLCLI commands) If multiple configuration servers with a load balancer will be established. 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. or approximately 5% of the value of MaxClientContexts. The following table describes the parameters that most strongly affect the performance of the client connection service. it is not necessary to change these parameters from their default values. BMC recommends estimating peak client connection demand. blasadmin Setting Module AppServer Setting MaxClientContexts Description and Recommended Value Number of maximum client connections to the Application Server. Page 25 . In most cases. blasadmin Setting Module Database Setting MaxClientConnections Description and Recommended Value Maximum connections in the pool for client connections.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Thus. 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 10. 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 should be the sum of MaxWorkerThreads and MaxNshProxyThreads. Database MaxClientConnections Maximum connections in the pool for client connections. BMC suggests an initial estimate of 20% of MaxNshProxyContexts. In the absence of usage estimates specific to the installation. AppServer MaxNshProxyThreads Number of NSH proxy threads. This value can be significantly less than MaxNshProxyContexts. For an Application Server configured to act exclusively as an NSH proxy server. configure the NSH Proxy server for the anticipated number of concurrent NSH connections it will be expected to handle. Set this value to the maximum number of concurrent NSH connections the proxy will be expected to handle. blasadmin Setting Module AppServer Setting MaxNshProxyContexts Description and Recommended Value Maximum number of NSH proxy connections to the Application Server. For best performance. 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. Page 26 . to account for idle NSH connections. this value should be the same as MaxNshProxyThreads.

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

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

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

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.