This topic provides the steps necessary to use the installation
wizard and perform a silent installation.
About this task
Use these steps to perform a silent installation, which uses
the installation wizard to install the product. Instead of displaying
a user interface, the silent installation provides interaction between
you and the wizard by reading all of your responses from a file that
you must customize.
Procedure
- Verify that the host server jobs are
started on your iSeries™ server. The host server jobs allow
the installation code to run on iSeries.
Enter this command on a CL command line: STRHOSTSVR SERVER(*ALL)
- Verify that your user profile has the
*ALLOBJ and *SECADM special authorities.
- Place the WebSphere® Application Server Supplements disc in the disc drive of your iSeries server.
- Customize the options response file.
- Locate the sample options response file. The file name
is setup.response in the operating system platform
directory on the product CD-ROM.
- Use the Copy (CPY) command to create a copy of the setup.response file
from the disk. For example:
CPY OBJ('/QOPT/WEBSPHERE/AppClient/setup.response') TODIR('/MYDIR')
Where:
QOPT
is the disk mount point.
WEBSPHERE is the disk volume label.
/AppClient
is the product directory on the disk. This will be referred to in
later steps.
Note: For DVD media, an additional directory prefix
is required before the product directory that reflects the operating
system and architecture of the installation. Using the previous example,
the following installation path applies when you use CD-ROM media:
CPY OBJ('/QOPT/WEBSPHERE/AppClient/setup.response') TODIR('/MYDIR')
However,
the following installation path applies when you use DVD media:
CPY OBJ('/QOPT/WEBSPHERE/os400_ppc64/AppClient/setup.response') TODIR('/MYDIR')
- Edit the copy of the file using EDTF from the i5/OS® command
line or using Wordpad from a mapped drive. Accept the
license agreement by making the following change in the response file:
-OPT silentInstallLicenseAcceptance="true'
This
is the only required change in the response file. Read the information
in the response file to determine if you want to change any other
options.
- Save the file.
- Invoke the installation program for WebSphere Application Client for i5/OS.
To do this, run the INSTALL command from
Qshell :
- From the i5/OS command line, start a Qshell
session: STRQSH
- Change directory to the AppClient subdirectory of CD-ROM
or DVD-ROM drive: cd /QOPT/WEBSPHERE/AppClient OR cd
/QOPT/WebSphere/os400_ppc64/AppClient
- Issue the INSTALL command to start
the installation program: install –options /MYDIR/setup.response
Important: Do not exit the Qshell session (PF3) until
the installation has completed. Doing so might cause the installation
to stop prematurely.
A JDK is automatically selected for invoking
the installer and configuring the product based on what JDKs are installed
on the machine. The priority for selection is done in the following
order:
- IBM® Technology for JDK 6 - 32 bit (5722-JV1 or
5761JV1 option 11)
- IBM Technology for JDK 6 - 64 bit (5722-JV1 or
5761JV1 option 12)
- IBM Developer Kit for Java™ 1.6
(5722-JV1 or 5761JV1 option 10)
To force IBM Technology for JDK 6 - 64 bit add the parameter:
-devkit16_64.
To
force IBM Developer Kit for Java 1.6
add the parameter: -devkit16_CLASSIC.
Consider the
following example to force the use of IBM Technology
for JDK 6 - 64 bit:
install –options /MYDIR/setup.response -devkit16_64
Results
You installed application clients silently by using the response
file.
Attention: Troubleshooting an invalid response
file name that was submitted during the silent installation. If
you get a response file error, the response file name may have been
typed incorrectly. Verify that this is the problem by removing the -silent command
and leaving -options <responsefile>. You may get a pop-up
window or command line error stating that the wizard cannot continue
because of the following error: The response file was not found (1001)
(403). The response file that you are passing cannot be found on the
system. Make sure that the path is correct, with no spelling mistakes,
and try the installation again.
What to do next
Use the installation
verification utility to verify a successful installation. If the installation
is not successful, fix the error as indicated in the installation
error message. For example, if you do not have enough disk space,
add more space, and reinstall the Application Client.