Silent installation and configuration for Content Manager Enterprise Edition
In a silent installation and configuration, you use response files to specify the parameters instead of typing them in the graphical user interface. A response file is a text file that has one line for each input field that you would find in the regular installation.
Overview
- you are installing the same components on a large number of computers
- you want to clone a system.
- If the IBMCMREPO environment variable is set, the response file does not set USER_INSTALL_DIR. If you need to specify the installation directory, you can add USER_INSTALL_DIR to the response file after it is generated.
- If the IBMCMREPO environment variable is not set, the response file sets USER_INSTALL_DIR.
When running a silent installation with a response file:
- If the IBMCMREPO environment variable is set, the silent installation installs Content Manager Enterprise Edition in the IBMCMREPO directory, even if USER_INSTALL_DIR is set in the response file.
- If the IBMCMREPO environment variable is not
set:
- If USER_INSTALL_DIR is set in the response file, the silent installation installs Content Manager Enterprise Edition in USER_INSTALL_DIR.
- If USER_INSTALL_DIR is not set in the
response file, the silent installation installs
Content Manager Enterprise Edition in the
default directory:
- Windows: $ProgramsDir\IBM\cmrepository
- UNIX: $opt/IBM/cmrepository
Generating response files for the installation and configuration
To record the information that you enter in the installation program
install -r [path/]install.rspIf you are installing a fix pack, use installUpdate
instead of install.
Replace path/install.rsp with the full path and name of the file in which you want to record the information. The default path is the local directory.
This command installs only the repository files into IBMCMREPO; the product files are installed into IBMCMROOT when you perform the configuration step.
To record the information that you enter in the configuration manager
To generate a response file, use one of the following methods:
- On the Summary panel, click Save response
file.
You can do this even if the installation or configuration is incomplete.
You can do this only on the system that you are configuring.
- Run the configuration response file generation tool in either
interactive mode or command line
mode.
You can do this on any system: for example, if you have a Linux server, you can copy the IDR file to a Windows system; generate the response file there; copy the response file back to the Linux server, and then use it to run a silent configuration.
Running the configuration response file generation tool in interactive mode
- Windows
- Run the following
command:
IBMCMREPO\8.7.<version>\bin\generateRsp.bat - AIX and Linux
- Run the following
command:
IBMCMREPO/8.7.<version>/bin/generateRsp.sh
You can use the following action types:
- FIXPACK_ADD
- Creates a response file to add a fix pack.
- FIXPACK_REMOVE
- Creates a response file to remove a fix pack.
- FRESH_ADD_MODIFY
- Creates a response file to configure IBM Content Manager for the first time.
- FRESH_REMOVE_CONFIG
- Creates a response file to remove the IBM Content Manager configuration.
- RECONFIG_ADD_MODIFY
- Creates a response file to reconfigure IBM Content Manager to add components.
Running the configuration response file generation tool in command line mode
In command line mode, the configuration response file generation tool creates two commands: one with the minimum parameters that are required, and one with all the parameters. You can edit either command as required, and then run it to generate the response file.
The configuration response file generation tool uses the information that is in the install data repository (IDR) file, except for the user IDs and passwords; for example, the user ID and password for WebSphere® Application Server when WebSphere Application Server security is enabled. WebSphere Application Server security is enabled by default.
The command line supports only FIXPACK_ADD and FIXPACK_REMOVE.
- Windows
- Run the following
command:
IBMCMREPO\8.7.<version>\bin\generateRsp.bat -idrFile <idrFilePath> -actionType [FIXPACK_ADD|FIXPACK_REMOVE] ? - AIX and Linux
- Run the following
command:
IBMCMREPO/8.7.<version>/bin/generateRsp.sh -idrFile <idrFilePath> -actionType [FIXPACK_ADD|FIXPACK_REMOVE] ?
where:
- <idrFilePath>
- The path and name of the install data repository (IDR)
file.
- Windows
- The default IDR file is: C:\ProgramData\IBM\ecm\ECMInstallDataV8.xml
- AIX and Linux
- The default IDR file is: /var/ibm/ecm/ECMInstallDataV8.xml
For example, the following command generates two commands:
IBMCMREPO/8.7.<version>/bin/generateRsp.sh -idrFile /var/ibm/ecm/ECMInstallDataV8.xml -actionType FIXPACK_ADD ?
The minimum parameters command looks like this:
generateRsp.sh -rspFile <response_file_full_path> -actionType FIXPACK_ADD -lsdbAdminUser icmadmin -lsdbAdminPwd <password> -rmdbAdminUser rmadmin -rmdbAdminPwd <password> -rmasWasSecurityEnabled Y -rmasWasAdminID wasadmin -rmasWasAdminPwd <password> -websvcWasSecurityEnabled Y -websvcWasAdminID wasadmin -websvcWasAdminPwd <password>
The full parameters command looks like this:
generateRsp.sh -rspFile <ResponseFileFullPath> -idrFile "/var/ibm/ecm/ECMInstallDataV8.xml" -actionType FIXPACK_ADD -dbHome "/opt/oracle/19.3" -lsdbName icmnlsdb -lsdbPort 1521 -lsdbAdminUser icmadmin -lsdbAdminPwd password -lsdbJdbcUrl "jdbc:oracle:thin:@//<hostname>:1521/share19c" -rmdbName rmdb -rmdbPort 1521 -rmdbAdminUser rmadmin -rmdbAdminPwd password -rmdbJdbcUrl "jdbc:oracle:thin:@//<hostname>:1521/share19c" -rmasWasServerHome "/opt/IBM/WebSphere/AppServer" -rmasWasProfileHome "/opt/IBM/WebSphere/AppServer/profiles/AppSrv01" -rmasWasSecurityEnabled Y -rmasWasAdminID wasadmin -rmasWasAdminPwd password -rmasWasJdbcPath "/opt/oracle/19.3/jdbc/lib/ojdbc8.jar" -rmasDeployTarget ApplicationServer -rmasWasAppNodeName utp02cm8vqtxw07Node01 -rmasWasAppServerName server1 -rmasWasHostName utp02cm8vqtxw07.development.unicom.software -rmasHttpPort 9080 -rmasHttpsPort 9443 -websvcWasServerHome "/opt/IBM/WebSphere/AppServer" -websvcWasProfileHome "/opt/IBM/WebSphere/AppServer/profiles/AppSrv01" -websvcWasSecurityEnabled Y -websvcWasAdminID wasadmin -websvcWasAdminPwd password
Displaying more information about the configuration response file generation tool
To display more information about the configuration response file generation tool, run the following command:
generateRsp.bat –help
Running the silent installation and configuration
install -i silent -f path/install.rspIf you are installing a fix pack, use installUpdate
instead of install.
Replace path/install.rsp with the full path and name of the installation response file. The default path is the local directory.
IBMCMREPO/8.7.version/bin/cmcfgmgr_CM -f path/config.rsp -p passwordWhen the configuration manager runs in silent mode, no windows display, and the configuration progresses as if you had entered the values in each window.
If the silent installation or configuration process stops immediately, you might not see any error messages. Some error messages are hidden when there are no installation windows.
For configuration, check if there are any errors in the log files that are the following folder: IBMCMREPO/8.7.version/cmcfgmgr/log/HOSTNAME. For more information about the log files, see Installation and configuration log locations on Windows.
Running the silent configuration removal and uninstallation
If you want to remove the whole Content Manager Enterprise Edition system from your machine, you should first remove its configuration, then run the uninstall. If your system was upgraded using a fix pack, you need to remove both the fix pack configuration and then the base CM configuration. For detailed instructions, refer to Removing content management system components.
To perform a silent configuration removal:
- Generate a response file for removal.
- Refer to To record the information that you enter in the Configuration Manager.
- Set the
actionTypeparameter to eitherFIXPACK_REMOVEorFRESH_REMOVE_CONFIG, depending on your environment.
- Run the silent configuration using the response file.
- Refer to Running the silent installation and configuration.
- Use the generated removal response file to run the silent removal process.
- To run a silent uninstallation, enter the following
command:
uninstall_CM87 -i silentA response file is not required.