Macromedia Connect - 9.4 Installation Manual
Migrating, Installing, and Conguring
ADOBE® CONNECT™ 9
Legal notices
Legal notices
For legal notices, see http://help.adobe.com/en_US/legalnotices/index.html.
Last updated 3/1/2015
Contents
Chapter 1: About this document
What this document contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Who should read this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Useful resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Chapter 2: Preparing for migration, installation, and configuration
Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Supported configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Preparing to migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Preparing to install Adobe Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Preparing to install integrated telephony adaptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 3: Installing or Upgrading to Adobe Connect 9.4
Install or upgrade Adobe Connect and associated products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Verify your installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Install Adobe Connect Edge Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Uninstalling the servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
iii
Chapter 4: Deploying and configuring Adobe Connect
Use the Application Management Console to configure Adobe Connect Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Deploying Adobe Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuring Dispatcher for AEM bundled with Adobe Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Deploying Adobe Connect Edge Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Integrating with a directory service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Deploying Universal Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring a video telephony device to work with Adobe Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Deploying integrated telephony adaptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configuring shared storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Configuring Help and Resources links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Configuring account notification settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Configuring the session timeout value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configuring PDF to SWF conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configuring single sign-on (SSO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configuring a reverse proxy in front of Adobe Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Hosting Adobe Connect Add-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Chapter 5: Security
SSL (secure sockets layer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Securing the infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Security tips and resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Contents
Chapter 6: Administering Adobe Connect
Start and stop the servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Managing and monitoring logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Maintaining disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Backing up data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Building custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
iv
Last updated 3/1/2015
Chapter 1: About this document
What this document contains
This document explains how to install, configure, and deploy Adobe® Connect™ 9.4 and the associated components.
The document also covers the pre-install requirements and post-install tasks, such as verification, manual settings,
system security, and administration tasks.
To refer to install, configure, and deploy instructions of the other versions of Adobe Connect, access the installation
guide of other versions at
Who should read this document
This document is intended for users who are installing, configuring, administering, or deploying Adobe Connect and
the associated components. These users include Adobe Connect evaluators, administrators, developers, and Adobe
partners.
http://www.adobe.com/go/learn_Connect_doclisting_en.
1
Conventions used in this document
This document uses the following naming conventions for common file paths.
Name Default value Description
[root_install_dir] C:\Connect The default installation directory where Adobe
[extract_dir] NA The location on your hard disk where you extract the
Connect 9.3 gets installed is C:\Connect\9.3.1\.
However, the content and the logs are placed in
C:\Connect\ folder.
files from the Adobe Connect ESD file.
Useful resources
Following resources can help you learn more about and troubleshoot Adobe Connect.
For information about See
Help and support for Adobe Connect Adobe Connect Help
Adobe Connect forums, tutorials, whitepapers, partner
showcase, events, and latest news
Using Adobe Connect guide Using Adobe Connect guide
Adobe Connect User Community
A list of Adobe Connect resources Adobe Connect resources
Adobe Connect videos on Adobe TV Adobe Connect on Adobe TV
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
About this document
For information about See
2
Adobe Connect downloads and updates like, meeting addins, patches for on-site deployments, extensions, and so on
Get the latest Adobe Connect add-in Latest add-in for Windows
SDKs and learning materials to help developers extend the
functionality of Adobe Connect for end users
Adobe Connect news, announcements, best practices, and
how-to instructions
Troubleshooting the installation, deployment, and
configuration issues
Adobe Connect downloads and updates
Latest add-in for Mac
Adobe Connect Development Center
Adobe Connect official blog
Adobe Connect Support blog
Last updated 3/1/2015
Chapter 2: Preparing for migration, installation, and configuration
Installation requirements
The techniques you use to install Adobe® Connect™ depend on the type of installation you are performing.
• If you are installing Adobe Connect for the first time, review the installation requirements, supported
configurations, and technical overview. Then see
• If you are migrating from a previous version of Adobe Connect, review the information that explains what’s new
in this version. Then see
“Preparing to migrate” on page 6.
Hardware, software, and user requirements
For Adobe Connect and Adobe Connect Edge Server requirements, see www.adobe.com/go/adobeconnect_techspecs.
“Installing or Upgrading to Adobe Connect 9.4” on page 22.
3
Port requirements
The following table describes ports on which users must be able to establish TCP connections.
Number Bind Address Access Protocol
80 */Any Adaptor Public HTTP, RTMP
443 */Any Adaptor Public HTTPS, RTMPS
1935 */Any Adaptor Public RTMP
Note: RTMP (Real Time Messaging Protocol) is an Adobe protocol.
The following table describes the ports open inside a cluster. Each Adobe Connect server in a cluster must be able to
establish TCP connections to all other servers in the cluster on these ports.
Note: These ports should not be open to the public, even if you are not using a cluster.
Number Source Port Bind Address Access Protocol
8506 Any */Any Adaptor Private RTMP
8507 Any */Any Adaptor Private HTTP
Each Adobe Connect server in a cluster must be able to establish a TCP connection to the database server on the
following port:
Number Source Port Access Protocol
1433 Any Private TSQL
The following table describes server ports that Adobe Connect uses to communicate internally. These ports must not
be in use by any other process or program on a server hosting Adobe Connect, or Adobe Connect may fail to start.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Number Bind Address Access Protocol
1111 127.0.0.1 Internal RTMP
2909 127.0.0.1 Internal RMI
4111 */Any Adaptor Internal JMX
8510 127.0.0.1 Internal HTTP
If you are installing an integrated or custom telephony adaptor, each Adobe Connect server in a cluster must have the
following port available:
Number Bind Address Access Protocol
4
9080 or 9443 */Any Adaptor Public if using InterCall or Arkadin
telephony adaptor; internal
otherwise
HTTP
Some integrated telephony adaptors require access to specific ports in addition to the ports listed in the tables above.
These ports are listed in the information for each adaptor; see
“Preparing to install integrated telephony adaptors” on
page 16.
For information about Flash Media Gateway ports, see “Flash Media Gateway ports and protocols” on page 50.
Ports in the range 8088-8093 are used by Adobe® CQ for clustering. For more information, see CRX Clustering. Default
ports for CQ Author and Publish servers are 4502 and 4503, respectively. On the system(s) where CQ is installed, free
the ports in this range.
Supported configurations
Supported Adobe Connect-Adobe CQ configurations
Adobe Connect uses Adobe® CQ technology to create and manage event and email templates, and event catalog. Adobe
CQ Author and Publish servers support authoring and publishing, respectively. CQ Author and CQ Publish servers
can be installed with Adobe Connect either on a single machine or on separate machines. Also, a cluster of CQ Author
server, CQ Publish server, or both, can exist with a server or a cluster of Adobe Connect.
Supported server-database configurations
Adobe Connect uses a database to store information about users and content. The Adobe Connect 9.3 installer
includes Microsoft® SQL Server® 2008 Express Edition and supports Microsoft SQL Server 2008 Enterprise Edition and
Microsoft SQL Server 2012 Enterprise Edition.
The following are the supported Adobe Connect and database configurations:
Single server with embedded database engine Install Adobe Connect on a single computer and install the embedded
database engine (included on the Adobe Connect installer) on the same computer. The embedded database engine is
Microsoft SQL Server 2008 Express Edition.
Note: This configuration should be used only in testing environments, not in production environments.
Single server with SQL Server Install Adobe Connect on a single computer and install MicrosoftSQL Server on the
same computer.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Single server with an external SQL Server database Install Adobe Connect on a single computer and install SQL
Server on another computer.
Single server with multiple external SQL Server databases Install Adobe Connect on a single computer and install
SQL Server on multiple computers (also called a cluster) external to Adobe Connect. Adobe Connect supports
mirroring and clustering of the SQL Server databases.
Multiple servers with an external SQL Server database Install Adobe Connect on multiple servers (also called a
cluster) and install SQL Server on another computer.
Multiple servers with multiple external SQL Server databases Install Adobe Connect on multiple servers (also called a
cluster) and install SQL Server in a separate cluster. Adobe Connect supports mirroring and clustering of the SQL
Server databases.
Supported Flash Media Gateway deployments
Deploy Flash Media Gateway to enable Universal Voice. The following are supported deployments:
Single computer Install Adobe Connect, Flash Media Gateway, and SQL Server on the same computer.
Two computers Install Adobe Connect and Flash Media Gateway on the same computer and SQL Server on a separate
computer.
5
A cluster of computers Install each Adobe Connect server and each Flash Media Gateway on its own computer. If you
are installing Adobe Connect and FMG on separate machines, install Adobe Connect before installing FMG.
More Help topics
“Adobe Connect audio and video conferencing options” on page 16
“Deploying Universal Voice” on page 49
Supported LDAP directory servers
You can configure user authentication against your organization's LDAP directory server and import directory
information into Adobe Connect from your organization’s LDAP directory server. For a list of the supported LDAP
directory servers, see
Note: Any LDAP v.3 directory server may integrate with Adobe Connect. However, only directory servers that have been
tested by Adobe are supported.
www.adobe.com/go/learn_cnn_sysreqs_en.
More Help topics
“Integrating with a directory service” on page 43
Supported content storage devices
You can configure your Adobe Connect system to store content on Network Attached Storage (NAS) and Storage Area
Network (SAN) devices. For a list of supported NAS and SAN devices, see
www.adobe.com/go/learn_cnn_sysreqs_en.
More Help topics
“Configuring shared storage” on page 60
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Preparing to migrate
Migration paths
Run Adobe Connect installer to upgrade from the previous versions of Adobe Connect. The Adobe Connect installer
guides you through the upgrade. The upgrade paths are mentioned below.
Adobe Connect 9.3 installer supports upgrading from the following versions of Adobe Connect:
• Adobe Connect 9.0
• Adobe Connect 9.1
• Adobe Connect 9.2
For more information about upgrading, contact Adobe Support: www.adobe.com/support/programs/connect.
Workflow for migrating to Adobe Connect 9.3
Follow this workflow to migrate to Adobe Connect 9.3 from one of the supported older versions.
1. Test the migration in a non-production environment.
It’s a good idea to take a snapshot of your current production environment and test the migration in a non-production
environment before you migrate your production environment. Once you’ve successfully migrated in a test
environment, proceed to step
2.
6
2. Inform users about the migration.
See “Informing users about the migration” on page 7.
3. (Optional) Back up content and configuration files.
See “Back up files” on page 7.
4. Back up the database.
See “Back up the database” on page 90.
5. Run the Adobe Connect installer.
See “Installing or Upgrading to Adobe Connect 9.4” on page 22. The installer stops the Adobe Connect services and
backs up existing files, including the custom.ini file.
(Optional) Gather information required to install one or more integrated telephony adaptors.
See “Preparing to install integrated telephony adaptors” on page 16.
Verify your installation.
See “Verify your installation” on page 31.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Informing users about the migration
As with any software upgrade—especially one that affects a workgroup—communication and planning are important.
Before you begin migrating or adding modules to Adobe Connect, Adobe suggests that you do the following:
• Allocate enough time to ensure a successful migration. The upgrade should fit into your normal maintenance
period.
• Let users know in advance that they won’t be able to use Adobe Connect during the migration.
• Let users know what types of changes they can expect (such as new features or improved performance) after the
migration. For information about what’s new, see
www.adobe.com/products/connect.
Back up files
The installer creates backup copies of the appserv and comserv directories and the custom.ini file and installs new
versions. The installer does not erase or overwrite the content directory. Customizations done in
ConnectProSvc.conf or TelephonyService.conf files, on a 64-bit OS, are not retained after a migration to Adobe
Connect 9.x.
You can optionally choose to create backup copies of these directories and files.
7
Migrating the existing database to a new machine
Follow this workflow to migrate from using the embedded database to using SQL Server 2008 on a different computer.
Note: You may perform this migration when you migrate to Adobe Connect. You may also perform this migration at any
time after installing Adobe Connect.
1. Install SQL Server on a different computer than the computer hosting Adobe Connect.
Follow the instructions provided by Microsoft to install SQL Server.
2. Back up the embedded database (SQL Server 2008 Express Edition).
See “Back up the database” on page 90.
3. Copy the BAK file from the computer hosting Adobe Connect to the computer hosting SQL Server.
When you back up SQL Server Express Edition, a file is created called breeze.bak (where breeze is the name of the
database).
4. Restore the database on the computer hosting SQL Server.
For more information about restoring SQL Server, see How to Restore a Database Backup.
5. Enter the SQL Server database information in the Application Management Console on the server hosting
Adobe Connect.
Choose Start > Programs > Adobe Connect Server > Configure Adobe Connect Server.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Preparing to install Adobe Connect
Adobe Connect technical overview
An Adobe Connect installation consists of several components: Adobe Connect Central Application Server, Adobe®
CQ, Adobe® Flash® Media Server, Adobe Connect, Flash Media Gateway (Universal Voice), a database, the Adobe
Connect Telephony service, and telephony adaptors for audio conferencing.
The Adobe Connect Central Application Server is built as a J2EE web application running on the Tomcat servlet
engine. Called the application server, it manages users, groups, on-demand content, and client sessions. Some of the
application server’s duties include access control, security, quotas, licensing, and auditing and management functions
such as clustering, failover, and replication. It also transcodes media, including converting Microsoft® PowerPoint and
audio to Adobe® Flash®. The application server handles meeting requests and content transfer requests (slides, HTTP
pages, SWF files, and files in the File Share pod) over an HTTP or HTTPS connection.
Certain components of Flash Media Server (FMS), also called the meeting server, are installed with Adobe Connect to
handle real-time audio and video streaming, data synchronization, and rich-media content delivery, including Adobe
Connect meeting interactions. Some Flash Media Server tasks include meeting recording and playback, timing the
synchronization of audio and video, and transcoding—converting and packaging data for real-time screen sharing and
interaction. Flash Media Server also reduces server load and latency by caching frequently accessed web pages, streams,
and shared data. Flash Media Server streams audio, video, and accompanying meeting data over Adobe’s highperformance Real Time Messaging Protocol (RTMP or RTMPS).
8
Flash Media Gateway integrates Adobe Connect with your SIP/RTP infrastructure. Flash Media Gateway receives
audio from a SIP server and sends it into Adobe Connect meeting rooms. Flash Media Gateway also streams video and
audio from Video Conference devices to the Video Telephony pod. This solution is called Universal Voice.
Adobe Connect requires a database for persistent storage of transactional and application metadata, including user,
group, content, and reporting information. You can use the embedded database engine (SQL Server 2008 Express
Edition) included in the Adobe Connect installer, or you can purchase and install Microsoft SQL Server 2008
Enterprise Edition or Microsoft SQL Server 2012 Enterprise Edition.
Adobe Connect supports several telephony adaptors to enable audio conferencing. You can choose to install one or
more adaptors during the installation process.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Data flow
The following diagram illustrates how data flows between a client application and Adobe Connect.
9
Client application
Web browser
Flash Player
HTTPS:443
HTTP:80
Audio conference participants
Adobe CQ
Author and
Publish Servers
1
HTTP:80
HTTPS:443
A
RTMPS:443
C
RTMP:1935
3
3a 4a
RTMPT:80
HTTP:80
2
B
D
4
HTTPS:443
JDBC or JDBC with SSL
Adobe Connect
SQL database server
Web
Services
API
Audio-conferencing service Video-conferencing service
Web/application
server
port 80
port 9080
Telephony
integration server
port 8506
Flash Media Server
PSTN
HTTP:2222
RTMP:8506
Flash Media Gateway
SIP:5060
RTP:5000~5500
SIP server
The data can flow over an unencrypted connection or an encrypted connection.
Unencrypted connection
Unencrypted connections are made over HTTP and RTMP and follow the paths described in the table. The numbers
in the table correspond to the numbers in the data flow diagram.
Number Description
1 The client web browser requests a meeting or content URL over HTTP:80.
2 The web server responds and transfers the content or provides the client with information to connect to the meeting.
3 The client Flash Player requests a connection to the meeting over RTMP:1935.
3a The client Flash Player requests a connection to the meeting but can only connect over RTMP:80.
4 Flash Media Server responds and opens a persistent connection for Adobe Connect streaming traffic.
4a Flash Media Server responds and opens a tunneled connection for Adobe Connect streaming traffic.
Encrypted connection
Encrypted connections are made over HTTPS and RTMPS and follow the paths described in the table. The letters in
the table correspond to the letters in the data flow diagram.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Letter Description
A The client web browser requests a meeting or content URL over a secure connection on HTTPS:443.
10
B The web server responds and transfers the content over a secure connection or provides the client with information
C The client Flash Player requests a secure connection to Flash Media Server over RTMPS:443.
D Flash Media Server responds and opens a secure, persistent connection for Adobe Connect streaming traffic.
to connect to the meeting securely.
Telephony data flow
The following diagram illustrates how data flows between telephony services and Adobe Connect.
Database server
A
Adobe Connect
B
F
E
Connect Central
Telephony Service
Process
Adaptor
C
Conference
Bridge
D
Flash Media Server
G
Adobe Connect meeting client
A. Persistence. B. Service management and failover, service connection and session brokering, and user data provisioning and access. C. Native
commands and events using proprietary vendor APIs for conference control. D. Commands and events using RPC calls. E. Provisioning.
F. Telephony service request. G. Telephony commands and state.
Installation workflow
The following steps help you design, install, and configure an Adobe Connect system. Some steps require you to make
a decision, and other steps require you to complete a task. Each step refers you to background information about the
decision or task.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
1. Choose which database to use.
For more information, see “Choosing a database” on page 13.
2. If you chose SQL Server in step 1, install it.
For more information, see the SQL Server documentation.
Note: If you are installing the embedded database, you don’t have to perform this step.
3. (Optional) Choose and gather information needed for installing telephony adaptors.
If you are installing one or more of the integrated telephony adaptors, collect the information that the installer
requires. For more information, see
4. Install Adobe Connect and the selected components.
“Choosing to install integrated telephony adaptors” on page 14.
During the installation of Adobe Connect, you can also install Adobe CQ Author and Publish servers, embedded
database engine, one or more telephony adaptors, and Flash Media Gateway (Universal Voice). See
“Installing or
Upgrading to Adobe Connect 9.4” on page 22.
5. Verify that Adobe Connect and the selected components are installed correctly.
For more information, see “Verify your installation” on page 31.
11
6. Deploy Adobe Connect.
For more information, see “Deploying Adobe Connect” on page 36.
7. (Optional) Integrate Adobe Connect with your infrastructure.
There are many possibilities for integrating Adobe Connect into your organization’s existing infrastructure. It’s a good
idea to verify that Adobe Connect is functional after configuring each of these features.
Integrate with Adobe Omniture Adobe Connect 9 uses the Adobe Omniture technology to provide detailed event
analytics reports. Adobe SiteCatalyst integration involves providing the credentials to Adobe’s Omniture website in
Adobe Connect configuration. For more information, contact Omniture support at
http://www.omniture.com/en/contact/support.
Integrate with a SIP provider Integrate Adobe Connect with your organization’s SIP server or a third-party SIP
provider (also called a VoIP provider) to provide seamless audio conferencing. See
“Deploying Universal Voice” on
page 49.
Integrate with an LDAP Directory Integrate Adobe Connect with your organization’s LDAP directory server so you
don’t need to manage multiple user directories. See
Configure a secure sockets layer Conduct all Adobe Connect communication securely. See “SSL (secure sockets
“Integrating with a directory service” on page 43.
layer)” on page 74.
Store content on NAS/SAN devices Use network devices to share content storage duties. See “Configuring shared
storage” on page 60.
Host Adobe Connect Add-in Users can download the Adobe Connect Add-in easily from Adobe servers. However, if
your organization’s security policy doesn’t allow external downloads, host the add-in on your own server and still
retain a great user experience. See
“Hosting Adobe Connect Add-in” on page 72.
8. (Optional) Choose whether to install Adobe Connect in a cluster.
For more information, see “Choosing to deploy Adobe Connect in a cluster” on page 12.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
9. (Optional) Choose whether to install edge servers.
For more information, see “Choosing to deploy Adobe Connect Edge Server” on page 14.
Choosing to deploy Adobe Connect in a cluster
It is possible to install all Adobe Connect components, including the database, on a single server, but this system design
is best used for testing, not production.
A group of connected servers, each doing an identical job, is usually called a cluster. In an Adobe Connect cluster, you
install an identical copy of Adobe Connect on each server in the cluster.
Note: When you install Adobe Connect in a cluster, use a supported SQL server and install it on a separate computer.
If one host in the cluster fails, another host in the cluster can take over and host the same meeting. You must use thirdparty hardware or software to provide load balancing for the cluster. Often, load balancing hardware can also function
as an SSL accelerator.
Note: In the Application Management Console you can configure shared storage so that content is stored on external
devices and cached on the Adobe Connect server. For a fresh installation, you can also configure NAS.
Reliable networked systems are designed with redundant components; if one component fails, another identical
(redundant) component can take over the same job. When a component fails and its counterpart takes over, failover
has occurred.
12
Ideally, every component in a system should be redundant, not just Adobe Connect. For example, you could use
multiple hardware load balancing devices (such as BIG-IP by F5 Networks), a cluster of servers hosting Adobe
Connect, and SQL Server databases on multiple external computers. Build your system with as many redundancies as
possible and add to your system over time.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
13
clients
Router Hardware load
Adobe Connect/CQ cluster
Microsoft Network
Load Balancing software
SQL Server cluster
ABC
Three clustering options
A. A cluster with Network Load Balancing software and two external databases B. BIG-IP hardware load balancing devices, cluster, and two
external databases C. Two BIG-IP load balancing devices, cluster, and two external databases
Adobe Connect/CQ cluster Adobe Connect/CQ cluster
SQL Server cluster
balancing devices
clientsclients
SQL Server cluster
More Help topics
“Configuring shared storage” on page 60
Choosing a database
Adobe Connect uses a database to store information about users, content, courses, meetings, and reports. You can use
the embedded database engine (included with the installer), or you can install a supported SQL server (which must be
purchased separately).
Note: The embedded database engine in Adobe Connect 9.3 is Microsoft SQL Server 2008 Express Edition.
Embedded database
The embedded database engine is recommended for testing and development. It uses the same data structures as SQL
Server 2008 Enterprise Edition, but it isn’t as robust.
The embedded database engine has the following limitations:
• Because of licensing restrictions, you must install the embedded database engine on the same computer as Adobe
Connect. The computer must be a single-processor computer.
• 2 GB is the maximum size of the database.
• The embedded database engine has a command-line interface, rather than a graphical user interface.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
External database
Adobe Connect installer contains and installs the Microsoft SQL Server 2008 Express Edition. However, for
production environments, Adobe recommends using Microsoft SQL Server 2008 Enterprise Edition or Microsoft SQL
Server 2012 Enterprise Edition as it is a more scalable database management system (DBMS) designed to support a
large number of concurrent users. SQL Server 2008 Standard Edition also provides graphical user interfaces for
managing and querying the database.
You can install SQL Server 2008 Standard Edition on the same computer as Adobe Connect or on a different computer.
If you install them on different computers, synchronize the computers to the same time source. For more information,
see the following TechNote:
www.adobe.com/go/2e86ea67.
Install SQL Server in mixed login mode so that you can use SQL authentication. Set the database to case insensitive.
You must use SQL Server in the following deployment scenarios:
• To install the database on a computer that doesn’t have Adobe Connect installed.
• Adobe Connect is deployed in a cluster.
• Adobe Connect is installed on multiprocessor computers with Hyper-Threading.
More Help topics
“Supported server-database configurations” on page 4
14
Choosing to install integrated telephony adaptors
During the Adobe Connect installation process, you have the option to install one or more telephony adaptors.
Each adaptor requires you to supply specific pieces of information. If you have the information, you can configure the
adaptor during the initial installation of Adobe Connect. If you prefer, you can install the adaptor without configuring
it. When you are ready to configure the adaptor, run the installer again. For more information, see
“Preparing to install
integrated telephony adaptors” on page 16.
Choosing to deploy Adobe Connect Edge Server
When you deploy Adobe Connect Edge Server on your network, clients connect to the edge server and the edge server
connects to Adobe Connect (also called the origin server). This connection occurs transparently—to users, it appears
that they are connected directly to the origin server hosting the meeting.
Edge servers provide the following benefits:
Decreased network latency Edge servers cache on-demand content (such as recorded meetings and presentations)
and split live streams, resulting in less traffic to the origin. Edge servers place resources closer to clients.
Security Edge servers are an additional layer between the client Internet connection and the origin.
If your license permits it, you can install and configure a cluster of edge servers. Deploying edge servers in a cluster has
the following benefits:
Failover When an edge server fails, clients are routed to another edge server.
Support for large events If you require more than 500 simultaneous connections to the same meeting, a single edge
server will run out of sockets. A cluster allows more connections to the same meeting.
Load balancing If you require more than 100 simultaneous meetings, a single edge server may run out of memory.
Edge servers can be clustered behind a load balancer.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
How edge servers work
Edge servers authenticate users and authorize their requests for web services such as Adobe Connect Meeting rather
than forwarding every request to the origin server and consuming its resources for these tasks. If the requested data is
found in the edge server’s cache, it returns the data to the requesting client without calling Adobe Connect.
If the requested data is not found in the edge server’s cache, the edge server forwards the client’s request to the origin
server, where the user is authenticated and the request for services is authorized. The origin server returns the results
to the requesting edge server, and the edge server delivers the results to the requesting client. The edge server also stores
this information in its cache, where other authenticated users can access it.
Sample edge server deployment
Consider the following sample edge server deployment:
15
Meeting X
BOSTON
Meeting X
SAN FRANCISCO
Adobe Connect
Edge Server
Adobe Connect
Edge Server
Meeting X
CHICAGO
Adobe Connect
origin server
Clients on-site in Chicago use the origin located in a data center in Chicago. The edge servers in Boston and San
Francisco aggregate local client requests and forward them to the origin. The edge servers receive the responses from
the origin in Chicago and transmit them to clients in their zones.
More Help topics
“Install Adobe Connect Edge Server” on page 34
“Deploying Adobe Connect Edge Server” on page 40
Building and optimizing a VMWare environment
Installing Adobe Connect on VMWare is no different than installing it on a physical computer. For information about
hardware, software, and configuration requirements, see the
environment.
Last updated 3/1/2015
white paper about running Adobe Connect in a virtual
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Adobe Connect audio and video conferencing options
Adobe Connect supports two ways to connect to audio conferencing providers: Universal Voice and integrated
telephony adaptors. Each solution has different benefits. You can configure one solution or both solutions for a single
audio conferencing provider. You can configure any number of audio conferencing providers for an Adobe Connect
account.
Universal Voice enables Adobe Connect to send and receive audio from any audio conferencing provider. You can
record the audio along with your web conference and stream the audio to VoIP-only attendees.
Use Universal Voice to integrate video telephony devices that support SIP/H.264. Adobe Connect officially supports
the Tandberg 990MXP and Edge 95 video conferencing devices, though other Tandberg H.264 devices should work as
well. For more information, see the
The Universal Voice solution uses a component called Flash Media Gateway that installs with Adobe Connect. Flash
Media Gateway receives audio from a SIP server and sends it to Adobe Connect over RTMP. To use Universal Voice
you need to host your own SIP server or have an account with a SIP provider. For information about configuring Flash
Media Gateway, see
“Deploying Universal Voice” on page 49.
After you have deployed Universal Voice, account administrators can use Adobe Connect Central to configure audio
conference information. For more information, see
Integrated telephony adaptors are Java extensions that provide communication between Adobe Connect and specific
audio conferencing providers. Integrated telephony adaptors provide enhanced call control. You can install one or
more telephony adaptors when you install Adobe Connect. For more information, see
telephony adaptors” on page 14.
Tandberg website.
Configure audio providers for universal voice.
“Choosing to install integrated
16
You can also use the Adobe Connect Telephony Java API to develop an integrated telephony adaptor for any audio
conferencing provider.
The following table describes the features of both solutions:
Universal Voice Audio Provider Integrated Telephony Adaptor
Broadcast audio to VoIP-only attendees Yes No (unless adaptor is configured for Universal
Enhanced call control. For example, mute, hold,
and so on.
Record audio with Adobe Connect meeting Yes Yes
Requires Flash Media Gateway (bundled in the
Adobe Connect installer)
No Yes
Yes No (unless adaptor is configured for Universal
Voice)
Voice)
Preparing to install integrated telephony adaptors
Integrated telephony adaptors provide communication between Adobe Connect and specific audio conferencing
providers. Integrated adaptors have advanced call capabilities, allowing hosts and presenters to control the audio
conference from the meeting.
To install integrated telephony adaptors, run the Adobe Connect installer.
Each adaptor requires you to supply specific pieces of information during when you install it. For more information, see:
• “Avaya telephony adaptor” on page 17
• “Cisco Unified MeetingPlace telephony adaptor” on page 18
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
• “InterCall telephony adaptor” on page 18
• “MeetingOne telephony adaptor” on page 19
• “PGi (formerly Premiere Global) NA or EMEA telephony adaptor” on page 20
• “Arkadin telephony adapter” on page 21
Note: You can enable multiple audio bridges for Adobe Connect Server. Meeting hosts choose which audio bridge to use
when they create a meeting in Adobe Connect Central. Each meeting can have only one audio bridge.
Avaya telephony adaptor
The Avaya Meeting Exchange™ telephony adaptor allows meeting hosts, presenters, and participants to control audio
conference features from Adobe Connect meeting rooms. Complete the following workflow to enable the telephony
adaptor.
Working with Avaya customer support
It’s a good idea to involve Avaya customer support early in the planning process. Make certain that you have the
contact information for the Avaya account representative and Avaya customer support available. Contact Avaya
support to inform them that you are installing and using the adaptor and gather information about the bridge.
Note: A current maintenance contract with Avaya covering the audio bridge is required.
17
1 Contact Avaya Customer Support.
2 Request the following information:
• The IP address of the bridge
Communication between Adobe Connect and the telephony adaptor takes place through the Avaya bridge.
• An administration login
Use the administration login to configure and restart the bridge, change the number of operators, add new users,
and view statistics.
Note: Avaya uses an additional login for root access. Avaya does not usually supply that login to customers. For
operations that require root access, contact Avaya Customer Support.
• A file access login
Use the file access login to connect to the recording files directory.
• A Bridge Talk user name and password
Bridge Talk is an application to manage conferences and callers on the Avaya Meeting Exchange Audio
Conference Bridge. Use Bridge Talk to determine if there is a problem with the bridge or the adaptor. You can
also use this program to dial phone numbers; create, schedule, and manage new conferences; view running
conferences; and monitor bridge activity. For more information, including a User Guide, see
3 Verify that you have FTP access to the recording files directory by entering the following from an FTP prompt:
ftp://bridgeIPAddress
ftp>dcbguest:abc123@machineNameOrIPAddress
ftp>cd /usr3/confrp
ftp>bye
www.avaya.com.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Information needed when installing
Items marked with an asterisk (*) are required.
Enable Dial Out Select this option to enable system-wide dial out. If you don’t select this option, any selections you
make for the following four entries are ignored. If you do select this option, use the following four entries to specify
how dial out is implemented.
Enable Dial Out for Host Select this option to permit the meeting host to dial out.
Enable Dial Out for Presenter Select this option to permit the presenter to dial out.
Enable Dial Out for Participant Select this option to permit participants to dial out.
Enable “Call Me” Dialog If dial out is enabled, select this option to display the "Call Me" dialog box to participants
when they join a meeting.
Meeting Exchange Host Name* The hostname or address of the Avaya Meeting Exchange server.
Phone Operator ID* The ID of the operator channel used to associate with the Meeting Exchange server.
Login ID* The Login ID used to establish a connection with the Meeting Exchange Server.
Password* The password used with the Login ID to connect to the Avaya Meeting Exchange server.
FTP Directory* The FTP directory for audio files on the Avaya Bridge.
18
FTP Login* User name for FTP login.
FTP Password* Password for FTP login.
Meeting Exchange Dial In Number* A valid phone number dialed by Adobe Connect to reach the Meeting Exchange
server.
Cisco Unified MeetingPlace telephony adaptor
The MeetingPlace telephony adaptor allows meeting hosts, presenters, and participants to control audio conference
features from Adobe Connect meeting rooms.
Information needed while installing
Items marked with an asterisk (*) are required.
CISCO Unified MeetingPlace Server* URL for the MeetingPlace server
CISCO Unified MeetingPlace Administrator* The ID you use to connect to MeeetingPlace server as an administrator.
CISCO Unified MeetingPlace Password* Password for the MeetingPlace administrator account.
Confirm Password retype the password for the MeetingPlace administrator account.
InterCall telephony adaptor
The InterCall telephony adaptor allows meeting hosts, presenters, and participants to control audio conference
features from Adobe Connect meeting rooms. This adaptor requires a VoIP or SIP provider and Flash Media Gateway
(Universal Voice) for recording meetings. Complete the following workflow to enable the telephony adaptor.
Note: InterCall recommends using API instead of CCAPI.
Planning for deployment
To deploy the InterCall adaptor, certain ports must be available, as shown in the following table:
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Port Description
19
80 InterCall uses port 80 to communicate with Adobe Connect over HTTP. This port must be open for
443 InterCall uses port 443 to communicate with Adobe Connect over HTTPS (SSL). This port must be open
8443 Adobe Connect uses port 8443 to communicate with InterCall over HTTPS (SSL). Adobe Connect uses
9080 As mentioned earlier, this port is required for telephony in general. For InterCall, however, it must
incoming communication, to be able to receive callbacks from InterCall to Adobe Connect.
for incoming communication, to be able to receive callbacks from InterCall to Adobe Connect.
this port for CCAPI/API and authorization services. This port must be open so that outgoing messages
can be sent from Adobe Connect to InterCall.
additionally be opened on the firewall for each node in a cluster.
Information needed when installing
Items marked with an asterisk (*) are required.
Enable Dial Out Select this option to enable system-wide dial out. If you don’t select this option, any selections you
make for the following four entries are ignored. If you do select this option, use the following four entries to specify
how dial out is implemented.
Enable Dial Out for Host Select this option to permit the meeting host to dial out.
Enable Dial Out for Presenter Select this option to permit the presenter to dial out.
Enable Dial Out for Participant Select this option to permit participants to dial out.
Enable “Call Me” Dialog If dial out is enabled, select this option to display the "Call Me" dialog box to participants
when they join a meeting.
CCAPI Host* URL for the InterCall CCAPI service
CCAPI Auth Host* URL for the InterCall CCAPI authorization service.
Client Callback URL* Callback URL used the InterCall service to call back to Adobe Connect. This URL must be
publicly accessible.
Application Token* Value used to identify your connection with the InterCall audio service.
Country Codes* List of country codes for which Adobe Connect displays available conference service numbers.
Toll Free Number Country Code The country code whose conference number is toll-free; for example, US.
MeetingOne telephony adaptor
The MeetingOne telephony adaptor allows meeting hosts, presenters, and participants to control audio conference
features from Adobe Connect meeting rooms.
Information needed when installing
Items marked with an asterisk (*) are required.
Enable Dial Out Select this option to enable system-wide dial out. If you don’t select this option, any selections you
make for the following four entries are ignored. If you do select this option, use the following four entries to specify
how dial out is implemented.
Enable Dial Out for Host Select this option to permit the meeting host to dial out.
Enable Dial Out for Presenter Select this option to permit the presenter to dial out.
Enable Dial Out for Participant Select this option to permit participants to dial out.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Enable “Call Me” Dialog If dial out is enabled, select this option to display the "Call Me" dialog box to participants
when they join a meeting.
MeetingOne API URL* URL for the MeetingOne audio conference API service.
SSH Specifies whether SSH downloading of recordings is enabled.
Telephony API Server Login* The ID you use to for the MeetingOne audio conference API service.
Telephony API Server Password* Password for the administrator account.
Confirm Password retype the password for the MeetingPlace administrator account.
PGi (formerly Premiere Global) NA or EMEA telephony adaptor
The PGi telephony adaptor allows meeting hosts, presenters, and participants to control audio conference features
from Adobe Connect meeting rooms. The information in this section applies to both the PGi NA and the PGi EMEA
adaptors.
Information needed when installing
Items marked with an asterisk (*) are required.
Enable Dial Out Select this option to enable system-wide dial out. If you don’t select this option, any selections you
make for the following four entries are ignored. If you do select this option, use the following four entries to specify
how dial out is implemented.
20
Enable Dial Out for Host Select this option to permit the meeting host to dial out.
Enable Dial Out for Presenter Select this option to permit the presenter to dial out.
Enable Dial Out for Participant Select this option to permit participants to dial out.
Enable “Call Me” Dialog If dial out is enabled, select this option to display the "Call Me" dialog box to participants
when they join a meeting.
Note: The next four values are supplied to you by PGi.
PGi Hostname* The host name or IP address of the PGi audio conference service. For PGi NA, this value is usually
csaxis.premconf.com. For PGi EMEA, this value is usually euaxis.premconf.com.
PGi Port Number* The port number that Adobe Connect uses to connect to the PGi audio conference service. This
value is usually
PGi Web ID* The ID you use when you connect to the PGi audio conference service.
PGi Password* The password you use when you connect to the PGi audio conference service.
Recording Download Login* The login used to download audio recordings from the PGi audio conference service.
Download Password* The password used with the Recording Download Login to retrieve recordings from the PGi
443.
audio conference service.
Download URL The URL that Adobe Connect uses to download recordings from the PGi audio conference service.
The default value is for PGi NA is https://ww5.premconf.com/audio/. The default value for PGi EMEA is
http://eurecordings.premiereglobal.ie/audio/.
Country Code for Universal Line Number* The corresponding country code for a Universal line number.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Preparing for migration, installation, and configuration
Arkadin telephony adapter
The Arkadin telephony adaptor allows meeting hosts, presenters, and participants to control audio conference features
from Adobe Connect meeting rooms. This adaptor requires a VoIP or SIP provider and Flash Media Gateway
(Universal Voice) for recording meetings. Complete the following workflow to enable the telephony adaptor.
Planning for deployment
For Arkadin telephony adapter to work, you must get the host IP address of your Adobe Connect Server running
telephony services, whitelisted on the firewall of Arkadin. Since the IP address is allowed on Arkadin’s firewall, the
Adobe Connect Server hosting Arkadin services, must have a public IP address.
For more information, see http://www.arkadin.com/.
Information needed when installing
Enable Dial Out Select this option to enable system-wide dial out. If you don’t select this option, any selections you
make for the following four entries are ignored. If you select this option, use the following four entries to specify how
dial out is implemented.
Enable Dial Out for Host Select this option to permit the meeting host to dial out.
Enable Dial Out for Presenter Select this option to permit the presenter to dial out.
21
Enable Dial Out for Participant Select this option to permit participants to dial out.
Arkadin client application identifier* Arkadin client application identifier (provided by Arkadin, no default value).
Arkadin server URL* Arkadin server URL (provided by Arkadin, no default value).
Adobe Connect external hostname* Adobe Connect external hostname (https://[external-
hostname]/servlet/bamboo/ is the default value).
Arkadin Access Number server URL* Arkadin access number server URL (provided by Arkadin, no default value).
Arkadin authentication server URL* Arkadin authentication server URL (provided by Arkadin, no default value.
Last updated 3/1/2015
Chapter 3: Installing or Upgrading to
Fresh installaon of
Get the installer and
using the license
Connect 9.4 patch
9.1 or 9.2
Deploy Adobe
patch
patch
Upload Adobe
license
g the
exisng license
C9.0 license
Adobe Connect 9.4
Install or upgrade Adobe Connect and associated products
Adobe Connect 9.4 is distributed as a patch that can be added only on an existing Adobe Connect 9.3 system. For an
existing Adobe Connect 9.x (x = 0, 1, or 2) installation, upgrade it to the latest Adobe Connect 9.3 before deploying
Adobe Connect 9.4 patch. For a new installation, install Adobe Connect 9.3 using the installer and then deploy version
9.4 patch.
Important: If an existing Adobe Connect 9.x instance does not have AEM license and you want to upgrade it to an Adobe
Connect 9.4 instance with an AEM license, then upgrade to Adobe Connect 9.3 with an AEM-enabled license and apply
the Adobe Connect 9.4 patch.
Workflow for a new installation is illustrated in the following diagram.
22
Adobe Connect 9.4
Adobe Connect 9.4 new installation workflow
an appropriate
license for Adobe
Connect 9.3
Install Adobe
Connect 9.3
Deploy Adobe
Upload Adobe
Connect 9.4
license
The various upgrade paths are illustrated in the following workflow diagram.
upgrade using
8.x
9.0
Check the version of
your exisng Adobe
Connect installaon
Adobe Connect 9.4 upgrade workflows
upgrade usin
9.3
Connect 9.4
Connect 9.4
Install Adobe Connect 9.3 using the installer
After reviewing and gathering required information (see “Preparing for migration, installation, and configuration” on
page 3), you are ready to install Adobe® Connect™.
1 Verify that the computer is connected to the Internet.
2 Log on to the computer as an Administrator. By default, Adobe Connect installer requires a different local
administrator account, than the one you are logged in with. Keep the credentials of an administrator account
handy, using which you want to install Adobe Connect.
3 Close all applications.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Installing or Upgrading to Adobe Connect 9.4
4 Extract the files from the Adobe Connect ESD file to a location on your hard disk. [extract-dir] denotes this
location.
5 Double-click the install.exe file. Adobe Connect 9.3 installation file is available at
[extract_dir]\Connect\9.3.1\Disk1\InstData\VM\install.exe. In case of DVD, double-click the install.exe file at
[DVD Drive]\Connect\9.3.1\Disk1\InstData\VM\
6 Select a language and click OK to continue.
7 On the Introduction screen, click Next to continue.
8
On the License Agreement screen read the agreement, select I accept the terms of the License Agreement, and click Next.
9 On the Deployment Options screen, select Deploy Adobe Connect to install Adobe Connect. Provide the
credentials of a local administrator account, than the one logged in, to install Adobe Connect.
Note: If you choose to use a different local administrator account, ensure the account has the rights to install services.
For more information, see
10 Select Perform pre-deployment tasks in the background without affecting the live server. If you select this option,
Add the Log on as a service Right to an Account.
the installer starts to install Adobe Connect and other selected components without deploying them. To deploy
them, re-run the installer later and select Deploy Adobe Connect. You can run the installer with both the options
selected, if necessary.
11 Do one of the following to select the Adobe Connect installation location:
• Click Next to accept the default Adobe Connect installation location (C:\Connect), or click Choose to select a
different location.
Note: Subsequent installations of Adobe Connect on the same machine share content and logs location. However
files for different versions of Adobe Connect are in their own version folder in C:\Connect. If you are migrating from
an earlier version, all the files except content and log files are backed up.
23
• If you’ve chosen a different location and decide to use the default location instead, click Restore Default.
• If Adobe Connect is already installed on this computer, the Update Existing Install screen appears. Select the
check box to confirm you’ve backed up your database and the Adobe Connect root directory.
12 Enter your serial number and click Next.
13 Click the link to download your license file from Adobe. Click Choose and browse to the downloaded license file.
Click Next.
14 Choose the products you wish to install and click Next to continue. Adobe AEM-related options can be selected
only if your license has Events enabled. Otherwise, the AEM options are grayed out.
• Adobe Connect Server
• Flash Media Gateway (Universal Voice)
Note: To install only FMG on a machine, select this option and ignore the other options. To install FMG on a
machine where Adobe Connect Server 9.x is already installed, rerun the installer and select the appropriate options.
Important: If you are installing Adobe Connect and FMG on separate machines, install Adobe Connect before
installing FMG.
Note: Flash Media Gateway requires an upstream SIP/VoIP provider. For more information, see “Adobe Connect
audio and video conferencing options” on page 16.
• AEM Author Server
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Installing or Upgrading to Adobe Connect 9.4
Note: To install only AEM Author server on a machine, select this option and ignore the other options. If you want
to install AEM Author server on a machine where Adobe Connect Server 9.x is already installed, rerun the installer
with appropriate options selected. Provide the FQDN of the AEM Author server, along with the port. If AEM Author
server is clustered, provide the load balancer URL along with the port. Use the proceeding
http://
in the URL.
• AEM Publish Server
Note: To install only AEM Publish server on a machine, select this option and ignore the other options. To install
AEM Publish server on a machine where Adobe Connect Server 9.x is already installed, rerun the installer with
appropriate options selected. Provide the FQDN of the AEM Publish server, along with the port. If AEM Publish
server is clustered, provide the load balancer URL along with the port. Use the proceeding
http:// in the URL.
• PGi (NA) Telephony Adaptor
• PGi (EMEA) Telephony Adaptor
• Cisco Unified MeetingPlace
• Avaya Telephony Adaptor
• InterCall Telephony Adaptor
Note: Install Adobe Flash Media Gateway (FMG), to use the InterCall adaptor.
• Arkadin Telephony Adaptor
• MeetingOne Telephony Adaptor
Note: When you click Next, the installer verified the system hardware and proceeds with the installation if the machine
meets the minimum system requirements. For a complete list of system requirements, refer to the Adobe Connect tech
here.
specs
24
15 On the Embedded Database Engine screen, do one of the following:
• If you plan to install a database on a different computer, select Do not install the embedded database engine.
• To install the embedded database, select Install the embedded database engine. To install to the default location,
click Next. To select a different location, click Choose.
Note: If the Adobe Connect 9.3 installer detects that Microsoft SQL Server 2008 Enterprise Edition or Microsoft SQL
Server 2012 Enterprise Edition is already installed on this computer, the installer does not install the database. If
you’re migrating and are already using the embedded database, Adobe Connect uses the existing database. When the
installer detects an embedded Microsoft SQL Server 2005 Express Edition, the installer prompts to upgrade the
database. When the installer detects an external database, it prompts the user to upgrade the database.
16 If you installed the embedded database engine, enter a strong password and confirm it, and then click Next.
17 Set values for the Database Connection settings listed below, then click Next. Items marked with an asterisk (*) are
required.
• Host* The host name of the computer on which the database is installed. If you installed the embedded
database, the value is
localhost.
• Port* The port the database uses to communicate with Adobe Connect. The default value is 1433.
• Database Name* The name of the database. The default value is breeze.
• User* The name of the database user. If you installed the embedded database, the default value is sa.
• Password* The password for the database user. If you installed the embedded database, you set the password
in the previous step.
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Installing or Upgrading to Adobe Connect 9.4
18 Set values for the network settings listed below, then click Next. Items marked with an asterisk (*) are required.
• Account Name* A name that identifies the Adobe Connect account, such as “Adobe Connect account”.
• Adobe Connect Host* A Fully Qualified Domain Name (FQDN) clients use to connect to Adobe Connect.
For example, if the URL of the account is http://connect.example.com, the Adobe Connect Host value would be
connect.example.com (without the leading http://).
• Installation Type Select the type of installation as Single or Cluster.
19 Set values for the mail settings listed below, then click Next. Items marked with an asterisk (*) are required.
• SMTP Host The host name of the computer hosting the SMTP mail server.
• SMTP Username The user name used to authenticate against the SMTP host. If this field is left blank, Adobe
Connect tries to send emails without authenticating with the SMTP server.
• SMTP Password The password for the SMTP user name.
• System E-mail* The email address to which administrative messages are addressed.
• Support E-mail* The email address to which Adobe Connect user support requests are sent.
• BCC E-mail A blind-copy email address to which all user notifications are also sent. This variable allows
administrative tracking of email messages sent through Adobe Connect without exposing an internal email
address.
20 Enter the values in the Support Settings screen to provide the contact information used by Adobe Connect when
users needs support or help.
• Administrators name Provide the name of the Adobe Connect Account Administrator.
• Support email address Provide the email address to which users can direct their queries and support requests.
• Support phone number Provide the contact number that users can call to seek support.
• Support comments Provide any other comments.
21 Enter values for the shared storage settings listed below, then click Next.
• Shared Storage A volume and directory on an external server where content is stored, for example,
\\volume\directory. If you want to store content on multiple volumes, separate them with semicolons (;). Before
configuring this feature, see
“Configuring shared storage” on page 60.
• Content Cache Size An integer from 1 through 100 specifying the percent of free disk space to use to store
content on Adobe Connect. The cache can grow beyond the percent you specify, so it’s a good idea to keep the
value from 15 through
Adobe Connect or any external volumes. Before configuring this feature, see
page 60.
22 If you choose to install AEM servers, specify the External Host Settings.
50. If you leave the box blank or enter 0, no cache is used, and content is mirrored on
“Configuring shared storage” on
• Is your CQ environment is SSL enabled? Select the checkbox, if you plan to access AEM setup via https.
• CQ Author server URL* Provide the FQDN of the AEM Author server, along with the port. If AEM Author
server is clustered, provide the load balancer URL.
• CQ Publish server URL* Provide the FQDN of the AEM Publish server, along with the port. If AEM Publish
server is clustered, provide the load balancer URL.
• Adobe Connect Host Cookie Prefix* A text string that is used as a prefix for the Adobe Connect Host cookie.
23 If you choose to install the AEM Author server, specify the cluster and author settings.
• Is CQ Author Server clustered Select the checkbox if your AEM Author server is a cluster.
25
Last updated 3/1/2015
MIGRATING, INSTALLING, AND CONFIGURING ADOBE CONNECT 9
Installing or Upgrading to Adobe Connect 9.4
• Node designation* If your AEM Author server is clustered, then one node is designed as the master node and
all the other nodes are designated as Slave. Choose the node designation of the machine on which you are
installing AEM Author server.
• Master Node IP* Provide the IP of the master node if you are installing AEM Author instance on a slave node.
Note: Before installing a Slave node of a AEM server, deploy the corresponding Master node. Latter must be
available on the network, while installing the former.
• Hostname (ie http://)* Specify the host name URL of the author.
• Port* Specify the port of the AEM Author server. The default value is 4502.
• Publish Hosts* Specify the FQDN and port of all the Publish servers.
24 If you choose to install AEM Publish server, specify its settings.
• Hostname (ie http://)* Specify the host name of the AEM Publish server.
• Port* Specify the port of the Publish server. The default value is 4503.
• Adobe Connect Host Cookie Prefix* A text string that is used as a prefix for the Adobe Connect Host cookie.
Note: Cookie prefix you specify here, must exactly match the cookie prefix specified on the External Host Settings
screen.
25 If you install AEM Author or Publish server, create a password for AEM administration.
Note: Credentials of AEM administrators must be the same for all the AEM Author and Publish servers. Also, these
credentials are required for subsequent upgrades and should be carefully managed. It is not possible to upgrade, in the
future, without these credentials.
26
26 If you chose to install Flash Media Gateway, enter the following settings and click next. The settings do not take
effect instantaneously. When you click OK to confirm the settings, Adobe Connect restarts all Flash Media Gateway
servers. The settings are pushed to all Flash Media Gateway servers in a cluster.
• Username The user name for the SIP profile that Flash Media Gateway server uses to create SIP sessions, for
example sipUN1.
• Password The password for the SIP profile that Flash Media Gateway server uses to create SIP sessions.
• SIP Address The address of the SIP server for the SIP profile that Flash Media Gateway server uses to create
SIP sessions, for example, 10.12.13.14.
• Default Host The default host for the SIP profile. This parameter is the SIP server address to use if registration
with the SIP server fails. This parameter is set to the same value as SIP Address.
• Port Lower Limit The lowest port number that can be used for RTP audio data. The default value is 5000.
• Port Upper Limit The highest port number that can be used for RTP audio data. The default value is 6000.
• Registration Expiration The interval, in seconds, at which Flash Media Gateway renews its registration with
the SIP server. The default value is 2400 seconds (40
minutes).
• SIP Port The port on which Flash Media Gateway server listens for SIP requests. The default value is 5060.
• Registration Choose whether a Flash Media Gateway server must register on the SIP server.
27 Fill in the requested values to create an account administrator, and then click Next.
Every Adobe Connect account needs at least one administrator to perform tasks in the Adobe Connect Central web
application. Upgraded accounts already have at least one account administrator, but you can add an additional one here.
If the person installing Adobe Connect is not the Administrator who maintains Adobe Connect, then select the
option to change the password at next login.
Last updated 3/1/2015
Loading...