Posts in Category "Administration"

Stunnel Support with Adobe Connect 9.x

Up until Adobe Connect 9.0.0.1 (full installer) for on-premise (licensed) deployments, Adobe packaged Stunnel with the Connect application to handle the software SSL.  With the release of 9.0.0.1 of Adobe Connect, we included Stunnel 4.53 but do not unpack and install it with the installer (as we previously had done with Connect 8.x).  If you install (or are running) 9.0.0.1 and are looking for the Stunnel package, you need to navigate into the unpacked Adobe Connect 9.0.0.1 installer folder ({unpacked folder}\Adobe Connect 9.0.0.1\Adobe Connect\Merge_Modules) and look for the stunnel-4.53.zip file.  From there, you can install Stunnel 4.53 for your SSL deployment.

With the release of Adobe Connect 9.1.1, we no longer even ship the Connect installer with the Stunnel bits.  So you will need to obtain the Stunnel installer from either Stunnel’s website or from a 9.0.0.1 installer of Adobe Connect.  The last shipped version of Stunnel (with Connect 9.0.0.1) was 4.53, but again it was not ‘unpacked and installed’ as of 9.0.0.1.

The latest build of Stunnel that Adobe QE has tested with is version 4.56, which at the time of this article, is the latest production Stunnel build.

 

 

 

The Mystery of Burst Packs for Meetings

Issue: Adobe Connect hosted customers sometimes ask how to predict the burst pack size needed for insurance that their large meetings with unexpected attendance will be handled.

Solution: Burst Packs will extend the capacity of the Named Host license by up to five times the ceiling. This means that a room with a ceiling of 100 is best covered by a burst pack of up to 500 attendees, or 400 above the standard capacity of 100.  The burst pack minutes will be depleted, for each minute each user exceeds the capacity of 100.  For example, if 110 people join your meeting at the same time, and all 110 stay for 10 minutes, this will require 100 burst pack minutes to accommodate the 10 additional attendees in overage multiplied by 10 minutes.

If during a meeting, you accidentally go over the number of attendees accommodated by your burst pack, then the burst pack  balance will appear as a negative number.  If the meeting is very well attended and the burst pack exceeds 1000, it will be disabled for future meetings so no more overage will be accrued.   For the initial meeting overage, it will go over 1000 (one-time) if a current meeting is on-going, and won’t shut down until that meeting ends. Adobe does not penalize you for your successful use of Connect, but the hard limit for overage is set to 1000.

The meeting will not kick people out because of an overage;  burst pack minutes will continue to accumulate, even if the burst pack is depleted in order to ensure the meeting is not disrupted.  Adobe will then take those overage minutes out of their next burst pack purchase.

Ask your sale representative about burst packs and how to add them to insure successful large meeting in Connect.

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.

 

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>

Connect Meeting Session Management

Behavior: There are two variables with reference to Meeting room session management that a good Connect Administrator will want to consider:

  • When you close a Meeting room, it remains active (on Adobe’s hosted accounts) for 15 minutes before completely shutting down.
  • You cannot keep a continuous active Meeting open beyond 12 hours; the Meeting will timeout after 12 hours.

These two variables are important: The first one is good to know because you may not see some changes propagate to a Meeting room until it has been closed for 15 minutes and then reopened. Tonight, for example I was in a meeting and switched the account settings from RTMP to RTMPS to secure all traffic rather than just the log-in via HTTPS; the padlock icon in the meeting bandwidth indicator (green light in upper right corner) that indicates RTMPS did not appear in the Meeting upon making the change and will not until 15 minutes after the meeting room is closed and then reopened. The variable is called <HOST_LEFT_TIMEOUT> and it also sets the number of minutes participants can stay in a Meeting room after the last host leaves the room. After 15 minutes, participants will be  disconnected from the room.

The second timeout variable is called <SESSION_TIMEOUT> It is very important if you use a Connect meeting room for any support activities and keep it open for longer than 12 hours. The workaround is to set up two rooms and rotate every eleven hour between two rooms to support any sustained activity that will last more than 12 hours.

For on-premise customers these variables are adjustable, though the default settings are highly recommended. These settings can be manipulated in the in application.xml file in \ConnectRoot\comserv\win32\conf\originhost\_defaultVHost_\:

<HOST_LEFT_TIMEOUT>15</HOST_LEFT_TIMEOUT>

<SESSION_TIMEOUT>12</SESSION_TIMEOUT>

Note that changing these setting is not recommended unless there is a pressing need. And with that said, never increase the <SESSION_TIMEOUT> beyond 12 hours, though you may lower it if needed.

Note also the separate third Administration option in Connect Central that manages the timeout of sessions that do not have any activity:

Untitled-1.fw

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…

XML API Tips: User Manager Associations

A common workflow for Adobe Connect admins is to associate users to managers via the UI.

In the UI, you can navigate to the Administration > Users and Groups > {select a user} > Edit Team Members area to select users who will be direct reports of that manager.

This information will show up in the ‘My Profile‘ > Organization area for the user, where they will be able to see their Manager information (if they have a manager set) and their Team Members (if they are a manager themselves).

But with the XML API, this process is undocumented. Here’s how you accomplish this:

How do I associate a user to a Manager?

http://connectURL/api/xml?action=user-manager-update&manager-id=XXXXXXX&principal-id=XXXXXXX

Where:
action=user-manager-update
manager-id= principal-id of user who is going to be the manager
principal-id= principal-id of the user who is being assigned a manager

Note:
The user-manager-update call is UNDOCUMENTED.

Results:

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

How do I disassociate a user from a Manager?

http://connectURL/api/xml?action=user-manager-update&manager-id=XXXXXXX&principal-id=XXXXXXX

Where:
action=user-manager-update
manager-id= the account-id (‘7′ if an on-prem/Licensed customer or a longer numeric value for an Adobe Hosted customer)
principal-id= principal-id of the user who is being assigned a manager

Note:
The user-manager-update call is UNDOCUMENTED.

Results:

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

 

The below IS documented, however it is applicable to this post, so I will include it:

How do I list all direct reports of a Manager?

http://connectURL/api/xml?action=principal-list&filter-manager-id=XXXXXX

Where:
action=principal-list
filter-manager-id= the sco-id of the user who is the manager

Results:

<results>

<status code="ok"/>
<principal-list>
<principal principal-id="XXXXXXXXX" account-id="XXXXXXXXX" type="user" has-children="false" is-primary="false" is-hidden="false" manager-id="XXXXXXXXX" training-group-id="">
<name>USER NAME (FIRST AND LAST)</name>
<login>USER LOGIN VALUE</login>
<email>USER EMAIL VALUE</email>
<display-uid>USER LOGIN VALUE</display-uid>
</principal>
</principal-list>
</results>

 

Using the XML API and Microsoft Excel to obtain additional reporting from Adobe Connect

Sometimes customers need a custom report that is not included in the normal reports in the Adobe Connect UI.   They can obtain this data by running an API call, however the results get displayed in a browser (in an XML result set) and is not in a user-friendly format as-is.  In lieu of actually building an application that can parse and display the XML in a nice format for the user to be able to display in a useful manner, we can simply use Microsoft Excel to display the data in a nice tabbed report format.

An example of this would be as follows:

Say, you want to report on what users are in a particular group within Adobe Connect, and there is no good established report to actually display this data (other than in the datagrid in the Users and Groups area)…

Here’s what you can do.

Log into the account in a browser, as an admin.

Run the following API (or any API you need to run to obtain the data you are looking for):
http://connectURL/api/xml?action=principal-list&group-id=XXXXXXX&filter-is-member=true

Where:

action=principal-list
group-id= principal-id of group you want to report on
filter-is-member=true

 The results will get returned in the browser in XML format (as seen in the screenshot below):

Save the current page as an XML file by going into the browser options and select ‘Save As’ and make sure you save the page as ‘.xml’.

xml-1

 

After saving the XML locally, open up Microsoft Excel (on Windows) and select Data > From XML Data Import.

xml-2

 

Click OK through all the next pop ups that show up after selecting the XML file and just select the defaults:

xml-3 xml-4

 

Once the data loads in the worksheet, it will be formatted in a nice tabbed display as you see below:

xml-5

Passing a user into an Adobe Connect Meeting without the Login Page

Periodically customers want to be able to pass in Guest users into an Adobe Connect Meeting without having those users actually have to pass in a guest name in the Meeting login page.  The scenario here may be that organizations may have an external registration system where users put in their email address, first name, last name, and other data, into a form on their registration portal and they do not want users to have to register (externally) for a Meeting and then put their name or login value in again a second time, on the Meeting login page.  Also, the organization may want to keep close tabs on how the guest name is entered, so it will match their own registration system, for reporting later.  For this, we have a quick and simple solution.

If the meeting is setup for public access (‘Anyone who has the URL for the meeting can enter the room‘) or for the default access level (‘Only registered users and accepted guests may enter the room), then you can simply append ‘?guestName=XXXXXXX‘ to the end of the meeting URL (where ‘XXXXXXX’ would be the value of their name that you want to display in the Attendee List Pod when they are in the meeting).  It would look something like this: https://{connectDomain}/{meetingURL}?guestName=Jim Johnson

The behavior will be:

For access level: ‘Only registered users and accepted guests may enter the room': the user will be let right into the room’s lobby (without seeing the login page) and will see the message: ‘This is a private meeting. Your request to enter has been sent to the host. Please wait for a response.’  Then a host can accept them and they will be let into the meeting as whatever value was appended to the ‘?guestName=’ parameter.

For access level: ‘Anyone who has the URL for the meeting can enter the room': the user will be let right into the room itself, as they normally would, but they never see the login page and their name value in the Attendee List Pod is whatever was passed in in the ‘?guestName=’ parameter.

 

From the integration perspective, the external registration system which mines the user data (name, email, etc.) you’d need to programmatically set this guestName value in the URL for each user.  This can be done in the application which presents the URL to the end users from the registration system and you can put the first name + last name, email address, or whatever other value you want to set in there.