Installing 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.
Before you begin
About this task
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:
Procedure
- On each node, stop any running instances of WebSphere® Application Server and WebSphere® node agents.
- Start WebSphere® Application Server Network Deployment Manager.
-
Copy the installation files to the system that hosts the Deployment Manager.
Note: Ensure that the directory path that you enter contains no spaces.
- Start IBM® Installation
Manager in console mode:Note: 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®: IBM_Connections_Install/IM/aix/install.console.sh
- Linux™: IBM_Connections_Install/IM/linux/install.console.sh
- Windows™: IBM_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®: IBM_Connections_Install/IM/aix/tools/imcl -c -nl language_code
- Linux™: IBM_Connections_Install/IM/linux/tools/imcl -c -nl language_code
- Windows™: \IBM 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.
- If Installation Manager is already installed, open a command
prompt and change to the IBM® Installation
Manager installation directory. Then run the following command:
- In the console window, specify the IBM® Connections repository:Note: If you chose the option to run the install.console.bat|sh file in Step 4, you 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 IBM® 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 Select packages to install step, 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 IBM® Installation Manager.
- Enter the location of the Shared Resources Directory.
- Type N to proceed.
Notes:- 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.
- Specify the location of the IBM® Installation
Manager installation directory.
- Enter the location of the Installation Manager Directory.
- Type N to proceed.
Notes:- 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.
- Specify the locations of the package group for IBM® Installation Manager and the
installation directory for IBM® Connections:
- Select the applications that you want to install and then type
N to proceed. You can select from the following options: Important:
- The wizard
always installs the Home page, News, and Search, Common, Files, Push Notification, Rich Text
Editors, and Widget Container applications, which are core features. Note: If you install Communities and want users to be able to add the Rich Content app in a community, you must also install Wikis now.
- Even if you are not planning to configure Cognos® later, 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 5.5 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 web sites. Files Share files among users. Forums Discuss projects and exchange information. Content Manager Use this application to manage files using advanced sharing and draft review in content management libraries in Communities. This application requires the Communities application to be installed. Important: If you choose to install IBM Connections Content Manager, you must also select Communities; otherwise installation quits. These two features need to work together.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. - The wizard
always installs the Home page, News, and Search, Common, Files, Push Notification, Rich Text
Editors, and Widget Container applications, which are core features.
-
Enter the details of your WebSphere® Application
Server environment:
The wizard creates a dmInfo.properties file under WebSphere® Application Server to record details of the cell, node, and server.
- Configure the IBM Connections Content Manager deployment
option.Note: This panel only displays if you chose to install the Connections Content Manager feature.
- Select 1 to use a new FileNet deployment for
Connections Content Manager.
- Enter the FileNet installer packages location. The four FileNet installers: Content Platform
Engine, FileNet Collaboration Services (as part of IBM Content Navigator), the FileNet fix pack, and
Content Platform Engine Client, need to be placed into the same folder.Note: For Connections Content Manager 5.0 CR1, FileNet Collaboration Services is now a component of IBM Content Navigator 2.0.3, and the installer package names reflect this new delivery mechanism.
- Press Enter to validate whether the correct installers could be found.
- Enter the FileNet installer packages location. The four FileNet installers: Content Platform
Engine, FileNet Collaboration Services (as part of IBM Content Navigator), the FileNet fix pack, and
Content Platform Engine Client, need to be placed into the same folder.
- Select 2 to use an existing FileNet deployment for Connections Content Manager.
- Enter the User Id for the FileNet Object Store administrator user name.
- Enter password for the FileNet Object Store administrator password.
- Enter the HTTP URL for the FileNet Collaboration Services server such as: http://fncs.example.com:80/dm.
- Enter the HTTPS URL for the FileNet Collaboration Services serve such as: https://fncs.example.com:443/dm.
- Press Enter to validate. You can still continue even if the validation failed. If you 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.
- Select 1 to use a new FileNet deployment for
Connections Content Manager.
-
Configure your topology. For more information about each option, see Deployment
options.
Note: If you chose to use existing deployment of FileNet for Connections Content Manager, the application Connections Content Manager 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. Note: IBM® Installation Manager creates servers and clusters when required.
- Select a Node for
each cluster. Accept the predefined node or select a different node.Note: 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.
- Enter a Server
member name for the selected node. Choose the default
or enter a custom name.Note: If you enter a custom server member name, the name must be unique across all nodes in your deployment.
- The topology that you 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. Note: IBM® Installation Manager creates servers and clusters when required.
- Select a Node for
each cluster. Accept the predefined node or select a different node.Note: 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.
- Enter a Server
member name for the selected node. Choose the default
or enter a custom name.Note: If you enter a custom server member name, the name must be unique across all nodes in your deployment.
- The topology that you 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.
- Small deployment:
-
Attention: The Connections Content Manager databases will not be shown if you have chosen to use an existing FileNet® deployment.Note: Database information for Global Configuration Data and Object Store must be set correctly, otherwise installation will fail.Enter the database 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 DM. Local content is node-specific. Each content
store is represented by a corresponding WebSphere® variable that is further defined
as shared or local.Note: If you are migrating from IBM® Connections 4.5, you must reuse your existing content stores in 5.0 in order to maintain data integrity. For more information, refer to Content store migration.
- 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. Refer to Configuring notifications for more information.
- Enable Notification only.
- 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 name.
Identify the mail server to use for sending email:- Host name of SMPT messaging server
- Enter the host name of the preferred SMPT 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
- 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 name or IP address of the DNS server.
- DNS port used for the messaging servers query
- Enter the port number 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.
Note: You can modify the ReplyTo settings after installation. To edit the domain name and prefix or suffix, edit the news-config.xml file. To edit the server and authentication details, log in to the WebSphere® Application Server 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 app_server_root/profiles/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:
- Log in
to the Integrated Solutions Console on the DM to perform a full synchronization
of all nodes.
- Go to .
- Select the nodes and click Full Resynchronize.
Note: 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:
- Log in to the Integrated Solutions Console on the DM.
- Navigate to .
- Select the IBM® Connections clusters and click Start.
Note: 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 start with the core features, then move to the other features:- Hompage cluster
- News cluster
- Search cluster
- Common cluster
- Files cluster
- Push Notification cluster
- Rich Text Editor cluster
- Widget Container cluster
The other features include.
- Activities cluster
- Blogs cluster
- Bookmarks cluster
- Communities cluster
- Forums cluster
- Metrics cluster
- Moderation cluster
- Profiles cluster
- Wikis cluster
Results
The installation wizard has installed IBM® Connections in a network deployment.
To confirm that the installation was successful, open the log files in the connections_root/logs directory. Each IBM® Connections application that you 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.
- 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.
Accessing network shares:
If you installed WebSphere® Application Server 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.