You can use the iRemoteInstall command
to install IBM® Installation
Manager or a WebSphere® Application
Server product offering from a Windows workstation
to a remote target IBM i system.
Before you begin
Prepare for the installation before using this procedure.
See Preparing the operating system for installation on IBM i for more information.
The
product offering repository files or the IBM Installation
Manager for IBM i installation
kit compressed file must be available on the Windows system.
Important: You
must set your JAVA_HOME environment variable to your IBM Installation Manager JRE home before running
the command directly from the product media. You do not need to set
your JAVA_HOME environment variable to your IBM Installation Manager JRE home before running
the command from a WebSphere Customization Toolbox installation.
Restrictions: - The iRemoteInstall command does not support
keyring files used to pass confidential information You must use the
physical media or download the installation files to your local system.
- The iRemoteInstall command does not support
the use of response files.
About this task
Note: By running this script, you accept the terms of the
product license. The relevant terms and conditions, notices, and other
information are provided in the license-agreement files in the lafiles or product_name/lafiles subdirectory
of the installation image or repository for this product.
- Location of the iRemoteInstall command:
- The iRemoteInstall command is located in the
following directory when it has been installed as part of the WebSphere Customization Toolbox:
wct_root/Remote_Installation_Tool_for_IBM_i
Tip: A version of this utility that is current when the product
is released is also available on the media or installation image.
You can run the command directly from the media connected to a Windows system to install the
offering on a remote target IBM i
system. This version of the utility is located at the following location:
media_root\Remote_Installation_Tool_for_IBM_i\iRemoteInstall.bat
where
media_root is
the root directory of the media or installation image containing the
product or supplements.
- Syntax of the iRemoteInstall command:
iRemoteInstall.bat
-hostname i5_hostname
-username user_login_name
-password user_login_password
-iminstkit im_install_kit_file_path_and_name | -wasoid was_offering_id
-wasrepoloc was_install_file_location
-appdataloc im_agent_data_location
-wasinstloc was_install_location
-wassharedloc was_shared_location
-features feature_ID_1,feature_ID_2, . . .
-waslangs lang_ID_1,lang_ID_2, . . .
-properties key=value,key=value, . . .
-log log_file_path_and_name
-trace
-version
-help
- Parameters of the iRemoteInstall command:
- -hostname i5_hostname
- Specifies the host name of the target IBM i machine to which Installation Manager or
the WebSphere Application
Server product offering is going to be installed
This parameter
is required.
- -username user_login_name
- Specifies the login name of the user who is performing the Installation
Manager or WebSphere Application
Server remote installation
This user must be a valid user for the
target IBM i system with *ALLOBJ
and *SECADM special authorization.
- -password user_login_password
- Specifies the login password of the user specified in -username
- -iminstkit im_install_kit_file_name
- Specifies the location of the Installation Manager for IBM i installation kit
You must
include the path if it is not in the same directory as the command.
This
parameter is required.
- -wasoid was_offering_id
- Specifies the ID of the WebSphere Application
Server product offering being installed
Example values are base,
nd, express, etc. This parameter is not case sensitive.
The
value to use can be found in the product offering ID. If the offering
ID is com.ibm.websphere.XXX.v85,
for example, the -wasoid value should be XXX. The IDs for various WebSphere Application Server
product offerings can be found in WebSphere Application Server product offerings for supported operating systems
- -wasrepoloc was_install_file_location
- Specifies the location of the WebSphere Application
Server installation repository
This option must be specified if
the -wasoid parameter is specified.
- -appdataloc im_agent_data_location
- Specifies the location of the Installation Manager agent data
If
no value is specified for this parameter, it is set to the default
value of /QIBM/UserData/InstallationManager.
- -wasinstloc was_install_location
- Specifies the location of the WebSphere Application
Server installation
If no value is specified for this parameter,
it is set to the default value of /QIBM/WAS85/AppServer.
- -wassharedloc was_shared_location
- Specifies the location of the WebSphere Application
Server shared location
If no value is specified for this parameter,
it is set to the default value of /QIBM/WAS85/AppServer_Shared.
- -features feature_ID_1,feature_ID_2,
. . .
- Specifies the features to be installed
The feature IDs must
be separated by commas (,). For example: core.feature,ejbdeploy,thinclient,embeddablecontainer,samples,liberty
Tip: If
no features are specified, the default features (core.feature, ejbdeploy, thinclient,
and embeddablecontainer) are installed. To install
only the features that you want, specify the list of features explicitly.
- -waslangs lang_ID_1,lang_ID_2,
. . .
- Specifies the languages for which translated content should be
installed
The language IDs must be separated by commas (,). For
example: en,fr,it,zh,ro,ru,zh_TW,de,ja,pl,es,cs,hu,ko,pt_BR
English
is installed even if it is not specified in the language list.
If
this parameter is not specified, only the English translation content
is installed by default.
If languages are specified using both
this parameter and the -properties parameter, the values specified
in this parameter are used.
- -properties key=value,key=value,
. . .
- Specifies package-group (profile) properties
- -log log_file_path_and_name
- Turns on the log, and sends all messages to the specified file
and location
The path can be absolute (c:\temp\mylog.log for
exampled) or relative (..\mylog.log for example).
Because
you can append multiple installation actions into the same log, the
actual name of a log file that is generated is log_file_path_and_name.x.log,
where x is the number of the log file from 0 to
29. The maximum log file size is approximately 10 MB; and the maximum
number of log files generated is 30.
- -trace
- Provides trace output of what the command checks and what the
command discovers
- -version
- Displays the version information for the command
- -help
- Displays usage information for the command
Procedure
- Log in to the IBM i
machine using the IBM Personal
Communications tool, or telnet with TN5250 to the IBM i machine.
- If TCP/IP is not started or if you do not know if TCP/IP
is started, enter the following command on the Control Language (CL)
command line:
STRTCP
- Verify that the host server jobs are started on your IBM i server.
The
host server jobs allow the installation code to run on IBM i.
Enter the following command on
the CL command line:
STRHOSTSVR SERVER(*ALL)
- Verify that your user profile has *ALLOBJ and *SECADM special
authorities.
- Run the iRemoteInstall command in the
temporary directory to install Installation Manager or the Websphere
Application Server product offering.
In order to install
a Websphere Application Server product offering, Installation manager
must already be installed on the target system.
- Verify the installation.
- Check for error messages in the output from the iRemoteInstall command.
- Look for errors in the installation log.
Example
Here is an example of installing IBM Installation Manager with the
iRemoteInstall command:
./iRemoteInstall
-hostname iserver1.somedomain.com
-username wasadmin -password mypwd
-iminstkit E:\agent.installer.os400.motif.ppc_1.4.3000.20101206_0100.zip
Here
is an example of installing WebSphere Application
Server with the
iRemoteInstall command:
./iRemoteInstall
-hostname iserver1.somedomain.com
-username wasadmin -password mypwd
-wasoid BASE
-wasrepoloc E:\repository
What to do next
After you install WebSphere Application
Server, you can create a standalone
application server profile or a management profile with an administrative
agent server by running the manageprofiles command
on the IBM i system containing
the WebSphere Application
Server installation.
The following is an example
of using the
manageprofiles command to create
a default standalone application server profile. This example is based
on the following assumptions:
- The samples feature is installed.
- Security is to be enabled.
- The system host name is myhost.abc.com.
- The appserver_install_root is /QIBM/ProdData/WebSphere/AppServer/V85/BASE.
- The user_data_root is /QIBM/UserData/WebSphere/AppServer/V85/BASE.
- The administrative user name is wasadmin.
- The password is password.
Default standalone application server:manageprofiles -create
-portsFile /QIBM/ProdData/WebSphere/AppServer/V85/BASE/profileTemplates/default/actions/portsUpdate/portdef.props
-serverName server1
-nodeName myhost
-hostName myhost.abc.com
-cellName myhost
-adminUserName wasadmin
-adminPassword password
-templatePath /QIBM/ProdData/WebSphere/AppServer/V85/BASE/profileTemplates/default
-enableAdminSecurity true
-profileName default