docker/domino
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Initial release

Browse Source
This commit is contained in:
Deon George 2017-07-23 22:55:17 +10:00
commit ceeb4ce388
6 changed files with 1217 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
.gitlab-ci.yml Normal file
View File

@ -0,0 +1,45 @@
image: docker:latest
stages:
- test
- build
variables:
VERSION: latest
AUTO_VERSION: ${CI_COMMIT_TAG:-latest}
CACHETAG: build
DOCKER_REGISTRY: registry.leenooks.net
DOCKER_HOST: tcp://${DOCKER_REGISTRY}-leenooks-ci-docker:2375
services:
- ${DOCKER_REGISTRY}/leenooks/ci-docker:dind
before_script:
- docker info
- docker version
- docker login -u gitlab-ci-token -p $CI_BUILD_TOKEN ${DOCKER_REGISTRY}
- echo "CI_PROJECT_PATH ${CI_PROJECT_PATH} CI_COMMIT_TAG ${CI_COMMIT_TAG} CI_COMMIT_REF_NAME ${CI_COMMIT_REF_NAME}"
- echo "CI_REGISTRY ${CI_REGISTRY} CI_REGISTRY_IMAGE ${CI_REGISTRY_IMAGE} CI ${CI}"
- echo "AUTO_VERSION ${AUTO_VERSION}"
test:
stage: test
script:
- cat /etc/hosts
- env|sort
- docker build -t ${CI_REGISTRY_IMAGE}:${VERSION} .
- docker images
only:
- debug
build:
stage: build
script:
- docker pull ${CI_REGISTRY_IMAGE}:${CACHETAG} || true
- docker build --cache-from ${CI_REGISTRY_IMAGE}:${CACHETAG} -t ${CI_REGISTRY_IMAGE}:${VERSION} -t ${CI_REGISTRY_IMAGE}:${CACHETAG} .
- docker push ${CI_REGISTRY_IMAGE}:${VERSION}
- docker push ${CI_REGISTRY_IMAGE}:${CACHETAG}
tags:
- docker
only:
- master

25
Dockerfile Normal file
View File

@ -0,0 +1,25 @@
# NAME leenooks/domino
# VERSION 9.0.1.8-9.0.1.18
FROM registry.leenooks.net/leenooks/base:7
RUN yum -y install which perl glibc.i686 libgcc.i686 && yum clean all
RUN groupadd -g 201 servers && useradd -u 202 -g 201 notes
# Base Version of Domino & FP
COPY response.dat response-fp.dat /tmp/
RUN mkdir /tmp/domino && \
cd /tmp/domino && curl -SL http://yum.leenooks.net/docker/domino/9.0.1 | tar xf - && cd /tmp/domino/linux64/domino && ./install -silent -options /tmp/response.dat && \
cd /tmp/domino && curl -SL http://yum.leenooks.net/docker/domino/9.0.1.8 | tar xf - && cd /tmp/domino/linux64/domino && NUI_NOTESDIR=/opt/ibm/domino ./install -script /tmp/response-fp.dat && rm -rf /tmp/*
# TRAVELLER
COPY response-tvl.dat /tmp/
RUN mkdir /tmp/domino && cd /tmp/domino && \
curl -SL http://yum.leenooks.net/docker/traveler/9.0.1.18 | tar xzf - && ./TravelerSetup -f /tmp/response-tvl.dat -i SILENT -l en && rm -rf /tmp/*
# curl -SL http://yum.leenooks.net/docker/traveler/9.0.1.8 | tar xzf - && ./TravelerSetup -f /tmp/response-tvl.dat -i SILENT -l en && \
COPY domino.sh /usr/local/sbin/
EXPOSE 25 80 110 143 443 465 993 995 1352
# Starting
ENTRYPOINT [ "/usr/local/sbin/domino.sh" ]

56
domino.sh Executable file
View File

@ -0,0 +1,56 @@
#!/bin/sh
function start {
su ${DOMINO_USR} -c "$DOMINO_BIN -jc -c"
}
function stop {
su ${DOMINO_USR} -c "echo Y| $DOMINO_BIN -jc -q"
}
# set the domino path and user name under which domino will run
DOMINO_BIN=/opt/ibm/domino/bin/server
test -x $DOMINO_BIN || exit 5
DOMINO_USR=notes
cd /notesdata
[ -f .init ] && . ./.init
case "$1" in
setup)
if [ ! -d /data ]; then
echo "Please start with -v <SRC>:/data, so that your domino data can be initiated" && exit 1
fi
echo "Domino setup is listening on 1352"
su ${DOMINO_USR} -c "${DOMINO_BIN} -listen 1352"
cp -pR /notesdata/* /data/
echo "Please start domino with -v <SRC>:/notesdata"
;;
start)
trap 'stop' SIGTERM
MAX_OPEN_FILES=`ulimit -n`
if [ $MAX_OPEN_FILES -lt 60000 ]; then
echo "setting maximum open files to 60000"
ulimit -n 60000
fi
echo -n "Starting Domino server"
start &
wait
;;
stop)
echo -n "Shutting down Domino server"
stop
;;
*)
echo "Usage: $0 {setup|start|stop}"
exit 1
;;
esac

74
response-fp.dat Executable file
View File

@ -0,0 +1,74 @@
# Lotus Domino Server for UNIX
# Incremental Installer Script Template
# The Lotus Domino Incremental Installer is used to update an existing
# installation to a new revision. All installation settings are
# automatically set to be those of the last installation.
# There are two ways to use the Lotus Domino Incremental Installer:
# 1) Interactive Mode - the Domino installation on the local host
# is updated.
# 2) Script Mode - you may specify one or more hosts on which
# the Domino installation is to be updated.
#
# Interactive Mode
# To use, invoke the install program without any arguments,
# such as "./install". The Install Program will display the
# installation settings, and prompt you to proceed with
# the update. For Interactive Mode, you do not need this template file.
#
# Script Mode
# To use, copy this file, edit it, and invoke the install program
# such as "./install -script /tmp/script.dat". There are only
# two changes you can make to this file ("target_hosts" and "installation_type"), below.
#
# "target_hosts"
#
# If not set (by default it is commented-out),
# the Domino Server will be updated only to the computer on which
# the Incremental Installer is being run (the "local host").
#
# If set, specifies one or more target hosts on which the Domino Server
# will be updated. The local host will be installed to only if it is
# one of the hosts specified in the target_hosts list.
#
# The double-quoted, comma-separated list may be specified on
# a single line, or using multiple lines.
# For example:
# target_hosts = (
# "host1",
# "host2",
# "host3"
# )
#
# To use this setting, be sure to remove the '#' comment character
# on the "target_hosts=" line.
#
# !!!
#target_hosts=("host1","host2")
######################################################################
#
# begin "Default Settings" sections
#
#
# "installation_type"
#
# Specifies the set of product options that are to be installed.
# Specify the desired type by its number.
#
# Domino Mail Server : 0
# Domino Application Server : 1
# Domino Enterprise Server : 2
#
# !!!
#installation_type = 0
######################################################################
installation_type = 0

256
response-tvl.dat Executable file
View File

@ -0,0 +1,256 @@
#########################################################################
#
# Licensed Materials - Property of IBM
# (C) Copyright IBM Corp. 2007, 2015
#
# Do not make modifications to this file unless instructed to do so.
#
#########################################################################
#
# Response file for silent install.
#
# Usage:
#
# To perform silent install modify this file then run:
# TravelerSetup -f installer.properties -i silent -l <locale>
#
# Where <locale> is:
#
# en - English (default)
# ca - Catalan
# cs - Czech
# da - Danish
# de - German
# dl - Dutch
# el - Greek
# es - Spanish
# fi - Finnish
# fr - French
# hu - Hungarian
# it - Italian
# ja - Japanese
# ko - Korean
# pl - Polish
# pt - Portuguese
# pt_BR - Brazilian Portuguese
# ru - Russian
# sk - Slovakian
# sl - Slovenian
# sv - Swedish
# th - Thai
# tr - Turkish
# zh_CN - Simplified Chinese
# zh_TW - Traditional Chinese
#
#
# EX: TravelerSetup -f /tmp/installer.properties -i silent -l en
#
#
# Important Notes about Silent Install:
#
# 1. If silent install is performed, the uninstall will also
# be silent, I.E. it is not possible to perform a UI uninstall
# after performing a silent install.
#
# 2. If any fatal errors are encountered they will be logged to
# InstallError.log in the current working directory. If their
# are no fatal errors, the install log file will be found at:
# <DOMINO_DATA_DIRECTORY_1>/traveler/logs
#
#
#
# IMPORTANT - Run installer as root if Linux OS.
#
# License Acceptance
# ------------------
#
# ACCEPT_LICENSE= true | false
#
# true - You accept the terms of the license agreement
# false - You do not accept terms of the license agreement,
# the product will not be installed.
#
#
ACCEPT_LICENSE=true
# Domino Install Directories
# --------------------------
#
# DOMINO_PROGRAM_DIRECTORY - Domino Programs directory
# DOMINO_DATA_DIRECTORY_1 - Domino Data directory.
# DOMINO_NOTESINI_DIRECTORY_1 - Location of notes.ini file (if not in default location)
#
# If installing multiple partitions - increment data directory and notes.ini directories as needed
# DOMINO_DATA_DIRECTORY_2
# DOMINO_NOTESINI_DIRECTORY_2
# etc...
#
# NOTE: Directories must be in sequential order starting with 1,2,3... This is not the same
# as partition number. Partition number will be discovered by the application and does
# not need to be represented here.
#
DOMINO_PROGRAM_DIRECTORY=/opt/ibm/domino/notes/latest/linux
DOMINO_DATA_DIRECTORY_1=/notesdata
DOMINO_NOTESINI_DIRECTORY_1=/notesdata
#
# LINUX_USER_NAME
#
# A non root user is required to run Domino Scripts during installation.
# This should be the same user that Domino Server runs as.
# This parameter is optional. If not specified or commented out,
# the user name will be auto detected.
#
# Linux OS only
#
# LINUX_USER_NAME=notes
LINUX_USER_NAME=notes
# NOTE: If installing to multiple partitions and have different user names for each partition
# use _# format matching the partition directories above. This is required if
# installing partitions with different user/group names. Auto detect will only
# detect the user/group for the first partition then will use that value for all
# remaining partitions.
#
# Example:
#
# LINUX_USER_NAME_1=usera
# LINUX_USER_NAME_2=userb
# etc...
#
# LINUX_GROUP_NAME
#
# Group name the LINUX_USER_NAME belongs to.
# This parameter is optional. If not specified or commented out,
# the group name will be auto detected.
#
# Linux OS only
#
# LINUX_GROUP_NAME=notes
LINUX_GROUP_NAME=servers
# NOTE: If installing to multiple partitions and have different group names for each partition
# use _# format matching the partition directories above. This is required if
# installing partitions with different user/group names. Auto detect will only
# detect the user/group for the first partition then will use that value for all
# remaining partitions.
#
# Example:
#
# LINUX_GROUP_NAME_1=groupa
# LINUX_GROUP_NAME_2=groupb
# etc...
#
# NTS_WEBSITE_HOME= 0 | 1
# 0 - NTS will not set the user homepage as default site for server.
# 1 - NTS will set the user homepage as default site for server.
#
NTS_WEBSITE_HOME=0
# Override Backrev Warning
# ------------------
#
# OVERRIDE_BACKREV= true | false
#
# true - Install will continue if newer version of IBM Traveler detected.
# false - Install will not continue if newer version of IBM Traveler detected.
#
OVERRIDE_BACKREV=false
#
# External Server URL
# -------------------
#
# The External Server URL is the fully qualified URL that the Notes
# Traveler clients use to connect to the IBM Traveler server.
# This URL is either the address of this server or a proxy server. If this
# URL is currently unknown, it should be configured on the IBM
# Traveler tab of the Domino server document later.
#
# For example:
# https://my.travelerserver.com/traveler
# https://my.travelerproxy.com:4443/traveler
#
# It is recommended that clients always communicate with the IBM Traveler
# Server over a secure connection. Consider specifying SSL communications by using a
# URL that begins with https://. Note that SSL must be setup and configured on the target
# server before clients will be able to communicate with the IBM Traveler server.
# NTS_SET_EXTERNAL_URL=https://my.travelerserver.com/traveler
#
# Multi Instance Install
# -------------------
#
# Set to true if installing multiple instances on the same OS. This is only supported
# on Linux and if the Domino server has already been installed in multi instance mode.
#
# IMPORTANT: This is not the same as Partitioned Domino support. Use data directory numbering
# for partitioned servers as shown above. This parameter is for multiple separate
# instances of Domino and Traveler on the same OS.
#
# The default is false.
# MULTI_INSTANCE_INSTALL=true
#
# Install Instance
#
# If using Multi-Instance install on Linux, use this to set the instance
# number when upgrading servers. It is not needed for installing new servers.
# This parameter must match NTS_INSTALL_INSTANCE from the notes.ini
# file of the server being upgraded.
#
# Default is 1 which is correct if single instance install
# NTS_INSTALL_INSTANCE=1
#
#
# INSTALLED_DOMINO_VERSION
# ------------------------
#
# Set this value to indicate the version of the Domino Server that is currently installed.
# This should only be needed if the Traveler installer is not correctly identifying the installed
# Domino version.
#
# Current supported versions: 8.5.3 | 9.0.0 | 9.0.1
#
# Default value is always the latest supported Domino version.
INSTALLED_DOMINO_VERSION=9.0.1
#
#
# BYPASS_DOMINO_VERSION_CHECK
# ---------------------------
#
# Set to true to bypass the Domino Version lookup. This may be useful if any issues encountered when
# determining the Domino version, such as application hang or crash.
#
# IMPORTANT: If setting this flag, also set INSTALLED_DOMINO_VERSION parameter above unless the default
# Domino version is the correct value.
#
# Accepted values are true | false
BYPASS_DOMINO_VERSION_CHECK=true

761
response.dat Executable file
View File

@ -0,0 +1,761 @@
################################################################################
#
# InstallShield Options File
#
# Wizard name: Install
# Wizard source: setup.jar
# Created on: Wed Jul 13 15:00:03 EDT 2005
# Created by: InstallShield Options File Generator
#
# This file can be used to configure Install with the options specified below
# when the wizard is run with the "-options" command line option. Read each
# setting's documentation for information on how to change its value.
#
# A common use of an options file is to run the wizard in silent mode. This lets
# the options file author specify wizard settings without having to run the
# wizard in graphical or console mode. To use this options file for silent mode
# execution, use the following command line arguments when running the wizard:
#
# for normal installations:
# -options "sample_response.txt" -silent
#
# for express installations:
# -express -options "sample_response.txt" -silent
#
# If this installation appears to have failed (ex. prompt has been returned too quick)
# search the end of the DominoInstall.log for clues as to why the script installation failed.
# The DominoInstall.log may be found either in the /opt/ibm/domino/notes/latest/<platform> or /tmp folders.
#
################################################################################
################################################################################
#
# Has the license been accepted
#
# The license must be accepted before installation so this value must be true
# for the install to be successful.
#
-G licenseAccepted=true
##############################################################################
#
# Install Data Directories only
#
# Setting the option below allows you to install additional or upgrade existing Server Partitions.
# The existing Program directory must be specified in this file in order for new Server Partitions
# to be created, but it will not be upgraded.
# Existing Data directories do not need to be listed.
# Only those Data directories specified in this file will be upgraded or added.
# If you wish to add more than one Partition to your existing Domino server,
# set an option to install a Partitioned server later in this file to true:
# -W programFiles.isPartitioned = true
# Otherwise you will only be able to upgrade or install one Data directory.
#
# Warning:
# If you do not have an existing Domino Server on your system,
# please do not check the box below for the option to add data directories only.
###
-W InstallDataOnlyOptionPanel.InstallDataOnly=false
################################################################################
#
# IBM Domino Program Files Install Location
#
# The install location of the program files. Specify a valid directory into which the
# program files should be installed. Directory must not contain spaces.
# For example, to install the product to /opt/ibm/domino, use
#
# -P installLocation="/opt/ibm/domino"
#
#
###
-P installLocation="/opt/ibm/domino"
################################################################################
#
# IBM Domino Data Install Location
#
# The install location of the data files. Specify a valid directory into which
# the data files should be installed. This property is ignored for partitioned
# installs. For example, to install the non-partitioned data files to /local/notesdata, use
#
# -W normalData.installLocationData="/local/notesdata"
#
###
-W normalData.installLocationData="/notesdata"
################################################################################
#
# User Input Field - UserName
#
#
###
-W NameUserGroupPanel.UserName="notes"
################################################################################
#
# User Input Field - GroupName
#
#
###
-W NameUserGroupPanel.GroupName="servers"
################################################################################
#
# IBM Domino Is Partitioned Install
#
# Determines if the install is to use partitioned directories or not. Specify a
# true if this is a paritioned server install, otherwise false. For example, to
# install partitioned servers, use
#
# -W programFiles.isPartitioned=true
#
### -W programFiles.isPartitioned=<value>
################################################################################
#
# IBM Domino Number of Partitions
#
# The number of partition directories to be installed. Specify a number between
# 1 and 15. This property is used to determine how many of the
# partitionData.installLocationDataX= lines are used below. For example, to
# install 3 partitions, use
#
# -W unixPartitionDestinationPanel.numPartitions=3
#
### -W unixPartitionDestinationPanel.numPartitions=<value>
################################################################################
#
# IBM Domino Install Partitions Locations
#
# The install location of the data files for each partition. Specify a valid
# directory into which the data files should be installed. This property is
# ignored for non-partitioned installs. It is suggested that you use the name of
# your server as the name of the directory. For example, to install the
# partitioned data files for MyServer , use
#
# -W unixPartitionDestinationPanel.installLocationData0="/local/notesdata0"
#
# To install multiple partitions use a seperate directory line for each
# partition, for example to install 3 partitions, use
#
# -W unixPartitionDestinationPanel.installLocationData0="/local/notesdata0"
#
# -W unixPartitionDestinationPanel.installLocationData1="/local/notesdata1"
#
# -W unixPartitionDestinationPanel.installLocationData2="/local/notesdata2"
#
###-W unixPartitionDestinationPanel.installLocationData0="/local/notesdata0"
##############################################################################
#
################################################################################
#
# IBM Domino Partitions Users
#
# The data directory users for each partition. Specify a valid
# user who will have the permissions to modify data files in each installed partition.
#This property is ignored for non-partitioned installs.
#For example, to install the
# partitioned data files for user "notes" , use
#
# -W unixPartitionDestinationPanel.installLocationUser0="notes"
#
# Use a separate directory line for each
# partition user, for example for 3 partitions, use
#
# -W unixPartitionDestinationPanel.installLocationUser0="user0"
#
# -W unixPartitionDestinationPanel.installLocationUser1="user1"
#
# -W unixPartitionDestinationPanel.installLocationUser2="user2"
#
### -W unixPartitionDestinationPanel.installLocationUser0="<value>"
##############################################################################
################################################################################
#
# IBM Domino Partitions Groups
#
# Groups for each user of data partition. Specify a valid
# group for corresponding user of each installed partition.
#This property is ignored for non-partitioned installs.
#For example, to specify the group "notesgroup" for user "notes" (see above entry)
#
# -W unixPartitionDestinationPanel.installLocationGroup0="notesgroup"
#
# Use a separate directory line for each
# partition user, for example for 3 partitions, use
#
# -W unixPartitionDestinationPanel.installLocationGroup0="Group0"
#
# -W unixPartitionDestinationPanel.installLocationGroup1="Group1"
#
# -W unixPartitionDestinationPanel.installLocationGroup2="Group2"
#
### -W unixPartitionDestinationPanel.installLocationGroup0="<value>"
##############################################################################
################################################################################
#
# Setup Type
#
# The setup type to be used when installing the product. Legal values are:
#
# UtilityServer - Domino Utility Server: Installs a Domino server that
# provides application services only. Note that it does
# not include support for messaging services. See full
# licensing text for details.
# MessagingServer - Messaging Server: Installs a Domino server that
# provides messaging services. Note that it does not
# include support for application services or Domino
# clusters.
# EnterpriseServer - Enterprise Server: Installs a Domino server that
# provides both messaging and application services.
# CustomServer - Customize: Allows you to select the features you want
# to install.
#
# For example, to specify that the "Domino Utility Server" setup type is
# selected, use
#
# -W SetupTypePanel.selectedSetupTypeId=UtilityServer
#
# You may also set the setup type to nothing by using
#
# -W SetupTypePanel.selectedSetupTypeId=
#
# This clears the current setup type and prevents any changes to the set of
# selected features. Use this option whenever you set feature active states in
# this options file. If you do not clear the selected setup type, the setup type
# panel will override any changes you make to feature active states using this
# file.
#
###
-W SetupTypePanel.selectedSetupTypeId=MessagingServer
################################################################################
#
# Express Installation Setup Type
#
# The setup type to be used when installing the product in Express mode (ex. ./install -express). Legal values are:
#
# UtilityServer - Domino Utility Server Express: Installs a Domino
# server that provides application services only. Note
# that it does not include support for messaging
# services. See full licensing text for details.
# MessagingServer - Domino Messaging Server Express: Installs a Domino
# server that provides messaging services. Note that
# it does not include support for application services
# or Domino clusters.
# CollaborationServer - Domino Collaboration Server Express: Installs a
# Domino server that provides both messaging and
# application services.
#
# For example, to specify that the "Domino Utility Server Express" setup type is
# selected, use
#
# -W ExpressSetupTypePanel.selectedSetupTypeId=UtilityServer
#
# You may also set the setup type to nothing by using
#
# -W ExpressSetupTypePanel.selectedSetupTypeId=
#
# This clears the current setup type and prevents any changes to the set of
# selected features. Use this option whenever you set feature active states in
# this options file. If you do not clear the selected setup type, the setup type
# panel will override any changes you make to feature active states using this
# file.
#
### -W ExpressSetupTypePanel.selectedSetupTypeId=<value>
################################################################################
#
# User Input Field - InstallxSPServer
#
#
# The option to setup an xSP server refers to the configuration of an
# Application Service Provider server. This type of server can only be
# configured after an Enterprise Server installation.
# A value of true below will cause the Domino Setup program
# to configure the server appropriately for xSP functionality.
# This will add security features not present in a normal configuration,
# so do not set the vaule to true unless an xSP configuration is
# specifically required for this server.
### -W InstallOptionPanel.InstallxSPServer=false
################################################################################
#
# User Input Field - CreateOptIbmDomino
#
#
# The Domino Server software no longer requires the /opt/lotus or
# /opt/ibm/lotus or /opt/ibm/domino soft link for handling
# multi- Domino Server installations on a single operating system.
# You can now select your own option for the /opt/ibm/domino soft link feature
# if you have chosen a directory other than /opt/ibm/domino for installation.
# (The default install program path to /opt/ibm/domino since Domino 9)
#
# true - indicates creating "/opt/ibm/domino" soft link
# false - indicates not creating "/opt/ibm/domino" soft link
### -W InstallOptionPanel.CreateOptIbmDomino=true
################################################################################
#
# User Input Field - StartServerSetupType
#
#
# This option is for single local domino server only.
# Do not use this option for partitioned server or remote server installation.
# For Express Mode Installations this option is required to be set to either the Local or Remote value.
#
# For new server installations, this option allows server setup to be launched
# automatically after the installation is complete.
#
# For server upgrades, this option allows the server to restart automatically
# after the installation is complete.
#
# The default value of Manual , which does not launch
# server setup or restart the server after installation.
#
# Manual - indicated manual server setup (not valid for Express mode)
# Local - indicated launches local server setup or restarts server
# Remote - indicates launches server setup in listen mode for remote server setup
-W ServerSetupPanel.ServerSetupType="Manual"
################################################################################
################################################################################
# The below Feature options are used when selecting CustomServer for the Setup Type.
# Indicate feature by feature which install options you select to/not install.
#
################################################################################
#
# "License" Feature
#
# The selection state of the "License" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "License" for installation, use
#
#-P LicenseFeature.active=true
#
-P LicenseFeature.active=true
################################################################################
#
# "Program Files" Feature
#
# The selection state of the "Program Files" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Program Files" for installation, use
#
#-P ProgramFilesFeature.active=true
#
-P ProgramFilesFeature.active=true
################################################################################
#
# "Billing Support" Feature
#
# The selection state of the "Billing Support" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Billing Support" for installation, use
#
#-P BillingSupportFeature.active=true
#
-P BillingSupportFeature.active=true
################################################################################
#
# "Clustering Support" Feature
#
# The selection state of the "Clustering Support" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Clustering Support" for installation, use
# -P ClusteringSupportFeature.active=true
#
-P ClusteringSupportFeature.active=false
################################################################################
#
# "Java Support" Feature
#
# The selection state of the "Java Support" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Java Support" for installation, use
#
#-P bean2236.active=true
#
-P bean2236.active=true
################################################################################
#
# "Data Files" Feature
#
# The selection state of the "Data Files" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Data Files" for installation, use
#
# -P DataFilesFeature.active=true
#
-P DataFilesFeature.active=true
################################################################################
#
# "Required Templates" Feature
#
# The selection state of the "Required Templates" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Required Templates" for installation, use
#
# -P beanRequiredTemplates.active=true
#
-P beanRequiredTemplates.active=true
################################################################################
#
# "Administration Templates" Feature
#
# The selection state of the "Administration Templates" feature. Legal values
# are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Administration Templates" for installation, use
#
# -P beanAdministrationTemplates.active=true
#
-P beanAdministrationTemplates.active=true
################################################################################
#
# "Optional Templates" Feature
#
# The selection state of the "Optional Templates" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Optional Templates" for installation, use
#
# -P beanOptionalTemplates.active=true
#
-P beanOptionalTemplates.active=true
################################################################################
#
# "Certificate Management" Feature
#
# The selection state of the "Certificate Management" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Certificate Management" for installation, use
#
#-P beanCertificateManagement.active=true
#
-P beanCertificateManagement.active=true
################################################################################
#
# "Web Services Data Files" Feature
#
# The selection state of the "Web Services Data Files" feature. Legal values
# are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Web Services Data Files" for installation, use
#
#-P beanWebServicesDataFiles.active=true
#
-P beanWebServicesDataFiles.active=true
################################################################################
#
# "Readme - File" Feature
#
# The selection state of the "Readme File" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Readme File" for installation, use
#
# -P beanReadme.active=true
#
-P beanReadme.active=<value>
################################################################################
#
# "Dojo 1.4.3" Feature
#
# The selection state of the "Dojo 1.4.3" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Dojo 1.4.3" for installation, use
#
# -P beanDojo.active=true
#
-P beanDojo.active=true
################################################################################
#
# "Dojo 1.3.3" Feature
#
# The selection state of the "Dojo 1.3.3" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Dojo 1.3.3" for installation, use
#
# -P beanDojo2.active=true
#
-P beanDojo2.active=true
################################################################################
#
# xPages Feature
#
# The selection state of the Dojo feature.
# Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select xPages for installation,
# use
#
# -P beanXSPages.active=true
#
-P beanXSPages.active=true
################################################################################
#
# "Domino Enterprise Connection Services" Feature
#
# The selection state of the "Domino Enterprise Connection Services" feature.
# Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Domino Enterprise Connection Services" for
# installation, use
#
# -P DECSFeature.active=true
#
-P DECSFeature.active=true
################################################################################
#
# "Domino Offline Services" Feature
#
# The selection state of the "Domino Offline Services" feature. Legal values
# are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Domino Offline Services" for installation, use
#
# -P DOLSFeature.active=true
#
-P DOLSFeature.active=true
################################################################################
#
# "iNotes" Feature
#
# The selection state of the "iNotes" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "iNotes" for installation, use
#
# -P DWAFeature.active=true
#
-P DWAFeature.active=true
################################################################################
#
# "Resource Modeling Engine" Feature
#
# The selection state of the "Resource Modeling Engine" feature. Legal values
# are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Resource Modeling Engine" for installation, use
#
# -P RMEFeature.active=true
#
-P RMEFeature.active=true
################################################################################
#
# "Help" Feature
#
# The selection state of the "Help" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "Help" for installation, use
#
# -P HelpFeature.active=true
#
-P HelpFeature.active=true
################################################################################
#
# "OS Integration" Feature
#
# The selection state of the "OS Integration" feature. Legal values are:
#
# true - Indicates that the feature is selected for installation
# false - Indicates that the feature is not selected for installation
#
# For example, to select "OS Integration" for installation, use
#
# -P OSIntegFeature.active=true
#
-P OSIntegFeature.active=true