Before you begin
Use this procedure if you do not want to use the database wizard to create your databases.
The SQL scripts are located in a compressed file called connections.sql.zip|tar
, located in the IBM_Connections_Install/IBMConnections/connections.sql
directory of the IBM
Connections set-up directory or installation media. Extract this file before proceeding. When extracted, the SQL scripts are located in the IBMConnections/connections.sql/application_subdirectory
directory of the IBM
Connections set-up directory or installation media, where application_subdirectory
is the directory that contains the SQL scripts for each application.
If you are using AIX
®, see the note in the Preparing the database wizard
topic about decompressing TAR files.
- If you are using Linux™ on IBM System z® with the DASD driver, the SQL scripts are located in the Lotus_Connections_Install_s390/LotusConnections/connections.s390.sql directory.
- If you are using Linux on IBM System z with the SCSI driver, back up the connections.s390.sql directory and rename the connections.sql directory to connections.s390.sql.
If the database server and IBM
Connections are installed on different systems, copy the SQL scripts to the system that hosts the database server.
only) Configure the AIX
system that hosts the DB2
databases to use the enhanced journaled file system (JFS2), which supports file sizes larger than 2 GB. To enable large files in the JFS system, complete the following steps:
- In the SMIT tool, select System Storage Management
File System>Add/Change/Show/Delete File Systems
- Select the file system type you want to use and specify other characteristics as wanted. If you use a Journaled File System, set the Large File Enabled setting to true.
See the AIX documentation
for more options.
When you are creating a database either with the database wizard or SQL scripts, you must log into the system where the database is hosted with the database administrator account. The default values for DB2 are db2admin on Microsoft™ Windows™, and db2inst1 on Linux and AIX. For Oracle, the default value on AIX and Linux is oracle, and system administrator on Windows. For SQL Server, the default value is the system administrator.
About this task
You must perform this task for each IBM
Connections application that you are installing.
To capture the output of each command to a log file, append the following parameter to each command: /file_path/db_application.log
is the full path to the log file and application
is the name of the log file. For example:
db2 -tvf createDb.sql /home/db2inst1/db_activities.log
Ensure that you have write permissions for the directories and log files.
To create the application databases, complete the following steps:
- Optional: (Only required if the database server and IBM Connections are installed on different systems.) Copy the IBM Connections SQL scripts to the DB2 database system. Authorize a user ID that can create the databases.
- Log in to the DB2 database system with the user ID of the owner of the database instance. The user ID must have privileges to create a database, a tablespace, tables, and indexes.
- If you created multiple database instances, specify the user ID for the first instance.
- The default administrative ID for Microsoft Windows is db2admin.
- Start the DB2 command line processor in command mode and enter the following command:
- For Home page and Profiles, change to the directory where the SQL scripts for each application are stored, and then enter the following command to run the script:
db2 -tvf createDb.sql
- For Home page, run the following script:
db2 -tvf initData.sql
- For Activities, Communities, Blogs, Bookmarks, Files, Forums, Mobile, and Wikis, change to the directory where the SQL scripts for each application are stored, and then enter the following command to run the script:
db2 -td@ -vf createDb.sql
Note: The SQL scripts for Bookmarks are stored in the dogear directory.
- Run the following command to grant access privileges to the lcuser account for the Home page and Profiles databases:
db2 -tvf <application_subdirectory>/appGrants.sql
- Run the following command to grant access privileges to the lcuser account for the Activities, Communities, Blogs, Bookmarks, Files, Forums, Mobile, and Wikis databases:
db2 -td@ -vf application_subdirectory/appGrants.sql
- Run the following commands to generate statistics for the Home page database:
db2 -tvf application_subdirectory/reorg.sql
db2 -tvf application_subdirectory/updateStats.sql
- Run the following commands to create Calendar tables in the Communities database:
db2 -td@ -vf communities/calendar-createDb.sql
db2 -td@ -vf communities/calendar-appGrants.sql
- If you plan to use the Metrics application, run the following commands to create the Metrics and Cognos® databases:
db2 -td@ -vf metrics/createDb.sql
db2 -td@ -vf metrics/appGrants.sql
db2 -td@ -vf cognos/createDb.sql
db2 -td@ -vf cognos/appGrants.sql
Note: The first two of these commands create the Metrics database and the following two commands create the Cognos database. The Cognos database tables are created when you start the Cognos BI Server for the first time.
- Close the DB2 command line processor.
- Optional: When you install IBM Connections, the JDBC configuration page of the installation wizard asks you to provide a user ID and password for the Application User. The user ID that you specify on that page must have read and write access to the database. You can provide the user ID of an administrative user or you can create a dedicated user ID with fewer privileges. See the Creating a dedicated DB2 user topic for more information.
What to do next
on System z
only.) To improve database performance, enable the NO FILE SYSTEM CACHING option. For more information, see the Enabling NO FILE SYSTEM CACHING for DB2 on System z
Parent topic: Creating databases with SQL scripts
Preparing the database wizard
Creating a dedicated DB2 user
Enabling NO FILE SYSTEM CACHING for DB2 on System z