Posts in Category "Events"

How to stop Event pages (CQ) from being indexed

This article (and link below) is intended for Licensed (On-Premise) customers who have a standalone instance or cluster of CQ servers to serve up the Events Management piece of the Adobe Connect platform.  If you would like to stop event pages from being indexed in search engines like Google, you can follow this quick article below on adding robots.txt to the root of the CQ instances.

http://crxdelight.com/2012/02/04/how-to-protect-your-cq-instances-from-google-searches/

Event Template Account Logo will not Publish

Issue: The Connect Events template account logo in AEM does not change when you attempt publish a new template logo

Solution: To change the account logo on Event templates, you need to change the account logo of the Connect account from within Connect Central:

Click on the the thumbnail image to see the Customization page in Connect Central: Administration > Customization > Customize Central

Event-logo-CC.fw

 

For more information on Connect Central customization options see the following help link: Customize the Adobe Connect Central user interface

For more customization options see the following resource: Extensions : Solution extensions

For more information on Events Templates see the following tutorials:

Creating and Editing Event Templates

Resetting the Default Event Templates in Adobe Connect

Creating a Two Person Event Template with Adobe Connect

Event Administration in Adobe Connect 9

Adobe Connect 9: Event Migration Guide

SSL Configuration Checklist for Connect with AEM-based Events

This supplemental checklist alongside the  Adobe Connect installation guide and the SSL Configuration guide, will help expedite your SSL implementation of Connect with AEM-Events:

1. Always begin with a fully functional installation of Connect and AEM-based Events before adding SSL; Do not attempt to secure a server that is not fully tested to run all features without SSL: A server running all features in the clear with no problems manifested is the only place to begin.

2. Decide whether to use hardware-based or software-based SSL and obtain appropriate public certificates and FQDN’s. If needed, see Mohit’s excellent instructions to generate CSRs. If you are using software-based SSL, stunnel can either be installed locally or on a separate server. If you are using hardware-based SSL you will want to refer to the relevant third-party documentation along with that provided by Adobe. For F5 BIG-IP LTM, the following articles along with this blog article and the resources aforementioned will help:

For information about stunnel installation options with Connect 9, see Jim’s blog post on Adobe Connect 9.0.0.1 and 9.1 stunnel installation options. Within the 9.0.0.1 installation folder, under  \Adobe Connect 9.0.0.1\Adobe Connect\Merge_Modules, we provide the installer for  stunnel-4.53.  From there, you can install Stunnel 4.53 for your SSL deployment. Adobe QE has tested stunnel version 4.56 collocated with Connect – installed within the Connect installation directory. These days it is arguably prudent to use the latest security option tested. Depending on the version of Connect you are running, if you wish to use stunnel locally, then you would create and/or populate the stunnel directory under the root install directory: Connect\9.1.2\stunnel.

Click on this thumbnail diagram below to see what it would look like with a hardware-based SSL accelerator:

C9SSLAEMSingle

Click on this thumbnail diagram below to see what it would look like with stunnel collocated with Connect:

C9SSLAEMStunnel

The rest of this checklist & summary will assume stunnel is being used collocated with Connect, but the configuration variables will apply to hardware-based external SSL acceleration options as well and even a casual glance back at these diagrams will help you infer the differences.

The sample file editing offered herein will be based on the single server stunnel example depicted in the diagram above.

3. Four FQDN’s are required: This is how our working example FQDN list would appear in a host file.

  • 192.167.21.176  connectmtg.domain.com
  • 192.167.21.175 connect.domain.com
  • 192.167.21.174:443  cqauthor.domain.com
  • 192.167.21.173:443  cqpublisher.domain.com

4. Four certificates (or a wildcard certificate) is needed; here is the list of certificates for SSL following our example:

  • connectmtg.domain.com
  • connect.domain.com
  • cqauthor.domain.com
  • cqpublisher.domain.com

Note: These are depicted in our working example as a wildcard certificate: domain.com. If the certificates are not trusted public certificates, then meeting rooms will not open; self-signed certificates will not work with meeting unless they are installed on all clients. Place the certificates into the stunnel installation directory: \Connect\9.1.2\stunnel\

5. Backup and edit the stunnel.conf file: in the \Connect\9.1.2\stunnel\ directory to set up the four VIPs and pools:

stunnel.conf for four servers on one
; Protocol version (all, SSLv2, SSLv3, TLSv1)
sslVersion = all
; Some performance tunings
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1
TIMEOUTclose=0
options = DONT_INSERT_EMPTY_FRAGMENTS
; Service-level configuration
[https-vip]
; incoming vip for https (to secure Connect Application Traffic)
; ip address of the server with stunnel on it
; listens on port 443
accept =192.167.21.175:443
; ip of the connect server
; send the unecrypted request to port 8443
connect =127.0.0.1:8443
; Certificate info for Connect cert key in stunnel root
cert = domain.com.cert.pem
key = domain.com.key.pem
[rtmps-vip]
; incoming vip for fms (to secure Connect Meeting Traffic)
accept = 192.167.21.176:443
; ip of the fms server
; Send unencrypted request to 1935
connect = 127.0.0.1:1935
; Certificate info for Connect meeting cert key in stunnel root
cert = domain.com.cert.pem
key = domain.com.key.pem
[CQ_Author-vip]
; incoming vip for CQ-Author (to secure AEM-based Events Authoring)
accept = 192.167.21.174:443
; ip of the CQ Author server
; Send unencrypted request to 4502
connect = 127.0.0.1:4502
; Certificate info for CQ Author cert key in stunnel root
cert = domain.com.cert.pem
key = domain.com.key.pem
[CQ_Publisher-vip]
; incoming vip for CQ-Publisher (to secure AEM-based Events Publishing)
accept = 192.167.21.173:443
; ip of the CQ Publisher server
; Send unencrypted request to 4503
connect = 127.0.0.1:4503
; Certificate info for CQ Publisher cert key in stunnel root
cert = domain.com.cert.pem
key = domain.com.key.pem

6. Next backup and edit the custom.ini file: By default, the custom.ini will point to 4502 and 4502 for CQ Author and Publisher respectively; you must change the links to reflect https rather than http and also change the  names to the correct FQDNs and also enable SSL for Connect with these following entries:

CQ_AUTHOR_SERVER=https://author.adobeconnect.com
CQ_PUBLISH_SERVER=https://publisher.adobeconnect.com
DOMAIN_COOKIE=adobeconnect.com
ADMIN_PROTOCOL=https://
SSL_ONLY=yes
RTMP_SEQUENCE=rtmps://external-host:443/?rtmp://localhost:8506/

7. Next backup and edit the server.xml file; in the \appserv\conf\ directory; uncomment two sections depicted here to enable SSL:

<Executor name=”httpsThreadPool”
namePrefix=”https-8443-”
maxThreads=”350″
minSpareThreads=”25″/>

<Connector port=”8443″ protocol=”HTTP/1.1″
executor=”httpsThreadPool”
enableLookups=”false”
acceptCount=”250″
connectionTimeout=”20000″
SSLEnabled=”false”
scheme=”https”
secure=”true”
proxyPort=”443″
URIEncoding=”utf-8″/>

Note: Be sure to test the server.xml file for correct editing by opening it in a browser and viewing any syntax errors.

8. After configuring the stunnel.conf, the custom.ini and the server.xml file for all four server instances, stop all five the services in the following order:

  • Adobe Connect CQ Author
  • Adobe Connect CQ Publisher
  • Adobe Connect Server
  • Adobe Flash Media Server
  • stunnel

9. After all services are completely stopped, start all five services in reverse order; do not cheat and just restart each one successively.

  • stunnel
  • Adobe Flash Media Server
  • Adobe Connect Server
  • Adobe Connect CQ Publisher
  • Adobe Connect CQ Author

10. Open a browser on the Connect server; go to localhost:4502 and log into CQ5 Author as an administrator and edit the URL

  • Select CRXDE Lite on the menu list on the right side of the screen
  • Go to: content>connect>c1>jcr:content
  • Scroll to the serverURL line
    • Edit the URL for https
    • https://cqauthor.domain.com

11. Open a browser on the Connect server and go to localhost:4503 and log into CQ5 Publisher as an administrator and edit the URL

  • Select CRXDE Lite on the right menu list
  • Go to content>connect>c1>jcr content
  • Scroll to the serverURL line
    • Edit the URL for https
    • https://cqpublisher.domain.com

12. Open a browser on the Connect server and go to localhost:4502/system/console/configmgr and log in as an administrator and edit the author externalizer name and statistics URL

  • Scroll to and edit the Day CQ Link Externalizer and edit the hostname value to reflect the FQDN of the Author server
  • cqauthor.domain.com
  • Scroll to and edit the Day CQ WCM Page Statistics and edit the localhost:4502 URL to reflect the FQDN of the Author server and HTTPS
  • https://cqauthor.domain.com/libs/wcm/stats/tracker

13. Open a browser on the Connect server and go to localhost:4503/system/console/configmgr and log in as an administrator and edit the publisher externalizer name and statistics URL

  • Scroll to and edit the Day CQ Link Externalizer and edit the hostname value to reflect the FQDN of the Publisher server
  • cqpublisher.domain.com
  • Scroll to and edit the Day CQ WCM Page Statistics and edit the localhost:4503 URL to reflect the FQDN of the Author server and HTTPS
  • https://cqpublisher.domain.com/libs/wcm/stats/tracker

14. Stop all services and and restart as shown in steps 8 & 9 or reboot the server

15. Log into Connect and test all features including the Events module.

Troubleshooting appendix:

  • Check to make sure all five  services are running and start any that are not running.
  • Once all the services are up, click on the stunnel.exe icon in the stunnel directory and insure that stunnel runs without errors
    • If stunnel.exe throws an error then examine the stunnel.conf for syntax problems
    • If stunnel.exe starts successfully then look elsewhere for problems
  • If  Firefox browsers Fail to Connect when stunnel is used to secure Adobe Connect, then double check to be sure that the
    • sslVersion = all
    • fips = no
  • To make certain the help files are served via SSL, follow the instructions in Jim’s blog article: Changing the Help Links to use HTTPS://
  • Make sure there is not a passphrase on stunnel: see Jim’s blog article Adobe Connect Stunnel prompting for passphrase when server/services restarts
  • If stunnel does not start with Connect upon reboot, this technique will help: Stunnel does not Startup with Connect
  • Depending on the version of Connect you are running, you may need to add the certificate to the java CA certificates in Connect in order to allow images in the AEM-based Events module to appear in Connect. Ignore this step unless you are running Connect 9.0.0.1 and even then, if at all possible, simply use a later version of Connect instead as this issue has been fixed and this workaround is made superfluous for later versions:
    • For 9.0.0.1, export and then import the SSL certificate: Log into Connect and click on the lock in the URL line to the left of HTTPS and click the button in the pop-up: More Information>View Certificates>Details>Export to export the SSL certificate. Save the certificate in the jre\bin directory in the root install directory for Connect: Connect\9.1.2\jre\bin
    • Use the command prompt to complete the importation: F:\Connect\9.1.2\jre\bin> keytool -import -trustcacerts -alias connect -file certificate-name -keystore cacerts
      • The default password is changeit.
      • Overwrite any existing certificate.
      • The italicized alias connect is a variable
      • The italicized certificate-name must match the name of the certificate

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.

 

Issue with upgrading CQ (Events) on standalone server

Note:

This article is for On-Premise (Licensed) Adobe Connect customers with the Events module who may be thinking of upgrading to 9.1.

This only applies to customers who meet ALL of the following criteria:

  • Customers who have installed CQ at the Adobe Connect 9.0 level (officially 9.0.0.1) and who are upgrading to 9.1 (officially 9.1.1)
  • Customers who have installed CQ on a standalone machine (so not on the same server or servers as Adobe Connect)
  • Customers who have installed CQ on a drive other than C:/.  

We have uncovered an issue with upgrading CQ (Events Module) from 9.0 version to 9.1 version on a standalone server where you would have installed CQ on a drive other than the C:/ drive.

With Adobe Connect 9.0.0.1 (the full 9.0 installer’s actual version), we introduced Adobe CQ as the backend for the Events module in Adobe Connect.  This required you to install CQ on either the same server as Adobe Connect, or on it’s own dedicated (preferred) server or servers (if in a cluster).  A typical workflow would have been to install the CQ application for both the Author and the Publisher instances of CQ on a drive other than the C:/ drive on the server (or servers).  The full installation of the original 9.0 version of CQ would have given  you the option of installing CQ wherever you wanted (say for this example, the ‘E:/’ drive).

With the latest (as of October, 2013) version of Adobe Connect and CQ (9.1.1 officially), we introduced a new version of CQ.  So customers who already installed CQ at version 9.0, would have already had CQ on a machine and would be upgrading CQ by running the new 9.1 .1 Adobe Connect installer on that server.  This is where the problem is.  The installer, for an upgrade to CQ will not give you the option to choose the installation folder/location. It just goes through and installs in the C:/ drive, which is obviously not correct if you installed in another location.

There is a workaround for this.

For now, you can work around this problem by adding a property value – USER_INSTALL_DIR=<old Installation directory> to the file <INSTALLER_ROOT>\Standard_DVD\Connect\9.1.1\Disk1\InstData\VM\cps.properties. Any valid installation path can be provided but format of the old installation path has to be either E:/Connect or E:\\CONNECT (or whatever drive letter you are using).

Note: Again, the full installation of 9.1 will allow you to choose the installation directory. The issue detailed above is only for upgrades from 9.0 to 9.1 CQ.

This issue with the installer will be addressed in Adobe Connect 9.2, which will be coming in Q1 of 2014.

 

Is there a way to set a filter on the Event Catalog Page ?

Problem Description:-  User would like to know if there is a way to set a filter for end-users around the world who can access their organisation website and click on the public link which is associated with their site event catalog page.

For instance if they share their catalog page publically on a website : https://pub-server/content/connect/c1/7/en/events/catalog.html

All the end-users around the world who navigate to this link, can see the upcoming events. Therefore, client would like to know if there is a way to set a filter that they cannot see all the upcoming events and can only see which the host or the organization wants.

Solution :-

To achieve this use separate catalogs for different audiences. You can create folders in your Events area and put different events in each catalog. You can then make the folder public which will turn it into a separate catalog with a unique URL.

Event-Catalogs

 

 

 

Connect On-Premise Installer for 9.1.1 on the Adobe LWS – Version Questions

Issue: There was an earlier version of 9.1 that looks very similar to the current (9.1.1), but the earlier version is missing some important updates. This will be fixed with the release of Connect 9.1.2

Solution: The normal way to check the Connect version is to poll the version.txt file at any Connect account domain name. To see an example, check this Adobe Connect hosted account for one of our training partners:

http://reximedia.adobeconnect.com/version.txt

The output from this shows the versions of all components of the release: package=9.1.1.80.20130729.1194934… patch=CPS_9.1.1.55_9.1.1.59, patch=CPS_9.1.1.59_9.1hotfix.12

This normal means of checking the build will not work with the 9.1.1 released installer. See the output from its version.txt:

package=9.1.1.92.20130804.1194934….

The version.txt is missing the patch numbers.

Workaround technique to find the version:

Look in the downloaded zip installer for versionInfo.xml

  • The date should read: 2013/09/27:08:12:57
  • The build should read: 9.1.1.5.20130924.1215873

This is valid as of the writing of this tech-note. It is safe to say that if you see a later date and build number on a full installer download, then you are not going to see this problem and your version.txt will be correct.

Event vs. Session Expected Number of Participants for Seminars

When you create a Seminar SESSION, depending on your Seminar License quota for the number of concurrent users, it will give you the Expected Number of Participants drop down (to select over or under 600 users).

The values are:

  • Large Seminar Session (> 600 participants)
  • Regular Seminar Session (Up to 600 Participants)

If your Seminar License allows for over 600 concurrent seats, you get this option when you create a Seminar Session for a Seminar Room that exists under that License. If the quota on the License is under 600 for a maximum concurrency, you do not see this option when creating a session and it defaults to a ‘Regular’ session.

sessionload

 

However when creating an EVENT in the Event Management area and point it to a Seminar Room, you do not get presented with an option to select a Large Seminar Session (> 600 participants) or Regular Seminar Session (Up to 600 Participants).  It will just assume the maximum for the License.  So if you select a Room to point an Event to, which resides in a Seminar License folder, which has a quota of over 600, the default for the Event ‘Session’ will be ‘Large Seminar Session (> 600 participants)’ (although you won’t see this referenced in the information for the Event).

 

 

Event Administrator or Account Administrator group permissions do not allow a user to edit AEM/ CQ Events templates

Event Administrators or Account Administrators group permissions do not allow a user to edit AEM/ CQ Events templates

Note: This issue applies to Connect version 9.1 for amelioration of Adobe Connect bug # 3629575 scheduled to be fixed in a 9.1 point release.

Issue: Connect users with only Event Administrator and/or Account Administrator group permissions are not able to edit the AEM/CQ Events templates; this happens with migrated Connect accounts. This article applies to Connect hosted accounts that have  been migrated.

To reproduce the problem: Create a user with Event Administrator or Account Administrator group permissions and log in as that user. Go to the Events management tab in CPS and try to edit an Event template. The result will be the following error:

No resource found

Cannot serve request to /content/connect/c1/##########/en/events/email/shared/absentee.html in /libs/sling/servlet/errorhandler/404.jsp

The workaround for this issue is to add Event Managers group permissions for users with Event Administrators/Account Administrators permissions to facilitate editing of Events templates. After adding the user to the Event Managers group, be sure to clear the browser cache.

Untitled-1.fw

Account Administrators and Event Administrators who are not Event Managers will not be able to open AEM/CQ templates belonging to migrated AEM/CQ microsites.

Empty session in the redirect after a user logs into to an Event

If you have recently upgraded to Adobe Connect 9.1 with the Events Module, you may run into a problem where after your users log into an Event via the Event Login page, they are redirected to the Adobe Connect login page with an empty session variable in the URL.  So instead of immediately letting the user into the Event (be it a Meeting, Training Course, etc) it simply redirects the user back to the Adobe Connect login page with the URL: https://{connectURL}/{eventURL}?session= .  

This is a known issue where the CQ packages for 9.1 were not applied with the installer if this was an upgrade from a previous version of Adobe Connect.

To resolve this issue, steps must be taken to update the CQ packages on the Author and Publish instance of every CQ server in the cluster/environment.

Here are the steps.  Please read this carefully.

Updating the CQ Instance for Author and Publisher after upgrading to Adobe Connect 9.1

These steps below are first done on the CQ Author instance on the CQ server, which has a 4502 port value after the FQDN. The EXACT same steps are applicable for the Publisher instance at port 4503. What you have to do is follow these steps through to the end on the Author instance (port 4502) and then REPEAT all the way through for the Publisher instance (port 4503).

First, download the following files to all the CQ servers you need to update:

https://connecttech.adobeconnect.com/system/download?download-url=/_a89803438/p7srku5tnzo/output/&name=ConnectEventApp.jar

https://connecttech.adobeconnect.com/system/download?download-url=/_a89803438/p48svq6kemn/output/&name=connect-osgi-service.jar

https://connecttech.adobeconnect.com/system/download?download-url=/_a89803438/p6vst873mv1/output/&name=cq-5.5.0-hotfix-NPR-2061-1.0.jar

These steps below are documented for performing first on the CQ Author environment and for the basis of this document, I will reference the Author instance when referring to the URLs to navigate to. HOWEVER, after you are done with these steps on the Author instance of CQ (port 4502), the EXACT SAME steps need to be cycled through again, in their entirety on the Publish instance of CQ (port 4503). For the sake of making this document as brief as possible, I did NOT repeat all the screenshots and steps for Publisher, as they are exactly the same, except a different port (if the CQ Author and Publish instances are on the same machine). If they are on separate machines, you’d obviously need to perform this on that other machine. You also need to do this on EVERY CQ server in the cluster (if you have a cluster of CQ).

On the CQ Author Server, navigate to:

http://{CQURL}:4502/crx/packmgr/index.jsp (where {CQURL} value is your FQDN for CQ)…

cq1

 

Log in with your admin user/password. (If you don’t login with user/pass you will see ‘No packages found’ when looking at the Package Manager).

Once into the CRX Package Manager (shown below):

cq2

 

 

Make sure you are logged in as an ‘admin’ (in top right-hand corner):

cq3

Look at the ConnectEventApp.zip (the first package listed in the list). If the ConnectEventApp.zip’s icon is a blue cube (as shown above) and the size is 8.7MB, it was NOT updated by the Adobe Connect 9.1.1 installer and needs to be deleted and updated with the new package.

The old package that should be updated would look like this:

cq4

 

The new package would look like this (it will have the Adobe Connect Logo and will be a larger 10.4 MB in size):

cq5

 

You need to Delete the old ConnectEventApp.zip package and upload the new one (downloaded from the link at the top of this document).

First, click on the ‘ConnectEventApp.zip’ package name in the list to expand the information and options below it.

cq6

 

 

Then click the ‘More’ dropdown in the top right-hand corner of the options menu and select ‘Delete’ from the dropdown options (shown below):

cq7

 

 

Confirm the deletion by pressing ‘Delete’ button:

cq8

 

You will now see the package is deleted and it gets removed from the list.  You also see the deletion being logged at the bottom in the Activity Log area.  If you see a red error in there, it is probably because you are not logged in as an admin, therefor it won’t be deleted.

cq9

 

 

Now, click on the ‘Upload Package’ link at the top of the page (shown below as well):

cq10

In the ‘Upload Package’ pop up window, navigate to your ConnectEventApp.jar that you downloaded above, and select it.  Do NOT click ‘Force Upload’ option.

cq11

 

 

Once the package has finished uploading, you will now see the following (below) in your packages:

cq12

 

 

Now you need to INSTALL the package.

In the top right-hand corner you see the ‘Install’ link in blue (shown below as well):

cq13

 

Click Install.

In the ‘Install Package’ dialogue that comes up, be sure to select ‘MERGE’ as the Access Control Handling option. By default this is ‘Overwrite’. Select ‘Merge’ and then click the ‘Install’ button.

cq14

 

 

You will see a lot of logging in the ‘Activity Log’ area below the package until it finishes with a ‘Package installed’ message (shown below).

cq15

 

Now navigate to CRXDE Lite on the CQ Author server:

http://{CQURL}:4502/crx/de/index.jsp (where {CQURL} value is your FQDN for CQ)…

Drop down through the following path shown below: (content>connect>c1>jcr:content)

cq16

 

Look in the Properties tab and confirm that:

The ‘cookiePrefix’ value is equal to the DB_PREFIX= value in your custom.ini located on your Adobe Connect server at: C:\Connect\9.1.1\custom.ini.

cq17

 

Look at the ‘serverUrl’ value and make sure it matches your Adobe Connect Host value (FQDN) of your Adobe Connect system.

cq18

 

This is the full view:

cq19

 

Now navigate to the system console on the CQ Author server:

http://{CQURL}:4502/system/console (where {CQURL} value is your FQDN for CQ)…

Log in again as an admin if it prompts you.

cq20

 

 

On this page, search for ‘connect’ (or scroll down until you see the item below).

You will be taken to the item (bundle): ‘connect-osgi-service’

 

cq21

 

Click on the item to expand:

cq22

 

 

Confirm the version of the bundle.

cq28

 

 

The latest version for 9.1 should be:   1.0.0.20130716-1834

If your version is different (older) than this version (as in this example where my version is: 1.0.0.20120726-0101), you need to update the bundle.

Click ‘Install/Update’ button in the header above the item information (shown below):

cq23
On the ‘Upload/Install Bundles’ pop up window, click on:

‘Start Bundle’ and make sure it is checked.

Click ‘Choose File’ button and navigate to your ‘connect-osgi-service.jar’ that you downloaded from the top of this document.

Click ‘Install or Update’ button.

cq24

 

Once this is done, search again for ‘connect’ in this page and find the ‘connect-osgi-service’ item again.

Click on the third button on the right (the one that looks like two arrows moving in different directions and it will say ‘Update’ if you hover over it with your pointer) (shown below):

cq25

 

It should update quickly, and show ‘Active’.

 

Now, REPEAT all the steps above for the PUBLISHER instance of CQ. All the URLs and steps will be the same except the URLs will use 4503 rather than 4502.

Once you do this through and repeat for the Publisher instance at 4503, Stop and Restart the Services.

  • First stop Adobe Connect CQ-Author, then stop Adobe Connect CQ-Publish.
  • Then start Adobe Connect CQ-Author, then start Adobe Connect CQ-Publish.

cq26

 

Remember to clear your browser cache!!!

Now test your Events to see if they are working correctly.

Addendum:

If you do not have the ‘cq-5.5.0-hotfix-NPR-2061-1.0.zip’ package visible in your Package Manager on both 4502 and 4503 (the same place you uploaded and installed the ‘ConnectEventApp.zip’ file), please follow the same steps to Upload this package (which can also be downloaded from the links above) and Install on both 4502 and 4503). Remember to upload, and then install choosing the ‘Merge’ option. Once this uploads, it should show up in the list as below:

cq27

If you already see that hotfix, you do not need to do this step. If you do have to add this hotfix, please do so and then stop/restart the CQ services again. This also needs to be done on EVERY CQ Author and Publisher instance in the cluster.