Issue: Anything that may happen during a meeting which has a pejorative effect on end-user experience.
Solution: In Connect 9.1 we have a great diagnostic option in the meeting room. You can immediately pull logs from any meeting to diagnose:
If you click Help>About Adobe Connect, while holding down the Ctrl key, the debug logs will appear int he meeting room and you will have the option to copy them to your clipboard.
Sending me these, along with the RTMP string Help> About Adobe Connect, while holding down the Shift key – this will be most helpful from the client experiencing the extreme latency.
Now if you want to take it even one step further and provide a client-side view of the meeting:
The instructions for enabling client-side logging are here: http://helpx.adobe.com/adobe-connect/kb/enable-logging-acrobat-connect-professional.html
Providing all this data along with the date and time (including timezone) and Meeting URL of any issue, will greatly expedite analysis and solution.
Issue: Plan for the flow of traffic to enable UV among the various components in any Connect deployment: Connect, Flash Media Gateway (FMG), Session Initiation Protocol (SIP)
There are numerous documents on the topic of Unified Voice (UV) with Connect:
This diagram shows the flow of traffic and the protocols used for UV with Connect and is offered as a planning and a troubleshooting tool; click on the diagram to expand it for viewing:
Issue: Be careful when following the Adobe Connect Deployment Guide posted on the F5 Website. While the article is be helpful, there are some ambiguities that can lead to trouble. I have tried to update their deployment guide but have not succeeded; the LTM is the most popular load-balancing device and SSL accelerator in the Connect niche and when it is set up properly it works splendidly. Here are corrections, updates and things to watch out for when deploying Connect behind an LTM:
1. Do not use an HTTP profile for an RTMP VIP. An HTTP profile for RTMP VIPs may affect playback of video as well as break remote Edge connectivity. Remember that you have two servers running on each box, a Tomcat application server and an FMS server. Do not treat the FMS server as though it were an application server; RTMP is a streaming protocol that requires a TCP profile at the HLD VIP.
2. Use the health monitor documented here for LTM.
3. Do not use session-awareness or stick-sessions even if you use SSL. The Round Robin algorithm should float freely to the Tomcat application pool.
4. Do not use Nagle’s Algorithm with SSL; it will have a negative effect on performance.
Review this general Connect pool/cluster configuration tutorial before configuring BIG-IP LTM with Connect: Adobe® Connect™ server pools/clusters and hardware-based load-balancing devices with SSL acceleration
This updated article offers a best-practice configuration of a basic Connect pool/cluster behind a high-end, application-aware HLD such as F5 BIG-IP LTM. This article does not discuss SSL-acceleration. This article does not describe all the possible configurations, but offers a general working example of a basic HTML/RTMP non-SSL cluster/pool of Connect servers.
Adobe Connect Server Pools and Hardware-based Load-balancing Devices: http://www.connectusers.com/tutorials/2009/04/load_balancing/index.php
Issue: Many customers ask Adobe what camera to use with Connect
The short answer is, most any camera you would like. Adobe does not recommend specific cameras but we do have this posted for guidance: Peters’ Camera Options Recording: https://my.adobeconnect.com/p11223582/?launcher=false&fcsContent=true&pbMode=normal
Many software-based server load-balancing and fail-over options have prematurely reached the end of the product life cycle. The market prediction that effectively swept software-based options off the enterprise landscape was that the price of superior hardware-based solutions would decrease enough to make the software options superfluous. The problem with this prediction is obvious to anyone who has tried to cluster a small pool of application servers on a tight budget: the price of the hardware options that are worth having have not dropped enough to fill the niche occupied by software clustering applications….
Criseyde and Troilus live: See the updated tutorial on the Connect Users Community: http://www.connectusers.com/tutorials/2009/04/clustering_nlb/index.php
When most people think of meeting recordings, they often expect a standard video capture of the original meeting. For most web conferencing platforms, this is the case. Adobe Connect recordings however provide much more functionality. It’s certainly possible to generate a static video by clicking the ‘Make Offline’ button. By default however, Adobe Connect recordings are much more interactive and completely indexed….
See Alistair Lee’s complete tutorial here: http://www.connectusers.com/tutorials/2013/01/accessing_editing_adobe_connect_recordings/index.php
The most robust means of implementing secure socket layer (SSL) with Adobe Connect servers is through a hardware-based SSL accelerator and similarly, the most robust means of clustering Connect servers is with a hardware-based load-balancing device (HLD). Since all enterprise-class HLDs are also SSL accelerators (any that are not both are either legacy or low-end by definition), this example-based article offers a best-practice configuration of a Connect Server pool or cluster running Connect Meetings, Adobe Presenter on-demand content, Adobe Connect Training, Curriculum and Virtual Classrooms securely behind a high-end, application-aware HLD and SSL acceleration device such as F5 BIG-IP LTM. This article does not exhaust the possible configurations, but offers a general working example.
The full tech-note is published here: http://www.connectusers.com/tutorials/2011/09/connect_servers_ssl_acceleration/index.php
This article focuses on Enterprise Proxy Connect Edge deployments and troubleshooting: http://www.connectusers.com/tutorials/2011/06/edge_server_deploy2/index.php