Overview

The following properties are associated in an LDAP directory that will be used as the source for the data. If you wish to use a source other than LDAP, see Manually populating the Profiles DB.

Directory variable	Description	Default installation root
app_server_root	IBM WAS installation directory	AIX: /usr/IBM/WebSphere/AppServer Linux: /opt/IBM/WebSphere/AppServer Windows: C:\IBM\WebSphere\AppServer
profile_root	WAS installation directory	AIX: /usr/IBM/WebSphere/AppServer/profiles/profile_name Linux: /opt/IBM/WebSphere/AppServer/profiles/profile_name Windows: C:\IBM\WebSphere\AppServer\profiles\profile_name
ibm_http_server_root	IBM HTTP Server installation directory	AIX: /usr/IBM/HTTPServer Linux: /opt/IBM/HTTPServer Windows: C:\IBM\HTTPServer
connections_root	IBM Connections installation directory	AIX or Linux: /opt/IBM/Connections Windows: C:\IBM\Connections
local_data_directory_root	Local content stores	AIX or Linux: /opt/IBM/Connections/data/local Windows: C:\IBM\Connections\data\local
shared_data_directory_root	Shared content stores	AIX or Linux: /opt/IBM/Connections/data/shared Windows: C:\IBM\Connections\data\shared\
IM_root	IBM Installation Manager installation directory	AIX: /opt/IBM/InstallationManager Linux: /var/IBM/InstallationManager Windows: C:\\IBM\Installation Manager
shared_resources_root	Shared resources directory	AIX or Linux: /opt/IBM/SSPShared Windows: C:\IBM\SSPShared
db2_root	DB2 DB installation directory	AIX or Linux: /usr/IBM/db2/version Linux: /opt/ibm/db2/version Windows: C:\IBM\SQLLIB\version
oracle_root	Oracle DB installation directory	AIX or Linux: /home/oracle/oracle/product/version/db_1 Windows: C:\oracle\product\version\db_1
sql_server_root	Microsoft SQL Server DB installation directory	Windows: C:\Microsoft SQL Server
Cognos_BI_install_path	IBM Cognos BI Server installation directory	AIX or Linux: /opt/IBM/Cognos64 Windows: C:\IBM\Cognos64 You specify the installation directory in the cognos-setup.properties file during installation.
Cognos_Transformer_install_path	Cognos Transformer installation directory	AIX or Linux: /opt/IBM/Cognos Windows: C:\IBM\Cognos You can specify the installation directory in the cognos-setup.properties file during installation.

LDAP data type	Example	Details
LDAP server type and version	Lotus Domino 8.5
Primary host	domino_ldap.example.com
Port	389
Bind distinguished name	cn=lcadmin,ou=People,dc=example,dc=com
Bind password
Certificate mapping
Certificate filter
Login attribute	mail or uid

WAS item	Example	Details
WAS version	V7.0 fix pack 21
Installation location	C:\IBM\WebSphere\AppServer
Update installer location	C:\IBM\WebSphere\UpdateInstaller
Administrator ID	wsadmin
Administrator password
WAS URL	http://was.example.com:9060/ibm/console
WAS secure URL	https://was.example.com:9043/ibm/console
WAS host
HTTP transport port
HTTPS transport port
SOAP connector port
Run application server as a service? (True/False)

Tivoli Directory Integrator item	Example	Details
Tivoli Directory Integrator installation location	C:\IBM\TDI\
Tivoli Directory Integrator version.	7.1 fix pack 2.
Solutions Directory path	C:\IBM\TDISOL\TDI

Profiles DB attribute	LDAP attribute (example)	Profiles DB column
alternateLastname	null	PROF_ALTERNATE_LAST_NAME
bldgId	null	PROF_BUILDING_IDENTIFIER
blogUrl	null	PROF_BLOG_URL
calendarUrl	null	PROF_CALENDAR_URL
countryCode	c	PROF_ISO_COUNTRY_CODE
courtesyTitle	null	PROF_COURTESY_TITLE
deptNumber	null	PROF_DEPARTMENT_NUMBER
description	description	PROF_DESCRIPTION
displayName	cn	PROF_DISPLAY_NAME
distinguishedName	$dn	PROF_SOURCE_UID
email	mail	PROF_MAIL
employeeNumber	employeenumber	PROF_EMPLOYEE_NUMBER
employeeTypeCode	employeetype	PROF_EMPLOYEE_TYPE
experience	null	PROF_EXPERIENCE
faxNumber	facsimiletelephonenumber	PROF_FAX_TELEPHONE_NUMBER
floor	null	PROF_FLOOR
freeBusyUrl	null	PROF_FREEBUSY_URL
givenName	givenName	PROF_GIVEN_NAME
givenNames	givenName
groupwareEmail	null	PROF_GROUPWARE_EMAIL
guid	(Javascript function: {func_map_from_GUID})	PROF_GUID
ipTelephoneNumber	null	PROF_IP_TELEPHONE_NUMBER
isManager	null	PROF_IS_MANAGER
jobResp	null	PROF_JOBRESPONSIBILITIES
loginId	employeenumber	PROF_LOGIN and PROF_LOGIN_LOWER
logins	mail	PROF_LOGIN
managerUid	$manager_uid This attribute represents a lookup of the UID of a manager using DN in the manager field.	PROF_MANAGER_UID
mobileNumber	mobile	PROF_MOBILE
nativeFirstName	null	PROF_NATIVE_FIRST_NAME
nativeLastName	null	PROF_NATIVE_LAST_NAME
officeName	physicaldeliveryofficename	PROF_PHYSICAL_DELIVERY_OFFICE
orgId	ou	PROF_ORGANIZATION_IDENTIFIER
pagerId	null	PROF_PAGER_ID
pagerNumber	null	PROF_PAGER
pagerServiceProvider	null	PROF_PAGER_SERVICE_PROVIDER
pagerType	null	PROF_PAGER_TYPE
preferredFirstName	null	PROF_PREFERRED_FIRST_NAME
preferredLanguage	preferredlanguage	PROF_PREFERRED_LANGUAGE
preferredLastName	null	PROF_PROF_PREFERRED_LAST_NAME
profileType	null	PROF_TYPE
secretaryUid	$secretaryUid This attribute represents a lookup of the UID of a secretary using DN in the secretary field.	PROF_SECRETARY_UID
shift	null	PROF_SHIFT
surname	sn	PROF_SURNAME
surnames	sn	PROF_SURNAME
telephoneNumber	telephonenumber	PROF_TELEPHONE_NUMBER
timezone	null	PROF_TIMEZONE
title	null	PROF_TITLE
uid	(Javascript function - {func_map_to_db_UID})	PROF_UID
workLocationCode	postallocation	PROF_WORK_LOCATION

IBM HTTP Server item	Example	Details
IBM HTTP Server installation location	C:\IBM\HTTPServer\
IBM HTTP Server version	V7.0 fix pack 21.
IBM HTTP Server httpd.conf file directory path	C:\IBM\HTTPServer\conf\
web server definition name	webserver1
web server plugin-cfg.xml file directory path	C:\IBM\HTTPServer\Plugins\config\webserver1\
IBM HTTP Server host
IBM HTTP Server fully qualified host
IBM HTTP Server IP address
IBM HTTP Server communication port	80
IBM HTTP Server administration port	8008
Run IBM HTTP Server as a service? (Y/N)
Run IBM HTTP administration as a service? (Y/N)
IBM HTTP Server administrator ID
IBM HTTP Server administrator password

Cognos BI Server and Transformer item	Details
Cognos BI Server and Transformer	Refer to the cognos-setup.properties file.

Option	Description
AIX	/usr/IBM/WebSphere/AppServer/profiles/<profile_name>/config/cells/<cell_name>/wim/config
Linux	/opt/IBM/WebSphere/AppServer/profiles/<profile_name>/config/cells/<cell_name>/wim/config
Microsoft Windows	C:\IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\wim\config

Property	Value	Description
dbtype	db2 \| oracle \| sqlserver	The DB system to use. Choose from IBM DB2, Oracle, or Microsoft SQL Server.
dbInstance	DB_instance_name	The instance name of the DB that you want to use. For example: DB2 (DB2 on Windows) db2inst1 (DB2 on AIX or Linux) orcl (Oracle) \\ (SQL Server) The first '\' is an escape character.
dbHome	DB_location	File path to the DB. If you encounter an Invalid DB instance error, the file path to the DB might be incorrect. If the dbHome value is, for example, /home/oracle/oracle/product/10.2.0/db_1/, then you must remove the final / character. This limitation applies only on Oracle DBs. On Windows, you need to add an escape character '\'. For example, activities.filepath=C\:\\SQLSERVER.
action	create \| delete \| upgrade	The action performed by the wizard. The options are create, delete, or upgrade.
dbVersion	DB2: 9 \| Oracle: 10 or 11\| SQL Server 2005:9 SQL Server 2008: 10	The major version number of the DB type. For example, if you use SQL Server 2005, enter 9. If you use SQL Server 2008, enter 10.
applications	activities, blogs, cognos, communities, dogear, files, forum, homepage, metrics, mobile, profiles, wikis	IBM Connections applications for which the wizard creates DBs. Use a comma (,) character to separate multiple applications.

Property	Value	Description
<application>.password	Password for application DBs	Password for the applications. The passwords will be removed from the response file after the wizard has finished processing.
<application>.filepath	File path to the directory where DB files are stored	(SQL Server only) File path to the DB file location. On Windows, add an escape character '\'. For example, activities.filepath=C\:\\SQLSERVER.

Property	Recommended value	Description
port	DB2 default is 50000 Oracle default is 1521 SQL Server default is 1433	Database server port for starting JDBC
administrator	DB2 default on Windows is db2admin DB2 default on AIX and Linux is db2inst1 Oracle default is system SQL Server default is sa	Database administrator account for starting JDBC
adminPassword		Database administrator password for starting JDBC
storyLifetimeInDays		The Home page upgrade requires this parameter. It should be the same as the value in the news-config.xml file.
profiles.db.name profiles.db.hostname profiles.db.port profiles.db.admin profiles.db.adminPassword		The Home page migration process copies data from the Profiles DB. For this reason, you must update the Home page DB before updating the Profiles DB. The migration process supports the use of different instances to host the Home page and Profiles DBs.
jdbcLibPath		(SQL Server only) JDBC library path for starting JDBC. On Windows, add an escape character '\'. For example, jdbcLibPath=C\:\\sqljdbc4.jar

Directory type	Map file
IBM Lotus Domino	defaultMapping_domino.properties
IBM Tivoli Directory Server	defaultMapping_tivoli.properties
Microsoft Active Directory Application Mode	defaultMapping_adam.properties
Microsoft Windows Server 2003 Active Directory	defaultMapping_ad.properties
Novell Directory Services	defaultMapping_nds.properties
Sun ONE	defaultMapping_sun.properties

Parameter	Value	Description
responseFile (required)	full path to the tdisettings.properties response file	After running the population wizard successfully, the tdisettings.properties response file is stored in the Wizards\TDIPopulation directory in the IBM Connections set-up directory.
mappingFile (optional)	full path to the mappings.properties file	The mappings.properties file is stored in the Wizards\TDIPopulation directory in the IBM Connections set-up directory. If you do not use specify a different file with the -mappingFile parameter, the wizard uses this file to map properties to the LDAP directory.
dbPassword (optional)	Database password	Overwrites the DB password in the response file. If you do not specify the DB password here, you must specify it in the response file.
ldapPassword (optional)	LDAP password	Overwrites the LDAP password in the response file. If you do not specify the LDAP password here, you must specify it in the response file.
sslPassword (optional)	SSL key store password	Overwrites the SSL key store password in the response file. If you do not specify the SSL password here, you must specify it in the response file.

Property	Description	Value
db.hostname	Host name of the DB server.
db.jdbcdriver	Location of the JDBC driver.	Example: C\:\\IBM\\SQLLIB\\java The extra "\" symbol is an escape character.
db.name	Name of the Profiles DB.	Default: PEOPLEDB
db.password	Password for connecting to the DB. The property is required if you do not specify -dbPassword as a command parameter.	DB2 default: 50000 Oracle default: 1521 SQL Server default: 1433
db.port	Database server port for invoking JDBC.	DB2 default: 50000 Oracle default: 1521 SQL Server default: 1433
db.type	DB2, Oracle, or SQL Server.	db2 \| oracle \| sqlserver
db.user	Name of the DB user, such as lcuser.	Example: lcuser
ldap.dn.base	LDAP distinguished name search base.	Example: dc=example, dc=com
ldap.enable.ssl	Boolean value that determines if SSL is enabled. If the value of this property is yes, you must also provide values for the ssl.keystore, ssl.password, and ssl.type properties.	yes \| no
ldap.filter	Filter for the LDAP.	Example: (&(uid=*)(objectclass=inetOrgPerson))
ldap.hostname	Host name of the LDAP server.
ldap.password	Password for connecting to the LDAP directory.	Default: 389 or 663 (SSL)
ldap.port	Communications port of the LDAP server.	Default: 389 or 663 (SSL)
ldap.user	DN of the LDAP administrative user.
ssl.keyStore	File path to the keystore. Required only if the ldap.enable.ssl property is set to yes.
ssl.password	SSL password. Required only if the ldap.enable.ssl property is set to yes.
ssl.type	SSL standard. Required only if the ldap.enable.ssl property is set to yes.	JKS \| PKCS12
task.list	Tasks that the Profiles population wizard can perform. You can choose from the following options: LDAP_OPTIONAL_TASK_MARK_MANAGER, LDAP_OPTIONAL_TASK_FILL_COUNTRIES, LDAP_OPTIONAL_TASK_FILL_DEPARTMENT, LDAP_OPTIONAL_TASK_FILL_ORGANIZATION, LDAP_OPTIONAL_TASK_FILL_EMPLOYEE, and LDAP_OPTIONAL_TASK_FILL_WORK_LOCATION To execute multiple tasks, separate the tasks with the comma symbol.	Example: LDAP_OPTIONAL_TASK_MARK _MANAGER,LDAP_OPTIONAL _TASK_FILL_COUNTRIES
task.country.csv	File path to the isocc.csv file. Required if you specify LDAP_OPTIONAL_TASK_FILL_COUNTRIES in the task.list property.	Example: C\:\\build\\isocc.csv The extra "\" symbol is an escape character.
task.department.csv	File path to the deptinfo.csv file. Required if you specify LDAP_OPTIONAL_TASK_FILL_DEPARTMENT in the task.list property.	Example: C\:\\build\\deptinfo.csv The extra "\" symbol is an escape character.
task.empoyeetype.csv	File path to the emptype.csv file. Required if you specify LDAP_OPTIONAL_TASK_FILL_EMPLOYEE in the task.list property.	Example: C\:\\build\\emptype.csv The extra "\" symbol is an escape character.
task.organization.csv	File path to the orginfo.csv file. Required if you specify LDAP_OPTIONAL_TASK_FILL_ORGANIZATION in the task.list property.	Example: C\:\\build\\orginfo.csv The extra "\" symbol is an escape character.
task.worklocation.csv	File path to the workloc.csv file. Required if you specify LDAP_OPTIONAL_TASK_FILL_ORGANIZATION in the task.list property.	Example: C\:\\build\\workloc.csv The extra "\" symbol is an escape character.
TDI.dir	Installation location of Tivoli Directory Integrator.	Example: C\:\\IBM\\TDI\\V7.1 The extra "\" symbol is an escape character.

LDAP Properties

Property	TDI parameter	Definition
source_ldap_url	LDAP URL hostname and LDAP URL Port	Required. The LDAP web address used to access the source LDAP system. The port is required and is typically 389 for non-SSL connections. Express this value in the form of ldap://host:port. For example: ldap://myservername.com:389. If using the population wizard, this property is configured using the LDAP server name and LDAP server port on the LDAP server connection page. The LDAP query constructed from the source URL, search base, and search filter are stored in a source url property, which can be used to segment the Profiles DB user set during synchronization. Using different values for this property, which may be equivalent (for example referencing the LDAP server by IP address or DNS name) is not advised. The default value is ldap://localhost:389.
source_ldap_use_ssl	LDAP URL Use SSL connection	Required if you are using SSL to authenticate. Set to either true or false. Set to true if you are using SSL (for example if you are using port 636 in the LDAP URL). The default value is false. If using the population wizard, this property is configured with the Use SSL communication checkbox on the LDAP server connection page.
source_ldap_user_login	Login user name	Login user name used for authentication. You can leave this blank if no authentication is required. If using the population wizard, this property is configured in the Bind distinguished name (DN) field on the LDAP authentication properties page.
source_ldap_user_password	Login password	Login password used for authentication. Leave this blank if no authentication is required. The value will be encrypted in the file the next time it is loaded. If using the population wizard, this property is configured in the Bind password field on the LDAP authentication properties page.
source_ldap_search_base or source_ldap_user_search_base	Search Base	The search base (the location from where the search begins) of the iterating directory. The search begins at this point in the ldap directory structure and searches all records underneath. This should be a distinguished name. Most directories require a search base, and as such it must be a valid distinguished name. Some directory services allow you to specify a blank string which defaults to whatever the server is configured to do. A default value is not specified. If using the population wizard, this property is configured in the LDAP user search base field on the LDAP page.
source_ldap_search_filter or source_ldap_user_search_filter	Search Filter	Search filter used when iterating the directory. This determines which objects are included or excluded in the search. If using the search base and the specified search filter properties do not allow you to adequately construct your search set, use the source_ldap_required_dn_regex property. Search filters are used by those directories to select entries from which data is retrieved from a search operation. Care should be taken when specifying search filters as they can affect performance of the directory being searched. The directory server schema being queried can impact performance. A default value is not specified. If using the population wizard, this is the LDAP user search filter field on the LDAP authentication properties page.
source_ldap_sort_page_size	Page size	If specified, the LDAP Connector tries to use paged mode search. Paged mode causes the directory server to return a specific number of entries (called pages) instead of all entries in one chunk. Not all directory servers support this option. The default value is 0, which indicates that paged mode is disabled. The default value is 0. This parameter is not configurable when using the population wizard.

source_ldap_authentication_method	Authentication Method	Options include the following: Anonymous This method provides minimal security. Simple This method uses a login user name and password to authenticate. It is treated as anonymous if no user name and password are provided. CRAM-MD5 Challenge/Response Authentication Mechanism using Message Digest 5. This method provides reasonable security against various attacks, including replay. SASL Simple Authentication and Security Layer. This method adds authentication support to connection-based protocols. Specify parameters for this type of authentication using the Extra Provider Parameters option. This parameter is not configurable when using the population wizard.
source_ldap_collect_dns_file		Name of the file used to collect distinguished names (DNs) by the collect_dns.bat/sh process from the source, and then used during population by the populate_from_dn_file.bat/sh processes to look up entries to add to the DB repository. This file can also be constructed by hand to populate an explicit set of users. The default value is collect.dns. This parameter is not configurable when using the population wizard.
source_ldap_escape_dns		Indicates that special characters have not been escaped properly and identifies them so the processor can find those characters and escape them. Special characters are: , (comma) = (equals) + (plus) < (less than) > (greater than) # (number sign) ; (semicolon) \ (backslash) " (quotation mark) The backslash is used to escape special characters. A plus sign is represented by \+ and a backslash is represented by \\. if your distinguished names contains these special characters and you receive errors when running the collect_dns/populate_from_dn_file process, set this property to true so that the characters are escaped. The default value is false. This parameter is not configurable when using the population wizard.
source_ldap_required_dn_regex		Allows a regular expression to be used to limit the distinguished names (DNs) which are processed by providing a regular expression which must be matched. If the regular expression is not matched, that particular record is skipped. Although the search filter property gives some flexibility, in case this is not sufficient, you can use a more powerful regular expression. A default value is not specified. This parameter is not configurable when using the population wizard.
source_ldap_sort_attribute	Sort Attribute	Specifies server-side sorting. This parameter instructs the LDAP server to sort entries matching the search base on the specified field name. Server-side sorting is an LDAP extension. The iterating directory must be able to support this sorting extension. A default value is not specified. This parameter is not configurable when using the population wizard.
source_ldap_iterate_with_filter		This property should be used if the size of the data to be retrieved from LDAP exceeds the search limit from the LDAP. For example, if your search parameters would return 250K records but the LDAP only allows 100K to be returned at a time, this parameter must be used. If the data is too large, an LDAP size limit exceeded error message is generated. To configure this mechanism, see the Populating a large user set topic. When set to true, this specifies that the default iteration assembly line use the collect_ldap_dns_generator.js file to iterate over a set of LDAP search bases and filters. The cconfig setting replaces the sync_all_dns_forLarge and collect_dns_iterate scripts used in earlier releases. This parameter is not configurable when using the population wizard. The default value is false.
source_ldap_binary_attributes	Binary Attributes	By default, this property is set internally to GUID, objectGUID, objectSid, sourceObjectGUID. Any additional values specified in the property are appended to the list. This parameter is not configurable when using the population wizard. The default value is GUID.
source_ldap_time_limit_seconds	Time Limit	Specifies the maximum number of seconds that can be used when searching for entries; 0 = no limit. This parameter is not configurable when using the population wizard. The default value is 0.
source_ldap_map_functions_file		Specifies the location of any referenced function mappings. When using the population wizard, the functions shown in the mapping dialog are read from and written to this file. The default value is profiles_functions.js.
source_ldap_logfile		In addition to the standard logs/ibmdi.log file, output from the populate_from_dn_file.bat or populate_from_dn_file.sh task is written to this file. This parameter is not configurable when using the population wizard. The default value is logs/PopulateDBFromSource.log.
source_ldap_compute_function_for_givenName		Connections allows Javascript functions for setting values of common LDAP fields such as cn, sn, givenName to execute before Connections performs its mapping. For example, sn and/or givenName can be parsed from cn (common name). This parameter is not configurable when using the population wizard. A default value is not specified.
source_ldap_compute_function_for_sn		Connections allows Javascript functions for setting values of common LDAP fields such as cn, sn, givenName to execute before Connections performs its mapping. For example, sn and/or givenName can be parsed from cn (common name). This parameter is not configurable when using the population wizard. A default value is not specified.
source_ldap_collect_updates_file		This property is no longer used.
source_ldap_manager_lookup_field		This property is no longer used.
source_ldap_secretary_lookup_field		This property is no longer used.

Many properties in the TDI LDAP connector are not mapped to Profiles TDI properties. To configure properties other than those listed here, consider using an alternate source repository and creating your own specialized configuration. Use the LDAP iterator and connectors provided with the TDI solution directory as a starting point, see Using a custom source repository connector for more information.

The following properties must be set in the profiles_tdi.properties file, even if developing your own assembly lines using the connectors provided in the Profiles TDI solution directory. These properties are not configured in the Connector panels, but rather in the profiles_tdi.properties file.

Profiles Database Properties

Property	TDI parameter	Definition
dbrepos_jdbc_driver	JDBC Driver	Required. The JDBC driver implementation class name used to access the Profiles DB repository. For DB2, the default is com.ibm.db2.jcc.DB2Driver. For example: dbrepos_jdbc_driver=com.ibm.db2.jcc.DB2Driver For Oracle, the default is oracle.jdbc.driver.OracleDriver. For example: dbrepos_jdbc_driver=oracle.jdbc.driver.OracleDriver If you are using a Microsoft SQL Server DB, change the value to reference a SQL Server driver, for example: dbrepos_jdbc_driver=com.microsoft.sqlserver.jdbc.SQLServerDriver This corresponds to the JDBC driver path in the population wizard. If not using the wizard, this library must be present in the CLASSPATH of Tivoli Directory Integrator, or Tivoli Directory Integrator cannot load the library when initializing the Connector and cannot communicate with the Relational Database (RDBMS). To install a JDBC driver library so that Tivoli Directory Integrator can use it, copy it into the TDI_install_dir/jars directory, or a subdirectory such as TDI_install_dir/jars/local.
dbrepos_jdbc_url	JDBC URL	Required. JDBC web address used to access the Profiles DB repository. You must modify the hostname portion and port to reference your server information. You can find this information by accessing the WAS Administration Console (http://yourhost:9060), and then selecting Resources > JDBC > Data sources > profiles. The default syntax is for DB2, unless using the wizard, but the default uses a local host. If the DB2 is not on the same system as the TDI solution directory, update the URL with the host. If you are using an Oracle DB, use the following syntax: dbrepos_jdbc_url=jdbc:oracle:thin:@<host_name>:1521:orcl If you are using a SQL Server DB, use the following syntax: dbrepos_jdbc_url=jdbc:sqlserver://<host_name>:1433;DBName=PEOPLEDB
dbrepos_username	User name	Required. User name under which the DB tables, which are part of the Profiles DB repository, are accessed.
dbrepos_password	Password	Required. Password associated with the username under which the DB tables, which are part of the Profiles DB repository, are accessed.
dbrepos_mark_manger_if_referenced		This property is no longer used.

The following properties are associated with the task that monitors the Profiles employee draft table for changes and transmits them through a DSML v2 connector.

Change Monitoring Properties

Property	TDI parameter	Definition
monitor_changes_dsml_server_authentication		Type of authentication used by the DSML server update requests. Options include the following: HTTP basic authentication A method designed to allow a web browser, or other client program, to provide credentials, in the form of a user name and password, when making a request. Anonymous This method provides minimal security.
monitor_changes_dsml_server_url		Required if you are transmitting user changes back to the source repository. Web address of the DSML server to which the DSML update requests should be sent.
monitor_changes_dsml_server_username		Required if you are transmitting user changes back to the source repository. User name used for authentication to the DSML server.
monitor_changes_dsml_server_password		Required if you are transmitting user changes back to the source repository. Password used for authentication to DSML server that the DSML update requests should be sent to.
monitor_changes_map_functions_file		Path to the file containing mapping functions for mapping from a changed DB field to a source. for example LDAP field. This is only needed if changes made to the source based on DB repository field changes are not mapped one-to-one. You can use the same file you use to map from source to DB repository fields, assuming the functions are named appropriately.
monitor_changes_sleep_interval		Polling interval, in seconds, between checks for additional changes when no changes exist.

The following properties are associated with the Tivoli Directory Integrator processing that reads a Tivoli Directory Server change log and subsequently updates the DB repository with those changes.

Tivoli Directory Server Change Log Properties

Property	TDI parameter	Definition
ad_changelog_ldap_url		LDAP web address used to access the LDAP system that was updated. For example: ldap://host:port
ad_changelog_ldap_user_login		Login user name to use to authenticate with an LDAP system that has been updated. You can leave this blank if no authentication is needed.
ad_changelog_ldap_user_password		Login user name to use to authenticate with an LDAP that has been updated. You can leave this blank if no authentication is needed. The value will be encrypted in the file the next time it is loaded.
ad_changelog_ldap_search_base
ad_changelog_ldap_use_ssl		Defines whether or not to use SSL in authenticating with an LDAP system that was updated. The options are true and false.
ad_changelog_timeout
ad_changelog_sleep_interval		Polling interval, in seconds, between checks for additional changes when no changes exist.
ad_changelog_use_notifications		Indicates whether to use changelog notifications rather than polling. If true, the tds_changelog_sleep_interval is not applicable since polling is not used. The options are true and false.
ad_changelog_ldap_page_size
ad_changelog_start_at		Change number in the Active Directory changelog to start at. Typically this is an integer, while the special value EOD means start at the end of the changelog.
ad_changelog_ldap_required_dn_regex.
tds_changelog_ldap_authentication_method	Authentication Method	Authentication method used to connect to LDAP to read records. Options include the following: Anonymous This method provides minimal security. Simple This method uses a login user name and password to authenticate. It is treated as anonymous if no user name and password are provided. CRAM-MD5 Challenge/Response Authentication Mechanism using Message Digest 5. This method provides reasonable security against various attacks, including replay. SASL Simple Authentication and Security Layer. This method adds authentication support to connection-based protocols. Specify parameters for this type of authentication using the Extra Provider Parameters option.
tds_changelog_ldap_changelog_base	ChangelogBase	Changelog base to use when iterating through the changes. This is typically cn=changelog.
tds_changelog_ldap_time_limit_seconds	Time Limit	Search for entries must take no more than this number of seconds; 0 = no limit.
tds_changelog_ldap_url	LDAP URL	LDAP web address used to access the LDAP system that was updated. For example: ldap://host:port
tds_changelog_ldap_use_ssl	Use SSL	Defines whether or not to use SSL in authenticating with an LDAP system that was updated. The options are true and false.
tds_changelog_ldap_user_login	Login user name	Login user name to use to authenticate with an LDAP system that has been updated. You can leave this blank if no authentication is needed.
tds_changelog_ldap_user_password	Login password	Login user name to use to authenticate with an LDAP that has been updated. You can leave this blank if no authentication is needed. The value will be encrypted in the file the next time it is loaded.
tds_changelog_sleep_interval		Polling interval, in seconds, between checks for additional changes when no changes exist.
tds_changelog_start_at_changenumber		Change number in the Tivoli Directory Server changelog to start at. Typically this is an integer, while the special EOD value means start at the end of the changelog.
tds_changelog_use_notifications		Indicates whether to use changelog notifications rather than polling. If true, the tds_changelog_sleep_interval is not applicable since polling is not used. The options are true and false.

The following properties are available in the profiles_tdi.properties file and are associated with Tivoli Directory Integrator debug activities.

The debug properties enable TDI debugging for an entire assembly. In addition, enabling debug_update_profile which enables debugging for the commands that use the Profiles Connector, also enables Java debugging for the following packages.

Tivoli Directory Integrator Debug and Trace Properties

Property	TDI parameter	Definition
sync_all_dns		For information about sync_all_dns, see Understanding how the sync_all_dns process works.
debug_managers		Flag that instructs TDI to log additional debug information for the following command(s). The options are true and false. To enable, set as debug_managers=true. This property maps as follows: debug_managers mark_managers The default setting is false.
debug_photos		Flag that instructs TDI to log additional debug information for the following command(s). The options are true and false. This property maps as follows: debug_photos load_photos_from_files dump_photos_to_files The default setting is false.
debug_pronounce		Flag that instructs TDI to log additional debug information for the following command(s). The options are true and false. This property applies to the following command(s): debug_pronounce load_pronounce_from_files, dump_pronounce_to_files The default setting is false.
debug_fill_codes		Flag that instructs TDI to log additional debug information for the following command(s). The options are true and false. This property applies to the following command(s): debug_fill_codes fill_country fill_department fill_emp_type fill_organization fill_worklok The default setting is false.
debug_draft		Flag that instructs TDI to log additional debug information for the following command(s). The options are true and false. This property applies to the following command(s): debug_draft process_draft_updates reset_draft_iiterator_state set_draft_iterator_count The default setting is false.
debug_update_profile		Flag that instructs TDI to log additional debug information for the following command(s). The options are true and false. This property applies to the following command(s): debug_update_profile populate_from_dn_file delete_or_inactivate_employees populate_from_xml_file process_ad_changes process_tds_changes The default setting is false.
debug_collect		Flag that instructs TDI to log additional debug information for the following command(s). The options are true and false. This property applies to the following command(s): debug_collect collect_dns The default setting is false.
debug_special		Flag that instructs TDI to log additional debug information for the following command(s). The options are true and false. This property applies to the following command(s): debug_special unused at present The default setting is false.
trace_profile_tdi_javascript		Enables generation of an internal Javascript trace file. Options are OFF, FATAL, ERROR, WARN, INFO, DEBUG, TRACE, ALL ( values are not case-sensitive). The default setting is OFF.

Batch files for processing Profiles data

IBM Connections provides several batch files that automate the collection and processing of LDAP data for the Profiles DB.

Batch file functions

The name of each batch file ends with the .sh suffix for the IBM AIX and Linux operating systems and with the .bat suffix for the Microsoft Windows operating system.

The following list describes each batch file and its functions. You can search for more information about these files in the help topics.

Populate a large user set

In very large organizations, the number of users in the LDAP directory exceeds the capacity of the Tivoli Directory Integrator assembly lines for Profiles. To overcome this restriction, you can populate the DB by using manual TDI assembly lines. You cannot use the Profiles population wizard.

Limits with large user sets

The LDAP administrator can change the LDAP size limit. The capacity of the standard assembly lines provided with IBM Connections is 100,000 users. In some cases, you can modify the maximum number of entries returned from the LDAP or adjust the source_ldap_page_size parameter in the profiles_tdi.properties file.

For example, set the parameter to the maximum number of records the LDAP repository will return, using the following sample statement:

If neither of these alternatives is successful, use a special set of assembly lines to populate your Profiles DB from the LDAP directory.

Alternative population process

If you have a very large set of data, set the source_ldap_iterate_with_filter property in the profiles_tdi.properties file to true. This uses the collect_ldap_dns_generator.js file to retrieve search criteria for a batch of records. The batch is always smaller than the limit of the LDAP retrieval.

The collect_ldap_dns_generator.js file constructs a search filter with a portion of UIDs but does not modify the search base. It is data-specific so you need to modify it for your own deployment. Modify suppliesSearchBase() or suppliesSearchBase(), depending on which filter is used in the LDAP retrieval.

If one of the filters is changed to return true (in the supplied file, suppliesSearchBase returns true), the corresponding function, either getNextSearchBase() or getNextSearchFilter(), is called in iterations. Each time the function is called it returns a string with the next search base or filter to use. When it reaches the end of the batch, it returns null.

The process first uses some special characters and then examines the first two characters of the UID string, or example aa*, ab*, and so on. After it reaches zz* it returns null and the collect_dns assembly line stops processing. You can then run populate_from_dn_file.

Map fields manually

To populate the Profiles DB with data from the enterprise LDAP directory, map the content of the fields in the DB to the fields in the LDAP directory.

Edit the map_dbrepos_from_source.properties file to map fields between the Profiles DB and the LDAP directory. Open the profiles_functions.js file to see the options for the different mapping functions. You can add your own functions if necessary.

When you run the Profiles population wizard in interactive mode, it generates two property files in the Wizards\TDIPopulation directory: a tdisetting.properties file and a mappings.properties file. The properties in mappings.properties are very similar to those in map_dbrepos_from_source.properties.

The internal name of the Profiles DB is PEOPLEDB.

To map fields:

On the system hosting your Tivoli Directory Integrator installation, create a subdirectory in which to store the Tivoli Directory Integrator solution directory. Make sure that the file path does not contain spaces. Do not, for example, create the subdirectory in the Program Files directory in Microsoft Windows.
Copy the tdisol compressed file from the TDISOL directory of the IBM Connections installation media to the system
...where you installed Tivoli Directory Integrator.
Use appropriate tools, extract the tdisol file to the directory that you created in Step 1. This process creates a Tivoli Directory Integrator Solution directory called TDI.
From the TDI solution directory, open the tdienv.bat or tdienv.sh file in a text editor. Ensure that the path to the Tivoli Directory Integrator installation directory is specified correctly in the TDIPATH variable. If the path is not correct, edit the TDIPATH environment variable.
- AIX or Linux:
  The default value for TDIPATH is:
```
export TDIPATH=/opt/IBM/TDI/V7.1 
```
- Windows:
  The default value for TDIPATH is:
```
SET TDIPATH=C:\IBM\TDI\V7.1
```
Other scripts in the solution directory use this Tivoli Directory Integrator path or tdienv.bat or tdienv.sh file to find Tivoli Directory Integrator files.
Edit the properties files to define the mapping between the LDAP directory and the Profiles DB. Consider using LDAP viewer software to help you map the fields. To define the mappings that are used when populating the Profiles DB from the enterprise directory:
1. From the TDI directory, open the map_dbrepos_from_source.properties file in a text editor.
2. Add or modify the field values. Any values that you omit or set to null are not populated in the DB. You can modify the values in one of the following ways:
  
  1:1 mapping
  
  If one field in the Profiles DB matches one field in the enterprise directory, type the name of the field in the Profiles DB and set it equal to the associated source DB LDAP property. For example:
  bldgId=buildingname
  
  Complex mapping
  
  If there is a more complex relationship between the fields in the Profiles DB and enterprise directory, such as the content of the property in the enterprise LDAP directory must be split into multiple fields in the Profiles DB, use a JavaScript function to define the relationship. Define the function in the profiles_functions.js file and wrap the name of the JavaScript function in braces {}. Begin function names with func_ so that you can more easily identify them. For example:
  bldgId={func_map_to_db_bldgId}
  
  See Example complex mapping of Profiles data for an example of complex mapping.
  The uid, guid, dn, surname, and displayName attributes are always required.
Open the tdi-profile-config.xml file. After the IBM Tivoli Directory Integrator Solution files are extracted, the file is located in the following directory:
TDI/conf/LotusConnections-config

Modify the file to configure the extension attribute, specifying the property's name and mapping from the source. Use the following parameters:

Custom extension attribute parameters
Parameter Description
extensionId The ID of the extension attribute.
This parameter is required.
sourceKey The name of the attribute from the source.
This parameter is required.

Parameter	Description
extensionId	The ID of the extension attribute. This parameter is required.
sourceKey	The name of the attribute from the source. This parameter is required.

For example, to add a simple attribute called spokenLangs, the configuration would look like the following extract from the tdi-profiles-config.xml file:

<simpleAttribute extensionId="spokenLangs"
    sourceKey="spokenLang"/>

The formatting between the tdi-profile-config.xml and the profiles-config.xml files is compatible, so you can copy and paste configuration information between the files. For the extension to be displayed in the user interface, the modifications must be made in profiles-config.xml.

To leverage the custom attribute in the Profiles user interface or REST API, configure the application per the instructions in the Customize Profiles section. For a detailed example that uses custom attributes, see Creating a simple profile data model and template customization.

Save your changes to the tdi-profile-config.xml file.
Optional: Write a JavaScript function that combines different attributes from the LDAP directory to map a customized extension attribute for the Profiles DB:
1. Add the extension attribute function definition in the map_dbrepos_from_source.properties file, using the following format:
  extattr.spokenLangs={func_map_to_langs}
  The extensionAttribute name must match the specified extensionId in the tdi-profiles-config.xml extension attribute definition.
2. Add a new func_map_to_db_extensionAttribute JavaScript function in the TDISolution\TDI\profiles_functions.js file. Write logic for the function that specifies the new extension attribute mapping.
3. Repeat these steps for each JavaScript function.

What to do next

The properties in the map_dbrepos_from_source.properties file have the default values defined in the following table. Many of them are null. You must determine which LDAP properties to map to your DB fields and edit this file to specify values that apply to your configuration. Any values that you omit or set to null are not populated in the DB.

Default values for properties in the map_dbrepos_from_source.properties file
TDI property Default LDAP attribute mapping
alternateLastname null
bldgId null
blogUrl null
calendarUrl null
countryCode c
courtesyTitle null
deptNumber null
description null
displayName cn
Required.
distinguishedName $dn
Required.
email mail
employeeNumber employeenumber
employeeTypeCode employeetype
experience null
faxNumber facsimiletelephonenumber
floor null
freeBusyUrl null
givenName givenName
givenNames gn
groupwareEmail null
guid Required
ipTelephoneNumber null
isManager null
jobResp null
loginId

logins null
managerUid $manager_uid
This property represents a lookup of the UID of the manager using the DN in the manager field.
mobileNumber mobile
nativeFirstName null
nativeLastName null
officeName physicaldeliveryofficename
orgId ou
pagerId null
pagerNumber null
pagerServiceProvider null
pagerType null
preferredFirstName null
preferredLanguage preferredlanguage
preferredLastName null
secretaryUid null
shift null
surname sn
You must provide this field because the Search application expects to find it in the Profiles DB.
Required.
surnames sn
telephoneNumber telephonenumber
timezone null
title null
uid Required.
workLocationCode postallocation

TDI property	Default LDAP attribute mapping
alternateLastname	null
bldgId	null
blogUrl	null
calendarUrl	null
countryCode	c
courtesyTitle	null
deptNumber	null
description	null
displayName	cn Required.
distinguishedName	$dn Required.
email	mail
employeeNumber	employeenumber
employeeTypeCode	employeetype
experience	null
faxNumber	facsimiletelephonenumber
floor	null
freeBusyUrl	null
givenName	givenName
givenNames	gn
groupwareEmail	null
guid	Required
ipTelephoneNumber	null
isManager	null
jobResp	null
loginId
logins	null
managerUid	$manager_uid This property represents a lookup of the UID of the manager using the DN in the manager field.
mobileNumber	mobile
nativeFirstName	null
nativeLastName	null
officeName	physicaldeliveryofficename
orgId	ou
pagerId	null
pagerNumber	null
pagerServiceProvider	null
pagerType	null
preferredFirstName	null
preferredLanguage	preferredlanguage
preferredLastName	null
secretaryUid	null
shift	null
surname	sn You must provide this field because the Search application expects to find it in the Profiles DB. Required.
surnames	sn
telephoneNumber	telephonenumber
timezone	null
title	null
uid	Required.
workLocationCode	postallocation

Map the guid, uid, and loginId: The guid property identifies the global unique ID of a user. This property's value is created by the LDAP directory and is unique, complex, and never changes. It is essential in that it maps each user's IBM Connections data to their User ID when using the Profiles DB as the user repository. The mapping of the guid property must be handled differently depending on the type of LDAP directory that you are using:

Microsoft Active Directory
guid={function_map_from_objectGUID} You must use a JavaScript function to define the value for Active Directory because objectGUID is stored in Active Directory as a binary value, but is mapped to guid, which is stored as a string in the Profiles DB. Also, the samAccountName property used by Active Directory has a 20 character limit, as opposed to the 256 character limit of the other IDs used by IBM Connections.
IBM Lotus Domino
guid={function_map_from_dominoUNID}
IBM Directory Server
guid=ibm-entryUuid
Sun Java System Directory Server
guid=nsUniqueID
Novell eDirectory
guid={function_map_from_GUID}

If you edited the wimconfig.xml file to use a custom global unique ID, be sure to specify that custom ID here. The uid property, not to be confused with the guid property, defines the unique ID of a user. This property differs from a guid in that it is the organization-specific permanent identifier for a user . often a login ID or some value based on the user's employee code. The uid is a critical field in the Profiles DB. By default, this property links a given person's user record back to LDAP data. The value you map to uid must meet the following requirements:

It must be present in every entry that is to be added to the DB.
It must be unique.
In a multi-LDAP environment, it must be unique across LDAP directories.
It must be 256 characters or fewer in length.

In Active Directory, although there often is a UID field available, this field is not always the best choice for mapping to uid because it is not guaranteed to be present for all entries. A better choice is sAMAccountName because it usually does exist for all entries. Other values are acceptable also, as long as they meet the requirements.

> If you are mapping the uid from an LDAP field, specify the name of the field. However, if you need to parse it from the distinguished name and it is in the DN in the form of uid=value, use the following mapping function:

{func_map_to_db_UID}

Use the isManager and managerUid properties to set up the organizational structure of the organization. The isManager field determines whether the current person is a manager or not. You must assign a Y (Yes) or N (No) value to this property for each entry. Y identifies the person as a manager. The managerUid identifies the UID of the current person's manager. By default, managerUid is mapped to $manager_uid, which represents a lookup of the UID of the manager (using the DN contained in the LDAP manager field). If a user's manager information is not contained in the $manager_uid field, you should adjust the mapping accordingly. These two properties work together to identify manager/employee relationships and create a report-to chain out of individual user entries.

If users intend to log into Profiles using a single-valued user name other than the value specified in the uid or email properties, you must map that user name value to the loginId property. To do so, complete the following step:

Set the loginId property in the map_dbrepos_from_source.propeties file equal to the LDAP property to use as the login ID.
For example, if you want to use employeeNumber as the login property, edit the property value as follows:
loginId=employeeNumber

If you have more than one additional login ID (such as with a long and short form UID) and you want to allow users to login with either of their login IDs, you can populate multiple additional login IDs by using one of the following settings:

logins=multiValuedLdapAttribute

logins={function_to_get_multiple_ldap_values}

For more information, see the Tivoli Directory Integrator product documentation.

Add profile types:

IBM Connections supports the ability to classify a profile using a profile type. The profile type allows the application to provide the set of properties that are intended for a given profile object. For more information, see Profile-types.

Example complex mapping of Profiles data

This example illustrates a sample complex mapping using Javascript functions to define mapping between the LDAP directory and the Profiles DB.

When manually mapping Profiles fields you can perform 1:1 or complex mapping as described in the Mapping fields manually topic.

In this example, the mapping pertains to the surnames list. The primary CRUD functions (create, retrieve, update and delete) are illustrated context. The example is intended for illustrative purposes only.

The map_dbrepos_from_source.properties mapping file contains the following statement:

surname=sn
surnames={func_surNames_basic}

This means there is an LDAP field named sn which contains a list of surnames. The first property (surname=sn) causes the first entry in the list to be stored in the surname field or row in the Profiles user table. If the second property were also assigned to sn, this would cause the list to be placed in the Profiles SURNAME table. However, the following function has been specified.

function func_surNames_basic(fieldName) 
{
    var fieldName str = fieldName.toString();   // be cautious, make sure it is a string.
    var result = work.getAttribute("sn");       // get the list

    if(result == null) 
    {
        result = "no sn work element";          // return bogus value. See the function
                                                // func_compute_givenName() in profiles_functions.js
                                                // for a more realistic approach.
    }
    else
    {
        result = result.clone();
        var len = result.size();
        for (var i = 0; i <len; i++) 
        {
            var val = result.getValue(i);
            if (!(val instanceof java.lang.String)) 
            {
                val = java.lang.String.valueOf(val);
                val = val + " Esq                    // append .Esq.
                result.setValue(i, val);             // update value
            }
        }
    }
    result.setValue(len, fieldNamestr);
    return result;
}

In the first line the fieldName value is the name of the property, in this example the surnames property. This makes it possible to use the same function for a number of items.

In the third line the sn list is a variable named result. The argument of the getAttribute() must be the value of a property, in this example the sn property value.

A test for sn not being available occurs at the fourth line in the result = "no sn work element" statement.

Given that the list is available, we clone it to avoid changing the entry list. We next iterate through the list testing to verify that each value is a string. This is a best practice even though in this case it may seem unnecessary. The line containing .result.getValue(i);. gets the next item in the list; this represents the R element of CRUD. The result.setValue(i, val); line shows how to modify a value; this represents the U element of CRUD. After the iteration we add the fieldname to the list in the result.setValue(len, fieldNamestr); statement; this represents the C element of CRUD. The example uses the same setValue method for both the create and update functions.

Further, let.s suppose we don.t want any more than five names in the surnames list. Add the following entry after the for (var i = 0; i <len; i++) { demonstrate how the delete function works.

if (i > 4)
{
result.removeValue(i);
len--; i--;
continue;
}

Attribute mapping for Profiles

When the Profiles directory service is enabled, IBM Connections relies on the Profiles DB to provide user data such as user name, ID, and email.

The internal name of the Profiles DB is PEOPLEDB.

The following table shows the mapping relationships between Profiles, the Profiles directory service, Virtual Member Manager, and LDAP.

Attribute mapping table
Profiles DB column Profiles Directory Service Virtual Member Manager LDAP
PROF_GUID ID uniqueId UUID/GUID/UNID (defined in RFC4122)
PROF_DISPLAY_NAME Name cn/displayName cn/displayName
PROF_MAIL Mail mail/ibm-primaryEmail mail/ibm-primaryEmail
PROF_SOURCE_UID DN uniqueName DN
PROF_UID UID UID UID or samAccountName (in MS AD/ADAM only)
PROF_LOGIN LOGIN Login attributes other than UID and mail LDAP login attributes other than UID and mail

Profiles DB column	Profiles Directory Service	Virtual Member Manager	LDAP
PROF_GUID	ID	uniqueId	UUID/GUID/UNID (defined in RFC4122)
PROF_DISPLAY_NAME	Name	cn/displayName	cn/displayName
PROF_MAIL	Mail	mail/ibm-primaryEmail	mail/ibm-primaryEmail
PROF_SOURCE_UID	DN	uniqueName	DN
PROF_UID	UID	UID	UID or samAccountName (in MS AD/ADAM only)
PROF_LOGIN	LOGIN	Login attributes other than UID and mail	LDAP login attributes other than UID and mail

The following table shows the population functions that are used in TDI scripts to populate ID into PROF_GUID.

Population functions for populating ID into PROF_GUID
LDAP implementations LDAP attribute type names LDAP syntax TDI scripts with functions
IBM Lotus Domino Server dominoUNID Directory String (in Byte String Format)
{function_map_from_dominoUNID}
Novell eDirectory Server GUID Octet String (in Binary Format)
{function_map_from_GUID}
Microsoft AD/ADAM Server/Service objectGUID Octet String (in Binary Format)
{function_map_from_objectGUID}
Microsoft AD/ADAM Server/Service objectSID Octet String (in Binary Format)
{function_map_from_objectSID}
IBM Tivoli Directory Server ibm-entryUUID Directory String (in Canonical Format) n/a
Sun Java Directory Server nsuniqueid Directory String (in Canonical Format) n/a

LDAP implementations	LDAP attribute type names	LDAP syntax	TDI scripts with functions
IBM Lotus Domino Server	dominoUNID	Directory String (in Byte String Format)	{function_map_from_dominoUNID}
Novell eDirectory Server	GUID	Octet String (in Binary Format)	{function_map_from_GUID}
Microsoft AD/ADAM Server/Service	objectGUID	Octet String (in Binary Format)	{function_map_from_objectGUID}
Microsoft AD/ADAM Server/Service	objectSID	Octet String (in Binary Format)	{function_map_from_objectSID}
IBM Tivoli Directory Server	ibm-entryUUID	Directory String (in Canonical Format)	n/a
Sun Java Directory Server	nsuniqueid	Directory String (in Canonical Format)	n/a

Configure the Manager designation in user profiles

When you map manager data in the Profiles DB, you can mark manager profiles and also create report-to chains.

Each profile contains a manager_uid field which stores the uid value of that person's manager. This information is used to build the Reports To display widget in the Profiles user interface. For information about the manager_uid field, see Mapping fields manually.

Additionally, the isManager field (which equates to the Mark manager mapping task in the Profiles population wizard) is used to mark the user profile as being a manager. This information is used to build the People Managed display widget in the Profiles user interface. A Y or N attribute is assigned to an employee to indicate whether the employee is listed as a manager of other employees.

You can set the isManager field as described in the Mapping fields manually topic (using either 1:1 mapping or function mapping) or by running the Mark manager task (using the population wizard or by running the mark_manager.bat or mark_manager.sh script). For more information about these options see Using the Profiles population wizard and Manually populating the Profiles DB.

If you are setting the ismanager field using a 1:1 mapping, ensure specified how to set the field in the map_dbrepos_from_source.properties file. For example, if the LDAP has an ismanager field that is set to a value of Y or N, your map_dbrepos_from_source.properties file could specify the following property:

PROF_IS_MANAGER=ismanager

If the manager information is supplied directly from the source, the Mark manager task is not necessary.

The Mark manager task will iterate through the profiles, and see if that particular profile is referenced as the manager for any other profiles. If yes, it will mark that profile as a manager. If that profile is not referenced as anyone else's manager, it will be marked as not a manager.

For information about configuring the display of the Reports To and People Managed widgets for your organization, see Enabling the display of organizational structure information.

Supplemental user data for Profiles

You can supplement user profiles data using a mapping table, the profiles_tdi.properties file, and CSV files.

Map user data

You can map additional user data to supplemental tables within the Profiles DB and then display that data in a user's profile.

When the LDAP directory provides a code or abbreviation for a particular setting, the supplemental table can provide extra data. For example, an employeeType of P in the LDAP directory might correspond to Permanent. If the employee-type table is populated with data such as p;permanent, this extra data can be displayed in the profile.

The profiles_tdi.properties file stores the settings that determine how the files are formatted.

These properties are supplied in the profiles_tdi.properties file. The file path specified is relative to the TDI solution directory.

The mapping task for Profiles maps your user data to the following entities:

Fill countries: Add country data to each profile.
Fill departments: Add department data to each profile.
Fill organization: Add organization data to each profile.
Fill employee types: Add employee-type data to each profile.
Fill work locations: Add location data to each profile.

CSV files

A CSV (comma separated value) file is required as input for each of these tasks.

The following properties pertain to the CVS files used by these tasks:

country_table_csv_separator=;
country_table_csv_file=isocc.csv

department_table_csv_separator=;
department_table_csv_file=deptinfo.csv

emp_type_table_csv_separator=;
emp_type_table_csv_file=emptype.csv

organization_table_csv_separator=;
organization_table_csv_file=orginfo.csv

workloc_table_csv_separator=;
workloc_table_csv_file=workloc.csv

The separator character separates the different tokens in each line. The second property is the name of the file, relative to the solution directory.

The first token is the code. The next attributes are read in order for each additional field. No other fields are required.

The data that can be populated in these tables is usually provided as two values per line: code;description. For the workloc code, the values can be code;addr1;addr2;city;state;zip. For example: WSF;FIVE TECHNOLOGY PARK DR;;WESTFORD;MA;01886-3141.

Fields that you do not require in your mapping can be omitted from the file; this example uses only one addr field.

The default file name for each codes is shown in the following list:

countryCode: isocc.csv
deptNumber: deptinfo.csv
orgId: orginfo.csv
employeeTypeCode: emptype.csv
workLocationCode: workloc.csv

Sample CSV file

This sample shows some lines from the isocc.csv file, which can be used to fill countries data:

ad;Andorra, Principality of
ae;United Arab Emirates
af;Afghanistan, Islamic State of
ag;Antigua and Barbuda
ai;Anguilla
al;Albania
am;Armenia
an;Netherlands Antilles
ao;Angola
aq;Antarctica
ar;Argentina

You can find more sample CSV files in the wizard_files_directory/TDIPopulation/TDISOL/aix|lin|win/samples directory,

...where the wizard_files_directory is the location of the various Wizard files that you downloaded or received on disk, and aix|lin|win is the AIX, Linux, or Microsoft Windows version of the directory.

Install Cognos Business Intelligence

IBM Cognos Business Intelligence collects, manages, and displays statistical information for the Metrics application in IBM Connections. Installing Cognos Business Intelligence involves installing IBM WAS Network Deployment, plus a DB client, in addition to the Cognos components.

This documentation assumes you are deploying Cognos Business Intelligence before you install IBM Connections. If you choose to deploy Cognos later, you can ignore any Cognos-related validation errors during the Connections installation process and then return to this section later for instructions on deploying the Cognos components. Even if you are not deploying Cognos now, you can create the raw Metrics DB and install the Metrics application so that Connections can immediately begin capturing event data for later use.

IBM Connections requires a customized version of Cognos Business Intelligence, which is installed using the provided script. You cannot use previously deployed Cognos Business Intelligence components with the Metrics application. For best performance, use a separate computer for the customized version of Cognos Business Intelligence.

To install the Cognos Business Intelligence and its supporting software, complete these tasks:

Install required patches on the Cognos BI Server system

Before installing IBM Cognos Business Intelligence and its related software, prepare the server environment by applying required patches to the operating system and other third-party components.

Any required patches must be installed before you attempt to deploy the Cognos server.

Review IBM technote 7022463, Cognos BI 10.1.1 Software Environments - Required Patches.
Open Motif libraries are still required (as mentioned in the technote) for headless Linux systems.
Install the patches specified for your server environment.
Restart the server to make sure all patches take effect.

Install WAS for Cognos Business Intelligence

Install IBM WAS Network Deployment on the computer that will host IBM Cognos Business Intelligence, so that the server can be managed by the Deployment Manager used with IBM Connections.

The WebSphere node hosting the Cognos BI server will be federated to the same dedicated Deployment Manager as your IBM Connections deployment. Do not use a WebSphere node that has already been federated to a different Deployment Manager.

Install WAS Network Deployment as described in the WAS Version 7.0 information center.
This server should be installed using the Application server profile; you will federate it to the Deployment Manager in a later task.
If you will use a server where the appropriate version of WAS Network Deployment is already deployed, you do not have to install it again; just create a new Application server profile for Cognos Business Intelligence as follows:
IBM AIX, Linux
```
manageprofiles.sh -create -templatepath  WAS_install_root/profileTemplates/default -adminUserName was_admin_name -adminPassword was_admin_password
```
Microsoft Windows
```
manageprofiles.bat -create -templatepath  WAS_install_root\profileTemplates\default -adminUserName was_admin_name -adminPassword was_admin_password
```
You can verify that the installation was successful by reviewing the WAS log stored in: Cognos_WAS_node_profile/logs/Cognos_server_name/SystemOut.log; for example on Windows:
```
C:\IBM\WebSphere\AppServer\profiles\CognosNode01\logs\cognos_server\SystemOut.log
```
On the newly installed server, set the system clock to match the time (and time zone) on the Deployment Manager.s computer.
The node.s clock must be synced to within 1 minute of the Deployment Manager.s clock to ensure that federation does not fail in a later task.

Install Cognos Business Intelligence components

Install IBM Cognos Business Intelligence on the computer where you previously installed IBM WAS Network Deployment and the DB client. The Cognos product consists of two components (Cognos BI Server and Cognos Transformer); you must install both components as part of this deployment.

The following conditions must be satisfied to ensure that the Cognos Business Intelligence components installs correctly:

The Cognos Content Store DB must have been created on the DB server, and that DB server must be running (see Create DBs
The Deployment Manager must be running.
The DB client must have been installed on the current server, but does not have to be running.
The current server must reside within the same domain as the IBM Connections servers so you can enable SSO (Single Sign-On) as required for generating reports.
The user running the Cognos installation script must have permissions to use the DB client.

Install Cognos Business Intelligence requires two Cognos packages (BI Server and Transformer) in addition to the scripts provided in the IBM Connections kit.

The installation packages for Cognos Business Intelligence components are available in the IBM Connections kit as separate downloads.

Package names for Cognos components to be installed for use with IBM Connections.
Operating System Cognos BI Server package name Cognos Transformer package name
IBM AIX IBM Cognos Business Intelligence Server 64-bit 10.1.1 AIX Multilingual IBM Cognos Business Intelligence Transformer 10.1.1 AIX Multilingual
Linux IBM Cognos Business Intelligence Server 64-bit 10.1.1 Linux x86 Multilingual IBM Cognos Business Intelligence Transformer 10.1.1 Linux x86 Multilingual
Microsoft Windows IBM Cognos Business Intelligence Server 64-bit 10.1.1 Windows Multilingual IBM Cognos Business Intelligence Transformer 10.1.1 Windows Multilingual
zLinux (System z) IBM Cognos Business Intelligence Server 64-bit 10.1.1 Linux on System z Multilingual (CI5W5ML IBM Cognos Business Intelligence Transformer 10.1.1 Linux on System z Multilingual (CI2QHML)

Operating System	Cognos BI Server package name	Cognos Transformer package name
IBM AIX	IBM Cognos Business Intelligence Server 64-bit 10.1.1 AIX Multilingual	IBM Cognos Business Intelligence Transformer 10.1.1 AIX Multilingual
Linux	IBM Cognos Business Intelligence Server 64-bit 10.1.1 Linux x86 Multilingual	IBM Cognos Business Intelligence Transformer 10.1.1 Linux x86 Multilingual
Microsoft Windows	IBM Cognos Business Intelligence Server 64-bit 10.1.1 Windows Multilingual	IBM Cognos Business Intelligence Transformer 10.1.1 Windows Multilingual
zLinux (System z)	IBM Cognos Business Intelligence Server 64-bit 10.1.1 Linux on System z Multilingual (CI5W5ML	IBM Cognos Business Intelligence Transformer 10.1.1 Linux on System z Multilingual (CI2QHML)

Create a shared network folder where Cognos Transformer can publish metrics data (in the form of PowerCubes) for reports to access.
The shared network folder is used when you cluster multiple Cognos servers; you can use any name you want for the folder. Record this location so you can assign it to the cognos.cube.path property when you set up the cognos-setup.properties file in step 6.
Prepare the Cognos BI Server package:
1. Download the Cognos BI Server package to a temporary location on the server.
2. Create a directory to contain the expanded package; for example:
  - AIX or Linux: /opt/biserver_10.1.1
  - Windows: C:\biserver_10.1.1
3. Expand the package into the new directory.
Prepare the Cognos Transformer package:
1. Download the Cognos Transformer package to a temporary location on the server.
2. Create a directory to contain the expanded package; for example:
  - AIX or Linux: /opt/transformer_10.1.1
  - Windows: C:\transformer_10.1.1
  Due to potential file name conflicts, the Transformer package cannot share a directory with the BI Server package. Extracting the packages to the same location will overwrite libraries and result in a non-functioning server.
3. Expand the package into the new directory.
Prepare the Cognos server setup package:
CognosConfig.zip or CognosConfig.tar can be found in the /Cognos folder within the Connections product media.
1. Download the CognosConfig package to a temporary location on the server.
2. Create a directory to contain the expanded package; for example:
  - AIX or Linux: /opt/CognosSetup
  - Windows: C:\CognosSetup
3. Expand the package into the new directory.
Set up the JDBC driver:
1. Locate the type 4 JDBC driver provided by your DB server product.
2. Copy the JDBC driver to the following location: /CognosSetup/BI-Customization/JDBC
Prepare the cognos-setup.properties file by filling in a value for each property.
The cognos-setup.properties file is located in the CognosSetup directory where you expanded the Cognos server setup package in step 4. This file provides values that are used during installation; each property setting in the file is accompanied by a description.
Notes® on the settings in this file:
- The shared network folder is represented by the cognos.cube.path property; set this property to the name you used for the shared network folder that you created in step 1.
- The Cognos administrator account specified for the cognos.admin.username setting must represent a valid LDAP user . this is not the WebSphere administrator. You should have already set up a user in the LDAP for this purpose; for information see Create the Cognos administrator.
- (Oracle DB) When you installed the Oracle DB client, you should have written down the DB settings hat you will use in the cognos-setup.properties file; refer to those settings now.
- Any passwords stored in this file will be removed after the script finishes running; if you need to run the script again you will need to insert the passwords before the next run. If you prefer, you can omit the passwords from the properties file and supply them on the command line when you run the script, as shown in step 9.
(RedHat Linux 6 64-bit systems) Run the following command to preload libraries needed for the setup scripts used in the next step:
```
export LD_PRELOAD=/usr/lib64/libfreebl3.so
```
(SuSE 11 zLinux systems) Create a symbolic link to the libXm.so.3 package:
The openmotif22-libs-32bit-2.2.4-138.18.1 kit includes libXm.so.4, while the Cognos installer program issetup script links with libXm.so.3 and encounters an error if it is not available. Prevent this error by creating a symbolic link to libXm.so.3 with the following command:
```
ln -s /usr/lib/libXm.so.4 /usr/lib/libXm.so.3
```
(Microsoft SQL Server) If you are using Microsoft SQL Server as your DB management system, configure it to support remote connections before running the cognos-setup.bat|sh script, or the DB validation will fail. For information on enabling remote connections in SQL Server, see the Microsoft site.
Run the cognos-setup.sh script to install the Cognos BI Server and Transformer components.
Any of the properties specified in the cognos-setup.properties file can be passed in as parameters when you run this script. In particular, you might want to supply passwords using this method rather than adding them into the properties file because they will be deleted from the file after it runs. For any properties you supply at run time, use the following syntax:
```
cognos-setup.sh -property_name1=property_value1 -property_name2=property_value2
```
For example, the properties file contains settings for four passwords. You can pass all of them in at run time by including them on the command line as shown:
```
cognos-setup.sh -was.local.admin.password=WASadmin_pwd -cognos.admin.password=CognosAdmin_pwd -cognos.db.password=CognosContentStore_pwd -metrics.db.password=Metrics_DB_pwd
```
Output from this operation is stored in the /CognosSetup/cognos-setup.log.
If you encounter an error when running the cognos-setup.bat|sh script, correct the error and run the script again before proceeding to the next step. For example, if you provided an incorrect password in the cognos-setup.properties file, modify the password and then run the cognos-setup.sh script again. Remember that if you added passwords to the properties file, they were deleted after the previous run, and must be provided again. If you encounter other problems, see Troubleshoot Cognos Business Intelligence components for possible solutions.
Now run the cognos-configure.sh script to configure the Cognos server and set up DB connections.
Any of the properties specified in this script can be passed in as parameters when you run this script, using the syntax shown in the previous step.
Output from this operation is stored in the /CognosSetup/cognos-configure.log.
If you encounter an error when running the cognos-configure.sh script, correct the error and run the script again before proceeding to the next step. For example, if you provided an incorrect password in the cognos-setup.properties file, modify the password and then run the cognos-setup.sh script again. Remember that if you added passwords to the properties file, they were deleted after the previous run, and must be provided again. If you encounter other problems, see Troubleshoot Cognos Business Intelligence components for possible solutions.
Leave the Cognos server stopped for now; you will start the server after federating it to the Deployment Manager in the next task.
In the future, whenever you want to stop the Cognos server, you must stop the WAS hosting it; wait at least 1 full minute to ensure that all of the Cognos processes (AIX or Linux: cgsServer.sh and CAM_LPSvr processes;
Windows: cgsLauncher.exe and CAM_LPSvr processes) have completely stopped before you attempt to start the server again.

Results

The Cognos BI Server and Transformer components are installed into the directories specified in the cognos-setup.properties file; for example:

Cognos BI Server: cognos.biserver.install.path
- AIX or Linux: /opt/IBM/Cognos64
- Windows: C:\Program Files\IBM\Cognos
Cognos Transformer: cognos.transformer.install.path
- AIX or Linux: /opt/IBM/Cognos
- Windows: C:\Program Files (x86)\IBM\Cognos

During the installation, you might see the following message: ERROR: The system cannot find the file specified. If this message is followed by "success" messages" similar to those shown here, then the installation was successful and you can ignore the error message.

<date><time> : daily refresh success
<date><time> : rebuild <year><month> success

You can verify that the components were installed successfully by reviewing the installation logs at the following locations:

Cognos BI Server installation log: Cognos_BI_install_path/logs/cogserver.log
- AIX or Linux: /opt/IBM/Cognos64/logs/cogserver.log
- Windows: C:\Program Files\IBM\Cognos\logs\cogserver.log
Cognos Transformer installation log: Cognos_Transformer_install_path/logs/cogserver.log:
- AIX or Linux: /opt/IBM/Cognos/logs/cogserver.log
- Windows: C:\Program Files (x86)\IBM\Cognos\logs\cogserver.log

Install the DB client for Cognos Transformer

Install a DB client on the computer where you will host IBM Cognos Business Intelligence. The Cognos Transformer component requires the use of a DB client to ensure proper access to the DB server for PowerCube generation and reporting.

Install the DB2 DB client for Cognos Transformer

Install the IBM DB2 DB client on the computer

...where you will host IBM Cognos Business Intelligence.

Before you install the DB client, the DB server must be installed and running, and you must have created the Metrics DB and the Cognos Content Store DB.

Install the DB client on the server where you will deploy Cognos Business Intelligence, using the instructions provided with your DB product.
For instructions on installing the IBM DB2 client, see the Installation methods for IBM data server clients in the DB2 information center.
(DB2 on Linux only) Ensure that the DB2 client library is properly sourced:
1. In the DB2 client installation directory, open the /etc/ld.so.conf file for editing.
2. Add the following library /opt/ibm/db2/V9.7/lib32 to the file.
3. Save and close the file.
4. Run the ldconfig command to regenerate dynamic link libraries (DLLs).
Create a connection between the client and the DB.
First, connect the client to the node (the DB2 server) where the DB is hosted by completing the following steps.
1. Log on to the client computer as a user with at least DB2 SYSADM authority.
  You cannot catalog a node as a root authority.
2. Change to the home directory of instance.
  The substeps below refer to this directory as INSTHOME.
3. (AIX or Linux) Set up the instance environment by running the startup script:
  bash, Bourne, or Korn shell
```
. INSTHOME/sqllib/db2profile
```
  C shell
```
source INSTHOME/sqllib/db2cshrc
```
  ...where INSTHOME indicates the home directory of the instance.
4. Open the DB2 command line processor:
  AIX or Linux
```
db2
```
  Windows
```
db2cmd
```
  ...where INSTHOME indicates the home directory of the instance.
5. Catalog the DB2 server by entering the following commands in the command line processor:
```
db2 => catalog tcpip node Node_name remote Host_name|IP_address
       server Service_name|DB2_Instance_Port

db2 => terminate
```
  Where:
  - Node_name indicates a local nickname (for example, the short host) that you can set for the DB2 server.
  - Host_name|IP_address indicates the host or IP address of the server instance where the DB resides (both IPv4 and IPv6 addresses are accepted).
  - Service_name|DB2_Instance_Port indicates the service name or DB2 instance port used for the connection (typically port 50000 for DB2).
  For example, connect to the server called "db2node" with the IP address "2001:DB8:0:0:0:0:0:0" on port 50000 as follows:
```
db2 =>  catalog tcpip node db2node remote 2001:DB8:0:0:0:0:0:0 server 50000 
DB20000I  The CATALOG TCPIP NODE command completed successfully.
DB21056W  Directory changes may not be effective until the directory cache is refreshed.

db2 =>  terminate 
DB20000I  The TERMINATE command completed successfully.
```
Now connect the client to the DB2 DB itself .
For DB2, configure the client to use Metrics as both the Database name and the Database alias.
1. Run the following commands in the DB2 command line processor:
```
db2 => catalog DB Database_name as Database_alias at node Node_name

db2 => connect to Metrics user Metrics_db_user

db2 => terminate
```
  Where the DB2 server is the node you just connected to, and the DB information matches the values specified in the cognos-setup.properties file that is used during installation:
  - Database_name indicates the name of the Metrics DB (the metrics.db.name setting; the default value is METRICS).
  - Database_alias indicates the alias for the Metrics DB (the metrics.db.local setting; the default value is METRICS).
  - Node_name is the same local nickname that you used to connect to the DB2 server earlier in this step.
  - Metrics_db_user indicates the user name that will be used to access the DB (the metrics.db.user setting; the default value is LCUSER).
  For example, catalog the METRICS DB on the server "db2node" as the user "LCUSER" and then test the connection with the following commands:
```
db2 =>  catalog DB METRICS as METRICS at node db2node 
DB20000I  The CATALOG DATABASE command completed successfully.
DB21056W  Directory changes may not be effective until the directory cache is refreshed.

db2 =>  connect to METRICS user LCUSER 
Database Connection Information     
Database server = DB2 9.7.0     
SQL authorization ID = LCUSER     
Local DB alias = METRICS

db2 =>  terminate 
DB20000I  The TERMINATE command completed successfully.
```
2. When you have successfully cataloged the DB, close the DB2 command line processor with the following command:
```
db2 =>  quit 
```
For more information on connecting the DB2 client to the DB2 server and DB (including optional arguments), see Configure client-to-server connections using the command line processor in the DB2 information center.

Install the Oracle DB client for Cognos Transformer

Install the Oracle DB client on the computer where you will host IBM Cognos Business Intelligence.

Before you install the DB client, the DB server must be installed and running, and you must have created the Metrics DB and the Cognos Content Store DB.

For troubleshooting information on configuring the Oracle DB client for use with Cognos, see the IBM technote, Resolve Oracle connection errors.

Install the standard 32-bit DB client on the server
...where you will deploy Cognos Business Intelligence; for information see Install Oracle Database Client.
Be sure to install the standard 32-bit client rather than the Instant Client, which is not supported by Cognos. If you installed the 64-bit client, you must uninstall it before installing the 32-bit client.
Copy the following files to the Cognos_Transformer_install_path/bin directory:
- Oracle_client_install_path/lib/libclntsh.so.11.1
- Oracle_client_install_path/lib/libnnz11.so
If you are using a different version of the Oracle client, you should find similar files (named for the version) in the same location, and can use those files instead.
(AIX or Linux) If you are not logged in as root, change the permissions on the two files using chmod 755.
Restart the server:
1. Stop the IBM WAS that hosts the Cognos server.
2. Wait at least 1 full minute to ensure that all Cognos processes have stopped:
  - AIX or Linux: cgsServer.sh and CAM_LPSvr processes
  - Windows: cgsLauncher.exe and CAM_LPSvr processes
3. Start WAS.
4. Start the Cognos server.
If possible restart the server and then start Cognos service. If you cannot restart the server, just restarting the Cognos service should do.

Define the ORACLE_HOME, TNS_ADMIN, and LD_LIBRARY_PATH locations:

ORACLE_HOME=/u01/app/oracle/product/11.2.0/client_1
LD_LIBRARY_PATH=Cognos_Transformer_install_path/bin; ORACLE_HOME/lib
TNS_ADMIN=ORACLE_HOME/network/admin

Edit the Oracle_client_install_path/network/admin/tnsnames.ora file and add the following TNS settings into the file:
The TNS setting on the Oracle client should look like the example that follows:
```
METRICS =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = Oracle_DB_server_host_name)(PORT = Port))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = Database_service_name)
    )
  )
```
...where:
- Oracle_DB_server_host_name is the host of the server hosting the Oracle DB server; for example: oradb.example.com.
- Port is port on which the Oracle DB server is listening; typically port 1521.
- Database_service_name is the DB service name; for example orcl.

Write down the following settings so you can enter them into the cognos-setup.properties file in a later task:

Use the same values for the Oracle_DB_server_host_name, the Port, and the Database_instance_name that you used in the Oracle tnsnames.ora file.

cognos.db.type=oracle
cognos.db.host=Oracle_DB_server_host_name:Port
cognos.db.name=Database_instance_name
cognos.db.user=cognos           //created by installer
cognos.db.password=pass

metrics.db.type=oracle
metrics.db.host=Oracle_Database_Server:1521
metrics.db.name=orcl

metrics.db.local.name=METRICS   //local TNS name
metrics.db.user=metricsuser     //created by installer
metrics.db.password=pass

Verify the client can connect to the Metrics DB.
If the Oracle client encounters errors connection to the Metrics DB, refer to the IBM technote, Resolve Oracle connection errors.

Federate the Cognos server to the Deployment Manager

The computer hosting the IBM Cognos Business Intelligence server must be federated to the same dedicated Deployment Manager used by IBM Connections.

Before attempting to federate the Cognos node to the Deployment Manager, make sure that:

The Deployment Manager is running.
The Cognos server is stopped (if you started it after installation, stop it now by stopping the IBM WAS hosting it).
The system clock on the Cognos server is set to within 1 minute of the time (and time zone) of the system clock on the Deployment Manager.
The Deployment Manager and the Cognos server are either both registered in the DNS or are referenced in each other.s etc/hosts file.

This task involves working on the newly installed Cognos Business Intelligence server to add the node to the Deployment Manager, and then working on the Deployment Manager to create virtual ports for the new node.

On the Deployment Manager, disable Java 2 security:
1. Log into the Integrated Solutions Console as the WebSphere administrator.
2. Click Security > Global Security
3. Look under "Java 2 security" and clear the selection for Use Java 2 security to restrict application access to local resources.
4. Click Apply.
5. Click OK.
Use the computer hosting the Cognos components to federate the new node to the Deployment Manager:
1. On the computer hosting the Cognos components, open a command window and navigate to the/bin directory in the WAS installation root; for example:
  - IBM AIX, Linux: /opt/IBM/WebSphere/AppServer/bin
  - Microsoft Windows:: C:\Program Files\IBM\WebSphere\AppServer\bin
2. Run the addNode command to federate the node to the Deployment Manager as follows:
```
addNode.bat|sh DM_host_name DM_port -profileName Cognos_profile_name -includeapps -username DM_admin_user_name -password DM_admin_password
```
  where:
  - DM_host_name is the fully qualified host of the Deployment Manager.
  - DM_port is the SOAP_CONNECTOR port that the Deployment Manager is listening on; the default port is 8879.
    You can determine the port by checking the SOAP_CONNECTOR_ADDRESS value in the following file on the computer hosting the Deployment Manager::
    WAS_install_root/profiles/DM_Name/properties/portdef.props; for example on Windows:
```
C:\IBM\WebSphere\AppServer\profiles\Dmgr01\properties\portdef.props
```
  - Cognos_profile_name is the profile name where Cognos Business Intelligence is installed (in case multiple profiles are installed on the same server).
    Tip: If you only installed one WebSphere profile on the server, you can omit this parameter.
    If you are not sure of the Deployment Manager.s profile name, you can determine it by looking at the directory name
    ...where it was installed; for example on Linux:
```
/opt/IBM/WebSphere/AppServer/profiles/Cognos_profile_name
```
  - DM_admin_user_name is the user name of the WebSphere administrator on the Deployment Manager, and DM_admin_password is the associated password.
  Make sure you specify -includeapps as shown in the example.
  For example:
```
addNode.bat lc40.example.com 8879 -profileName AppSrv01 -includeapps -username wasadmin -password my_WASadmin_pwd
```
3. Now start the node agent by running the startNode command (from within the same directory); for example:
  - AIX or Linux: startNode.sh
  - Windows: startNode.bat
Move back to the Deployment Manager and create virtual ports for the new node:
1. Log into the Integrated Solutions Console as the WebSphere administrator.
2. In the navigation tree, click Servers > Server Types > WebSphere Application servers > Cognos_server_name > Ports.
3. Note the values for the following ports, for use in the next step:
  - WC_defaulthost
  - WC_defaulthost_secure
4. Back in the navigation tree, click Environment > Virtual Hosts > default_host > Host Aliases.
5. Click the New button in the ports table and add a port representing WC_defaulthost; then click OK:
  - Host name: *
  - Port: use the value of the WC_defaulthost port that you noted earlier.
6. Click the New button again and add a port representing WC_defaulthost_secure; then click OK:
  - Host name: *
  - Port: use the value of the WC_defaulthost_secure port that you noted earlier.
7. Save the changes to the master configuration by clicking the Save link in the "Messages" box at the top of the page.
Synchronize the new node to the Deployment Manager:
1. On the navigation tree, click System Administration > Nodes.
2. In the nodes table, click the checkbox that precedes the new node (the Cognos server).
3. Click the Synchronize button in the table and wait for the operation to finish before proceeding to the next step.
  Synchronization might take several minutes to complete; be sure to allow sufficient time before restarting the Cognos server in the next task.
Restart the Cognos server:
1. Stop the IBM WAS that hosts the Cognos server.
2. Wait at least 1 full minute to ensure that all Cognos processes have stopped:
  - AIX or Linux: cgsServer.sh and CAM_LPSvr processes
  - Windows: cgsLauncher.exe and CAM_LPSvr processes
3. Start WAS.
4. Start the Cognos server.

Validate the Cognos BI server installation

Verify the IBM Cognos Business Information server is correctly installed by viewing its content manager and dispatcher pages.

Make sure the Cognos server is running.

For configuration tips and information on troubleshooting the Cognos Business Intelligence installation, see Troubleshoot Cognos Business Intelligence.

From any browser, navigate to the Cognos server.s content manager at the following address:
```
http://Host_Name:Port/Context_Root/servlet
```
where:
- Host_Name is the fully qualified host of the Cognos server; for example, host.example.com.
  This value is specified in the was.fqdn.hostname property in the cognos-setup.properties file used for installing the server.
- Port is the port that the Cognos server is listening on.
- Context_Root is the context root to which you installed the Cognos server; for example, cognos.
  This value is specified in the cognos.context_root property in the cognos-setup.properties file using for installing the server (the default value was set to cognos).
For example:
```
http://cognosserver.example.com:9083/cognos/servlet
```
The IBM Cognos Content Manager displays the following information: build number, server start time, current time, and current server state. The state should be running; if it is not, see Troubleshoot Cognos Business Intelligence components for possible problems and suggested solutions.
Next, verify the dispatcher:
1. In the browser, navigate to the dispatcher.s address:
  - If you have not yet federated the node to the Deployment Manager, use the following URL:
```
http://Host_Name:Port/Context_Root/servlet/dispatch/ext
```
  - If you have already federated the node to the Deployment Manager, use the following URL:
```
http://Host_Name:Port/Context_Root/servlet/dispatch
```
    Images and icons may not display properly for this URL, but it is sufficient to validate that the IBMConnectionsMetrics folder and subfolders exist.
  where the Host_Name, Port, and Context_Root values are the same as those used in step 1. For example:
```
http://cognosserver.example.com:9083/cognos/servlet/dispatch
```
  The dispatcher displays tabs listing public and private folders.
2. In the dispatcher, click the Public tab; in the list of public folders click the IBMConnectionsMetrics folder and verify that it contains three subfolders (Metrics, MetricsCubeDS, and MetricsDBQuery).

What to do next

If you deployed Cognos Business Intelligence as a prerequisite step to installing IBM Connections, continue the next section, Install IBM Connections. You will complete the Cognos configuration tasks after you install the Connections applications.

If you originally installed IBM Connections without first deploying Cognos Business Intelligence and are now deploying the Cognos server, skip the Connections installation topics (which you have already completed) and instead go directly to Configure Cognos Business Intelligence.

Install IBM Connections

Select the IBM Connections applications and install them in a clustered deployment.

An IBM Connections deployment consists of the following components:

WAS nodes:
- One node with IBM WAS Network Deployment Manager (DM) installed.
- One or more WAS nodes that can be federated into the DM cell. These nodes are hosts for cluster members.
A system with a DB server installed.
An LDAP server.
A system with IBM HTTP Server installed.

Before beginning the installation, you must understand the prerequisites for IBM Connections 4.0. For more information, see the Before installing topic and ensure that you meet all the conditions that are prescribed for your deployment environment.

Before installing

Verify that all necessary prerequisite conditions are complete before installing IBM Connections.

Prerequisites

Check the Release notes for late-breaking issues.
If you previously installed IBM Installation Manager, update it to V1.4.4 or higher. For more information, go to the IBM Installation Manager updates webpage.
Use the same user account to install IBM Installation Manager and IBM Connections.
IBM Installation Manager presents three options for the type of deployment that you can install. For more information about these options, see the Deployment options topic.
The IBM Connections installation process supports the creation of new server instances and clusters. Do not use existing clusters to deploy IBM Connections.
You can install IBM Connections with either root or non-root accounts on AIX and Linux, or administrator or non-administrator accounts on Microsoft Windows. For more information, see the Installing as a non-root user topic.
Complete the Pre-installation tasks.
If you are migrating from IBM Connections 3.0.1, you need to complete only the following tasks:
- Install IBM WAS if you are installing on the same host as 3.0.1.
- Set up federated repositories
- Do not complete the Pre-installation tasks for creating DBs or populating the Profiles DB. The migration process handles those tasks separately.
Install IBM WAS Network Deployment (Application Server option) on each node. IBM Connections is installed on the system where WAS Deployment Manager is installed. For more information, see the Installing IBM WAS topic.
Back up the profile_root/Dmgr01 directory.
Configure WAS to communicate with the LDAP directory. For more information, see the Set up federated repositories topic.
Prepare directories to use as content stores. You need to provide shared content stores on network share devices and local content stores on each node. Both shared and local content stores must be accessible using the same path from all nodes and from the Deployment Manager.
Set the system clocks on the Deployment Manager and the nodes to within 1 minute of each other. If these system clocks are further than 1 minute apart, you might experience synchronization errors.

Copy the JDBC files for your DB type to the Deployment Manager (DM) and then from the DM to each node. Place the copied files in the same location on each node as their locations on the DM. If, for example, you copied the db2jcc.jar file from the C:\IBM\SQLLIB directory on the DM, place the copy in the C:\IBM\SQLLIB directory on each node.

JDBC files
Database type JDBC files
DB2
db2jcc.jar
db2jcc_license_cu.jar
Oracle
ojdbc6.jar
Ensure that you are using the latest version of the ojdbc6.jar file.
SQL Server
sqljdbc4.jar

If you are going to use a trusted SSL certificate, ensure that is available before you begin the installation.
If you do not plan to deploy IBM Cognos Business Intelligence now to support metrics, you can still install the Metrics application along with the other IBM Connections applications. This enables Connections to begin collecting event data immediately and store it in the Metrics DB for use when Cognos is available to provide reports.
(Microsoft Windows) You must use an administrator account to install IBM Connections on Windows. If you are installing on Windows Server 2008, you must use a local administrator account. If you use a domain administrator account, the installation might fail.
(Linux only) If you receive an error message after attempting to start IBM Installation Manager, you might need to install additional 32-bit libraries. For more information about required Linux libraries, see the Linux libraries topic. For more information about IBM Installation Manager errors, go to the Unable to install Installation Manager on RHEL 6.0/6.1 (64-bit) webpage.
(AIX and Linux) Ensure that the directory paths that you enter contain no spaces.
(AIX and Linux) Ensure that the Open File Descriptor limit is 8192. For information about setting the file limit, go to the Installation error messages topic and search for error code CLFRP0042E.
(AIX only) IBM Installation Manager requires additional libraries for the AIX operating system. For more information, go to the Required filesets on AIX for Installation Manager webpage.
(AIX only) If IBM Installation Manager hangs while being installed on your system, you might need to update your version of the software. For more information, read the IBM Installation Manager hangs on 64-bit AIX systems technote.
(AIX only) If you are downloading IBM Installation Manager, the TAR program available by default with AIX does not handle path lengths longer than 100 characters. To overcome this restriction, use the GNU file archiving program instead. This program is an open source package that IBM distributes through the AIX Toolbox for Linux Applications at the IBM AIX Toolbox website. Download and install the GNU-compatible TAR package. You do not need to install the RPM Package Manager because it is provided with AIX.
After installing the GNU-compatible compression program, change to the directory where you downloaded the IBM Connections tar file. Enter the following command to extract the files from the file:
gtar -xvf Lotus_Connections_wizard_aix.tar
This command creates a directory named after IBM Installation Manager.

Database type	JDBC files
DB2	db2jcc.jar db2jcc_license_cu.jar
Oracle	ojdbc6.jar Ensure that you are using the latest version of the ojdbc6.jar file.
SQL Server	sqljdbc4.jar

Tips:

Establish naming conventions for nodes, servers, clusters, and web servers.
Use a worksheet to record the UIDs, passwords, server names, and other information required during and after installation. For more information, see the Worksheet for installing IBM Connections topic.
Install and configuring IBM Connections is a complex process; not only should you read the instructions but you must also pay attention to the Before you begin prerequisites in each topic.

Linux libraries

The complete list of Linux libraries required for deploying IBM Connections 4.0.

Linux

Install the following Linux packages and libraries:

Ensure that the GTK library is available on your system. Even when you are installing on a 64-bit system, you still need the 32-bit version of the GTK library.

compat-libstdc++-33.x86_64

libcanberra-gtk2.i686

PackageKit-gtk-module

gtk2.i686

compat-libstdc++-33.i686

compat-libstdc++-296

compat-libstdc++

libXtst.i686

Cognos

If you plan to install Cognos, you also need the libraries listed in the Cognos BI 10.1.1 Software Environments - Required Patches technote.

Both 32-bit and 64-bit versions are required.

Install as a non-root user

Grant permissions to a non-root user to install IBM Connections.

Ensure that you complete all the prerequisite tasks that are relevant for your environment. For more information, see the Before installing topic. This task applies to the AIX and Linux operating systems only.

By default, only root users have the necessary permissions to install an IBM Connections deployment. On the AIX and Linux operating systems, you can permit non-root users to install the product by changing their permissions to access certain data directories. On the Windows operating system, the user must be a member of the administrator group.

The non-root user must be the same user who installed IBM WAS.

To grant the necessary permissions to a non-root user:

Unless it already exists, create the non-root user account to use to install IBM Connections.
If it does not already exist, create a home directory for the user.
Edit the install.ini file:
1. Open the install.ini file for editing from the following location:
  - AIX: IBM_Connections_set-up directory/IM/aix/install.ini
  - Linux: IBM_Connections_set-up directory/IM/linux/install.ini
  - Linux on System z: IBM_Connections_set-up directory/IM/zlinux/install.ini
2. In the second line of the file, change admin to nonadmin.
3. Save and close the file.

Open a command prompt and grant the appropriate permissions to the user by entering the commands shown in the following table:

AIX or Linux:

Use either the chmod or chown commands, depending on your security environment. Use the chown commands to grant permissions to a user and group but ensure that the group includes the user account that installed WAS.

Non-root user permissions
Directory Permissions chmod command chown command
app_server_root RWX chgrp -R non-root_user_group app_server_root chmod -R g+wrx app_server_root
where non-root_user_group is a user group that contains the non-root user account.
chown -R non-root_ID:group app_server_root
where non-root_ID is the non-root user account and group is the user group that contains this account.

IBM_ Connections set-up directory
RWX chgrp -R non-root_user_group IBM_Connections_set-up_directory chmod -R g+wrx IBM_Connections_set-up_directory chown -R non-root_ID:group IBM_connections_set-up_directory
connections_root RWX chgrp -R non-root_user_group connections_root chmod -R g+wrx connections_root chown -R non-root_ID:group connections_root
IM_root RWX chgrp -R non-root_user_group IM_root chmod -R g+wrx IM_root chown -R non-root_ID:group IM_root
shared_resources_root RWX chgrp -R non-root_user_group shared_resources_root chmod -R g+wrx shared_resources_root chown -R non-root_ID:group shared_resources_root

var/ibm/InstallationManager
RWX chmod -R ugo+rwx /var/ibm/InstallationManager
Grant permissions to this folder only if the root user installed IBM Installation Manager.
chown -R non-root_ID:group /var/ibm/InstallationManager

Install IBM Connections using either the wizard, the console, or a silent installation method.

Directory	Permissions	chmod command	chown command
app_server_root	RWX	chgrp -R non-root_user_group app_server_root chmod -R g+wrx app_server_root where non-root_user_group is a user group that contains the non-root user account.	chown -R non-root_ID:group app_server_root where non-root_ID is the non-root user account and group is the user group that contains this account.
IBM_ Connections set-up directory	RWX	chgrp -R non-root_user_group IBM_Connections_set-up_directory chmod -R g+wrx IBM_Connections_set-up_directory	chown -R non-root_ID:group IBM_connections_set-up_directory
connections_root	RWX	chgrp -R non-root_user_group connections_root chmod -R g+wrx connections_root	chown -R non-root_ID:group connections_root
IM_root	RWX	chgrp -R non-root_user_group IM_root chmod -R g+wrx IM_root	chown -R non-root_ID:group IM_root
shared_resources_root	RWX	chgrp -R non-root_user_group shared_resources_root chmod -R g+wrx shared_resources_root	chown -R non-root_ID:group shared_resources_root
var/ibm/InstallationManager	RWX	chmod -R ugo+rwx /var/ibm/InstallationManager Grant permissions to this folder only if the root user installed IBM Installation Manager.	chown -R non-root_ID:group /var/ibm/InstallationManager

Example

Grant permissions to a non-root user who wants to install an IBM Connections deployment on Linux.

Assumptions:

The app_server_root directory is /opt/IBM/Websphere/Appserver.
The IBM_Connections_set-up_directory directory is /opt/ConnectionsSetup.
The connections_root, IM_root, and shared_resources_root directories are subdirectories of the /opt/ConnectionsInstallation directory.
The non-root user account is a member of the ConnectionsInstallers group.

Procedure:

Create a non-root user account called ConnectionsInstaller.
Create a home directory for the new user account.
Add the new user account to the ConnectionsInstallers group.
Open a command prompt and enter the following commands:
1. chgrp -R ConnectionsInstallers /opt/IBM/Websphere/Appserver chmod -R g+wrx /opt/IBM/Websphere/Appserver chown -R ConnectionInstaller:ConnectionsInstallers /opt/IBM/Websphere/Appserver
2. chgrp -R ConnectionsInstallers /opt/ConnectionsSetup chmod -R g+wrx /opt/ConnectionsSetup chown -R ConnectionInstaller:ConnectionsInstallers /opt/IBM/Websphere/Appserver
3. chgrp -R ConnectionsInstallers /opt/ConnectionsInstallation chmod -R g+wrx /opt/ConnectionsInstallation chown -R ConnectionInstaller:ConnectionsInstallers /opt/IBM/Websphere/Appserver

Install IBM Connections 4.0

Install IBM Connections.

Ensure that you complete all the prerequisite tasks that are relevant for your environment. For more information, see the Before installing topic.

To install IBM Connections, run the IBM Installation Manager wizard on the system where the Deployment Manager is installed.

If an error occurs during installation, IBM Installation Manager cancels the installation and rolls back the installation files. Installation errors are usually caused by environment problems such as insufficient disk space, privilege issues, or corruption of a WebSphere profile. If your installation is canceled, complete the following steps:

Identify and resolve the error that caused the cancellation. After canceling the installation, IBM Installation Manager displays an error message with an error code. You can look up the error code in the Installation error messages topic or check the log files.
Restore the Deployment Manager profile from your backup.
Delete the connections_root directory.
Start this task again.

To install IBM Connections, complete the following steps:

On each node, stop any running instances of WAS and WebSphere node agents.
Start WAS Network Deployment Manager.
Copy the installation files to the system hosting the Deployment Manager.
Ensure that the directory path that you enter contains no spaces.
From the Connections setup directory, run the file to start the IBM Connections launchpad:
- AIX or Linux: Connections set-up/launchpad.sh
- Windows: Connections set-up\launchpad.exe
The launchpad needs a web browser to run. If your system does not have a web browser, take one of the following actions:
- Install a web browser.
- Install IBM Connections in silent mode. For more information, see the Installing silently topic.
- Start IBM Installation Manager manually:
  1. Open a command prompt.
  2. Change to the Connections_install/IM/OS directory, where OS is your operating system.
  3. Enter ./install.sh -input response.xml.
Click Install IBM Connections 4.0 and then click Launch the IBM Connections 4.0 install wizard.
Click the links to Documentation, Pre-installation tasks, or Post-installation tasks to view the product documentation.
In the Select packages to install window, select the packages to install and click Next to continue.
Accept the default setting for Show all versions.
If you are using an earlier version of IBM Installation Manager than 1.4.4, the 1.4.4 package is selected in this window.
Click Check for Other Versions and Extensions to search for updates to IBM Installation Manager.
Review and accept the license agreement by clicking I accept the terms in the license agreements. Click Next.
Set the location of shared directories for IBM Installation Manager.
1. Set the location of the Shared Resources Directory.
2. Set the location of the Installation Manager Directory. This option appears only if you have not previously installed IBM Installation Manager.
3. Click Next.
The Shared Resources directory stores resources that can be shared by multiple packages. If you used IBM Installation Manager before, the wizard automatically enters this value.
The Installation Manager directory stores resources that are unique to the packages that you are installing.
Choose to Use the existing package group or Create a new package group.
If you are using the wizard for the first time, the Use the existing package group option is not available.
Set the location of the installation directory for IBM Connections. You can accept the default directory location, enter a new directory name, or click Browse to select an existing directory. Click Next.

Confirm the applications to install and click Next. You can select from the following options:

The wizard always installs the Home page, News, and Search applications.
To use media gallery widgets in the Communities application, you must install the Files application. Media gallery widgets store photo and video files in the Files DB.
Even if you are not configuring Cognos yet, install Metrics now so that your application data is captured from the moment that IBM Connections is deployed. Metrics captures your deployment data whereas Cognos is used for viewing data reports. If you install Metrics at a later stage, you will not have any data reports for the period before you installed Metrics.

Option Description
IBM Connections 4.0 Install all IBM Connections applications.
Activities Collaborate with colleagues.
Blogs Write personal perspectives about projects.
Communities Interact with people on shared projects.
Bookmarks Bookmark important websites.
Files Share files among users.
Forums Discuss projects and exchange information.
Metrics Identify and analyze usage and trends.
Mobile Access IBM Connections from mobile devices.
Moderation Forum and community owners can moderate the content of forums.
Profiles Find people in the organization.
Wikis Create content for your website.

Enter the details of your WAS environment:
1. Select the WAS installation location that contains the Deployment Manager.
  Note the default path to the WAS installation:
  - AIX: /usr/IBM/WebSphere/AppServer
  - Linux: /opt/IBM/WebSphere/AppServer
  - Windows: C:\Program Files\IBM\WebSphere\AppServer
2. Enter the properties of the WAS Deployment Manager (DM):
  
  Deployment Manager profile
  
  Name of the DM to use for IBM Connections. The wizard automatically detects any available DMs.
  
  Host name
  
  Name of the host DM server.
  
  Administrator ID
  
  The administrative ID of the DM.
  This ID is set to the connectionsAdmin J2C authentication alias, which is mapped to the following J2EE roles: dsx-admin, widget-admin, and search-admin. It is also used by the service integration bus. To use security management software such as Tivoli Access Manager or SiteMinder, the ID that you specify here must exist in the LDAP directory. For more information, see the Switching to unique administrator IDs for system level communication topic.
  
  Administrator Password
  
  The password for the administrative ID of the DM.
  
  SOAP port
  
  The SOAP port of the DM. The wizard automatically detects this value.
3. Click Validate to verify the DM information that you entered and that application security is enabled on WAS. If the verification fails, IBM Installation Manager displays an error message.
  (AIX and Linux) The validation process checks the number of open files that are supported by your system. If the value for this parameter, known as the Open File Descriptor limit, is too low, a file open error, memory allocation failure, or connection establishment error could occur. If one of these errors occurs, exit the installation wizard and increase the open file limit before restarting the wizard. To set the file limit, go to the Installation error messages topic and search for error code CLFRP0042E. The recommended value for IBM Connections is 8192. For more information about the Open File Descriptor limit, see the documentation for your operating system.
4. When the verification test is successful, click Next.
The wizard creates a dmInfo.properties file under WAS to record details of the cell, node, and server.
Configure your topology. For more information about each option, see the Deployment options topic.

If you return to this page from a later page in the installation wizard, your settings are still present but not visible. If you want to change any settings, you must enter all of the information again. If you do not want to change your initial settings, click Next.
- Small deployment:
  1. Select the Small deployment topology.
  2. Enter a Cluster name for the topology.
  3. Select a Node.
  4. Click Next.
- Medium deployment:
  1. Select the Medium deployment topology.
  2. Select the default value or enter a Cluster name for each application or for groups of applications.
    For example, use Cluster1 for Activities, Communities, and Forums.
    IBM Installation Manager creates servers and clusters when required.
  3. Select a Node for each cluster. Accept the predefined node or select a different node.
    These nodes host application server instances that serve IBM Connections applications. You can assign multiple nodes to a cluster, where each node is a server member of that cluster.
  4. Enter a Server member name for the selected node. Choose the default or enter a custom name.
    If you enter a custom server member name, the name must be unique across all nodes in your deployment.
  5. Click Next.
- Large deployment:
  1. Select the Large deployment topology.
  2. Enter a Cluster name for each application.
    IBM Installation Manager creates servers and clusters when required.
  3. Select a Node for each cluster. Accept the predefined node or select a different node.
    These nodes host application server instances that serve IBM Connections applications. You can assign multiple nodes to a cluster, where each node is a server member of that cluster.
  4. Enter a Server member name for the selected node. Choose the default or enter a custom name.
    If you enter a custom server member name, the name must be unique across all nodes in your deployment.
  5. Click Next.
Enter the DB information:

If you return to this page from a later page in the installation wizard, your settings are still present but not visible. If you want to change any settings, you must enter all of the information again. If you do not want to change your initial settings, click Next.
1. Specify whether the installed applications use the same DB server or instance: Select Yes or No.
  If allowed by your DB configuration, you can select multiple DB instances as well as different DB servers.
2. Select a Database type from one of the following options:
  - IBM DB2 Universal Database.
  - Oracle Enterprise Edition
  - Microsoft SQL Server Enterprise Edition
3. Enter the Database server host. For example: appserver.enterprise.example.com
  If your installed applications use different DB servers, enter the DB host for each application.
4. Enter the Port number of the DB server. The default values are: 50000 for DB2, 1521 for Oracle, and 1433 for SQL Server.
  If your installed applications use different DB servers or instances, enter the port for each DB server or instance.
5. Enter the JDBC driver location. For example:
  - AIX: /usr/IBM/WebSphere/AppServer/lib
  - Linux:
    /opt/IBM/WebSphere/AppServer/lib
  - Windows:
    C:\IBM\WebSphere\Appserver\lib
6. Ensure that the following JDBC driver libraries are present in the JDBC directory:
  
  DB2
  
  db2jcc.jar and db2jcc_license_cu.jar
  Ensure that your user account has the necessary permissions to access the DB2 JDBC files.
  
  Oracle
  
  ojdbc6.jar
  
  SQL Server
  
  Download the SQL Server JDBC 2 driver from the Microsoft website to a local directory and enter that directory name in the JDBC driver library field.
  The directory must not contain the sqljdbc.jar file, only the sqljdbc4.jar file. Even though the data source is configured to use the sqljdbc4.jar file, an exception occurs if both files are present in the same directory.
  IBM recommends that you obtain this Microsoft hotfix for the JDBC 2 driver for production deployments.
7. Enter the User ID and Password for each DB. If each DB uses the same user credentials, select the Use the same password for all applications check box and then enter the UID and password for the first DB in the list.
  
  If your DB type is Oracle, connect to the DB with the UID that you used when you created the application DB.
8. Click Validate to verify your DB settings. If the validation fails, check your DB settings. When the validation succeeds, click Next.
  IBM Installation Manager tests your DB connection with the DB values that you supplied. You can change the DB configuration later in the WAS Integrated Solutions Console.

Option	Description
IBM Connections 4.0	Install all IBM Connections applications.
Activities	Collaborate with colleagues.
Blogs	Write personal perspectives about projects.
Communities	Interact with people on shared projects.
Bookmarks	Bookmark important websites.
Files	Share files among users.
Forums	Discuss projects and exchange information.
Metrics	Identify and analyze usage and trends.
Mobile	Access IBM Connections from mobile devices.
Moderation	Forum and community owners can moderate the content of forums.
Profiles	Find people in the organization.
Wikis	Create content for your website.

Specify your Cognos configuration details as explained in the table, and then click Validate to verify your connection.

The IBM Cognos configuration panel appears only if you chose to install the Metrics application earlier in this task.
Ensure that Cognos Business Intelligence Server is running because the wizard pings the server during the validation process.
If you do not want to deploy Cognos now, enter dummy values for UID and password, click Load node info, and then click Validate. Ignore the error message that appears. To continue installing IBM Connections, click Next. For information about deploying Cognos, see the Installing Cognos Business Intelligence topic. For information about resolving Cognos validation problems, see the Troubleshooting Cognos validation problems topic.

Option Description
Administrator UID Set the user name of the administrator account that you selected for Cognos Business Intelligence. This user must be included in the LDAP directory used with Connections.
Administrator password Set the password for the Cognos administrator.
Name Click the Load node info button to retrieve the list of available nodes and profiles, then click the arrow and select the WebSphere profile that hosts the Cognos BI server. The profile you select here must match the profile you specified as the was.profile.name in the cognos-setup.properties file.

Host name

This is a non-editable field that is populated when you select a profile in the Name field. Seeing the associated host for each profile/node can help you choose the correct node where the Cognos BI Server is running.
Server name There might be multiple servers installed on the same computer as the Cognos BI server; click the arrow and select the instance that represents the Cognos server. Must match what you specified as the cognos.was.server.name in the cognos-setup.properties file.
Tip: A default value of cognos_server was assigned in the properties file, so unless you changed that value, use it now.
Port Set the number of the port that the Cognos BI Server is listening on; this defaults to port 9080 but might have been changed. You can determine the port by checking the WC_defaulthost value in the following file: WAS_install_root/config/cells/Cell_Name/nodes/Node_Name/serverindex.xml; for example on Windows:
C:\IBM\WebSphere\AppServer\profiles\AppSvr01\config\cells\lc40Cell01\nodes\lc40CellManager01\serverindex.xml

Web context root The context root determines which requests will be delegated to the Cognos application for processing (any request beginning with this string will be handled by Cognos). Must match the cognos.contextroot specified in the cognos-setup.properties file.
Tip: A default value of cognos was assigned in the properties file, so unless you changed that value, use it now.

Option	Description
Administrator UID	Set the user name of the administrator account that you selected for Cognos Business Intelligence. This user must be included in the LDAP directory used with Connections.
Administrator password	Set the password for the Cognos administrator.
Name	Click the Load node info button to retrieve the list of available nodes and profiles, then click the arrow and select the WebSphere profile that hosts the Cognos BI server. The profile you select here must match the profile you specified as the was.profile.name in the cognos-setup.properties file.
Host name	This is a non-editable field that is populated when you select a profile in the Name field. Seeing the associated host for each profile/node can help you choose the correct node where the Cognos BI Server is running.
Server name	There might be multiple servers installed on the same computer as the Cognos BI server; click the arrow and select the instance that represents the Cognos server. Must match what you specified as the cognos.was.server.name in the cognos-setup.properties file. Tip: A default value of cognos_server was assigned in the properties file, so unless you changed that value, use it now.
Port	Set the number of the port that the Cognos BI Server is listening on; this defaults to port 9080 but might have been changed. You can determine the port by checking the WC_defaulthost value in the following file: WAS_install_root/config/cells/Cell_Name/nodes/Node_Name/serverindex.xml; for example on Windows: C:\IBM\WebSphere\AppServer\profiles\AppSvr01\config\cells\lc40Cell01\nodes\lc40CellManager01\serverindex.xml
Web context root	The context root determines which requests will be delegated to the Cognos application for processing (any request beginning with this string will be handled by Cognos). Must match the cognos.contextroot specified in the cognos-setup.properties file. Tip: A default value of cognos was assigned in the properties file, so unless you changed that value, use it now.

If you deployed Cognos Business Intelligence and the validation fails at this point, you can click Next and continue installing IBM Connections. After the installation is complete, you can correct the validation issue as explained in the topic, Troubleshooting Cognos validation problems.

Set the locations of the content stores. All nodes in a cluster must have read-write access to shared content. Both shared and local content stores must be accessible using the same path from all nodes and from the DM. Each content store is represented by a corresponding WebSphere variable that is further defined as shared or local. Local content is node-specific.
If you are migrating from IBM Connections 3.0.1, you can reuse your existing content stores in 4.0. For more information, see the Content store migration topic.
1. Enter the location of the Shared content store. The shared content store usually resides in a shared repository that grants read-write access to the DM and all the nodes. Use one of the following methods to create a shared data directory:
  - Network-based file shares (for example: NFS, SMB/Samba, and so on)
  - Storage area network drives (SAN)
  - If you are using a shared-file system on Microsoft Windows, specify the file location using the Universal Naming Convention (UNC) format. For example: \\server_name\share_name.
    (Windows only) If you use Remote Desktop Connection to map shared folder drives, ensure that you use the same session to start the node agents. Otherwise, the shared drives might be invisible to the nodes.
2. Enter the location of the Local content store.
3. Click Validate to verify that the account that you are using to install IBM Connections has write access to the content store.
4. Click Next.
Select a Notification solution. Notifications are email messages to users about new information and events in your IBM Connections deployment.
- Enable Notification only.
  Use notifications but without the ReplyTo capability.
- Enable Notification and ReplyTo.
  Use notifications and the ReplyTo capability. To use ReplyTo, your mail server must be able to receive all the replies and funnel these replies into a single inbox. IBM Connection connects to the mail server using the IMAP protocol.
- None.
  Do not use a notification solution in your IBM Connections deployment. You can configure notifications after installation.
Select and specify a mail server solution and then click Next.
- WebSphere Java Mail Session: Use a single mail server for all notifications. Select this option if you can access an SMTP server directly using the host.
  Complete the following fields to identify the mail server to use for sending email:
  
  Host name of SMTP messaging server
  
  Enter the host or IP address of the preferred SMTP mail server.
  
  This SMTP server requires authentication
  
  Select the check box to force authentication when mail is sent from this server.
  
  User ID
  
  If the SMTP server requires authentication, enter the UID.
  
  Password
  
  If the SMTP server requires authentication, enter the user password.
  
  Encrypt outgoing mail traffic to the SMTP messaging server using SSL
  
  Select this check box if you want to encrypt outgoing mail to the SMTP server.
  
  Port
  
  Accept the default port of 25, or enter port 465 if you are using SSL.
- DNS MX Records: Use information from DNS to determine which mail servers to use. Select this option if you use a Domain Name System (DNS) server to access the SMTP messaging server.
  
  Messaging domain name
  
  Enter the name or IP address of the messaging domain.
  
  Choose a specific DNS server
  
  Select this check box if you want to specify a unique SMTP server.
  
  DNS server for the messaging servers query
  
  Enter the host or IP address of the DNS server.
  
  DNS port used for the messaging servers query
  
  Enter the port that is used for sending queries using the messaging server.
  
  This SMTP server requires authentication
  
  Select the check box to force authentication when notification mail is sent from this server.
  
  User ID
  
  If SMTP authentication is required, enter the administrator user ID for the SMTP server.
  
  Password
  
  If SMTP authentication is required, enter the password for the administrator user of the SMTP server.
  
  Encrypt outgoing mail traffic to the SMTP messaging server using SSL
  
  Select the check box if you want to use the Secure Sockets Layer (SSL) when connecting to the SMTP server.
  
  Port
  
  Set the port to use for the SMTP server connection. The default port for the SMTP protocol is 25. The default port number for SMTP over SSL is 465.
- If you click Do not enable Notification, IBM Installation Manager skips the rest of this step. You can configure notification later.
If you selected the Notification and ReplyTo option, configure the ReplyTo email settings. IBM Connections uses a unique ReplyTo address to identify both the person who replied to a notification and the event or item that triggered the notification.
1. Enter a domain name. For example: mail.example.com.
  This domain name is used to build the ReplyTo address. The address consists of the suffix or prefix, a unique key, and the domain name.
2. The reply email address is given a unique ID by the system. You can customize the address by adding a prefix or suffix, using a maximum of 28 characters. This extra information is useful if the domain name is already in use for other purposes. Select one of the following options:
  
  None
  
  Use the ID generated by the system.
  
  Prefix
  
  Enter a prefix in the Example field.
  
  Suffix
  
  Enter a suffix in the Example field.
  
  As you select an option, the wizard creates an example of the address, combining your selection with the ID generated by the system.
  For example:
  - unique_id@domain
  - prefix_unique_id@domain
  - unique_id_suffix@domain -
3. Specify the details of the mail file to which ReplyTo emails are sent:
  
  Server
  
  The domain where your mail server is located. For example: replyTo.mail.example.com.
  
  User ID
  
  The user account for the mail server. The UID and password are credentials that IBM Connections will use to poll the inbox on the mail server to retrieve the replies and process the content. IBM Connections connects to the mail server using IMAP.
  
  Password
  
  Password for the user account. The UID and password are credentials that IBM Connections will use to poll the inbox on the mail server to retrieve the replies and process the content. IBM Connections connects to the mail server using IMAP.
4. Click Next.
You can modify the ReplyTo settings after installation. To edit the domain name and prefix or suffix, edit the news-config.xml file. For more information, see the Post-migration step for status updates topic. To edit the server and authentication details, log in to the WAS Integrated Solutions Console and navigate to the Mail Sessions page, where you can edit the configuration.
Review the information that you have entered. To revise your selections, click Back. To finalize the installation, click Next.
Review the result of the installation. Click Finish to exit the installation wizard.
Restart the Deployment Manager:
- AIX or Linux: Open a command prompt and change to the profile_root/Dmgr01/bin directory. Enter the ./stopManager.sh command and then enter the ./startManager.sh command.
- Windows: Stop and restart the Deployment Manager service.
Start all the federated nodes and enter the startNode command. Repeat these steps for each node:
1. Log in to a node.
2. From a command line, change to the profile_root/bin directory.
3. Enter the startNode command for your operating system:
  - AIX or Linux: ./startNode.sh
  - Windows: startNode.bat
Log in to the Integrated Solutions Console on the DM to perform a full synchronization of all nodes.
1. Go to System administration > Nodes.
2. Select the nodes and click Full Resynchronize.
Wait until the DM copies all the application EAR files to the installedApps directory on each of the nodes. This process can take up to 30 minutes.
To verify that the DM has distributed the application EAR files to the nodes, check the SystemOut.log file of each node agent. The default path to the SystemOut.log file on a node is profile_root/logs/nodeagent.
Look for a message such as the following example: ADMA7021I: Distribution of application application_name completed successfully. where application_name is the name of an IBM Connections application.
Restart the Deployment Manager.
Start all your IBM Connections clusters:
1. Log in to the Integrated Solutions Console on the DM
2. Go to Servers > Clusters > WebSphere Application server clusters.
3. Select the IBM Connections clusters and click Start.
If you installed a cluster with multiple Search nodes, create the initial index. For more information about creating the Search index, see the Creating the initial Search index topic.
1. The index is ready when the INDEX.READY and CRAWLING_VERSION files are present in the index directory.
If some applications do not start, the file-copying process might not have completed. Wait a few minutes and start the applications.

Results

The installation wizard has installed IBM Connections in a network deployment.

To confirm that the installation was successful, open the log files in connections_root/logs. Each IBM Connections application installed has a log file, using the following naming format: application_nameInstall.log, where application_name is the name of an IBM Connections application. Search for the words error or exception to check whether any errors or exceptions occurred during installation.

To view the log file for system events that occurred during the installation, open the date_time.xml file, where date_time represents the date and time of the installation. The file is located by default in the following directory:

AIX or Linux (root user): /var/ibm/InstallationManager/logs
AIX or Linux (non-root user): /home/user/var/ibm/Installation Manager/logs where user is the non-root user name
Windows Server 2008 64-bit: C:\ProgramData\IBM\Installation Manager\logs

What to do next

Complete the post-installation tasks that are relevant to your installation. For more information, see the Post-installation tasks topic.

Access network shares:

If you installed WAS on Microsoft Windows and configured it to run as a service, ensure that you can access network shares. For more information, see the Accessing Windows network shares topic.

Install in console mode

Install IBM Connections in console mode. This method is convenient if you cannot or do not want to use the graphical mode.

Ensure that you complete all the prerequisite tasks that are relevant for your environment. For more information, see the Before installing topic. Use console mode to complete the installation process in a non-graphical environment. This mode is useful when you have to install IBM Connections on a system that does not have a video card.

In steps where you enter custom information, such as server details, you can type P at any time to return to the previous input choice in that step. However, you cannot type P to return to a previous step.

To install IBM Connections, you need to use IBM Installation Manager, which manages the installation process.

To install IBM Connections in console mode, complete the following steps:

On each node, stop any running instances of WAS and WebSphere node agents.
Start WAS Network Deployment Manager.
Copy the installation files to the system hosting the Deployment Manager.
Ensure that the directory path that you enter contains no spaces.
Start IBM Installation Manager in console mode:
Run IBM Installation Manager on the system where the Deployment Manager is installed.
- If Installation Manager is already installed, open a command prompt and change to the IBM Installation Manager installation directory. Then run the following command:
  - AIX or Linux: /opt/IBM/InstallationManager/eclipse/tools/imcl -c
  - Windows: \Program Files\IBM\Installation Manager\eclipse\tools\imcl.exe -c
- To install both IBM Installation Manager and IBM Connections, open a command prompt and change to the IBM Installation Manager installation directory. Then run the following command:
  - AIX: Lotus_Connections_Install/IM/aix/install.console.sh
  - Linux: Lotus_Connections_Install/IM/linux/install.console.sh
  - Windows: Lotus_Connections_Install\IM\windows\install.console.bat
  The batch script calls a response file which contains information about the repositories for both IBM Installation Manager and IBM Connections.
- To use another language for the installation process, open a command prompt, change to the IBM Installation Manager installation directory, and run the following command:
  - AIX: Lotus_Connections_Install/IM/aix/tools/imcl -c -nl language_code
  - Linux: Lotus_Connections_Install/IM/linux/tools/imcl -c -nl language_code
  - Windows: \Program Lotus_Connections_Install\IM\windows\tools\imcl.exe -c -nl language_code
  where language_code is the two-letter code for a language, such as fr for French.
In the console window, specify the IBM Connections repository:
If you chose the option to run the install.console.bat|sh file in Step 4, you can skip this step.
1. Type P to edit preferences.
2. Type 1 to specify repositories.
3. Type D to add a repository.
4. Set the repository path for IBM Connections 4.0, for example: Lotus_Connections/repository.xml.
5. Type A to save the repository information.
6. Type C to return to the console window.
In the Select packages to install step, type 1 to select the package and then type N to proceed.
Review the license agreement by typing the appropriate number to view license information. To accept the license agreement, type A. Type N to proceed.
Set the location of the shared resources directory for IBM Installation Manager.
1. Enter the location of the Shared Resources Directory.
2. Type N to proceed.
The Shared Resources directory stores resources that can be shared by multiple packages. If you used IBM Installation Manager before, the wizard automatically enters this value.
Ensure that the directory path that you enter contains no spaces.
Set the location of the IBM Installation Manager installation directory.
1. Enter the location of the Installation Manager Directory.
2. Type N to proceed.
This option is available only if you have not previously installed IBM Installation Manager.
The Installation Manager directory stores resources that are unique to the packages that you are installing.
Ensure that the directory path that you enter contains no spaces.
Set the locations of the package group for IBM Installation Manager and the installation directory for IBM Connections:
1. The wizard automatically detects the IBM Connections package group. Type M to change the default location where the package group will be installed.
2. Type N to proceed.
3. To accept the default location for the IBM Connections installation directory, type N. To specify a new directory name, type M and enter the new directory name and path.
4. Type N to proceed.

Select the applications to install and then type N to proceed. You can select from the following options:

The wizard always installs the Home page, News, and Search applications.
If you clear the selections of the Home page, News, or Search applications, the wizard will exit.
To use media gallery widgets in the Communities application, you must install the Files application. Media gallery widgets store photo and video files in the Files DB.
Even if you are not configuring Cognos yet, install Metrics now so that your application data is captured from the moment that IBM Connections is deployed. Metrics captures your deployment data whereas Cognos is used for viewing data reports. If you install Metrics at a later stage, you will not have any data reports for the period before you installed Metrics.

Enter the details of your WAS environment:
1. Select the WAS installation location that contains the Deployment Manager.
  Note the default path to the WAS installation:
  - AIX: /usr/IBM/WebSphere/AppServer
  - Linux: /opt/IBM/WebSphere/AppServer
  - Windows: C:\Program Files\IBM\WebSphere\AppServer
2. Enter the properties of the WAS Deployment Manager (DM):
  
  Deployment Manager profile
  
  Name of the DM to use for IBM Connections. The wizard automatically detects any available DMs.
  
  Host name
  
  Name of the host DM server.
  
  Administrator ID
  
  The administrative ID of the DM.
  This ID is set to the connectionsAdmin J2C authentication alias, which is mapped to the following J2EE roles: dsx-admin, widget-admin, and search-admin. It is also used by the service integration bus. To use security management software such as Tivoli Access Manager or SiteMinder, the ID that you specify here must exist in the LDAP directory. For more information, see the Switching to unique administrator IDs for system level communication topic.
  
  Administrator Password
  
  The password for the administrative ID of the DM.
  
  SOAP port
  
  The SOAP port of the DM. The wizard automatically detects this value.
3. Press Enter to verify the DM information that you entered. The verification process also checks that application security is enabled on WAS. If the verification fails, IBM Installation Manager displays an error message.
  (AIX and Linux) The validation process checks the number of open files that are supported by your system. If the value for this parameter, known as the Open File Descriptor limit, is too low, a file open error, memory allocation failure, or connection establishment error could occur. If one of these errors occurs, exit the installation wizard and increase the open file limit before restarting the wizard. To set the file limit, go to the Installation error messages topic and search for error code CLFRP0042E. The recommended value for IBM Connections is 8192. For more information about the Open File Descriptor limit, see the documentation for your operating system.
4. If the verification check is successful, type N to proceed. If verification fails, press B to re-enter the required information.
The wizard creates a dmInfo.properties file under WAS to record details of the cell, node, and server.
Configure your topology. For more information about each option, see the Deployment options topic.
- Small deployment:
  1. Type 1 to select the Small deployment topology.
  2. Enter a Cluster name for the topology.
  3. Select a Node.
  4. Enter a Server member name for the node.
  5. Type N to proceed.
- Medium deployment:
  1. Type 2 to select the Medium deployment topology.
  2. Select the default value or enter a Cluster name for each application or for groups of applications.
    For example, use Cluster1 for Activities, Communities, and Forums.
    IBM Installation Manager creates servers and clusters when required.
  3. Select a Node for each cluster. Accept the predefined node or select a different node.
    These nodes host application server instances that serve IBM Connections applications. You can assign multiple nodes to a cluster, where each node is a server member of that cluster.
  4. Enter a Server member name for the selected node. Choose the default or enter a custom name.
    If you enter a custom server member name, the name must be unique across all nodes in your deployment.
  5. The topology specified is displayed. To re-specify any details, type the number that corresponds to the application; for example, type 1 for Activities.
  6. Type N to proceed.
- Large deployment:
  1. Type 3 to select the Large deployment topology.
  2. Enter a Cluster name for each application.
    IBM Installation Manager creates servers and clusters when required.
  3. Select a Node for each cluster. Accept the predefined node or select a different node.
    These nodes host application server instances that serve IBM Connections applications. You can assign multiple nodes to a cluster, where each node is a server member of that cluster.
  4. Enter a Server member name for the selected node. Choose the default or enter a custom name.
    If you enter a custom server member name, the name must be unique across all nodes in your deployment.
  5. The topology specified is displayed. To re-specify any details, type the number that corresponds to the application; for example, type 1 for Activities.
  6. Type N to proceed.
Enter the DB information:
1. Specify whether the installed applications use the same DB server or instance: Type 1 to specify that the applications use same DB server or instance; type 2 to specify that they use different DB servers or instances.
  If allowed by your DB configuration, you can select multiple DB instances as well as different DB servers.
2. Select a Database type from one of the following options:
  - IBM DB2 Universal Database
  - Oracle Enterprise Edition
  - Microsoft SQL Server Enterprise Edition
3. Enter the Database server host. For example: appserver.enterprise.example.com
  If your installed applications use different DB servers, enter the DB host for each application.
4. Enter the Port number of the DB server. The default values are: 50000 for DB2, 1521 for Oracle, and 1433 for SQL Server.
  If your installed applications use different DB servers or instances, enter the port for each DB server or instance.
5. Enter the JDBC driver location. For example:
  - AIX: /usr/IBM/WebSphere/AppServer/lib
  - Linux:
    /opt/IBM/WebSphere/AppServer/lib
  - Windows:
    C:\IBM\WebSphere\Appserver\lib
6. Ensure that the following JDBC driver libraries are present in the JDBC directory:
  
  DB2
  
  db2jcc.jar and db2jcc_license_cu.jar
  Ensure that your user account has the necessary permissions to access the DB2 JDBC files.
  
  Oracle
  
  ojdbc6.jar
  
  SQL Server
  
  Download the SQL Server JDBC 2 driver from the Microsoft website to a local directory and enter that directory name in the JDBC driver library field.
  The directory must not contain the sqljdbc.jar file, only the sqljdbc4.jar file. Even though the data source is configured to use the sqljdbc4.jar file, an exception occurs if both files are present in the same directory.
  IBM recommends that you obtain this Microsoft hotfix for the JDBC 2 driver for production deployments.
7. Enter the User ID and Password for each DB. If each DB uses the same user credentials, confirm the Use the same password for all applications question and then enter the UID and password for the first DB in the list.
  
  If your DB type is Oracle, connect to the DB with the UID that you used when you created the application DB.
8. If you need to make changes, type the number that corresponds to the application to change. Alternatively, type R to reset all the DB specifications to their default values.
9. Press Enter to verify your DB settings. If the validation fails, check your DB settings. When the validation succeeds, click Next.
  IBM Installation Manager tests your DB connection with the DB values that you supplied. You can change the DB configuration later in the WAS Integrated Solutions Console.
10. If the verification check is successful, type N to proceed. If verification fails, press B to re-enter the required information.
Specify your Cognos configuration.
The IBM Cognos configuration panel appears only if you chose to install the Metrics application earlier in this task.
If you do not want to configure Cognos now, enter dummy values for UID and password, and select any values from the list of nodes and servers. Then press Enter and ignore the validation error message that appears. To continue installing IBM Connections, type N. For information about configuring Cognos after installation, see the Installing Cognos Business Intelligence topic. For information about resolving Cognos validation problems, see the Troubleshooting Cognos validation problems topic.
1. Enter the LDAP UID for the Cognos administrator.
2. Enter the password for the Cognos administrator.
3. Select the node where the Cognos BI Server is installed.
4. Enter the port of the Cognos server.
5. Enter the web context root.
6. Press Enter to validate the configuration.
7. Type N to proceed.
Set the locations of the content stores. Shared content must be read/write accessible by all nodes in a cluster. Both shared and local content stores must be accessible using the same path from all nodes and the DM. Local content is node-specific. Each content store is represented by a corresponding WebSphere variable that is further defined as shared or local.
If you are migrating from IBM Connections 3.0.1, you can reuse your existing content stores in 4.0. For more information, see the Content store migration topic.
1. Enter the location of the Shared content store. The shared content store usually resides in a shared repository that grants read-write access to the DM and all the nodes. Use one of the following methods to create a shared data directory:
  - Network-based file shares (for example: NFS, SMB/Samba, and so on)
  - Storage area network drives (SAN)
  - If you are using a shared-file system on Microsoft Windows, specify the file location using the Universal Naming Convention (UNC) format. For example: \\server_name\share_name.
    (Windows only) If you use Remote Desktop Connection to map shared folder drives, ensure that you use the same session to start the node agents. Otherwise, the shared drives might be invisible to the nodes.
2. Enter the location of the Local content store.
3. Press Enter to verify that the account that you are using to install IBM Connections has write access to the content store.
4. Click Next.
Select a Notification solution. Notifications are email messages to users about new information and events in your IBM Connections deployment.
- Enable Notification only.
  Use notifications but without the ReplyTo capability.
- Enable Notification and ReplyTo.
  Use notifications and the ReplyTo capability. To use ReplyTo, your mail server must be able to receive all the replies and funnel these replies into a single inbox. IBM Connection connects to the mail server using the IMAP protocol.
- None.
  Do not use a notification solution in your IBM Connections deployment. You can configure notifications after installation.
If you chose a mail notification option, select and specify a mail server solution.
- WebSphere Java Mail Session: Use a single mail server for all notifications. Select this option if you can access an SMTP server directly using the host.
  Identify the mail server to use for sending email:
  
  Host name of SMTP messaging server
  
  Enter the host or IP address of the preferred SMTP mail server.
  
  This SMTP server requires authentication
  
  Enter Y to force authentication when mail is sent from this server.
  
  User ID
  
  If the SMTP server requires authentication, enter the UID.
  
  Password
  
  If the SMTP server requires authentication, enter the user password.
  
  Encrypt outgoing mail traffic to the SMTP messaging server using SSL
  
  If you want to encrypt outgoing mail to the SMTP server, press Y.
  
  Port
  
  Press Enter to accept the default port of 25, or enter 465 if you are using SSL.
- DNS MX Records: Use information from DNS to determine which mail servers to use. Select this option if you use a Domain Name System (DNS) server to access the SMTP messaging server.
  
  Messaging domain name
  
  Enter the name or IP address of the messaging domain.
  
  Choose a specific DNS server
  
  To specify a unique SMTP server, press Y.
  
  DNS server for the messaging servers query
  
  Enter the host or IP address of the DNS server.
  
  DNS port used for the messaging servers query
  
  Enter the port that is used for sending queries using the messaging server.
  
  This SMTP server requires authentication
  
  Enter Y to force authentication when mail is sent from this server.
  
  User ID
  
  If SMTP authentication is required, enter the administrator user ID for the SMTP server.
  
  Password
  
  If SMTP authentication is required, enter the password for the administrator user of the SMTP server.
  
  Encrypt outgoing mail traffic to the SMTP messaging server using SSL
  
  If you want to encrypt outgoing mail to the SMTP server, press Y.
  
  Port
  
  Press Enter to accept the default port of 25, or enter 465 if you are using SSL.
- If you specify Do not enable Notification, IBM Installation Manager skips the rest of this step. You can configure notification later.
If you selected the Notification and ReplyTo option, configure the ReplyTo email settings. IBM Connections uses a unique ReplyTo address to identify both the person who replied to a notification and the event or item that triggered the notification.
1. Enter a domain name. For example: mail.example.com.
  This domain name is used to build the ReplyTo address. The address consists of the suffix or prefix, a unique key, and the domain name.
2. The reply email address is given a unique ID by the system. You can customize the address by adding a prefix or suffix, using a maximum of 28 characters. This extra information is useful if the domain name is already in use for other purposes. Select one of the following options:
  
  None
  
  Use the ID generated by the system.
  
  Prefix
  
  Enter a prefix in the Example field.
  
  Suffix
  
  Enter a suffix in the Example field.
  
  As you select an option, the wizard creates an example of the address, combining your selection with the ID generated by the system.
  For example:
  - unique_id@domain
  - prefix_unique_id@domain
  - unique_id_suffix@domain -
3. Specify the details of the mail file to which ReplyTo emails are sent:
  
  Server
  
  The domain where your mail server is located. For example: replyTo.mail.example.com.
  
  User ID
  
  The user account for the mail server. The UID and password are credentials that IBM Connections will use to poll the inbox on the mail server to retrieve the replies and process the content. IBM Connections connects to the mail server using IMAP.
  
  Password
  
  Password for the user account. The UID and password are credentials that IBM Connections will use to poll the inbox on the mail server to retrieve the replies and process the content. IBM Connections connects to the mail server using IMAP.
4. Click Next.
You can modify the ReplyTo settings after installation. To edit the domain name and prefix or suffix, edit the news-config.xml file. For more information, see the Post-migration step for status updates topic. To edit the server and authentication details, log in to the WAS Integrated Solutions Console and navigate to the Mail Sessions page, where you can edit the configuration.
Review the information that you entered. To revise your selections, press B. To continue installing, press N.
To install the product, press I. To generate a response file, press G.
Review the result of the installation. Press F to exit the installation wizard.
Restart the Deployment Manager:
- AIX or Linux: Open a command prompt and change to the profile_root/Dmgr01/bin directory. Enter the ./stopManager.sh command and then enter the ./startManager.sh command.
- Windows: Stop and restart the Deployment Manager service.
Start all the federated nodes and enter the startNode command. Repeat these steps for each node:
1. Log in to a node.
2. From a command line, change to the profile_root/bin directory.
3. Enter the startNode command for your operating system:
  - AIX or Linux: ./startNode.sh
  - Windows: startNode.bat
Log in to the Integrated Solutions Console on the DM to perform a full synchronization of all nodes.
1. Go to System administration > Nodes.
2. Select the nodes and click Full Resynchronize.
Wait until the DM copies all the application EAR files to the installedApps directory on each of the nodes. This process can take up to 30 minutes.
To verify that the DM has distributed the application EAR files to the nodes, check the SystemOut.log file of each node agent. The default path to the SystemOut.log file on a node is profile_root/logs/nodeagent.
Look for a message such as the following example: ADMA7021I: Distribution of application application_name completed successfully. where application_name is the name of an IBM Connections application.
Restart the Deployment Manager.
Start all your IBM Connections clusters:
1. Log in to the Integrated Solutions Console on the DM
2. Go to Servers > Clusters > WebSphere Application server clusters.
3. Select the IBM Connections clusters and click Start.
If you installed a cluster with multiple Search nodes, create the initial index. For more information about creating the Search index, see the Creating the initial Search index topic.
1. If you are installing a non-English language deployment, enable Search dictionaries. For more information, see the Enabling Search dictionaries topic.
2. The index is ready when the INDEX.READY and CRAWLING_VERSION files are present in the index directory.
If some applications do not start, the file-copying process might not have completed. Wait a few minutes and start the applications.

Option	Description
IBM Connections 4.0	Install all IBM Connections applications.
Activities	Collaborate with colleagues.
Blogs	Write personal perspectives about projects.
Communities	Interact with people on shared projects.
Bookmarks	Bookmark important websites.
Files	Share files among users.
Forums	Discuss projects and exchange information.
Metrics	Identify and analyze usage and trends.
Mobile	Access IBM Connections from mobile devices.
Moderation	Forum and community owners can moderate the content of forums.
Profiles	Find people in the organization.
Wikis	Create content for your website.

Results

The installation wizard has installed IBM Connections in a network deployment.

AIX or Linux (root user): /var/ibm/InstallationManager/logs
AIX or Linux (non-root user): /home/user/var/ibm/Installation Manager/logs where user is the non-root user name
Windows Server 2008 64-bit: C:\ProgramData\IBM\Installation Manager\logs

What to do next

Complete the post-installation tasks that are relevant to your installation. For more information, see the Post-installation tasks topic.

Access network shares:

If you installed WAS on Microsoft Windows and configured it to run as a service, ensure that you can access network shares. For more information, see the Accessing Windows network shares topic.

Install silently

Silent installation is a tool for installing the same IBM Connections profile on multiple computers without using the IBM Installation Manager. This simplifies the installation process in enterprises that need multiple, identical instances of IBM Connections.

Silent installation uses installation parameters in a response file to install identical IBM Connections profiles on different computers. To specify silent installation parameters you can edit the default response file provided with IBM Connections, or create a new file.

In addition to silently installing IBM Connections, you can use the silent installation process to modify, update, or uninstall IBM Connections.

Install IBM Connections in silent mode (with an existing IBM Installation Manager)

Use a silent installation to perform an identical installation of IBM Connections on multiple systems.

Ensure that you complete all the prerequisite tasks that are relevant for your environment. For more information, see the Before installing topic.

Ensure that IBM Installation Manager is installed on your system. To prevent errors caused by using the wrong version of IBM Installation Manager, remove the following line from the default response file:

<offering id='com.ibm.cic.agent' version='1.4.4000.20110525_1254' profile='IBM Installation Manager' features='agent_core,agent_jre' installFixes='none'/>

To create a customized version of the default response file, run the installation wizard in interactive mode. For more information, see the Creating a response file topic.

Use a response file for your intended deployment, install IBM Connections on multiple systems without needing to interact with the installation wizard.

To perform a silent installation:

cd IM_root/eclipse/tools
Enter the following command:
- AIX or Linux: ./imcl -input response_file -log log_file -acceptLicense
- Windows: imcl.exe -input response_file -log log_file -acceptLicense
  The IM_root/eclipse directory contains a similar file called IBMIM.exe but that file is not suitable for silent installation.
where response_file is the full path and name of the response file and log_file is the full path and name of the log file. The default name of the response file is LC.rsp. By default, the response file is in the following directory:
- AIX or Linux: connections_root.
- Microsoft Windows:: connections_root.
Examples:
- AIX or Linux: ./imcl -input /opt/IBM_Connections_Install/IBMConnections/LC.rsp -log /mylog/silent_install_log.xml -acceptLicense
- Windows: imcl.exe -input E:\IBM_Connections_Install\IBMConnections\LC.rsp -log \mylog\silent_install_log.xml -acceptLicense

Results

IBM Installation Manager writes the result of the installation command to the log file specified with the -log parameter.

To check the complete details of the installation, open each of the log files in connections_root/logs. Each IBM Connections application installed has a log file, using the following naming format: applicationInstallog.txt, where application is the name of an IBM Connections application.

If the installation is successful, the log files are empty. For example:

<?xml version="1.0" encoding="UTF-8"?>
<result>
</result>

The log file contains an error element if the operation was not completed successfully. A successful installation adds a value of 0 to the log file. An unsuccessful installation adds a positive integer to the log file.

The log file for IBM Installation Manager records the values that you entered when you ran IBM Installation Manager in interactive mode. To review the log file for IBM Installation Manager, open the date_time.xml file, where date_time represents the date and time of the installation. The file by default is in the following directory:

AIX or Linux (root user): /var/ibm/InstallationManager/logs
AIX or Linux (non-root user): user_home/var/ibm/InstallationManager/logs
Windows (administrator): C:\ProgramData\IBM\Installation Manager\logs
Windows (non-administrator): C:\user\Application Data\IBM\Installation Manager\logs

What to do next

Complete any applicable post-installation tasks. For more information, see the Post-installation tasks topic.

Install IBM Connections and IBM Installation Manager in silent mode

Use a silent installation to perform an identical installation of IBM Connections and IBM Installation Manager on multiple systems.

This task assumes that IBM Installation Manager is not installed on your system.

Ensure that you complete all the prerequisite tasks that are relevant for your environment. For more information, see the Before installing topic.

However, do not complete the prerequisite tasks that relate to IBM Installation Manager.

Edit the default response file to suit your environment. For more information, see the Using the default response file topic.

Use a response file for your intended deployment, install IBM Connections on multiple systems without needing to interact with the installation wizard.

To perform a silent installation:

Open a command prompt and go to the location of the silent installation file. The file is stored in the IBM_Connections_set-up/IBM_Connections_install/IM/OS directory,
...where IBM_Connections_set-up is the directory or media where the IBM Connections installation files are located and OS represents your operating system
To change the paths to the response file and log file, edit the lc_install.ini file. The file is located in the IBM_Connections_set-up/IBM_Connections_install/IM/OS directory.
Run the silent installation script:
- AIX or Linux (root user): ./installc -input response_file -log log_file -acceptLicense
- AIX or Linux (non-root user): ./userinstc -input response_file -log log_file -acceptLicense
- Windows (administrator): installc.exe -input response_file -log log_file -acceptLicense
- Windows (non-administrator): userinstc.exe -input response_file -log log_file -acceptLicense
where response_file is the full path and name of the response file and log_file is the full path and name of the log file. The default name of the file is LC.rsp.
By default, the response file is stored in the IBM_Connections_set-up/IBM_Connections_install/IBMConnecgtions directory on the installation media.

Results

IBM Installation Manager writes the result of the installation command to the log file specified with the -log parameter.

If the installation is successful, the log files are empty. For example:

<?xml version="1.0" encoding="UTF-8"?>
<result>
</result>

AIX or Linux (root user): /var/ibm/InstallationManager/logs
AIX or Linux (non-root user): user_home/var/ibm/InstallationManager/logs
Windows (administrator): C:\ProgramData\IBM\Installation Manager\logs
Windows (non-administrator): C:\user\Application Data\IBM\Installation Manager\logs

What to do next

Complete any applicable post-installation tasks. For more information, see the Post-installation tasks topic.

The default response file

Response files provide input parameters for silent installations of IBM Connections.

The default response file for AIX and Linux is called LC.rsp and is located in the IBM Connections set-up directory or installation media. You can edit this file and use it as input for a silent installation.

IBM does not provide a default response file on Windows because it is more convenient if you to generate the file yourself. For information about generating a response file, see the Creating a response file topic.

Instead of generating a new response file, you can edit the default response file that is provided with the product. However, if you edit the default response file, you need to add encrypted passwords to the file. For more information, see the Creating encrypted passwords for a response file topic.

Use the default response file

Use the default response file to specify silent installation parameters for your environment.

Encrypt your administrator passwords. For more information about encrypting passwords, see the Creating encrypted passwords for a response file topic.

Silent installation uses the parameters in a response file to install the same IBM Connections profile on multiple computers.

If you are silently installing IBM Connections as a non-root user in an AIX or Linux environment, you must specify that parameter in the silent-install.ini file.

Navigate to the connections_root directory and open the LC.rsp response file.
Specify your installation parameters. For more information, see the Default response file topic.
Add the encrypted passwords to the relevant elements of the response file. The following example shows the elements for the Activities passwords:
```
<data key='user.activities.adminuser.password' value='encrypted_password'/>
```
```
<data key='user.activities.dbUserPassword value='encrypted_password'/>
```
where encrypted_password is the password after you encrypted it.
Change the default WAS administrator name from wasadmin if your administrator name is different.
Save your changes.
If you are performing the silent installation as a non-root user on AIX or Linux systems:
1. Open the silent-install.ini file for editing from the following location:
  - AIX: IBM_Connections_set-up/IBM_Connections_install/IM/aix/silent-install.ini
  - Linux: IBM_Connections_set-up/IBM_Connections_install/IM/linux/silent-install.ini
  - Linux on System z: IBM_Connections_set-up/IBM_Connections_install_s390/IM/zlinux/silent-install.ini
  where IBM_Connections_set-up is the IBM Connections set-up directory or installation media.
2. In the second line of the file, change admin to nonadmin.
3. Save and close the file.

Create a response file

Use a response file to install, modify, update, or uninstall IBM Connections without user interaction.

You can create a response file by using IBM Installation Manager or by editing the file that is provided with the product. For more information about editing the file, see the Default response file topic.

Ensure that IBM Installation Manager is installed. For more information, see the Installing IBM Connections 4.0 topic.

To ensure that the response file captures the details of your SSL certificates, start IBM WAS.

The default location of a response file that you generate is the connections_root/silentResponseFile directory. To specify a different location, edit the generate_install_responsefile.bat|sh file or generate_other_responsefile.bat|sh file, depending on the task to carry out.

Instead of creating your own response file, you can edit the file that is provided with the product. The file is in the IBM_Connections_set-up/IBM_Connections_install/IBMConnections directory. However, this default file is applicable only for installation. The response files for modifying, updating, rolling back, and uninstalling the product are based on the response file for installation. Before you create a response file for any of those procedures, you must first run the silent installation procedure.

For more information about creating response files with IBM Installation Manager, go to the Recording a response file with Installation Manager webpage.

This task describes the procedure to generate a response file for the following procedures:

Install IBM Connections
Modify an existing installation by adding or removing IBM Connections applications
Update an existing installation by installing a fix pack
Roll back an update
Uninstall IBM Connections

For each procedure, run a simulated instance of the IBM Installation Manager and record your input to a response file. Later, you can run a silent command that uses this response file as an input parameter.

Default response files on AIX or Linux:

Install: LC.rsp
Modify - Add: LC_modify_add.rsp
Modify - Remove: LC_modify_remove.rsp
Update: LC_update.rsp
Roll back: LC_rollback.rsp
Uninstall: LC_uninstall.rsp

To create a response file, complete the following steps:

Open a command prompt and go to the IM_root/eclipse directory.
Ensure that the IBM_Connections_set-up/IBM_Connections_install/IM/OS/skip directory allows write access, where IBM_Connections_set-up is the directory or media where the IBM Connections installation files are located, and OS represents your operating system.
Run the command to record a response file. This command uses the -skipInstall agentDataLocation argument, which records the installation commands without installing IBM Connections. Substitute your own file name and path for the response file. Verify the file paths that you enter exist because IBM Installation Manager does not create directories for the response file.
- AIX and Linux: ./IBMIM -record /response_files/install_product.xml -skipInstall agentDataLocation
- Microsoft Windows:: IBMIM.exe -record responseFile -skipInstall agentDataLocation
where agentDataLocation is the file path to the skip directory, which stores IBM Installation Manager data files.
- The -log option is not available when recording a response file.
- Use quotation marks around file paths that contain spaces.
- You can use the same agentDataLocation parameter in the next recording session to update, modify, roll back or uninstall IBM Connections. However, if you want to record a new installation, you must specify a new agentDataLocation parameter.
Enter the required information in the IBM Installation Manager.
- To install a new deployment, open Files > Preferences, and enter the path to the IBM Connections repository; for example: C:\build\\IBM_Connections_Install\IBMConnections. Click Install and enter the required information as if you were installing the product. For more information, see the Installing IBM Connections 4.0 topic.
- To modify an existing installation, click Modify and enter the required information.
  - To add applications, select the applications to add in the Application Selection pane.
    Ensure that all the currently installed applications are also selected.
  - To remove applications, clear the check boxes of the applications to remove in the Application Selection pane.
  For more information, see the Modifying the installation in interactive mode topic.
- To update an existing installation, click Update and enter the required information.
- To roll back an update, click Rollback and enter the required information
- To uninstall IBM Connections, click Uninstall and enter the required information. For more information, see the Uninstalling a deployment topic.
Confirm that the new response file is present.

What to do next

Use the response file to silently install, modify, update, roll back, or uninstall IBM Connections.

If you are running IBM Installation Manager as a non-administrator and plan to use the response file to install the product on another user's system, change the file paths in your response file from absolute paths to relative paths.

Create encrypted passwords for a response file

Add encrypted passwords to your edited version of the default response file.

You can create a response file using IBM Installation Manager or by editing the file that is provided with the product. For more information about editing the file, see the Default response file topic.

When you edit the default response file to suit your own environment, create encrypted passwords and add them to the file. Create encrypted passwords for both WebSphere Application Sever and your DBs.

To create encrypted passwords for a response file, complete the following steps:

Open a command prompt and change to the IBM_Connections_setup/IBM_Connections_Install/IM/OS/tools where OS is your operating system.
Run the following command:
- AIX or Linux: ./imutilsc encryptString Password -silent -noSplash
- Windows: imutilsc.exe encryptString Password -silent -noSplash
  where Password is your password.
Add the encrypted password to the relevant line in the response file. You usually need to enter passwords for both the WAS administrator and the DB user. For example:
<data key='user.activities.adminuser.password' value='encrypted_password'/>
<data key='user.activities.dbUserPassword value='encrypted_password'/>
where encrypted_password is the value generated by the command.
You might also need to change the default WAS administrator name from wasadmin, if different from your administrator name.
Repeat these steps for each unique password.

What to do next

Use the response file to silently install, modify, update, roll back, or uninstall IBM Connections.

Directory paths for IBM Installation Manager

IBM Installation Manager uses default directory paths for its installation files.

Purpose

This topic describes the default directory paths for IBM Installation Manager.

IBM Installation Manager

Each instance of Installation Manager must have its own installation directory and agent data directory.

The directories where IBM Installation Manager is installed are determined by the type of user account that you used to install the product.

Any changes that you make to an installation of IBM Installation Manager installed with a root user or non-administrator account do not affect an installation of IBM Installation Manager installed with a non-root user or non-administrator account. The reverse is also true.

The following table indicates the location of the relevant directories.

Default installation directories for IBM Installation Manager
Directory Root/Administrator Non-root/non-administrator
Default installation directory
AIX or Linux: /opt/IBM/InstallationManager/eclipse
Windows: C:\IBM\Installation Manager\eclipse

AIX or Linux: /<user/IBM/InstallationManager/eclipse
Windows XP Professional, Windows Server 2003: C:\<user>\IBM\Installation Manager\eclipse
Windows Vista, Windows Server 2008, Windows 7: C:\Users\<user>\IBM\Installation Manager\eclipse
Eclipse log file
AIX or Linux: /var/ibm/InstallationManager/pluginState/.metadata
Windows Server 2008: C:\ProgramData\IBM\Installation Manager\pluginState\.metadata

AIX or Linux: /<user/var/ibm/InstallationManager/pluginState/.metadata
Windows Server 2008: C:\Users\<user\IBM\Installation ManagerInstaller\pluginState\.metadata
Default agent data location.
For more information about agent data, go to the Agent data location page in the IBM Installation Manager information center.

AIX or Linux: /var/ibm/InstallationManager
Windows Server 2008: C:\ProgramData\IBM\Installation Manager

AIX or Linux: /<user>/var/ibm/InstallationManager
Windows Server 2008: C:\Users\<user>\AppData\Roaming\IBM\Installation Manager

Directory	Root/Administrator	Non-root/non-administrator
Default installation directory	AIX or Linux: /opt/IBM/InstallationManager/eclipse Windows: C:\IBM\Installation Manager\eclipse	AIX or Linux: /<user/IBM/InstallationManager/eclipse Windows XP Professional, Windows Server 2003: C:\<user>\IBM\Installation Manager\eclipse Windows Vista, Windows Server 2008, Windows 7: C:\Users\<user>\IBM\Installation Manager\eclipse
Eclipse log file	AIX or Linux: /var/ibm/InstallationManager/pluginState/.metadata Windows Server 2008: C:\ProgramData\IBM\Installation Manager\pluginState\.metadata	AIX or Linux: /<user/var/ibm/InstallationManager/pluginState/.metadata Windows Server 2008: C:\Users\<user\IBM\Installation ManagerInstaller\pluginState\.metadata
Default agent data location. For more information about agent data, go to the Agent data location page in the IBM Installation Manager information center.	AIX or Linux: /var/ibm/InstallationManager Windows Server 2008: C:\ProgramData\IBM\Installation Manager	AIX or Linux: /<user>/var/ibm/InstallationManager Windows Server 2008: C:\Users\<user>\AppData\Roaming\IBM\Installation Manager

To find the location of IBM Installation Manager:

AIX or Linux:
1. Open the /etc/.ibm/registry/InstallationManager.dat file.
2. Examine the location entry.
  For example, location=/var/ibm/InstallationManager.
Windows:
1. Open the Windows Registry.
2. Search for the following registry key: HKLM\SOFTWARE\Wow6432Node\IBM\Installation Manager\location.
3. Open the key and examine its value.

Modify the installation in interactive mode

Modify your deployment of IBM Connections by adding or removing applications. Use the Modify function of the IBM Installation Manager to add or remove IBM Connections applications.

To modify your installation:

Open a command prompt and change to the IM_root directory.
Run the following command:
- AIX or Linux: ./launcher
- Windows: launcher.exe
From the IBM Installation Manager menu, click File > Preferences.
Click Repositories.
In the Repositories area, select the repositories that you want to modify.
Click OK to save your selections.
Click Modify.
Select IBM Connections and click Next.
In the Application Selection page, choose the applications you want to add or remove and then click Next.
- Add applications: Select the check boxes of any applications that are not already installed and to add to your deployment.
- Remove applications: Clear the check boxes of any installed applications to remove from your deployment.
All installed applications are selected by default.
The Home page, News, and Search applications are required and cannot be removed.
Enter the administrative ID and password of the Deployment Manager.
This ID is set to the connectionsAdmin J2C authentication alias, which is mapped to the following J2EE roles: dsx-admin, widget-admin, and search-admin. It is also used by the service integration bus. To use security management software such as Tivoli Access Manager or SiteMinder, the ID that you specify here must exist in the LDAP directory. For more information, see the Switching to unique administrator IDs for system level communication topic.
Configure your topology:
The panel described in this step appears only if you selected new applications to install.
If you select an existing cluster on which to deploy applications, the nodes in that cluster are fixed and cannot be modified.
- Small deployment:
  1. Select the Small deployment topology.
  2. Enter a Cluster name for the topology.
  3. Select a Node.
  4. Click Next.
- Medium deployment:
  1. Select the Medium deployment topology.
  2. Select the default value or enter a Cluster name for each application or for groups of applications.
    For example, use Cluster1 for Activities, Communities, and Forums.
    IBM Installation Manager creates servers and clusters when required.
  3. Select a Node for each cluster. Accept the predefined node or select a different node.
    These nodes host application server instances that serve IBM Connections applications. You can assign multiple nodes to a cluster, where each node is a server member of that cluster.
  4. Enter a Server member name for the selected node. Choose the default or enter a custom name.
    If you enter a custom server member name, the name must be unique across all nodes in your deployment.
  5. Click Next.
- Large deployment:
  1. Select the Large deployment topology.
  2. Enter a Cluster name for each application.
    IBM Installation Manager creates servers and clusters when required.
  3. Select a Node for each cluster. Accept the predefined node or select a different node.
    These nodes host application server instances that serve IBM Connections applications. You can assign multiple nodes to a cluster, where each node is a server member of that cluster.
  4. Enter a Server member name for the selected node. Choose the default or enter a custom name.
    If you enter a custom server member name, the name must be unique across all nodes in your deployment.
  5. Click Next.
Enter the DB information.
The panel described in this step appears only if you selected new applications to install and if the new applications require DB configuration.
1. Specify whether the installed applications use the same DB server or instance: Select Yes or No.
  If allowed by your DB configuration, you can select multiple DB instances as well as different DB servers.
2. Select a Database type from one of the following options:
  - IBM DB2 Universal Database
  - Oracle Enterprise Edition
  - Microsoft SQL Server Enterprise Edition
3. Enter the Database server host. For example: appserver.enterprise.example.com
  If your installed applications use different DB servers, enter the DB host for each application.
4. Enter the Port number of the DB server. The default values are: 50000 for DB2, 1521 for Oracle, and 1433 for SQL Server.
  If your installed applications use different DB servers or instances, enter the port for each DB server or instance.
5. Enter the JDBC driver location. For example:
  - AIX: /usr/IBM/WebSphere/AppServer/lib
  - Linux:
    /opt/IBM/WebSphere/AppServer/lib
  - Windows:
    C:\IBM\WebSphere\Appserver\lib
6. Ensure that the following JDBC driver libraries are present in the JDBC directory:
  
  DB2
  
  db2jcc.jar and db2jcc_license_cu.jar
  Ensure that your user account has the necessary permissions to access the DB2 JDBC files.
  
  Oracle
  
  ojdbc6.jar
  
  SQL Server
  
  Download the SQL Server JDBC 2 driver from the Microsoft website to a local directory and enter that directory name in the JDBC driver library field.
  The directory must not contain the sqljdbc.jar file, only the sqljdbc4.jar file. Even though the data source is configured to use the sqljdbc4.jar file, an exception occurs if both files are present in the same directory.
  IBM recommends that you obtain this Microsoft hotfix for the JDBC 2 driver for production deployments.
7. Enter the User ID and Password for each DB. If each DB uses the same user credentials, select the Use the same password for all applications check box and then enter the UID and password for the first DB in the list.
  
  If your DB type is Oracle, connect to the DB with the UID that you used when you created the application DB.
8. Click Validate to verify your DB settings. If the validation fails, check your DB settings. When the validation succeeds, click Next.
  IBM Installation Manager tests your DB connection with the DB values that you supplied. You can change the DB configuration later in the WAS Integrated Solutions Console.
In the summary panel, confirm your selection and click Modify.
When the modification process is complete, restart the Deployment Manager and all the nodes.
Wait until the DM copies all the application EAR files to the installedApps directory on each of the nodes. This process can take up to 30 minutes.
To verify that the DM has distributed the application EAR files to the nodes, check the SystemOut.log file of each node agent. The default path to the SystemOut.log file on a node is profile_root/logs/nodeagent.
Look for a message such as the following example: ADMA7021I: Distribution of application application_name completed successfully. where application_name is the name of an IBM Connections application.
To confirm that the installation was successful, open the log files in connections_root/logs. Each IBM Connections application installed has a log file, using the following naming format: application_nameInstall.log, where application_name is the name of an IBM Connections application. Search for the words error or exception to check whether any errors or exceptions occurred during installation.

Modify the installation in silent mode

Modify your deployment of IBM Connections by adding or removing applications in silent mode. With the help of a response file, use the Modify function of the IBM Installation Manager to add or remove IBM Connections applications.

To modify your installation in silent mode, complete one of the following tasks:

Add applications in silent mode

Add applications to your deployment of IBM Connections without using the installation wizard.

Create a response file for this task by running a simulated modification. For more information, see the Creating a response file topic.

A silent modification uses a response file to automate the addition of applications to your deployment.

To perform a silent modification:

cd IM_root/eclipse/tools
Enter the following command:
- AIX or Linux: ./imcl -input response_file -log log_file -acceptLicense
- Windows: imcl.exe -input response_file -log log_file -acceptLicense
  The IM_root/eclipse directory contains a similar file called IBMIM.exe but that file is not suitable for silent installation.
where response_file is the full path and name of the response file and log_file is the full path and name of the log file. The default name of the response file is LC.rsp. By default, the response file is in the following directory:
- AIX or Linux: connections_root.
- Microsoft Windows:: connections_root.
Examples:
- AIX or Linux: ./imcl -input /opt/IBM_Connections_Install/IBMConnections/LC.rsp -log /mylog/silent_install_log.xml -acceptLicense
- Windows: imcl.exe -input E:\IBM_Connections_Install\IBMConnections\LC.rsp -log \mylog\silent_install_log.xml -acceptLicense

Results

IBM Installation Manager writes the result of the installation command to the log file specified with the -log parameter.

If the installation is successful, the log files are empty. For example:

<?xml version="1.0" encoding="UTF-8"?>
<result>
</result>

AIX or Linux (root user): /var/ibm/InstallationManager/logs
AIX or Linux (non-root user): user_home/var/ibm/InstallationManager/logs
Windows (administrator): C:\ProgramData\IBM\Installation Manager\logs
Windows (non-administrator): C:\user\Application Data\IBM\Installation Manager\logs

Remove applications in silent mode

Silently remove applications from your deployment of IBM Connections.

Create a response file for this task by running a simulated modification. For more information, see the Creating a response file topic.

A silent modification uses a response file to automate the removal of applications from your deployment.

To perform a silent modification:

cd IM_root/eclipse/tools
Enter the following command:
- AIX or Linux: ./imcl -input response_file -log log_file -acceptLicense
- Windows: imcl.exe -input response_file -log log_file -acceptLicense
  The IM_root/eclipse directory contains a similar file called IBMIM.exe but that file is not suitable for silent installation.
where response_file is the full path and name of the response file and log_file is the full path and name of the log file. The default name of the response file is LC.rsp. By default, the response file is in the following directory:
- AIX or Linux: connections_root.
- Microsoft Windows:: connections_root.
Examples:
- AIX or Linux: ./imcl -input /opt/IBM_Connections_Install/IBMConnections/LC.rsp -log /mylog/silent_install_log.xml -acceptLicense
- Windows: imcl.exe -input E:\IBM_Connections_Install\IBMConnections\LC.rsp -log \mylog\silent_install_log.xml -acceptLicense

Results

IBM Installation Manager writes the result of the installation command to the log file specified with the -log parameter.

If the installation is successful, the log files are empty. For example:

<?xml version="1.0" encoding="UTF-8"?>
<result>
</result>

AIX or Linux (root user): /var/ibm/InstallationManager/logs
AIX or Linux (non-root user): user_home/var/ibm/InstallationManager/logs
Windows (administrator): C:\ProgramData\IBM\Installation Manager\logs
Windows (non-administrator): C:\user\Application Data\IBM\Installation Manager\logs

Modify the installation in console mode

Use console mode, modify your deployment of IBM Connections by adding or removing applications. Use IBM Installation Manager in console mode to add or remove IBM Connections applications. This method is convenient if you cannot or do not want to use the interactive mode.

To modify your installation:

On each node, stop any running instances of WAS and WebSphere node agents.
Start WAS Network Deployment Manager.
Open a command prompt and change to the IM_root/tools
Start IBM Installation Manager in console mode:
- AIX or Linux: ./imcl -c
- Windows: imcl.exe -c
Type 1 to begin modifying the deployment.
In the Select packages to install step, type 1 to select the package and then type N to proceed.
Select the applications to add or remove and then type N.
- Add applications: Set the numbers corresponding to applications that are not already installed and to add to your deployment.
- Remove applications: Set the numbers corresponding to installed applications to remove from your deployment. The Home page, News, and Search applications are required and can't be removed.
All installed applications are selected by default.
Enter the administrative ID and password of the Deployment Manager.
This ID is set to the connectionsAdmin J2C authentication alias, which is mapped to the following J2EE roles: dsx-admin, widget-admin, and search-admin. It is also used by the service integration bus. To use security management software such as Tivoli Access Manager or SiteMinder, the ID that you specify here must exist in the LDAP directory. For more information, see the Switching to unique administrator IDs for system level communication topic.
Configure your topology. For more information about each option, see the Deployment options topic.
- Small deployment:
  1. Type 1 to select the Small deployment topology.
  2. Enter a Cluster name for the topology.
  3. Select a Node.
  4. Enter a Server member name for the node.
  5. Type N to proceed.
- Medium deployment:
  1. Type 2 to select the Medium deployment topology.
  2. Select the default value or enter a Cluster name for each application or for groups of applications.
    For example, use Cluster1 for Activities, Communities, and Forums.
    IBM Installation Manager creates servers and clusters when required.
  3. Select a Node for each cluster. Accept the predefined node or select a different node.
    These nodes host application server instances that serve IBM Connections applications. You can assign multiple nodes to a cluster, where each node is a server member of that cluster.
  4. Enter a Server member name for the selected node. Choose the default or enter a custom name.
    If you enter a custom server member name, the name must be unique across all nodes in your deployment.
  5. The topology specified is displayed. To re-specify any details, type the number that corresponds to the application; for example, type 1 for Activities.
  6. Type N to proceed.
- Large deployment:
  1. Type 3 to select the Large deployment topology.
  2. Enter a Cluster name for each application.
    IBM Installation Manager creates servers and clusters when required.
  3. Select a Node for each cluster. Accept the predefined node or select a different node.
    These nodes host application server instances that serve IBM Connections applications. You can assign multiple nodes to a cluster, where each node is a server member of that cluster.
  4. Enter a Server member name for the selected node. Choose the default or enter a custom name.
    If you enter a custom server member name, the name must be unique across all nodes in your deployment.
  5. The topology specified is displayed. To re-specify any details, type the number that corresponds to the application; for example, type 1 for Activities.
  6. Type N to proceed.
Enter the DB information:
1. Specify whether the installed applications use the same DB server or instance: Type 1 to specify that the applications use same DB server or instance; type 2 to specify that they use different DB servers or instances.
  If allowed by your DB configuration, you can select multiple DB instances as well as different DB servers.
2. Select a Database type from one of the following options:
  - IBM DB2 Universal Database
  - Oracle Enterprise Edition
  - Microsoft SQL Server Enterprise Edition
3. Enter the Database server host. For example: appserver.enterprise.example.com
  If your installed applications use different DB servers, enter the DB host for each application.
4. Enter the Port number of the DB server. The default values are: 50000 for DB2, 1521 for Oracle, and 1433 for SQL Server.
  If your installed applications use different DB servers or instances, enter the port for each DB server or instance.
5. Enter the JDBC driver location. For example:
  - AIX: /usr/IBM/WebSphere/AppServer/lib
  - Linux:
    /opt/IBM/WebSphere/AppServer/lib
  - Windows:
    C:\IBM\WebSphere\Appserver\lib
6. Ensure that the following JDBC driver libraries are present in the JDBC directory:
  
  DB2
  
  db2jcc.jar and db2jcc_license_cu.jar
  Ensure that your user account has the necessary permissions to access the DB2 JDBC files.
  
  Oracle
  
  ojdbc6.jar
  
  SQL Server
  
  Download the SQL Server JDBC 2 driver from the Microsoft website to a local directory and enter that directory name in the JDBC driver library field.
  The directory must not contain the sqljdbc.jar file, only the sqljdbc4.jar file. Even though the data source is configured to use the sqljdbc4.jar file, an exception occurs if both files are present in the same directory.
  IBM recommends that you obtain this Microsoft hotfix for the JDBC 2 driver for production deployments.
7. Enter the User ID and Password for each DB. If each DB uses the same user credentials, confirm the Use the same password for all applications question and then enter the UID and password for the first DB in the list.
  
  If your DB type is Oracle, connect to the DB with the UID that you used when you created the application DB.
8. If you need to make changes, type the number that corresponds to the application to change. Alternatively, type R to reset all the DB specifications to their default values.
9. Press Enter to verify your DB settings. If the validation fails, check your DB settings. When the validation succeeds, click Next.
  IBM Installation Manager tests your DB connection with the DB values that you supplied. You can change the DB configuration later in the WAS Integrated Solutions Console.
10. If the verification check is successful, type N to proceed. If verification fails, press B to re-enter the required information.
Review the information that you have entered. To revise your selections, press B. To finish modifying, press M.
Review the result of the installation. Press F to exit the installation wizard.
Restart the Deployment Manager:
- AIX or Linux: Open a command prompt and change to the profile_root/Dmgr01/bin directory. Enter the ./stopManager.sh command and then enter the ./startManager.sh command.
- Windows: Stop and restart the Deployment Manager service.
Start all the federated nodes and enter the startNode command. Repeat these steps for each node:
1. Log in to a node.
2. From a command line, change to the profile_root/bin directory.
3. Enter the startNode command for your operating system:
  - AIX or Linux: ./startNode.sh
  - Windows: startNode.bat
Log in to the Integrated Solutions Console on the DM to perform a full synchronization of all nodes.
1. Go to System administration > Nodes.
2. Select the nodes and click Full Resynchronize.
Wait until the DM copies all the application EAR files to the installedApps directory on each of the nodes. This process can take up to 30 minutes.
To verify that the DM has distributed the application EAR files to the nodes, check the SystemOut.log file of each node agent. The default path to the SystemOut.log file on a node is profile_root/logs/nodeagent.
Look for a message such as the following example: ADMA7021I: Distribution of application application_name completed successfully. where application_name is the name of an IBM Connections application.
Start all your IBM Connections clusters:
1. Log in to the Integrated Solutions Console on the DM
2. Go to Servers > Clusters > WebSphere Application server clusters.
3. Select the IBM Connections clusters and click Start.
If you installed a cluster with multiple Search nodes, create the initial index. For more information about creating the Search index, see the Creating the initial Search index topic.
1. If you are installing a non-English language deployment, enable Search dictionaries.
2. The index is ready when the INDEX.READY and CRAWLING_VERSION files are present in the index directory.
If some applications do not start, the file-copying process might not have completed. Wait a few minutes and start the applications.

Post-installation tasks

After installation, you need to perform further tasks to ensure an efficient deployment.

After running the wizards to install applications and create DBs, check which of the following additional tasks you need to complete.

Tasks to be completed

After you complete the mandatory post-installation tasks, update the deployment with the latest fixes.

Mandatory post-installation tasks

Review the JVM heap size

Review the size of the Java Virtual Machine heap and adjust it, if necessary, to avoid out-of-memory errors or to suit your hardware capabilities.

If you selected the Small or Medium deployment option when you installed IBM Connections, IBM Installation Manager set the Maximum Heap Size of the Java Virtual Machine (JVM) on each application server. This setting is designed to avoid out-of-memory errors.

Review the heap size on each server to ensure that you are allocating enough memory for IBM Connections but also to ensure that you are not allocating more memory than the physical capabilities of the systems where the JVMs are deployed.

Whether you installed a Small, Medium, or Large deployment of IBM Connections, you should review the JVM heap sizes in your deployment and make adjustments, if necessary.

To review the JVM heap size:

Log into the WAS Integrated Solutions Console and select Servers > Server Type > WebSphere application servers.
Click server,
...where server is the name of an IBM Connections server. You might have several servers in your deployment, so you might need to repeat these steps for each server.
In the Server Infrastructure area, click Java and Process Management and then click Process Definition > Java Virtual Machine.
Review the Maximum heap size. IBM Installation Manager sets the following default values:
- Small deployment:
  
  Maximum Heap Size
  
  2506 MB
- Medium deployment:
  
  Maximum Heap Size
  
  2506 MB
- Large deployment:
  Each application in a Large deployment, except News and Search, has a default Heap size of 256 MB. The News and Search applications have a default Heap size of 784 MB.
Ensure that you are not allocating more memory than the physical capacity of the system where the JVM is installed.
Adjust the current values of the heap size up or down to suit the needs of your deployment and your hardware capabilities.
Click OK and then click Save.
Repeat these steps for any additional servers in your deployment.

Configure IBM HTTP Server

Configure IBM HTTP Server to manage web requests to IBM Connections.

When you have successfully installed IBM Connections to run on WAS, you can configure IBM HTTP Server to handle web traffic by completing the following tasks:

Define IBM HTTP Server

Define IBM HTTP Server to manage web connections.

Install web server plug-ins for IBM HTTP Server, if they are not already installed. For more information, go to the Install web server plug-ins web site.

IBM Connections uses a web server as the entry point for all the applications.

This procedure describes how to create a web server using the Integrated Solutions Console. There are other ways to create the web server. See the IBM WAS information center for more information.

To define IBM HTTP Server:

Start the IBM HTTP Administration Server:
- AIX / Linux
- Windows:
  1. Open the Services window in the Windows Control Panel.
  2. Verify the IBM HTTP Administration Server service is started. If this service is not running, start it
Log in to the WAS Integrated Solutions Console on the Deployment Manager and select...
Select Unmanaged node and click Next.
Set the properties of the node...

Name

Enter the name of the node.

Host Name

Enter the fully qualified DNS host for IBM HTTP Server. For example: webserver.example.com.

Platform

Select the operating system type that hosts your IBM HTTP Server.

Click OK and then click Save.
Select Servers > Server Types > Web servers and click New.
Provide values for the following fields:

Select node

Select the node specified in Step 4.

Server name

Enter the name of the your web server. The default value is webserver1.

Type

Select IBM HTTP Server.
Click Next.
Select the default web server template and click Next.
On the Enter the properties for the new web server page, check the paths and make adjustments if necessary, and then enter the user name and password specified when you installed IBM HTTP Server. Confirm the password and click Next.
Confirm to create the new web server.
Click Finish and then click Save.
Synchronize all the nodes.
Select Servers > Server Types > Web servers and click the link to your webserver.
Click Generate Plug-in.
Select the check box for your webserver.
Click Propagate Plug-in.
Select Servers > Server Types > Web servers and click the link to your webserver.
Click Plug-in properties and then click Copy to Web Server key store directory.
If the plugin-key.kdb file is on a different system from the IBM HTTP Server system, copy it manually from the WAS system to the IBM HTTP Server system.
Restart IBM HTTP Server.

What to do next

Complete the steps in the Configuring IBM HTTP Server for SSL topic.

Configure IBM HTTP Server to handle file downloads from the Files and Wikis applications. For information on this configuration, see the Configuring Files and Wikis downloads topic.

Configure IBM HTTP Server for SSL

Configure IBM HTTP Server to use the SSL protocol.

To support SSL, create a self-signed certificate and then configure IBM HTTP Server for SSL traffic. If you use this certificate in production, users might receiver warning messages from their browsers. In a typical production deployment, you would use a certificate from a trusted certificate authority.

To configure IBM HTTP Server for SSL:

Create a key file.
1. Start the iKeyman user interface.
2. Click Key Database File in the main user interface, then click New.
  Select CMS for the Key DB type. IBM HTTP Server does not support DB types other than CMS.
3. Enter a name for the new key file.
  For example, hostname-key.kdb. Click OK.
4. Enter your password in the Password Prompt dialog box, and confirm the password. Select Stash the password to a file and then click OK. The new key DB should display in the iKeyman utility with default signer certificates. Ensure that there is a functional, non-expiring signer certificate for each of your personal certificates.
Create a self-signed certificate:
1. Start the iKeyman user interface.
2. Click Key Database File and then click Open.
3. Enter your key file name in the Open dialog box and click OK.
4. In the Password Prompt dialog box, enter your password and click OK.
5. Click Personal Certificates in the Key Database content frame, and then click New Self-Signed.
6. Enter the required information about the key file, your webserver, and organization in the dialog box.
7. Click OK.
Save the new self-signed certificate with a unique file name; do not overwrite the default Plugin-key.kdb file because that file might be accessed by other applications.
Stop IBM HTTP Server.
Log in to the WAS Integrated Solutions Console for the Deployment Manager and select Servers > Server types > Web servers.
From the list of web servers, click the web server that you defined for this profile.
On the Configuration page for this web server, click Edit for the Configuration file name field. This action opens the httpd.conf configuration file on the Deployment Manager.
Add the following text to the end of the configuration file:
LoadModule ibm_ssl_module modules/mod_ibm_ssl.so
<IfModule mod_ibm_ssl.c>
Listen 0.0.0.0:443
<VirtualHost *:443>
ServerName server_name
#DocumentRoot C:\IBM\HTTPServer\htdocs
SSLEnable
</VirtualHost>
</IfModule>
SSLDisable
Keyfile "path_to_key_file"
SSLStashFile "path_to_stash_file"
where
- server_name is the host of the IBM HTTP Server.
- path_to_key_file is the path to the key file that you created with the iKeyman utility.
- path_to_stash_file is the path to the associated stash file.
For example:
- AIX:
  - Keyfile: /usr/IBM/keyfiles/key_file.kdb
  - SSLStashFile: /usr/IBM/keyfiles/key_file.sth
- Linux:
  - Keyfile: /opt/IBM/keyfiles/key_file.kdb
  - SSLStashFile: /opt/IBM/keyfiles/key_file.sth
- Microsoft Windows::
  - Keyfile: C:\IBM\keyfiles\key_file.kdb
  - SSLStashFile: C:\IBM\keyfiles\key_file.sth
...where key_file is the name that you have given to your key file and stash file.
Click Apply and then click OK.
Restart IBM HTTP Server to apply the changes.
Test the new configuration: Open a web browser and ensure that you can successfully reach https://server_name. You might be prompted to accept the self-signed certificate on your browser.

Results

IBM Connections users can access applications through the SSL protocol.

If you receive an error message about failing to load a GSK library (libgsk7ssl.so), install the libgsk7ssl.so GSK library. For more information, go to the following Support page: Failure attempting to load GSK library when using SSL with IBM HTTP Server.

What to do next

For more information about securing web communications, go to the IBM WAS Information Center or read the IBM WAS V7.0 Security Handbook.

For more information about the key store and setting up the IBM HTTP Server, see the Securing communications topic in the WAS Information Center. The key file can be shared between two webservers, thus providing failover capability.

Map applications to IBM HTTP Server

Map IBM Connections applications to IBM HTTP Server.

Complete this task if you installed and configured IBM HTTP Server before installing IBM Connections.

If you plan to configure a reverse proxy, see the Configuring a reverse caching proxy topic.

If you installed and configured IBM HTTP Server after installing IBM Connections, your IBM Connections applications are automatically mapped to the web server. However, if you installed and configured IBM HTTP Server before installing IBM Connections, manually map the applications.

To map your IBM Connections applications to IBM HTTP Server and regenerate the plugin:

Open the WAS Integrated Solutions Console on the system where you installed the Deployment Manager.
Select Applications > Application Types > WebSphere enterprise applications.
Map an IBM Connections application to IBM HTTP Server:
This step instructs you to select webserver1. Ensure defined this web server before you attempt to complete these steps.
1. Select application > Manage Modules,
  ...where application is an IBM Connections application.
2. In the Clusters and Servers box, select the cluster and server on which you installed the application. If necessary, use the Ctrl key to select both targets.
3. Select the check boxes for all the modules and click Apply.
4. Review the Server details and ensure that both servers are listed there. Click OK and then click Save.
5. Repeat this step for each IBM Connections application.
From the WAS Integrated Solutions Console, select Servers > Server Types > Web servers and then click the web server (webserver1).
Click Generate Plug-in.
Click your web server again and then click Propagate Plug-in.
If you have trouble propagating the plug-in on Linux, restart IBM HTTP Server s:
```
 ./adminctl start
 ./apachectl -k stop
 ./apachectl -k start
```
Stop and restart the web server.
Synchronize the nodes.
Restart all IBM Connection clusters.
Restart the Deployment Manager.

What to do next

To verify that the mappings are correct, complete the steps in the Verifying application mappings topic.

Test the mappings: open a web browser and try to access each of the applications by specifying the web address using the following syntax:

http://hostname/application_name

where hostname is the host of the web server to which you mapped the application and application_name is the name of the application. Do not specify the port.

Verify application mappings

Verify that IBM Connections applications are mapped to your webserver.

From the WAS Integrated Solutions Console, select Servers > Server Types > Web servers and then click the web server (webserver1).
Click Generate Plug-in.
Click your web server again and then click Propagate Plug-in.
If you have trouble propagating the plug-in on Linux, restart IBM HTTP Server s:
```
 ./adminctl start
 ./apachectl -k stop
 ./apachectl -k start
```
Wait until a confirmation message is displayed; for example:
```
PLGC0062I: The plug-in configuration file is propagated from /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/servernameCell01/nodes/webserver1/servers/webserver1/plugin-cfg.xml to /opt/IBM/HTTPServer/Plugins/config/webserver1/plugin-cfg.xml.
```
The message identifies where the plugin-cfg.xml file is on the system that hosts IBM HTTP Server. In this example, the file path is: /opt/IBM/HTTPServer/Plugins/config/webserver1/plugin-cfg.xml.
Log on to the system that hosts IBM HTTP Server and open the plugin-cfg.xml file.

Verify the URIs for the installed IBM Connections applications are present. For example:

<UriGroup Name="default_host_Cluster1_URIs">      
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/activities/*"/>      
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/activities/quickrpicker/*"/>      
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/communities/*"/>      
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/communities/calendar/*"/>      
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/communities/recomm/*"/>      
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/forums/*"/>      
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/metrics/service/*"/>      
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/metrics/*"/>      
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/profiles/*"/>      
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/profiles/seedlist/*"/>   
</UriGroup>

If the IBM Connections URIs are not present, complete the steps in the Mapping applications to IBM HTTP Server topic.

Add certificates to the WebSphere trust store

Import a self-signed IBM HTTP Server certificate into the default trust store of IBM WAS.

Before you complete this procedure, ensure that IBM HTTP Server is configured to support SSL.

This topic describes the procedure to configure certificates in a deployment with one webserver.

To establish trusted server to server communication for IBM Connections, import signer certificates from IBM HTTP Server into the WAS default trust store.

There are different types of certificates that you can use. This procedure describes how to import a self-signed certificate. You can also import a certificate that you purchased from a third-party Certificate Authority. To help decide a key file strategy for your environment, go the IBM HTTP Server information center.

To import a public certificate from IBM HTTP Server to the default trust store in IBM WAS, complete the following steps:

Log into the IBM WAS Integrated Solutions Console and select Security > SSL Certificate and key management > Key stores and certificates.
Click CellDefaultTrustStore.
Click Signer Certificates.
Click Retrieve from port.
Enter the Host name, SSL Port, and Alias of the webserver.
Click Retrieve Signer Information and then click OK. The root certificate is added to the list of signer certificates.

Results

If your configuration changes aren't successful, ensure that you have applied the instructions to configure a default personal certificate.

What to do next

Verify that users can create a private community and add other widgets, such as Activities, Blogs, Dogear, and so on, to it. Ensure that there are no errors when these widgets are added. If problems are reported, consult the Communities SystemOut.log file.

The proxy-config.tpl file allows a proxy to work with self-signed certificates. This is true for an out-of-the-box deployment but for improved security you should set the value of the unsigned_ssl_certificate_support property to false when your deployment is ready for production.

Ensure that you are ready to renew your certificate before it expires. WAS provides a utility for monitoring certificates.

Add certificates to IBM HTTP Server

Add signer certificates to an IBM HTTP Server plug-in.

Before you complete this procedure, ensure that IBM HTTP Server is configured to support SSL.

To establish trusted communication between IBM HTTP Server and a web browser, import signer certificates from WAS.

There are different types of certificates that you can use. This procedure describes how to import the self-signed certificate that is shipped with WAS. You can also import a certificate that you purchased from a third-party Certificate Authority, or create a new self-signed certificate. To import a public WAS certificate into the IBM HTTP Server plug-in:

Copy the plugin-key.kdb file from the ibm_http_server_root/Plugins/config/webserver1 directory to the app_server_root/profiles/AppSrv01/config/cells/cell_name/nodes/node_name/servers/webserver_name directory.
where cell_name, node_name, and webserver_name are the names of your WAS cell, the name of the node that you are configuring, and your web server.
Log into the IBM WAS Integrated Solutions Console and select Security > SSL Certificate and key management > Key stores and certificates.
Click CellDefaultTrustStore.
Click Personal Certificates.
Select the check box beside the default certificate and click Extract.
Enter a fully-qualified Certificate file name. If you do not specify a directory path, the certificate is stored in the app_server_root/profiles/profile_name/etc directory, where profile_name is the name of the current WAS profile.
Click OK to extract the file.
In the IBM WAS Integrated Solutions Console, select Servers > Server Types > Web servers.
Click webserver_name, where webserver_name is the name of your IBM HTTP Server web server.
Click Plug-in properties and then click Manage keys and certificates.
Under Additional Properties, click Signer certificatesand then click Add.
Enter the certificate Alias and its fully-qualified File nameand then click OK.
Click Save to import the file.
In the IBM WAS Integrated Solutions Console, select Servers > Server Types > Web servers > webserver_name > Plug-in properties.
Click Copy to web server key store directory to synchronize the KDB file with IBM HTTP Server.
To apply the changes, restart IBM HTTP Server.

Results

If your configuration changes are not successful, ensure that you have applied the instructions to configure a default personal certificate.

What to do next

The proxy-config.tpl file allows the proxy to work with self-signed certificates. For improved security, set the value of the unsigned_ssl_certificate_support property to false when your deployment is ready for production.

Determine which files to compress

If you are not compressing content with the IBM WAS Edge components or a similar device, configure the IBM HTTP Server to compress certain types of content to improve browser performance.

This is an optional configuration. You do not need to perform this procedure if you are compressing content elsewhere in your network. Compression requires a significant amount of CPU; you must monitor resource availability if you choose to use this option. The directives discussed here do not compress images, but do compress JavaScript.

To specify which types of files to compress:

Use a text editor, open the httpd.conf file. The file is stored in the following directory by default:
- AIX: /usr/IBM/HTTPServer/conf
- Linux: /opt/IBM/HTTPServer/conf
- Microsoft Windows:: C:\IBM\HTTPServer\conf
Find the following entry in the configuration file:
```
LoadModule deflate_module modules/mod_deflate.so
```
If this entry is not present, add it.

Add the following statements to compress multiple content types used by IBM Connections:

#Only the specified MIME types will be compressed.

AddOutputFilterByType DEFLATE application/atom+xml
AddOutputFilterByType DEFLATE application/atomcat+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/json
AddOutputFilterByType DEFLATE application/octet-stream
AddOutputFilterByType DEFLATE application/x-javascript
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/javascript
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/xsl

Add the following statement to specifically indicate that image files and binaries must not be compressed to prevent web browser hangs:

# Ensures that images and executable binaries are not compressed
SetEnvIfNoCase Request_URI \\.(?:gif|jpe?g|png|exe)$ no-gzip dont-vary

Add the following statement to ensure that proxy servers do not modify the User Agent header needed by the previous statements:
```
# Ensure that proxies do not deliver the wrong content
Header append Vary User-Agent env=!dont-vary
```
If the following line is commented out, remove the commenting from it:
```
LoadModule headers_module modules/mod_headers.so
```
Save and close the configuration file.
Restart IBM HTTP Server.

Update web addresses in IBM HTTP Server

Update the web addresses that IBM HTTP Server uses to access IBM Connections applications.

Before continuing with this task, map the application modules to IBM HTTP Server.

If you are using the Files or Wikis applications, configure IBM HTTP Server to handle file downloads from those applications.

If you choose to let the WAS redirect servlet manage file downloading, configure the server to transfer data synchronously instead of asynchronously. This configuration helps avoid errors caused by using too much memory. See the Excessive native memory use in IBM WAS technote for instructions.

If you do not install a web server such as IBM HTTP Server, users must include the correct port in the web address that they use to access the application. When you use a webserver, users can access the applications without using port numbers.

By default, the web address that you enter to access IBM Connections applications includes the port number for each application. To avoid using ports, update the web addresses by editing LotusConnections-config.xml. IBM HTTP Server can then redirect requests to the appropriate port for each application.

To update the web addresses to your IBM Connections applications, complete the following steps:

Stop WAS.
Check out LotusConnections-config.xml. The file is stored by default in the following directory:
- AIX: /usr/IBM/WebSphere/AppServer/profiles/profile_name/config/cells/cell_name/LotusConnections-config
- Linux: /opt/IBM/WebSphere/AppServer/profiles/profile_name/config/cells/cell_name/LotusConnections-config
- Windows: C:\IBM\WebSphere\AppServer\profiles\profile_name\config\cells\cell_name\LotusConnections-config
For each application, update the web addresses specified in the href and ssl_href properties:
```
<sloc:href>
<sloc:hrefPathPrefix>/application</sloc:hrefPathPrefix>
<sloc:static
href="http://webserver:port"
ssl_href="https://webserver:port">
<sloc:interService 
href="https://webserver:port">
</sloc:href>
```
where
- webserver is the domain name of IBM HTTP Server, such as webserver.example.com.
- port is the default port of the application. Remove the port when you specify a webserver.
- application is the name of an IBM Connections application.
Each href attribute in LotusConnections-config.xml is case-sensitive and must specify a fully-qualified domain name.
For example, to update the web address for Communities, add the following specifications to the file:
```
<sloc:href> 
<sloc:hrefPathPrefix>/communities</sloc:hrefPathPrefix> 
<sloc:static href="http://webserver.example.com" 
ssl_href="https://webserver.example.com"> 
<sloc:interService  href="https://webserver.example.com"> 
</sloc:href>
```
To use a reverse proxy, the web addresses defined in this file must be updated to match the appropriate proxy server URLs. Go to the IBM Connections wiki for more information about deployment scenarios, including how to configure a reverse proxy.
Save and check in LotusConnections-config.xml.
Synchronize the nodes.
Log on to each application to ensure that the web addresses in the navigation bar are correct.

Results

You can access each application without needing to specify a port.

Configure the Home page administrator

Create an administrator for Home page so that you can make changes to the application such as adding and removing widgets.

IBM Connections administrators must be dedicated users. Their only purpose should be application administration.

Only a Home page administrator can add, remove, enable, or disable widgets on the Home page.

You can also create global administrators for any of the applications, for the purpose of managing content.

To configure administrative access to the Home page application, complete the following steps:

Log in to the WAS Integrated Solutions Console on the Deployment Manager.
Select Applications > Application Types > WebSphere enterprise applications.
Click the link to the Home page application.
Click the Security role to user/group mapping link.
Select the check box beside the admin role and then click Map Users.
In the Search String box, type the name of the person whom you would like to set as an administrator, and then click Search. If the user name exists in the LDAP directory, it is found and displayed in the Available box.
Select the name from the Available box and then move it into the Selected column by clicking the right arrow button.
Repeat Steps 4 and 5 to add more users to the administrative role.
Click OK.
From the Enterprise Applications > <application> > Security role to user/group mapping page, click OK and then click Save.
Synchronize and restart all your WAS instances.

Enable Search dictionaries

During installation, only the English language dictionary is enabled by default. When your organization spans multiple geographies and multiple languages, you need to enable the relevant language dictionaries for your deployment to ensure that Search returns optimum results for your users.

For non-English deployments, enabling multilingual support for Search is a mandatory post-installation step that needs to be performed before you start your IBM Connections Search server for the first time. Without multiple dictionary support, for languages other than English, Search only returns results where there is an exact match between the search term and content term. Enabling multiple dictionaries ensures better quality search results when your user base is multilingual.

For information about how to enable multilingual support, see Configuring dictionaries for Search.

Database item	Example	Details
Database type and version	Oracle Database 10g Enterprise Edition Release 2 10.2.0.4
Database instance or service name
Database server host	DB.example.com
Port	DB2=50000 Oracle=1433 MS SQL Server=1523
JDBC driver fully qualified file path	C:\IBM\SQLLIB
Database client name and version	MS SQL Server Management Studio Express® v9.0.2
Database client UID	db2admin
Database client user password
DB2 administrators group (Windows only)	DB2ADMNS
DB2 users group (Windows only)	DB2USERS
Activities DB server host
Activities DB server port
Activities DB name.	OPNACT
Activities DB application UID
Activities DB application user password
Blogs DB server host
Blogs DB server port
Blogs DB name.	BLOGS
Blogs DB application UID
Blogs DB application user password
Cognos DB server host
Cognos DB server port
Cognos DB name.	COGNOS
Cognos DB application UID
Cognos DB application user password
Communities DB server host
Communities DB server port
Communities DB name	SNCOMM.
Communities DB application UID
Communities DB application user password
Dogear DB server host
Dogear DB server port
Dogear DB name.	DOGEAR.
Dogear DB application UID
Dogear DB application user password
Files DB server host
Files DB server port
Files DB name.	FILES.
Files DB application UID
Files DB application user password
Forums DB server host
Forums DB server port
Forums DB name.	FORUM.
Forums DB application UID
Forums DB application user password
Home page DB server host
Home page DB server port
Home page DB name.	HOMEPAGE.
Home page DB application UID
Home page DB application user password
Metrics DB server host
Metrics DB server port
Metrics DB name.	METRICS.
Metrics DB application UID
Metrics DB application user password
Mobile DB server host
Mobile DB server port
Mobile DB name.	MOBILE.
Mobile DB application UID
Mobile DB application user password
Profiles DB server host
Profiles DB server port
Profiles DB name.	PEOPLEDB.
Profiles DB application UID
Profiles DB application user password
Wikis DB server host
Wikis DB server port
Wikis DB name.	WIKIS
Wikis DB application UID
Wikis DB application user password

IBM Connections item	Example	Details
IBM Connections installation location	C:\IBM\Connections
Response file directory path.	C:\IBM\Connections\InstallResponse.txt
DNS host	connections.example.com
Choose: DNS MX Records or Java Mail Session?
DNS MX Records only: Local mail domain	example.com
Java Mail Session only: DNS server name or SMTP relay host	dns.example.com; relayhost.example.com
Domain name for Reply-to email address
Suffix or prefix for Reply-to email address
Server that receives Reply-to emails
User name and password for that server
URL and ports for admin and user access	You can look up the URLs for each application in the text files that the installation wizard generates under connections_root
Activities server name
Activities cluster member name
Activities URL	http://www.example.com:9080/activities
Activities secure URL	https://www.example.com:9446/activities
Activities statistics files directory path
Activities content files directory path
Blogs server name
Blogs cluster member name
Blogs URL	http://www.example.com:9080/blogs
Blogs secure URL	https://www.example.com:9446/blogs
Blogs upload files directory path
Bookmarks server name
Bookmarks cluster member name
Bookmarks URL	http://www.example.com:9080/dogear
Bookmarks secure URL	https://www.example.com:9446/dogear
Bookmarks favicon files directory path
Communities server name
Communities cluster member name
Communities URL	http://www.example.com:9080/communities
Communities secure URL	https://www.example.com:9446/communities
Communities statistics files directory path
Communities discussion forum content directory path
Files server name
Files cluster member name
Files URL	http://www.example.com:9080/files
Files secure URL	https://www.example.com:9446/files
Files content store directory path
Forums server name
Forums cluster member name
Forums URL	http://www.example.com:9080/forums
Forums secure URL	https://www.example.com:9446/forums
Forums content store directory path
Home page server name
Home page cluster member name
Home page URL	http://www.example.com:9080/homepage
Home page secure URL	https://www.example.com:9446/homepage
Home page content store directory path
Metrics server name
Metrics cluster member name
Moderation server name
Moderation cluster member name
Moderation URL	http://www.example.com:9080/moderation
Moderation secure URL	https://www.example.com:9446/moderation
Profiles server name
Profiles cluster member name
Profiles URL	http://www.example.com:9080/profiles
Profiles secure URL	https://www.example.com:9446/profiles
Profiles statistics files directory path
Profiles cache directory path
Search server name
Search cluster member name
Search dictionary directory path
Search index directory path
Wikis server name
Wikis cluster member name
Wikis URL	http://www.example.com:9080/wikis
Wikis secure URL	https://www.example.com:9446/wikis
Wikis content directory path

Display name	The cn LDAP attribute is used to display a person's name in the product user interface.
Log in	Attribute or attributes to log in to IBM Connections. For example: uid. The login name must be unique in the LDAP directory.
Messaging	Optional. Attribute to use to define the email address of a person. The email address must be unique in the LDAP directory. If a person does not have an email address and does not have an LDAP attribute that represents the email address, that person cannot receive notifications.
Global unique identifier	Attribute to use as the unique identifier of each person and group in the organization. Must be unique across the organization.

Directory Type	Directory service from the available vendors and versions.
Primary host
Port
Bind distinguished name
Bind password
Certificate mapping
Certificate filter, if applicable.
LDAP entity types or classes	LDAP object classes. For example, select the LDAP inetOrgPerson object class for the Person Account entity, or the LDAP groupOfUniqueNames object class for the Group entity.
Search base	Distinguished name (DN) of the LDAP subtree as the search scope. For example, select o=ibm.com to allow all directory objects underneath this subtree node to be searched. For example: Group, OrgContainer, PersonAccount, or inetOrgPerson

Operating system	Fix pack
AIX	10.1.1-BA-CBI-AIX64-FP001
Linux	10.1.1-BA-CBI-Linuxi38664-FP001
Windows	10.1.1-BA-CBI-Win64-FP001
zLinux	10.1.1-BA-CBI-zLinux64-FP001

Activities	Collaboration tool for collecting, organizing, sharing, and reusing work related to a project goal.
Blogs	Online journals used to deliver timely information with a personal touch.
Bookmarks	Social bookmarking tool for saving, organizing, and sharing Internet and intranet bookmarks. Previously named Dogear.
Communities	A website where people who share a common interest can interact with one another, share information, and exchange ideas. Community members can participate in community-specific activities and forums, and can share blogs, bookmarks, feeds, and files.
Files	A common repository in which you can upload files and share them with others. Store versions of a file, view who has downloaded a file or commented on it, and see highly recommended files.
Forums	A place to brainstorm and collect feedback on topics that are relevant to you and your colleagues. Statements and comments are collected in a format that captures the exchange of ideas and presents them as an ongoing conversation.
Home page	A central location that provides a snapshot of the latest updates collected from IBM Connections. Perform in-context actions on entries in your activity stream, check the latest updates from the content and people that you are following, stay up to date with the latest notifications and updates that require a response from you, or post your own status updates.
Profiles	Directory of the people in your organization, including the information you need to form and encourage effective networks across your organization.
Metrics	Statistics tool that collects and displays information about how people use Connections applications. Community metrics show details on a particular community while global metrics show information across all of Connections.
Wikis	A tool for creating wikis that individuals, groups, and communities can use to capture, share, and coauthor information. View page changes, recommendations, and comments.

IBM Tivoli Directory Server	ibm-entryUUID
Microsoft Active Directory	objectGUID For AD, the samAccountName attribute has a 20-character limit; other IDs used by IBM Connections have a 256-character limit.
IBM Domino Enterprise Server	dominoUNID If the bind ID for the Domino LDAP does not have sufficient manager access to the Domino directory, the Virtual Member Manager (VMM) does not return the correct attribute type for the Domino schema query; DN is returned as the VMM ID. To override VMM's default ID setting, add the following line to the <config:attributeConfiguration> section of the wimconfig.xml file: <config:externalIdAttributes name="dominoUNID"/>
Sun Java System Directory Server	nsuniqueid
eNovell Directory Server	GUID
Custom ID	If your organization already uses a unique identifier for each user and group, you can configure IBM Connections to use that identifier.

Property Name	Description
commonear.ClusterName	Desired cluster name for Common.
commonear.FirstNodeName	Name of first node of the cluster.
commonear.SecondaryNodesNames	Comma-delimited list of secondary node names.
commonear.<FirstNodeName>.ServerName	Name of the server on the first node, note that the <FirstNodeName> needs to be an actual name.
commonear.<SecondaryNodesNames1>.ServerName	Name of the server on the secondary node 1, note that the <SecondaryNodesNames1> needs to be an actual name.
...	...
commonear.<SecondaryNodesNamesN>.ServerName	Name of the server on the secondary node n, note that the <SecondaryNodesNamesN> needs to be an actual name.

Property	Description
widgetcontainer.ClusterName	Desired cluster name for the WidgetContainer.
widgetcontainer.FirstNodeName	Name of first node of the cluster.
widgetcontainer.SecondaryNodesNames	Comma-delimited list of secondary node names.
widgetcontainer.<FirstNodeName>.ServerName	Name of the server on the first node, note that the <FirstNodeName> needs to be an actual name.
widgetcontainer.<SecondaryNodesNames1>.ServerName	Name of the server on the secondary node 1, note that the <SecondaryNodesNames1> needs to be an actual name.
...	...
widgetcontainer.<SecondaryNodesNamesN>.ServerName	Name of the server on the secondary node n, note that the <SecondaryNodesNamesN> needs to be an actual name.

Customization	Automatically migrated	Migrate manually
User interface (customized CSS, JSP, and HTML; labels and strings). Customized string files are preserved in the customization directory but you might need to rename some string files to match new Java and Dojo package names in IBM Connections 4.0. Custom CSS files are preserved in the customization directory but you must update them to match the new OneUI version in IBM Connections 4.0.	Partially.	Yes.
Template configuration Manual post-migration steps may be required, see the Post-migration steps for profile types and profile policies topic .	Partially.	See the post-migration steps.
Header and Footer The customized header and footer are preserved in the customization directory, which is not migrated. You must update your customized header and footer to match the new layout and functionality of IBM Connections 4.0.	No.	Yes.
Email notification templates. Email notification templates have been translated from JSP to FreeMarker. Merge your existing customizations with the new Notification templates in the profile_root/Dmgr01/config/cells/cell_name/LotusConnections-config/notifications directory. If a global customization exists for all emails, then you only need to customize the shared resources. If JSP templates were customized in the 3.0.1 customization folders - you can remove them.	No.	Yes.
Blog themes	Partially.	Yes.
Community themes The default Communities themes are migrated automatically. However, must redefine any custom theme.	Yes	Redefine any custom themes.
Business cards The Links and Actions attributes of business cards are migrated when the LotusConnections-config.xml and profiles-config.xml are migrated. Link definitions defined as attributes to each service in the LCC.xml file are migrated to the new LCC.xml file. The photo and contact information in business cards is migrated from the profiles-config.xml file in 3.0.1 to the new businessCardInfo.ftl FreeMarker Template Language file in 4.0. Other elements in the profiles-config.xml file are migrated to the new profiles-config.xml file. Manual steps may also be required to migrate profile customizations for business cards from 3.0.1 as described in the Post-migration steps for profile types and profile policies topic.	Yes.	Partially.
Security role mappings. Redefine your security role mappings.	No.	Yes.
service-location.xsd Customized extended service names are not migrated. Copy any customized XSD elements to the 4.0 service-location.xsd file.	Partially.	Yes.
profiles-policy.xml Copy the 3.0.1 version of profiles-policy.xml file to the 4.0 deployment, overwriting the 4.0 version of the file.	No.	Yes.
validation.xml Redefine customized Profile field validation settings.	No	Yes.
JavaScript The file path and contents of JavaScript string customizations have changed and require manual migration. The ui-extensions framework is deprecated in 4.0 so manually migrate your 3.0.1 JavaScript customizations.	No.	Yes
IBM Connections Connector for Lotus Quickr®. The IBM Connections Connector for Lotus Quickr was updated for IBM Connections 4.0. You must obtain the 4.0 version from the catalog.	No.	Reinstall the connector.
Server whitelist for publishing file attachments from Activities to Lotus Quickr.	No.	Redefine the whitelist.

Application	Directory	DB2 commands
Activities	/connections.sql/activities/db2	db2 -tvf predbxfer301.sql
Blogs	/connections.sql/blogs/db2	db2 -td@ -vf predbxfer301.sql
Bookmarks	/connections.sql/dogear/db2	db2 -td@ -vf predbxfer301.sql
Communities	/connections.sql/communities/db2	db2 -td@ -vf predbxfer301.sql
Files	/connections.sql/files/db2	db2 -td@ -vf predbxfer301.sql
Forum	/connections.sql/forum/db2	db2 -tvf predbxfer301.sql
Home page	/connections.sql/homepage/db2	db2 -tvf predbxfer301.sql
Profiles	/connections.sql/profiles/db2	db2 -tvf predbxfer301.sql
Wikis	/connections.sql/wikis/db2	db2 -td@ -vf predbxfer301.sql

Application	Directory	Oracle commands
Activities	/connections.sql/activities/oracle	@predbxfer301.sql
Blogs	/connections.sql/blogs/oracle	@predbxfer301.sql
Bookmarks	/connections.sql/dogear/oracle	@predbxfer301.sql
Communities	/connections.sql/communities/oracle	@predbxfer301.sql
Files	/connections.sql/files/oracle	@predbxfer301.sql
Forum	/connections.sql/forum/oracle	@predbxfer301.sql
Home page	/connections.sql/homepage/oracle	@predbxfer301.sql
Profiles	/connections.sql/profiles/oracle	@predbxfer301.sql
Wikis	/connections.sql/wikis/oracle	@predbxfer301.sql

Application	Directory	SQL Server commands
Activities	/connections.sql/activities/sqlserver	sqlcmd -U sa -P password -i "predbxfer301.sql"
Blogs	/connections.sql/blogs/sqlserver	sqlcmd -U sa -P password -i "predbxfer301.sql"
Bookmarks	/connections.sql/dogear/sqlserver	sqlcmd -U sa -P password -i "predbxfer301.sql"
Communities	/connections.sql/communities/sqlserver	sqlcmd -U sa -P password -i "predbxfer301.sql"
Files	/connections.sql/files/sqlserver	sqlcmd -U sa -P password -i "predbxfer301.sql"
Forum	/connections.sql/forum/sqlserver	sqlcmd -U sa -P password -i "predbxfer301.sql"
Home page	/connections.sql/homepage/sqlserver	sqlcmd -U sa -P password -i "predbxfer301.sql"
Profiles	/connections.sql/profiles/sqlserver	sqlcmd -U sa -P password -i "predbxfer301.sql"
Wikis	/connections.sql/wikis/sqlserver	sqlcmd -U sa -P password -i "predbxfer301.sql"

Application	Directory	DB2 commands
Activities	/connections.sql/activities/db2	db2 -tvf postdbxfer301.sql db2 -tvf clearScheduler.sql
Blogs	/connections.sql/blogs/db2	db2 -td@ -vf postdbxfer301.sql
Bookmarks	/connections.sql/dogear/db2	db2 -td@ -vf postdbxfer301.sql
Communities	/connections.sql/communities/db2	db2 -td@ -vf postdbxfer301.sql db2 -td@ -vf clearScheduler.sql
Files	/connections.sql/files/db2	db2 -td@ -vf postdbxfer301.sql db2 -td@ -vf clearScheduler.sql
Forum	/connections.sql/forum/db2	db2 -tvf postdbxfer301.sql db2 -td@ -vf clearScheduler.sql
Home page	/connections.sql/homepage/db2	db2 -tvf postdbxfer301.sql db2 -tvf clearScheduler.sql
Profiles	/connections.sql/profiles/db2	db2 -tvf postdbxfer301.sql db2 -tvf clearScheduler.sql
Wikis	/connections.sql/wikis/db2	db2 -td@ -vf postdbxfer301.sql db2 -td@ -vf clearScheduler.sql

Application	Directory	Oracle commands
Activities	/connections.sql/activities/oracle	@postdbxfer301.sql @clearScheduler.sql
Blogs	/connections.sql/blogs/oracle	@postdbxfer301.sql
Bookmarks	/connections.sql/dogear/oracle	@postdbxfer301.sql
Communities	/connections.sql/communities/oracle	@postdbxfer301.sql @clearScheduler.sql
Files	/connections.sql/files/oracle	@postdbxfer301.sql @clearScheduler.sql
Forum	/connections.sql/forum/oracle	@postdbxfer301.sql @clearScheduler.sql
Home page	/connections.sql/homepage/oracle	@postdbxfer301.sql @clearScheduler.sql
Profiles	/connections.sql/profiles/oracle	@postdbxfer301.sql @clearScheduler.sql
Wikis	/connections.sql/wikis/oracle	@postdbxfer301.sql @clearScheduler.sql

Application	Directory	SQL Server commands
Activities	/connections.sql/activities/sqlserver	sqlcmd -U sa -P password -i "postdbxfer301.sql" sqlcmd -U sa -P password -i "clearScheduler.sql"
Blogs	/connections.sql/blogs/sqlserver	sqlcmd -U sa -P password -i "postdbxfer301.sql"
Bookmarks	/connections.sql/dogear/sqlserver	sqlcmd -U sa -P password -i "postdbxfer301.sql"
Communities	/connections.sql/communities/sqlserver	sqlcmd -U sa -P password -i "postdbxfer301.sql" sqlcmd -U sa -P password -i "clearScheduler.sql"
Files	/connections.sql/files/sqlserver	sqlcmd -U sa -P password -i "postdbxfer301.sql" sqlcmd -U sa -P password -i "clearScheduler.sql"
Forum	/connections.sql/forum/sqlserver	sqlcmd -U sa -P password -i "postdbxfer301.sql" sqlcmd -U sa -P password -i "clearScheduler.sql"
Home page	/connections.sql/homepage/sqlserver	sqlcmd -U sa -P password -i "postdbxfer301.sql" sqlcmd -U sa -P password -i "clearScheduler.sql"
Profiles	/connections.sql/profiles/sqlserver	sqlcmd -U sa -P password -i "postdbxfer301.sql" sqlcmd -U sa -P password -i "clearScheduler.sql"
Wikis	/connections.sql/wikis/sqlserver	sqlcmd -U sa -P password -i "postdbxfer301.sql" sqlcmd -U sa -P password -i "clearScheduler.sql"

Directory	Permissions	Command
app_server_root	RWX	chown -R non-root_user app_server_root
connections_root	RWX	chown -R non-root_user connections_root
data_directory_root	RWX	chown -R non-root_user data_directory_root
path/tmp/efixes	RWX	chown -R non-root_user tmp/efixes

Overview - IBM Connections v4

What's new in IBM Connections 4?

What's new in installing?

What's new in administering?

What's new in customizing?

What's new in security?

What's new in mobile?

What's new in developing?

What's new in troubleshooting and support?

Supported languages

Related tasks

Administrators: Deploying a preview guide to your users

Accessibility

IBM Connections user interface

Plan

Directory path conventions

Deployment options

IBM Connections system requirements

IBM Connections support statement

Worksheet for installing IBM Connections

Recording installation data

LDAP server details

WAS details

Database details

Tivoli Directory Integrator details

LDAP-Profiles mapping details

IBM Connections details

IBM HTTP Server

Cognos BI Server and Transformer

IBM Connections release notes

Contents

Install IBM Connections 4

Known problems

Install

New for IBM Connections 4.0 install

Migrate to this release

The installation process

Accessibility applications for installing IBM Connections

Use the wizards

Pre-installation tasks

Prepare to configure the LDAP directory

Create the Cognos administrator account

Install IBM WAS

Install and configure WAS

Set up federated repositories

Set up federated repositories in WAS

Results

Choose login values

Multi-valued attributes

Custom attributes

Use Profiles or LDAP as the repository

Set the global ID attribute for users and groups

Specify a custom ID attribute for users or groups

What to do next

Create DBs

Create multiple DB instances

What to do next

Register the DB2 product license key

What to do next

Create a dedicated DB2 user

Configure the DB2 DBs for unicode

Create DBs with the DB wizard

Prepare the DB wizard

Use the DB wizard

What to do next

Use the DB wizard in silent mode

What to do next

The DB wizard response file

Create DBs with SQL scripts

Create IBM DB2 DBs manually

What to do next

Create Oracle DBs manually

Create SQL Server DBs manually

What to do next

Enable NO FILE SYSTEM CACHING for DB2 on System z

Populate the Profiles DB

Related

Configure Tivoli Directory Integrator

Related tasks