You can install WebSphere® Application
Server Liberty - Express® on IBM® i operating systems using the
Installation Manager command line.
Before you begin
Prepare for the installation before using this procedure.
See Preparing the operating system for installation on IBM i for more information.
Important: Before installing WebSphere Application
Server Liberty - Express, you
must read the license agreement that you can find with the product
files. Signify your acceptance of the license agreement by specifying -acceptLicense in
the command as described in this topic.
Install Installation
Manager on the system onto which you want to install the product.
- If you want to use the Installation Manager that comes with this
product, perform the following actions:
- Obtain the necessary files.
There are three basic options for
obtaining and installing Installation Manager and the product.
Note: If you do not have a Passport Advantage ID and password,
you must install the product from the product repositories on the
media or local repositories.
- Choose three separate locations for Installation Manager's binaries,
runtime data (agent data), and shared data locations.
- Install Installation Manager using the Installation Manager command
line.
- Sign on to the IBM i system
with a user profile that has *ALLOBJ and *SECADM special authorities.
- On a CL command line, run the STRQSH command
to start the Qshell command shell.
- Make sure that the umask is set to 022.
To verify the umask
setting, issue the following command:
umask
To
set the umask setting to 022, issue the following command:
umask 022
- Change to the location containing the Installation Manager installation
files, and run the following command:
installc -acceptLicense -log log_file_path_and_name
- If you already have a version of Installation Manager installed
on your system and you want to use it to install and maintain the
product, obtain the necessary product files.
There are three basic
options for installing the product.
- Access the physical media, and use local installation
You
can access the product repositories on the media. Use Installation
Manager to install the product from the product repositories on the
media.
- Download the files from the Passport Advantage site, and use
local installation
Licensed customers with a Passport Advantage ID and password
can download the necessary product repositories from the Passport Advantage site.
- Download the product repositories from the Passport Advantage site.
- Use Installation Manager to install the product from the downloaded
repositories.
- Access the live repositories, and use web-based installation
If
you have a Passport
Advantage ID and password, you can use Installation Manager to
install the product from the web-based repositories. Use Installation
Manager to install the product from the web-based repository located
at
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.EXPRESS.v85
Note: This
location does not contain a web page that you can access using a web
browser. This is a remote web-based repository location that you must
specify for the value of the -repositories parameter
so that the imcl command can access the files in
this repository to install the product.
Whenever possible,
you should use the remote web-based repositories so that you are accessing
the most up-to-date installation files.
Note: If you do not have a Passport Advantage ID and password,
you must install the product from the product repositories on the
media or local repositories.
Procedure
- Optional: If the repository requires a username
and password, create a credential-storage file to access this repository.
Tip: When creating a credential-storage file, append /repository.config at
the end of the repository URL location if the imutilsc command
is unable to find the URL that is specified.
Note: When you
use Installation Manager Version 1.6.2 and later, you should use the
-secureStorageFile and
-masterPasswordFile options
to store credentials in a credential-storage file. In versions of
Installation Manager earlier than Version 1.6.2, the
-keyring and
-password options
were used to access credentials in a keyring file. These options were
deprecated in Version 1.6.2. There is no migration path from keyring
files to storage files because of the differences in the file structures.
For more information on using the
-secureStorageFile and
-masterPasswordFile options
to store credentials in a credential-storage file, see the
Installation Manager Version 1.6 Information Center.
For more information on using the
-keyring and
-password options
to store credentials in a keyring file, see the
Installation Manager Version 1.5 Information Center.
- Choose three separate locations for the product's
binaries, runtime data (agent data), and shared data locations.
- Sign on to the IBM i
system with a user profile that has *ALLOBJ and *SECADM special authorities.
- On a CL command line, run the STRQSH command
to start the Qshell command shell.
- Make sure that the umask is set to 022.
To
verify the umask setting, issue the following command:
umask
To set the umask setting
to 022, issue the following command:
umask 022
- Change to the eclipse/tools subdirectory
in the directory where you installed Installation Manager.
- Use the imcl command to install the
product.
./imcl install com.ibm.websphere.liberty.EXPRESS.v85_offering_version,optional_feature_ID
-repositories source_repository
-installationDirectory installation_directory
-sharedResourcesDirectory shared_directory
-preferences preference_key=value
-properties property_key=value
-secureStorageFile storage_file -masterPasswordFile master_password_file
-acceptLicense
Tips: - 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 offering.
- You can install a list of features that are separated by commas.
- Embeddable EJB container and JPA client (embeddablecontainer)
This
option installs the embeddable EJB container and JPA client.
The
embeddable EJB container is a Java™ Archive
(JAR) file that you can use to run enterprise beans in a standalone Java Platform, Standard Edition
(SE) environment. You can run enterprise beans using this embeddable
container outside the application server. The embeddable EJB container
is a part of the EJB 3.1 specification and is primarily used for unit
testing enterprise beans business logic.
The JPA client can
be used with the embeddable EJB container to provide Java Persistence API capability in a Java SE environment.
- Extended Programming Models (extprogmodels)
The
Extended Programming Models feature provides a rich set of programming
models such as Web Services, JMS (including Message-Driven Beans),
and Mongo 2.0.
Notes: - If no features are specified, the default features (embeddablecontainer and extprogmodels)
are installed. To install only
the feature that you want, specify that feature explicitly.
- The offering_version, which optionally can
be attached to the offering ID with an underscore, is a specific version
of the offering to install (8.5.5.20110503_0200 for
example).
- If offering_version is not specified,
the latest version of the offering and all interim fixes for
that version are installed.
- If offering_version is specified, the specified
version of the offering and no interim fixes for that version
are installed.
The offering version can be found attached to the end of the
offering ID with an underscore when you run the following command
against the repository:
./imcl listAvailablePackages -repositories source_repository
- You can also specify none, recommended or all with
the -installFixes argument to indicate which interim
fixes you want installed with the offering.
- If the offering version is not specified, the -installFixes option
defaults to all.
- If the offering version is specified, the -installFixes option
defaults to none.
- For initial installations, it is a good practice to specify the user_data_root;
otherwise, the default value for the user_data_root, /QIBM/UserData/WebSphere/AppServer/V85/Express, is used. Use
the was.install.os400.profile.location property to
specify the user_data_root. If the user_data_root is
to be /QIBM/UserData/WebSphere/AppServer/V85/Express_1, for example, specify -properties
was.install.os400.profile.location=/QIBM/UserData/WebSphere/AppServer/V85/Express_1 on the imcl installation
command.
- The program might write important post-installation instructions
to standard output.
For more information on using the imcl command
to install the product, see the IBM Installation
Manager Information Center.
Example
Here is an example of using the
imcl command
to install Websphere Application Server Liberty
- Express:
./imcl install com.ibm.websphere.liberty.EXPRESS.v85
-repositories https://downloads.mycorp.com:8080/WAS_85_repository
-installationDirectory /QIBM/ProdData/WebSphere/AppServer/V85/Express
-properties was.install.os400.profile.location=/QIBM/UserData/WebSphere/AppServer/V85/Express
-sharedResourcesDirectory /QIBM/UserData/InstallationManager/IMShared
-secureStorageFile $HOME/WASFiles/temp/credential.store -masterPasswordFile $HOME/WASFiles/IM/master_password_file.txt
-acceptLicense