Author Archive: Jim Johnson

Adobe Connect Meeting Add-in for 9.1.2 is Now Available

The new Adobe Connect Meeting Add-in is now available.  This latest version of Adobe Connect Add-in is 11.2.392.0 for both Windows and Mac platforms.  Please see the following knowledge base article below for the latest information including the list of issues that have been fixed in this release as well as the links to download both the Windows and Mac versions of the Add-in.

http://helpx.adobe.com/adobe-connect/kb/latest-connect-91-addin.html

Pulling Applicable Logs for Telephony / UV Issues

Typically when on-premise Adobe Connect customers experience telephony issues or UV related issues in their Adobe Connect Meeting rooms, Adobe Support will request specific logs from the customer’s environment.  These logs may come from different places depending on your Connect deployment.  Below is a good guide to understand how to grab just the applicable logs that Connect Support will need.

Typically, for telephony or UV issues these logs will be:

  • application.log
  • core.log (for FMG/UV if applicable)
  • SipLog (for FMG/UV if applicable)
  • TelephonyService.log

and any of the following (‘adaptor logs’ as I’ll refer to it as in this article), depending on the Telephony Integration/Provider you are using:

  • Arkadin_Adaptor.log
  • Avaya_Adaptor.log
  • Intercall_Adaptor.log
  • MeetingOne_Adaptor.log
  • MeetingPlace_Adaptor.log
  • Premiere_Adaptor.log
  • Premiere_EMEA_Adaptor.log

One thing to understand is that if you have a ‘cluster’ of Adobe Connect origin servers, your telephony services for the meeting in question may or may not open on the same server as the meeting itself.  So you could have a meeting running on one node in the cluster, while the actual telephony services are running on another.  Also, if you are running an FMG server (for UV), the FMG services may or may not be on the same server that is running the actual meeting.

Here’s how to collect the applicable logs to submit to Adobe Support if they request the ‘telephony’ logs for a meeting:

For Adobe Connect 9.x:

Application.log (also sometimes referred to as the ‘Meeting log’)

This is the log that contains all the logging for the meeting itself.  It will contain the telephony service connection in which you can identify what server the telephony services actually connected on.  It will also tell you  (if applicable) what server the FMG connection happened on.  This log will also show all the user activity in the meeting (including phone numbers, etc.). This is very crucial for Adobe to obtain when troubleshooting an audio issue in an Adobe Connect Meeting.

It is located in: [Root Connect Install Directory]\logs\support\apps\_defaultVHost_\meetingas3app\7\{sco-id} where ‘sco-id’ is the actual numeric value of the Meeting room’s sco-id.

To find the sco-id of the meeting room, you can log into Adobe Connect’s web manager and navigate to the Meeting Information page in the UI.  The URL of that page will look something like this:

http://myConnectURL/admin/meeting/sco/info?account-id=7&principal-id=11033&sco-id=11115&tab-id=11003

(where the values for principal-id, sco-id-, tab-id are obviously just example values for the sake of this article)

The ‘sco-id‘ from that URL will be the name of the folder you are looking for in the above directory for finding the application.log.

Note: If you have a cluster for Adobe Connect that contains multiple servers, you may have to search every server in the cluster for this file.  You may also notice that if the meeting room in question is used over and over, it will open eventually on all the servers in the cluster, so you may in fact have the sco-id folder present on more than one (or all) of the servers, but the actual application.log for the session you are looking for will only be on one server.  Each session will get it’s own Application.log.  So you will see multiple (eventually) versions of the application.log in this folder over time.  You need to look at the timestamp of the logs to make sure you are getting the right one for the day/time the session in question occurred.  Once you identify the right application.log for the meeting session in question, you need to open it up and look for the following logging looking similar to this:

(you can search the log for the values in red):

2013-11-19	10:21:32	94648	(s)2641173	get-telephony-service API result obtained.	-
2013-11-19	10:21:32	94648	(s)2641173	get-telephony-service API successful	-
2013-11-19	10:21:32	94648	(s)2641173	  .get-telephony-service result object:  [Object]	-
2013-11-19	10:21:32	94648	(s)2641173	    \\	-
2013-11-19	10:21:32	94648	(s)2641173	    .host [Object]	-
2013-11-19	10:21:32	94648	(s)2641173	        \\	-
2013-11-19	10:21:32	94648	(s)2641173	        .external-name [string]= connect01.mycompany.com	-
2013-11-19	10:21:32	94648	(s)2641173	        .ip [string]= 10.11.123.44	-
2013-11-19	10:21:32	94648	(s)2641173	        .name [string]= connecthost01	-
2013-11-19	10:21:32	94648	(s)2641173	        .service-host-id [string]= 15647477	-
2013-11-19	10:21:32	94648	(s)2641173	    .subcode [undefined]	-
2013-11-19	10:21:32	94648	(s)2641173	    .code [string]= ok	-
2013-11-19	10:21:32	94648	(s)2641173	hostName: connecthost01, hostIp: 10.11.123.44	-

where the hostName will be the server in which the telephony services opened on.  The logging snippet will contain that hostName and the hostIP as well as the external name (FQDN) of that meeting server.  The above examples in BLUE are just merely generic values for the sake of this article.

** IF applicable (if you are using UV), also look for the following (you can search the log for the values in red):

 

2013-11-19	10:21:44	94648	(s)2641173	FMGServiceConnector.asc:: get-fmg-service API onResult obtained	-
2013-11-19	10:21:44	94648	(s)2641173	FMGServiceConnector.asc:: get-fmg-service API successful	-
2013-11-19	10:21:44	94648	(s)2641173	FMGServiceConnector.asc:: fmgHostName=fmghost02, fmgHostIp=10.11.123.456	-
2013-11-19	10:21:44	94648	(s)2641173	FMGServiceConnector.asc:: FMG client has already connected, connected ip= 10.11.123.456	-
2013-11-19	10:21:44	94648	(s)2641173	FMGServiceConnector.asc:: Setting connected fmg ip:10.11.123.456	-
2013-11-19	10:21:44	94648	(s)2641173	FMGServiceConnector.asc:: fmgHostName saved = fmghost02	-

where the fmgHostName and fmg ip address will be visible.  The above examples in BLUE are just merely generic values for the sake of this article.

 

Once you identify the server the Telephony Services opened on (and if applicable, UV), move on to getting those logs…

TelephonyService.log

This is the log that contains all the logging for the Adobe Connect Telephony Services.

It is located in: [Root Connect Install Directory]\Breeze\logs\telephony

Note: If you have a cluster for Adobe Connect that contains multiple servers, refer to the info above on making sure you know what server to pull this log from.

{XXXXX}_Adaptor.log

This is the log (depending on your telephony provider) that includes all the logging for the communication between Adobe Connect and the telephony provider’s bridge.  It will contain the communication back and forth and the messages sent to and from the telephony provider using that provider’s API, as well as applicable responses. The ‘XXXXX’ value in the name will obviously be the name of the provider (e.g. Arkadin, PGI, Intercall, etc.).

It is located in: [Root Connect Install Directory]\Breeze\logs\telephony

Note: If you have a cluster for Adobe Connect that contains multiple servers, refer to the info above on making sure you know what server to pull this log from.  It will be the same server that the TelephonyServices.log will come from.

Of course in some circumstances, Adobe Support will also need to work with the telephony provider to obtain logging from their side, should the Adobe Connect logs not yield enough data to continue with the investigation.

core.log 

This is one of two applicable FMG related logs.  If you are using UV, this will be necessary to obtain for support to review the FMG logging.

It is located in: [Root Connect Install Directory]\Flash Media Gateway\{FMG version}\log

Note: If you have a cluster for Adobe Connect that contains multiple servers, refer to the info above on making sure you know what server to pull this log from.

SipLog (this will be date/timestamped in the actual name of the log)

This will be the log that will contain the communication between FMG and the SIP server/service.  If you are using UV, this will be necessary to obtain for support to review the FMG logging.

It is located in: [Root Connect Install Directory]\Flash Media Gateway\{FMG version}\log

Note: If you have a cluster for Adobe Connect that contains multiple servers, refer to the info above on making sure you know what server to pull this log from.

 

7.x Recordings Not Playing after Upgrading to 9.1.1

If you have recently upgraded an Adobe Connect on premise deployment from version 7.x to 9.1.1 (with various 8.x steps possibly in-between), you may encounter an issue where older recordings no longer launch.  However, newly created recordings open and playback without issue.

If this is the case, please check the following directories…

First check:

[Root Connect Install]\9.1.1\appserv\common\meeting\shell

This directory should contain the following SWF files:

  • BreezeUIComponents.swf
  • CorePodCollection.swf
  • meeting.swf
  • meeting_sgn.swf
  • shell.swf
  • shell_sgn.swf
  • StamperSymbols.swf

If they do NOT exist in that directory (but just the ‘breezeLive’ folder and xml files are the only files present), please download the files from here and place into the directory.

Then check:

[Root Connect Install]\9.1.1\appserv\common\meeting\launcher

This directory should contain the following SWF files:

  • listener.swf
  • openmeeting.swf
  • openmeetingversioncheck.swf

If they do NOT exist in that directory, please download the files from here and place into the directory.

After confirming these files are now in those directories, retry launching an older Connect recording.  No restart is required.

Event Module Tutorial Collection

The below is a great collection of Event Module tutorials by both Adobe and our some of our partners.  These cover everything from administration, creation, migration, reporting, best practices, and API integration.

 

Creating an Event in Adobe Connect 9
by video2brain
In this tutorial, you’ll see how to create a new event in Adobe Connect 9 and add it to the Event Catalog

Creating and Editing Event Templates
by Alistair Lee
In this video tutorial, Alistair Lee shows you how to create, edit and manage event templates – new to Adobe Connect 9.

Event Administration in Adobe Connect 9
by Alistair Lee
In this video tutorial, Alistair Lee walks through the new features available to Event Administrators in Adobe Connect 9

Adobe Connect 9: Event Migration Guide
by Alistair Lee, Adobe Systems
This tutorial features a 23-page PDF guide on Adobe Connect 9 events. It highlights the new features introduced in version 9 of Adobe Connect and discusses the impact on events that have migrated.

Creating a Two Person Event Template with Adobe Connect
by Alistair Lee, Adobe Systems
In this tutorial, you’ll see how to quickly create a new event template that features two or more speakers.

Adobe Connect Events Overview
by Alistair Lee, Adobe Systems
In this video, Alistair Lee walks through an overview of the new Adobe Connect Events module.

Adobe Connect best practices for large events and seminars
by Rocky Mitarai, Adobe Systems
This checklist is an invaluable resource for any producers of large webinars and events on Adobe Connect.

Resetting the Default Event Templates in Adobe Connect
by Alistair Lee, Adobe Systems
This tutorial walks through the steps required to reset a default template.

Campaign Tracking in Adobe Connect 9.1
by Alistair Lee, Adobe Systems
In this video tutorial, Alistair walks through some of the new features in Adobe Connect 9.1 that make measuring campaigns and optimizing your promotional channels more intuitive.

Event Registration using Adobe Connect API’s
by Dustin Tauer, Easel Solutions
In this tutorial, Dustin covers how to use the Adobe Connect API’s to register a user for an event.

 

Meeting Add-in | Mac OS X Mavericks 10.9, 10.8, 10.7 with Safari 6.1 or 7

In case you have not seen, we have published a brief article on the issues with using the Adobe Connect Meeting Add-in with Mac OSX Mavericks and newer versions of  the Safari browser.

Details and instructions (in an additional linked article) on how to suppress the restrictions put in place by the newer browsers can be found here:

http://helpx.adobe.com/adobe-connect/kb/connect-add-in-osx-mavericks-109.html

Presenter 9.0.2 Now Available

Presenter 9.0.2 is now available as an updater here:

http://www.adobe.com/support/downloads/product.jsp?product=153&platform=Windows

This is the update for existing Presenter 9.0 customers.

The full installer for Adobe Presenter 9.0.2 will be made live on November 18th - which means the existing build of Presenter 9.0 will be replaced on the Adobe online store, trial downloads, our Licensing system, and DVDs, with Presenter (9.0 + 9.0.2) consolidated installer.

The normal Presenter release notes have therefore been updated to include Presenter 9.0 PLUS Presenter 9.0.2 features and is live now. View the release notes here.

Release notes specific to Presenter 9.0.2 are found here and point out Presenter 9.0.2 details separately.

You can also download and install the update directly from inside of Adobe Presenter 9 by going to the Adobe Presenter > Help > Updates menu (pictured below).

 

presenter902

 

 

In the end (after updating), you should see the following version when going to: Adobe Presenter > Help > About Adobe Presenter…

presenter902a

 

 

Adobe Connect Mobile 2.2 Now Available

We have released Adobe Connect Mobile 2.2 for iOS and Android devices, and this new version is now live on iTunes and Google Play stores.

With this latest release, we’ve continued to focus on enabling the ability to fully host meetings from any device, as well as enable mobile learning.  The key enhancements we have added in this release include:

·         Widescreen (16:9) webcam viewing support

·         Manage audio conferencing from all devices (not just tablets)

·         Enhanced mobile learning, with additional quiz types in virtual classes

·         Optimized support for high-definition Android and iOS Retina displays

·         And more – More information on features and updates can be found in the release notes here.

Check out the official blog post that announces this.

 

Connect Default Bandwidth Adjustments for On Premise Deployments

In addition to other parameters (like chat pod character limits, connection light thresholds,  etc.) you can adjust the default bandwidth and performance settings for your Adobe Connect meeting room experience via the configuration file reference below. This is applicable for On-Premise installations of Adobe Connect only, and is not for Hosted Adobe Connect accounts.

The location of the internal configuration file on Adobe Connect 9.1.1:
{InstallDir}\9.1.1\comserv\win32\conf\originhost\_defaultVHost_\Application.xml

You can throttle these up or down to suit the needs and requirements of your network or infrastructure.
Note: You must cycle the Connect services after making any changes to this file on every node in your cluster (if more than one origin server).

Room Bandwidth Settings:

bw-room

The first setting you can modify relates to the Optimize Room Bandwidth setting inside of the Meeting > Preferences > Room Bandwidth area of the Meeting UI.  This option gives you the three  Room bandwidth options of ‘LAN’, ‘DSL/Cable’, and ‘Modem’.  These settings throttle production based on the room settings and their associated values below.

These contain the bandwidth settings for ‘Client to Server’ as ‘C2S’ and ‘Server to Client’ as ‘S2C’.

  • ‘Up’ values are the C2S values (‘Client to Server’).  This is most important for screen sharing.
  • ‘Down’ values are the S2C values (‘Server to Client’).

All clients in the room will utilize this single setting.

In Connect 9.1.1 these options correlate to the following values (default):

Room Bandwidth Client to Server Server to Client
LAN 100000 KB/Sec 100000 KB/Sec
DSL/Cable 600 KB/Sec 800 KB/Sec
Modem 200 KB/Sec 200 KB/Sec

Room Bandwidth Settings in Application.xml: 

<BW_C2S_MODEM>200</BW_C2S_MODEM>
<BW_C2S_DSL>600</BW_C2S_DSL>
<BW_C2S_LAN>100000</BW_C2S_LAN>
<BW_S2C_MODEM>200</BW_S2C_MODEM>
<BW_S2C_DSL>800</BW_S2C_DSL>
<BW_S2C_LAN>100000</BW_S2C_LAN>

Camera Settings:

bw-video

The next values you can modify, correlate to the video settings at Meeting > Video > Video Settings > Video Quality, in the Meeting UI. This option gives you the ability to adjust the slider from the ‘Low’ to ‘High’ values.  The in-between values are actually ‘Medium’ and ‘Standard’.  All of these 4 options actually determine values for Quality, Frames Per Second (FPS), Max Resolution, and Max Widescreen Resolution.  As the menu in the UI indicates, the 4 quality settings are actually also affected by the previous Room Bandwidth setting as shown below:

9.1.1 Adobe Connect Camera Pod Settings (Default):

LAN

Camera Setting = Quality FPS Max Resolution Max WideScreen Resolution
Low = 70 8 320×240 427×240
Medium = 75 10 320×240 427×240
Standard = 80 15 640×480 854×480
High = 90 20 640×480 854×480

DSL/Cable

Camera Setting = Quality FPS Max Resolution Max WideScreen Resolution
Low = 70 4 320×240 427×240
Medium = 75 8 320×240 427×240
Standard = 80 10 320×240 427×240
High = 85 15 640×480 854×480

Modem

Camera Setting = Quality FPS Max Resolution Max WideScreen Resolution
Low = 70 4 160×120 214×120
Medium = 70 8 320×240 427×240
Standard = 75 10 320×240 427×240
High = 80 15 320×240 427×240

 

Camera Pod Settings in Application.xml: 

- <!– LAN –>
<CAMERA_LAN_LOW_QUALITY>70</CAMERA_LAN_LOW_QUALITY>
<CAMERA_LAN_LOW_FPS>8</CAMERA_LAN_LOW_FPS>
<CAMERA_LAN_LOW_MAX_RESOLUTION>320×240</CAMERA_LAN_LOW_MAX_RESOLUTION> <CAMERA_LAN_LOW_MAX_WIDESCREEN_RESOLUTION>427×240</CAMERA_LAN_LOW_MAX_WIDESCREEN_RESOLUTION>
<CAMERA_LAN_MEDIUM_QUALITY>75</CAMERA_LAN_MEDIUM_QUALITY>
<CAMERA_LAN_MEDIUM_FPS>10</CAMERA_LAN_MEDIUM_FPS>
<CAMERA_LAN_MEDIUM_MAX_RESOLUTION>320×240</CAMERA_LAN_MEDIUM_MAX_RESOLUTION> <CAMERA_LAN_MEDIUM_MAX_WIDESCREEN_RESOLUTION>427×240</CAMERA_LAN_MEDIUM_MAX_WIDESCREEN_RESOLUTION> <CAMERA_LAN_STANDARD_QUALITY>80</CAMERA_LAN_STANDARD_QUALITY>
<CAMERA_LAN_STANDARD_FPS>15</CAMERA_LAN_STANDARD_FPS>
<CAMERA_LAN_STANDARD_MAX_RESOLUTION>640×480</CAMERA_LAN_STANDARD_MAX_RESOLUTION> <CAMERA_LAN_STANDARD_MAX_WIDESCREEN_RESOLUTION>854×480</CAMERA_LAN_STANDARD_MAX_WIDESCREEN_RESOLUTION> <CAMERA_LAN_HIGH_QUALITY>90</CAMERA_LAN_HIGH_QUALITY>
<CAMERA_LAN_HIGH_FPS>20</CAMERA_LAN_HIGH_FPS>
<CAMERA_LAN_HIGH_MAX_RESOLUTION>640×480</CAMERA_LAN_HIGH_MAX_RESOLUTION> <CAMERA_LAN_HIGH_MAX_WIDESCREEN_RESOLUTION>854×480</CAMERA_LAN_HIGH_MAX_WIDESCREEN_RESOLUTION>
- <!– DSL –>
<CAMERA_DSL_LOW_QUALITY>70</CAMERA_DSL_LOW_QUALITY>
<CAMERA_DSL_LOW_FPS>4</CAMERA_DSL_LOW_FPS>
<CAMERA_DSL_LOW_MAX_RESOLUTION>320×240</CAMERA_DSL_LOW_MAX_RESOLUTION> <CAMERA_DSL_LOW_MAX_WIDESCREEN_RESOLUTION>427×240</CAMERA_DSL_LOW_MAX_WIDESCREEN_RESOLUTION>
<CAMERA_DSL_MEDIUM_QUALITY>75</CAMERA_DSL_MEDIUM_QUALITY>
<CAMERA_DSL_MEDIUM_FPS>8</CAMERA_DSL_MEDIUM_FPS>
<CAMERA_DSL_MEDIUM_MAX_RESOLUTION>320×240</CAMERA_DSL_MEDIUM_MAX_RESOLUTION> <CAMERA_DSL_MEDIUM_MAX_WIDESCREEN_RESOLUTION>427×240</CAMERA_DSL_MEDIUM_MAX_WIDESCREEN_RESOLUTION> <CAMERA_DSL_STANDARD_QUALITY>80</CAMERA_DSL_STANDARD_QUALITY>
<CAMERA_DSL_STANDARD_FPS>10</CAMERA_DSL_STANDARD_FPS>
<CAMERA_DSL_STANDARD_MAX_RESOLUTION>320×240</CAMERA_DSL_STANDARD_MAX_RESOLUTION>
<CAMERA_DSL_STANDARD_MAX_WIDESCREEN_RESOLUTION>427×240</CAMERA_DSL_STANDARD_MAX_WIDESCREEN_RESOLUTION> <CAMERA_DSL_HIGH_QUALITY>85</CAMERA_DSL_HIGH_QUALITY>
<CAMERA_DSL_HIGH_FPS>15</CAMERA_DSL_HIGH_FPS>
<CAMERA_DSL_HIGH_MAX_RESOLUTION>640×480</CAMERA_DSL_HIGH_MAX_RESOLUTION>
<CAMERA_DSL_HIGH_MAX_WIDESCREEN_RESOLUTION>854×480</CAMERA_DSL_HIGH_MAX_WIDESCREEN_RESOLUTION>
- <!– MODEM –>
<CAMERA_MODEM_LOW_QUALITY>70</CAMERA_MODEM_LOW_QUALITY>
<CAMERA_MODEM_LOW_FPS>4</CAMERA_MODEM_LOW_FPS>
<CAMERA_MODEM_LOW_MAX_RESOLUTION>160×120</CAMERA_MODEM_LOW_MAX_RESOLUTION>
<CAMERA_MODEM_LOW_MAX_WIDESCREEN_RESOLUTION>214×120</CAMERA_MODEM_LOW_MAX_WIDESCREEN_RESOLUTION> <CAMERA_MODEM_MEDIUM_QUALITY>70</CAMERA_MODEM_MEDIUM_QUALITY>
<CAMERA_MODEM_MEDIUM_FPS>8</CAMERA_MODEM_MEDIUM_FPS>
<CAMERA_MODEM_MEDIUM_MAX_RESOLUTION>320×240</CAMERA_MODEM_MEDIUM_MAX_RESOLUTION>
<CAMERA_MODEM_MEDIUM_MAX_WIDESCREEN_RESOLUTION>427×240</CAMERA_MODEM_MEDIUM_MAX_WIDESCREEN_RESOLUTION> <CAMERA_MODEM_STANDARD_QUALITY>75</CAMERA_MODEM_STANDARD_QUALITY>
<CAMERA_MODEM_STANDARD_FPS>10</CAMERA_MODEM_STANDARD_FPS>
<CAMERA_MODEM_STANDARD_MAX_RESOLUTION>320×240</CAMERA_MODEM_STANDARD_MAX_RESOLUTION>
<CAMERA_MODEM_STANDARD_MAX_WIDESCREEN_RESOLUTION>427×240</CAMERA_MODEM_STANDARD_MAX_WIDESCREEN_RESOLUTION> <CAMERA_MODEM_HIGH_QUALITY>80</CAMERA_MODEM_HIGH_QUALITY>
<CAMERA_MODEM_HIGH_FPS>15</CAMERA_MODEM_HIGH_FPS>
<CAMERA_MODEM_HIGH_MAX_RESOLUTION>320×240</CAMERA_MODEM_HIGH_MAX_RESOLUTION>
<CAMERA_MODEM_HIGH_MAX_WIDESCREEN_RESOLUTION>427×240</CAMERA_MODEM_HIGH_MAX_WIDESCREEN_RESOLUTION>

 

Screen Share Settings:

bw-ss

The last applicable setting is for Optimizations with Screen sharing.  In the UI, you can set it to ‘Low’, ‘Medium’, ‘Standard’, and ‘High’.  The below chart indicates what each of the values for these settings (for the ON2 SS Codec) actually are.

SS_ON2 Setting BW Limit Quality FPS Worst Quality Minimum Worst Quality
Low 500 65 2 1 1
Medium 800 80 4 30 15
Standard 1200 90 6 70 30
High 2000 100 8 90 50

Notes: 
SS_ON2_BW_LIMIT is in kb/sec.
SS_ON2_QUALITY defines the compression level (size vs quality).
SS_ON2_FPS defines the target number of frames per second to generate.

 

Screen Sharing Settings in Application.xml: 

<!– BANDWIDTH_LIMIT in kbps–>
<SS_ON2_BW_LIMIT_LOW>500</SS_ON2_BW_LIMIT_LOW>
<SS_ON2_BW_LIMIT_MEDIUM>800</SS_ON2_BW_LIMIT_MEDIUM>
<SS_ON2_BW_LIMIT_STANDARD>1200</SS_ON2_BW_LIMIT_STANDARD>
<SS_ON2_BW_LIMIT_HIGH>2000</SS_ON2_BW_LIMIT_HIGH>
- <!–  QUALITY –>
<SS_ON2_QUALITY_LOW>65</SS_ON2_QUALITY_LOW>
<SS_ON2_QUALITY_MEDIUM>80</SS_ON2_QUALITY_MEDIUM>
<SS_ON2_QUALITY_STANDARD>90</SS_ON2_QUALITY_STANDARD>
<SS_ON2_QUALITY_HIGH>100</SS_ON2_QUALITY_HIGH>
- <!–  FPS –>
<SS_ON2_FPS_LOW>2</SS_ON2_FPS_LOW>
<SS_ON2_FPS_MEDIUM>4</SS_ON2_FPS_MEDIUM>
<SS_ON2_FPS_STANDARD>6</SS_ON2_FPS_STANDARD>
<SS_ON2_FPS_HIGH>8</SS_ON2_FPS_HIGH>
- <!– WORST QUALITY –>
<SS_ON2_WQ_LOW>1</SS_ON2_WQ_LOW>
<SS_ON2_WQ_MEDIUM>30</SS_ON2_WQ_MEDIUM>
<SS_ON2_WQ_STANDARD>70</SS_ON2_WQ_STANDARD>
<SS_ON2_WQ_HIGH>90</SS_ON2_WQ_HIGH>
- <!– MINIMUM WORST QUALITY –>
<SS_ON2_MINWQ_LOW>1</SS_ON2_MINWQ_LOW>
<SS_ON2_MINWQ_MEDIUM>15</SS_ON2_MINWQ_MEDIUM>
<SS_ON2_MINWQ_STANDARD>30</SS_ON2_MINWQ_STANDARD>
<SS_ON2_MINWQ_HIGH>50</SS_ON2_MINWQ_HIGH>

XML API Tips: Modification of Help / Support Links

In Adobe Connect (both On Prem and Hosted accounts), there are methods to modify existing support and help links using the XML API.  This was implemented to provide the capability to replace the in product support / help links and details with partner or organization-specific links / contact information.

Use Case

Say a partner or organization wants to be able to replace the help / support links embedded in the Connect meeting client or Connect web app with links to their own version of the help documentation / support information or support portal. They need to provide a combined cohesive help / support channel to their customers or their users.

The following undocumented APIs are provided to modify the support or help link customization on a per-account basis. Here is how it works:

Link 1 – Contact Support (In Meeting)

First, the ‘Contact Support’ link in the Meeting interface itself (as seen below):

contactsupport
To modify this, use the XML API call: account-support-link-update to enable or disable the account feature and modify the support link.

The default support link is: http://helpx.adobe.com/adobe-connect.html

XML API Call Info:
account-support-link-update
parameters:
account-id = the account-id of the account you are modifying the links for
enable = true or false – enables (true) or disables (false) this feature
support-link = link to partner or customer support site (must be http link)
- if enable is true, must provide support-link
- if enable is false, remove support-link for the account

To enable a custom link:

https://{AccountURL}/api/xml?action=account-support-link-update&enable=true&support-link=http://mySupportsiteURL

Results:

<results>
<status code=”ok”/>

</results>

To verify it is now active (aside from testing in a new meeting session), you can run the ‘feature-info’ API call which will return that feature as part of account information if the feature is enabled on the account.

Example:

https://{AccountURL}/api/xml?action=feature-info&account-id=XXXXXXXX

<results>
<status code=”ok”/>
<disabled-features>
….snip snip….
<feature account-id=”XXXXXXXX” feature-id=”fid-non-partner-support-link“>
<date-begin>2013-10-29T16:53:09.533-04:00</date-begin>
<date-end>2999-12-31T19:00:00.863-05:00</date-end>
<recordcreated>2013-10-29T11:53:09.553-04:00</recordcreated>
</feature>
….snip snip….
</disabled-features>
</results>

Note: it’s deceiving, but it WILL be listed in the ‘disabled-features’ XML node if it is ENABLED.  If it is NOT enabled, it will NOT show up in the results of this call.

To disable (or set back to the original default setting):

https:{AccountURL}/api/xml?action=account-support-link-update&enable=false

Results:

<results>
<status code=”ok”/>
</results>

Note: For meetings that are still active and have not unloaded from memory yet, the links will not change until it fully shuts down.  For new meeting sessions, the link will immediately be updated/reflected to show the intended webpage.

Link 2 – Help Link (Login Page)

Second, the ‘Help’ link on the login page (as seen below):

help

The default value will take you to: http://helpx.adobe.com/adobe-connect.html

XML API Call Info:
account-custom-help-link-update
parameters:
account-id = the account-id of the account you are modifying the links for
field-id = the field-id of the help link you are trying to modify. Values are:
- account-login-help-link
- account-webapp-help-link
value = link to partner or customer support site (The help link must start with either ‘http://’ or ‘https://’.  No javascript urls are allowed as values.)

 

To enable a custom link (use the ‘account-login-help-link’ field-id above):

https://{AccountURL}/api/xml?action=account-custom-help-link-update&account-id=XXXXXXX&field-id=account-login-help-link&value=http://mySupportURL

Results:

<results>
<status code=”ok”/>
</results>

Link 3 – Help Link (Connect Central Page)

Third, the ‘Help’ link on the top of the Connect Central page (as seen below):

central

The default value will be: http://help.adobe.com/en_US/connect/9.0/using/index.htm

XML API Call Info:
account-custom-help-link-update
parameters:
account-id = the account-id of the account you are modifying the links for
field-id = the field-id of the help link you are trying to modify. Values are:
- account-login-help-link
- account-webapp-help-link
value = link to partner or customer support site (The help link must start with either ‘http://’ or ‘https://’.  No javascript urls are allowed as values.)

 

To enable a custom link (use the ‘account-webapp-help-link’ field-id above):

https://{AccountURL}/api/xml?action=account-custom-help-link-update&account-id=XXXXXXX&field-id=account-webapp-help-link&value=http://mySupportURL

Results:

<results>
<status code=”ok”/>
</results>

To REMOVE any of these link customizations, simply leave the VALUE param empty:

https://{AccountURL}/api/xml?action=account-custom-help-link-update&account-id=XXXXXXX&field-id=account-webapp-help-link&value=

Results:

<results>
<status code=”ok”/>
</results>

And:

https://{AccountURL}/api/xml?action=account-custom-help-link-update&account-id=XXXXXXX&field-id=account-webapp-help-link&value=

Results:

<results>
<status code=”ok”/>
</results>

To view any custom help links set on the account:

XML API Call Info:
account-custom-help-links
parameters:
none.

https://{AccountURL}api/xml?action=account-custom-help-links

If NO help links have been customized, you will see only an ‘ok’ result returned.

Results if no help links:

<results>
<status code=”ok”/>
</results>

 Results if help links are customized:

<results>
<status code=”ok”/>
<custom-help-links>
<links>
<login-help-link>http://www.mysupport.com</login-help-link>
<webapp-help-link>http://www.mysupport.com</webapp-help-link>
</links>
</custom-help-links>
</results>

Using the FMS API for On-Prem Adobe Connect

For monitoring purposes, you can build an application which utilizes additional API calls that hook directly into the Flash Media Administration Server services.  This is undocumented but may help you with additional monitoring or statistics on the FMS side.

A full list of FMS/FCS API entries for the 9.1 version of FMS (which is version 4) can be found here:
http://help.adobe.com/en_US/flashmediaserver/adminapi/WSa4cb07693d12388431df580a12a34991ebc-8000.html

Previously, as an Adobe Connect administrator, you probably have always had the additional FMS service (Flash Media Administration Server) shut off.  In order to utilize the API, you need to make sure this service is running:

fmsadmin

In order to hit the API for FMS, you need to use the FMS admin username and password.

This can be found in:

[install drive]:\Connect\9.1.1\comserv\conf

# An administrator for the server. Users.xml
DEFAULT_FCS_USER=XXXXXX
# Password for this vhost administrator. Users.xml
DEFAULT_FCS_PASSWORD=XXXXXX

In order to use all the calls (or a select few, depending on your desire), you need to modify one additional FMS file (see below).

Continue reading…