Configuring the product
You can configure the product manually making sure to set your environment variables, your runtime properties, your database drivers, and the application server settings.
- Set your environment variables.
- Create the env_settings.ini file.
- Validate the environment.
- Configure the installation.
- Run the compatibility scripts.
- Configure the WebSphere® Application Server.
- Configure a cluster environment.
- Deploy the product in a cluster environment.
- Configure runtime properties.
- Run schema creation scripts.
- Configure GDS feature.
Set your environment variables
You must set up specific environment variables in order for IBM® InfoSphere® Master Data Management Collaboration Server - Collaborative Edition to run successfully.
env_settings.inifile by using any of the following methods:
- The deploy.properties.sample Java properties file,
- The <install dir>/bin/conf/env_settings.ini.default template,
- The <install dir>/bin/conf/deploy.samples sample file.
- Set and export the following environment variables in to the
.bashrcfile of the InfoSphere Master Data Management Collaboration Server - Collaborative Edition user.
PERL5LIB = <install dir>/bin/perllib
LANG=<locale value>, for example en_USNote: Locale
Cshould not be set as a default since that can cause problems when you use Perl.
- Logout and login as the InfoSphere
Master Data Management Collaboration Server - Collaborative Edition user to
pick up the changes to
Create the env_settings.ini file
For more information, see Creating the env_settings.ini file.
Validate the environment
- Go to the
- Run the
- Check if the database client is configured.
- Validate the Perl installation and notify if any Perl modules are missing.
Configuring the installation
Before you can configure the WebSphere Application Server, you need to configure the installation.The configureEnv.sh script:
- Validates the env_settings.ini file and notifies in case of any errors.
- Generates the configuration for IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition services.
- Generates a <install dir>/build/build.properties file for Apache Ant.
- Generates the common.properties file.Note:
- Comments inside the common.properties file are deleted after you run the configureEnv.sh script. If you want the descriptions for each property, refer the common.properties.default file.
- If the common.properties file exists, a warning message is reported and displays the missing properties, which exist in the common.properties.template file.
- If the common.properties file does not exist, you can either copy the properties from the common.properties.default file or delete the common.properties file and run the configureEnv.sh script to generate a new file.
You must run this script after a change is made to the env_settings.ini file or the addition of any JAR files to the jar directory in an enterprise installation.Procedure
- Go to the
- Run the
Running the compatibility scripts
Use the compatibility scripts to add some of the old environment variables that are used in previous versions of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition. The variables include $TOP, $CCD_DB, and $JAVA_RT.Procedure
- Add the following compatibility script lines to the .bashrc file:
Configure the WebSphere Application Server
For more information, see Configuring the WebSphere Application Server.
Configure a cluster environment
For more information, see Configure a cluster environment.
Deploy the product in a cluster environment
For more information, see Deploy the product in a cluster environment.
Configuring runtime properties
You must set a few runtime properties in the common.properties file as part of configuring IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition. For more information about these parameters, see the comments in the common.properties file.Procedure
- If you are using FTP, set the directory for using FTP for import operations by specifying the FTP_root_dir parameter.
- Set the temporary directory by specifying a value for the tmp_dir parameter. The directory /tmp is the default.
Run schema creation scripts
For more information, see Run schema creation scripts.
Configure GDS feature
For more information, see Configuring GDS feature.