1 Reply Latest reply on Feb 7, 2011 2:18 PM by Paul Seager-Smith

    Advanced Repeaters in BL 8.1


              I'm looking for advice on the features of Advanced Repeaters in 8.0 or ideally in 8.1.


      Can someone direct me to docs that cover the design of Advanced Repeaters please?




      1. What operating systems will they run on?

      2. What TCP ports do they use and for what?

      3. How are client servers configured to use them?

      4. What spec of server will they run on?

      5. What are their limitations?



      Hope someone can help.






        • 1. Advanced Repeaters in BL 8.1
          Paul Seager-Smith



          few pointers here:


          • Advanced File Server. The Advanced File Server is an enhanced Java application server running on an existing File Server. It uses the Marimba (now BBCA) master transmitter component to hold a second copy of the depot content in a compressed, proprietary format that is well suited to providing bandwidth efficient transfer of data.
          • Advanced Repeater. The Advanced Repeater runs together with the traditional BladeLogic repeater and utilises the Marimba (BBCA) Proxy component to efficiently download the data from the Advanced File Server. This is also a Java application. An RSCD agent must also be installed on the servers hosting both components.
          • Tuner. Both the advanced repeater and advanced file server are built on the modular Marimba components based on the core tuner. The tuner is a Java application that can have additional modules installed to update its functionality. The advanced file server uses the transmitter module and the advanced repeater uses the proxy module. The modules are referred to as channels in Marimba.
          • Content Replicator (Rep). The Content Replicator Module is used to publish the content from the file server to the Marimba Transmitter on the advanced file server. It is then also used to pull the content down to the file system on the advanced repeater, via the Marimba proxy module.
          • Installation. The advanced repeater and advanced file server are both installed from the same installer binary and are configured to autostart either as a service (on Windows) or using the init.d startup scripts (on Unix platforms).
          • Configuration. Configuration of the advanced repeater and advanced file server are both done using the BladeLogic Infrastructure Administration component of the console UI. This results in NSH commands being executed that call command line operations to configure the components.
          • Supported Platforms. Basically, the same as the other Bladelogic infrastructure components.



          Communication and Security

          • Communication Ports and Protocols. The advanced repeater, unlike most other Bladelogic components, makes a connection from the advanced repeater back to the advanced file server. By default this is an http connection on port 5282 (J-A-V-A on a telephone keypad). The port can be changed and 256-bit encrypted SSL can also be used.
          • Encryption. By default the traffic between advanced file server and advanced repeater is not encrypted. However, SSL can be used if encryption is required. Note that the SSL certificate needs to be provided by the customer.WARNING: If you do switch the advanced file server/repeater to use SSL, the caching function on the advanced repeater will be disabled as the advanced repeater can then no longer see inside the data stream to cache individual files or blocks of data. It will still offer differencing and compression advantages over the standard repeater, but no caching.
          • Accounting. All connections to the advanced file server are logged and an overview of the transaction and any errors are also logged, along with the amount of data transmitted.