One installation alternative is to install WebSphere® ESB for i5/OS® from a Windows® workstation command line.
About this task
The remote silent mode allows you to install the product
with a single command from a remote Windows workstation.
Installation options must be specified in a response file. During
the installation, you are unable to change the installation options.
The parameters and default values are described in
responsefile.wesb.txt for command-line
installation.
Procedure
- If TCP/IP is not started on your System i® server, enter the Start TCP/IP (STRTCP)
command on the Control Language (CL) command line.
- Verify that the host server jobs are started on your System i server.
The host server jobs allow the installation code to run on i5/OS.
On a CL
command line, enter the following command:
STRHOSTSVR SERVER(*ALL)
- Verify that your user profile has the *ALLOBJ and *SECADM
special authorities.
- Place the WebSphere ESB for i5/OS disk in the disk drive of
your Windows workstation.
The autorun feature brings up the GUI. Click Cancel to
exit the GUI.
Do not use the WebSphere ESB for Windows disk or any other operating
system disk other than the disk for i5/OS.
- On your Windows workstation,
open a command prompt.
- Access the disk drive of your Windows workstation by switching to the disk
drive. For example, enter e: where e: is the letter assigned to your
DVD drive.
- Change to the WBI directory.
For example: cd WBI.
- Copy the response file from the disk directory to a directory
on your Windows workstation,
such as the C:\temp directory.
For
example:
copy responsefile.wesb.txt C:\temp\RESPONSEFILE
- If you have not already done so, read the IBM® International Program License Agreement located
in the \LICENSES directory.
If
you agree to the terms of the agreement, continue with the installation
process.
- Edit the RESPONSEFILE file.
- Change the value for -OPT silentInstallLicenseAcceptance
from false to true.
A value of true indicates that you
have read and accept the terms of the license agreement. This change
is required to run the installation.
- By default, the PROF_enableAdminSecurity option is set
to true. If you want to enable administrative security for the default
profile created during install, you must specify values for the PROF_adminUserName
and PROF_adminPassword options.
The user ID and password
do not need to be a system user ID and password or an LDAP user ID
and password. The ID-and-password pair specified are stored in the
user registry and used for administrative security for the default
profile. If you specify WebSphere local
security, the userid must be a valid user profile. If you specify
an LDAP registry, the userid must be a member of that registry. Write
down the user ID and password.
If you do not want to enable
administrative security for the default profile, change the value
for the PROF_enableAdminSecurity option from true to false.
Note: The Samples feature is not installed with the product
by default. If you want to use the samples, perform the following
actions:
- Specify sampleSelected for the -OPT addFeature option.
- Specify a value for the -OPT samplesPassword option if you are
enabling security.
- Run the install.exe command.
Specify the response file to use during the installation. Specify
the i5/OS system name and
a valid i5/OS user profile
and password when you run this command.
Your user profile
must have *ALLOBJ and *SECADM special authorities for this step.
install.exe system_name user_name password -options response_file -silent
The system_name variable
is the name of your System i server.
The user_name variable and the password variable
are your user profile login credentials, and the response_file variable
is the name of your response file.
The password used in this
command is displayed in clear text on the command line. For example:
install.exe MYISERIES myUserName myPassword
-options C:\temp\RESPONSEFILE -silent
After
you issue the command, control returns to the command prompt while
the installation process runs.
Results
This procedure results in installing WebSphere ESB from
a Windows workstation command
line.
What to do next
Verify the success of the installation
by examining the log.txt log file. The log file
is located in the directory install_root/logs/wbi/install/log.txt on
the System i server, where install_root
represents the location of the WebSphere ESB.
If this log file contains
the string INSTCONFSUCCESS on the last line, then the installation
was successful. Note that other terms such as INSTCONFPARTIALSUCCESS
or INSTCONFFAILED can occur on other lines within the file, or even
on the last line, but if INSTCONFSUCCESS is included in the last line,
the installation was successful.
If the
string INSTCONFPARTIALSUCCESS or INSTCONFFAILED appears in the last
line of the file without INSTCONFSUCCESS, problems were detected during
installation. INSTCONFPARTIALSUCCESS indicates that the installation
completed but errors were generated; INSTCONFFAILED, that the installation
failed completely.
If the installation was
unsuccessful, examine the install_error.log file to determine why.
This log file is located by default on the System
i server in the directory install_root/logs/wbi/install/install_error.log.
If the installation failed completely, also examine
any temporary log files located by default in the directory user_home/wbilogs.
See the description of all log files in Installation and profile creation log files.
You can
review other useful troubleshooting information in the following topics: