Archive for July, 2013

Telephony service monitor

Issue -: You need to check the connect telephony service availability as we have it for the connect app (/servlet/testbuilder)

Solution -: Use the telephony-service health check api to get telephony service status as follows:

http://<Your-Connect-URL>:<port>/api/xml?action=get-health&shared-secret=<secret>

Example – http://my-connect-server:9080/api/xml?action=get-health&shared-secret=breeze

On executing this API , You would get the below XML Response:

<results>
<status code=”Ok”/>
<server-health>
<status>normal</status>
<memory-usage>122880</memory-usage>
<conference-count>0</conference-count>
</server-health>
</results>
 
Parse the XML results from your custom app.

Note -:

1.This API has to be executed in web browser or any other custom web based app/AIR.

2. This API expects port 9080 to be opened between connect server and API requesting agent.

3. Tested on standalone connect server.

4. On custom.ini the TELEPHONY_SERVICE_SHARED_SECRET parameter is set to breeze (It is on encrypted format).

 

 

Adobe Connect does not pull all the questions from the Quiz created in captivate 6

Problem: = Quiz created in Captivate 6 does not pass all the information to Adobe Connect 9

 

Solution: = Now in order to make it do so, you can choose from the two options mentioned below.

 

First Option: = Publish the Captivate Project for Adobe Connect.

 

  1. Open the Captivate project
  2. Click on Edit.
  3. Go to Preferences>Click on Reporting and from the drop-down select Adobe Connect
  4. Publish the Project.

captivate1

 

Second Option:=

  1. Open an Adobe Captivate project.
  2. Select Edit > Preferences (Windows) or Adobe Captivate > Preferences (Mac OS).
  3. In the Category panel, expand Project and select Publish Settings.
  4. Select Publish Adobe Acrobat Connect Pro Metadata.
  5. Click OK.

Captivate2

This should resolve your problem. In case the problem still persist please contact support.

Adobe Connect with H.323/two-way video telephony-support.

Problem : 1. – Does Adobe Connect works with H.323? If yes, is it an on-premise solution only or also achievable on hosting environment for adobe?

2. – If there are any plans in future for supporting two-way video telephony.

Answer : 

No, we don’t work with H.323 directly – only SIP. However you could work with an external service to bridge your H.323 devices with our servers. There are companies that provide cloud-based services that will communicate with legacy H.323 hardware and then use SIP to communicate with Connect to provide the video and audio directly.

 

 

What rights an Event Manager holds as in comparison to Event administrator in Adobe connect 9 ?

Topic Discussed : Rights for both Event Administrator and Event Manager:

Solution : In connect 9 there are two new system groups added for event license users, those are Event Administrator and Event Manager.

First we will talk about an Event Administrator :

An Event Administrator :

  • Can create any number of custom templates.
  • Have full control over the Event Catalog layout and branding.
  • Can create shared templates, limit tags in the Event Catalog, create Reply To options for email triggers, and assign Event Manager role to the registered users.
  • Manage the event tags, which in turn make it possible to filter the events in the Event Catalog.
  • Can update, rename, delete, or copy existing templates
  • Can apply the Featured Event tag to display an event in the Featured Events section of the Event Catalog
  • Members of the Event Administrators group assign users to the Event Managers group, manage shared templates, event tags, and email aliases.
  • Event Administrators can also configure analytic’ s.

Now in comparison if talk about event manager :

An Event Manager :

  • Assigns attendee roles when setting up the event in the Participant Management tab.
  • Can create private template
  • Can only create a private copy of the shared templates.
  • Can only create a private copy of the existing templates.
  • Members of the Event Managers group can create events and manage their own folders in the Event library.
  • If you assign a user to this group, Adobe Connect creates a folder for this user in the User folder of the Event library.
  • Can manage only their individual My Events folders in the User Events folder.
  • Can manage events in the Shared folders if they are hosting the event and have Manage permissions for the folder that contains the event.
  • Manage their own Event library user folder, performing all file-management functions, and create and manage all aspects of an event in this folder.
  • Can view event reports.

 

Connect throws an error “The item is not selected” or “Please select an item” when user try to create a new event.

Problem : ( After applying patch 9.0.4 ) User when creates a new event on connect, experience an error stating “The item is not selected” or “Please select an item”

Solution : 

Check in the debug log on connect server and look for “REMOTE_CQ_TEMPLATE”. You will see this item is either missing or not found in the Database table name “PPS_EVENT_DETAILS”. The debug log would capture an entry and throws an exception stating “REMOTE_CQ_TEMPLATE” is not found or invalid.

Reason why this happens is because when user apply the patch for 9.0.4 they definitely have not executed the SQL queries provided in the patch ( 9.0.3.0 and 9.0.4.0). The “REMOTE_CQ_TEMPLATE” is present in the script 9.0.4.0.

Therefore go to the Database, make sure the current data base is selected and run the two scripts in sequence ( First 9.0.3.0 and then 9.0.4.0 ).

This should resolve your problem. In case the problem still persist please contact support.

 

 

Adobe Connect Event Template throws an error “No resource found”

Problem : Some users

–  When trying the event registration page experience ” No Resource found” error.

–  When edit the event template and activate, the edits are not being saved or reflects on the template where the change is made.

–  When click on different custom/system templates experience “No Resource found”

Solution :

For users who are on our hosted server or in other words who are using our hosted services, if the above mentioned problem is what you witness/experience at your end. Please open a ticket with our base support team at 1-800-422-3623.

For license users/Users who have Adobe connect installed on premises.

Please understand the workflow of Events with CQ Author Server and CQ Publish Server. Here is the brief description on that:

There is a concept/process called as “Replication” which should be working between the two servers. We have a Replication Agent on CQ author server which uses a mechanism to publish ( activate ) content from an Author to a Publish environment and we have a “Receiver Servlet Agent”  on CQ Publish server which lifts such packaged content from the replication queue on CQ Author server. Replication to a publish instance takes place in several steps : ( Follow the figure below while i explain here )

 

file

  • The Author requests that certain content to be published (activated); this can be initiated by a manual request, or by automatic triggers which have been preconfigured in the system.
  • The request is passed to the appropriate default replication agent; an environment can have several default agents which will always be selected for such actions.
  • The replication agent “packages” the content and places it in the replication queue.
  • The content is lifted from the queue and transported to the publish environment using the configured protocol; usually this is HTTP.
  • A Servlet in the publish environment receives the request and publishes the received content;

Now Considering the above fact that i just explain here:

If a user is experiencing the problem statement shown above in the start of this blog.

There are two important things you need to check in such situations : 

First check if the replication agent exist or not and if its not, do as explained below:

  • Navigate to the CRXDE | Lite page on the author environment http://localhost:4502/crx/de/index.jspAuthor-Login   CRXDE-Lite
  • On the Left Pane where you see the Tree folder structure Go  to folder ETC ( click on plus sign )

CRXDE-Lite-etc

  • Now look for folder name Replication underneath that folder ( Click on Plus sign )

CRXDE-Lite-etc-replication

  • –>Now click on a plus sign for Node name “agents.author”  which is your replication agent node, if this node does not exist ( Call us ) else —>Underneath that folder look for a Node name “Publish_Your_Publish_Instant_Name”, i am typing the name in generic form.

Note:- In the picture below you will see the replication agent name for my local server as “Publish_connect-publish_dev_com” because my public instance FQDN name is Connect-publish.dev.com.

 

CRXDE-Lite-Etc-Replication-Agent

If this does not exist, you will experience what i have explained in this blog. To fix this you need to recreate this node by following the below steps:

Click on the CRXDE-Lite home page

CRXDE-Lite-HomePage

Navigate to Tools option on the home page.

CRXDE-Lite-HomePage-Tools

Under the tools option, Navigate to the replication folder and hightlight the “Agents on Author” option as shown below:

CRXDE-Lite-HomePage-Tools-ReplicationAgent

Now on the right pane click on the New page option as shown below :

CRXDE-Lite-HomePage-Tools-ReplicationAgent-New

You will see a window where you can create a new Replication agent. You can type your Replication Agent Name and Choose the option Replication Agent then hit the create button, as shown below:

CRXDE-Lite-HomePage-Tools-ReplicationAgent-New-Window

Now you will see a new replication Agent instance is created underneath your Replication agent Node on CRXDE-Lite page as shown below :

CRXDE-Lite-etc-replication-2

Now Double click on the agent you just created and go to edit under settings. ( Remember it will be disabled as shown below untill we check the enable option )

Replication-agent-1

Change the name to Replication agent under the settings TAB and make sure its enabled, so check the box called Enabled.

Replication-agent-2

Now go to the Transport Tab and Change the URI : http://localhost:4503/bin/receive?sling:authRequestLogin=1. Instead of localhost here, you can put your CQ publish instance FQDN here and hit ok without making any other change. User Name and Password will be your CQ credentials.

Replication-agent-3

At the end you can do what is explained in the second step below to confirm if replication is successfully Replicating.

Secondly if the replication agent exists and still you are experiencing such issues, please do the following :

  • Double click on the replication agent “Publish_Your_Publish_Instant_Name” and click on “Test connection” link: you should receive “Replication test succeeded". If you do not receive that, call us on our support line. 

Replication-agent-4

Replication-agent-5

Thats about it !

I hope this blog will help you solve most of your issues related to replication.

Thanks !

 

Changing the Help Links to use HTTPS://

For Licensed (On-Prem) Adobe Connect systems, the Help Links will still use HTTP:// instead of HTTPS:// if you have configured SSL for the web application.

To change the protocol for the help pages from http:// to https:// you will need to make a modification to the following file on each server in the Adobe Connect cluster:

\Connect\9.0.0.1\appserv\apps\system\help_redirect.xsl
The section you need to modify is:

<xsl:variable name=”redirectUrl”>

<xsl:choose>

<xsl:when test=”($configurableWebappHelp!=” and /results/params/param[@name=’help’]=$isWebappHelp)”>

<xsl:value-of select=”$configurableWebappHelp”/>

</xsl:when>

<xsl:when test=”($configurableLoginHelp!=” and /results/params/param[@name=’help’]=$isLoginHelp)”>

<xsl:value-of select=”$configurableLoginHelp”/>

</xsl:when>

<xsl:when test=”$HELP_HOST!=””>

<xsl:value-of select=”concat(‘http://‘, $HELP_HOST, ‘/’, $localeId, /results/params/param[@name=’help’])”/>

</xsl:when>

<xsl:otherwise>

<xsl:value-of select=”concat(‘http://‘, $ADMIN_HOST, ‘/common/help/’, $locale, /results/params/param

[@name=’help’])”/>

</xsl:otherwise>

</xsl:choose>

</xsl:variable>

 

Changing the http:// to https:// in both lines.
Save the file.
Then restart the Adobe Connect Service on each server in the cluster after making the change.