LiveCycle Product Blog

"Bootstrapping" is the term commonly used for the creation of tables, indexes, views and sequences by LiveCycle in the database. For DB2, getting these to get created in the designated tablespace has been a struggle. This has mainly been because unlike WebSphere's JMS Message Store which asks the configurator for the name of the database schema to use, LiveCycle does not. As a result, tables, indexes, views and sequences all end up in the USERSPACE1 tablespace or the bootstrapping will fail.

Minimum required storage is 300 MB, 500 MB is better.

Here are steps you can take to ensure that LiveCycle bootstraps to the tablespace you want it to.

CREATE NEW BUFFERPOOL WITH 16 KB PAGESIZE
- Using the DB2 Control Center or the Command Line Processor (CLP), create a bufferpool (called LC_AIX for example) with a 16 KB pagesize. For a 300 MB bufferpool of 16 KB page size, you can create a size of 18,750 pages.

CREATE NEW SYSTEM TEMPORARY TABLESPACE WITH 16 KB PAGESIZE
- Create a "system temporary" tablespace called LC_SYSTEMP and configure it to use the newly created bufferpool

CREATE NEW REGULAR TABLESPACE WITH 16 KB PAGESIZE
- Create a new "regular" tablespace called LIVECYCLE, also configured it to use the newly created bufferpool. You could create another 16 KB bufferpool for this, it's up to you based on your corporate IT policy. Also, if possible, delete the USERSPACE1 tablespace that is created by default whenever a new database is created in DB2. It only has a 4 KB pagesize which is insufficient for LiveCycle.

CREATE NEW SCHEMA and DB USER
- Create a new schema called LC_USR. Depending on your IT policy, you would also have to create an OS user. For example, if DB2 is running on Windows, create a Windows user named LC_USR first and assign the user to the DB2USERS Windows user group. Then create the schema with this user. Creation of the schema will also create a DB2 DB user. If you used DB2 Control Center to do this, you wouldn't see the new user until you log out and then log back in!

GRANT ADDITIONAL AUTHORITIES TO DB USER
- Using DB2 Control Center or CLP, change the user LC_USR giving it two authorities, namely 'Connect to database' and 'Create tables'.

SET DEFAULT TABLESPACE FOR DB USER
- Also set this user's default tablespace as LIVECYCLE, with GRANT if your IT policy permits
- Make sure the schema is set as LC_USR

CONFIGURE WEBSPHERE
- If your appserver is WebSphere, make sure that the schema for the JMS message store is LC_USR
- Also for WebSphere, ensure that the J2C Authentication Alias for LiveCycle uses the same user credentials

START WEBSPHERE MESSAGING ENGINE
- Start the WebSphere appserver instance(s) hosting the JMS messaging engine(s).
- Check the tablespace, you should see eight tables with names starting with SIB... SIB is IBM's WebSphere Service Integration Bus.

START WEBSPHERE INSTANCE HOSTING LIVECYCLE, DEPLOY LIVECYCLE EARs
BOOTSTRAP LIVECYCLE
- Bootstrap LiveCycle using LiveCycle Configuration Manager (LCM).

VERIFY
- Check DB2. Tables, indexes, views and sequences belonging to LiveCycle (many but not all have names that start with EDC...) should now be created in the designated tablespace.
- Verify by logging in to the LiveCycle Admin Console and navigating to Home ->Services ->Archive Administration->Service Management. About 140 services should get listed, depending on the LiveCycle components you have licensed.

UPDATE DB STATS
- Run update statistics so that queries run faster - CLP command is REORGCHK UPDATE STATISTICS ON TABLE ALL

RUN CONFIGURATION ADVISOR
- Run DB2 Configuration Advisor on the database configuring it for "a mixed" workload, fewer than 10 (short transactions), faster transaction performance, 100 average number of connected remote applications, and "cursor stability" isolation level.