Note: The information contained in this document is
meant for users who are installing MySQL manually and not for a
turnkey installation. See Installing and Deploying LiveCycle for
JBoss Using Turnkey.
Use the MySQL tools to create a MySQL 5 database for use with
LiveCycle and a MySQL user account that the application server can
use to connect to the database. You also must modify the MySQL database
server configuration. For information about creating the database
and user account, see the MySQL documentation. LiveCycle supports
MySQL 5 with JBoss 5.1.
Note: MySQL does not support the use of special characters
or spaces in the user name or password. Ensure that your user name
and password adhere to this restriction. Also, to avoid Scheduler
errors, do not use a dash (-) in the MySQL database name.
Note: On AIX, Linux, or Solaris, you must set the
lower_case_table_names system variable to 1 to ensure that table
names are case-insensitive. On Windows systems, this parameter does
not have any effect. For more information about setting table names
for case-sensitivity, see http://dev.mysql.com/doc/refman/5.1/en/identifier-case-sensitivity.html.
Note: To set up a database schema and new users on
MySQL by using a graphical user interface (GUI), you must install
the MySQL Administrator tool. (See the MySQL user documentation.)
When installing the MySQL database, you must specify UTF-8 character
encoding in the Variables section of the MYSQL UI.
You need the following information when you configure the data
source on JBoss:
4.6.1 Limitation on document usage in processes for MySQL databases
The MySQL database limits the amount of data that can be
stored in a table row. Processes that involve multiple instances
of documents can require more storage space than the MySQL row size
limitation. Because LiveCycle stores data for a process instance
in a single table row, processes that involve large amounts of data
can exceed the MySQL limitation on row size, causing errors to occur.
If you run a process that involves many instances of documents
and errors occur in the database, you can redesign the process so
that the operations that handle documents execute in several subprocesses.
For example, you can redesign your process so that its operations
are executed in two processes. The first process includes the first
half of the operations of the original process, and the second process
includes the last half of the operations. The first process must
include the invoke operation of the second process so that the second
process runs as a subprocess.
