IBM Domino 9.0.1 FP10 Social Edition System Requirements

IBM Domino 9.0.1 FP10 Social Edition MSI name: IBM Domino Release number: 9.0.1 FP10 Social Edition Electronic GA, actual date: 6 Feb 2018

Contents

This document contains the detailed system requirements specified in the Clearinghouse database for the IBM Domino 9.0.1 FP10 Social Edition deliverable. This deliverable is planned to ship with the MSI name IBM Domino with the release level of 9.0.1 FP10 Social Edition. 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 2. Software requirements 3. Operating systems 4. Hardware requirements 1.1 Deployment structure 2.1 Capabilities used by 3.1 Supported operating NOTE: components systems 1.2 Packaging list Hardware requirements 2.2 Capabilities details 3.2 Families details 1.3 Integrated products are reviewed only at the 2.2.1 Databases (Mandatory) 3.2.1 AIX release 2.2.2 Databases (Additional) 3.2.2 IBM i or mod level. 2.2.3 E-mail Application 3.2.3 Linux 2.2.4 Web Browsers 3.2.4 Mobile OS 3.2.5 Windows 3.3 Supported Hypervisors

1. Deliverable overview

1/28 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, IBM 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 Server 1 Notes Traveler Native Install

2 Server - 128 bit Native Install

3 Server - 32 bit Native Install

4 Server - 64 bit Native Install

5 Server Native Install

2 Mobile Device 6 Notes Traveler - on mobile device Native Install

2/28 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

3/28 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

4/28 2.1 Capabilities used by components

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

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

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

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

components, even if those deployable components are optional.

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

software the deliverable integrates with.

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

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

the product fulfilling the capability.

Capabilities

Mandatory Additional 1. Databases 2. Databases

3. E-mail Application

4. Web Browsers

Deployment unit Components 1 2 3 4

1 Server 1 Notes Traveler Y N Y N

2 Server - 128 bit N Y Y Y

3 Server - 32 bit N Y Y Y

4 Server - 64 bit N Y Y Y

5 Server N N Y N

2 Mobile Device 6 Notes Traveler - on mobile device N N Y N

5/28 2.2.1 Databases (Mandatory)

2.2.1.1 Summary of products fulfilling this capability

The software products that can fulfill the Databases (Mandatory) 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 DB2 Enterprise Server Edition 10.1 interact and future fix packs

2 DB2 Enterprise Server Edition 9.7.0.5 interact and future fix packs

3 DB2 Workgroup Server Edition 10.1 interact and future fix packs

4 DB2 Workgroup Server Edition 9.7.0.5 interact and future fix packs

5 Microsoft SQL Server Enterprise Edition 2008 R2 interact and future fix packs

6 Microsoft SQL Server Enterprise Edition 2008 SP1 interact and future fix packs

2.2.1.2 Operating system restrictions for Databases (Mandatory)

When any of the products listed in this table are used to fulfil the Databases (Mandatory) 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 (Mandatory) 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

6/28 2.2.1.3 Component usage restrictions for Databases (Mandatory)

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 Server 1 Notes Traveler No restriction

2 Server - 128 bit 1. DB2 Enterprise Server Edition 10.1 2. DB2 Enterprise Server Edition 9.7.0.5 3. DB2 Workgroup Server Edition 10.1 4. DB2 Workgroup Server Edition 9.7.0.5 5. Microsoft SQL Server Enterprise Edition 2008 R2 6. Microsoft SQL Server Enterprise Edition 2008 SP1

3 Server - 32 bit 1. DB2 Enterprise Server Edition 10.1 2. DB2 Enterprise Server Edition 9.7.0.5 3. DB2 Workgroup Server Edition 10.1 4. DB2 Workgroup Server Edition 9.7.0.5 5. Microsoft SQL Server Enterprise Edition 2008 R2 6. Microsoft SQL Server Enterprise Edition 2008 SP1

4 Server - 64 bit 1. DB2 Enterprise Server Edition 10.1 2. DB2 Enterprise Server Edition 9.7.0.5 3. DB2 Workgroup Server Edition 10.1 4. DB2 Workgroup Server Edition 9.7.0.5 5. Microsoft SQL Server Enterprise Edition 2008 R2 6. Microsoft SQL Server Enterprise Edition 2008 SP1

5 Server

2 Mobile Device 6 Notes Traveler - on mobile device

7/28 2.2.1.4 Notes for Databases (Mandatory)

This table contains a section for any of the software products fulfilling the Databases (Mandatory) 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: DB2 Enterprise Server Edition 10.1 DB2 Enterprise Server Edition 9.7.0.5

1 Only mandatory if Traveler High Availability feature will be used

64-bit version recommended

Footnotes for: DB2 Workgroup Server Edition 9.7.0.5

2 Only mandatory if Traveler High Availability feature will be used

64-bit version recommended

Footnotes for: DB2 Workgroup Server Edition 10.1

3 Only mandatory if Traveler High Availability feature will be used

64-bit version recommended

A limited entitlement to IBM DB2 10.1 Workgroup Server Edition is included with the IBM Notes Traveler 9.0.0 release. This limited entitlement is provided for customers who want to deploy a Notes Traveler High Availability server and elect to use this entitled DB2 version as their RDBMS solution. The DB2 entitlement may be used for no purpose other than the support of IBM Notes Traveler.

8/28 2.2.2 Databases (Additional)

2.2.2.1 Summary of products fulfilling this capability

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

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 ODBC Driver 7.0 interact and future fix packs

2.2.2.2 Operating system restrictions for Databases (Additional)

When any of the products listed in this table are used to fulfil the Databases (Additional) 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 (Additional) 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 IBM ODBC Driver 7.0 Any IBM i, Windows operating systems supported by the deliverable. and future fix packs None of the AIX, Mobile OS operating systems supported by the deliverable.

Specific Linux operating systems (operating systems in grey are not supported) 1. Red Hat Enterprise Linux (RHEL) Server 6 6.3 IBM z Systems 2. Red Hat Enterprise Linux (RHEL) Server 6 6.3 x86-64 3. Red Hat Enterprise Linux (RHEL) Server 7 IBM z Systems 4. Red Hat Enterprise Linux (RHEL) Server 7 x86-64 5. SUSE Linux Enterprise Server (SLES) 11 SP1 IBM z Systems 6. SUSE Linux Enterprise Server (SLES) 11 SP1 x86-64 7. SUSE Linux Enterprise Server (SLES) 12 IBM z Systems 8. SUSE Linux Enterprise Server (SLES) 12 x86-64

9/28 2.2.2.3 Component usage restrictions for Databases (Additional)

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.

Deployment unit Components Products not supported

1 Server 1 Notes Traveler 1. IBM ODBC Driver 7.0

2 Server - 128 bit No restriction

3 Server - 32 bit No restriction

4 Server - 64 bit No restriction

5 Server

2 Mobile Device 6 Notes Traveler - on mobile device

2.2.2.4 Notes for Databases (Additional)

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

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

Footnotes for:

1 None provided

10/28 2.2.3 E-mail Application

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

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 IBM Notes 9.0 interact and future mod levels and their fix packs

2 IBM Notes 9.0.1 Social Edition interact and future fix packs

3 Lotus Notes 8.0 interact and future mod levels and their fix packs

4 Lotus Notes 8.5 interact and future mod levels and their fix packs

2.2.3.2 Operating system restrictions for E-mail Application

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

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

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

1 No restrictions for all 4 products listed in this capability

11/28 2.2.3.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.3.1 that cannot be used with the specified deployment units and/or deployable components.

Deployment unit Components Products not supported

1 Server 1 Notes Traveler No restriction

2 Server - 128 bit No restriction

3 Server - 32 bit No restriction

4 Server - 64 bit No restriction

5 Server No restriction

2 Mobile Device 6 Notes Traveler - on mobile device No restriction

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

12/28 2.2.4 Web Browsers

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

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 Apple Safari 5.0 interact and future fix packs

2 Google Chrome 8 interact and future fix packs

3 Microsoft Internet Explorer 10 interact and future fix packs

4 Microsoft Internet Explorer 11 interact and future fix packs

5 Microsoft Internet Explorer 8.0 interact and future fix packs

6 Microsoft Internet Explorer 9.0 interact and future fix packs

7 Mozilla Firefox 3.6 interact and future fix packs

8 Mozilla Firefox 4.0 interact and future fix packs

13/28 2.2.4.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 Apple Safari 5.0 Any IBM i, Linux, Windows operating systems supported by the deliverable. and future fix packs None of the AIX, Mobile OS operating systems supported by the deliverable.

2 Microsoft Internet Explorer 8.0 Any IBM i, Linux, Windows operating systems supported by the deliverable. and future fix packs None of the AIX, Mobile OS operating systems supported by the deliverable.

3 Microsoft Internet Explorer 9.0 Any IBM i, Linux, Windows operating systems supported by the deliverable. and future fix packs None of the AIX, Mobile OS operating systems supported by the deliverable.

4 Mozilla Firefox 4.0 Any IBM i, Linux, Windows operating systems supported by the deliverable. and future fix packs None of the AIX, Mobile OS operating systems supported by the deliverable.

2.2.4.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.4.1 that cannot be used with the specified deployment units and/or deployable components.

Deployment unit Components Products not supported

1 Server 1 Notes Traveler

2 Server - 128 bit No restriction

3 Server - 32 bit No restriction

4 Server - 64 bit No restriction

5 Server

2 Mobile Device 6 Notes Traveler - on mobile device

2.2.4.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.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: Microsoft Internet Explorer 8.0

1 toleration mode

14/28 Back to top

3. Operating systems

15/28 3.1 Supported operating system families

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

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

Family Operating systems Editions and versions

AIX 1 AIX 7.1

7.2

IBM i 2 IBM i 7.1

7.2

7.3

Linux 3 Red Hat Enterprise Linux (RHEL) Server 6

4 SUSE Linux Enterprise Server (SLES) 11

Mobile OS 5 Android 2.2

3.0

4.0

4.1

4.2

6 Blackberry 10

7 Windows Phone 7.5

8 Windows RT

9 iOS 4

4.1

4.2

4.3

5.1

6.1

Windows 10 Windows Server 2008 Enterprise Edition R2

16/28 3.1 Supported operating system families

11 Windows Server 2012 Datacenter Edition

Datacenter Edition R2

Standard Edition

Standard Edition R2

12 Windows Server 2016 Datacenter Edition

3.2.1 AIX family

3.2.1.1 Supported operating system summary

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

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

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

include operating systems that require additional fixpacks of the deliverable.

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

listed.

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

statement covering all future versions of an operating system.

Name Version Maintenance Hardware

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

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

3.2.1.2 Component restrictions for the AIX family

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

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

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

1 Server 1 Notes Traveler None of the AIX operating systems supported by the deliverable

2 Server - 128 bit None of the AIX operating systems supported by the deliverable

3 Server - 32 bit None of the AIX operating systems supported by the deliverable

4 Server - 64 bit Any AIX operating system supported by the deliverable

5 Server None of the AIX operating systems supported by the deliverable

2 Mobile Device 6 Notes Traveler - on mobile None of the AIX operating systems supported by the deliverable device

17/28 Back to top

3.2.1.3 Application bitness for the AIX family

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

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

Name Version Maintenance Hardware Application bitness

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

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

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 POWER7 mode AIX 7.2 and future OS versions and fix packs POWER System - Big Endian

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

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

3.2.1.5 Notes for the AIX family

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

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

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

1 • 64-bit kernel • APAR IV29604 required for 7.1 TL0

• APAR IV27204 required for 7.1 TL1 • All TL, SP, and non-major releases are supported

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

2 All TL, SP, and non-major releases are supported

18/28 3.2.2 IBM i family

3.2.2.1 Supported operating system summary

The operating systems for the IBM i 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 IBM i 7.1 And future OS fix packs POWER System - Big Endian

2 IBM i 7.2 And future OS fix packs POWER System - Big Endian

3 IBM i 7.3 And future OS fix packs POWER System - Big Endian

3.2.2.2 Component restrictions for the IBM i 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 Server 1 Notes Traveler None of the IBM i operating systems supported by the deliverable

2 Server - 128 bit Any IBM i operating system supported by the deliverable

3 Server - 32 bit None of the IBM i operating systems supported by the deliverable

4 Server - 64 bit None of the IBM i operating systems supported by the deliverable

5 Server None of the IBM i operating systems supported by the deliverable

2 Mobile Device 6 Notes Traveler - on mobile None of the IBM i operating systems supported by the deliverable device

19/28 3.2.2.3 Application bitness for the IBM i 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 IBM i 7.1 And future OS fix packs POWER System - Big Endian 64-Exploit

2 IBM i 7.2 And future OS fix packs POWER System - Big Endian 64-Exploit

3 IBM i 7.3 And future OS fix packs POWER System - Big Endian 64-Exploit

3.2.2.4 Notes for the IBM i family

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: IBM i 7.1 and future OS fix packs POWER System - Big Endian

1 • 128 bit • NSFDB2 not supported • IBM i only runs on 64-bit hardware and has been enabled for 64-bit for a long time. IBM i also provides 128-bit pointer capability. This means that all software that runs on IBM i , including Domino, is 64-bit capable and typically uses 128-bit pointers. • For IBM Traveler

• IBM Developer Kit for Java 5761JV1 (6.1 and 7.1) Base plus

• Option 11: J2SE 6.0 32-bit JVM (SR12 required) • Option 12: J2SE 6.0 64-bit JVM (SR12 required) • IBM Toolbox for Java

• IBM i 7.1 5770SS1 option 3

Footnotes for: IBM i 7.2 and future OS fix packs POWER System - Big Endian

2 • 128 bit • NSFDB2 not supported • For IBM Traveler • IBM Developer Kit for Java 5770JV1 (7.2) Base plus • Option 11: J2SE 6.0 32-bit JVM (Latest SR required) • Option 12: J2SE 6.0 64-bit JVM (Latest SR required)

• IBM Toolbox for Java

• IBM i 7.2 5770SS1 Option 3

20/28 3.2.3 Linux family

3.2.3.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) Server 6 6.3 and future OS fix packs IBM z Systems

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

3 Red Hat Enterprise Linux (RHEL) Server 7 And future OS fix packs IBM z Systems

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

5 SUSE Linux Enterprise Server (SLES) 11 SP1 and future OS fix packs IBM z Systems

6 SUSE Linux Enterprise Server (SLES) 11 SP1 and future OS fix packs x86-64

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

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

3.2.3.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.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 Server 1 Notes Traveler None of the Linux operating systems supported by the deliverable

2 Server - 128 bit None of the Linux operating systems supported by the deliverable

3 Server - 32 bit None of the Linux operating systems supported by the deliverable

4 Server - 64 bit Any Linux operating system supported by the deliverable

5 Server None of the Linux operating systems supported by the deliverable

2 Mobile Device 6 Notes Traveler - on mobile None of the Linux operating systems supported by the deliverable device

21/28 3.2.3.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) Server 6 6.3 and future OS fix packs IBM z Systems 64-Exploit

2 Red Hat Enterprise Linux (RHEL) Server 6 6.3 and future OS fix packs x86-64 64-Exploit

3 Red Hat Enterprise Linux (RHEL) Server 7 And future OS fix packs IBM z Systems 64-Exploit

4 Red Hat Enterprise Linux (RHEL) Server 7 And future OS fix packs x86-64 64-Exploit

5 SUSE Linux Enterprise Server (SLES) 11 SP1 and future OS fix packs IBM z Systems 64-Exploit

6 SUSE Linux Enterprise Server (SLES) 11 SP1 and future OS fix packs x86-64 64-Exploit

7 SUSE Linux Enterprise Server (SLES) 12 And future OS fix packs IBM z Systems 64-Exploit

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

3.2.3.4 Notes for the Linux family

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: SUSE Linux Enterprise Server (SLES) 11 SP1 and future OS fix packs x86-64 Red Hat Enterprise Linux (RHEL) Server 6 6.3 and future OS fix packs x86-64

1 • XGL and SELinux must be disabled

Footnotes for: Red Hat Enterprise Linux (RHEL) Server 6 6.3 and future OS fix packs IBM z Systems SUSE Linux Enterprise Server (SLES) 11 SP1 and future OS fix packs IBM z Systems

2 • XGL and SELinux must be disabled

Footnotes for: SUSE Linux Enterprise Server (SLES) 12 and future OS fix packs IBM z Systems SUSE Linux Enterprise Server (SLES) 12 and future OS fix packs x86-64

3 XGL and SELinux must be disabled

22/28 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 2.2 And future OS versions and fix packs

2 Android 3.0

3 Android 4.0 And future OS versions and fix packs

4 Android 4.1 And future OS versions and fix packs

5 Android 4.2 And future OS versions and fix packs

6 Blackberry 10 And future OS versions and fix packs

7 Windows Phone 7.5 And future OS versions and fix packs

8 Windows Phone 8 And future OS versions and fix packs

9 Windows RT And future OS versions and fix packs

10 iOS 4.1 And future OS versions and fix packs

11 iOS 4.2 And future OS versions and fix packs

12 iOS 4.3 And future OS versions and fix packs

13 iOS 4 And future OS fix packs

14 iOS 5.1 And future OS versions and fix packs

15 iOS 5 And future OS versions and fix packs

16 iOS 6.1 And future OS versions and fix packs

17 iOS 6 And future OS versions and fix packs

23/28 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 Server 1 Notes Traveler None of the Mobile OS operating systems supported by the deliverable

2 Server - 128 bit None of the Mobile OS operating systems supported by the deliverable

3 Server - 32 bit None of the Mobile OS operating systems supported by the deliverable

4 Server - 64 bit None of the Mobile OS operating systems supported by the deliverable

5 Server None of the Mobile OS operating systems supported by the deliverable

2 Mobile Device 6 Notes Traveler - on mobile Any Mobile OS operating system supported by the deliverable device

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 2.2 And future OS versions and fix packs

2 Android 3.0

3 Android 4.0 And future OS versions and fix packs

4 Android 4.1 And future OS versions and fix packs

5 Android 4.2 And future OS versions and fix packs

6 Blackberry 10 And future OS versions and fix packs

7 Windows Phone 7.5 And future OS versions and fix packs

8 Windows Phone 8 And future OS versions and fix packs

9 Windows RT And future OS versions and fix packs

10 iOS 4.1 And future OS versions and fix packs

11 iOS 4.2 And future OS versions and fix packs

12 iOS 4.3 And future OS versions and fix packs

13 iOS 4 And future OS fix packs

14 iOS 5.1 And future OS versions and fix packs

15 iOS 5 And future OS versions and fix packs

16 iOS 6.1 And future OS versions and fix packs

17 iOS 6 And future OS versions and fix packs

24/28 Back to top

3.2.4.4 Notes for the Mobile OS family

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

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 Server 2008 Enterprise Edition R2 And future OS fix packs x86-64

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

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

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

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

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

7 Windows Server 2016 Datacenter Edition And future OS versions and fix packs x86-64

8 Windows Server 2016 Standard Edition And future OS versions and fix packs x86-64

25/28 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 Server 1 Notes Traveler None of the Windows operating systems supported by the deliverable

2 Server - 128 bit None of the Windows operating systems supported by the deliverable

3 Server - 32 bit Any Windows operating system supported by the deliverable

4 Server - 64 bit Any Windows operating system supported by the deliverable

5 Server None of the Windows operating systems supported by the deliverable

2 Mobile Device 6 Notes Traveler - on mobile None of the Windows operating systems supported by the deliverable device

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 Server 2008 Enterprise Edition R2 And future OS fix packs x86-64 32

64-Exploit

64-Tolerate

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

64-Exploit

64-Tolerate

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

4 Windows Server 2012 Datacenter Edition And future OS fix packs x86-64 64-Exploit

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

6 Windows Server 2012 Standard Edition And future OS fix packs x86-64 64-Exploit

7 Windows Server 2016 Datacenter Edition And future OS versions and fix packs x86-64 64-Exploit

8 Windows Server 2016 Standard Edition And future OS versions and fix packs x86-64 64-Exploit

26/28 3.2.5.4 Notes for the Windows family

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

Footnotes for: Windows Server 2008 Standard Edition R2 and future OS fix packs x86-64 Windows Server 2008 Enterprise Edition R2 and future OS fix packs x86-64

1 • Server Core not supported

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

2 • Server Core not supported

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

27/28 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 Server 1 Notes Traveler No restriction

2 Server - 128 bit No restriction

3 Server - 32 bit No restriction

4 Server - 64 bit No restriction

5 Server No restriction

2 Mobile Device 6 Notes Traveler - on mobile device 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.

28/28