BBCA Fundamentals – Infrastructure –

1. BBCA Fundamentals– Infrastructure – • Nitish Shrivastava

2. Section one Introducing BBCA

3. BBCA gives customers dynamic control of their IT resources by offering software change and configuration management solutions within a secure, scalable, multi-platform environment

4. What are we good at? Endpoint/Client Distribution Server

5. Policy Manager Perform policy-based distribution, updating, repair, removal, and license compliance of applications. Inventory Management Collect accurate hardware, software, system, and logging information about your IT assets. BBCA Product Family Server Management Manage, configure, and maintain servers across multi-platform environments. BBCA Patch Management Manage the distribution of patches (such as anti-virus and application security patches) and maintain a high level of security across your enterprise. OS Management Automate and accelerate operating system migrations across your enterprise. Application Manager Manage the distribution, installation, and configuration requirements needed for complex applications.

6. BBCA helps customers dramatically reduce costs and improve quality of service for today's most complex IT challenges, including: Security Patch and Anti-Virus Management Software License Compliance OS Migration Inventory Management – Software and Hardware Distribution and Management of applications Policy-based automation lets IT departments manage the entire state of their IT environments BBCA Technology Benefits

7. Section two Distribution

8. PACKAGING Off-the-shelf applicationsWindows Installer Packages (MSI)Customer ApplicationsContent/Data Change Management Lifecycle DEPLOYMENT Bandwidth EfficiencyFirewall SupportSecurityScalabilitySelf-Healing BBCA – Distribution POLICY DISCOVERY Policy based targetingWho gets what?When should they get it? Enterprise-wideReportingHardware and Software InventoryOperating systemsSoftware usage

9. Section three BBCA Infrastructure

10. BBCA Architecture BBCA Console BBCA Core

11. Infrastructure core Channels Transmitter Tuners • Client Agents – BBCA Tuners • Distribution Servers – BBCA Transmitters • Content – BBCA Channels

12. Tuners… Channels Transmitter Tuners BBCA agents {Tuners} are installed on managed endpoints {Such as desktop, laptop computer, server or device} and provide a platform for change management activities.

13. Transmitters Transmitter Channels Tuners BBCA distribution servers {Transmitters} deliver content to endpoints {Tuners}. Transmitters host channels for distribution to endpoints Transmitters use the HTTP protocol to deliver channels to a client. The Transmitter listens on a port, waiting for requests from clients.

14. Channels Transmitter Channels Tuner BBCA “Channels” are discrete, packaged units of “change” to be delivered / applied to an endpoint; examples might include: 1) an application {e.g. proprietary, Windows Installer, Java}, 2) data, 3) directories / files, 4) registry key, etc.

15. Subscription Request 1 Channel Index 2 Get File Request 3 Content Download 4 Channel subscription Transmitter Tuner When the Tuner subscribes to a channel, it downloads all necessary channel components {e.g. files, applications, content, etc.} into the Tuner workspace.

16. Transmitter Console… Console Server Endpoints Console Web Interface

17. What is console • Collectively, the entire set of tools is called the Console. • The Console contains all the tools necessary to administer a BBCA environment. Infrastructure Administration Report Center Schema Manager Policy Manager Patch Manager Common Management Services BBCA Tuner

18. Console Server • BBCA Console – the browser-based interface for BBCA applications • Infrastructure Administration – administrative toolset • Schema Manager – database and directory service configuration / maintenance • Report Center – inventory, software usage and centralized logging • Policy Management – endpoint targeting and package distribution

19. BBCA's core components – Tuners, Transmitters, and Channels c) A Tuner acts as the base for BBCA technology and resides on all endpoints and distribution servers to enable communication between these components The applications installed on BBCA Console include – Console, Infrastructure Administration, Policy Manager, and Report Manager A Channel can deliver content such as applications, files, registry key settings, etc. A client (endpoint Tuner) subscribes or requests to download and install content from a Transmitter. The clients can subscribe and update content automatically according to a policy. The default listening Port for BBCA Transmitter = 5282 Core - Summary

20. Section four Channel Management

21. Channels… Transmitter Channels Tuner BBCA “Channels” are discrete, packaged units of “change” to be delivered / applied to an endpoint; examples might include: 1) an application {e.g. proprietary, Windows Installer, Java}, 2) data, 3) directories / files, 4) registry key, etc. Channel URL: http//<machinename>:5282/category/<channelname>

22. Channel subscription process Subscription WorkspaceDirectory Tuner Channels Transmitter Distribution Server Endpoint (Client) When the Tuner subscribes to a channel, it downloads all necessary channel components {e.g. files, applications, content, etc.} into the Tuner workspace.

23. Client / Server communication (as well as storage) is optimized using: File-level Differencing Byte-level Differencing Compression Checkpoint restart Bandwidth Management P2P distribution Channel – Performance Optimization

24. Section five Transmitters…

25. Transmitter Types • Master Transmitter – Primary source of content distributing content to other components • Mirror Transmitter – One or more Mirrors can be used to replicate the content of a Master Transmitter • Repeater Transmitter – One or more Repeaters can be used to distribute content across a WAN Although typically considered pivotal to certain BBCA architecture, a Proxy is NOT a Transmitter type

26. http://master:5282/Global/ch1 http://master:5282/Global/ch2 http://master:5282/Global/ch3 http://master:5282/Global/ch4 What is Transmitter? Master Transmitter Channels Tuners Global – ch1 – ch2 – ch3 – ch4 A single Master Transmitter lies at the heart of every BBCA infrastructure; this machine serves channels to distributed endpoints and replicates to Mirror Transmitters and Repeaters

27. – ch1 – ch2 – ch3 – ch4 Global http://mirror1:5282/Global/ch1 http://mirror2:5282/Global/ch1 Mirror 1 Load Balancer http://master:5282/Global/ch1 http://lb:5282/Global/ch1 Mirror 2 Global – ch1 – ch2 – ch3 – ch4 What are Mirror Transmitters? Master Transmitter Global – ch1 – ch2 – ch3 – ch4 One or more Mirror Transmitters replicate channels from the Master Transmitter and offer such benefits as: 1) fault tolerance, 2) high availability, 3) backup and 4) disaster recovery Tuners

28. – Global/ch1 – Global/ch2 – Asia/ch5 – Asia/ch6 Repeater http://master:5282/Global/ch1 Repeater 1 – Global/ch3 – Global/ch4 – Europe/ch7 – Europe/ch8 Repeater 2 Repeater http://master:5282/Global/ch3 Tuners What are Repeater Transmitters? Master Transmitter – Global/ch1 – Global/ch2 – Global/ch3 – Global/ch4 – Asia/ch5 – Asia/ch6 – Europe/ch7 – Europe/ch8 Repeaters replicate channels from the Master Transmitter and serve redirected Tuner requests; redirection types include: 1) round-robin, 2) geographic, 3) IP- / subnet-based or 4) custom

29. Master Transmitter Replicate • Replicate – initiated by Mirrors, Repeaters and Channel Copier (similar to a Subscribe request) Mirror Mirror Load Balancer • Subscribe – commonly referred to as the requests from an endpoint for a published channel Repeater Repeater Subscribe Endpoints Transmitter – Request Types Publish • Publish – initiated by Publisher or Channel Copier; used to create new versions of a channel and make it available to clients

30. Typical BBCA Infrastructure • Master Transmitter –serves applications and content packaged into “channels.” • Mirrors – set up to regularly auto-replicate all their content from the Master Transmitter. • Repeaters – set up to redirect client requests from a Master Transmitter. Repeaters regularly auto-replicate some or all of the content from a Master/Mirror. • Proxies – used in remote locations where endpoints do infrequent updates. • Endpoints – A BBCA Tuner is placed on every endpoint.

31. Section six Proxy

32. What is Proxy? Proxy 1 Master Transmitter Proxy 2 Tuners BBCA Proxies act as intermediaries between servers and agents, brokering requests from Tuners and sending files back to them on behalf of a Transmitter Although typically considered pivotal to certain BBCA architecture, a Proxy is NOT a Transmitter type

33. Preload Cache can be used to “stage” frequently used or large files onto a Proxy; verify preload success by checking for new “db.x” files in the “cache” directory Another way to optimize data distribution in the infrastructure. Customer can configure proxy and pre-load the data. Clients in that network would take it from proxy and thus optimize the data subscription process. Next section talks about the new distribution methodology that does not need any dedicated server (like proxy/repeater) but still optimize the data distribution. Proxy - Summary

34. Section Seven Summary

35. The infrastructure scales really well up to 300,000 endpoints Works really well even on a very low bandwidth. Key features like Checkpoint restart, repeaters, Proxies and distribution using p2p offers great flexibility in optimizing the data transfer. BMC’s Blade logic too would be using this infrastructure for their data distribution.

36. Thank you