5.1 Configuration options

When using a JBoss Application Server, you have three installation options:

This section covers the use of the Adobe preconfigured JBoss Application Server when you are not using the turnkey installation option. You need to use the non-turnkey method for any of the following scenarios:

  • You are using a Linux or Solaris operating systems.

  • You are using Oracle or SQL Server, or if you don’t want to use the MySQL that install by default in a turnkey setup.

  • You need advanced control of the JBoss configurations.

LiveCycle runs on JBoss on Windows Server 2008 R1 and R2 (Enterprise Edition or Standard Edition), Red Hat Enterprise Linux 5.5, Red Hat Enterprise Linux Advanced Platform 5.5, Solaris 10, and SUSE Enterprise Linux 11 platforms.

Note: If you are planning to use the LiveCycle turnkey installation for JBoss, you do not need to review this document. All the instructions required for preparing your environment for a turnkey installation are available in Installing and Deploying for JBoss Using Turnkey.

5.1.1 Notes about configuring JBoss

The JBoss Application Server is configured using various XML configuration files. JBoss must be shut down before editing any of these configuration files. If JBoss is running and these files are changed, JBoss will likely crash. On Linux or Solaris, JBoss also has several .property configuration files that must be UNIX text files. It is important to take care if they are edited on Windows environments at any time.

5.1.2 Adobe-preconfigured JBoss

The Adobe-preconfigured JBoss software is delivered as part of the LiveCycle media. This is the simplest option for installing JBoss because advanced knowledge of JBoss is not required.

If you intend to download a supported version of JBoss from the internet, you must follow the configuration steps in 9 Appendix - Manually Configuring JBoss.

Adobe downloads EAP 5.1 archive from the Red Hat website and configures it with the options required to run LiveCycle in a stand-alone configuration. You can review these configurations in the next section.

Note: JBoss 5.1 deployment creates distinct directories for the data sources for each database type under the [appserver root]/server/ folder. Each database is prefixed with “lc_”. Thus, data source files for MySQL, Oracle, and MS SQL databases are placed in lc_mysql, lc_oracle, and lc_sqlserver directories, respectively. In the following sections, lc_<db-name> is used to designate these distinct directories.

If you download the Electronic Software Distribution (ESD) from the Adobe web site, extract the lces_server_10_0_2_jboss_all_win.zip (Windows) or lces_server_10_0_2_jboss_all_unix.tar.gz (Linux or Solaris) file to your file system. After the main archive file is extracted, extract the following directories: merge-modules, server, and third_party.

Note: Be sure to keep the directory hierarchy unchanged from the original ESD file.

The preconfigured JBoss software is located on the installation media or electronic software distribution (ESD) in the /third_party directory. The jboss.zip file contains the Adobe pre-configured JBoss 5.1.

Depending on your installation requirements, copy the JBoss directories and their contents to the location where you intend to install JBoss. The JBoss installation has all the configuration steps completed except for the steps detailed in 5.4 Database connectivity for Adobe pre-configured JBoss 5.1, which you must complete if you plan to use MySQL. If you do not intend to use a MySQL database, you must complete the appropriate configuration steps for your database detailed later in this chapter.

Note: The preconfigured JBoss includes a number of JSafe JAR files, which provide cryptography and Public Key Infrastructure (PKI) related FIPS-certified implementations in LiveCycle. When you install the product files, these files are deployed in the [appserver root]/server/lc_<db-name>/lib directory. Depending on the class loading, these JSafe JARs are used, even if your applications have their own version of JSafe JAR files.

// Ethnio survey code removed