![[Note]](images.admon/note.gif) | |
|
Installation Liberty Profile using the IBM Installation Manager
Prior to WebSphere Application Server V8.5.5, the Liberty profile was installed from the IBM Installation Manager as a feature of the WebSphere Application Server package. With V8.5.5, the Liberty profile is a separate package.
To install the Liberty profile using the IBM Installation Manager:
Install the IBM Installation Manager, and configure the repository with the WebSphere Application Server packages.
Start the Installation Manager.
Click Install.
Check the IBM WebSphere Application Server package, and then click Next.
Accept the license agreement, provide your installation location for the product, and click Next.
Select the Liberty profile package and the IBM WebSphere SDK Java Technology Edition Version 6 for Liberty, as illustrated in figure below. You might use this Java runtime later for the Liberty profile servers. Click Next.
Click Install to start the installation process and when the installation process ends, click Finish.
Using WebSphere Developer Tools (WDT) to work with the configuration
Each Liberty profile is configured using a server.xml configuration file. The only required entry
in the server.xml file is the server tag, which defines a server configuration scope.
You can use the WebSphere Developer Tools (WDT) to work with the server.xml file. Wizards and
windows in the Eclipse workbench help to configure all of the server properties. To configure
the server.xml file using WebSphere developer tools, double-click the
Server Configuration, as illustrated in figure:
The current server configuration will be shown in a new window with all of its features and properties listed, as illustrated in figure:
Instead of typing the name of each of the configuration elements or their numerous properties, you can simply click Add..., and the WebSphere developer tools will guide you with the possible values and properties to configure. See figure:
Profiles
WebSphere Application Server runtime environments are built by creating sets of configuration files, named profiles, that represent a WebSphere Application Server configuration.
The Customization Toolbox allows you to create separate environments, such as for development or testing, without a separate product installation for each environment. Different profile templates are available in the Customization Toolbox Profile Management Tool (PMT):
Cell
A cell template contains a federated application server node and a deployment manager.
Deployment manager
The deployment manager profile provides the necessary configuration for starting and managing the deployment manager server.
Default profile
This server default profile provides the necessary configuration file for starting and managing an application server, and all the resources that are needed to run enterprise applications.
Administrative agent
This profile is used to create the administrative agent to administer multiple stand-alone application servers.
Secure proxy
This profile is available when you install the DMZ secure proxy server feature.
Job manager
This profile coordinates administrative actions among multiple deployment managers, and administers multiple stand-alone application servers. It also asynchronously submits jobs to start servers, and completes various other tasks.
Custom
This profile, also known as empty node because it has no application server inside, can be federated to a deployment manager cell later. It is used to host application servers, clusters, an on-demand router, and other Java processes.
Each profile contains files that are specific to that run time (such as logs and configuration files). You can create profiles during and after installation. After you create the profiles, you can perform further configuration and administration by using WebSphere administrative tools.
Each profile is stored in a unique directory path, which is selected by the user when the profile is created. Profiles are stored in a subdirectory of the installation directory by default, but can be located anywhere.
By creating various profiles, you can create a distributed server configuration by using one of the following methods:
Create a deployment manager profile to define the deployment manager, and then create one or more custom node profiles. The nodes that are defined by each custom profile can be federated into the cell managed by the deployment manager. You can federate these nodes during profile creation, or manually later. The custom nodes can exist inside the same operating system image as the deployment manager, or in another operating system instance. You can then create application servers by using the administrative console or
wsadminscripts.This method is useful when you want to create multiple nodes, multiple application servers on a node, or clusters.
Create a deployment manager profile to define the deployment manager. Then, create one or more application server profiles, and federate these profiles into the cell that is managed by the deployment manager. This process adds both nodes and application servers into the cell. The application server profiles can exist on the deployment manager system or on multiple separate systems or z/OS images.
This method is useful in development or small configurations. Creating an application server profile gives you the option of having the sample applications installed on the server. When you federate the server and node to the cell, any installed applications can be carried into the cell with the server.
Create a cell profile. This method creates both a deployment manager profile and an application server profile. The application server node is federated to the cell. Both profiles are on the same system.
This method is useful in a development or test environment. Creating a single profile provides a simple distributed system on a single server or z/OS image.
