Install in console mode

Install in console mode

Overview

Use console mode to complete the installation process in a non-graphical environment.
Complete all the prerequisite tasks.
We can find part numbers for this release on the Download IBM Connections 5.0 page.
We can type P at to return to the previous input choice in a step. We cannot type P to return to a previous step.

Install Connections in console mode

On each node, stop any running instances of WAS and WebSphere node agents.

Start WAS dmgr.

Copy the installation files to the system hosting the dmgr.

From the dmgr host, start Installation Manager (IIM) in console mode:

cd /opt/IBM/InstallationManager/eclipse/tools/
./imcl -c

To install both IIM and Connections...

cd INSTALL/IM/aix/
./install.console.sh

The batch script calls a response file which contains information about the repositories for both IIM and Connections.

To use another language for the install process...

cd IIM_INSTALL
INSTALL/IM/aix/tools/imcl -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 Connections repository:
If we chose the option to run the install.console.sh file earlier, we can skip this step.

Type P to edit preferences.

Type 1 to specify repositories.

Type D to add a repository.

Type the repository path for Connections 5.0, for example:
Lotus_Connections/repository.xml

Type A to save the repository information.

Type C to return to the console window.

In the step...
Select packages to install
...type the appropriate number 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.

Specify the location of the shared resources directory for IIM.
If we used IIM before, the wizard automatically enters this value. Type N to proceed.

Specify the location of the IIM install directory. Type N to proceed.

Specify the locations of the package group for IIM and the install directory for Connections:

The wizard automatically detects the Connections package group. Type M to change the default location where the package group will be installed.

Type N to proceed.

To accept the default location for the Connections install directory, type N. To specify a new directory name, type M and enter the new directory name and path.

Type N to proceed.

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

Or select individual applications to install...

Activities
Blogs
Communities
Bookmarks
Files
Forums
Content Manager
Metrics
Mobile
Moderation
Profiles
Wikis

Enter the details of the WAS environment:

Select the WAS installation location containing the dmgr.

/opt/IBM/WebSphere/AppServer

Properties of the WAS dmgr:

dmgr profile Name of the dmgr to use for Connections. The wizard automatically detects any available dmgrs.
Host name Name of the host dmgr server.
Administrator ID The administrative ID of the dmgr.
This ID is set to the connectionsAdmin J2C authentication alias, which is mapped to the following Java EE roles:

dsx-admin
widget-admin
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 specified here must exist in the LDAP directory.
This user account needs to be both a WAS admin user and an LDAP user
Administrator Password The password for the administrative ID of the dmgr.
SOAP port The SOAP port number of the dmgr. The wizard automatically detects this value.

Press Enter to verify the dmgr information.
The verification process checks that application security is enabled on WAS. If the verification fails, IIM displays an error message.
(AIX and Linux) The validation process checks the number of open files supported by the system. If the value for 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 limit before restarting the wizard. To set the file limit, refer to the Installation error messages.and search for error code CLFRP0042E. The recommended value for Connections is 8192.

If the verification check is successful, type N to proceed. If verification fails, press B to reenter the required information.

The wizard creates file...
WAS_HOME/dmInfo.properties
...to record details of the cell, node, and server.

Configure the Connections Content Manager deployment option.
This panel displays if you chose to install the CCM feature.

Select 1 to use a new FileNet deployment for CCM.

Enter the FileNet installer packages location.
The four FileNet installers need to be placed into the same folder...

Content Platform Engine
FileNet Collaboration Services
FileNet fix pack
Content Platform Engine Client

Press Enter to validate whether the correct installers could be found.

Select 2 to use an existing FileNet deployment for CCM.

Enter the User Id for the FileNet Object Store administrator username.

Enter password for the FileNet Object Store administrator password.

Enter the HTTP URL for the FileNet Collaboration Services server:
http://fncs.myco.com:80/dm

Enter the HTTPS URL for the FileNet Collaboration Services server:
https://fncs.myco.com:443/dm

Press Enter to validate.
We can still continue even if the validation failed. If we are sure that correct information has been specified, then the FileNet server might not be available. Type N to continue; otherwise type B to reenter the information.

Configure the topology.
If we chose to use existing deployment of FileNet for Connections Content Manager, the application CCM will not show in this topology panel.

Small deployment:

Type 1 to select the Small deployment topology.

Enter a cluster name for the topology.

Select a Node.

Enter a Server member name for the node.

Type N to proceed.

Medium deployment:

Type 2 to select the Medium deployment topology.

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.
IIM creates servers and clusters when required.

Select a Node for each cluster. Accept the predefined node or select a different node.
These nodes host application server instances that serve Connections applications. We can assign multiple nodes to a cluster, where each node is a server member of that cluster.

Enter a Server member name for the selected node.
The name must be unique across all nodes in the deployment.

The topology specified is displayed.
To re-specify any details, type the number that corresponds to the application; for example, type 1 for Activities.

Type N to proceed.

Large deployment:

Type 3 to select the Large deployment topology.

Enter a Cluster name for each application.
IIM creates servers and clusters when required.

Select a Node for each cluster. Accept the predefined node or select a different node.
These nodes host application server instances that serve Connections applications. We can assign multiple nodes to a cluster, where each node is a server member of that cluster.

Enter a Server member name for the selected node.
The name must be unique across all nodes in the deployment.

The topology specified is displayed.
To re-specify any details, type the number that corresponds to the application; for example, type 1 for Activities.

Type N to proceed.

The Connections Content Manager databases will not be shown if you have chosen to use an existing FileNet deployment.
Database information for Global Configuration Data and Object Store must be set correctly, otherwise installation will fail. Enter the database information:

Specify whether the installed applications use the same database server or instance:

Type 1 to specify the applications use same database server or instance
Type 2 to specify they use different database servers or instances.

If allowed by the database configuration, we can select multiple database instances as well as different database servers.

Select a Database type from one of the following options: If installing on Windows, Linux, or AIX:

IBM DB2 Universal Database
Oracle Enterprise Edition
Microsoft SQL Server Enterprise Edition

Enter the Database server host name. For example: appserver.enterprise.myco.com
If the installed applications use different database servers, enter the database host name for each application.

Enter the Port number of the database server. The default values are: 50000 for DB2 , 1521 for Oracle, and 1433 for SQL Server.

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

Ensure the following JDBC driver libraries are present in the JDBC directory:

DB2 db2jcc4.jar and db2jcc_license_cu.jar. Ensure the 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.

Enter the User ID and Password for each database.
If each database uses the same user credentials, confirm the Use the same password for all applications question and then enter the user ID and password for the first database in the list.
If the database type is Oracle, we must connect to the database with the user ID used when we created the application database.

If make changes, type the number that corresponds to the application to change.
Alternatively, type R to reset all the database specifications to their default values.

Press Enter to verify the database settings.
If the validation fails, check the database settings. When the validation succeeds, click Next.
IIM tests the database connection with the database values that you supplied. We can change the database configuration later in the WAS console.
Usually we can continue even if the validation failed because we can change the database settings from WAS console afterwards. However, we cannot continue if you have entered incorrect information for the Connections Content Manager database, because there are database operations during installation. Incorrect database information will cause installation to fail. So use correct information for Connections Content Manager database.

If the verification check is successful, type N to proceed. If verification fails, press B to reenter the required information.

Select the Do Later option, and configure Cognos later through the Cognos Wizard.

Specify 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 dmgr. Local content is node-specific. Each content store is represented by a corresponding WebSphere variable that is further defined as shared or local.
For migrations from IBM Connections 4.5, reuse your existing content stores in 5.0 in order to maintain data integrity.

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 dmgr 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)

For a shared-file system on Windows, specify the file location using the Universal Naming Convention (UNC) format. For example:
\\server_name\share_name

(Windows only) If we use Remote Desktop Connection to map shared folder drives, use the same session to start the node agents. Otherwise, the shared drives might be invisible to the nodes.

Enter the location of the Local content store.

Press Enter to verify the account that we are using to install Connections has write access to the content store.

Click Next.

Select a Notification solution.
Notifications are email messages to users about new information and events in the 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, the mail server must be able to receive all the replies and funnel these replies into a single inbox. IBM Connections connects to the mail server using the IMAP protocol.

None.
Do not use a notification solution in the Connections deployment. We can configure notifications after installation. Refer to Configure notifications for more information.

If we 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 we can access an SMTP server directly using the host name.
Identify the mail server to use for sending email:

Host name of SMTP messaging server

Host name 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 user ID.

Password

If the SMTP server requires authentication, enter the user password.

>Encrypt outgoing mail traffic to the SMTP messaging server using SSL

To encrypt outgoing mail to the SMTP server, press Y.

Port

Press Enter to accept the default port of 25, or enter 465 if we are using SSL.

DNS MX Records
Use information from DNS to determine which mail servers to use. Select this option if you use a DNS server to access the SMTP messaging server.

Messaging domain name

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

Host name or IP address of the DNS server.

DNS port used for the messaging servers query

Port number 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

To encrypt outgoing mail to the SMTP server, press Y.

Port

Press Enter to accept the default port of 25, or enter 465 if we are using SSL.

If we specify Do not enable Notification, IIM skips the rest of this step. We can configure notification later.

If we selected the Notification and ReplyTo option, configure the ReplyTo email settings.
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.

Enter a domain name. For example:
mail.myco.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.

The reply email address is given a unique ID by the system. We 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 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 the selection with the ID generated by system.
For example:

unique_id@domain
prefix_unique_id@domain
unique_id_suffix@domain -

Specify the details of the mail file to which ReplyTo emails are sent:

Server Domain where the mail server is located. For example: replyTo.mail.myco.com.
User ID User account for the mail server. The user ID 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 user ID 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.

Type N to proceed.

We can modify the ReplyTo settings after installation. To edit the domain name and prefix or suffix, edit the news-config.xml file. See Post-migration step for status updates topic. To edit the server and authentication details, log in to the WAS console and navigate to the Mail Sessions page, where we can edit the configuration.

Review the information 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 dmgr.

AIX or Linux:
cd app_server_root/profiles/Dmgr01/bin
./stopManager.sh
./startManager.sh

Windows: Stop and restart the dmgr service.

For each node, start the node agent...
Log on to a node and run...
cd profile_root/bin
./startNode.sh

Perform a full synchronization of all nodes.
System administration | Nodes | node | Full Resynchronize

Wait until the dmgr 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 the dmgr has distributed the application EAR files to the nodes, check SystemOut.log of each node agent. The default path to SystemOut.log 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 a Connections application.

Restart the dmgr.

Start all the Connections clusters:
Servers | Clusters | WebSphere Application server clusters | Connections clusters | Start

If we installed a cluster with multiple Search nodes, create the initial index.

If we are installing a non-English language deployment, enable Search dictionaries.

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.

In case the Connections applications are installed on different clusters, the cluster start order should be :

News cluster
Profiles cluster
Search cluster
Dogear cluster
Communities cluster
Activities cluster
Blogs cluster
Files cluster
Forums cluster
Wikis cluster
Hompage cluster
Metrics cluster
Mobile cluster
Moderation cluster
Connections Content Manager cluster

Results

The installation wizard has installed IBM Connections in a network deployment.
To confirm the installation was successful, open the log files in...
connections_root/logs

Each Connections application that you installed has a log file, using the following naming format: application_nameInstall.log, where application_name is the name of a 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...

AIX or Linux (root user):
/var/ibm/InstallationManager/logs

AIX or Linux (non-root user):
/home/user/var/ibm/InstallationManager/logs

Windows Server 2008 64-bit:
C:\ProgramData\IBM\Installation Manager\logs

What to do next

Complete the post-installation tasks that are relevant to the installation.

Access network shares

If we installed WebSphere Application Server on Windows and configured it to run as a service, ensure that we can access network shares.

Parent topic:
Install Connections

Related:
Install Cognos Business Intelligence
Create the initial Search index

dmgr profile	Name of the dmgr to use for Connections. The wizard automatically detects any available dmgrs.
Host name	Name of the host dmgr server.
Administrator ID	The administrative ID of the dmgr. This ID is set to the connectionsAdmin J2C authentication alias, which is mapped to the following Java EE roles: dsx-admin widget-admin 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 specified here must exist in the LDAP directory. This user account needs to be both a WAS admin user and an LDAP user
Administrator Password	The password for the administrative ID of the dmgr.
SOAP port	The SOAP port number of the dmgr. The wizard automatically detects this value.

DB2	db2jcc4.jar and db2jcc_license_cu.jar. Ensure the 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.

None	Use the ID generated by system.
Prefix	Enter a prefix in the Example field.
Suffix	Enter a suffix in the Example field.

Server	Domain where the mail server is located. For example: replyTo.mail.myco.com.
User ID	User account for the mail server. The user ID 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 user ID 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.