BMC BladeLogic Server. Automation User Guide. Supporting. Version of BMC BladeLogic Server Automation. February BMC Server Automation Sizing Guide ; Main Documentation (by version): .. BladeLogic Customer Portal; User Contributed topics (lots of. If the ready-made PDFs of this space do not satisfy your requirements, you can export a custom PDF. Downloading the installation files. Page.
|Genre:||Health and Food|
|Published (Last):||5 March 2006|
|PDF File Size:||18.85 Mb|
|ePub File Size:||20.1 Mb|
|Price:||Free* [*Free Regsitration Required]|
Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U. All other trademarks or registered trademarks are the property of their respective owners.
Linux is the registered trademark of Linus Torvalds. Other names may be trademarks of their respective owners. The information included in this documentation is the proprietary and confidential information of BMC Software, Inc. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation.
Restricted rights legend U. Government Restricted Rights to Computer Software. Use, duplication, or disclosure of any data and computer software by the U. Any contract notices should be sent to this address. To expedite your inquiry, see Before contacting BMC.
Support website You can obtain technical support from BMC 24 hours a day, 7 days a week at From this website, you can read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation download products and maintenance report an issue or ask a question subscribe to receive proactive alerts when new product notices are released find worldwide BMC support center locations and contact information, including addresses, fax numbers, and telephone numbers Support by telephone or In the United States and Canada, if you need technical support and do not have access to the web, call or send an message to In the subject line, enter SupID: Outside the United States and Canada, contact your local support center for assistance.
Before contacting BMC Have the following information available so that Customer Support can begin working on your issue immediately: Determining the database insertion rate Issue 2: Determining the volume of log entries generated Issue 3: Controlling the queue size on the transmitter Issue 4: Controlling the size of the database table Part 2 Installation 47 Chapter 4 Installation overview 49 About the product architecture Contents 5. Chapter 16 Preparing for the upgrade Supported upgrade paths Overview of the upgrade process Creating a test environment Verifying that you can log in as a primary administrator Backing up workspaces and databases Preparing for the transmitter upgrades Preparing for database schema upgrade Disk space requirements Preparing for the Report Center upgrade Preparing for the Patch Management upgrade Verifying disk space Saving patch edits Printing repository and Patch Service configuration settings Changing the update schedules Archiving the channels Upgrading channels from an earlier release What s next?
Chapter 17 Upgrading transmitters and proxies Upgrade order Prerequisites Upgrading the master transmitter and its tuner Upgrading mirror transmitters Upgrading a few mirrors Upgrading many mirrors Upgrading repeater transmitters Upgrading a few repeaters Upgrading many repeaters Upgrading proxies Upgrading a few proxies Upgrading many proxies What s next?
This chapter presents the following topics: Administrators use the CMS console to manage software changes, manage content changes, configure endpoints, and collect inventory information. You use the CMS console to configure most components. Master distribution server transmitter The master distribution server also known as the master transmitter in a BMC BladeLogic Client Automation infrastructure functions like a web server, except that instead of serving web pages, it serves applications and content that are packaged into channels.
The channel format enables cross-platform support and byte-level updates to software and content. Because the transmitter hosts all the content and applications that you distribute to endpoints, it is the heart of your BMC BladeLogic Client Automation infrastructure. Mirrors Mirrors and repeaters are regular transmitters with some simple configuration changes that enable them to function in a new capacity.
Mirrors provide high availability and scalability. You can set up a master to redirect client requests to a repeater transmitter. The client redirection enables clients to communicate with the nearest server, and it provides built-in fault tolerance.
You can also use a proxy in a remote location where hardware resources are limited. In this situation, you can host the proxy on a desktop-class machine to service up to 50 endpoints.
Endpoints Endpoints refers to target desktops and laptops and servers. The agent enables targeting, installation, and updates on the endpoints. When enabled, MESH allows a tuner on an endpoint to function as a transmitter mirror or repeater by allowing it to request content and provide that content to other MESH-enabled endpoints.
MESH-enabled tuners can also replace proxies except when the proxy is used route network traffic around a firewall. Enabling the MESH functionality in endpoint tuners is a good choice in remote locations or other places where hardware resources are limited. The MESH functionality enables tuners to act as a local mirror or repeater for a group of endpoints.
BMC can help you to design a setup that is more suitable for your environment. You copy channels from the test or QA lab to your production environment on an ongoing basis, usually weekly or monthly, or when new content is available.
The Report Center publishes the Inventory and Logging plug-ins to the master transmitter. The plug-ins contain schedules for inventory scanning and log collection. You can also publish these plug-ins if you need to change a configuration setting, such as the schedule for an inventory scan or log collection from endpoints.
The Policy Manager publishes the Policy Service plug-in to the master transmitter. In the diagram, two of the mirrors and the master transmitter are placed behind a load balancer. A third mirror, located at a different site for disaster recovery, can be promoted into use in the event of a master transmitter or data center failure.
NOTE Alternative If you do not want to use a load balancer to provide fault tolerance, you can have only one master that replicates to repeaters and then have a mirror that is not part of the rotation.
In this case, the mirror is not used by endpoints unless the master goes down. Then you quickly convert the mirror to a master by using Transmitter Administrator, a fairly simple operation.
Channels are cached on proxies at remote sites on an on-demand basis. Plug-ins are replicated to repeaters but not to proxies.
TrueSight Server Automation
In this scenario, the master and mirrors are placed behind a load balancer. The load balancer is identified by a single IP guiee. When repeaters connect to that IP address for replication, they are automatically routed to the master or one of the mirrors. If the endpoints use Policy Manager, the endpoints get the channels according to their policies. If the guidr are part of a Deployment Manager system, the endpoints get their channels according to the job schedule set in Deployment Manager.
The repeaters then forward the data to the plug-ins on the guice and mirrors. You specify this data in one or more of the following ways: You create queries for hardware and software inventories, software usage if you have the Software Usage componentpolicy compliance, and so on.
You can create your own queries or use predefined queries from the Query Library.
BMC BladeLogic Client Automation Installation Guide
Your previously created queries are automatically run according to schedules, and the results are ed to the appropriate people. You build queries that return a group of machines, and you save these queries in special predefined folders. Other management tools, such as Deployment Manager, Transmitter Administrator, Tuner Administrator, use these queries so that you can manage multiple machines simultaneously.
The Policy Management module then targets these collections. The following topics are provided: Determining the requirements for the infrastructure setup Identifying business objectives Adding infrastructure components to your architectural diagram Determining the infrastructure platforms and hardware Determining the requirements for the infrastructure setup To get started, you must identify your requirements to determine how to set up the BMC BladeLogic Client Automation infrastructure in your environment.
This section helps you make those decisions. Identifying business objectives Writing down the basic business requirements for your BMC BladeLogic Client Automation infrastructure helps you determine the hardware and software requirements for your environment. For example, updating Blarelogic of web content on servers every admiinistration requires more hardware than updating a MB custom application on desktops once a month.
Maintain accurate asset inventories of all hardware and software. Deploy and manage applications on remote desktops and laptops. These applications can consist of both custom applications and shrink-wrapped applications, such as Microsoft Office.
Streamline the current software distribution process. Adding infrastructure components to your architectural diagram To create an architectural plan for your BMC BladeLogic Client Automation infrastructure, complete the following steps: Estimate how many of each component you need, as described in Machine count and location requirements.
Consider some issues that can affect those original estimates, as described in Estimated service load on page 29 and Security requirements on page Ensure that your existing hardware and software meet the minimum system requirements, as described in Determining the infrastructure platforms and hardware on page Machine count and location requirements Determine if the setup shown in Figure 1 works for your enterprise.
That diagram shows a master transmitter, mirrors, and repeater distribution servers at regional and branch offices.
The required number of distribution servers and proxies depends on the number of endpoints and the number of remote sites in your enterprise. Corporate headquarters and the various regional and branch sites.
Speed of the network connections between the sites. Location of the database and directory service. Sites that replicate the directory service.
H Coordination for Creation and Operation of Virtual L-Servers
Number of endpoints located at each site. Figure 1 Network diagram example Corporate HQ Branch office A Database Kbps Directory services desktops and laptops server endpoints 40 desktops and laptops T1 line T1 line kbps Regional office 1 Regional office 2 Gkide office B Replicated directory services desktops gjide laptops Replicated directory services desktops and laptops 90 desktops and laptops Use the number of remote sites and the number of endpoints at each site to help you determine how many mirrors, repeaters, and proxies you need, as described in administraation following paragraphs.
To help you determine how many transmitters you need, use the following formula: NOTE This formula provides a rough estimate. You must also consider the update frequency and the size of the updates. With infrequent updates and small changes, a master transmitter might be able to handle 50, endpoints.
TrueSight Server Automation – BMC Software
If the total adminiztration of endpoints is under 5, and you do not have or do not want to use a load balancer, you can use one master and then use one mirror as a backup or hot spare transmitter. The mirror provides fault tolerance by maintaining workspace backups of the master and can quickly be promoted to master in the event that the master system failure. However, this strategy requires a manual DNS alias change when you promote the mirror to a master.
Requirements for the console server Figure 1 shows only one console server, which bladelpgic one Report Center.
When users run queries, the reports can contain results from endpoints in one or more domains, depending on how the query is constructed.
If your enterprise uses Active Directory and supports a multi-domain forest, and you want to restrict administrators in one domain from seeing queries that the administrators in another domain use, you can install multiple console servers and Report Centers. The setup described in this guide assumes you have only one console server. If you want to use bladelogid than one, contact Customer Support for assistance. Requirements for a directory service You can also use access control lists, which allow Report Center to limit the endpoints that display in query results.