Installing HCL Connections 7.0
Install HCL Connections.
Before you begin
Ensure that you complete all the prerequisite tasks that are relevant for your environment. For more information, see the Before installing topic.
About this task
To install HCL Connections, run the IBM® Installation Manager wizard on the system where the Deployment Manager is installed.
- Depending on your database vendor, have a look at your database limitations. In case of Db2, the NUMDB setting might limit the number of databases for your installation, so consider increasing this parameter if needed, especially if you plan to deploy Community Surveys or HCL Docs, which work with their own databases.
- It is best that you change the SOAP Request Timeout in the soap.client.props file to com.ibm.SOAP.requestTimeout=0, to ensure that no requests time out during the installation.
- Make sure that the JVM heap size of your Deployment Manager is high enough to prevent your system from crashing with OutOfMemory errors during the upgrade. At least temporarily, modify the JVM heap size to an initial and maximum value of 2048.
- After making any of the modifications above, restart the Deployment Manager and start the HTTP services afterwards.
Assuming you made any of the modifications suggested, restart the Deployment Manager and then start the HTTP services before you proceed to install Connections.
Procedure
- Start WebSphere® Application Server Network Deployment Manager.
-
Start all the federated nodes using the startNode command. Repeat these
steps for each node:
-
Copy the installation files to the system that hosts the Deployment Manager.
Note: Ensure that the directory path that you enter contains no spaces.
- From the Installation Manager directory, run the file to
start the Installation Manager and add the repository to it as follows:
- AIX® or Linux™: IBMIM
- Windows™: IBMIM.exe
- AIX® or Linux™: Connections set-up\HCL_Connections_Install\HCLConnections\repository.config
- Windows™: Connections set-up\HCL_Connections_Install\HCLConnections\repository.config
Note: Installation Manager might ask you to upgrade the Installation Manager. Connections bundles only the 64-bit, version 1.8.5.1 Installation Manager. - When IBM® Installation
Manager is launched, in the Select packages to install window,
select the packages that you want to install, and then click Next to
continue.Notes:
- Accept the default setting for Show all versions.
- If you are using an earlier version of IBM® Installation Manager than 1.8.5.1, the 1.8.5.1 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.
- Specify the location of the installation directory for HCL Connections. You can accept
the default directory location, enter a new directory name, or click Browse to
select an existing directory. Click Next.
Note: The path must consist of letters (a-z, A-Z), numbers (0-9), and an underscore (_).
- Confirm the applications that you want to install and click Next.
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.
- Install Metrics now so that your application data is captured from the moment that HCL Connections is deployed. If you install Metrics at a later stage, you will not have any data reports for the period before you installed Metrics.
Option Description HCL Connections 7.0 Install all HCL Connections applications. Activities Collaborate with colleagues. Blogs Write personal perspectives about projects. Communities Interact with people on shared projects. Bookmarks Bookmark important websites. Feature Foundation Install software that provides capabilities required for Community Templates* and Export to PDF Forums Discuss projects and exchange information. Metrics Identify and analyze usage and trends. Mobile Access HCL 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. *Community Templates also requires Component Pack for HCL Connections. - 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 your topology. For more information about each
option, see the Deployment options topic.
Note:
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:
- Select the Small deployment topology.
- Enter a Cluster name for the topology.
- Select a Node.
- Click Next.
- Medium deployment:
- 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 HCL 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.
- Click Next.
- Large deployment:
- 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 HCL 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.
- Click Next.
- Small deployment:
- Enter the database information:
- Select
a Notification solution. Notifications are email messages to users
about new information and events in your HCL 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 HCL Connections deployment. You can configure notifications after installation. Refer to Configuring notifications for more information.
- Enable Notification only.
- 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 name.
Complete the following fields to identify the mail server to use for sending email:- Host name of SMTP messaging server
- Enter the host name 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 user ID.
- 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 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
- 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
- Specify the port number to use for the SMTP server connection. The default port number 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. HCL 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.
- In the Role Mapping window, you can add administrative users. Enter the LDAP user names to map them to the admin role. If that role is empty, the Application server administrative user is mapped to the role by default.
- In the Role Mapping window, you can add Global Moderator Users. Enter the LDAP user name to the global-moderator role. If that role is empty, the Application server administrative user is mapped to the role by default.
- 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.
- Clear the server cache. This needs to be done when the Node is not running. Delete the contents of the cache under the App Server. For example, C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp.
- 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.
Run C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin\startManager.bat and change directory to
C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin using stopManager.bat -username WASadmin -password WAS_password.
- AIX® or Linux™: Open a command prompt and change to
the app_server_root/profiles/Dmgr01/bin directory.
Enter the
- 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 HCL Connections application.
-
Configure the HTTP Server plugin with Connections
If you chose to configure the WebServer during the install, the settings and configuration for Connections will use the IBM HTTP Server URL for communication. Ensure the HTTP Server plugin is configured to access the different Connections components.
Note: The following examples are only for Unix. If WebSphere Application server is enabled then trust the HTTP Server certificate - Restart the Deployment Manager.
- Start
all your HCL Connections clusters:
- Log in to the Integrated Solutions Console on the DM.
- Navigate to .
- Select the HCL 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
- 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.
What to do next
- Complete the Post-installation Tasks.
- 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.
- Download the Connections V7.0 Update Wizard from the HCL License & Delivery Portal.