bb c Installing and Deploying Adobe Flash

bb c Installing and Deploying Adobe Flash
bc
Installing and Deploying Adobe® Flash®
Media Rights Management Server for
JBoss®
Adobe® Flash® Media Rights Management Server
May 2008
Version 1.0
© 2008 Adobe Systems Incorporated. All rights reserved.
Installing and Deploying Adobe® Flash® Media Rights Management Server 1.0 for JBoss® for Microsoft® Windows® and Linux®
Edition 1.1, May 2008
If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished
under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part
of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording,
or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected
under copyright law even if it is not distributed with software that includes an end user license agreement.
The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or
inaccuracies that may appear in the informational content contained in this guide.
Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The
unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to
obtain any permission required from the copyright owner.
Any references to company names, company logos and user names in sample material or sample forms included in this documentation
and/or software are for demonstration purposes only and are not intended to refer to any actual organization or persons.
Adobe, the Adobe logo, Flash, and LiveCycle are either registered trademarks or trademarks of Adobe Systems Incorporated in the United
States and/or other countries.
IBM is a trademark of International Business Machines Corporation in the United States, other countries, or both.
Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the U.S. and other countries.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Red Hat and JBoss are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries.
Sun and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
All other trademarks are the property of their respective owners.
This product contains either BSAFE and/or TIPEM software by RSA Security, Inc.
This product includes software developed by the IronSmith Project (http://www.ironsmith.org/).
This product includes software developed by the Apache Software Foundation (http://www.apache.org/)
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.
Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101,
consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R.
§12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable,
the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users
(a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein.
Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA
95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if
appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of
1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60,
60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.
Contents
About This Document.................................................................................................................. 5
Who should read this document? ............................................................................................................................................ 5
Conventions used in this document ....................................................................................................................................... 5
Additional information................................................................................................................................................................. 6
............................................................................................................................................................................................................... 6
1
Preparing the Environment ........................................................................................................ 7
Introduction ..................................................................................................................................................................................... 7
System requirements.................................................................................................................................................................... 7
Minimum hardware requirements .................................................................................................................................... 7
Intel x86 compatibility ........................................................................................................................................................... 8
Recommended hardware requirements ......................................................................................................................... 8
Supported software ................................................................................................................................................................ 8
Web browser support............................................................................................................................................................. 9
Additional requirements for Linux operating systems .............................................................................................. 9
Installing from network drives.................................................................................................................................................10
Installing on a JBoss Application Server cluster ................................................................................................................10
Configuration worksheet...........................................................................................................................................................10
2
Creating the LiveCycle ES Database......................................................................................... 12
Database configuration requirements .................................................................................................................................12
Creating a MySQL database .....................................................................................................................................................12
Creating an Oracle database ....................................................................................................................................................13
Creating a SQL Server database..............................................................................................................................................14
Install the SQL Server database driver:...........................................................................................................................15
Setting up SQL Server for LiveCycle ES ..........................................................................................................................15
Sizing your SQL Server database......................................................................................................................................16
Creating the LiveCycle ES database ................................................................................................................................16
Creating the LiveCycle ES user in SQL Server ..............................................................................................................17
Associating the LiveCycle ES user with the database...............................................................................................18
Setting the isolation level for the LiveCycle ES database........................................................................................18
3
Configuring a JBoss Application Server .................................................................................. 19
Installing the J2SE SDK ...............................................................................................................................................................19
Installing JBoss ..............................................................................................................................................................................20
Using Adobe-preconfigured JBoss ..................................................................................................................................20
Manually installing JBoss.....................................................................................................................................................21
Starting and stopping JBoss ..............................................................................................................................................21
Modifying JBoss configuration files.......................................................................................................................................21
Configuring the LiveCycle ES database connectivity......................................................................................................26
Configuring MySQL for Adobe-preconfigured JBoss................................................................................................26
Configuring MySQL for manually installed JBoss.......................................................................................................28
Configuring Oracle for Adobe-preconfigured JBoss.................................................................................................31
Configuring Oracle for manually installed JBoss........................................................................................................34
Configuring SQL Server..............................................................................................................................................................37
Configuring the SQL Server data source .......................................................................................................................37
3
Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
4
Contents
4
Installing, Configuring, and Deploying ................................................................................... 41
About the installation, configuration, and deployment process................................................................................41
Flash Media Rights Management Server installation......................................................................................................42
Installation considerations .................................................................................................................................................42
Installing Flash Media Rights Management Server ...................................................................................................43
About LiveCycle Configuration Manager ............................................................................................................................45
Selecting tasks for configuring and deploying LiveCycle ES........................................................................................46
Running LiveCycle Configuration Manager........................................................................................................................46
Viewing the error log ..................................................................................................................................................................48
5
Initial Administration Tasks...................................................................................................... 49
Restart the application server..................................................................................................................................................49
Verify access to LiveCycle Administration Console..........................................................................................................49
Accessing LiveCycle Administration Console..............................................................................................................49
Viewing the log files..............................................................................................................................................................50
Change default password .........................................................................................................................................................50
Set the correct date, time, and time zone ...........................................................................................................................50
6
Post-Deployment Tasks ............................................................................................................ 51
Configuring SSL for JBoss Application Server....................................................................................................................51
Creating an SSL Credential .................................................................................................................................................51
Configuring SSL on Windows Vista .................................................................................................................................54
Configuring the settings............................................................................................................................................................54
Configuring the credentials......................................................................................................................................................56
External authenticators and authorizers..............................................................................................................................56
Flash Media Rights Management Server tools ..................................................................................................................56
Uninstalling Flash Media Rights Management Server....................................................................................................57
Uninstalling LiveCycle ES...........................................................................................................................................................57
7
Troubleshooting ........................................................................................................................ 58
Getting help ...................................................................................................................................................................................58
Installation considerations .................................................................................................................................................58
Application server considerations ...................................................................................................................................58
Database initialization considerations ...........................................................................................................................59
Troubleshooting with LiveCycle Configuration Manager log files.............................................................................59
Scheduler service configuration for nondefault JNDI URLs..........................................................................................59
Error messages ..............................................................................................................................................................................60
Class not found .......................................................................................................................................................................60
JNDI name not found ...........................................................................................................................................................60
Exceptions thrown when initializing the LiveCycle ES database multiple times ...........................................61
Failure to deploy EARs................................................................................................................................................................61
About This Document
This document explains how to install, configure, and deploy
Adobe® Flash® Media Rights Management Server for JBoss Application Server and Oracle®, Microsoft SQL
Server, and MySQL databases. The steps covered in this document help you configure your environment
and get a Flash Media Rights Management Server system up and running.
Who should read this document?
This document is intended for evaluators, administrators, or developers who are responsible for installing,
configuring, administering, or deploying Flash Media Rights Management Server. The information
provided is based on the assumption that anyone reading this document is familiar with the Microsoft®
Windows® or Red Hat® Linux® operating systems and web environments.
Conventions used in this document
This guide uses the following naming conventions for common file paths.
Name
Description
Default value
[appserver root]
The home directory of the application
server that runs the Adobe LiveCycle® ES
services.
JBoss Application Server on Windows:
C:\jboss
[dbserver root]
The location where the LiveCycle ES
database server is installed.
Depends on the database type and
your specification during installation.
[FMRMS root]
The installation directory where
Windows: C:\Adobe\FMRMS1.0\
Flash Media Rights Management Server
Linux: /opt/adobe/fmrms1.0/
resides, as well as the command line tools
and SPI library.
[LiveCycleES root]
The installation directory that is used for Windows: C:\Adobe\LiveCycle8\
all LiveCycle ES solution components. The Linux: /opt/adobe/livecycle8/
installation directory contains
subdirectories for LiveCycle Configuration
Manager and each LiveCycle ES solution
component installed (along with the
product documentation). This directory
also includes directories that relate to
third-party technologies.
JBoss Application Server on Linux:
/opt/jboss
Most of the information about directory locations in this guide is cross-platform (all file names and paths
are case-sensitive on Linux). Any platform-specific information is indicated as required.
5
Adobe Flash Media Rights Management Server
About This Document
Installing and Deploying Flash Media Rights Management Server for JBoss
Additional information
Additional information
The resources in this table provide additional information about Flash Media Rights Management Server.
For information about
See
The Flash Media Rights Management Server solution,
development environment, run-time environment,
and each Flash Media Rights Management Server
component
Overview
Installing, configuring, and deploying Flash Media
Rights Management Server
Installing and Deploying Flash Media
Rights Management Server for JBoss Using
Turnkey
Installing and Deploying Flash Media
Rights Management Server for JBoss
Managing administrative users and user roles
User Management Help
Installing Flash Media Server
Adobe Flash Media Server Installation Guide
Customizing and configuring Flash Media Server
Adobe Flash Media Server Administration and
Configuration Guide
Creating custom service providers for Adobe
User Management and Adobe LiveCycle
Rights Management ES
Developing Service Providers
The Java™ interfaces and classes used to create custom Adobe Flash Media Rights Management Server API
Reference (Javadoc)
service providers
Securing video content and playlists by using the
Securing Video Content and Playlists
Flash Media Rights Management Server command line
tools
Delivering content in Adobe Media Player
Adobe Media Player Content Developer Kit
Using Adobe Media Player to find and view content
Adobe Media Player Help
6
1
Preparing the Environment
Introduction
This section provides the information you require to prepare your server environment before you perform
the installation and deployment of Flash Media Rights Management Server solution on Windows and
Linux. This section contains two types of information:
●
All hardware and software requirements and configurations that must be already in place to ensure a
successful Flash Media Rights Management Server install process.
●
All tasks that can be performed without having Flash Media Rights Management Server installed and
deployed but are not needed for installing or deploying.
This overview summarizes the order in which you will perform steps required for preparing your server
environment.
1. Prepare the hardware as per your requirements. (See “Minimum hardware requirements” on page 7).
2. Install the operating system and update with all necessary patches and service packs. (See “Supported
software” on page 8).
3. Install and configure the database server. (See “Creating the LiveCycle ES Database” on page 12).
4. Install and configure the application server. (See “Configuring a JBoss Application Server” on page 19).
5. Install, configure, and deploy Flash Media Rights Management Server solution components. (See
“Installing, Configuring, and Deploying” on page 41).
6. Perform post-deployment tasks. (See “Post-Deployment Tasks” on page 51).
System requirements
This section provides the minimum and recommended hardware requirement for Flash Media
Rights Management Server.
Minimum hardware requirements
This table provides the minimum hardware requirement supported by Flash Media
Rights Management Server.
7
Adobe Flash Media Rights Management Server
Preparing the Environment
Installing and Deploying Flash Media Rights Management Server for JBoss
Intel x86 compatibility
Operating system
Minimum hardware requirement
Microsoft Windows Server® 2003 Enterprise
Edition or Standard Edition SP1 and R2
(32-bit edition only)
Intel® Pentium® 3 or x86 equivalent, 1 GHz processor
VMWare ESX Server and GSX Server
RAM - 2 GB
Free disk space - 2.7 GB of temporary space plus 1.7 GB
for LiveCycle ES
Red Hat Enterprise Linux AS or ES 4.0
(32-bit edition only)
Pentium 3 or x86 equivalent, 1 GHz processor
RAM - 2.5 GB
Free disk space - 2.7 GB of temporary space plus 1.7 GB
for LiveCycle ES
Intel x86 compatibility
On supported Windows and Linux environments, Flash Media Rights Management Server supports Intel
EDT64 and AMD64 compatible chipsets, but the operating system must be 32 bit.
Recommended hardware requirements
In addition to the minimum hardware requirements listed previously, here are the recommended
hardware requirements for a small production environment:
Intel environments: Pentium 4, 2.8 GHz or greater. Using a dual core processor will further enhance
performance.
Memory requirements: 4 GB of RAM.
Supported software
This table provides a summary of the application servers, web browsers, databases, database drivers, and
the Sun™ Java™ Development Kit (JDK) versions that Flash Media Rights Management Server supports.
Required software
Supported version
Operating system
●
Microsoft Windows Server 2003 Enterprise Edition or Standard Edition SP1
and R2 (32-bit edition only)
●
Red Hat Enterprise Linux AS or ES 4.0 (32-bit edition only)
●
JBoss® 4.0.3 SP1
Application server
●
Web browser
See “Web browser support” on page 9 for a complete list of web browsers.
JDK
●
JBoss on all platforms - Sun JDK 1.5.0_11 (or later version of the 1.5.0
release) available at http://.java.sun.com
8
Adobe Flash Media Rights Management Server
Preparing the Environment
Installing and Deploying Flash Media Rights Management Server for JBoss
Web browser support
Required software
Supported version
Database
●
Microsoft SQL Server 2005 SP1 (Enterprise Edition and Standard Edition)
●
MySQL 5.0.18 (InnoDB Engine)
●
Oracle 10g (Standard and Enterprise Editions)
●
SQL Server 2005 JDBC 1.1 - sqljdbc.jar
●
MySQL - mysql-connector-java-3.1.12-bin.jar (3.1.12)
●
Oracle 10g - ojdbc14.jar, Release 2 (10.2.0.2 Thin)
Database driver
9
Web browser support
This table outlines the supported web browsers for the Flash Media Rights Management Server
administrator user interface, LiveCycle Administration Console.
Operating system
Flash® Player
Supported browser
Microsoft Windows Vista™
N/A
Internet Explorer 7 or later(1)
Firefox 2.0.0.1 or later(1)
Windows 2000
N/A
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
Windows XP
N/A
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
Windows Server 2003
N/A
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
OS X v 10.4.x (Intel)
N/A
Firefox 2.0.0.1 or later(1)
(1)“or later” includes major revisions. For example, Microsoft Internet Explorer 6.0 or later also covers
Microsoft Internet Explorer 7.0
Additional requirements for Linux operating systems
The installer for Adobe LiveCycle ES (Enterprise Suite) Update 1 requires the bc tool to be available on the
Linux system. Normally, the bc tool is present by default. Ensure that the bc tool (an arbitrary precision
calculator language) is installed on the system before you run the installer. If the tool is not present, you
will encounter error messages warning about lack of disk space because the bc tool is used to compute
whether enough disk space is available before you start the installation. The bc tool may be provided by
your operating system vendor; otherwise, you can get the GNU bc tool at www.gnu.org.
Note: To verify that the tool is available, execute which bc from the shell. If the tool is available, the path
to the program is displayed.
Adobe Flash Media Rights Management Server
Preparing the Environment
Installing and Deploying Flash Media Rights Management Server for JBoss
Installing from network drives
10
Installing from network drives
It is recommended that you install Flash Media Rights Management Server only from the installation
media or a local disk drive. Attempting to install the software over a network results in considerable delays
in launching and installing.
Installing on a JBoss Application Server cluster
If you intend to install and deploy Flash Media Rights Management Server in a clustered environment,
follow the preparatory and installation tasks outlined in Configuring LiveCycle ES Application Server Clusters
Using JBoss.
Note: When accessing this document, ensure that you have the version specified for LiveCycle ES version
8.0.1.2 (SP2) and not a later version.
Configuration worksheet
It is recommended that you record the following information and keep it conveniently accessible for
future use. This information will be required during the installation and configuration process as well as
being important for activities such as patching and upgrades.
Tip: Print this page to keep note of your settings as you progress through this document.
Component
Information
Value
Application server
Computer IP address or
fully qualified domain
(see note below)
enter value here
Database
Host name or IP address
enter value here
Database
Port number
enter value here
Database
Service ID
enter value here
Database
Database name
enter value here
Database
User name & password
enter value here
JDK
Install path
[JAVA_HOME]
enter value here
JBoss Application Server
Install path
[appserver root]
enter value here
JBoss Application Server
User name & password
enter value here
JBoss Application Server
Port number
enter value here
Flash Media
Rights Management Server
Serial number
enter value here
Flash Media
Rights Management Server
Install path
[FMRMS root]
enter value here
Adobe Flash Media Rights Management Server
Preparing the Environment
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuration worksheet
Component
Information
Value
Flash Media
Rights Management Server
Certificate expiry date
enter value here
LiveCycle ES
Install path
[LiveCycleES root]
enter value here
POP3.jar file
Location
enter value here
LiveCycle Administration Console
Administrator name &
password
enter value here
11
Note: Use of [localhost] during configuration causes errors; use the application server’s IP address or fully
qualified domain for all instances.
2
Creating the LiveCycle ES Database
This section describes how to set up the database for use with Flash Media Rights Management Server.
Before you create the database, ensure that you have read the preinstallation requirements and that you
have the required software installed. (See “System requirements” on page 7.)
If this is your first installation of Flash Media Rights Management Server, create an empty database. All of
the tables that are required to support Flash Media Rights Management Server are created when you run
the Initialize LiveCycle ES Database task by using LiveCycle Configuration Manager.
Database configuration requirements
This section describes special tables, indexes, and other properties that are required in the LiveCycle ES
database that are not configured by LiveCycle Configuration Manager.
●
“Creating a MySQL database” on page 12
●
“Creating an Oracle database” on page 13
●
“Creating a SQL Server database” on page 14
Creating a MySQL database
Note: The information contained in this document is meant for users who are installing MySQL manually
and not for a turnkey installation. For information about the turnkey installation, see Installing and
Deploying Flash Media Rights Management Server for JBoss Using Turnkey.
Use the MySQL tools to create a MySQL 5 database for use with LiveCycle ES and a MySQL user account
that the application server can use to connect to the database. You also need to modify the MySQL
database server configuration. For information about creating the database and user account, see the
MySQL documentation. Flash Media Rights Management Server supports MySQL 5 with JBoss 4.0.
Tip: To set up a database schema and new users on MySQL by using a graphical user interface (GUI), install
the MySQL Administrator tool. (See the MySQL user documentation.)
When installing the MySQL database, specify UTF-8 character encoding.
You need the following information when you configure the data source on JBoss:
●
User name and password of the MySQL user account
●
Host name or IP address of database server
●
MySQL port number
MySQL user account
The MySQL user account that you create requires these privileges to access the tables in the LiveCycle ES
database:
●
SELECT
●
INSERT
12
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
●
UPDATE
●
DELETE
●
CREATE
●
DROP
●
REFERENCES
●
INDEX
●
ALTER
●
CREATE_TMP_TABLE
●
LOCK_TABLES
Creating the LiveCycle ES Database
Creating an Oracle database
13
MySQL database server configuration
To prevent issues from occurring when uploading large files to MySQL, set the maximum allowed
communication packet size to 25 MB. You can set this property in the MySQL my.ini file (Windows) or
my.cnf file (Linux). For more information about the maximum allowed communication packet size
property in MySQL, see dev.mysql.com/doc/mysql/en/packet-too-large.html.
If your MySQL installation does not include a my.ini or my.cnf file, create one. For information about the
location of the file or how to create the file, see the MySQL documentation.
➤ To customize the MySQL configuration:
1. Open the my.ini (Windows) or my.cnf (Linux) file in a text editor.
2. Add the following line to the [mysqld] section:
max_allowed_packet=25M
3. Save and close the file.
MySQL initial server configuration recommendations
These configuration settings are recommended for MySQL server:
●
Key Buffer Size: 64 MB
●
Sort Buffer Size: 1 MB
●
Buffer Pool Size:100 MB
●
Additional Memory Pool Size: 5 MB
●
Log Buffer Size: 8 MB
●
Max Packet Size: 25 MB
●
Read Buffer Size: 1 MB
●
Read and Buffer Size: 1 MB
Creating an Oracle database
Install Oracle according to the manufacturer’s instructions. During the installation, a default database is
installed. This database will be used by your Flash Media Rights Management Server and will be initialized
during the configuration process.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Creating the LiveCycle ES Database
Creating a SQL Server database
14
If you prefer not to use the default database that was created when you installed Oracle 10g, create a
database by using the Database Configuration Assistant tool. For information about using Oracle 10g, see
the appropriate user documentation.
You must create your Oracle database to support UTF-8 characters. Ensure that the database character set
is Unicode (AL32UTF8). You must use the transaction processing template when creating the database.
The connection mode for the server must be Shared Server Mode.
You must also create a new user on the database and assign it the following system privileges:
●
CREATE SEQUENCE
●
CREATE VIEW
●
UNLIMITED TABLESPACE
●
CREATE TABLE
●
CREATE CLUSTER
●
CREATE SESSION
For deployments on Linux, the user name cannot exceed 8 characters and, on Windows, it must not exceed
12 characters.
You need the following information when you configure the data source on the application server:
●
SID (Service ID)
●
User name and password of the Oracle user account
●
Host name or IP address of the database server
●
Oracle port number (default is 1521)
Creating a SQL Server database
You can create a SQL Server database that Flash Media Rights Management Server will use to store
run-time and configuration data. For information about creating a SQL Server database, refer to the SQL
Server documentation. Flash Media Rights Management Server supports SQL Server 2005 SP1 with JBoss
4.0.
Create a SQL Server database and create a user with DB_OWNER privileges that can be used when
configuring the data source on the application server. For information about creating the database and
user, see the SQL Server documentation.
You need the following information when you configure the data source on the application server:
●
Database name
●
User name and password of the SQL Server user account
●
Host name or IP address of the database server
●
SQL Server port number
The SQL Server database can be configured with the Windows or SQL Server authentication types. For
Flash Media Rights Management Server, the authentication type must be set to SQL Server.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Creating the LiveCycle ES Database
Install the SQL Server database driver:
15
Install the SQL Server database driver:
If you have not done so already, download the SQL Server 2005 JDBC Driver 1.1 from the following location
on the Microsoft website:
www.microsoft.com/downloads/details.aspx?familyid=6d483869-816a-44cb-9787-a866235efc7c&disp
laylang=en
Follow the instructions on the website for downloading and installing the driver. Make a note of the
directory location where you install the driver on your system.
Setting up SQL Server for LiveCycle ES
Before you create the LiveCycle ES database, optimize SQL Server by changing these settings.
Increasing memory
The default SQL Server settings do not aggressively allocate memory. This situation significantly impacts
performance on most deployments of a SQL Server database.
➤ To increase the memory for SQL Server:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you want to
host the LiveCycle ES database.
2. Right-click the database connection and select Properties.
3. Select the Memory page and enter a size in the Minimum Server Memory (in MB) box that is equal to
the size of the free memory you have on the server.
Setting processor priority
On dedicated database servers (recommended for production installations of Flash Media
Rights Management Server), the SQL Server process is configured to prevent over-consumption of the
system CPU resources.
➤ To set the processor priority:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you want to
host the LiveCycle ES database.
2. Right-click the database connection and select Properties.
3. Select the Processors page and select Boost SQL Server Priority.
Increasing the recovery interval
This setting specifies the amount of time the deployment waits for recovery after a crash. The SQL Server
default setting is 1 minute. Increasing this setting to a larger value improves performance because it
allows the server to be more relaxed in writing changes from the database log to the database files. This
setting does not compromise the transactional behavior; however, it does affect the size of the log file that
is replayed on startup.
Adobe Flash Media Rights Management Server
Creating the LiveCycle ES Database
Installing and Deploying Flash Media Rights Management Server for JBoss
Sizing your SQL Server database
16
➤ To increase the recovery interval:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you want to
host the LiveCycle ES database.
2. Right-click the database connection and select Properties.
3. Select the Database Settings page and type 5 in the Recovery Interval (Minutes) box.
Note: After you change these settings, restart the SQL Server database to ensure that the settings take
effect.
Integrated Security
If you are using SQL Server 2005 integrated security, you can set your SQL Server 2005 database to either
Mixed Mode or Windows Authentication Mode. If you set it to Windows Authentication Mode for JBoss
(Windows), follow the steps in “To configure Integrated Security on Windows:” on page 38.
Sizing your SQL Server database
The default database sizes that SQL Server provides are too small for Flash Media
Rights Management Server. Even if the database is set to auto-grow, unintended consequences can occur,
such as reduced performance when the database grows or the size growth begins to fragment the disk.
Because of these effects, it is best to preallocate the database size at creation to reflect your deployment
requirements:
Medium size deployments: Environments where the LDAP directory has approximately 100,000 users
and 10,000 groups. Set Database Data Initial Size to 1 GB, and set autogrowth to 250 MB.
Large size deployments: Environments where the LDAP directory has approximately 350,000 users
and more than 10,000 groups. Set Database Data Initial Size to 2 GB, and set autogrowth to 1 GB.
Note: Database growth is always restricted to a certain size. Administrators need to monitor the resource
usage of the LiveCycle ES database to ensure that it does not run out of restricted space or the space
available on the disks where the database resides.
Creating the LiveCycle ES database
After you optimize the SQL Server, you are ready to create the LiveCycle ES database.
Caution: Ensure that you use the Latin1_General_CP1_CI_AS collation when you create the LiveCycle ES
database. Any other collation may cause your database initialization to fail.
➤ To create the LiveCycle ES database:
1. Using Microsoft SQL Server Management Studio, click Server, and then right-click Database and select
New Database.
2. In the New Database dialog box, replace database_name with the database name of your choice.
3. Ensure that Use Full-Text Indexing is deselected.
4. In the Database Data Initial Size MB box, enter the appropriate value:
●
For small development or small production system: 200 MB.
●
For larger systems: See “Sizing your SQL Server database” on page 16.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Creating the LiveCycle ES Database
Creating the LiveCycle ES user in SQL Server
17
5. In the Database Data Autogrowth box, enter 50%.
6. In the Database Log Initial Size box, enter the appropriate value:
●
For small development or small production system: 20MB
●
For larger systems: See “Sizing your SQL Server database” on page 16.
7. In the Database Log Autogrowth box, enter 50%.
Creating the LiveCycle ES user in SQL Server
In the following procedure, database_name represents the name you specified when you created your
database, and database_username represents the name you specify for the new user.
➤ To create the LiveCycle ES user:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you created the
LiveCycle ES database.
2. Click Server > Security, and then right-click Logins and select New Login.
3. In the New Login dialog box, enter the login name database_username.
4. Select SQL Server Authentication and type a new password.
5. Deselect Enforce Password Expiration. User must change password on next login is also
deselected.
6. Leave the default database as Master, and click OK.
7. Click Server > Databases > database_name > Security, and then right-click Schemas and select New
Schema.
8. In the Schema Name box, type database_username, and then click OK.
9. Click Server > Databases > database_name > Security, right-click Users and then select New User.
10. In the New User dialog box, enter the login name and user name database_username.
11. Set the default schema to database_username.
Note: The schema name should be the same as the database_username.
12. In the Schemas Owned By This User area, select the schema database_username.
13. In the Database Role Membership area, select db_owner.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Creating the LiveCycle ES Database
Associating the LiveCycle ES user with the database
Associating the LiveCycle ES user with the database
After you create the LiveCycle ES user, associate it with the LiveCycle ES database.
➤ To associate the LiveCycle ES user with the database:
1. Click Security > Logins, and then right-click database_username and select Properties.
2. In the Login Properties, in the General page, set the user’s default database to database_name.
3. Select the User Mapping page and, in the Users Mapped To This Login section, verify that
database_name is selected, User is set to database_username, and Default Schema is set to
database_username.
4. Ensure that database_name is selected in the Users Mapped To This Login table, and ensure that
db_owner and public are selected in the Database Role Membership For database_name table.
Setting the isolation level for the LiveCycle ES database
SQL Server 2005 provides a number of new isolation levels. Flash Media Rights Management Server
requires a specific isolation level to manage deadlocking when long-running transactions occur at the
same time as numerous shorter reads.
➤ To set the isolation level:
1. Click Databases, and then right-click database_name and select New Query.
Note: database_name represents the name you specified when you created your database.
2. In the Query panel, type the following text:
ALTER DATABASE database_name
SET READ_COMMITTED_SNAPSHOT ON
GO
3. Click Execute. A response is displayed in the messages panel.
18
3
Configuring a JBoss Application Server
When using a JBoss Application Server, you have three installation options:
●
Turnkey
●
Adobe-preconfigured JBoss
●
Manual JBoss configuration
This section covers the use of the JBoss Application Server when you are not using the turnkey installation
option. Use the non-turnkey method under these conditions:
●
You are using a Linux operating system.
●
You are preparing a cluster deployment on Windows or Linux.
●
You are using Oracle or SQL Server as your database.
●
You need advanced control of the JBoss configurations.
Flash Media Rights Management Server runs on JBoss on Windows Server 2003 (Enterprise Edition or
Standard Edition) and Red Hat Linux ES/AS 4.0 platforms. (See “System requirements” on page 7.)
Note: If you are planning to use the Flash Media Rights Management Server turnkey installation for JBoss,
you do not need to review this document. All the instructions that are required for preparing your
environment for a turnkey installation are available in Installing and Deploying Flash Media
Rights Management Server for JBoss Using Turnkey.
This chapter uses the following conventions.
Name
Default value
[appserver root]
(Windows) C:\jboss
(Linux) /opt/jboss
Installing the J2SE SDK
You must download and install the Sun J2SE SDK version 1.5.0_11 or a later update of version 1.5.0 from
www.java.sun.com.
You must also create or set the JAVA_HOME environment variable to point to the location where the Java
SDK is installed.
➤ To set the JAVA_HOME environment variable (Windows):
1. Select Start > Control Panel > System.
2. Click the Advanced tab and then click Environment Variables.
3. In the System Variables area, click New.
4. Enter JAVA_HOME as the variable name, and enter the directory where you installed the Java SDK. This
directory is the one that contains the /bin subdirectory. For example, type the following line:
19
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Installing JBoss
20
C:\Program Files\Java\jdk1.5.0_11
Note: To verify your JAVA_HOME environment variable, open a command prompt and run the following
command:
cd %JAVA_HOME%\bin
java -version
You should receive a response beginning with Java version 1.5.0_11 (or a later version of 1.5.0).
➤ To set the JAVA_HOME environment variable (Linux):
●
It is recommended that you set the JAVA_HOME variable for Borne and Bash shells as shown in the
following example:
JAVA_HOME=/usr/java
export JAVA_HOME
➤ To set the PATH environment variable (Linux):
●
It is recommended that you set the PATH variable for Borne and Bash as shown in the following
example:
PATH=$JAVA_HOME/bin:$PATH
export PATH
Installing JBoss
Use one of the following two ways to proceed with the deployment of JBoss for a Flash Media
Rights Management Server installation. Choose the option that is more appropriate:
●
Use the Adobe-preconfigured JBoss software that is delivered as part of the Flash Media
Rights Management Server media. In most cases, this option is the simplest. Advanced knowledge of
JBoss is not required.
●
Download the required JBoss software from the Internet (version 4.0.3 SP1). This option should be
considered for advanced installations only. Advanced knowledge of JBoss is typically required.
Using Adobe-preconfigured JBoss
Adobe downloads the standard JBoss 4.0.3 SP1 archive from the JBoss website and configures it with the
options required to run Flash Media Rights Management Server in a stand-alone configuration. You can
review these configurations in the next section.
The preconfigured JBoss software is located on the installation media in the /third_party directory. Copy
the JBoss directory and its contents to the location where you intend to install JBoss. This JBoss installation
has all of the configuration steps completed as described in the “Modifying JBoss configuration files” and
“Configuring MySQL” sections except for the steps that are detailed in “Configuring MySQL for
Adobe-preconfigured JBoss” on page 26, which you must complete if you plan to use MySQL. If you do not
intend to use a MySQL database, complete the remaining database configuration steps.
Adobe Flash Media Rights Management Server
Configuring a JBoss Application Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Manually installing JBoss
21
Manually installing JBoss
If you are manually configuring JBoss for running Flash Media Rights Management Server, download and
unpackage JBoss Application Server 4.0.3 SP1.
➤ To download and unpackage JBoss:
1. In a browser, go to labs.jboss.com/portal/jbossas/download.
2. Locate the entry for JBoss Application Server 4.0.3 SP1 and click the Download link beside it.
3. On the download page, select the appropriate file for your operating system:
●
(Windows) jboss-4.0.3SP1.zip
●
(Linux) jboss-4.0.3SP1.tar.gz
4. Extract the file to the directory of your choice on your server.
Starting and stopping JBoss
Several procedures in this chapter require you to stop and start the instance of JBoss where you want to
deploy the product.
Note: These procedures apply to both the Adobe-preconfigured JBoss and the manually installed JBoss
software.
➤ To start JBoss:
1. From a command prompt, navigate to [appserver root]/bin.
2. Start the application server by typing the following command:
●
(Windows) run.bat -c all
●
(Linux) ./run.sh -c all
➤ To stop JBoss:
1. From a command prompt, navigate to [appserver root]/bin.
2. Stop the application server by typing the following command:
●
(Windows) shutdown.bat -S
●
(Linux) ./shutdown.sh -S
Modifying JBoss configuration files
Note: This procedure is required only if you are not using the Adobe-preconfigured JBoss software
provided on the installation media.
Modify the following areas on the instance of JBoss that hosts Flash Media Rights Management Server:
●
Update the xalan version.
●
Update the jacorb.properties file.
●
Modify the EAR and WAR file class-loading isolation.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
●
Remove the JavaServer™ Faces (JSF) libraries.
●
Disable cluster service (for single node installations only).
●
Enable Watched Folder invocations.
●
Remove the tests directory.
●
Create the security policy file.
●
Modify the run.bat file (Windows only).
●
Modify the run.sh file (Linux only).
●
Modify run.conf.
●
Modify log4J.xml.
●
Remove the JMX Console and Web Console.
●
Create the Java Message Service (JMS) topics and queues.
Configuring a JBoss Application Server
Modifying JBoss configuration files
22
➤ To update the xalan version:
1. Download the xalan-j 2.7.0 download package from the following website:
http://xml.apache.org/xalan-j/
2. Download the required file:
●
(Windows) xalan-j_2_7_0-bin.zip
●
(Linux) xalan-j_2_7_0-bin.tar.gz
3. Extract the xalan.jar file and the serializer.jar file from the downloaded archive file.
4. From the [appserver root]/lib/endorsed directory, delete the old xalan.jar file.
5. Copy the new xalan.jar file and the serializer.jar files to the [appserver root]/lib/endorsed directory.
➤ To update the jacorb.properties file:
1. Open the [appserver root]/server/all/conf/jacorb.properties file in a text editor.
2. Locate the jacorb.poa.thread_pool_max setting and change the value to 16.
➤ To modify WAR file class-loading isolation:
1. Open the [appserver root]/server/all/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml file in
an editor.
2. Locate <attribute name="Java2ClassLoadingCompliance"> and change the value to true.
3. Locate <attribute name="UseJBossWebLoader"> and ensure that the value is false.
4. Save and close the file.
➤ To modify EAR file class-loading isolation:
1. Open the [appserver root]/server/all/conf/jboss-service.xml file in an editor.
2. Locate <attribute name="CallByValue"> and change the value to true.
3. Save and close the file.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Modifying JBoss configuration files
23
4. Open the [appserver root]/server/all/deploy/ear-deployer.xml file in an editor.
5. Locate <attribute name="Isolated"> and change the value to true.
6. Locate <attribute name="CallByValue"> and change the value to true.
7. Save and close the file.
➤ To remove the JSF libraries:
●
Navigate to the [appserver root]/server/all/deploy/jbossweb-tomcat55.sar directory and delete the
jsf-libs subdirectory and all its files.
➤ To disable the cluster service:
1. Open the [appserver root]/server/all/deploy/cluster-service.xml file in an editor, and locate and modify
the following attribute values:
●
mcast_port="34374"
●
ip_ttl="1"
2. Save and close the file.
3. Open the [appserver root]/server/all/deploy/tc5-cluster-service.xml file in an editor.
4. Locate ip_mcast and change it to false.
5. Save and close the file.
6. Open the [appserver root]/server/all/deploy/jms/hajndi-jms-ds.xml file in an editor.
7. Locate jnp.disableDiscovery and change the value to true.
8. Save and close the file.
➤ To remove the tests directory:
●
Delete the [appserver root]/docs/tests directory.
➤ To create the security policy file:
1. In a text editor, open a new document and add the following content:
grant {
// Allow everything for now
permission java.security.AllPermission;
};
2. Save the file as [appserver root]/server/all/conf/server.policy.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Modifying JBoss configuration files
24
➤ To modify the run.bat file (Windows only):
1. Open the [appserver root]/bin/run.bat file in an editor.
2. Locate rem Sun JVM memory allocation pool parameters and insert the following text
immediately before that string:
rem for Java 2 security
set JAVA_OPTS=%JAVA_OPTS% -Djava.security.manager
set JAVA_OPTS=%JAVA_OPTS% -Djava.security.policy=../server/all/conf/
server.policy
set JAVA_OPTS=%JAVA_OPTS% -Djava.security.debug=failure
3. Modify the line that immediately follows rem Sun JVM memory allocation pool parameters
to read as follows:
set JAVA_OPTS=%JAVA_OPTS% -XX:MaxPermSize=256m -Xms256m -Xmx1024m
-Djava.net.preferIPv4Stack=true
4. Modify the line that immediately follows rem Setup JBoss specific properties to set
encoding to UTF-8:
set JAVA_OPTS=%JAVA_OPTS% -Dadobeidp.serverName=server1
-Dfile.encoding=utf8 -Dprogram.name=%PROGNAME%
5. Save and close the file.
➤ To modify the run.sh file (Linux only):
1. Open the [appserver root]/bin/run.sh file in an editor.
2. Modify the line that immediately follows Setup JBoss specific properties to set encoding to
UTF-8 and security manager:
JAVA_OPTS="$JAVA_OPTS -Dadobeidp.serverName=server1 -Dfile.encoding=utf8
-Dprogram.name=$PROGNAME -Djava.security.manager
-Djava.security.policy=../server/all/conf/server.policy
-Djava.security.debug=failure"
Note: Ensure that this entry appears as a single line in the run.sh file.
3. Save and close the file.
➤ To modify the run.conf file:
1. Open the [appserver root]/bin/run.conf file in an editor.
2. Locate JAVA_OPTS="-server -Xms128m -Xmx128m" and modify it to read as follows:
JAVA_OPTS="-server -XX:MaxPermSize=256m -Xms256m -Xmx1024m"
Note: If you have Linux, also add the "-Djava.net.preferIPv4Stack=true" flag to remove the
warning “[HANamingService] Failed to start AutomaticDiscovery”.
3. Save and close the file.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Modifying JBoss configuration files
25
➤ To modify the log4j.xml file to increase the logging level from DEBUG to INFO:
1. Open the [appserver root]/server/all/conf/log4j.xml file in an editor.
2. Locate the following text in the FILE appender section and add the line that appears in bold:
<appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppe
nder">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="File" value="${jboss.server.home.dir}/log/cluster.log"/>
<param name="Threshold" value="INFO"/>
<param name="Append" value="false"/>
3. Locate the following text in the CONSOLE appender section:
<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
<param name="Target" value="System.out"/>
<param name="Threshold" value="INFO"/>
Modify the last line to read as follows:
<param name="Threshold" value="WARN"/>
4. Add the com.adobe category, and then find the Limit categories section and add the following
lines:
<category name="com.adobe">
<priority value="INFO"/>
</category>
5. Add the following category under the com.adobe category:
<category name="org.apache.xml.security.signature.Reference">
<priority value="WARN"/>
</category>
6. Save and close the file.
➤ To remove the JMX Console and Web Console:
●
To remove the default insecure web pages from JBoss, delete the following directories:
[appserver root]/server/all/deploy/jmx-console.war
[appserver root]/server/all/deploy/management
➤ To create JMS topics and queues:
1. Create a new file called adobe-service.xml and store it in the [appserver root]/server/all/deploy/jms
directory.
2. Add the following content to the file to define the topics and queues:
<?xml version="1.0" encoding="UTF-8"?>
<server>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=adobe_PECommandQueue">
<depends optional-attribute-name="
DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring the LiveCycle ES database connectivity
26
name="jboss.mq.destination:service=Queue,name=adobe_PEDCommandQueue">
<depends optional-attribute-name="
DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=adobe_PEInteractionQueue">
<depends optional-attribute-name="
DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=adobe_JobManagerQueue">
<depends optional-attribute-name="
DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Topic"
name="jboss.mq.destination:service=Queue,name=adobe_TaskEventTopic">
<depends optional-attribute-name="
DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
</server>
3. Save and close the file.
Configuring the LiveCycle ES database connectivity
To configure the LiveCycle ES database connectivity, complete the following tasks:
●
Configure the LiveCycle ES data source.
●
Configure JBoss to use your database as the default data source.
You must install database drivers to the installation directories of the application server. Drivers are
required to enable LiveCycle Configuration Manager and the application server to connect to the
LiveCycle ES database. Install the appropriate drivers for the database that you have installed.
You must also configure the data source to connect to the database. For JBoss, you can configure a MySQL,
SQL Server, or Oracle data source.
Configuring MySQL for Adobe-preconfigured JBoss
To enable Adobe-preconfigured JBoss to connect to the MySQL database that stores Flash Media
Rights Management Server data, complete these tasks:
●
Obtain and copy the MySQL JDBC driver to the instance of JBoss where you will deploy Flash Media
Rights Management Server.
●
Create a data source file and deploy it to the instance of JBoss where you will deploy Flash Media
Rights Management Server.
●
Configure JBoss to use MySQL for JMS.
If you are using a manually installed JBoss, see “Configuring MySQL for manually installed JBoss” on
page 28.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring MySQL for Adobe-preconfigured JBoss
27
Configuring the MySQL data source
Before you configure the MySQL data source, ensure that you already created the database on MySQL.
(See “Creating a MySQL database” on page 12.)
➤ To install the MySQL database driver:
●
Copy the mysql-connector-java-3.1.12-bin.jar driver file from the [DVD_root]/third_party/jdbc directory
on the installation DVD to the [appserver root]/server/all/lib directory.
➤ To create the MySQL data source file:
1. Copy the adobe-ds-jboss-mysql.xml file from the [DVD_root]/third_party/datasources directory on the
installation DVD to the [appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-mysql.xml file in a text editor and locate this line:
<connection-url>jdbc:mysql://localhost:3306/adobe</connection-url>
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
3306: The port used to access the database. The default port is 3306.
●
adobe: The name of the database that stores the LiveCycle ES data. You need to update the default
value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You need to update the default values, adobe and adobe, with the
credentials for your database.
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
LiveCycle Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
Setting MySQL as the JMS data source
If you are running Flash Media Rights Management Server with a MySQL database, set MySQL as the
default data source for JBoss. (JBoss is configured by default to use Hypersonic as the data source.)
This procedure assumes that the MySQL JDBC driver is installed in the [appserver root]/server/all/lib
directory.
➤ To set MySQL as the JMS data source:
1. Open the [appserver root]/server/all/deploy/mysql-ds.xml file in a text editor and modify the
<local-tx-datasource> element with your MySQL connection settings:
<jndi-name>DefaultDS</jndi-name>
<connection-url>jdbc:mysql://yourHostname:yourPort/
yourDatabaseName/</connection-url>
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring MySQL for manually installed JBoss
28
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>yourUserName</user-name>
<password>yourPassword</password>
2. Replace the bold text with values that are specific to your database:
yourHostname, yourPort, yourDatabaseName, youruserName, and yourPassword:
The database values the application server uses to access the database.
3. Save and close the file.
4. Open the [appserver root]/server/all/conf/login-config.xml file in a text editor and add the following
code within the <policy> element:
<application-policy name="MySqlDbRealm">
<authentication>
<login-module
code="org.jboss.resource.security.ConfiguredIdentityLoginModule" flag
= "required">
<module-option name="principal">database_name</module-option>
<module-option name="userName">database_username</module-option>
<module-option name="password">database_password</module-option>
<module-option
name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,
name=Default DS </module-option>
</login-module>
</authentication>
</application-policy>
5. Replace the bold text with values that are specific to your database:
database_name, database_username, and database_password: The user name and
password that the application server uses to access the database.
6. Save and close the file.
7. Restart JBoss.
Configuring MySQL for manually installed JBoss
To enable JBoss to connect to the MySQL database that stores Flash Media Rights Management Server
data, complete these tasks.
●
Obtain and copy the MySQL JDBC driver to the instance of JBoss where you will deploy Flash Media
Rights Management Server.
●
Create a data source file and deploy it to the instance of JBoss where you will deploy Flash Media
Rights Management Server.
●
Configure JBoss to use MySQL for JMS.
If you are using Adobe-preconfigured JBoss, see “Configuring MySQL for Adobe-preconfigured JBoss” on
page 26.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring MySQL for manually installed JBoss
29
Configuring the MySQL data source
Before configuring the MySQL data source, you must have already created the database on MySQL. (See
“Creating a MySQL database” on page 12.)
➤ To install the MySQL database driver:
●
Copy the mysql-connector-java-3.1.12-bin.jar driver file from the [DVD_root]/third_party/jdbc directory
on the installation DVD to the [appserver root]/server/all/lib directory.
➤ To create the MySQL data source file:
1. Copy the adobe-ds-jboss-mysql.xml file from the [DVD_root]/third_party/datasources directory on the
installation DVD to the [appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-mysql.xml file in a text editor and locate this line:
<connection-url>jdbc:mysql://localhost:3306/adobe</connection-url>
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
3306: The port used to access the database. The default port is 3306.
●
adobe: The name of the database that stores the LiveCycle ES data. You need to update the default
value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You need to update the default values, adobe and adobe, with the
credentials for your database.
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
LiveCycle Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
Setting MySQL as the JMS data source
If you are running Flash Media Rights Management Server with a MySQL database, set MySQL to be the
default data source for JBoss. (JBoss is configured by default to use Hypersonic for the data source.)
This procedure assumes that the MySQL JDBC driver is installed in the [appserver root]/server/all/lib
directory.
➤ To set MySQL as the JMS data source:
1. Navigate to the [appserver root]/server/all/deploy directory and delete the hsqldb-ds.xml file.
2. Navigate to the [appserver root]/docs/examples/jca directory and copy the mysql-ds.xml file to the
[appserver root]/server/all/deploy directory.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring MySQL for manually installed JBoss
30
3. Open the [appserver root]/server/all/deploy/mysql-ds.xml file in a text editor and modify the
<local-tx-datasource> element with your MySQL connection settings:
<jndi-name>MySqlDS</jndi-name>
<connection-url>jdbc:mysql://yourHostname:yourPort/
yourDatabaseName</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>yourUserName</user-name>
<password>yourPassword</password>
4. Replace the bold text with values that are specific to your database:
●
MySqlDS must be changed to DefaultDS.
●
yourHostname, yourPort, yourDatabaseName, youruserName, and yourPassword (the
database values the application server uses to access the database).
5. Save and close the file.
6. Open the [appserver root]/server/all/conf/standardjaws.xml file and change the <type-mapping>
element to MySQL:
<type-mapping>mySQL</type-mapping>
7. Save and close the file.
8. Open the standardjbosscmp-jdbc.xml file and change the following elements (not necessarily
contiguous):
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>mySQL</datasource-mapping>
<fk-constraint>true</fk-constraint>
9. Remove the text <!—optional since 4.0 and .." from the <datasource-mapping> tag to
uncomment it.
10. Save and close the file.
11. Open the login-config.xml file in a text editor and add the following text within the <policy>
element:
<application-policy name="MySqlDbRealm">
<authentication>
<login-module
code="org.jboss.resource.security.ConfiguredIdentityLoginModule" flag
= "required">
<module-option name="principal">database_name</module-option>
<module-option name="userName">database_username</module-option>
<module-option name="password">database_password</module-option>
<module-option
name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,
name=DefaultDS </module-option>
</login-module>
</authentication>
</application-policy>
12. Replace the bold text with values that are specific to your database:
database_name, database_username, and database_password: The user name and
password that the application server uses to access the database.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring Oracle for Adobe-preconfigured JBoss
31
13. Save and close the file.
14. Replace the hsql-jdbc2-service.xml file in the [appserver root]/server/all/deploy-hasingleton/jms
directory with the mysql-jdbc2-service.xml file from the [appserver root]/docs/examples/jms directory.
15. Open the [appserver root]/server/all/deploy-hasingleton/jms/mysql-jdbc2-service.xml file and change
MySqlDS to DefaultDS:
<mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
name="jboss.mq:service=PersistenceManager">
<depends optional-attributename="ConnectionManager">
jboss.jca:service=DataSourceBinding,name=DefaultDS
</depends>
<attribute name="SqlProperties">
...
16. In the same file, mysql-jdbc2-service.xml, change the SELECT_MAX_TX line to the following text:
SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES
17. Rename the hsqldb-jdbc-state-service.xml file to mysql-jdbc-state-service.xml.
18. Restart JBoss.
Configuring Oracle for Adobe-preconfigured JBoss
To enable JBoss to connect to the Oracle database that stores Flash Media Rights Management Server
data, complete the following tasks if you are manually deploying Flash Media Rights Management Server:
●
Obtain and copy the Oracle JDBC driver to the instance of JBoss where you will deploy Flash Media
Rights Management Server.
●
Create a data source file and deploy it to the instance of JBoss where you will deploy Flash Media
Rights Management Server.
●
Configure JBoss to use Oracle for JMS.
Configuring the Oracle data source
Before you configure the Oracle data source, you must have already created the database on Oracle. (See
“Creating an Oracle database” on page 13.)
➤ To install the Oracle 10g database driver:
1. Access the Oracle 10g driver file from the [LiveCycleES root]/lib/db/oracle directory. You can also
download the Oracle 10g Release 2 (10.2.0.2 Thin) driver from this location:
www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
2. Copy the ojdbc14.jar driver file to the [appserver root]/server/all/lib directory.
➤ To create the Oracle data source file:
1. Copy the adobe-ds-jboss-oracle.xml file from the [DVD_root]/third_party/datasources directory on the
installation DVD to the [appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-oracle.xml file in a text editor and locate this line:
<connection-url>jdbc:oracle:thin:@//localhost:1521/adobe</connection-url>
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring Oracle for Adobe-preconfigured JBoss
32
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
1521: The port used to access the database. The default port is 1521.
●
adobe: The name of the database that stores the Flash Media Rights Management Server data. You
need to update the default value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You need to update the default values, adobe and adobe, with the
credentials for your database.
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
LiveCycle Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
Setting Oracle as the JMS data source
If you are running LiveCycle ES with an Oracle database, set Oracle to be the default data source for JBoss.
(JBoss is configured by default to use Hypersonic for the data source.)
This procedure assumes that the Oracle JDBC driver is installed in the [appserver root]/server/all/lib
directory.
➤ To set Oracle to be the JMS data source:
1. Navigate to the [appserver root]/server/all/deploy directory and delete the mysql-ds.xml file.
2. Navigate to the [appserver root]/docs/examples/jca directory and copy the oracle-ds.xml to the
[appserver root]/server/all/deploy directory.
3. Open the [appserver root]/server/all/deploy/oracle-ds.xml file in a text editor and modify the
<local-tx-datasource> element with your Oracle connection settings:
<jndi-name>OracleDS</jndi-name>
<connection-url>jdbc:oracle:thin:@youroraclehost:1521:yoursid
</connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>x</user-name>
<password>y</password>
4. Replace the bold text with values that are specific to your database:
●
OracleDS: Change this value to DefaultDS.
●
youroraclehost: Replace this value with the host name of your Oracle server.
●
1521: If Oracle is not using the default port, replace this value with the appropriate port number.
●
yoursid: Replace this value with your Oracle System Identifier.
●
Replace x with the user name to access the Oracle database and y with the password that is
associated with the user. The application server uses these credentials to access the database.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring Oracle for Adobe-preconfigured JBoss
33
5. Save and close the file.
6. Open the [appserver root]/server/all/conf/standardjaws.xml file and change the <type-mapping>
element to Oracle:
<type-mapping>Oracle8</type-mapping>
7. Save and close the file.
8. Open the [appserver root]/server/all/conf/standardjbosscmp-jdbc.xml file and change the following
elements (not necessarily contiguous):
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>Oracle8</datasource-mapping>
<fk-constraint>true</fk-constraint>
9. Save and close the file.
10. Open the [appserver root]/server/all/conf/login-config.xml file in a text editor and add the following
text within the <policy> element:
<application-policy name = "OracleDbRealm">
<authentication>
<login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule" flag =
"required">
<module-option name = "principal">database_name </module-option>
<module-option name = "userName">database_username</module-option>
<module-option name = "password">password</module-option>
<module-option name ="managedConnectionFactoryName">
jboss.jca:service=LocalTxCM,name=DefaultDS</module-option>
</login-module>
</authentication>
</application-policy>
11. Replace the bold text with values that are specific to your database:
database_name, database_username, and password: The user name and password that the
application server uses to access the database.
12. Save and close the file.
13. Delete the mysql-jdbc2-service.xml file from the [appserver root]/server/all/deploy-hasingleton/jms
directory.
14. Copy the oracle-jdbc2-service.xml file from the [appserver root]/docs/examples/jms directory to the
[appserver root]/server/all/deploy-hasingleton/jms directory.
15. In the oracle-jdbc2-service.xml file in the [appserver root]/server/all/deploy-hasingleton/jms directory,
change OracleDS to DefaultDS:
<mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
name="jboss.mq:service=PersistenceManager">
<depends optional-attributename="ConnectionManager">
jboss.jca:service=DataSourceBinding,name=DefaultDS
</depends>
<attribute name="SqlProperties">
...
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring Oracle for manually installed JBoss
34
16. Save and close the file.
17. Rename the [appserver root]/server/all/deploy-hasingleton/jms/mysqldb-jdbc-state-service.xml file to
oracle-jdbc-state-service.xml.
18. Restart JBoss.
Configuring Oracle for manually installed JBoss
To enable JBoss to connect to the Oracle database that stores Flash Media Rights Management Server
data, complete the following tasks if you are manually deploying Flash Media Rights Management Server:
●
Obtain and copy the Oracle JDBC driver to the instance of JBoss where you will deploy Flash Media
Rights Management Server.
●
Create a data source file and deploy it to the instance of JBoss where you will deploy Flash Media
Rights Management Server.
●
Configure JBoss to use Oracle for JMS.
Configuring the Oracle data source
Before configuring the Oracle data source, you must have already created the database on Oracle. (See
“Creating an Oracle database” on page 13.)
➤ To install the Oracle 10g database driver:
●
Copy the ojdbc14.jar driver file from the [LiveCycleES root]/lib/db/oracle directory to the [appserver
root]/server/all/lib directory. In addition, you can download the Oracle 10g Release 2 (10.2.0.2 Thin)
driver from this location:
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
➤ To create the Oracle data source file:
1. Copy the adobe-ds-jboss-oracle.xml file from the [DVD_root]/third_party/datasources directory to the
[appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-oracle.xml file in a text editor and locate this line:
<connection-url>jdbc:oracle:thin:@//localhost:1521/adobe</connection-url>
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
1521: The port used to access the database. The default port is 1521.
●
adobe: The name of the database that stores the Flash Media Rights Management Server data. You
need to update the default value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You need to update the default values, adobe and adobe, with the
credentials for your database.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring Oracle for manually installed JBoss
35
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
LiveCycle Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
Setting Oracle as the JMS data source
If you are running Flash Media Rights Management Server with a Oracle database, set Oracle to be the
default data source for JBoss. (JBoss is configured by default to use Hypersonic for the data source.)
This procedure assumes that the Oracle JDBC driver is installed in the [appserver root]/server/all/lib
directory.
➤ To set Oracle to be the JMS data source:
1. Navigate to the [appserver root]/server/all/deploy directory and delete the hsqldb-ds.xml file.
2. Copy the oracle-ds.xml file from the [appserver root]/docs/examples/jca directory to the [appserver
root]/server/all/deploy directory.
3. Open the [appserver root]/server/all/deploy/oracle-ds.xml file in a text editor and modify the
<local-tx-datasource> element with your Oracle connection settings:
<jndi-name>OracleDS</jndi-name>
<connection-url>jdbc:oracle:thin:@youroraclehost:1521:yoursid
</connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>x</user-name>
<password>y</password>
4. Replace the bold text with values that are specific to your database:
●
OracleDS: Change this value to DefaultDS.
●
youroraclehost: Replace this value with the host name of your Oracle server.
●
1521: If Oracle is not using the default port, replace this value with the appropriate port number.
●
yoursid: Replace this value with your Oracle System Identifier.
●
Replace x with the user name to access the Oracle database and y with the password that is
associated with the user. The application server uses these credentials to access the database.
5. Save and close the file.
6. Open the [appserver root]/server/all/conf/standardjaws.xml file and change the <type-mapping>
element to Oracle:
<type-mapping>Oracle8</type-mapping>
7. Save and close the file.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring Oracle for manually installed JBoss
36
8. Open the [appserver root]/server/all/conf/standardjbosscmp-jdbc.xml file and change the following
elements (not necessarily contiguous):
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>Oracle8</datasource-mapping>
<fk-constraint>true</fk-constraint>
9. Remove the text: <!—optional since 4.0 and .. from the <datasource-mapping> tag to
uncomment it.
10. Save and close the file.
11. Open the [appserver root]/server/all/conf/login-config.xml file in a text editor and add the following
text within the <policy> element:
<application-policy name = "OracleDbRealm">
<authentication>
<login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule" flag =
"required">
<module-option name = "principal">database_name </module-option>
<module-option name = "userName">database_username</module-option>
<module-option name = "password">password</module-option>
<module-option name ="managedConnectionFactoryName">
jboss.jca:service=LocalTxCM,name=DefaultDS</module-option>
</login-module>
</authentication>
</application-policy>
12. Replace the bold text with values that are specific to your database:
database_name, database_username, and password: The user name and password that the
application server uses to access the database.
13. Save and close the file.
14. Delete the hsql-jdbc2-service.xml file from the [appserver root]/server/all/deploy-hasingleton/jms
directory.
15. Copy the oracle-jdbc2-service.xml file from the [appserver root]/docs/examples/jms directory to the
[appserver root]/server/all/deploy-hasingleton/jms directory.
16. Open the [appserver root]/server/all/deploy-hasingleton/jms/oracle-jdbc2-service.xml file and change
OracleDS to DefaultDS:
<mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
name="jboss.mq:service=PersistenceManager">
<depends optional-attributename="ConnectionManager">
jboss.jca:service=DataSourceBinding,name=DefaultDS
</depends>
<attribute name="SqlProperties">
...
17. Save and close the file.
18. Rename the hsqldb-jdbc-state-service.xml file that is located in the [appserver root]/server/all/
deploy-hasingleton/jms directory to oracle-jdbc-state-service.xml.
Adobe Flash Media Rights Management Server
Configuring a JBoss Application Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring SQL Server
37
19. Restart JBoss.
Configuring SQL Server
To enable JBoss to connect to the SQL Server database that stores Flash Media Rights Management Server
data, complete the following tasks:
●
Obtain and copy the SQL Server JDBC driver files to the instance of JBoss where you will deploy
Flash Media Rights Management Server.
●
Create a SQL Server data source file and deploy it to the instance of JBoss where you will deploy
Flash Media Rights Management Server.
●
Configure JBoss to use SQL Server for JMS.
Configuring the SQL Server data source
Before configuring the SQL Server data source, you must have already created the LiveCycle ES database
on SQL Server. (See “Creating a SQL Server database” on page 14.)
➤ To install the SQL database driver:
1. Obtain the SQL Server 2005 JDBC 1.1 database driver from the Microsoft website.
2. (Windows) Download the *.exe file and run the file, and then extract the files to a temporary directory
(referred to as the [SQL_root] directory in the remainder of this section).
3. (Linux) Extract the *.tar.gz files to a temporary directory (referred to as the [SQL_root] directory in the
remainder of this section).
4. Copy the sqljdbc.jar file from the [SQL_root]/sqljdbc_1.1/enu directory to the [appserver root]/server/
all/lib directory.
➤ To create the SQL Server data source file:
1. Copy the adobe-ds-jboss-mssql.xml file from the [DVD_root]/third_party/datasources directory to the
[appserver root]/server/all/deploy directory.
2. Open the adobe-ds-jboss-mssql.xml file in a text editor and locate this line:
<connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=adobe</connecti
on-url>
3. Replace the following text with values that are specific to your database:
●
localhost: The name, IP address, or fully-qualified path of the computer that hosts the database.
The default is localhost.
●
1433: The port used to access the database. The default port is 1433.
●
adobe: The name of the database that stores the Flash Media Rights Management Server data. You
need to update the default value, adobe, with your database name.
●
database_username and password: The user name and password that the application server
uses to access the database. You need to update the default values, adobe and adobe, with the
credentials for your database.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring the SQL Server data source
38
4. Complete step 3 for the IDP_DS, EDC_DS and com.celequest.metadata.metaDatasource
elements.
Note: The com.celequest.metadata.metaDatasource element is required only if you are using
LiveCycle Business Activity Monitoring ES
5. Save the file as adobe-ds.xml in the [appserver root]/server/all/deploy directory.
6. Restart JBoss.
The following steps provide instructions on how to use integrated security to make a trusted connection
with SQL Server.
➤ To configure Integrated Security on Windows:
1. Modify the adobe-ds.xml file, located in [appserver root]\server\all\deploy, to add
integratedSecurity=true to the connection URL, as shown in this example:
jdbc:sqlserver://<serverhost>:<port>;databaseName=<dbname>;integratedSecurit
y=true.
2. Add the sqljdbc_auth.dll file to the Windows systems path (C:\Windows) on the computer that is
running JBoss. The sqljdbc_auth.dll file is located with the Microsoft SQL JDBC 1.1 driver installation
(default is [dbserver root]/sqljdbc_1.1/enu/auth/x86).
3. Open the JBoss for Adobe LiveCycle ES v8.0 service and modify the Local System > Log On As property
to use an appropriate user account. This change is not required if you are running JBoss from the
command line.
4. Set SQL Server’s security to Windows Authentication only.
Configuring JMS with Microsoft SQL Server
This section applies to both Adobe-preconfigured JBoss and manually installed JBoss.
Setting SQL Server as the JMS data source
If you are running Flash Media Rights Management Server with a SQL Server database, set SQL Server to
be the default data source for JBoss. (It is configured by default to use Hypersonic for the data source.)
This procedure assumes that the SQL Server JDBC driver is installed in the [appserver root]/server/all/lib
directory.
➤ To set SQL Server to be the JMS data source:
1. Navigate to the [appserver root]/server/all/deploy directory and delete the hsqldb-ds.xml file. If you are
using the Adobe-preconfigured JBoss from the DVD, delete the mysql-ds.xml file.
2. Install the JBossMQ patch file, jbossmq.jar. You must replace the existing jbossmq.jar file in the
[appserver root]/server/all/lib directory. You can obtain the updated jbossmq.jar file from the
thirdparty\jboss\patches directory in the installation media.
3. Navigate to the [appserver root]/docs/examples/jca directory and copy the mssql-ds.xml file to the
[appserver root]/server/all/deploy directory.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring the SQL Server data source
39
4. Open the mssql-ds.xml file in a text editor and modify the <local-tx-datasource> element with
your SQL Server connection settings:
<jndi-name>DefaultDS</jndi-name>
<connection-url>jdbc:sqlserver:// your-hostname:
your-port;DatabaseName=yourdatabase-name</connection-url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver
</driver-class>
<user-name>yourUserName</user-name>
<password>yourPassword</password>
5. Save and close the file.
6. Open the [appserver root]/server/all/conf/standardjaws.xml file and change the <type-mapping>
element to SQL Server:
<type-mapping>MS SQLSERVER2000</type-mapping>
7. Open the [appserver root]/server/all/conf/standardjbosscmp-jdbc.xml file and change the following
elements (not necessarily contiguous):
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>MS SQLSERVER2000</datasource-mapping>
<fk-constraint>true</fk-constraint>
8. (Manually installed JBoss only) Remove the comment tags from the <datasource-mapping> tag to
uncomment it. For example, remove “<!—optional since 4.0 ....” and its corresponding
"--tag”>.
9. Save and close the file.
10. Open the [appserver root]/server/all/conf/login-config.xml file in a text editor and add the following
lines within the <policy> element:
<application-policy name = "MSSQLDbRealm">
<authentication>
<login-module code =
"org.jboss.resource.security.ConfiguredIdentityLoginModule"
flag = "required">
<module-option name = "principal">database_name</module-option>
<module-option name = "userName">database_username</module-option>
<module-option name ="password">password</module-option>
<module-option name =
"managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=
DefaultDS
</module-option>
</login-module>
</authentication>
</application-policy>
11. Replace the bold text with values that are specific to your database:
database_name, database_username, and password: The user name and password that the
application server uses to access the database.
12. Save and close the file.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Configuring a JBoss Application Server
Configuring the SQL Server data source
40
13. Delete the [appserver root]/server/all/deploy-hasingleton/jms/hssql-jdbc2-service.xml file or, if you are
using the Adobe-preconfigured JBoss from the DVD, delete the mysql-jdbc2-service.xml. Copy the
[appserver root]/docs/examples/jms/mssql-jdbc2-service.xml file to [appserver root]/server/all/
deploy-hasingleton/jms.
14. Open the [appserver root]/server/all/deployhasingleton/jms/mssql-jdbc2-service.xml file and change
mbean code to reference MSSQLJDBCStateManager and DefaultDS:
<mbean code="org.jboss.mq.pm.jdbc2.MSSQLPersistenceManager"
name="jboss.mq:service=PersistenceManager">
<depends optional-attributename="
ConnectionManager">jboss.jca:service=DataSourceBinding,name=DefaultDS
</depends>
<attribute name="SqlProperties">
...
15. Rename the [appserver root]/server/all/deploy-hasingleton/jms/hsqldb-jdbc-state-service.xml file to
mssql-jdbc-state-service.xml or, if you are using the Adobe-preconfigured JBoss from the DVD, rename
the [appserver root]/server/all/deploy-hasingleton/jms/mysql-jdbc-state-service.xml file to
mssql-jdbc-state-service.xml.
16. Open the [appserver root]/server/all/deploy-hasingleton/jms/mssql-jdbc-stateservice.xml file and
change mbean code to reference MSSQLJDBCStateManager:
<mbean code="org.jboss.mq.sm.jdbc.MSSQLJDBCStateManager"
name="jboss.mq:service=StateManager">
17. Restart JBoss.
4
Installing, Configuring, and Deploying
This chapter describes the tasks that are required to install, configure, and deploy the Flash Media
Rights Management Server and its supporting LiveCycle ES environment. You must perform the following
tasks:
1. Run the Flash Media Rights Management Server installer. (See “To install Flash Media
Rights Management Server:” on page 43.)
2. Install the LiveCycle ES platform. (See “To install LiveCycle ES:” on page 43.)
3. Install the LiveCycle ES service pack. (See“To install the service pack for the LiveCycle ES server:” on
page 44.)
4. Configure and deploy LiveCycle ES using LiveCycle Configuration Manager. (See “To perform
configuration or deployment tasks using LiveCycle Configuration Manager:” on page 47.)
About the installation, configuration, and deployment process
Installing, configuring, and deploying Flash Media Rights Management Server involves the following
processes:
Installing: You install Flash Media Rights Management Server by running the installation program.
Installing Flash Media Rights Management Server places all of the required files onto your computer,
within one installation directory structure. The default installation directory is C:\Adobe (Windows) or
/opt/adobe (Linux); however, you can install the files to a different directory. In this document, the
default installation directory for Flash Media Rights Management Server is referred to as [FMRMS root]
and, for LiveCycle ES, it is [LiveCycleES root].
Configuring and assembling: Configuring Flash Media Rights Management Server modifies a variety
of settings that determine how Flash Media Rights Management Server works. Assembling the product
places all of the installed components into several deployable EAR and JAR files, according to your
configuration instructions. Configure and assemble the components for deployment by running
LiveCycle Configuration Manager.
Deploying: Deploying the product involves deploying the assembled EAR files and supporting files to
the JBoss Application Server on which you plan to run your Flash Media Rights Management Server
solution.
Initializing the database: Initializing the database to be used with Flash Media
Rights Management Server creates tables for use with User Management and other components.
Deploying any solution component that connects to the database requires you to initialize the
database after the deployment process.
41
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Installing, Configuring, and Deploying
Flash Media Rights Management Server installation
42
Flash Media Rights Management Server installation
This section describes how to use the installation program to install Flash Media
Rights Management Server on a Windows or Linux operating system.
Before you install, ensure that your environment includes the software and hardware that is required to
run Flash Media Rights Management Server. You should also have prepared the environment as required.
(See “Preparing the Environment” on page 7.)
Installation considerations
When you run an installation program, you need your Flash Media Rights Management Server serial
number.
Note: To successfully install, you need read and write permissions for the installation directory. The
following installation directories are the defaults; however, you can specify a different directory as
required:
●
(Windows) C:\Adobe\LiveCycle8\ and C:\Adobe\FMRMS1.0
●
(Linux) /opt/adobe/livecycle8/ and /opt/adobe/FMRMS1.0
When installing on Linux, the installation program uses the logged-in user's home directory as a
temporary directory for storing files. As a result, messages such as the following text may appear in the
console:
WARNING: could not delete temporary file /home/<username>/ismp001/1556006
When you complete the installation, you must manually delete the temporary files.
Caution: Ensure that the temporary directory for your operating system meets the minimum
requirements as outlined in “Preparing the Environment” on page 7. The temporary directory is
one of the following locations:
●
(Windows) TMP or TEMP path as set in the environment variables
●
(Linux) Logged-in user’s home directory
The InstallShield command line parameter -is:tempdir is not supported with the Flash Media
Rights Management Server installer. To work around this limitation, use the TMP environment
variable to point to a disk that has the required amount of free space.
On Linux systems, you can install, configure, and deploy as a non-root user.
Note: When you are installing on Linux, you must be logged in as the root user to successfully install the
solution components to the default locations, which are /opt/adobe/FMRMS1.0 and
/opt/adobe/LiveCycle8/. If you are logged in as a non-root user, you must change the installation
directory to one that you have permissions for (read-write-execute privileges). For example, you can
change the directory to home/adobe/livecycle8.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Installing, Configuring, and Deploying
Installing Flash Media Rights Management Server
43
Installing Flash Media Rights Management Server
Before you install Flash Media Rights Management Server, make sure that you reviewed all previous
chapters and performed all the required preparatory tasks.
This section covers the initial installation of LiveCycle ES. For information about configuration and
deployment, see “Selecting tasks for configuring and deploying LiveCycle ES” on page 46.
Note: To avoid permission issues during the deployment, ensure that you are logged in as the user who
will run the JBoss process when you run the Flash Media Rights Management Server installer and
LiveCycle Configuration Manager.
Flash Media Rights Management Server is installed by using a wizard that guides you step by step through
the process of installing Flash Media Rights Management Server, LiveCycle ES, and the LiveCycle ES
Service Pack.
➤ To install Flash Media Rights Management Server:
1. On the install media, double-click the appropriate executable file at the root to start the installation.
●
(Windows) win32_fmrms_setup.exe
●
(Linux) linux_fmrms_setup.bin
2. On the Welcome screen, click Next.
3. Read the Adobe Flash Media Rights Management Server License Agreement, select I accept the terms
of the license agreement, and then click Next.
4. Accept the default directory as listed or click Browse and navigate to the directory where you want to
install the product, and then click Next. This directory is referred to as [FMRMS root].
5. Read the summary information and, if acceptable, click Install. If not acceptable, click Back and make
the necessary changes.
Flash Media Rights Management Server installs and then invokes the LiveCycle ES installer.
➤ To install LiveCycle ES:
1. When prompted, select English as the language for the installation, and then click OK.
Note: English is the only language available for this release.
2. On the Welcome screen, click Next.
3. On the Destination screen, accept the default directory as listed or click Browse and navigate to the
directory where you want to install, and then click Next.
Note: If you type the name of a directory that does not exist, it will be created for you.
Caution: When you install, you can specify a different installation location. If you are installing on Linux,
the directory you specify should not contain any spaces; if it does, the installation program does
not install properly.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Installing, Configuring, and Deploying
Installing Flash Media Rights Management Server
44
4. Type a serial number in the text box and click Add. After you add the serial number to the list, click
Next.
Note: Rights Management ES and Adobe LiveCycle Foundation are the only LiveCycle ES components
that will be installed.
5. Read the Product License Agreement and, if you agree, select I accept to the terms of the license
agreement, and then click Next.
6. Review the installation details and click Install. The installation program displays the progress of the
installation. A summary screen appears when the installation is completed.
7. Review the release notes that are displayed and click Next.
8. Deselect Start LiveCycle Configuration Manager and then click Finish.
The LiveCycle ES Service Pack 2 installer starts automatically. This installer opens a wizard that guides you
through the installation.
Caution: Do not run LiveCycle Configuration Manager at this point; install the LiveCycle ES Service Pack
and quickfix patch prior to configuration.
➤ To install the service pack for the LiveCycle ES server:
1. When prompted, select English as the language to use for the installation and then click OK.
Note: English is the only language available for this release.
2. On the Welcome screen, click Next.
3. On the Service Pack Installation Location screen, verify that the default location displayed is correct for
your existing installation or click Browse to select the alternate folder where LiveCycle ES is currently
installed, and then click Next.
4. On the Service Pack Summary screen, review the information and, if the information is correct, click
Next. Click Back to correct any errors.
5. On the Service Pack Summary (continued) screen, review the information and, if the information is
correct, click Next. Click Back to correct any errors.
6. On the Service Pack Installation Completion screen, click Install to apply the updates.
Note: Allow the service pack installer to completely apply the service pack updates. Typical time to apply
the patch updates is approximately 5 minutes, but it may take as much as 15 minutes (depending
on the resources available on your system).
7. When the Service Pack Installation Completion screen refreshes to indicate a successful installation,
ensure that the Launch LiveCycle Configuration Manager check box is deselected, and then click
Finish to exit the wizard.
Caution: Do not run LiveCycle Configuration Manager at this point; install the LiveCycle ES service pack
and quickfix patch prior to configuration.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Installing, Configuring, and Deploying
About LiveCycle Configuration Manager
45
8. On the Adobe Flash Media Rights Management Server - Installer wizard, click Finish to exit that wizard.
➤ To install the LiveCycle ES quickfix:
1. On the install media, navigate to \livecycle_server_quickfix\LC8.0.1.2_QF_2.11\x86_win32 and
double-click the adobe_livecycle_8_0_qf.exe file (for Windows) or adobe_livecycle_8_0_qf.bin file (for
Linux) to start the quickfix installation.
2. When prompted, select English as the language to use for the installation and then click OK.
Note: English is the only language available for this release.
3. On the Welcome screen, click Next.
4. On the Patch Installation Location screen, verify that the default location displayed is correct for your
existing installation or click Browse to select the alternate folder where LiveCycle ES is currently
installed, and then click Next.
5. On the Patch Summary screen, review the information and, if the information is correct, click Next.
Click Back to correct any errors.
6. On the Patch Summary (continued) screen, review the information and, if the information is correct,
click Install. Click Back to correct any errors.
7. On the Patch Installation Completion screen, click Next to apply the updates.
8. When the Patch Installation Completion screen refreshes to indicate a successful installation, ensure
that the Start LiveCycle Configuration Manager check box is deselected, and then click Finish to exit
the wizard.
About LiveCycle Configuration Manager
LiveCycle Configuration Manager is a wizard-like tool used to configure, deploy, and validate LiveCycle ES
components for deployment to the application server. You have the option of using
LiveCycle Configuration Manager to configure the application server and deploy the product EAR files to
the application server.
LiveCycle Configuration Manager is installed with the solution component files when you run the
LiveCycle ES installation program. When you run LiveCycle Configuration Manager, specify the
LiveCycle ES solution components you are configuring and the tasks for LiveCycle Configuration Manager
to perform.
You can start LiveCycle Configuration Manager from the installation program to configure solution
components during the installation process, or you can start LiveCycle Configuration Manager any time
after the installation. If you are planning to use LiveCycle Configuration Manager to configure or deploy to
the application server, the application server must be started to enable LiveCycle Configuration Manager
to perform configuration tasks on it.
You can configure an application server that is installed on a different computer than the one on which
you are running LiveCycle Configuration Manager. However, an application server must also be installed
(but does not have to be running) on the LiveCycle Configuration Manager computer so that
LiveCycle Configuration Manager can use the application server library files.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Installing, Configuring, and Deploying
Selecting tasks for configuring and deploying LiveCycle ES
46
Selecting tasks for configuring and deploying LiveCycle ES
After you perform the installation, run LiveCycle Configuration Manager to perform a variety of tasks:
●
Configure LiveCycle ES solution components in an EAR file for deploying to the application server
●
Configure application server properties to support LiveCycle ES
●
Validate application server configuration
●
Deploy LiveCycle ES EAR files
●
Initialize the LiveCycle ES database
●
Deploy LiveCycle ES components
●
Validate the LiveCycle ES component deployment
Although you can use LiveCycle Configuration Manager to configure the application server and set up
data sources to the database, you may prefer to complete these steps manually.
You may want to configure your application server manually for these reasons:
●
You have other applications running on the application server and are concerned about possible
conflicting configurations.
●
Corporate security procedures for configuration management dictate finer control.
●
You are performing deployments where automatic configuration is not available.
For the manual configuration, you will do the following tasks:
●
Use LiveCycle Configuration Manager to configure LiveCycle ES components to get the temp
directories.
●
Manually configure the application server and data sources, and deploy LiveCycle ES EAR files.
●
Run LiveCycle Configuration Manager to initialize the database.
Running LiveCycle Configuration Manager
When you run LiveCycle Configuration Manager, you can select the tasks for the program to perform
automatically.
Note: Using LiveCycle Configuration Manager to deploy LiveCycle ES solution components to remote
servers is supported only for node-managed application servers, and not for stand-alone
application servers.
Tip: LiveCycle Configuration Manager verifies the values that are specified on each screen when you click
Next. If it cannot validate a value, a warning appears, the property on the screen turns red, and you
cannot proceed until you enter a valid value.
When LiveCycle Configuration Manager completes the configuration, it places the files to be deployed to
the application server (adobe-livecycle-native-jboss-[OS].ear, adobe-livecycle-jboss.ear, and
adobe-workspace-client.ear) in the following directory:
●
(Windows) [LiveCycleES root]\configurationManager\export
●
(Linux) [LiveCycleES root]/configurationManager/export
If you plan to manually deploy LiveCycle ES to the application server, the files are located in the
appropriate directory.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Installing, Configuring, and Deploying
Running LiveCycle Configuration Manager
47
If you are configuring a remote application server, ensure that an application server is also installed on the
LiveCycle Configuration Manager computer so that LiveCycle Configuration Manager can use the
application server library files.
➤ To perform configuration or deployment tasks using LiveCycle Configuration Manager:
1. Start the application server.
2. Start LiveCycle Configuration Manager by navigating to the [LiveCycleES root]/configurationManager/
bin directory and entering the following command:
●
(Windows) ConfigurationManager.bat
●
(Linux) ./ConfigurationManager.sh
3. On the Welcome screen, click Next.
4. On the Upgrade Selection screen, ensure that Upgrade LiveCycle 7.x is deselected, and then click
Next.
5. On the Solution Component screen, keep the defaults and click Next.
6. On the Task Selection screen, keep the defaults except for deselecting Import LiveCycle ES Samples,
and click Next.
Caution: Do not import the LiveCycle ES samples; they are not required by Flash Media
Rights Management Server and they slow down the deployment process considerably.
Note: If you do not want to configure the application server and deploy LiveCycle ES by using
LiveCycle Configuration Manager, select the Configure LiveCycle ES task only. After
completing this task in LiveCycle Configuration Manager, configure the application server,
deploy the configured EAR files, and return to LiveCycle Configuration Manager to initialize the
database, and deploy and validate the component files.
7. Follow the instructions on the LiveCycle Configuration Manager screens. The following configurations
are required for Flash Media Rights Management Server.
●
On the Application Server Configuration Details screen, select Stand-alone as the deploy type.
●
On the Server Settings Configuration screen, enter or browse to the locations for JAVA_HOME and
the POP3.jar file on the application server.
●
On the Datasource Configuration screen, provide the location of the JDBC driver for your database.
For Oracle and MySQL, the drivers are located in the [LiveCycleES root]/lib/db/[database] directory.
For SQL Server, if you have not already done so, install the database driver by following these steps:
●
Download the SQL Server 2005 JDBC 1.1 database driver from the Microsoft website.
●
(Windows) Run the file. Extract the files to a temporary directory (referred to as the [SQL_root]
directory in the remainder of this section).
●
(Linux) Extract the *.tar.gz files to a temporary directory (referred to as the [SQL_root] directory in
the remainder of this section). The JDBC driver file is [SQL_root]/sqljdbc_1.1/enu/sqljdbc.jar.
Tip: For more information about the content or input that is required for any screen, press the F1 key on
your keyboard to view Help for that screen.
Note: LiveCycle Configuration Manager requires you to enter the IP address, or qualified host name, of the
server that is running the application server. The default value of localhost will not work.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Installing, Configuring, and Deploying
Viewing the error log
48
8. After you exit LiveCycle Configuration Manager, return to the Flash Media Rights Management Server
install wizard screen and click Finish.
Viewing the error log
If any errors occur during the installation, the installation program creates a log file called log.txt, which
contains the error messages. The log file is located in the [LiveCycleES root] directory.
For information about errors that may occur during installation, see “Troubleshooting” on page 58.
5
Initial Administration Tasks
This chapter describes the tasks that an administrator needs to perform after the installation is complete.
Restart the application server
When you first deploy Flash Media Rights Management Server, the server is in a deployment mode in
which most solution components are in memory. As a result, the memory consumption is high and the
server is not in a typical production state. You must restart the application server to get the server back to
a clean state.
Verify access to LiveCycle Administration Console
You can verify the deployment by logging in to LiveCycle Administration Console. If you can log in,
Flash Media Rights Management Server is running on the application server and the default user is
created in the database.
You can review the application server log files to ensure that components were deployed correctly or to
determine the cause of any deployment issues you may encounter.
Accessing LiveCycle Administration Console
LiveCycle Administration Console is the web-based portal for accessing a variety of configuration pages,
where you set run-time properties that control the way Flash Media Rights Management Server operates.
When you log in to LiveCycle Administration Console, you can change the attributes and behaviors of
specific services and change global settings. You access Archive Administration, which administrators use
for deploying services to a production environment from within LiveCycle Administration Console.
The default user name and password for logging in to LiveCycle Administration Console is administrator
and password. After you log in the first time, you can access User Management and change the password
for the LiveCycle ES administrator account.
Before you access LiveCycle Administration Console, LiveCycle ES must be deployed and running on your
application server.
For information about using LiveCycle Administration Console, see Adobe Administration Console Help
(available by clicking the Help link in the upper-right corner of the Home page).
➤ To access LiveCycle Administration Console:
1. Open a web browser and enter this URL:
http://localhost:[port]/adminui (local deployment using the default port)
2. Log in using the default user name and password:
User name: administrator
Password: password
49
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Initial Administration Tasks
Viewing the log files
50
3. Click Login.
4. Click Services to access the services’ pages, and click Settings to access the User Management and
Trust Store Management pages.
Viewing the log files
Events, such as run-time or startup errors, are recorded to the application server log files. If you have
problems deploying to the application server, you can use the log files to help you find the problem.
The JBoss Application Server log files are in the [LiveCycleES root]/jboss/server/all/log directory.
The LiveCycle Configuration Manager log files are in the [LiveCycleES root]/configurationManager/log
directory.
You can open the log files by using any text editor.
Change default password
Flash Media Rights Management Server creates one or more default users during the installation. The
password for these users is in the product documentation and is publicly available. You must change this
default password, depending on your security requirements.
The Flash Media Rights Management Server administrator user password is set to “password” by default.
You must change it in LiveCycle Administration Console.
➤ To change the administrator user password:
1. Type the following URL in a web browser:
http://[host name]:[port]/adminui
The default port number for JBoss Application Server is 8080.
2. Log in and click Settings > User Management > Users and Groups.
3. Click Find to return all default users and select Super Administrator.
4. On the Edit User: Super Administrator page, scroll to the bottom of the page and click Change
Password.
5. Enter and confirm your new password and then click Save Password.
6. Click Close.
Set the correct date, time, and time zone
Setting the correct date, time, and time zone on the server ensures that time-dependent policies will
function correctly.
6
Post-Deployment Tasks
This chapter describes how to verify the deployment by accessing LiveCycle Administration Console and
checking the application server log files. It also describes how to get started using LiveCycle ES solution
components and services after they are installed, configured, and deployed to your application server:
●
“Configuring SSL for JBoss Application Server” on page 51
●
“Configuring the settings” on page 54
●
“Configuring the credentials” on page 56
●
“External authenticators and authorizers” on page 56
●
“Flash Media Rights Management Server tools” on page 56
●
“Uninstalling Flash Media Rights Management Server” on page 57
●
“Uninstalling LiveCycle ES” on page 57
Configuring SSL for JBoss Application Server
Flash Media Rights Management Server requires the application server to be configured to use Secure
Sockets Layer (SSL). To configure SSL on JBoss Application Server, you need an SSL credential for
authentication. You can use the Java keytool to create a credential, or request and import a credential from
a certificate authority (CA). You must then enable SSL on JBoss.
Creating an SSL Credential
You can run keytool by using a single command that includes all of the information needed to create the
keystore.
➤ To create an SSL credential:
1. In a command prompt, navigate to [JAVA HOME]/bin and type the following command to create the
credential and keystore:
keytool -genkey -dname "CN=Host Name, OU=Group Name, O=Company Name,
L=City Name, S=State, C=Country Code" -alias "LC Cert"
-keypass key_password -keystore keystorename.keystore
Note: You must replace [JAVA_HOME] with the directory where the JDK is installed, and replace the
text in bold with values that correspond with your environment. The Host Name should be the
fully qualified domain name of the application server.
2. Enter the key_password when prompted for a password. Re-enter the same password when prompted.
3. Copy the keystorename.keystore to the [appserver root] conf directory by typing the following
command:
(Windows) copy keystorename.keystore [appserver root]\server\all\conf
51
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Post-Deployment Tasks
Creating an SSL Credential
52
4. Export the certificate file by typing the following command:
keytool -export -alias "LC Cert" -file LC_cert.cer -keystore
[appserver root]\server\all\conf\keystorename.keystore
5. Enter the key_password that you entered in step 2 when prompted for a password.
6. Copy the LC_cert.cer file to the [appserver root] conf directory by typing the following command:
●
(Windows) copy LC_cert.cer [appserver root]\server\all\conf
●
(Linux) cp LC_cert.cer [appserver root]/server/all/conf
7. View the contents of the certificate by typing the following command:
keytool -printcert -v -file [appserver root]\server\all\conf\LC_cert.cer
8. To provide write access to the cacerts file in [JAVA_HOME]\jre\lib\security, if required, right-click the
cacerts file and select Properties, and then deselect the Read-only attribute.
9. Import the certificate by typing the following command:
keytool -import -file LC_cert.cer -keystore
[JAVA_HOME]\jre\lib\security\cacerts
10. Type changeit as the password. This is the default password for a Java installation and may have been
changed by the system administrator.
11. When prompted for Trust this certificate? [no]:, type yes. The confirmation “Certificate
was added to keystore” is displayed.
12. In a text editor, open the server.xml file from the [appserver root]/server/all/deploy/
jbossweb-tomcat55.sar directory, and then uncomment the following section:
<!-- SSL/TLS Connector configuration using the SSL domain keystore
<Connector port="8443" address="${jboss.bind.address}"
maxThreads="100" minSpareThreads="5" maxSpareThreads="15"
scheme="https" secure="true" clientAuth="false"
keystoreFile="${jboss.server.home.dir}/conf/keystorename.keystore"
keystorePass="key_password" sslProtocol = "TLS" URIEncoding="UTF-8"/>
-->
13. Change the value for the keystoreFile attribute and the keystorePass attribute to the keystore
password that you specified when you created the keystore (shown in the example above).
14. Save the server.xml file.
15. Restart the application server:
●
Select Start > Control Panel > Administrative Tools, and then click Services.
●
Select JBoss for Adobe LiveCycle v8.0.
●
Select Action > Stop.
●
Wait for the status of the service to appear as stopped.
●
Select Action > Start.
16. To access LiveCycle Administration Console using SSL, type the following URL in a web browser:
https://[host name]:[port]/adminui
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Post-Deployment Tasks
Creating an SSL Credential
53
17. The default SSL port for JBoss is 8443. From this point on, you need to specify this port when accessing
LiveCycle ES.
➤ To request a credential from a CA:
1. In a command prompt, navigate to [JAVA HOME]/bin and type the following command to generate a
certificate request to send to the certificate authority:
keytool -certreq -alias "LC Cert" -keystore keystorename.keystore -file
LCcertRequest.csr
Note: You must replace [JAVA_HOME] with the directory where the JDK is installed, and replace the
text in bold with values that correspond with your environment.
2. After your request for a certificate file is fulfilled, complete the next section.
➤ To use a credential obtained from a CA:
1. In a command prompt, navigate to [JAVA HOME]/bin and type the following command to import the
credential into the keystore:
keytool -import -file CACertificateName.cer
-keystore keystorename.keystore
Note: You must replace [JAVA_HOME] with the directory where the JDK is installed, and replace the
text in bold with values that correspond with your environment.
Note: The imported CA signed certificate replaces a self-signed public certificate if it exists.
2. Copy the keystorename.keystore to the [appserver root] conf directory by typing the following
command:
(Windows) copy keystorename.keystore [appserver root]\server\all\conf
3. Export the certificate file by typing the following command:
keytool -export -alias "LC Cert" -file CACertificateName.cer
-keystore [appserver root]\server\all\conf\keystorename.keystore
4. Copy the CACertificateName.cer file to the [appserver root] conf directory by typing the following
command:
(Windows) copy CACertificateName.cer [appserver root]\server\all\conf
5. View the contents of the certificate by typing the following command:
keytool -printcert -v
-file [appserver root]\server\all\conf\CACertificateName.cer
6. To provide write access to the cacerts file in [JAVA_HOME]\jre\lib\security, if required, perform the
following task:
(Windows) Right-click the cacerts file and select Properties, and then deselect the Read-only
attribute.
7. Import the certificate by typing the following command:
keytool -import -file CACertificateName.cer
-keystore [JAVA_HOME]\jre\lib\security\cacerts
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Post-Deployment Tasks
Configuring SSL on Windows Vista
54
8. Type changeit as the password. This password is the default for a Java installation and may have been
changed by the system administrator.
9. When prompted for Trust this certificate? [no]:, type yes. The confirmation “Certificate
was added to keystore” is displayed.
10. Complete steps 12 to 17 of “To create an SSL certificate:” on page 54.
Configuring SSL on Windows Vista
To configure SSL on Windows Vista, you need an SSL certificate with RSA keys for authentication. You can
use the Java keytool to create the certificate.
Note: Windows Vista will not work with DSA keys.
You can run keytool by using a single command that includes all of the information needed to create the
certificate and keystore.
➤ To create an SSL certificate:
1. In a command prompt, navigate to [JAVA HOME]/bin and type the following command to create the
certificate and keystore:
keytool -genkey -keyalg RSA -dname "CN=Host Name, OU=Group Name,
O=Company Name, L=City Name, S=State, C=Country Code" -alias "LC Cert"
-keypass key_password -keystore keystorename.keystore
Note: You must replace [JAVA_HOME] with the directory where the JDK is installed, and replace the
text in bold with values that correspond with your environment.
2. Type changeit as the password. This password is the default for a Java installation and it may have
been changed by the system administrator.
Configuring the settings
This section describes the tasks that are required to configure the Flash Media Rights Management Server
settings.
Caution: Do not modify your Flash Media Rights Management Server in any manner other than the
configurations described in this section. Modifying your server environment can cause critical
issues.
●
Configure the server settings to set the base URL and other general settings.
●
Modify the config.xml file to enable web service, customize user prompts, and add support for private
keys.
●
Create the Packager User to be used by the Flash Media Rights Management Server command line
tools.
Tip: The successful creation of a new user will confirm that your LiveCycle ES server is properly configured
and communicating with your application and database servers.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Post-Deployment Tasks
Configuring the settings
55
➤ To configure the server settings:
1. In LiveCycle Administration Console, click Services > LiveCycle Rights Management ES >
Configuration > Server Configuration.
2. Configure the server settings as required, and then click OK to return to the Configuration page.
Note: The Base URL setting must be configured as a secure connection (that is, https), contain either
the full server name or the IP address (localhost is not acceptable in this instance), and have
the port number specified while configuring SSL for your application server (for example,
https://[RightsManagementServer].corp.[MyOrganization].com:8443)
The next task is to modify the config.xml file.
➤ To modify the config.xml file:
1. On the Configuration page, click Manual Configuration.
2. Click Export to get the existing configuration file and save the config.xml file to another location.
3. In a text editor, open the config.xml file and make the following changes:
●
Locate the property "WebServiceEnabled" and change the value to “true”.
●
Locate the property "CustomHeadingPrompt" and change the value to an appropriate display
message for your end users when they access Adobe Media Player.
The next part of the task is to add the configuration that allows for signing LiveCycle ES vouchers for
your Flash Media Rights Management Server.
4. With the config.xml file still open, navigate to the config directory, either on the DVD or in the
[FMRMS root] directory, and locate the DRM_Section.xml file.
5. In a text editor, open DRM_Section.xml, copy the contents and paste them into the open config.xml file
within the PolicyServer node, immediately after these lines:
<node name="Policy Server">
<map/>
Note: This node may not appear in the same location if you export the config.xml file again because
LiveCycle ES may reorder the nodes.
6. Save and close the config.xml file.
7. On the Manual Configuration page in LiveCycle Administration Console, browse to the config.xml file
you just modified and click Import to import it.
8. Click OK to exit the page.
The next task is to create and configure the Packager User in User Management. This user will be the
authorized user for the Flash Media Rights Management Server packaging tools.
➤ To create the Packager User:
1. In LiveCycle Administration Console, click > Settings > User Management > Users and Groups, and
then click New User.
2. Enter all required information (marked with an *) and click Next.
3. On the Add User to Groups page, click Next. A user group is not required.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Post-Deployment Tasks
Configuring the credentials
56
4. On the Assign Roles to User page, click Find Roles.
5. From the roles list, select the following roles to assign, and then click OK.
●
Application Administrator
●
Services User
Caution: Do not select Super Administrator for this user as it deactivates critical permissions.
6. Click Finish to save the new user.
Configuring the credentials
This section describes the steps that are required to import and configure the
Flash Media Rights Management Server certificate (PFX) file that you obtained from Adobe.
➤ To import the certificate:
1. In LiveCycle Administration Console, click > Settings > Trust Store Management > Local Credentials.
2. Click Import and, under Trust Store Type, select Document Signing Credential.
Note: For information about obtaining a credential, contact your Adobe representative.
3. In the Alias box, type the identifier for the credential. This identifier is used as the display name for the
credential in Flash Media Rights Management Server. This alias is also used to access the credential
programmatically by using the LiveCycle ES SDK.
Note: The alias name must be the same as the SignatureCredential value in the config.xml file. By
default, it is called FLV HEADER AND VOUCHER SIGNING. The alias name is automatically
converted to uppercase for display purposes but is not case-sensitive when you refer to it in a
process.
4. Click Browse to locate the credential, type the password of the credential, and then click OK.
External authenticators and authorizers
Before you can prepare your media content for publication, you must install an external authorization
handler that will provide centralized access control for FLV files in your organization.
Flash Media Rights Management Server controls access to policy-protected FLV files by evaluating the
policy when a user attempts to access a policy-protected file.
For evaluation purposes, you can choose to use the sample authorizer (in [FMRMS root]/SDK/samples), or
you can develop your own application by reviewing Developing Service Providers.
Flash Media Rights Management Server tools
Flash Media Rights Management Server installs with a suite of tools that are used to prepare the media
content for viewing in Adobe Media Player.
Before you can test protected content in Adobe Media Player, you must create a policy, and package and
sign the content. (See Securing Video Content and Playlists.)
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Post-Deployment Tasks
Uninstalling Flash Media Rights Management Server
57
Uninstalling Flash Media Rights Management Server
This section describes how to uninstall Flash Media Rights Management Server from your application
server.
Note: The uninstaller does not remove any of the LiveCycle ES solution components. Follow the
instructions in “Uninstalling LiveCycle ES” on page 57 to completely remove the
Flash Media Rights Management Server environment.
➤ To uninstall Flash Media Rights Management Server:
1. In the C:\Adobe\FMRMS1.0\_uninst directory, either double-click uninstaller.exe or select Start >
Settings > Control Panel > Add or Remove Programs.
2. When prompted, select the language for the installation to use, and then click OK.
3. On the Welcome screen, click Next.
4. Select the Flash Media Rights Management Server features to uninstall and click Next.
5. Read the summary and click Uninstall.
6. Click Finish.
Uninstalling LiveCycle ES
The uninstall program in the [LiveCycleES root] directory does not remove any files that you deployed to
your application server.
Caution: By running the uninstall program, all of the contents within the product installation directory are
subject to removal without further warning. Before proceeding, back up any data that you do
not want to lose.
➤ To remove the files from your computer:
1. Invoke the uninstall program:
●
(Windows) Use Add or Remove Programs in the Windows Control Panel to remove Adobe
LiveCycle ES.
●
(Linux) From a terminal, type ./livecycle8_uninstall.bin (you may need to make this
binary an executable file).
2. Follow the on-screen instructions in the uninstall program, and then click Finish.
7
Troubleshooting
This section discusses possible issues you may encounter when you install and deploy
Flash Media Rights Management Server, and suggests steps for avoiding or working around them.
Getting help
This section describes the steps you should take before you contact Adobe Support. If, after reviewing the
Flash Media Rights Management Server documentation, you have not resolved your issues, contact Adobe
Support. To help expedite your service, have the following information available:
●
What were you doing when the problem occurred?
●
Can you repeat the problem?
●
Was an error message displayed when the problem occurred? Did you observe anything else?
●
If you disable the Show Friendly HTTP Error Messages option in Internet Explorer (Tools > Options >
Advanced), do the errors persist?
Installation considerations
If you are having problems installing, configuring, or deploying Flash Media Rights Management Server,
ensure that you have carefully followed the instructions in this document or refer to the chapters:
●
“System prerequisites” on page 7
●
“Configuring a JBoss Application Server” on page 19
●
“Installing, Configuring, and Deploying” on page 41
●
“Initial Administration Tasks” on page 49
●
“Post-Deployment Tasks” on page 51
If you installed and configured everything according to the documentation, review the following sections
for issues that are similar to those you are experiencing.
Application server considerations
Check the following application server settings before you contact Adobe Support:
●
Total transaction lifetime timeout: 300
●
Initial heap size: 256
●
Maximum heap size: 1024 Mb
●
Prepared statement cache: 100
●
Database connection pool maximum: IDP_DS is 100 and RM_DS is 30
●
Topics and queues connection factories
58
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Troubleshooting
Database initialization considerations
59
Database initialization considerations
If you are having problems initializing Flash Media Rights Management Server, consider the following
possibilities:
●
Database instances must contain only alphanumeric characters in their names.
●
(Linux) Database instances must not exceed the platform-specific threshold of eight characters.
If the initialization fails at the beginning of the process, check for the following conditions:
●
(Non-turnkey installation) The LiveCycle ES database has already been created and the user has full
rights to it.
●
The database server is accessible when you ping it.
●
The database is empty; that is, it has no tables, sequences, views, or index tables.
●
The JNDI name for IDP_DS is created.
If initialization fails while writing to the registry, check the application server logs for errors that pertain to
the queues and topics. If errors exist, verify that the queues and topics are configured properly.
Troubleshooting with LiveCycle Configuration Manager log files
By default, the LiveCycle Configuration Manager log file is in [LiveCycleES root]\ConfigurationManager\log
and is named lcm.0.log (or similar). The log files are useful for LiveCycle Configuration Manager failure
analysis and may be required when dealing with Adobe Enterprise Support.
Scheduler service configuration for nondefault JNDI URLs
To function correctly, the Scheduler service may require some additional configuration.
This is the JNDI URL for the IDP_DS that your application server manages if the JNDI URL differs from the
default JNDI URL for the application server (that is, for JBoss: jnp://localhost:1099):
org.quartz.dataSource.idp.java.naming.provider.url
Complete these tasks to set the scheduler properties:
1. Create a new file called dscscheduler.properties.
2. Set the values of the above properties as necessary for the app server node, as shown in this example:
org.quartz.dataSource.idp.java.naming.provider.url =
jnp://localhost:1099/
org.quartz.jobstore.isClustered = true
org.quartz.scheduler.instanceId = AUTO
3. Add the JVM argument -Dadobe.idp.scheduler.properties=[Path to this
file]/dscscheduler.properties to the application server startup scripts/configuration.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Troubleshooting
Error messages
60
Error messages
This section contains a list of error messages that are specific to Flash Media Rights Management Server
and their definitions.
Class not found
If you encounter this error, check for the following issues:
●
Is the class path setting invalid or missing?
●
Is the JAR file obsolete?
●
Is there a compilation problem in the class?
JNDI name not found
If you encounter this error, check the following issues:
●
If the symptom is an exception stack trace showing the following line, check that the expected name is
spelled correctly:
javax.naming.NameNotFoundException: jdbc/<badName>
If it is not spelled correctly, you must fix the code.
To correct the most common JNDI exceptions, complete these steps:
1. Check the JNDI tree on the Flash Media Rights Management Server application server. Does the name
used appear in the tree?
●
If yes, it is most likely that your code did not properly set up the InitialContext object being
used for the look-up, and the look-up is being done on a JNDI tree that is not the one that the
resource is listed in.
●
If no, continue to step 2.
2. Does the resource appear in the JNDI tree under a name other than the name listed in the look-up?
●
If yes, you are using the incorrect look-up name. Provide the correct name.
●
If no, continue to step 3.
3. Review the application server logs during startup. If the application server is configured to make this
resource available but something is going wrong, an exception will be shown here. Is there an
exception?
●
If yes, review the exception and stack trace. If the NameNotFoundException is a symptom of
another problem based on your investigation of the server logs, move on to the troubleshooting
steps for that problem.
●
If no, continue to step 4.
4. If the resource is not listed in the JNDI tree, and there is no exception at startup to explain why it is not
available, the most probable issue is that the application server is not configured properly to make that
resource available. Contact Adobe Support.
Adobe Flash Media Rights Management Server
Installing and Deploying Flash Media Rights Management Server for JBoss
Troubleshooting
Exceptions thrown when initializing the LiveCycle ES database
Exceptions thrown when initializing the LiveCycle ES database multiple
times
When you initialize the LiveCycle ES database after it has been already initialized, exceptions may be
thrown, indicating that the POF schema has been initialized.
This error can be safely ignored.
Failure to deploy EARs
Depending on the LiveCycle ES services you are installing and your system configuration, you may receive
errors when deploying the EARs. If this occurs you should increase the MaxPermSize on your application
server from 256 to 512.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement