The data for the IBM Connections applications falls into the following areas:
- Primary application data: This is held in dedicated databases on a DB2, SQL Server, or Oracle server
- Shared data: Supplemental application data such as attachments uploaded into applications that are located on a file system location accessible to every server
- Local data: Supplemental application data such as search indexes or application statistics that are located on a file system accessible to the application that owns the data
- Configuration information about the IBMConnections environment
Prior to installing the IBM Connections applications, you have to first create the databases for each application and the installer uses those databases to build the original environment. All databases must be hosted on the same enterprise database server and must be of the same type, either DB2, Oracle, or SQL Server.
The following databases are created for each application, we do not recommend attempting to use different database names than those suggested by the default install. The databases have self explanatory names with the exception of :
- OPNACT - used by Activities
- SNCOMM - used by Communities
Local and shared data
When building an IBM Connections server and before starting the installation, consideration should be given to the location of the shared data. The shared data includes all file uploads across all applications and the location must be accessible to all servers. Location and capacity of the shared data store must be planned for and, ideally, leave room for data growth over time.
To find where the applications are storing their data, you can use the Integrated Solutions Console (ISC) because the location of each application’s data appears as a WebSphere variable. Log into the ISC for the deployment manager and choose WebSphere variables from the menus.
There are many variables across all the applications that each have their own roles. However, you can filter the list down to those you are interested in. In the figure below, we have filtered by *CONTENT_DIR that shows us the defined content directories.
There are other variables that define data locations by application and you might want to review them all (by disabling the filter) if you are looking to document all possible locations.
The configuration information for the Connections environment falls into three areas:
- WebSphere configuration files:
These are both held centrally by the Deployment Manager and distributed out to each of the Network Deployed nodes. The originals, held by the Deployment Manager can be found in the config directory underneath the Deployment Manager’s profile, that is, /profiles/DMgr01/config
- IBM Connections specific application configuration files:
You can find these files in the IBM Connections installation directory. This directory can be identified by reviewing the WebSphere variables in the Integrated Solutions Console, that is, ./IBM/LotusConnections
- IBM HTTP Server plugins, keystores, and configuration.
You can find these files within the “config” and “plugins” directories underneath the HTTPServer install directory, that is, /IBM/HTTPServer/