3 Pre-Installation Tasks

Introduction

The instructions in this guide show you how to install Connect’s supporting software, which must be completed before you install Connect.

Pre-installation Software Requirements

Make sure that the appropriate versions of the operating system software and supporting software are installed. The following list provides information about the required operating system software and supporting software for your platform. Where applicable, software download information is provided.

Note: Connect is certified to run with only the version numbers provided. Uninstall other versions before installing certified versions of any of the supporting software.

If the Connect Tracker will be installed on more than node, a software or hardware-based HTTP load balancing solution will be required to distribute incoming traffic to the Tracker nodes.

Operating System Software

Connect 10R4 is certified to run under Sun Solaris 10 on SPARC hardware, IBM AIX 6.1 on pSeries hardware, and 64-bit Linux on x86 hardware. Connect may be run on virtual machines based on Solaris Zones, AIX WPARs/LPARs, or VMWare.

The following Linux distributions are supported:
  • RedHat Enterprise Linux 5/6 and compatible distributions
  • SUSE Linux Enterprise 11 and compatible distributions
Note that both 32-bit and 64-bit Linux distributions are supported.

Supporting Software

UNIX systems generally do not require additional software to be installed in order to run Connect. Depending on deployment configuration, however, the following additional infrastructure may be required:
  • External mail servers (message transfer agents or MTAs) may be required to serve as outbound mail farms or as inbound mail proxies.
  • A software or hardware-based HTTP load balancing solution may be required to distribute incoming traffic to the Tracker nodes if the Connect Tracker will be installed on more than node.

Database Configuration

In general, an empty database must be configured before installing Connect.
  • If installing on Oracle, you must create an Oracle schema user, and tablespaces for storing the Connect schema.
  • If installing on Microsoft SQL Server, you must create a new database, a login with the database owner role for the database, and file groups for storing the Connect schema.
  • If installing on MySQL, you must create a new database, and one or more logins so that Connect can access the MySQL database from every inside node.

Configuring Oracle

The Oracle database used for Connect should have its character set configured to UTF8. Make sure that the NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET parameters are both set to UTF8. If the UTF8 character set is not used, Connect may not be able to store content from all languages properly.

Installing Oracle Tablespaces

Before the Connect schema objects can be created, the Connect tablespaces must exist. Connect does not create these tablespaces automatically; they must be created by the Database Administrator at the customer site.

The Connect software distribution contains sample scripts that can be edited and run to create these tablespaces. The sample scripts are found in:

$KCHOME/kc/initdb/oracle/setup/tablespaces_11g.sql
$KCHOME/kc/initdb/oracle/setup/tablespaces_ETL_11g.sql

These sample scripts should be used for Oracle 10G and later. They use locally managed, unlimited tablespaces. Note that Oracle tablespace creation scripts provided with the software distribution are just guidelines. You will need to refine the scripts for your physical database layout. Also, please refer to the Connect Database Administration Guide for additional information on sizing tablespaces for schema growth.

Creating Oracle User

Log in as the system user and create a new Oracle user for the Connect application:

create user connect10 identified by PASSWORD;
grant alter session to connect10;
grant create procedure to connect10;
grant create sequence to connect10;
grant create session to connect10;
grant create table to connect10;
grant create trigger to connect10;
grant create view to connect10;

The following permissions are required by the ETL2 loader package and must be granted by an Oracle SYSDBA:

grant select on v_$session to connect10;
grant execute on dbms_lock to connect10;
In addition, the following statement should be executed for each tablespace: 
alter user connect10 quota unlimited on <tablespace_name>;
For example: 
alter user connect10 quota unlimited on CRM_TABLES;
alter user connect10 quota unlimited on CRM_INDEX;
alter user connect10 quota unlimited on CUST_STATS_TABLES;
alter user connect10 quota unlimited on CUST_STATS_INDEX;
alter user connect10 quota unlimited on CUST_QUEUE_TABLES;
alter user connect10 quota unlimited on CUST_QUEUE_INDEX;
alter user connect10 quota unlimited on CUST_PREF_TABLES;
alter user connect10 quota unlimited on CUST_PREF_INDEX;
alter user connect10 quota unlimited on CUST_ATTRIB_TABLES;
alter user connect10 quota unlimited on CUST_ATTRIB_INDEX;
alter user connect10 quota unlimited on CUST_SUBSCRIPTION_TABLES;
alter user connect10 quota unlimited on CUST_SUBSCRIPTION_INDEX;
alter user connect10 quota unlimited on CUST_CONVERSION_TABLES;
alter user connect10 quota unlimited on CUST_CONVERSION_INDEX;
alter user connect10 quota unlimited on CRM_CUST_TABLES;
alter user connect10 quota unlimited on CRM_CUST_INDEX;
alter user connect10 quota unlimited on CRM_QUEUE_TABLES;
alter user connect10 quota unlimited on CRM_QUEUE_INDEX;
alter user connect10 quota unlimited on CRM_HISTORY_TABLES;
alter user connect10 quota unlimited on CRM_HISTORY_INDEX;
alter user connect10 quota unlimited on CRM_AGG_TABLES;
alter user connect10 quota unlimited on CRM_AGG_INDEX;
alter user connect10 quota unlimited on CRM_ETL_TABLES;
alter user connect10 quota unlimited on CRM_VC_TABLES;
alter user connect10 quota unlimited on CRM_VC_INDEXES;

Unpack the Connect Software Distribution

On UNIX, Connect is distributed in two files: the platform-independent Connect software and the platform-dependent Java Virtual Machine (JVM). Connect provides a separate JVM for each architecture:
  • java_sun.tar.gz for Solaris / SPARC
  • java_aix.tar.gz for AIX / pSeries
  • java_linux.tar.gz for 64bit Linux
  • java_linux32.tar.gz for 32bit Linux
  1. Typically, Connect will be deployed under a dedicated user account. In this document, we will assume the user name of this account is connect.
  2. On the Connect install node, create a directory for the Connect installation directory (e.g. /opt/connect.install C:\connect.install).

In the Connect installation directory, uncompress and unpack the platform-independent Connect software. This will create a kc directory. Then unpack the platform-dependent JMV. This will create a java directory. Inside the java directory, there will be a script named untar.jre.sh. Run this script on the install node to unpack the JVM so that it can be used by the Connect install utilities. The kc directory is the Connect home directory $KCHOME.