IBM Domino 9.0.1 FP10 Social Edition System Requirements
Total Page:16
File Type:pdf, Size:1020Kb
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 Back to top 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 Back to top 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. Back to top 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