hcl connections 5.5 cr3 - support.hcltechsw.com

51
Software Product Compatibility Reports Detailed System Requirements Product HCL Connections 5.5 CR3

Upload: others

Post on 28-Apr-2022

7 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: HCL Connections 5.5 CR3 - support.hcltechsw.com

Software Product Compatibility Reports

Detailed System Requirements

Product

HCL Connections 5.5 CR3

Page 2: HCL Connections 5.5 CR3 - support.hcltechsw.com

2 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

Contents

This document contains the detailed system requirements specified in the Clearinghouse database for the HCL Connections 5.5 CR3 deliverable. This deliverable is planned to ship with the MSI name HCL Connections with the release level of 5.5 CR3.

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 Operating System 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

1.1 Deployment structure

1.2 Packaging list

1.3 Integrated products

2. Software requirements

2.1 Capabilities used by components

2.2 Capabilities details

2.2.1 Application Servers

2.2.2 Installation

2.2.3 Collaboration

2.2.4 Connectors

2.2.5 Databases

2.2.6 E-mail Application

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

3. Operating systems

3.1 Supported operating systems

3.2 Families details

3.2.1 AIX

3.2.2 Linux

3.2.3 Mac OS

3.2.4 Mobile OS

3.2.5 Windows

3.3 Supported Hypervisors

4. Hardware requirements

NOTE: Hardware requirements are reviewed only at the release or mod level.

Page 3: HCL Connections 5.5 CR3 - support.hcltechsw.com

3 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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

Page 4: HCL Connections 5.5 CR3 - support.hcltechsw.com

4 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

1.2 Packaging list

When this deliverable is purchased by a client, 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 No products are co-packaged

Page 5: HCL Connections 5.5 CR3 - support.hcltechsw.com

5 of 50

HCL Connections 5.5 CR3: 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

Page 6: HCL Connections 5.5 CR3 - support.hcltechsw.com

6 of 50

HCL Connections 5.5 CR3: 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

1. Application Servers

2. Installation

Additional

3. Collaboration

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 Y Y Y Y Y Y Y N Y

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

2.2 Capabilities details

Page 7: HCL Connections 5.5 CR3 - support.hcltechsw.com

7 of 50

HCL Connections 5.5 CR3: 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. 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.12 interact

2 WebSphere Application Server Network Deployment 8.5.5.6 interact

3 WebSphere Application Server Network Deployment 8.5.5.7 interact

4 WebSphere Application Server Network Deployment 8.5.5.8 interact

5 WebSphere Application Server Network Deployment 8.5.5.9 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 5 products listed in this capability

Page 8: HCL Connections 5.5 CR3 - support.hcltechsw.com

8 of 50

HCL Connections 5.5 CR3: 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.12 WebSphere Application Server Network Deployment 8.5.5.9 WebSphere Application Server Network Deployment 8.5.5.7 WebSphere Application Server Network Deployment 8.5.5.8 WebSphere Application Server Network Deployment 8.5.5.6

1 HCL Connections v5.5 relies on the Java default version SDK 1.6 for WebSphere Application Server Network Deployment.

Page 9: HCL Connections 5.5 CR3 - support.hcltechsw.com

9 of 50

HCL Connections 5.5 CR3: 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 IBM Installation Manager 1.8.3 and future fix packs, mod levels and their fix packs

on the same machine

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

Page 10: HCL Connections 5.5 CR3 - support.hcltechsw.com

10 of

HCL Connections 5.5 CR3: 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

Page 11: HCL Connections 5.5 CR3 - support.hcltechsw.com

10 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 and future fix packs

interact

2 HCL Sametime Complete 9.0 and future fix packs

interact

3 HCL Sametime Unified Telephony Lite Client 1 and future fix packs

interact

4 Microsoft SharePoint Server 2010 and future fix packs

interact

5 Microsoft SharePoint Server 2013 and future fix packs

interact

6 Microsoft Windows SharePoint Foundation 2010 and future fix packs

interact

Page 12: HCL Connections 5.5 CR3 - support.hcltechsw.com

11 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 HCL Connections Docs 2.0 and future fix packs

Any AIX, Linux, Windows operating systems supported by the deliverable.

None of the Mac OS, Mobile OS operating systems supported by the deliverable.

2 Microsoft SharePoint Server 2010 and future fix packs

Any Linux, Windows operating systems supported by the deliverable.

None of the AIX, Mac OS, Mobile OS operating systems supported by the deliverable.

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

Page 13: HCL Connections 5.5 CR3 - support.hcltechsw.com

12 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 Sametime Unified Telephony Lite Client 1

1 Cautionary Note * Sametime 8.5.2IFR1 iFix level required for use with HCL Connections 5.0 is still being finalized.

Footnotes for: HCL Sametime Complete 9.0

2 Cautionary Note * Sametime 9.0 Fix level required for use with HCL Connections 5.0 is still being finalized.

Footnotes for: Microsoft SharePoint Server 2010

3 The HCL Connections Plug-in for Microsoft SharePoint and HCL Connections Widget for Microsoft SharePoint

support Microsoft SharePoint 2010 and Microsoft SharePoint 2013."

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 and future fix packs

interact

Page 14: HCL Connections 5.5 CR3 - support.hcltechsw.com

13 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 and future fix packs

Any AIX, Linux, Windows operating systems supported by the deliverable.

None of the Mac OS, Mobile OS operating systems supported by the deliverable.

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 Atom protocol

Page 15: HCL Connections 5.5 CR3 - support.hcltechsw.com

14 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 10.5.0.5 and future fix packs

interact

2 DB2 for i5/OS 7.1 and future fix packs

interact

3 DB2 for i5/OS 7.2 and future fix packs

interact

4 Microsoft SQL Server Enterprise Edition 2012 and future fix packs

interact

5 Microsoft SQL Server Standard Edition 2012 and future fix packs

interact

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

interact

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

interact

Page 16: HCL Connections 5.5 CR3 - support.hcltechsw.com

15 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 7 products listed in this capability

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

Page 17: HCL Connections 5.5 CR3 - support.hcltechsw.com

16 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 FP1 Social Edition and future fix packs

interact

2 Lotus Notes 8.5.3 and future fix packs

interact

3 Microsoft Outlook 2010 and future fix packs

interact

4 Microsoft Outlook 2013 and future fix packs

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 Lotus Notes 8.5.3 and future fix packs

Any AIX, Linux, Windows operating systems supported by the deliverable.

None of the Mac OS, Mobile OS operating systems supported by the deliverable.

2 Microsoft Outlook 2010 and future fix packs

Any Linux, Windows operating systems supported by the deliverable.

None of the AIX, Mac OS, Mobile OS operating systems supported by the deliverable.

Page 18: HCL Connections 5.5 CR3 - support.hcltechsw.com

17 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 No restriction

3 Mobile Device 3 No component No restriction

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: Microsoft Outlook 2010

1 The HCL Connections Plug-in for Microsoft Outlook is supported on HCL Connections 5.0 and higher.

Footnotes for: Lotus Notes 8.5.3

2 The HCL Connections Plug-ins for HCL Notes support HCL Lotus Notes 8.5.3 FP1, FP2, FP3, FP4, FP5, FP6.

Footnotes for: HCL Notes 9.0.1 FP1 Social Edition

3 HCL Connections Plug-in for HCL Notes

Page 19: HCL Connections 5.5 CR3 - support.hcltechsw.com

18 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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

Page 20: HCL Connections 5.5 CR3 - support.hcltechsw.com

19 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 3 is a required package after installing TDI v7.1.1.

Page 21: HCL Connections 5.5 CR3 - support.hcltechsw.com

20 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 and future fix packs

interact

2 IBM Security Directory Server 6.3.1 and future fix packs

interact

3 Lotus Domino 8.5.3 and future fix packs

interact

4 Microsoft Active Directory 2012 R2 and future fix packs

interact

5 NetIQ eDirectory 8.8 SP8 and future fix packs

interact

6 Novell eDirectory 8.8 and future fix packs

interact

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

interact

Page 22: HCL Connections 5.5 CR3 - support.hcltechsw.com

21 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 Novell eDirectory 8.8 and future fix packs

Any AIX, Linux, Windows operating systems supported by the deliverable.

None of the Mac OS, Mobile OS operating systems supported by the deliverable.

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: Novell eDirectory 8.8

1 Service Pack 8

Page 23: HCL Connections 5.5 CR3 - support.hcltechsw.com

22 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 8.5 and future fix packs

interact

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

Page 24: HCL Connections 5.5 CR3 - support.hcltechsw.com

23 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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

Page 25: HCL Connections 5.5 CR3 - support.hcltechsw.com

24 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 and future fix packs

interact

2 Microsoft Office 2010 and future fix packs

interact

3 Microsoft Office 2013 and future fix packs

interact

4 Microsoft Office 2016 and future fix packs

interact

5 No MSI Name (Deliverable Name: Sametime Limited Use) 9.0 and future fix packs

interact

Page 26: HCL Connections 5.5 CR3 - support.hcltechsw.com

25 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 Microsoft Office 2010 and future fix packs

None of the AIX, Linux, Mac OS, Mobile OS operating systems supported by the deliverable.

Specific Windows operating systems (operating systems in grey are not supported) 1. Windows 7 Enterprise Service Pack 1 x86-32 2. Windows 7 Enterprise Service Pack 1 x86-64

3. Windows 7 Professional Service Pack 1 x86-32

4. Windows 7 Professional Service Pack 1 x86-64 5. Windows 7 Ultimate Service Pack 1 x86-32 6. Windows 7 Ultimate Service Pack 1 x86-64 7. Windows 8 Standard x86-64

8. Windows Enterprise 10 x86-32 9. Windows Enterprise 10 x86-64

10. Windows Enterprise 8.1 x86-32 11. Windows Enterprise 8.1 x86-64 12. Windows Pro 10 x86-32 13. Windows Pro 10 x86-64

14. Windows Professional 8.1 x86-32 15. Windows Professional 8.1 x86-64 16. Windows Server 2008 Datacenter Edition R2 x86-64 17. Windows Server 2008 Enterprise Edition R2 x86-64 18. Windows Server 2008 Standard Edition R2 x86-64 19. Windows Server 2012 Datacenter Edition R2 x86-64

20. Windows Server 2012 Essentials Edition R2 x86-64 21. Windows Server 2012 Standard Edition R2 x86-64 22. Windows Standard 8.1 x86-32 23. Windows Standard 8.1 x86-64

2 Microsoft Office 2013 and future fix packs

None of the AIX, Linux, Mac OS, Mobile OS operating systems supported by the deliverable.

Specific Windows operating systems (operating systems in grey are not supported) 1. Windows 7 Enterprise Service Pack 1 x86-32 2. Windows 7 Enterprise Service Pack 1 x86-64 3. Windows 7 Professional Service Pack 1 x86-32 4. Windows 7 Professional Service Pack 1 x86-64 5. Windows 7 Ultimate Service Pack 1 x86-32 6. Windows 7 Ultimate Service Pack 1 x86-64 7. Windows 8 Standard x86-64 8. Windows Enterprise 10 x86-32 9. Windows Enterprise 10 x86-64

10. Windows Enterprise 8.1 x86-32 11. Windows Enterprise 8.1 x86-64 12. Windows Pro 10 x86-32

13. Windows Pro 10 x86-64 14. Windows Professional 8.1 x86-32 15. Windows Professional 8.1 x86-64 16. Windows Server 2008 Datacenter Edition R2 x86-64

Page 27: HCL Connections 5.5 CR3 - support.hcltechsw.com

26 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

17. Windows Server 2008 Enterprise Edition R2 x86-64 18. Windows Server 2008 Standard Edition R2 x86-64

19. Windows Server 2012 Datacenter Edition R2 x86-64 20. Windows Server 2012 Essentials Edition R2 x86-64 21. Windows Server 2012 Standard Edition R2 x86-64 22. Windows Standard 8.1 x86-32 23. Windows Standard 8.1 x86-64

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: Microsoft Office 2010

1 The HCL Connections Desktop Plug-ins for Microsoft Windows are supported on HCL Connections 5.0 and higher.

Files, News, and Profiles must be deployed on the server for the plug-ins to function properly.

Metrics works only with HCL Connections v4.5 CR2 or higher.

Page 28: HCL Connections 5.5 CR3 - support.hcltechsw.com

27 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 Cognos Business Intelligence 10.2.2.0 and future fix packs

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

Page 29: HCL Connections 5.5 CR3 - support.hcltechsw.com

28 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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:

1 None provided

Page 30: HCL Connections 5.5 CR3 - support.hcltechsw.com

29 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 and future fix packs

interact

2 IBM Security Access Manager for Web 7.0.0.2 and future fix packs

interact

3 IBM Security Access Manager for Web 8.0 and future fix packs

interact

4 No MSI Name (Deliverable Name: Java SPNEGO (Simple and Protected Negotiation) n/a)

interact

5 Tivoli Access Manager for e-business 6.1 and future fix packs

interact

Page 31: HCL Connections 5.5 CR3 - support.hcltechsw.com

30 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 and future fix packs

Any AIX, Linux, Mac OS, Windows operating systems supported by the deliverable.

None of the Mobile OS operating systems supported by the deliverable.

2 No MSI Name (Deliverable Name: Java SPNEGO (Simple and Protected Negotiation) n/a)

Any AIX, Linux, Windows operating systems supported by the deliverable.

None of the Mac OS, Mobile OS operating systems supported by the deliverable.

3 Tivoli Access Manager for e-business 6.1 and future fix packs

Any AIX, Linux, Windows operating systems supported by the deliverable.

None of the Mac OS, Mobile OS operating systems supported by the deliverable.

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

Page 32: HCL Connections 5.5 CR3 - support.hcltechsw.com

31 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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: No MSI Name (Deliverable Name: Java SPNEGO (Simple and Protected Negotiation) n/a)

1 SPNEGO/Kerberos (WAS 8.5 based)

Footnotes for: Tivoli Access Manager for e-business 6.1

2 Not Supported by HCL Connections 3.0 Portlets for WebSphere Portal

6.1 Fixpack 4 and greater

Page 33: HCL Connections 5.5 CR3 - support.hcltechsw.com

32 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 Safari 8.0 and future fix packs

interact

2 Google Chrome 43 and future fix packs

interact

3 Microsoft Edge 34 and future fix packs

interact

4 Microsoft Internet Explorer 11 and future fix packs

interact

5 Mozilla Firefox 38 and future fix packs

interact

6 Mozilla Firefox ESR 38 and future fix packs

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

Page 34: HCL Connections 5.5 CR3 - support.hcltechsw.com

33 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 No restriction

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 Mozilla Firefox ESR 38

Apple Safari 8.0 Mozilla Firefox 38 Google Chrome 43

1 Mobile only supports accessing HCL Connections using the native mobile apps.

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.

Footnotes for: Microsoft Edge 34

2 Mobile only supports accessing HCL Connections using the native mobile apps.

Page 35: HCL Connections 5.5 CR3 - support.hcltechsw.com

34 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 IBM 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

Page 36: HCL Connections 5.5 CR3 - support.hcltechsw.com

35 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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: IBM HTTP Server 8.5.5

1 HCL Connections 5.5 supports the same IBM HTTP Server 8.5.5 Fixpack levels as shown for Websphere Application Server (see Prerequisites section of the report).

3. Operating systems

Page 37: HCL Connections 5.5 CR3 - support.hcltechsw.com

36 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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

6.1

7.1

Linux

2

Red Hat Enterprise Linux (RHEL) Client

6

7

3

Red Hat Enterprise Linux (RHEL) Server

6

7

4

Red Hat Enterprise Linux (RHEL)

Advanced Platform 5

5

SUSE Linux Enterprise Desktop (SLED)

11.0

6

SUSE Linux Enterprise Server (SLES)

12

Mac OS

7

OS X El Capitan

10.11

8

OS X

Yosemite 10.10

Mobile OS

9

Android

4.1

10

iOS

9.2

Windows

11

Windows 7

Enterprise

12

Windows 8

Standard

13

Windows Server 2008

Datacenter Edition R2

14

Windows Server 2012

Datacenter Edition R2

15

Windows

Enterprise 8.1

Enterprise 10

Pro 10

Professional 8.1

Page 38: HCL Connections 5.5 CR3 - support.hcltechsw.com

37 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

3.2 Families details

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 6.1 TL7 and future OS fix packs POWER System - Big Endian

2 AIX 7.1 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

Page 39: HCL Connections 5.5 CR3 - support.hcltechsw.com

38 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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

6.1

TL7 and future OS fix packs

POWER System - Big Endian

64-Tolerate

2

AIX

7.1

And future OS versions and fix packs

POWER System - Big Endian

64-Tolerate

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

POWER7 in POWER6 mode

AIX 6.1 TL7 and future OS 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 6.1 TL7 and future OS fix packs POWER System - Big Endian AIX 7.1 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

Page 40: HCL Connections 5.5 CR3 - support.hcltechsw.com

39 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 6 6.6 and future OS fix packs x86-32

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

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

4 Red Hat Enterprise Linux (RHEL) Server 6 6.6 and future OS fix packs IBM z Systems

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

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

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

8 Red Hat Enterprise Linux (RHEL) Advanced Platform 5 5.11 and future OS fix packs IBM z Systems

9 Red Hat Enterprise Linux (RHEL) Advanced Platform 5 5.11 and future OS fix packs x86-64

10 Red Hat Enterprise Linux (RHEL) Desktop editions 5 5.11 and future OS fix packs x86-32

11 Red Hat Enterprise Linux (RHEL) Desktop editions 5 5.11 and future OS fix packs x86-64

12 SUSE Linux Enterprise Desktop (SLED) 11.0 SP3 and future OS fix packs x86-32

13 SUSE Linux Enterprise Desktop (SLED) 11.0 SP3 and future OS fix packs x86-64

14 SUSE Linux Enterprise Server (SLES) 12 And future OS fix packs IBM z Systems

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

Page 41: HCL Connections 5.5 CR3 - support.hcltechsw.com

40 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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) Advanced Platform 5 5.11 and future

OS fix packs IBM z Systems

2. Red Hat Enterprise Linux (RHEL) Advanced Platform 5 5.11 and future

OS fix packs x86-64

3. Red Hat Enterprise Linux (RHEL) Client 6 6.6 and future OS fix packs

x86-32

4. Red Hat Enterprise Linux (RHEL) Client 6 6.6 and future OS fix packs x86-64

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

6. Red Hat Enterprise Linux (RHEL) Desktop editions 5 5.11 and future OS fix packs x86-32

7. Red Hat Enterprise Linux (RHEL) Desktop editions 5 5.11 and future OS

fix packs x86-64

8. Red Hat Enterprise Linux (RHEL) Server 6 6.6 and future OS fix packs IBM z Systems

9. Red Hat Enterprise Linux (RHEL) Server 6 6.6 and future OS fix packs x86-64

10. Red Hat Enterprise Linux (RHEL) Server 7 7.1 and future OS fix packs

IBM z Systems

11. Red Hat Enterprise Linux (RHEL) Server 7 7.1 and future OS fix packs

x86-64

12. SUSE Linux Enterprise Desktop (SLED) 11.0 SP3 and future OS fix packs x86-32

13. SUSE Linux Enterprise Desktop (SLED) 11.0 SP3 and future OS fix packs

x86-64

14. SUSE Linux Enterprise Server (SLES) 12 and future OS fix packs IBM z

Systems

15. 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) Advanced Platform 5 5.11 and future

OS fix packs IBM z Systems

2. Red Hat Enterprise Linux (RHEL) Advanced Platform 5 5.11 and future OS fix packs x86-64

3. Red Hat Enterprise Linux (RHEL) Client 6 6.6 and future OS fix packs x86-32

4. Red Hat Enterprise Linux (RHEL) Client 6 6.6 and future OS fix packs

x86-64

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

6. Red Hat Enterprise Linux (RHEL) Desktop editions 5 5.11 and future OS fix packs x86-32

Page 42: HCL Connections 5.5 CR3 - support.hcltechsw.com

41 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

7. Red Hat Enterprise Linux (RHEL) Desktop editions 5 5.11 and future OS fix packs x86-64

8. Red Hat Enterprise Linux (RHEL) Server 6 6.6 and future OS fix packs IBM z Systems

9. Red Hat Enterprise Linux (RHEL) Server 6 6.6 and future OS fix packs x86-64

10. Red Hat Enterprise Linux (RHEL) Server 7 7.1 and future OS fix packs

IBM z Systems

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

12. SUSE Linux Enterprise Desktop (SLED) 11.0 SP3 and future OS fix packs x86-32

13. SUSE Linux Enterprise Desktop (SLED) 11.0 SP3 and future OS fix packs

x86-64

14. SUSE Linux Enterprise Server (SLES) 12 and future OS fix packs IBM z

Systems

15. 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

6

6.6 and future OS fix packs

x86-32

32

2

Red Hat Enterprise Linux (RHEL) Client

6

6.6 and future OS fix packs

x86-64

64-Tolerate

3

Red Hat Enterprise Linux (RHEL) Client

7

7.1 and future OS fix packs

x86-64

64-Tolerate

4

Red Hat Enterprise Linux (RHEL) Server

6

6.6 and future OS fix packs

IBM z Systems

64-Tolerate

5

Red Hat Enterprise Linux (RHEL) Server

6

6.6 and future OS fix packs

x86-64

64-Tolerate

6

Red Hat Enterprise Linux (RHEL) Server

7

7.1 and future OS fix packs

IBM z Systems

64-Tolerate

7

Red Hat Enterprise Linux (RHEL) Server

7

7.1 and future OS fix packs

x86-64

64-Tolerate

8

Red Hat Enterprise Linux (RHEL)

Advanced Platform 5

5.11 and future OS fix packs

IBM z Systems

64-Tolerate

9

Red Hat Enterprise Linux (RHEL)

Advanced Platform 5

5.11 and future OS fix packs

x86-64

64-Tolerate

10

Red Hat Enterprise Linux (RHEL)

Desktop editions 5

5.11 and future OS fix packs

x86-32

32

Page 43: HCL Connections 5.5 CR3 - support.hcltechsw.com

42 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 OS X El Capitan 10.11 And future OS fix packs x86-64

2 OS X Yosemite 10.10 And future OS fix packs x86-64

Page 44: HCL Connections 5.5 CR3 - support.hcltechsw.com

43 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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

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

OS X El Capitan

10.11

And future OS fix packs

x86-64

64-Tolerate

2

OS X

Yosemite 10.10

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: OS X El Capitan 10.11 and future OS fix packs x86-64

1 Support for OS El Capitan 10.11 is currently limited to the Mac File Sync plugin ONLY.

Page 45: HCL Connections 5.5 CR3 - support.hcltechsw.com

44 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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

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

Page 46: HCL Connections 5.5 CR3 - support.hcltechsw.com

45 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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

Page 47: HCL Connections 5.5 CR3 - support.hcltechsw.com

46 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 8 Standard And future OS versions and fix packs x86-64

8 Windows Server 2008 Datacenter Edition R2 And future OS fix packs x86-64

9 Windows Server 2008 Enterprise Edition R2 And future OS fix packs x86-64

10 Windows Server 2008 Standard Edition R2 And future OS fix packs x86-64

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

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

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

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

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

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

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

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

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

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

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

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

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

Page 48: HCL Connections 5.5 CR3 - support.hcltechsw.com

47 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 8 Standard and future OS versions and fix packs x86-64 8. Windows Enterprise 10 and future OS fix packs x86-32 9. Windows Enterprise 10 and future OS fix packs x86-64

10. Windows Enterprise 8.1 and future OS versions and fix packs x86-32 11. Windows Enterprise 8.1 and future OS versions and fix packs x86-64 12. Windows Pro 10 and future OS fix packs x86-32 13. Windows Pro 10 and future OS versions and fix packs x86-64 14. Windows Professional 8.1 and future OS versions and fix packs x86-32 15. Windows Professional 8.1 and future OS versions and fix packs x86-64

16. Windows Server 2008 Datacenter Edition R2 and future OS fix packs x86-64

17. Windows Server 2008 Enterprise Edition R2 and future OS fix packs x86-64

18. Windows Server 2008 Standard Edition R2 and future OS fix packs

x86-64

19. Windows Server 2012 Datacenter Edition R2 and future OS fix packs x86-64

20. Windows Server 2012 Essentials Edition R2 and future OS fix packs x86-64

21. Windows Server 2012 Standard Edition R2 and future OS fix packs

x86-64

22. Windows Standard 8.1 and future OS versions and fix packs x86-32 23. 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

Page 49: HCL Connections 5.5 CR3 - support.hcltechsw.com

48 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 packs

x86-32

32

2

Windows 7

Enterprise

Service Pack 1 and future OS fix packs

x86-64

64-Tolerate

3

Windows 7

Professional

Service Pack 1 and future OS fix packs

x86-32

32

4

Windows 7

Professional

Service Pack 1 and future OS fix packs

x86-64

64-Tolerate

5

Windows 7

Ultimate

Service Pack 1 and future OS fix packs

x86-32

32

6

Windows 7

Ultimate

Service Pack 1 and future OS fix packs

x86-64

64-Tolerate

7

Windows 8

Standard

And future OS versions and fix packs

x86-64

64-Tolerate

8

Windows Server 2008

Datacenter Edition R2

And future OS fix packs

x86-64

64-Tolerate

9

Windows Server 2008

Enterprise Edition R2

And future OS fix packs

x86-64

64-Tolerate

10

Windows Server 2008

Standard Edition R2

And future OS fix packs

x86-64

64-Tolerate

11

Windows Server 2012

Datacenter Edition R2

And future OS fix packs

x86-64

64-Tolerate

12

Windows Server 2012

Essentials Edition R2

And future OS fix packs

x86-64

64-Tolerate

13

Windows Server 2012

Standard Edition R2

And future OS fix packs

x86-64

64-Tolerate

14

Windows

Enterprise 10

And future OS fix packs

x86-32

32

15

Windows

Enterprise 10

And future OS fix packs

x86-64

64-Tolerate

16

Windows

Enterprise 8.1

And future OS versions and fix packs

x86-32

32

17

Windows

Enterprise 8.1

And future OS versions and fix packs

x86-64

64-Tolerate

18

Windows

Pro 10

And future OS fix packs

x86-32

32

19

Windows

Pro 10

And future OS versions and fix packs

x86-64

64-Tolerate

20

Windows

Professional 8.1

And future OS versions and fix packs

x86-32

32

21

Windows

Professional 8.1

And future OS versions and fix packs

x86-64

64-Tolerate

22

Windows

Standard 8.1

And future OS versions and fix packs

x86-32

32

Page 50: HCL Connections 5.5 CR3 - support.hcltechsw.com

49 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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

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:

1 None provided

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

Page 51: HCL Connections 5.5 CR3 - support.hcltechsw.com

50 of 50

HCL Connections 5.5 CR3: Detailed System Requirements

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 NOTE: Hardware requirements are reviewed only at the release level.