3 Replies Latest reply on Mar 29, 2012 8:32 AM by Adil Rathore

    Is BBCA a Push Techonology?

      I have heard it a lot of times that BBCA works on push technology, though, as per design it seems to be based on pull technology, as the request for subscribing packages, patches, configuration settings etc., originates from the client, and then the request is catered by the BBCA Transmitters.

        • 1. Is BBCA a Push Techonology?
          Paul Seager-Smith

          BBCA can actually handle both what are described as traditional push and pull mechanisms. In general, the majority of the functionality is initiated from the client as this is the only way that you can reliably manage a mobile workforce that only periodically connects to the network (or even desktops that are turned off regularly).

          Hence inventory requests, policy requests and patch requests are initiated from the client and then it connects back to the core transmitter infrastructure to find out what it needs to download.

          The deployment manager functionality allows you to to push requests out imediately from the core infrastructure (provided that the clients are all on and connected to the network). To do this it uses the tuner admin port on 7717 by default, so this will need to be open through any firewalls.





          • 2. Is BBCA a Push Techonology?
            Gordon McKeown

            Can't really add much to Paul's answer, but whilst the core technology is definitely pull (even the deployment manager is a push-initiated pull), the administration method is more push. A central group of people dictate what gets "pushed" to the clients, despite the technical method of delivery being a pull!

            1 of 1 people found this helpful
            • 3. Is BBCA a Push Techonology?

              Very valuable inputs I can say! Thank's Paul and Gordon.