Working with sample response files for IBM Installation Manager

Procedure

Sample response files for IBM Installation Manager are provided in the Silent_Install_Sample_Files.zip compressed file. The following procedures describe how to use them.

1. Pick the appropriate sample response file from the compressed file. The Silent_Install_Sample_Files.zip file contains one subdirectory per release.
   Important: For an installation that does not install Application Center on an application server, use the file named install-no-appcenter.xml.

   For an installation that installs Application Center, pick the sample response file from the following table, depending on your application server and database.

   Table 1. Sample installation response files in the Silent_Install_Sample_Files.zip file to install the Application Center

   Application server where you install the Application Center	Derby	IBM DB2®	MySQL	Oracle
   WebSphere® Application Server Liberty profile	install-liberty-derby.xml	install-liberty-db2.xml	install-liberty-mysql.xml (See Note)	install-liberty-oracle.xml
   WebSphere Application Server full profile, stand-alone server	install-was-derby.xml	install-was-db2.xml	install-was-mysql.xml (See Note)	install-was-oracle.xml
   WebSphere Application Server Network Deployment	n/a	install-wasnd-cluster-db2.xml install-wasnd-server-db2.xml install-wasnd-node-db2.xml install-wasnd-cell-db2.xml	install-wasnd-cluster-mysql.xml (See Note) install-wasnd-server-mysql.xml (See Note) install-wasnd-node-mysql.xml install-wasnd-cell-mysql.xml (See Note)	install-wasnd-cluster-oracle.xml install-wasnd-server-oracle.xml install-wasnd-node-oracle.xml install-wasnd-cell-oracle.xml
   Apache Tomcat	install-tomcat-derby.xml	install-tomcat-db2.xml	install-tomcat-mysql.xml	install-tomcat-oracle.xml

   Note: MySQL in combination with WebSphere Application Server Liberty profile or WebSphere Application Server full profile is not classified as a supported configuration. For more information, see WebSphere Application Server Support Statement. You can use IBM DB2 or another DBMS that is supported by WebSphere Application Server to benefit from a configuration that is fully supported by IBM Support.
   For uninstallation, use a sample file that depends on the version of MobileFirst Server or Worklight® Server that you initially installed in the particular package group:

   • MobileFirst Server uses the package group IBM MobileFirst Platform Server.
   • Worklight Server V6.x, or later, uses the package group IBM Worklight.
   • Worklight Server V5.x uses the package group Worklight.

   Table 2. Sample uninstallation response files in the Silent_Install_Sample_Files.zip

   Initial version of MobileFirst Server	Sample file
   Worklight Server V5.x	uninstall-initially-worklightv5.xml
   Worklight Server V6.x	uninstall-initially-worklightv6.xml
   IBM MobileFirst™ Platform Server V6.x or later	uninstall-initially-mfpserver.xml

2. Change the file access rights of the sample file to be as restrictive as possible. Step 4 requires that you supply some passwords. If you must prevent other users on the same computer from learning these passwords, you must remove the read permissions of the file for users other than yourself. You can use a command, such as the following examples:

   • On UNIX:

     chmod 600 <target-file.xml>

   • On Windows:

     cacls <target-file.xml> /P Administrators:F %USERDOMAIN%\%USERNAME%:F

3. Similarly, if the server is a WebSphere Application Server Liberty profile or Apache Tomcat server, and the server is meant to be started only from your user account, you must also remove the read permissions for users other than yourself from the following file:

   • For WebSphere Application Server Liberty profile: wlp/usr/servers/<server>/server.xml
   • For Apache Tomcat: conf/server.xml
4. Adjust the list of repositories, in the <server> element. For more information about this step, see IBM Installation Manager documentation at Repositories.

   In the <profile> element, adjust the values of each key/value pair.

   In the <offering> element in the <install> element, set the version attribute to match the release you want to install, or remove the version attribute if you want to install the newest version available in the repositories.

5. Type the following command:

   <InstallationManagerPath>/eclipse/tools/imcl input <responseFile>  -log /tmp/installwl.log -acceptLicense

   Where:
   • <InstallationManagerPath> is the installation directory of IBM Installation Manager.
   • <responseFile> is the name of the file that is selected and updated in step 1.
   For more information, see the IBM Installation Manager documentation at Installing a package silently by using a response file.