Author Archive: Jim Johnson

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…

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>

 

XML API Tips: Adding a Telephony Profile to a Meeting Room

Another one of the undocumented workflows for Adobe Connect with regards to the XML API is adding telephony profiles to Adobe Connect Meeting rooms.

How do I add a telephony profile to a meeting?

https://connectURL/api/xml?action=acl-field-update&field-id=telephony-profile&value=XXXXXXXX&acl-id=XXXXXXXX

Where:
action=acl-field-update
field-id = set to ‘telephony-profile’
value = profile-id value
acl-id = meeting sco-id value

Results:

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

To find the profile-id, you can run the telephony-profile-list API call, which will list the API caller’s telephony profiles.

XML API Tips: Setting/Changing Recording Permissions

One of the undocumented workflows for Adobe Connect with regards to the XML API is working with permission levels of recordings (archives).  A recording can either be Public or Private.

The workflow is similar to that of the permission level for Meetings.  See below for the steps for making a recording Public or Private in Adobe Connect 9.1:

How do I make a Private Adobe Connect Recording Public?

https://connectURL/api/xml?action=permissions-update&principal-id=public-access&permission-id=view&acl-id=XXXXXXX

Where:
action=permissions-update
acl-id= ‘sco-id’ of the recording.
principal-id=public-access
permission-id=view

Results:

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

 

How do I make a Public Adobe Connect Recording Private?

https://connectURL/api/xml?action=permissions-update&principal-id=public-access&permission-id=remove&acl-id=XXXXXXX

Where:
action=permissions-update
acl-id= ‘sco-id’ of the recording.
principal-id=public-access
permission-id=remove

Results:

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

Working with Chat Transcripts

As part of the Compliance and Control settings in Adobe Connect, administrators have the ability to enable Chat Transcripts for logging all chat happening on the Adobe Connect server.  This setting is located at: Administration > Compliance and Control > Recordings and Notice > Enable Chat Transcripts.

chattranscript-1

This transcript is stored on the Adobe Connect server in XML format.  One file for each meeting session.  Each file contains the chat from all chat pods used during that session.  When a meeting session has begun, the chat transcript is not created until someone first starts typing in the chat pod.  At the moment the first chat begins, a new sco (unrelated to the meeting sco itself) is created in the file system ({root}\Connect\content\7\XXXXX-1 where XXXXX = the unique sco-id that gets assigned by Connect for this item). The folder inside of the sco folder will be named ‘input‘ for the duration of the meeting session and will then change to ‘output‘ once the session is ended and fully unloads from memory.  Once the session is over, the chat transcript is available for retrieval.

chattrans2

Only administrators have the ability to navigate to and obtain these chat transcripts.  Here is the workflow you can use to download chat transcripts from the server, if the chat transcripts are enabled:

1) Find the folder for Chat Transcripts on the Connect system.  This is actually a hidden folder and you cannot navigate to it by the normal UI.  To do this, run the following API call:

http://{myServer}/api/xml?action=sco-contents&sco-id=7&filter-like-name=Chat

where sco-contents = the api call.
where sco-id = the account-id of the system (for On Prem Connect licenses this will be ’7′)
where filter-like-name=Chat

It will return the location of the Chat Transcripts folder.

Results will look like this:

<results>
<status code=”ok”/>
<scos>
<sco sco-id=”11011″ source-sco-id=”” folder-id=”7″ type=”tree” icon=”folder” display-seq=”0″ duration=”” is-folder=”0″>
<name>Chat Transcripts</name>
<url-path>/f88952271-4-14/</url-path>
<date-created>2013-10-24T07:30:08.460-07:00</date-created>
<date-modified>2013-10-24T07:30:08.460-07:00</date-modified>
<is-seminar>false</is-seminar>
</sco>
</scos>
</results>

2) Take the sco-id from this result set (in the above example it’s 11011) and run the following call:

http://{myServer}/api/xml?action=sco-contents&sco-id=11011

where the call is again ‘sco-contents’
where sco-id = the sco-id from the result of the first call.

This will list out all the Chat Transcripts on the system and the result will look like this:

<results>
<status code=”ok”/>
<scos>
<sco sco-id=”11140″ source-sco-id=”11137″ folder-id=”11011″ type=”content” icon=”transcript” display-seq=”0″ duration=”645″ is-folder=”0″><name>r35s9d4oskg_0</name>
<url-path>/p16jb8mcs6v/</url-path>
<date-begin>2013-10-24T12:17:15.127-07:00</date-begin>
<date-end>2013-10-24T12:28:00.263-07:00</date-end>
<date-created>2013-10-24T12:17:15.127-07:00</date-created>
<date-modified>2013-10-24T12:28:00.263-07:00</date-modified>
<is-seminar>false</is-seminar>
</sco>
</scos>
</results>

(in this example, I ONLY have 1 transcript on the system, so it only shows 1 above).

If you have a lot of transcripts (which you will after you enable this setting), you may want to filter on the meeting for which the transcripts were from.  This can be done by filtering on the ‘source-sco-id’ which is the sco-id of the meeting that was held.   So if you know the sco-id of the meeting, and you know the date range for which you had the session, you can filter on either the source-sco-id value (which will = the sco-id of the meeting) and/or the date/time fields to limit the data returned and find the transcripts you are looking for.

Now, the URL-path you see above in the second XML result is NOT accessible directly.  You cannot just append the value above (like ‘/p16jb8mcs6v/‘) to the Connect domain and expect to get the transcript.  This is what you need to do to download the file directly:

3)  Take your Connect domain + the url-path value + ‘output/foo.zip?download=zip‘ so the URL example would be:

http://mycomany.connect.com/p16jb8mcs6v/output/foo.zip?download=zip

This will get you a downloaded zip file that contains the Chat Transcript (in XML format).