The product code for WebSphere® Application Server for z/OS® Version 8.5 is installed using IBM® Installation Manager.
Create an Installation Manager on your z/OS system. You will need to know the location of the binaries directory for the Installation Manager and have access to a user ID that can invoke the Installation Manager.
Obtain the product repository for WebSphere Application Server for z/OS Version 8.5. The repository can be mounted read-only.
This copy of the product must be mounted at this location every time Installation Manager accesses it to install, uninstall, or modify it. This does not have to be the same location at which the product will be mounted when used in production.
Installation Manager requires that every installed product or group of products have its own installation location.
chown IMADMIN:IMGROUP /usr/lpp/zWebSphere/V8R5
chmod 775 /usr/lpp/zWebSphere/V8R5
cd /InstallationManager/bin/eclipse/tools
zCreateFileSystem.sh -name WAS.v85.SBBOHFS -type ZFS
-megabytes 1800 200 -volume PRV005
-mountpoint /usr/lpp/zWebSphere/V8R5
-owner IMADMIN -group IMGROUP
cd /InstallationManager/bin/eclipse/tools
installation_manager_binaries_directory/eclipse/tools/imutilsc saveCredential
-keyring keyring_file
-userName user_ID -userPassword user_password
-url http://www.ibm.com/software/repositorymanager/com.ibm.websphere.zOS.v85/repository.xml
where keyring_file is
the path and file name of the keyring to be created, and user_ID and user_password are
the universal IBM user ID and password that you use to access protected
IBM software websites./InstallationManager/eclipse/tools/imutilsc saveCredential
-keyring /u/jane/IBM.software.keyring
-userName jsmith01 -userPassword 732Ukelele
-url http://www.ibm.com/software/repositorymanager/com.ibm.websphere.zOS.v85/repository.xml
Make sure that the keyring file is readable by the Installation Manager user ID.
There is no migration path from keyring files to storage files because of the differences in the file structures. You must create a storage file to replace a keyring file.
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.
imcl listAvailablePackages -repositories list_of_repository_locations
You should see one or more levels of the WebSphere Application Server for z/OS Version 8.5 offering, com.ibm.websphere.zOS.v85.
The list_of_repository_locations should include the path to the initial product repository and the paths to any additional service repositories. Separate URLs in the list_of_repository_locations with commas.
imcl listAvailablePackages
-repositories /usr/lpp/InstallationManagerRepository/HBBO850
-useServiceRepository
-keyring /u/jane/IBM.software.keyring
There is no migration path from keyring files to storage files because of the differences in the file structures. You must create a storage file to replace a keyring file.
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.
imcl install com.ibm.websphere.zOS.v85
-installationDirectory installation_location
-repositories list_of_repository_locations
-sharedResourcesDirectory shared_data_location
-acceptLicense
[-useServiceRepository -keyring keyring_file]
[-installFixes <all | recommended | none> ]
The -sharedResourcesDirectory parameter points to a directory in which Installation Manager will store artifacts from the repository during installation processing. This value is set the first time a product is installed with a particular Installation Manager. This directory should have at least 30,000 tracks of free space. You can omit this parameter after the shared resources directory has been set.
By specifying -acceptLicense, 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.
If you do not specify the product version to be installed, Installation Manager will install the latest version of the product along with any fixes in the repository locations. You can prevent the installation of fixes by specifying -installFixes none or install only recommended fixes by specifying -installFixes recommended.
If you specify the product version to be installed, any fixes in the repository locations will only be installed if you specify -installFixes recommended or -installFixes all.
This optional feature contains the EJBDeploy tool for pre-EJB 3.0 modules.
Before you deploy applications on the server, you must run the EJBDeploy tool on applications that contain EJB modules that are based on specifications prior to EJB 3.0. Running the EJBDeploy tool generates deployment code for enterprise beans in the application. Beginning with the EJB 3.0 specification, the EJBDeploy tool is no longer required because WebSphere Application Server uses a new feature called JITDeploy, which automatically generates code when the application starts.
This optional feature contains the IBM standalone thin clients and resource adapters. IBM thin clients provide a set of clients for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. IBM resource adapters provide the resource adapters for JMS.
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 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.
This optional feature contains the PlantsByWebSphere sample application. The samples feature is recommended for installation in learning and demonstration environments, such as development environments; however, it is not recommended for installation in production application server environments.
This optional feature contains the EJBDeploy tool for pre-EJB 3.0 modules.
Before you deploy applications on the server, you must run the EJBDeploy tool on applications that contain EJB modules that are based on specifications prior to EJB 3.0. Running the EJBDeploy tool generates deployment code for enterprise beans in the application. Beginning with the EJB 3.0 specification, the EJBDeploy tool is no longer required because WebSphere Application Server uses a new feature called JITDeploy, which automatically generates code when the application starts.
This optional feature contains the IBM standalone thin clients and resource adapters. IBM thin clients provide a set of clients for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. IBM resource adapters provide the resource adapters for JMS.
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 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.
This optional feature contains the PlantsByWebSphere sample application. The samples feature is recommended for installation in learning and demonstration environments, such as development environments; however, it is not recommended for installation in production application server environments.
Installing this application-server feature gives you a lightweight profile of the application server along with a simplified configuration approach for the development environment. Its fast restart times, small size, and ease of use make it a good option for building web applications that do not require the full JEE environment of traditional enterprise application server profiles. The Liberty profile also can be used in production; and because it is a dynamic configuration, the application server provisions only the features required by the running applications.
If you installed the initial product repository with SMP/E, you can use sample job BBO1INST in the SBBOJCL dataset to perform the product installation.
Logs for the installation can be found in the logs subdirectory of the Installation Manager runtime data location.
You can now install other WebSphere Application Server components or configure an application-serving environment with the WebSphere Customization Toolbox or the zpmt.sh command. See Installing Liberty on z/OS for information on installing WebSphere Application Server Liberty for z/OS.