This action might not be possible to undo. Are you sure you want to continue?
BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration
Date March, 2011 Product version 8.1.00 Revisions Initial version.
................ 24 Recommendations for NSH Proxy servers .............................................................................. 16 Large-Scale installations ...... 12 Deployment guidance .......................................................................................................................................................................................... 4 Job execution framework ................................................................................................................................................................................................................................................................................................................................. 11 Administrative jobs.................................... 27 Page 3 ............................................................................................................................................................... 6 NSH Script Jobs .......................................................................................... 13 BMC BladeLogic Server Automation components ............................................................................................................................. 9 Patching Jobs ....... 19 Configuration guidance .................. 17 Geographically-distributed installations ................................. 26 Appendix: TCP/UDP Port Usage....................................................................................................................... 5 Component Discovery Jobs ............................................................................................................... 21 About database connections .BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration TABLE OF CONTENTS Revision history ................................................................................................................ 21 Recommendations for job servers .......................................... 20 About thread pools.................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. 22 Recommendations for Configuration servers .......................................................................................... 7 Provision Jobs ................................................................................................................... 20 About Java memory ................................ 9 Virtualization Jobs..................................... 7 Deploy Jobs .................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... 4 Compliance ........................................................................ 2 Understanding job behavior ...................................................................... 13 Simple installations ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
000 target hosts can create and schedule execution of possibly several thousand work items. called the job thread pool. Work items scheduled for execution are maintained in a work item queue in the job server. This section describes the overall operation of the framework.0. While it waits for a response from the remote target. with emphasis on computation. This resource utilization concern is addressed by the introduction of asynchronous tasks. a job that is scheduled to execute against 1. A work item may or may not be executed by the same job server that is responsible for executing the job that created it. Page 4 . This can present a potential resource issue. which maintains yet another thread pool. Some work items. It is in the execution of work items that the job carries out its responsibilities. otherwise. Currently. 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. on a target host. dedicated to executing jobs in the job queue. corresponding to different steps or stages of the job. threads from this pool manage lightweight work items. A work item thread assigned to such a work item blocks while it waits. an asynchronous BlExec task does not consume any thread resources. Jobs. Asynchronous BlExec tasks are managed by the BlExec service. If the lightweight work item thread pool is not empty (that is. instead of performing that remote operation and waiting for a response. however. having been introduced in BMC BladeLogic Server Automation version 8. Each job server maintains a pool of threads. In addition to the work item thread pool. storage. JOB EXECUTION FRAMEWORK All BMC BladeLogic Server Automation jobs execute in the job execution framework. as the work item thread is not available to service other work items with more active processing needs. a job may generate multiple work items for each target. Thus.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. Further. a work item thread is assigned exclusively to that work item. When a work item must perform a remote operation. work items are executed by job servers. all work items (lightweight and nonlightweight) are managed by the normal work item thread pool. the lightweight work item thread pool. Asynchronous BlExec tasks While a work item is executing. and network resource requirements. Work items are separately-schedulable units of work that are undertaken as part of the execution of a job. targets. known as work item threads. Asynchronous tasks are a relatively new feature of the job execution framework. or to a component on a target. Then the work item itself terminates. 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. but the tasks occupy a thread from the pool only when they have active processing to perform. for example. has a non-zero size). 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. spend much of their time waiting for results from operations being carried out remotely. Like jobs. A work item must be explicitly written to make use of asynchronous tasks. the work item can instead create and queue an asynchronous BlExec task to perform the operation. The main work of a job is the creation and management of individual work items and their results. each job server also maintains a separate thread pool for lightweight work items. some BMC BladeLogic Server Automation jobs are asynchronous task aware. and some are not. A work item is almost always bound to one target host. A pool of threads.
the next processing step takes place. repeated snapshots of an asset that changes very little or not at all result in relatively little information being stored in the database.bnp from that job run is still available on the job server. Version 8. Audit. capturing just the MD5 digest (checksum) of a file.0. Files are the most common type of asset used in Snapshot and Audit Jobs. To perform a full snapshot of a file.0.0 and later.bnp of the current snapshot of the asset and the .bnp file is obtained depends on the BMC BladeLogic Server Automation version.snp file.snp file. the next processing step takes place.bnp (baseline snapshot) representing the previous scan. On the other hand.bnp files (that is.snp file is completed on the Application Server. information about each asset is stored in a local (on the Application Server) file with a . As it is received by the Application Server. and a . Version 7. The table shows a summary of resource usage for Snapshot Jobs.snp file is constructed for each component part. the file’s content is received as a separate file and not included in the .bnp file from the prior snapshot). COMPLIANCE This section describes Snapshot.snp (snapshot) suffix. NSH Script jobs and patch analysis jobs take advantage of asynchronous BlExec tasks.6 and earlier Version 8. no additional data is recorded in the database. Snapshot Jobs Snapshot jobs collect information about assets from a target and convey that information to the Application Server. The lone exception to this rule is that when a file’s content is included in a snapshot.0. only the differences between the two versions are stored in the BMC BladeLogic Server Automation database.bnp file also remains on the job server.bnp file from the last scan of this particular target is available on the file server (see below).snp file. Otherwise. Therefore. the . in the case of an unchanged file. The . One .6 and earlier If the last scan of this particular target ran on the same job server and the old . Application Server CPU High Network Traffic High Database Load Moderate Agent Low Page 5 . it is then scanned and compared to the most recent prior snapshot from that target. the file is deleted). it is copied from the file server to the local Application Server and then used for comparison.1 The BlExec service and asynchronous BlExec tasks are not available earlier than BMC BladeLogic Server Automation 8. then the old . processing steps follow this flow: Only in version 7. This comparison is performed between the new . and rules-based Compliance Jobs. (In BMC BladeLogic Server Automation version 8. When construction of the .BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Version 7.6 and earlier After the snapshot job executes. the .bnp and copied to the file server. if one exists. After the comparison between the two . In BMC BladeLogic Server Automation 8. In BMC BladeLogic Server Automation 8.snp file is renamed to .6 and earlier Version 7. the entire contents of that file must be transferred to the Application Server. 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 8. Version7.1. For example. however.0.0 Version 8.bnp file as it would have existed following the last scan of this particular target. The exact means by which the .bnp file is used directly. The job server uses the data in the database to reconstruct a . instead of the actual contents. Otherwise. If the . Deploy jobs and Virtual Guest Jobs also take advantage of asynchronous BlExec tasks.
regardless of how many earlier audits may have detected the same difference. each target of the audit job is processed by first constructing a target . then each rule failure selects a BLPackage to be included in a combined remediation BLPackage for that host.snp files for that target are discarded. the relevant conditions are applied to determine compliance. Differences between the two . the asset from the target .snp files are copied to the file server. The result (compliant. When a Compliance Job runs. For example.bnp) on the Application Server.snp file is generated from data in the database.snp suffix this time). If it does need to retrieve assets for the current component part. Upon completion of the Audit Job. also called rule-based compliance jobs. master .snp or . but not the contents of the file. The table shows a summary of resource usage for Compliance Jobs that perform autoremediation. a single request is issued to collect the required information for each of the assets to be tested. After each audit target is processed. for each component part.snp files are marked for deletion on the file server. The master .snp files have been constructed. the specific value under test is also recorded in the database. (Any other hosts with the same combination of failing rules will use the same remediation package.snp files are recorded in the database. master . Compliance Jobs do not use temporary snapshot files (. Page 6 . and recording only the differences. For Audit Jobs. For each difference detected.snp files. Each suitable target is then contacted and sufficient assets collected to perform a test of the signature condition for the target. each work item operates by looping through the component parts of its assigned component. the master . in that it involves constructing and comparing two snapshot files on the Application Server (with a .BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Audit Jobs Audit Job behavior is largely similar to that of Snapshot Jobs. Compliance autoremediation If a target is noncompliant and if the Compliance Job has the Allow Auto-remediation option specified. a snapshot of the master target is performed and the results captured in . The Compliance Job does not complete until the BLPackage Deploy Job has completed. After the master . if necessary. As each requested asset arrives on the Application Server. Application Server CPU High Compliance Jobs Compliance jobs. For a snapshot-based audit. a non-complying condition on file size causes the actual file size to be recorded in the database. and shared among any Application Servers that run work items for the Audit Job.snp files are always constructed as part of the job.snp file is persisted in the database. The table shows a summary of resource usage for Audit Jobs. it decides whether or not it needs to retrieve data from the target. The table shows a summary of resource usage by Component Discovery Jobs. For live audits. noncompliant.) The Compliance Job then runs a BLPackage Deploy Job against the noncompliant targets. the target . In the case of a noncompliant result. or noncompliant with exception) of applying each condition is recorded in the database.snp file and then comparing the master and target . operate by: collecting asset information on the target transferring that data back to the Application Server applying the user-specified rules to the returned data to assess the target’s compliance Unlike Audit and Snapshot jobs.snp 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.
Issues with deadlock and hangs are resolved in release 8. the script running on the Application Server copies the file from its source to each target. the script running on the Application Server copies the file to one or more remote repeaters. The table shows a summary of resource usage by the Process Spawner. Page 7 . BMC does not recommend using the Process Spawner in these versions.1. users have the option of selecting asynchronous execution for Type 3 NSH Script Jobs.0 and later As of BMC BladeLogic Server Automation version 8. there is no direct data transfer between the source and the target.1 and later Prior to BMC BladeLogic Server Automation version 8.0. rather than on the Application Server. Process Spawner NSH Script Jobs invoke the actual NSH scripts in a separate process. The Application Server acts as an intermediary.nsh script to copy (push) the requested file. 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. That separate process can be created and managed either by the Application Server or by a separately-running application known as the Process Spawner. any nexec commands are executed on the target. see Asynchronous BlExec tasks on page 4. For an indirect File Deploy Job. Version 8. Use of the Process Spawner offers significant performance benefits for NSH Script jobs. Use of the Process Spawner can significantly reduce the overhead of creating and tearing down the process used to execute the NSH script. a script then runs on each repeater to push the file to the final target.1. File Deploy Jobs A File Deploy Job arranges to deploy a file from any NSH-accessible location to one or more remote targets. 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 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. Version 8. Application server CPU Varies Network Traffic Varies Database Load Low Agent Varies DEPLOY JOBS This section describes file and package deploy jobs.6 and earlier Version 8.0. Even for scripts executed on the Application Server however. Version 7. A File Deploy Job operates by first constructing and then executing an . For a direct File Deploy Job. Choosing this option causes the job to be executed using asynchronous BlExec tasks. with the Application Server again acting as an intermediary. This script runs on the Application Server. BMC recommends its use. passing the host list as a parameter (Type 4) From a performance perspective.
registry keys and configurations within files. presents almost no load to the BMC BladeLogic Server Automation infrastructure. these commands are executed on the remote target. for example. Undo If the deployment is unsuccessful. Execute Pre commands. as most of the work for this phase is carried out on the target hosts Page 8 . With the exception of work items for predeploy and postdeploy commands. page 4. These server objects are packaged together for unattended deployment on multiple remote hosts. 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. in contrast. no staging is required. any Repeaters involved can experience heavy load during a File Deploy Job. Version 8. presents almost no load to the BMC BladeLogic Server Automation infrastructure. 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). several phase work items have been enhanced to use asynchronous BLExec tasks for execution. The Commit phase.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. its effects are reverted on the target. 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.1. Notes Asynchronous BlExec task High file server load Lightweight Work Item Lightweight Work Item. not just files. See Lightweight work items.1 and later As of BMC BladeLogic Server Automation version 8. The Commit phase. if any. 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. Any necessary files are copied to the target in preparation for deployment. on the target. if any. The table shows a summary of resource usage by BLPackage Deploy Jobs. in contrast. Run installation commands on the target. BLPackage Deploy Jobs A BLPackage is an aggregation of many types of server objects. on the target. If the package uses the agent mounts source option. See Asynchronous BlExec tasks. The table shows a summary of resource usage by File Deploy Jobs. Commit Execute Post commands. on page 4. possibly by way of repeater servers. allowing for increased throughput even without populating the thread pool for lightweight work items. Similarly. including. 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.
The data store server may experience moderate to high load during provisioning. for initial booting instructions TFTP server. the install server (the data store) bears the greatest load. to identify a PXE server PXE server. from which it downloads a pre-boot kernel image. describing the patch and its applicability. containing the actual bits of the patch. The table shows a summary of resource usage by Provision Jobs. and a payload. for operating system installation files Generally speaking. 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. while installation files are served off an NFS server (data store). it requests progressive instructions from BMC BladeLogic servers and downloads boot images and operating system installation files from servers on the network. PATCHING JOBS In BladeLogic. Of the three functions. AIX provisioning The IBM AIX Network Installation Manager (NIM) technology uses a NIM master to control the provisioning target. none of these activities impose significant computational demands on the supporting servers. software patches released by a patch vendor (that is. The boot server must be on the same network as the provisioning target.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. but the network link between the target device and the data store server may experience substantial bandwidth usage. from which it retrieves the system package Data store. Red Hat. The device’s boot process varies. then the job monitors the progress of the provisioning activity as it occurs on the target. Provisioning details Windows and Linux provisioning Provisioning support for Windows and Linux devices is based on the Pre-Execution Environment (PXE) standard. Application Server. 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. in most cases. Page 9 . it requires network access to servers from which it can retrieve instructions and downloadable artifacts. a Windows or Linux target contacts the following: DHCP server. but in all cases. as the target device is rebooting. depending on the type of target device. or combined into one or two actual JumpStart servers. When booting under the control of a provisioning job. As the target device reboots. 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. Microsoft.
That is. Application Server CPU High Patch Analysis Jobs On all supported platforms as of BMC BladeLogic Server Automation version 8. patch analysis for Solaris now occurs on the target. Based on the patch analysis results. For example. patch analysis processing takes place on the affected target.0.0. This can present a moderate to high work load on the Application Server. Version 8. which typically mounts removable storage media onto which patch information is already loaded.0. where it is decoded. the patch remediation job runs an algorithm that creates a set of BLPackages and BLPackage Deploy Jobs. Version 7. So you can create a Windows patch catalog with all Windows 2008 patches and only download payloads of the patches that are found missing. If a repository is to include Windows patches. Further. If multiple servers have the same set of missing patches. patch analysis for Solaris was performed primarily on the Application Server. Application server CPU Low* Network Traffic Low Database Load Low Agent Moderate – High* *See version-specific notes.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Patches are stored in a repository in the computing environment. Catalog Update Jobs You can create Catalog Update Jobs for each type of patch repository. the catalog for Windows patches is separate from the catalog for Red Hat patches. For Windows and Solaris. the patch remediation job creates a single Deploy Job with BLPackages that target the servers. for Solaris patch analysis. according to filters defined in BladeLogic. Red Hat requires a payload download. rather than on the target. the Application Server must be configured to allow traffic to pass through any firewalls and web proxy servers). 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.0. Online patch catalogs are updated by downloading additional content from vendor and/or metadata-provider websites. The table shows a summary of resource usage by Catalog Update Jobs. above. you can run analysis with just the metadata. without downloading the payload. The Application Server running a catalog update job for an online repository requires web access to these sites (that is. Offline patch catalogs are updated by transferring content from a local server. the relevant metadata (typically less than 5 MB) is transferred from the repository to the target agent. patch analysis for all target types now uses an asynchronous agent call.1 and later Prior to BMC BladeLogic Server Automation version 8. 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. 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. 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. and the Application Server is running on a Linux host.6 and earlier Version 8. Patches are organized into patch catalogs. Network Traffic High Database Load Moderate Agent Low The table shows a summary of resource usage by Catalog Update Jobs. then you must identify a Windows Helper Server Location when you create the repository. If different Page 10 . the target agent then performs the necessary calculation to determine which patches to install on the target. allowing greater concurrency on the Application Server. which is an NSH-accessible directory somewhere in the BladeLogic environment.
Application Server CPU Very Low Network Traffic Low Database Load Low Agent Low Virtual Guest Jobs make demands on the Virtual Center host to accomplish construction of the virtual guest. The BLPackage Deploy Jobs are wrapped into a Batch Job. which may experience heavy workload during the Staging phase of deployment. from a known VCenter or other virtual infrastructure. Application Server CPU Low – Moderate UCS Provisioning Jobs A Cisco Unified Computing System (UCS) chassis comprises a number of hardware blades which act as a pool of computing resources. For some steps in its operation. and storage connectivity resources. Network Traffic Moderate Database Load Low – Moderate Agent Low Page 11 . The Batch Job then executes immediately (if specified). a Virtual Guest Job communicates with the VCenter through a custom object (CO) that must be installed on the Virtual Center host. 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. above. Internally. so the behavior and resource demands of a Virtual Guest Job correspond to those of the Deploy Job. Configuration decisions for the new virtual guest are captured in a Virtual Guest Package. The table shows a summary of resource usage by Virtual Guest Jobs. VIRTUALIZATION JOBS Virtual Guest Job A Virtual Guest Job constructs a virtual guest. Virtual Infrastructure Discovery Job Also called a sprawl job. The chassis also includes a hardware entity (the Fabric Interconnect) that manages all the computing. the patch remediation job creates a Deploy Job for each unique set of missing patches. or is scheduled to execute at a later time. The BladeLogic UCS custom object (CO) communicates with this hardware entity. and then provisions the server. The table shows a summary of resource usage by UCS Provisioning Jobs. with or without an operating system. and storage configurations (WWNN and WWPN). network. Virtual Guest Jobs require minimal Application Server resources. networking configuration. This template contains server identity information (MAC address). applies the template to a stateless blade (so that the blade becomes a server with an identity). 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. Patch resources are stored in the patch repository. A UCS template is a configuration that contains settings to configure a blade to become a server.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration servers have different patches missing. Application server CPU Low Network Traffic High Database Load Low Agent Low See BLPackage Deploy Job. The UCS Provisioning Job takes a predefined template. for more information about the resource demands of the deploy operations.
an ACL Push Job computes a set of entries for the user file on each target. Application Server CPU Low ACL Push Jobs At its core. and then overwrites the user file (the file in the target’s rsc directory whose name is ‘user’) with those entries. Application Server CPU Low Network Traffic Low Database Load Low Agent Low Page 12 . IP address. Application Server CPU Low Network Traffic Low Database Load Low Agent Low Network Traffic Low Database Load Low Agent Low Distribute Configuration Objects Jobs The table shows a summary of resource usage by Distribute Configuration Objects Jobs. operating system type and version. 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 – Moderate Database Load Low Agent Low – Moderate Decommission Configuration Object Jobs The table shows a summary of resource usage by Decommission Configuration Object Jobs. The table shows a summary of resource usage by Update Server Properties Jobs. The table shows a summary of resource usage by ACL Push Jobs. etc.
Database server At the center of every BMC BladeLogic Server Automation installation is the BMC BladeLogic database server. in a virtualized environment. BMC recommends the use of a dedicated physical machine or cluster to host the database server for BladeLogic. on page 17. A configuration server provides middle-tier functionality. answering requests from BMC BladeLogic Server Automation client applications both for data and for operations on that data. 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. or combinations of profiles. An Application Server can fulfill any of several distinct profiles. Alternatively. High latency on the link between the Application Servers and the database server can cause unacceptable performance for BladeLogic. Within limits. surprisingly. job servers are limited by internal resource contention. For more information. Page 13 . BLCLI command line client. see Adding Application Server instances. as described in NSH proxies. you can run multiple job server guest VMs on the same physical server. it is acceptable to run multiple Application Servers on a single physical server while still maintaining acceptable performance. including the number of targets to be managed and the expected job load for the system.exe) connect to configuration servers to allow interaction with the BladeLogic system. BMC BLADELOGIC SERVER AUTOMATION COMPONENTS This section describes the components that may constitute a BMC BladeLogic Server Automation installation. but. there is anecdotal evidence that high packet loss rates on the Application-Server-to-database link may cause issues for (expose defects in) the Oracle JDBC driver. The number and configuration of Application Servers in a deployment depends on many factors. depending on its configuration. bmi.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration DEPLOYMENT GUIDANCE A BMC BladeLogic Server Automation deployment typically involves a large number of individual software elements arrayed across a number of physical servers deployed around the environment. Application Servers are tightly coupled to the database and impose significant demands on the server that hosts the database. In many environments. Job servers Application Servers configured as job servers are responsible for the execution of BMC BladeLogic Server Automation jobs. Application Servers A BMC BladeLogic Server Automation deployment comprises one or more Application Server (appserver) processes. A configuration (UI) server is an Application Server of type CONFIGURATION of type ALL (which includes CONFIGURATION). Accordingly. The database server or cluster should be on the same LAN as the BMC BladeLogic Server Automation Application Server. NSH Proxy Servers NSH Proxy Servers perform a specialized role in BladeLogic installations. Configuration servers BMC BladeLogic Server Automation clients (rich client UI. page 16. This section discusses performance and other considerations for the deployment of the various BMC BladeLogic Server Automation software elements. Additionally. do not impose excessive workload on the hardware.
Servers for provisioning BMC BladeLogic Server Automation provisioning works with different provisioning technologies. In this configuration. localhost should be designated as the file server. A typical practice is to configure one of the configuration Application Servers also to act as an authentication server. Using NFS as a file server Because NFS sharing provides higher performance than NSH data transfer. Authentication servers do not normally experience a high work load. Authentication servers Although not a separate Application Server profile. BMC recommends running the console on a Citrix Presentation Server. but performance under that configuration may be unacceptable. BMC recommends deploying consoles to servers on the same LAN as the Application Servers to which they connect. depending on the type of server being provisioned. after which the user is allowed to interact with the BladeLogic client. Properly configured. page 14. PXE servers are discussed in Servers for provisioning. performs a specialized role in support of provisioning jobs. technically a specially configured Application Server. at least one Application Server in a BMC BladeLogic Server Automation environment must be configured as an authentication server. See Process Spawner considerations. PXE servers A BMC BladeLogic Server Automation PXE server. As its name implies. so that each Application Server treats the shared mount point as local storage. but not recommended.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. page 24. File server Every BMC BladeLogic Server Automation environment includes a server designated as the file server. It is possible. a repeater serves as a staging location at each site for packages as they are deployed. the authentication server verifies the identity of a BMC BladeLogic Server Automation user. For environments in which a population of geographically-dispersed users must all have access to the BMC BladeLogic Server Automation console. It is not normally necessary to configure more than one authentication server for a single BladeLogic environment. 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. for the console and Application Server to be separated by a longer network link. Repeaters For environments in which deploy job performance over the WAN is a concern. Advanced Repeaters An Advanced Repeater server is simply a repeater that uses BMC BladeLogic Advanced Repeater technology to enable file servers and repeater servers to store and share data more efficiently. BMC 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. Page 14 . This allows users who are offsite from the presentation server to run remote instances of the UI without experiencing excessive latency. BMC BladeLogic Server Automation consoles Communication between the BMC BladeLogic Server Automation console and Application Servers requires significant bandwidth. Any server running an RSCD agent can be designated as the file server for the installation. BMC recommends the use of one or more repeaters at each data center.
Page 15 . but may be remote from the BMC BladeLogic Server Automation Application Server. if the provisioning target will be retrieving files from a data store. It is therefore acceptable to install geographically-removed PXE servers. Although PXE servers do communicate with the database.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. all of which may be (and commonly are) hosted on the same physical device. The PXE server and the TFTP server must reside on the same physical server. Solaris provisioning The Oracle Solaris JumpStart technology identifies a JumpStart boot server. A provisioning target also needs access to the BladeLogic Application Server and a data store. However. AIX provisioning The IBM AIX NIM technology requires a NIM Master server on the same LAN as the AIX servers being provisioned. so it is not necessary for the Application Server to be geographically proximate to the provisioning target. which must communicate with the database over longer network legs. it is preferable that the data store be local to the provisioning target. To use a JumpStart server with provisioning jobs. the data volume of that communication is relatively low. To use a NIM Master with provisioning jobs. JumpStart servers should be located on the same LAN as the Solaris servers being provisioned. you must install an RSCD agent on the NIM Master server. Each target device needs to have access to a local PXE server. usually on the same LAN. and a JumpStart install server. Traffic to the Application Server is relatively light. you must install an RSCD agent on the JumpStart server. a JumpStart config server.
usually over port 4750. BMC recommends a dedicated database server or cluster to support a BMC BladeLogic Server Automation installation. NSH proxy servers played an important role in negotiating fire walls in large scale deployments. See also Large-Scale installations on page 17. NSH proxies are used mainly as a security enhancement measure. but this practice is no longer recommended.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. 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. In this situation. for example) or otherwise not directly accessible from the Application Servers. 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. rather than contacting the remote hosts directly. Proxies NSH proxies Historically. SIMPLE INSTALLATIONS This section describes basic considerations applicable to all BMC BladeLogic Server Automation installations. and Geographically-distributed installations.x and later. page 19. Configure the Application Server to establish communications with the remote targets by using the SOCKS proxy. In BMC BladeLogic Server Automation versions 7. One computer is dedicated to hosting the database. for additional considerations. Page 16 . 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. To use an Ignite Master with provisioning jobs. 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. SOCKS proxies To access targets that are behind a firewall (because they are in a remote data center. Accordingly.
Increasing job throughput To execute more jobs against more targets in a given period of time. it is usually necessary to increase the number of work item threads (WITs) available to execute jobs. adding WITs means configuring another Application Server. It is frequently the case that a physical server has CPU and other resources sufficient to host several times the total number of WITs that can be run in a single Application Server. 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). See Configuration guidance on page 20 for more detailed suggestions on memory and WIT settings for job servers. including the database server. doing so is likely to lead to unacceptable performance in most cases. In most cases. In figuring required RAM for the physical server. it is likely that additional Application Servers will need to be deployed. This section describes the use of additional infrastructure to provide greater capacity for a BMC BladeLogic Server Automation installation. Page 17 . a typical eight-core server computer with sufficient memory can support three to four Application Servers. Under these guidelines. it may also be necessary to deploy additional Configuration (UI) servers to support a larger user population. In some cases. then. including the Application Server launcher. you can add BMC BladeLogic Server Automation components to provide greater management capacity. Fortunately.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration For demonstration or other specialized purpose. remember to allow memory for the operating system and for other processes running on the computer. Most commonly it is necessary to add job servers to provide support for a larger number of managed servers. it is possible to host all the components on one machine. LARGE-SCALE INSTALLATIONS Most customer environments are too large to be managed by the simple 2-server infrastructure described in the previous section. but the number of WITs per job server is normally limited by the amount of memory available in a single Application Server. Adding Application Server instances To meet the demands of a larger data center. The number of WITs is a configurable option of each job server.
Load balancing In large deployments involving multiple instances of some or all BMC BladeLogic Server Automation components. in the absence of additional information. 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 the total number of Application Servers a particular BMC BladeLogic Server Automation implementation can support. scheduling jobs and work items according to availability. these guidelines call for one Configuration server for every 250 users. In both cases. If you plan to establish an extremely large BMC BladeLogic Server Automation implementation.pdf . Considerations for virtualized environments When BladeLogic Application Servers are hosted in virtual (guest) machines in a virtualized environment. or spread the Application Servers across separate virtual machines. the choice naturally arises whether it is better to deploy multiple Application Servers in a single virtual machine. allowing for redundancy and higher performance. a share exported by the filer is mounted at the same mount point on each computer hosting an Application Server. the Application Servers themselves are likely running on the same physical host computer. http://documents. and BMC BladeLogic 8. In combination. it may be necessary to provide load balancing services to ensure that the extra resources being applied are being utilized appropriately.pdf. See BMC BladeLogic Application Server Running on VMware ESX: Performance and Scalability Best Practices.bmc. Limits to growth Neither Oracle nor SQL Server has a theoretical limit on the number of database connections that a database server can support. In virtualized environments. avoid allocating more vCPUs than the physical host has physical CPU cores. Then work with the local DBA and database vendor to ensure that the database server is capable of supporting that load. of course. A NAS filer using NFS or SMB can act as a kind of virtual file server.bmc. http://documents. the Application Server performs best when the virtual machine hosting it is configured to have one dedicated virtual CPU (vCPU). Expect as many as 20% of total users to be logged in at any one time. In addition. No additional load balancing considerations are applicable for job servers. Further. in turn. you should use the information in the Configuration Guidance section to estimate the total number of database connections required for the implementation.com/supportu/documents/29/84/142984/142984. you may need to increase the number of Configuration (UI) Servers in the installation. The File Server is simply a server running the RSCD agent. The workload required to support a user varies widely. making the share appear to be local storage for each Application Server. Page 18 .com/supportu/documents/60/54/106054/106054. and the file storage path is that on which the shared storage is mounted. Scaling the file server The BMC BladeLogic Server Automation design requires a designated File Server to host the files in the BladeLogic Depot. a configuration offering several benefits in terms of performance and scalability. In addition. The File Server is then defined to be localhost. Job servers effectively perform their own load balancing.0 Application Server Running on Red Hat Xen: Performance and Scalability Best Practices. This. BMC recommends deploying Application Servers in separate virtual machines.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Support for more users For environments supporting a large user population. In this configuration. for best performance. You can control the minimum and maximum number of database connections maintained by an Application Server through user-configurable settings for the various database connection pools. However. this configuration allows the use of clustered NAS servers. BMC typically recommends: Install one Configuration server for every 50 concurrent logged-in users. 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. but as a starting point.
This section describes additional infrastructure recommended for managing servers in remote data centers. for purposes of failover) must similarly be provided by an external load balancer. Page 19 . the installation also requires access to BMC BladeLogic Server Automation for remote users. Repeaters You can configure repeaters as staging areas for deployment files. For more homogeneous load balancing. In these cases it is necessary to consider not just the scale of the BMC BladeLogic Server Automation installation but also its geographic distribution. Deploy Jobs with targets in remote data centers should normally be configured to use indirect push staging. SOCKS proxies For a remote data center accessible only through a firewall. for example DHCP.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. such as bandwidth throttling and secure communications. the RSCD agent port). GEOGRAPHICALLY-DISTRIBUTED INSTALLATIONS For a variety of reasons. Depending on the provisioning technology used. support for provisioning targets in remote data centers must be provided from provisioning servers located in the remote data center. BMC recommends the use of a Citrix Presentation Server. with at least one repeater configured in each remote data center. Advanced repeaters also offer additional features. which then brokers a connection to the actual target server agent (on port 4750. BMC recommends the use of advanced repeaters for geographically-distributed deployments. The BIG-IP product by F5 is a common choice for this purpose. each remote data center must provide support for one or more provisioning-related services. that may be important for large-scale installations. Citrix Presentation Server If. Appropriate use of repeaters in remote data centers can significantly reduce the amount of network traffic that must be carried over long (slow and/or expensive) data lines. (This staging pushes to the repeater and then pushes from the repeater to the target. in addition to remote managed servers. The firewall can be configured to route connections on port 1080 (the SOCKS proxy port) to the SOCKS Proxy Server.) Provisioning servers As a rule. it is unusual for the largest customer environments to be entirely contained within a single data center. PXE and TFTP servers. due to the bandwidth and latency requirements for the console-to-configuration server link. The BMC BladeLogic Advanced Repeater is an enhancement to the repeater architecture that provides scalable transport of data over wide-area networks. Load balancing for authentication servers (for example. For performance reasons. it is usually not practical to deploy a management console (BMC BladeLogic Server Automation console) at a remote site. you can achieve a crude but effective load balancing simply by assigning different users to use different configuration servers. BMC recommends the use of a SOCKS proxy in the remote data center. you must add an external load balancer to the installation and use it to distribute the load across configuration servers.
For large Java applications like Application Servers. and native heap A Java process comprises two distinct memory areas: the Java heap and the native heap. this process space limit imposes a ceiling on the number of threads that can be accommodated within a single Application Server. Java heap. typically 50% or more larger than the 32-bit Java process. Compared to a 32-bit Java process performing equivalent work. The Java heap is managed by the Java garbage collector. from which the operating system must reserve a significant portion for itself. For example. For an example. especially out-of-memory errors. If the maximum Java heap size is set too low. Refer to the BMC BLADE L OGIC SERVER AUTOMATION ADMINISTRATION GUIDE for details on using the blasadmin tool to control the configuration parameters. Both heaps. and so is sometimes called GC heap. peak memory use for either the Java heap or the native heap depends on the precise work load being considered. it is possible to run out of native heap memory. a 64-bit Java process also requires a larger Java heap. The native heap (also sometimes called the C heap) contains thread stacks. The java heap contains Java objects and accounts for most of the memory required by a running Application Server. allowing an application process only 2 GB total private process space.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. ABOUT JAVA MEMORY Effective operation of a large Java system like the BladeLogic Application Server depends critically on the availability of sufficient heap memory. this section organizes BMC configuration recommendations according to type for single-purpose Application Servers.ugent. not guarantees or absolute limits. see http://users. Process space. as well as timing effects between concurrently-operating threads. you must modify the parameter recommendations. it is possible to run out of Java heap memory. 32-bit processes A process running under any 32-bit operating system is limited to 4 GB of virtual address space.be/~leeckhou/papers/SPE06. must fit within the footprint of a single process. 64-bit processes A process running under a 64-bit operating system has access to a much larger virtual address space. In this case. of course. Apart from some general discussion. Recommended Java heap settings This section describes recommended Java heap sizes for Application Servers running under different operating systems. 32-bit Windows divides the entire address space in half. These are recommendations only and must be adjusted in light of observed conditions. This section provides an overview of some considerations that apply to correctly sizing Java memory for BladeLogic. If the maximum Java heap size is set too high. Therefore. the recommendations that follow are merely that: recommendations. 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. Page 20 . An Application Server can.elis. file handles.pdf. be configured to provide the combined services of the single-purpose Application Server (an Application Server of type ALL). To complicate matters further. together with the Java executable code itself. usually by adding recommended values for the same parameter for different Application Server types. and other objects not managed by the Java garbage collector.
As the number of threads in a process grows. increasing the number of threads is subject to diminishing returns. with each pool devoted to a different purpose. any given item request from any thread is more likely to be fulfilled from the cache. that is. Each thread consumes resources. a thread consumes even more memory. although BMC recommends leaving the minimum value at zero for all connection pools. For 64-bit processes. sometimes sharply so. Each additional thread provides a smaller and smaller net benefit. Page 21 . Threads within the same process share certain data structures. if there is sufficient physical memory to support this setting. ABOUT DATABASE CONNECTIONS Connections between an Application Server and the database are managed in three connection pools. especially caches. blasadmin Setting Module AppServer Setting MaxHeapSize Description and Recommendation Specifies the maximum heap size for this Application Server. Selecting appropriate sizes for each of the various thread pools is one of the most important configuration choices for an Application Server. available process size limits the number of threads available in an Application Server. Doubling the number of threads in a pool improves performance. but doesn’t double it. the negative contention effects grow more rapidly than do the positive serendipity effects. even when idle. This effect degrades per-thread performance as the number of threads increases. This phenomenon has a mildly positive effect on overall performance as the number of threads increases. See operating system-specific recommendations for this value summarized in the table below. Due to memory constraints. there is a greater likelihood of one thread having to wait for another thread’s exclusive access to conclude. job servers using 32-bit processes should be configured to use no more than 50 work item threads. which are not shared between threads in different processes. Contention: Because some operations on some data structures require exclusive access. While executing.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration For 32-bit processes. Regardless of additional performance considerations. Java threads may also consume operating system resources such as thread handles. while still consuming as much memory and other resources as any other thread. Max Java Heap Recommendations Operating System Windows Linux Solaris 32-bit 1024 MB 1536 MB 2048 MB 64-bit 6144 MB 6144 MB Not applicable ABOUT THREAD POOLS An Application Server maintains several thread pools. as the number of threads increases. especially memory. because another thread is more likely to have already placed the element in the cache. especially threads within a particular thread pool. has two consequences: Serendipity: Because there are more threads contributing to the process-wide caches. Each connection pool allows the configuration of a minimum and maximum number of connections. BMC recommends operating system-specific Java heap size values according to the table below. each dedicated to a specific purpose. BMC recommends that the Java heap size be increased as indicated in the table. Increasing the number of threads within a single process.
BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Configuring a database pool’s maximum size to be too high wastes resources. BMC recommends establishing additional Application Servers instead of increasing the number of work item threads. However. selecting the best size for this thread pool involves trade-offs. so a job targeted at thousands of servers can be expected to result in thousands of work items being queued for processing. You must also ensure that the database server has sufficient capacity to service all the connections from all the connection pools for all the Application Servers in the environment. may risk exceeding the total capacity of the database server. it is usually desirable to allocate a generous number of work item threads for a job server. RECOMMENDATIONS FOR JOB SERVERS This section provides general recommendations for configuring Application Servers established as job servers. Conversely. Version 8. Page 22 .6 and earlier. BMC recommends a value up to 200 if Deploy Jobs are a primary use. otherwise 0. In light of these considerations. BMC recommends working with the DBA and database vendor to ensure that you have this capacity. For 64-bit Application Servers. Version 8. Recommendations for the lightweight work item thread pool Lightweight work item threads are of benefit primarily for Deploy Jobs. The number of work item threads to configure is primarily determined by the effects of contention between work item threads.1 Up through BMC BladeLogic Server Automation 8.1. and for large installations. for parallelism. and the best size will be different for different environments. the work items themselves tend not to be CPU intensive. BMC recommends 50 work item threads for each of these Application Servers. lightweight or not. BMC recommends a setting of 50 work item threads. BMC recommends 50 work item threads for both 32-bit and 64-bit Application Servers. Further. Version 7. larger available process spaces make it possible to use a larger number of work item threads. For 32-bit Application Servers. 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. Most jobs generate one or more work items per target host. as a thread requesting a database connection from an empty connection pool blocks until a connection becomes available. particularly for very large installations. BMC suggests a value of 200 threads for lightweight work items.0. The default value of 0 threads for lightweight work items uses ordinary work item threads for the execution of all work items. configuring a database pool with a maximum size that is too low can degrade performance. blasadmin Setting Module AppServer Setting MaxLightweightWorkItem Threads Description and Recommended Value Number of threads that can be used to execute lightweight job parts. blasadmin Setting Module AppServer Setting MaxWorkItemThreads Description and Recommended Value Number of threads that can be used to execute job parts. Configuring a larger number of work item threads risks an OutOfMemoryError under the process size limitations of 32-bit processes. For installations in which Deploy Jobs represent a significant fraction of the workload. for parallelism.
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. Rather. a lower value reduces the demand for file descriptors. BlExec MaxSocketConnections Maximum simultaneous sockets open by the BlExec service. remains the responsibility of the job itself. Maximum size for the job execution pool. and will be carried out by the job execution pool. for parallelism. The maximum number of jobs the Application Server allows to run simultaneously. While most of the work involved in executing a job is delegated to work items. BlExec NumWorkerThreads Number of worker threads used by the BlExec service. BMC recommends using the default value of 500 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. when that option is selected. blasadmin Setting Module AppServer Setting MaxApprovalThreads Description Number of Approval Threads. AppServer MaxJobs Maximum number of jobs the Application Server can execute simultaneously. AppServer MaxJobThreads Maximum number of threads that can be used to execute a job. it is the default value that appears in the UI for a job’s maximum parallelism option. Other parameters For completeness. Deploy Jobs. The job execution pool is distinct from the work item thread pool. blasadmin Setting Module AppServer Setting EnableAsyncExecution Description and Recommended Value Enables/disables the async execution framework for jobs that allow it. These configuration parameters do not normally require adjustment from their default values. such as creating the work items themselves. regardless of the availability of resources to execute the jobs. This parameter has no direct effect on the operation of the Application Server. for example. the default values produce good results in most cases. some of the work. this section describes some additional configuration parameters related to thread pool sizes for job servers. Page 23 . JobFactory GlobalDefaultJobParallelism Global default value for Job Parallelism made available to user. BMC recommends using the default value of 20. This parameter governs a small pool of threads used to communicate with BMC Atrium Orchestrator. A higher value allows more simultaneous connections. BMC recommends leaving async execution enabled.
6 and earlier. blasadmin Setting Module ProcessSpawner Setting SpawnExternally Description and Recommendation Processes should be spawned outside the Application Server or not. For version 8. For NSH script jobs. 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. Version 8. Version 7. while other jobs use the job execution database connection pool.1 and beyond.1 and later. BMC recommends a value of 2 * MaxWorkItemThreads. The BLCLI client uses exactly one client connection for its execution. blasadmin Setting Module Database Setting MaxJobExecutionConnections Description and Recommended Value Maximum connections in the pool for job execution thread group. the benefit of using the Process Spawner increases. This value is the total of the number of client connections from UI clients (RCP) and from BLCLI clients.0 and earlier. 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.0. 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. For BMC BladeLogic Server Automation version 8.0 Up through BMC BladeLogic Server Automation 8. As an initial estimate. BMC recommends using the Process Spawner for all job servers for BMC BladeLogic Server Automation version 8. rather than spawning them directly. the default value should be adequate. For best performance of NSH script jobs in these versions of BladeLogic.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Recommendations for database connections For best job server performance. 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. Process Spawner considerations As memory size increases. Page 24 .5 client connections for each concurrent GUI user. 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. and is usually much more short-lived than an interactive user’s GUI session. As the configured size of the Application Server grows. 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. BMC recommends a value that is twice the number of work item threads (MaxWorkItemThreads). logging of output from NSH script jobs is handled with connections from the general database connection pool.
In most cases.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Thus. BMC recommends estimating peak client connection demand. BMC recommends using the default value of 10. or approximately 5% of the value of MaxClientContexts. BMC recommends a value that is twice the number of client connection threads. blasadmin Setting Module AppServer Setting MaxClientContexts Description and Recommended Value Number of maximum client connections to the Application Server.5 * (number of simultaneous GUI users) + (number of simultaneous BLCLI commands) If multiple configuration servers with a load balancer will be established. BMC recommends using the default value of 200. and setting MaxClientContexts to this value. 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). blasadmin Setting Module Database Setting MaxClientConnections Description and Recommended Value Maximum connections in the pool for client connections. as described in the previous section. 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. The client connection service maintains a pool of threads for servicing client requests. Page 25 . In the absence of sufficient information from which to form an estimate for peak client connection demand. for best configuration (UI) server performance. Recommendations for database connections Similarly. the peak demand estimate for client connections for the configuration server is: 2. then the total load for client connections can be divided across the number of configuration servers that will be established. AppServer MaxWorkerThreads Number of client connection worker threads. it is not necessary to change these parameters from their default values.
Page 26 . AppServer MaxNshProxyThreads Number of NSH proxy threads. blasadmin Setting Module AppServer Setting MaxNshProxyContexts Description and Recommended Value Maximum number of NSH proxy connections to the Application Server. For an Application Server configured to act exclusively as an NSH proxy server. Set this value to the maximum number of concurrent NSH connections the proxy will be expected to handle. this value should be the sum of MaxWorkerThreads and MaxNshProxyThreads. to account for idle NSH connections. BMC suggests an initial estimate of 20% of MaxNshProxyContexts. This value can be significantly less than MaxNshProxyContexts. this value should be the same as MaxNshProxyThreads. For an Application Server configured to act as both a configuration server and an NSH proxy server. configure the NSH Proxy server for the anticipated number of concurrent NSH connections it will be expected to handle.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. Database MaxClientConnections Maximum connections in the pool for client connections. In the absence of usage estimates specific to the installation. For best performance.
PXE Server binds to 67 UDP. File Server Page 27 . By default. Extended DHCP response to an initial extended DHCP request 68 69 80 80 161 162 443 445 1080 1433 1433 1433 1521 1521 1521 4011 4750 DHCP (UDP) TFTP (TCP/UDP) HTTP (TCP) HTTP (TCP) SNMP (UDP) SNMP (UDP) HTTPS (TCP) SMB (TCP) TCP MS-SQL (TCP) MS-SQL (TCP) MS-SQL (TCP) TNS (TCP) TNS (TCP) TNS (TCP) DHCP (UDP) RSCD (TCP) DHCP PXE client HTTP client PXE client Application Server Application Server HTTPS client PXE client SOCKS client Application Server BDSSA server PXE Server Application Server BDSSA server PXE Server PXE client Application Server Advanced Repeater PXE client TFTP Server BDSSA server PXE Server HTTP.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. 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. used for Windows PXE Servers SOCKS Proxy protocol 5282 HTTP (TCP) Adv.
Repeater BMCCM Tuner Adv. Server Application Server Launcher Launcher Launcher Application Server RMI Registry SSL Provisioning (user guide p. File Server are not co-located usually local traffic only usually local traffic only usually local traffic only usually local traffic only Cognos report BladeLogic SSO JMX listener -. with 9800 being the default base port. File Server Notes Marimba publishing -. 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.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Port 7717 Protocol TCP From File Server To Adv. Arbitrary port assignments can be made in all cases. with 9850-9899 being the default for a single Application Server. Application Server Application Server Auth. Page 28 . 853. File Server Adv. and so on. A second Application Server on the same host will typically have a base port of 9900.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. steps 7 and 9) 9838 (base+38*) 9840 (base+40*) 9840 (base+40*) 9841 (base+41*) 9842 (base+42*) 9850-9899 (MinPortMaxPort**) TCP TCP TCP TCP TCP Jconsole Application Server RCP (Client UI) RCP (Client UI) NSH. Repeater Cognos client BDSSA server BLASAdmin console Application Server Console Provisioning Client Application Server Adv. ** The MinPort-MaxPort range is configurable.if the File Server and Adv. Service Auth. Repeater BDSSA server BDSSA Auth.
and the BMC Software logo are the exclusive properties of BMC Software. faster and stronger. service marks. 2010. *195833* Page 29 . are registered with the U. or both.S. reduce risk and drive business profit. Inc.S. BMC offers a comprehensive approach and unified platform that helps IT organizations cut cost. AIX and IBM are trademarks or registered trademarks of International Business Machines Corporation in the United States. Linux is the registered trademark of Linus Torvalds. All other trademarks or registered trademarks are the property of their respective owners. Patent and Trademark Office.com for more information. Business thrives when IT runs smarter. Other names may be trademarks of their respective owners.S. All other BMC trademarks. virtual and cloud environments. All rights reserved. For the four fiscal quarters ended September 30.bmc. UNIX is the registered trademark of The Open Group in the U. mainframe. and other countries. Oracle and Java are registered trademarks of Oracle and/or its affiliates. IT runs on BMC Software. BMC revenue was approximately $1. other countries. © 2011 BMC Software. BMC. and may be registered or pending registration in other countries. and logos may be registered or pending registration in the U.96 billion. or in other countries. Recognized as the leader in Business Service Management.BMC BladeLogic Server Automation Best Practices for for Deployment and Configuration Business runs on IT. Inc. Visit www.. That’s why the most demanding IT organizations in the world rely on BMC Software across distributed. BMC Software.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.