Software Product Compatibility Reports Detailed System Requirements

Product

HCL Connections 6

1 of 53 HCL Connections 6: Detailed System Requirements

Contents

This document contains the detailed system requirements specified in the Clearinghouse for the HCL Connections 6.0 deliverable. This deliverable is planned to ship with the MSI name HCL Connections with the release level of 6.0. The detailed system requirements for this deliverable are organized into three major sections. The Software Requirements section covers the software (and the supported maintenance) that this deliverable either requires (that is, a mandatory prerequisite) or can work with in some way. The section contains the details describing the operating systems (and supported maintenance) that the deliverable supports as well as details about the supported hypervisors. The Hardware Requirements section provides details about the minimum recommended hardware requirements for a typical use of this deliverable.

The data in this report is for a specific level of the deliverable; whether release, modification or fixpack. For a release or modification deliverable, the technical details should describe what is supported for that release or modification with no fixpacks applied. For a fixpack deliverable, the technical details should describe what is supported by that specific fixpack.

Since this report is designed to enable review, each section will provide hints about what a reviewer should be focusing on.

1. Deliverable overview 2. Software requirements 3. Operating systems 4. Hardware requirements 1.1 Deployment structure 2.1 Capabilities used by 3.1 Supported operating 4.1 Disk Space components systems 1.2 Packaging list 4.2 Memory 2.2 Capabilities details 3.2 Families details 1.3 Integrated products 2.2.1 Application Servers 3.2.1 AIX 2.2.2 Installation 3.2.2 2.2.3 3.2.3 Mac OS 2.2.4 Connectors 3.2.4 Mobile OS 2.2.5 3.2.5 Windows 2.2.6 E- Application 3.3 Supported Hypervisors 2.2.7 Identity Management 2.2.8 LDAP Servers 2.2.9 Portal Servers 2.2.10 Productivity Applications 2.2.11 Reporting and Analysis 2.2.12 Security Management 2.2.13 Web Browsers 2.2.14 Web Servers

2 of 53 1. Deliverable overview

1.1 Deployment structure

Deployment structure identifies pieces of the deliverable that can be independently deployed, i.e., that may be installed onto multiple machines in a distributed infrastructure. Since the detailed system requirements often vary by these pieces, the details in this table capture the pieces that can be deployed separately. These pieces are specified at two levels: deployment units and deployable components. The deployment units level specifies pieces of the deliverable that are installed into different tiers of a distributed architecture (server tier, desktop tier, agent tier, mobile device tier). Deployment units are further divided into deployable components, which are the smallest externally identifiable, independently deployable pieces of a deliverable. With the advent of virtualization technologies, cloud, and appliances, HCL products are delivering our software to clients using new formats such as virtual appliances and physical appliances. Deployment units or components can have delivery formats associated with them which describe how the DU/component is delivered to clients.

Reviewers Tips Verify that the details of the deployment structure actually correspond to the deployable pieces of the deliverable. For deployment unit, verify that the specified deployment unit make sense for the high level architecture of the deliverable. For those deployment units that consist of independently deployable pieces, make sure there is a deployable component for each piece, with a name that is consistent with the installation program / install guide. In addition, make sure that the specified delivery format reflects the way in which the deployable pieces are provided to clients.

Deployment unit Deployable components Delivery format

1 Desktop 1 No component Native Install

2 Server 2 No component Native Install

3 Mobile Device 3 No component Native Install HCL Connections 6: Detailed System Requirements

1.2 Packaging list

When this deliverable is purchased by a , the other software products that are provided with the deliverable are enumerated in this section. This software can either be co-installed or co-packaged.

The software products listed in the co-installed section of the table are those incorporated into the installation program for the deliverable. The user of the installation program may or may not have control over whether the co-installed software products are actually installed (e.g., the installation program may provide an option to install a prerequisite database server, or to specify an existing one). If the software product is only co-installed on a subset of the supported operating systems, those restricted operating systems are listed in the third column.

The software products listed in the co-packaged section of the table are those that are packaged with the media used to ship the product but that are installed using a separated installation program. Typically, co-installed and/or co-packaged software fulfills an immediate prerequisite requirement of the deliverable so the capability that is fulfilled is enumerated in the ?Capability? column. When an enumerated software product is not an immediate prerequisite the ?Capability? column will include the words ?None specified?.

Reviewer tips Reviewers of this section should focus on ensuring all the co-installed and co-packaged software products are included and that for the co-installed software products any operating system restrictions are captured accurately. If there is no capability specified for a co-installed or co-packaged product, verify that the product is provided with the deliverable but not directly used by it.

1.2.1 Co-installed products Product Capability Co-installed on the following operating systems families

1 No products are co-installed

1.2.2 Co-packaged products Product Capability

1 DB2 Enterprise Server Edition 11.1.0 1. Databases

2 HCL Connections Docs 2.0 1. Collaboration

3 WebSphere Application Server Network Deployment 1. Application Servers Application Servers 8.5.5

4 of 53 HCL Connections 6: Detailed System Requirements

1.3 Integrated products

If some or all of your deliverable is delivered as an appliance or is an integrated system, there can be software products and/or operating systems that are integrated into that appliance/system that the client needs to be aware of. For example, you may need to communicate products within the deliverable that the client will directly use, monitor, deploy to or administer. You should not list products or operating systems that are intended to be invisible to the client. Typically, integrated products fulfill an immediate system requirement of the appliance/system.

The software products listed in the Integrated software section of the table are those software products that are integrated into the appliance/system. The list of integrated software can include hypervisors. The components listed in the second column of the table can only be virtual appliance, live disc appliance or integrated system components within your deliverable that integrate the software product.

The operating systems listed in the Integrated operating systems section of the table are those operating systems that are integrated into the appliance/system. The application bitness of the integrated operating system is listed in the second column of the table. The components listed in the third column of the table can only be virtual appliance, live disc appliance or integrated system components within your deliverable that integrate the operating system.

Reviewer tips Reviewers of this section should focus on ensuring that integrated software products that the client will directly use, monitor, deploy to or administer are listed. In addition, ensure that any operating system that is integrated is listed. Typically, there is just one operating system in this list, but multiple are allowed. Finally, ensure that the applicable components are correct and complete. If there are appliance/system components associated with this deliverable that have no integrated products listed in this section, verify that this is correct.

1.3.1 Integrated software Deployment unit Components Product

Integrated software can only be specified when the deliverable has deployment units or components with a delivery format other than native install.

1.3.2 Integrated operating systems Deployment unit Components Operating system Application bitness

Integrated operating systems can only be specified when the deliverable has deployment units or components with a delivery format other than native install.

2. Software requirements

5 of 53

HCL Connections 6: Detailed System Requirements

2.1 Capabilities used by components

The software used by this deliverable are organized into capabilities to provide some context about why or how the software is used.

Reviewer Tips Reviews of this table need to verify three aspects of the capabilities supported by this deliverable.

1. Verify that all the capabilities listed in the Mandatory column are actually mandatory. A capability is considered mandatory if the deliverable must be configured to

work with a product in that capability for any part of the deployment structure. That is, a capability is considered mandatory if it is required for any deployable

components, even if those deployable components are optional.

2. Verify that all the capabilities listed in the Additional column are software that the deliverable works with in some way and that the list includes capabilities for all the

software the deliverable integrates with.

3. Verify that the details in the matrix properly specify which part of the deployment structure uses a particular capability. A ?Y? indicates that the deployment unit or

deployable component of the deliverable uses this capability. The ?Y? does not imply that the particular part of the deployment structure is configured directly with

the product fulfilling the capability.

Capabilities

Mandatory Additional 1. Application Servers 3. Collaboration

2. Installation 4. Connectors

5. Databases

6. E-mail Application

7. Identity Management

8. LDAP Servers

9. Portal Servers

10. Productivity Applications

11. Reporting and Analysis

12. Security Management

13. Web Browsers

14. Web Servers

Deployment unit Components 1 2 3 4 5 6 7 8 9 10 11 12 13 14

1 Desktop 1 No component N Y Y Y N Y Y Y Y Y Y Y Y Y

2 Server 2 No component Y Y Y Y Y N Y Y Y Y Y Y N Y

3 Mobile Device 3 No component N Y Y Y N N Y Y Y Y Y Y N Y

2.2 Capabilities details

6 of 53 HCL Connections 6: Detailed System Requirements

2.2.1 Application Servers

2.2.1.1 Summary of products fulfilling this capability

The software products that can fulfill the Application Servers capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. tag">c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product. Deployment unit and/or deployable component restrictions are covered in section 2.2.1.3.

Supported product Packaging Interaction context

1 WebSphere Application Server Network Deployment 8.5.5.10 Co-packaged interact

2 WebSphere Application Server Network Deployment 8.5.5.11 Co-packaged interact

2.2.1.2 Operating system restrictions for Application Servers

When any of the products listed in this table are used to fulfil the Application Servers capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Application Servers capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 2 products listed in this capability

7 of 53

HCL Connections 6: Detailed System Requirements

2.2.1.3 Component usage restrictions for Application Servers

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.1.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component

2 Server 2 No component No restriction

3 Mobile Device 3 No component

2.2.1.4 Notes for Application Servers

This table contains a section for any of the software products fulfilling the Application Servers capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.1.1.

The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for: WebSphere Application Server Network Deployment 8.5.5.11

1 WebSphere Application Server 8.5.5.11 can have 6 or Java 8 installed. If you to install Connections Content Manager as part of this deployment, make sure that you do NOT configure WebSphere Application Server to use Java 8 now. Switching to Java 8 must be done after completing Connections installation and all other post-installation tasks. Please refer to the Connections product documentation for more details.

Footnotes for: WebSphere Application Server Network Deployment 8.5.5.10

2 HCL Connections 6.0 requires WebSphere Application Server 8.5.5.10, which has Java 6 installed. If you plan to install Connections Content Manager as part of this deployment, make sure that you do NOT configure WebSphere Application Server to use Java 8 now. Switching to Java 8 must be done after completing Connections installation and all other post-installation tasks. Please refer to the Connections product documentation for more details.

8 of 53

HCL Connections 6: Detailed System Requirements

2.2.2 Installation

2.2.2.1 Summary of products fulfilling this capability

The software products that can fulfill the Installation capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are:

a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.2.3.

Supported product Packaging Interaction context

1 HCL Installation Manager 1.8.5 on the same machine and future fix packs

2.2.2.2 Operating system restrictions for Installation

When any of the products listed in this table are used to fulfil the Installation capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Installation capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 1 products listed in this capability

9 of 53

HCL Connections 6: Detailed System Requirements

2.2.2.3 Component usage restrictions for Installation

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.2.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component No restriction

3 Mobile Device 3 No component No restriction

2.2.2.4 Notes for Installation

This table contains a section for any of the software products fulfilling the Installation capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.2.1. The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for:

1 None provided

10 of

HCL Connections 6.0 System Requirements Review Report

2.2.3 Collaboration

2.2.3.1 Summary of products fulfilling this capability

The software products that can fulfill the Collaboration capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.3.3.

Supported product Packaging Interaction context

1 HCL Connections Docs 2.0 CR2 Co-packaged interact and future fix packs

2 HCL Sametime Complete 9.0.1 interact and future fix packs

2.2.3.2 Operating system restrictions for Collaboration

When any of the products listed in this table are used to fulfil the Collaboration capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Collaboration capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 2 products listed in this capability

10 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.3.3 Component usage restrictions for Collaboration

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.3.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component No restriction

3 Mobile Device 3 No component No restriction

2.2.3.4 Notes for Collaboration

This table contains a section for any of the software products fulfilling the Collaboration capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.3.1. The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for: HCL Connections Docs 2.0 CR2

1 HCL Connections Docs 2.0 CR2 is required for Accessibility Compliance.

11 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.4 Connectors

2.2.4.1 Summary of products fulfilling this capability

The software products that can fulfill the Connectors capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.4.3.

Supported product Packaging Interaction context

1 Feed Reader All versions interact and future fix packs

2.2.4.2 Operating system restrictions for Connectors

When any of the products listed in this table are used to fulfil the Connectors capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Connectors capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product...... the deliverable needs to be on one of these operating systems

1 Feed Reader All versions Any AIX, Linux, Windows operating systems supported by the deliverable. and future fix packs None of the Mac OS, Mobile OS operating systems supported by the deliverable.

12 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.4.3 Component usage restrictions for Connectors

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.4.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there

are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component No restriction

3 Mobile Device 3 No component No restriction

2.2.4.4 Notes for Connectors

This table contains a section for any of the software products fulfilling the Connectors capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.4.1.

The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for: Feed Reader All versions

1 Any enterprise feed reader supporting protocol

13 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.5 Databases

2.2.5.1 Summary of products fulfilling this capability

The software products that can fulfill the Databases capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.5.3.

Supported product Packaging Interaction context

1 DB2 Enterprise Server Edition 11.1.0 Co-packaged interact and future fix packs

2 SQL Server 2016 interact and future fix packs

3 Microsoft SQL Server Enterprise Edition 2016 interact and future fix packs

4 Oracle Database 12c Release 1 (12.1.0.2.0) Enterprise Edition interact and future fix packs

5 Oracle Database 12c Release 1 (12.1.0.2.0) Standard Edition TWO interact and future fix packs

2.2.5.2 Operating system restrictions for Databases

When any of the products listed in this table are used to fulfil the Databases capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Databases capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 5 products listed in this capability

14 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.5.3 Component usage restrictions for Databases

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.5.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component

2 Server 2 No component No restriction

3 Mobile Device 3 No component

2.2.5.4 Notes for Databases

This table contains a section for any of the software products fulfilling the Databases capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.5.1. The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for:

1 None provided

15 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.6 E-mail Application

2.2.6.1 Summary of products fulfilling this capability

The software products that can fulfill the E-mail Application capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.6.3.

Supported product Packaging Interaction context

1 HCL Notes 9.0.1 Social Edition interact and future fix packs

2 2016 interact

2.2.6.2 Operating system restrictions for E-mail Application

When any of the products listed in this table are used to fulfil the E-mail Application capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the E-mail Application capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 2 products listed in this capability

16 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.6.3 Component usage restrictions for E-mail Application

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.6.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components

need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component

3 Mobile Device 3 No component

2.2.6.4 Notes for E-mail Application

This table contains a section for any of the software products fulfilling the E-mail Application capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.6.1. The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for:

1 None provided

17 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.7 Identity Management

2.2.7.1 Summary of products fulfilling this capability

The software products that can fulfill the Identity Management capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.7.3.

Supported product Packaging Interaction context

1 Tivoli Directory Integrator 7.1.1 interact

2.2.7.2 Operating system restrictions for Identity Management

When any of the products listed in this table are used to fulfil the Identity Management capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Identity Management capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 1 products listed in this capability

18 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.7.3 Component usage restrictions for Identity Management

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.7.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component No restriction

3 Mobile Device 3 No component No restriction

2.2.7.4 Notes for Identity Management

This table contains a section for any of the software products fulfilling the Identity Management capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.7.1.

The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for: Tivoli Directory Integrator 7.1.1

1 FixPack 6 is a required package after installing TDI 7.1.1.

See this Knowledge Center topic for configuring TDI on a Windows 2016 Server: Configuring HCL Tivoli Directory Integrator

The highest version of Java supported by TDI is Java 7.1.

19 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.8 LDAP Servers

2.2.8.1 Summary of products fulfilling this capability

The software products that can fulfill the LDAP Servers capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.8.3.

Supported product Packaging Interaction context

1 HCL Domino 9.0.1 Social Edition interact and future fix packs

2 HCL Security Directory Server 6.4.0.0 interact and future fix packs

3 Lotus Domino 8.5.3 interact and future fix packs

4 Microsoft 2012 R2 interact and future fix packs

5 Microsoft Active Directory 2016 interact and future fix packs

6 NetIQ eDirectory 8.8 SP8 interact and future fix packs

7 Oracle Directory Server 11g Enterprise Edition Release 2 (11.1.2) interact and future fix packs

20 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.8.2 Operating system restrictions for LDAP Servers

When any of the products listed in this table are used to fulfil the LDAP Servers capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the LDAP Servers capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 7 products listed in this capability

2.2.8.3 Component usage restrictions for LDAP Servers

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.8.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component No restriction

3 Mobile Device 3 No component No restriction

2.2.8.4 Notes for LDAP Servers

This table contains a section for any of the software products fulfilling the LDAP Servers capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.8.1. The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for:

1 None provided

21 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.9 Portal Servers

2.2.9.1 Summary of products fulfilling this capability

The software products that can fulfill the Portal Servers capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable.

Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.9.3.

Supported product Packaging Interaction context

1 WebSphere Portal Server 9.0 interact and future fix packs

2.2.9.2 Operating system restrictions for Portal Servers

When any of the products listed in this table are used to fulfil the Portal Servers capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Portal Servers capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 1 products listed in this capability

22 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.9.3 Component usage restrictions for Portal Servers

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.9.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component No restriction

3 Mobile Device 3 No component No restriction

2.2.9.4 Notes for Portal Servers

This table contains a section for any of the software products fulfilling the Portal Servers capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.9.1. The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for:

1 None provided

23 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.10 Productivity Applications

2.2.10.1 Summary of products fulfilling this capability

The software products that can fulfill the Productivity Applications capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.10.3.

Supported product Packaging Interaction context

1 HCL Sametime Conference 9.0.1 interact and future fix packs

2 No MSI Name (Deliverable Name: Sametime Limited Use) 9.0.1FP1 interact and future fix packs

2.2.10.2 Operating system restrictions for Productivity Applications

When any of the products listed in this table are used to fulfil the Productivity Applications capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Productivity Applications capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 2 products listed in this capability

24 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.10.3 Component usage restrictions for Productivity Applications

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.10.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component No restriction

3 Mobile Device 3 No component No restriction

2.2.10.4 Notes for Productivity Applications

This table contains a section for any of the software products fulfilling the Productivity Applications capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.10.1.

The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for:

1 None provided

25 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.11 Reporting and Analysis

2.2.11.1 Summary of products fulfilling this capability

The software products that can fulfill the Reporting and Analysis capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.11.3.

Supported product Packaging Interaction context

1 Elasticsearch 5.x interact

2.2.11.2 Operating system restrictions for Reporting and Analysis

When any of the products listed in this table are used to fulfil the Reporting and Analysis capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Reporting and Analysis capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 1 products listed in this capability

26 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.11.3 Component usage restrictions for Reporting and Analysis

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.11.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component No restriction

3 Mobile Device 3 No component No restriction

2.2.11.4 Notes for Reporting and Analysis

This table contains a section for any of the software products fulfilling the Reporting and Analysis capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.11.1.

The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for: Elasticsearch 5.x

1 Specific version tested is Elasticsearch v5.5.1.

27 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.12 Security Management

2.2.12.1 Summary of products fulfilling this capability

The software products that can fulfill the Security Management capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.12.3.

Supported product Packaging Interaction context

1 CA SiteMinder 12.5 interact and future fix packs

2 HCL Security Access Manager 9.0.1.0 interact and future fix packs

2.2.12.2 Operating system restrictions for Security Management

When any of the products listed in this table are used to fulfil the Security Management capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Security Management capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product...... the deliverable needs to be on one of these operating systems

1 CA SiteMinder 12.5 Any AIX, Linux, Windows operating systems supported by the deliverable. and future fix packs None of the Mac OS, Mobile OS operating systems supported by the deliverable.

28 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.12.3 Component usage restrictions for Security Management

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.12.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component No restriction

3 Mobile Device 3 No component No restriction

2.2.12.4 Notes for Security Management

This table contains a section for any of the software products fulfilling the Security Management capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.12.1.

The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for:

1 None provided

29 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.13 Web Browsers

2.2.13.1 Summary of products fulfilling this capability

The software products that can fulfill the Web Browsers capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.13.3.

Supported product Packaging Interaction context

1 Apple 10 interact

2 Chrome 53 interact

3 38 interact

4 Microsoft 11 interact

5 Mozilla 49 interact

6 Mozilla Firefox ESR 45 interact

2.2.13.2 Operating system restrictions for Web Browsers

When any of the products listed in this table are used to fulfil the Web Browsers capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Web Browsers capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 6 products listed in this capability

30 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.13.3 Component usage restrictions for Web Browsers

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.13.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component

3 Mobile Device 3 No component

2.2.13.4 Notes for Web Browsers

This table contains a section for any of the software products fulfilling the Web Browsers capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.13.1. The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for: Microsoft Internet Explorer 11 Microsoft Edge 38 Mozilla Firefox ESR 45 Mozilla Firefox 49 Google Chrome 53 Apple Safari 10

1 Mobile is supported accessing HCL Connections through the native mobile apps only.

The Connections detailed system requirements page lists the supported web browsers that have undergone compatibility testing by HCL. HCL recommends that customers always use the web browsers listed in the Connections system requirements; any variance has some level of risk because the combination has not been tested, and is not supported by HCL.

If a supported browser that is listed in the System Requirements has a new version released, HCL Support may provide support through the HCL PMR process on a case-by-case basis. HCL Support will accept problem reports (PMRs) relating to using these newer and untested browser releases and will validate on a case-by-case basis whether HCL can provide technical support. HCL Support may require you to test and reproduce the issue using recommended system requirements in order to receive further support.

31 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.14 Web Servers

2.2.14.1 Summary of products fulfilling this capability

The software products that can fulfill the Web Servers capability requirement of this deliverable are listed in this table.

Reviewers tips The products listed in this table should be those that are supported by the specific level of the deliverable identified at the top of this report, and should not include products that require additional fixpacks of the deliverable. Additional details that can be confirmed using this table are:

1. Verify that the Interaction context column accurately captures one of the three ways the specified product and deliverable execute together. The options are: a. The deliverable runs on top of the specified software products. (Used for mandatory capabilities only) b. The specified software product is expected to be on the same machine as the deliverable. c. The specified software product interacts (either locally or remotely) with the deliverable. 2. The Packaging column specifies whether or not a particular entry is co-installed by the deliverable installation program or is co-packaged with the media used

to ship the deliverable. These details need to be accurate so those preparing the order can determine whether or not additional software needs to be obtained

for a client.

3. The Supported product column should include 'and future fix packs', unless the product only supports specific fixpacks, in which case those fixpacks should be

listed.

4. If the Supported product column includes 'and future releases' or 'and future mod levels', make sure that this is consistent with the deliverable's support policy.

It is highly unusual to make a support statement covering all future releases of a product.

Deployment unit and/or deployable component restrictions are covered in section 2.2.14.3.

Supported product Packaging Interaction context

1 HCL HTTP Server 8.5.5 interact

2.2.14.2 Operating system restrictions for Web Servers

When any of the products listed in this table are used to fulfil the Web Servers capability, the deliverable must be deployed on one of the operating systems listed in the second column.

Reviewers tips Reviewers need to verify that the restrictions enumerated in the table are accurate and that no other product listed in the Web Servers capability has a restriction for the operating system the deliverable runs on. One of the reason such a restriction might exist is that the product in the capability must co-exist with the deliverable and the product runs on a subset of the deliverable's supported operating systems.

If using this product ...... the deliverable needs to be on one of these operating systems

1 No restrictions for all 1 products listed in this capability

32 of 53

HCL Connections 6.0 System Requirements Review Report

2.2.14.3 Component usage restrictions for Web Servers

In some deliverables, not all parts of the deployment structure that use a specific capability can work with the all of the products listed in the capability. This table lists the products from Section 2.2.14.1 that cannot be used with the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the Products not supported column are accurate and that there are no missing restrictions.

Deployment unit Components Products not supported

1 Desktop 1 No component No restriction

2 Server 2 No component No restriction

3 Mobile Device 3 No component No restriction

2.2.14.4 Notes for Web Servers

This table contains a section for any of the software products fulfilling the Web Servers capability requirements that have additional support notes that might influence the selection of a particular product to fulfill this capability.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include operating system restrictions and component usage restrictions, as well as the information on supported fixpacks shown in the Supported product column of the table in Section 2.2.14.1. The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for: HCL HTTP Server 8.5.5

1 HCL HTTP Server 8.5.5 Fixpack 10 is the only supported level for HCL Connections 6.0

3. Operating systems

33 of 53

HCL Connections 6.0 System Requirements Review Report

3.1 Supported operating system families

The operating system editions and releases for supported operating system families are enumerated in this table.

Reviewers tips Reviewers of this table should focus on the big picture ?support? story since there will be a 3.2.x sections with details for each of the families.

Family Operating systems Editions and versions

AIX 1 AIX 7.1

7.2

Linux 2 Enterprise Linux (RHEL) Client 7

3 (RHEL) Server 7

4 SUSE Linux Enterprise Server (SLES) 12

Mac OS 5 macOS Sierra 10.12

Mobile OS 6 Android 4.1

7 iOS 9.2

Windows 8 Windows 7 Enterprise

9 Windows Server 2012 Datacenter Edition R2

10 Windows Server 2016 Datacenter Edition

11 Windows Enterprise 8.1

Enterprise 10

Pro 10

Professional 8.1

3.2 Families details

34 of 53

HCL Connections 6.0 System Requirements Review Report

3.2.1 AIX family

3.2.1.1 Supported operating system summary

The operating systems for the AIX family that are supported by this deliverable are enumerated in this table.

Reviewers tips Additional details that can be confirmed using this table are:

1. The operating systems listed in this table should be those supported by the specific level of the deliverable identified at the top of this report, and should not

include operating systems that require additional fixpacks of the deliverable.

2. The Maintenance column should include 'and future fix packs', unless the product only supports specific OS fixpacks, in which case those fixpacks should be

listed.

3. If the Maintenance column includes 'and future versions', make sure that this is consistent with the deliverable's support policy. It is unusual to make a support

statement covering all future versions of an operating system.

Name Version Maintenance Hardware

1 AIX 7.1 And future OS versions and fix packs POWER System - Big Endian

2 AIX 7.2 And future OS versions and fix packs POWER System - Big Endian

3.2.1.2 Component restrictions for the AIX family

In some deliverables, not all parts of the deployment structure can run on all of the operating systems in a specific family. This table lists the operating systems from Section 3.2.1.1. that are supported by the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the The component must be on one of the indicated operating systems column are accurate and that there are no missing restrictions.

Deployment unit Components The component must be on one of the indicated operating systems

1 Desktop 1 No component None of the AIX operating systems supported by the deliverable

2 Server 2 No component Any AIX operating system supported by the deliverable

3 Mobile Device 3 No component None of the AIX operating systems supported by the deliverable

3.2.1.3 Application bitness for the AIX family

The deliverable is capable of running with the bitness specified in the Application bitness column for the operating system entry.

Reviewers tips Verify that support for Application bitness is accurate and complete for the associated operating systems.

Name Version Maintenance Hardware Application bitness

1 AIX 7.1 And future OS versions and fix packs POWER System - Big Endian 64-Tolerate

2 AIX 7.2 And future OS versions and fix packs POWER System - Big Endian 64-Tolerate

35 of 53

HCL Connections 6.0 System Requirements Review Report

3.2.1.4 Processor support for the AIX family

The deliverable provides additional support for various POWER processor compatibility modes as specified in the "Processor modes" column for the operating system entry. For detailed description of the support values, please refer to Clearing House Information Center for OS Support.

Reviewers tips Verify that the support for POWER processor compatibility modes is accurate and complete for the associated operating systems.

Processor modes Supported operating systems

1 POWER8 in POWER8 mode AIX 7.2 and future OS versions and fix packs POWER System - Big Endian

2 POWER9 in POWER8 mode AIX 7.2 and future OS versions and fix packs POWER System - Big Endian

3.2.1.5 Notes for the AIX family

This table contains a section for any of the operating system supported by this deliverable that has additional support notes that might influence the selection of a particular operating system choice.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include component usage restrictions, as well as the information on supported OS fixpacks shown in the Maintenance column of the table in Section 3.2.1.1.

The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for: AIX 7.1 and future OS versions and fix packs POWER System - Big Endian AIX 7.2 and future OS versions and fix packs POWER System - Big Endian

1 ksh UNIX shell (command execution program) is a system requirement for HCL Connections Content Manager

Component Support - Shared and Remote Filesystems: Network File System NFSv4 client with NFSv4 Server

36 of 53

HCL Connections 6.0 System Requirements Review Report

3.2.2 Linux family

3.2.2.1 Supported operating system summary

The operating systems for the Linux family that are supported by this deliverable are enumerated in this table.

Reviewers tips Additional details that can be confirmed using this table are:

1. The operating systems listed in this table should be those supported by the specific level of the deliverable identified at the top of this report, and should not

include operating systems that require additional fixpacks of the deliverable.

2. The Maintenance column should include 'and future fix packs', unless the product only supports specific OS fixpacks, in which case those fixpacks should be

listed.

3. If the Maintenance column includes 'and future versions', make sure that this is consistent with the deliverable's support policy. It is unusual to make a support

statement covering all future versions of an operating system.

Name Version Maintenance Hardware

1 Red Hat Enterprise Linux (RHEL) Client 7 7.1 and future OS fix packs x86-64

2 Red Hat Enterprise Linux (RHEL) Client 7 7.2 and future OS fix packs x86-64

3 Red Hat Enterprise Linux (RHEL) Client 7 7.3 and future OS fix packs x86-64

4 Red Hat Enterprise Linux (RHEL) Server 7 7.1 and future OS fix packs HCL z Systems

5 Red Hat Enterprise Linux (RHEL) Server 7 7.1 and future OS fix packs x86-64

6 Red Hat Enterprise Linux (RHEL) Server 7 7.2 and future OS fix packs HCL z Systems

7 Red Hat Enterprise Linux (RHEL) Server 7 7.2 and future OS fix packs x86-64

8 Red Hat Enterprise Linux (RHEL) Server 7 7.3 and future OS fix packs HCL z Systems

9 Red Hat Enterprise Linux (RHEL) Server 7 7.3 and future OS fix packs x86-64

10 SUSE Linux Enterprise Server (SLES) 12 And future OS fix packs HCL z Systems

11 SUSE Linux Enterprise Server (SLES) 12 And future OS fix packs x86-64

37 of 53

HCL Connections 6.0 System Requirements Review Report

3.2.2.2 Component restrictions for the Linux family

In some deliverables, not all parts of the deployment structure can run on all of the operating systems in a specific family. This table lists the operating systems from Section 3.2.2.1. that are supported by the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the The component must be on one of the indicated operating systems column are accurate and that there are no missing restrictions.

Deployment unit Components The component must be on one of the indicated operating systems

1 Desktop 1 No component Specific Linux operating systems (operating systems in grey are not supported) 1. Red Hat Enterprise Linux (RHEL) Client 7 7.1 and future OS fix packs x86-64 2. Red Hat Enterprise Linux (RHEL) Client 7 7.2 and future OS fix packs x86-64 3. Red Hat Enterprise Linux (RHEL) Client 7 7.3 and future OS fix packs x86-64 4. Red Hat Enterprise Linux (RHEL) Server 7 7.1 and future OS fix packs HCL z Systems 5. Red Hat Enterprise Linux (RHEL) Server 7 7.1 and future OS fix packs x86-64 6. Red Hat Enterprise Linux (RHEL) Server 7 7.2 and future OS fix packs HCL z Systems 7. Red Hat Enterprise Linux (RHEL) Server 7 7.2 and future OS fix packs x86-64 8. Red Hat Enterprise Linux (RHEL) Server 7 7.3 and future OS fix packs HCL z Systems 9. Red Hat Enterprise Linux (RHEL) Server 7 7.3 and future OS fix packs x86-64 10. SUSE Linux Enterprise Server (SLES) 12 and future OS fix packs HCL z Systems 11. SUSE Linux Enterprise Server (SLES) 12 and future OS fix packs x86-64

2 Server 2 No component Specific Linux operating systems (operating systems in grey are not supported) 1. Red Hat Enterprise Linux (RHEL) Client 7 7.1 and future OS fix packs x86-64 2. Red Hat Enterprise Linux (RHEL) Client 7 7.2 and future OS fix packs x86-64 3. Red Hat Enterprise Linux (RHEL) Client 7 7.3 and future OS fix packs x86-64 4. Red Hat Enterprise Linux (RHEL) Server 7 7.1 and future OS fix packs HCL z Systems 5. Red Hat Enterprise Linux (RHEL) Server 7 7.1 and future OS fix packs x86-64 6. Red Hat Enterprise Linux (RHEL) Server 7 7.2 and future OS fix packs HCL z Systems 7. Red Hat Enterprise Linux (RHEL) Server 7 7.2 and future OS fix packs x86-64 8. Red Hat Enterprise Linux (RHEL) Server 7 7.3 and future OS fix packs HCL z Systems 9. Red Hat Enterprise Linux (RHEL) Server 7 7.3 and future OS fix packs x86-64

38 of 53

HCL Connections 6.0 System Requirements Review Report

10. SUSE Linux Enterprise Server (SLES) 12 and future OS fix packs HCL z Systems 11. SUSE Linux Enterprise Server (SLES) 12 and future OS fix packs x86-64

3 Mobile Device 3 No component None of the Linux operating systems supported by the deliverable

3.2.2.3 Application bitness for the Linux family

The deliverable is capable of running with the bitness specified in the Application bitness column for the operating system entry.

Reviewers tips Verify that support for Application bitness is accurate and complete for the associated operating systems.

Name Version Maintenance Hardware Application bitness

1 Red Hat Enterprise Linux (RHEL) Client 7 7.1 and future OS fix packs x86-64 64-Tolerate

2 Red Hat Enterprise Linux (RHEL) Client 7 7.2 and future OS fix packs x86-64 64-Tolerate

3 Red Hat Enterprise Linux (RHEL) Client 7 7.3 and future OS fix packs x86-64 64-Tolerate

4 Red Hat Enterprise Linux (RHEL) 7 7.1 and future OS fix packs HCL z Systems 64-Tolerate Server

5 Red Hat Enterprise Linux (RHEL) 7 7.1 and future OS fix packs x86-64 64-Tolerate Server

6 Red Hat Enterprise Linux (RHEL) 7 7.2 and future OS fix packs HCL z Systems 64-Tolerate Server

7 Red Hat Enterprise Linux (RHEL) 7 7.2 and future OS fix packs x86-64 64-Tolerate Server

8 Red Hat Enterprise Linux (RHEL) 7 7.3 and future OS fix packs HCL z Systems 64-Tolerate Server

9 Red Hat Enterprise Linux (RHEL) 7 7.3 and future OS fix packs x86-64 64-Tolerate Server

10 SUSE Linux Enterprise Server (SLES) 12 And future OS fix packs HCL z Systems 64-Tolerate

11 SUSE Linux Enterprise Server (SLES) 12 And future OS fix packs x86-64 64-Tolerate

39 of 53

HCL Connections 6.0 System Requirements Review Report

3.2.2.4 Notes for the Linux family

This table contains a section for any of the operating system supported by this deliverable that has additional support notes that might influence the selection of a particular operating system choice.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include component usage restrictions, as well as the information on supported OS fixpacks shown in the Maintenance column of the table in Section 3.2.2.1.

The notes should be for the specific level of the deliverable identified at the top of this report, and should not

describe support that requires additional fixpacks of the deliverable.

Footnotes for:

1 None provided

3.2.3 Mac OS family

3.2.3.1 Supported operating system summary

The operating systems for the Mac OS family that are supported by this deliverable are enumerated in this table.

Reviewers tips Additional details that can be confirmed using this table are:

1. The operating systems listed in this table should be those supported by the specific level of the deliverable identified at the top of this report, and should not

include operating systems that require additional fixpacks of the deliverable.

2. The Maintenance column should include 'and future fix packs', unless the product only supports specific OS fixpacks, in which case those fixpacks should be

listed.

3. If the Maintenance column includes 'and future versions', make sure that this is consistent with the deliverable's support policy. It is unusual to make a support

statement covering all future versions of an operating system.

Name Version Maintenance Hardware

1 macOS Sierra 10.12 And future OS fix packs x86-64

3.2.3.2 Component restrictions for the Mac OS family

In some deliverables, not all parts of the deployment structure can run on all of the operating systems in a specific family. This table lists the operating systems from Section 3.2.3.1. that are supported by the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the The component must be on one of the indicated operating systems column are accurate and that there are no missing restrictions.

Deployment unit Components The component must be on one of the indicated operating systems

1 Desktop 1 No component Any Mac OS operating system supported by the deliverable

2 Server 2 No component None of the Mac OS operating systems supported by the deliverable

3 Mobile Device 3 No component None of the Mac OS operating systems supported by the deliverable

40 of 53

HCL Connections 6.0 System Requirements Review Report

3.2.3.3 Application bitness for the Mac OS family

The deliverable is capable of running with the bitness specified in the Application bitness column for the operating system entry.

Reviewers tips Verify that support for Application bitness is accurate and complete for the associated operating systems.

Name Version Maintenance Hardware Application bitness

1 macOS Sierra 10.12 And future OS fix packs x86-64 64-Tolerate

3.2.3.4 Notes for the Mac OS family

This table contains a section for any of the operating system supported by this deliverable that has additional support notes that might influence the selection of a particular operating system choice.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include component usage restrictions, as well as the information on supported OS fixpacks shown in the Maintenance column of the table in Section 3.2.3.1.

The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for:

1 None provided

3.2.4 Mobile OS family

3.2.4.1 Supported operating system summary

The operating systems for the Mobile OS family that are supported by this deliverable are enumerated in this table.

Reviewers tips Additional details that can be confirmed using this table are:

1. The operating systems listed in this table should be those supported by the specific level of the deliverable identified at the top of this report, and should not

include operating systems that require additional fixpacks of the deliverable.

2. The Maintenance column should include 'and future fix packs', unless the product only supports specific OS fixpacks, in which case those fixpacks should be

listed.

3. If the Maintenance column includes 'and future versions', make sure that this is consistent with the deliverable's support policy. It is unusual to make a support

statement covering all future versions of an operating system.

Name Version Maintenance Hardware

1 Android 4.1 And future OS versions and fix packs

2 iOS 9.2 And future OS versions and fix packs

41 of 53

HCL Connections 6.0 System Requirements Review Report

3.2.4.2 Component restrictions for the Mobile OS family

In some deliverables, not all parts of the deployment structure can run on all of the operating systems in a specific family. This table lists the operating systems from Section 3.2.4.1. that are supported by the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the The component must be on one of the indicated operating systems column are accurate and that there are no missing restrictions.

Deployment unit Components The component must be on one of the indicated operating systems

1 Desktop 1 No component None of the Mobile OS operating systems supported by the deliverable

2 Server 2 No component None of the Mobile OS operating systems supported by the deliverable

3 Mobile Device 3 No component Any Mobile OS operating system supported by the deliverable

3.2.4.3 Application bitness for the Mobile OS family

The deliverable is capable of running with the bitness specified in the Application bitness column for the operating system entry.

Reviewers tips Verify that support for Application bitness is accurate and complete for the associated operating systems.

Name Version Maintenance Hardware Application bitness

1 Android 4.1 And future OS versions and fix packs

2 iOS 9.2 And future OS versions and fix packs

3.2.4.4 Notes for the Mobile OS family

This table contains a section for any of the operating system supported by this deliverable that has additional support notes that might influence the selection of a particular operating system choice.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include component usage restrictions, as well as the information on supported OS fixpacks shown in the Maintenance column of the table in Section 3.2.4.1.

The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for:

1 None provided

42 of 53

HCL Connections 6.0 System Requirements Review Report

3.2.5 Windows family

3.2.5.1 Supported operating system summary

The operating systems for the Windows family that are supported by this deliverable are enumerated in this

table.

Reviewers tips Additional details that can be confirmed using this table are:

1. The operating systems listed in this table should be those supported by the specific level of the deliverable identified at the top of this report, and should not

include operating systems that require additional fixpacks of the deliverable.

2. The Maintenance column should include 'and future fix packs', unless the product only supports specific OS fixpacks, in which case those fixpacks should be

listed.

3. If the Maintenance column includes 'and future versions', make sure that this is consistent with the deliverable's support policy. It is unusual to make a support

statement covering all future versions of an operating system.

Name Version Maintenance Hardware

1 Windows 7 Enterprise Service Pack 1 and future OS fix packs x86-32

2 Windows 7 Enterprise Service Pack 1 and future OS fix packs x86-64

3 Windows 7 Professional Service Pack 1 and future OS fix packs x86-32

4 Windows 7 Professional Service Pack 1 and future OS fix packs x86-64

5 Windows 7 Ultimate Service Pack 1 and future OS fix packs x86-32

6 Windows 7 Ultimate Service Pack 1 and future OS fix packs x86-64

7 Windows Server 2012 Datacenter Edition R2 And future OS fix packs x86-64

8 Windows Server 2012 Essentials Edition R2 And future OS fix packs x86-64

9 Windows Server 2012 Standard Edition R2 And future OS fix packs x86-64

10 Windows Server 2016 Datacenter Edition And future OS fix packs x86-64

11 Windows Server 2016 Essentials Edition And future OS fix packs x86-64

12 Windows Server 2016 Standard Edition And future OS fix packs x86-64

13 Windows Enterprise 10 And future OS fix packs x86-32

14 Windows Enterprise 10 And future OS fix packs x86-64

15 Windows Enterprise 8.1 And future OS versions and fix packs x86-32

16 Windows Enterprise 8.1 And future OS versions and fix packs x86-64

17 Windows Pro 10 And future OS fix packs x86-32

18 Windows Pro 10 And future OS versions and fix packs x86-64

19 Windows Professional 8.1 And future OS versions and fix packs x86-32

20 Windows Professional 8.1 And future OS versions and fix packs x86-64

21 Windows Standard 8.1 And future OS versions and fix packs x86-32

22 Windows Standard 8.1 And future OS versions and fix packs x86-64

43 of 53

HCL Connections 6.0 System Requirements Review Report

3.2.5.2 Component restrictions for the Windows family

In some deliverables, not all parts of the deployment structure can run on all of the operating systems in a

specific family. This table lists the operating systems from Section 3.2.5.1. that are supported by the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the The component must be on one of the indicated operating systems column are accurate and that there are no missing restrictions.

Deployment unit Components The component must be on one of the indicated operating systems

1 Desktop 1 No component Any Windows operating system supported by the deliverable

2 Server 2 No component Specific Windows operating systems (operating systems in grey are not supported) 1. Windows 7 Enterprise Service Pack 1 and future OS fix packs x86-32 2. Windows 7 Enterprise Service Pack 1 and future OS fix packs x86-64 3. Windows 7 Professional Service Pack 1 and future OS fix packs x86-32 4. Windows 7 Professional Service Pack 1 and future OS fix packs x86-64 5. Windows 7 Ultimate Service Pack 1 and future OS fix packs x86-32 6. Windows 7 Ultimate Service Pack 1 and future OS fix packs x86-64 7. Windows Enterprise 10 and future OS fix packs x86-32 8. Windows Enterprise 10 and future OS fix packs x86-64 9. Windows Enterprise 8.1 and future OS versions and fix packs x86-32 10. Windows Enterprise 8.1 and future OS versions and fix packs x86-64 11. Windows Pro 10 and future OS fix packs x86-32 12. Windows Pro 10 and future OS versions and fix packs x86-64 13. Windows Professional 8.1 and future OS versions and fix packs x86-32 14. Windows Professional 8.1 and future OS versions and fix packs x86-64 15. Windows Server 2012 Datacenter Edition R2 and future OS fix packs x86-64 16. Windows Server 2012 Essentials Edition R2 and future OS fix packs x86-64 17. Windows Server 2012 Standard Edition R2 and future OS fix packs x86-64 18. Windows Server 2016 Datacenter Edition and future OS fix packs x86-64 19. Windows Server 2016 Essentials Edition and future OS fix packs x86-64 20. Windows Server 2016 Standard Edition and future OS fix packs x86-64 21. Windows Standard 8.1 and future OS versions and fix packs x86-32 22. Windows Standard 8.1 and future OS versions and fix packs x86-64

3 Mobile Device 3 No component None of the Windows operating systems supported by the deliverable

44 of 53

HCL Connections 6.0 System Requirements Review Report

3.2.5.3 Application bitness for the Windows family

The deliverable is capable of running with the bitness specified in the Application bitness column for the operating system entry.

Reviewers tips Verify that support for Application bitness is accurate and complete for the associated operating systems.

Name Version Maintenance Hardware Application bitness

1 Windows 7 Enterprise Service Pack 1 and future OS fix x86-32 32 packs

2 Windows 7 Enterprise Service Pack 1 and future OS fix x86-64 64-Tolerate packs

3 Windows 7 Professional Service Pack 1 and future OS fix x86-32 32 packs

4 Windows 7 Professional Service Pack 1 and future OS fix x86-64 64-Tolerate packs

5 Windows 7 Ultimate Service Pack 1 and future OS fix x86-32 32 packs

6 Windows 7 Ultimate Service Pack 1 and future OS fix x86-64 64-Tolerate packs

7 Windows Server 2012 Datacenter Edition R2 And future OS fix packs x86-64 64-Tolerate

8 Windows Server 2012 Essentials Edition R2 And future OS fix packs x86-64 64-Tolerate

9 Windows Server 2012 Standard Edition R2 And future OS fix packs x86-64 64-Tolerate

10 Windows Server 2016 Datacenter Edition And future OS fix packs x86-64 64-Tolerate

11 Windows Server 2016 Essentials Edition And future OS fix packs x86-64 64-Tolerate

12 Windows Server 2016 Standard Edition And future OS fix packs x86-64 64-Tolerate

13 Windows Enterprise 10 And future OS fix packs x86-32 32

14 Windows Enterprise 10 And future OS fix packs x86-64 64-Tolerate

15 Windows Enterprise 8.1 And future OS versions and fix packs x86-32 32

16 Windows Enterprise 8.1 And future OS versions and fix packs x86-64 64-Tolerate

17 Windows Pro 10 And future OS fix packs x86-32 32

18 Windows Pro 10 And future OS versions and fix packs x86-64 64-Tolerate

19 Windows Professional 8.1 And future OS versions and fix packs x86-32 32

20 Windows Professional 8.1 And future OS versions and fix packs x86-64 64-Tolerate

21 Windows Standard 8.1 And future OS versions and fix packs x86-32 32

22 Windows Standard 8.1 And future OS versions and fix packs x86-64 64-Tolerate

45 of 53

HCL Connections 6.0 System Requirements Review Report

3.2.5.4 Notes for the Windows family

This table contains a section for any of the operating system supported by this deliverable that has additional support notes that might influence the selection of a particular operating system choice.

Reviewers tips The support notes listed here should not cover ?restrictions? detailed in other sections of this report. These include component usage restrictions, as well as the information on supported OS fixpacks shown in the Maintenance column of the table in Section 3.2.5.1. The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for: Windows Server 2016 Essentials Edition and future OS fix packs x86-64 Windows Server 2016 Datacenter Edition and future OS fix packs x86-64 Windows Server 2016 Standard Edition and future OS fix packs x86-64

1 HCL Connections Content Manager 5.5 does not support 2016 Server.

3.3 Supported Hypervisors

3.3.1 Supported Hypervisors

The hypervisors supported by this deliverable are enumerated in this table along with the supported guest operating systems.

Reviewers tips Verify the hypervisor list and associated guest operating systems are accurate and complete.

Details that should be confirmed using this table are:

1. The hypervisors listed in this table should be those supported by the specific level of the deliverable identified at the top of this report, and should not include

hypervisors that require additional fixpacks of the deliverable.

2. If there are operating systems listed in Section 3.2.x that are supported by the hypervisor but not by the deliverable when running in the hypervisor, an explicit

list of supported guest operating systems specified in the edit guest operating system.

Hypervisor Guest operating systems

1 None specified

46 of 53

HCL Connections 6.0 System Requirements Review Report

3.3.2 Component restrictions

In some deliverables, not all parts of the deployment structure support the full list of hypervisors supported by the deliverable as a whole. This table lists the hypervisors from Section 3.3.1 that are not supported by the specified deployment units and/or deployable components.

Reviewers tips Subject matter experts familiar with the working details of specific deployment units or deployable components need to confirm that the restrictions identified in the "Hypervisors not supported" column are accurate and that there are no missing restrictions.

Deployment unit Components Hypervisors not supported

1 Desktop 1 No component No restriction

2 Server 2 No component No restriction

3 Mobile Device 3 No component No restriction

3.3.3 Notes

This table contains a section for any of the supported hypervisors that have additional support notes that might influence the selection of a hypervisor.

Reviewers tips The support notes listed here should not cover restrictions covered in other sections of this report. These include component usage restrictions, as well as the information on supported guest operating systems shown in the Guest operating systems column of the table in Section 3.3.1. The notes should be for the specific level of the deliverable identified at the top of this report, and should not describe support that requires additional fixpacks of the deliverable.

Footnotes for:

1 None provided

4. Hardware requirements

47 of 53

HCL Connections 6.0 System Requirements Review Report

Introduction

There is a 4.x section for each of the hardware requirements that are specified for this deliverable.

Reviewers tips These sections should provide details of the recommended minimum requirements for a typical use of this deliverable. For deliverables that have a deployment unit and/or deployable component with a delivery format of native install or virtual appliance, there should at least be a section for disk space and memory. For other delivery formats hardware requirements can be specified but they aren't as common.

4.1 Disk Space

The Disk Space requirements for the deployment units and/or deployable components are specified in the ?Requirements? column in the following table. For deliverables that have a deployment unit and/or deployable component with a delivery format of native install, these requirements are applicable to the operating systems enumerated in the ?Applicable operating system? column. For deliverables that have a deployment unit and/or deployable component with a delivery format other than native install, the notion of ?applicable operating system? does not apply since these delivery formats do not have operating system requirements. When the Disk

Space requirements are the same for multiple deployment units and/or deployable components, the details are specified once and referenced by other pieces.

Reviewers tips None.

Deployment unit Components Requirements Operating systems in the OS family to which requirement applies

1 Desktop 1 No component Post Install & Configuration Apply to all operating systems supported by Requirements: the deliverable - 100GB / system

Installation Server: Apply to all operating systems supported by - 10 MB of space required in the the deliverable installer \temp directory

- 10 MB of space required in the IM repository C:\ProgramData \HCL\Installation Manager

- 130 MB of space required in the IM installation C:\Program Files\HCL\Installation Manager directory.

- 6G of available space for the directory which has WebSphere Application Server installed: Linux; /opt/HCL/WebSphere /AppServer - Microsoft Windows C:\Program Files\HCL\WebSphere\AppServer

- 1G of available space for the HCL Connections installation home directory: Linux: /opt/HCL/LotusConnections Microsoft Windows: C:\Program Files\HCL\LotusConnections

Minimum recommended disk Apply to all operating systems supported by space required by HCL the deliverable Connections feature: Activities - 10 GB for Content store - 10 GB for Content store Bookmarks - 600 MB for FavIcons Communities - 3 GB for forum content Files - 10 GB Forums - 10 GB

48 of 53

HCL Connections 6.0 System Requirements Review Report

Introduction

There is a 4.x section for each of the hardware requirements that are specified for this deliverable.

Reviewers tips These sections should provide details of the recommended minimum requirements for a typical use of this deliverable. For deliverables that have a deployment unit and/or deployable component with a delivery format of native install or virtual appliance, there should at least be a section for disk space and memory. For other delivery formats hardware requirements can be specified but they aren't as common.

4.1 Disk Space Home page - 100 MB Mobile - Not required News - 500 MB per Message Store Profiles - 30 MB for Cache files directory Search - 15 GB for Index files directory. - 10 GB

Note: The sizes of these directories will grow as the number of users increases. Monitor the space availability to know when to increase capacity. See the Administration section of the HCL Connections Information Center for more information.

Disk space required for: - Content store (Holds files, images etc)

- File upload directory stores files uploaded to people's Blogs. Note: must add to a shared drive if you are setting up a network deployment.

- Cache files directory

- Index files directory

- Temporary download location for indexing Files content Directory size planning guidance:

- Blogs Default = 4MB Recommend 4MB x # of Blogs being hosted with at least 400MB to start

- Bookmarks The icons that are displayed on Bookmarks are stored in FavIcons file directory. This directory must have at least 150 MB of space for a deployment with 250,000 bookmarks.

- News Message store requirement of 500MB per message store engine will be determined by deployment choice. Network Deployment: 1 messaging engine/cluster.

- Search The disk space requirement for the search index is dependent on the amount of content in the individual Lotus Connections features and this requirement will grow as the HCL Connections content grows. It is recommended to ensure that a

49 of 53

HCL Connections 6.0 System Requirements Review Report

Introduction

There is a 4.x section for each of the hardware requirements that are specified for this deliverable.

Reviewers tips These sections should provide details of the recommended minimum requirements for a typical use of this deliverable. For deliverables that have a deployment unit and/or deployable component with a delivery format of native install or virtual appliance, there should at least be a section for disk space and memory. For other delivery formats hardware requirements can be specified but they aren't as common.

4.1 Disk Space minimum of 2.5 times the size of the index directory is available to allow for operations such as index optimization.

HCL Connections Content Manager :

Temp disk space: 3GB (default in /tmp on Unix systems; %Temp% on Windows). If there is insufficient disk space in the default location then an environment variable may be set to point to a location with sufficient space: IATEMPDIR Disk space for Configuration Manager : 35 MB Disk space for HCL FileNet Content Platform Engine: 5 GB, Temp Space 5 GB

Hardware requirements listed Apply to all operating systems supported by below are for Server the deliverable Requirements.

Pre-install Requirements by HCL Connections feature: (uncompressed)

Activities 132MB Blogs 157MB Communities 140MB Bookmarks 125MB Files 66MB Forums 114MB Help 55MB Homepage 129MB HCL Cognos BI 2.79 GB HCL Cognos Transformer 1.00 GB Metrics 130MB Mobile 34MB Moderation 110M News 117MB Profiles 170MB Search 127MB Wikis 85MB

Initial install will require 11 GB of disk space for all of HCL Connections Components, including WAS ND, Deployment Manager and blank set of DB2 Databases.

2 Server 2 No component Same as Desktop

Same as Desktop

Same as Desktop

Same as Desktop

3 Mobile Device 3 No component Same as Desktop

50 of 53

HCL Connections 6.0 System Requirements Review Report

Introduction

There is a 4.x section for each of the hardware requirements that are specified for this deliverable.

Reviewers tips These sections should provide details of the recommended minimum requirements for a typical use of this deliverable. For deliverables that have a deployment unit and/or deployable component with a delivery format of native install or virtual appliance, there should at least be a section for disk space and memory. For other delivery formats hardware requirements can be specified but they aren't as common.

4.1 Disk Space Same as Desktop

Same as Desktop

Same as Desktop

51 of 53

HCL Connections 6.0 System Requirements Review Report

4.2 Memory

The Memory requirements for the deployment units and/or deployable components are specified in the ?Requirements? column in the following table. These requirements are applicable to the operating systems enumerated in the ?Applicable operating system? column. When the Memory requirements are the same for multiple deployment units and/or deployable components, the details are specified once and referenced by other pieces.

Reviewers tips None.

Deployment unit Components Requirements Operating systems in the OS family to which requirement applies

1 Desktop 1 No component Apply to all operating systems supported by Memory requirement for the deliverable x86-32/64 and POWER Intel (x86-32 or x86-64 compatible server systems) and POWER systems per HCL Connections node:

Application Node: - Two processor cores per server, 2.0 GHz CPU speed, or higher - Minimum 8 GB of memory for HCL Connections Server - For enterprise-scale deployments, at least 4 CPU and 16 GB of memory is recommended

Database server: - 4 processor cores per server, 2.0 GHz CPU speed, or higher - Minimum 8 GB of memory - For enterprise-scale deployment, at least 16 GB of memory is recommended

- 50 GB of available disk space after installation and configuration of the base operating system Apply to all operating systems supported by Memory requirement for System the deliverable z

Application Node: - At least 2 system z9 processors with Integrated Facility for Linux (IFL) - Minimum 8 GB of memory for HCL Lotus Connection Server - For enterprise-scale deployments, at least 4 CPUs and 16 GB of memory is recommended

Database server: - 4 system z9 processors with Integrated Facility for Linux (IFL) - Minimum 8 GB of memory - For enterprise-scale deployment, at least 16 GB of memory is recommended

- 50 GB of available disk space after installation and configuration of the base operating system

2 Server 2 No component Same as Desktop

Same as Desktop

52 of 53

HCL Connections 6.0 System Requirements Review Report

4.2 Memory

3 Mobile Device 3 No component Same as Desktop

Same as Desktop

53 of 53