You can use the Installation Manager GUI to install WebSphere® Application Server Version 8.5.
Prepare your system as described in Installing Installation Manager and preparing to install the product.
You can remove any files that have already been saved by clicking Delete Saved Files. If you delete the files and you need to roll back a package later, you must connect to a repository or insert the media to obtain the required files for the previous version of the package.
Installation Manager searches its defined repositories for available packages.
If you already have the product installed on a WebSphere Application Server installation on your system, a message displays indicating that the product is already installed. To create another installation of the product in another location, click Continue.
Any recommended fixes are selected by default.
If there are recommended fixes, you can select the option to show only recommended fixes and hide non-recommended fixes.
Symbolic links are not supported.
WebSphere Application Server cannot install properly if the target directory includes a semicolon.
A semicolon is the character used to construct
the class path on Windows systems.
English is always selected.
This option installs 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.
IBM thin clients and resource adapters provide a set of clients and resource adapters for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. An embeddable container runs in a standalone Java Platform, Standard Edition environment. For example, you can use the embeddable EJB container to run enterprise beans outside the application server.
This option installs 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.
This option installs the embeddable EJB container.
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 option installs the sample applications for learning and demonstration environments.
The samples include both source code files and integrated enterprise applications that demonstrate some of the latest Java (TM) Platform, Enterprise Edition (Java EE) and WebSphere technologies. The samples are recommended for installation to learning and demonstration environments, such as development environments. However, they are not recommended for installation to production application server environments.
This option allows you to choose between a 32-bit and 64-bit Software Development Kit.
This option installs 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.
IBM thin clients and resource adapters provide a set of clients and resource adapters for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. An embeddable container runs in a standalone Java Platform, Standard Edition environment. For example, you can use the embeddable EJB container to run enterprise beans outside the application server.
This option installs 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.
This option installs the embeddable EJB container.
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 option installs the sample applications for learning and demonstration environments.
The samples include both source code files and integrated enterprise applications that demonstrate some of the latest Java (TM) Platform, Enterprise Edition (Java EE) and WebSphere technologies. The samples are recommended for installation to learning and demonstration environments, such as development environments. However, they are not recommended for installation to production application server environments.
Selecting 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 great 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.
This option allows you to choose between a 32-bit and 64-bit Software Development Kit.
You can create a standalone application server profile, management profile, managed (custom) profile, cell profile, or secure proxy profile using the Profile Management Tool or the manageprofiles command.
Do not enable this option if you do not have access to the service repository.