Today we will clear our understanding about the profiles in WebSphere Application Server. You must have a clear understanding of WebSphere Application Server packaging to understand what is profiles and needs of profiles in WebSphere Application Server.

What is Profiles in WebSphere Application Server?

In WebSphere Application Server there are two categories of files, Product files and User files. The Product files include the application binaries needed to run the application server. The User files contain information used by the application server. For example, this is where variables are defined, resources are configured, log files are written, and so on. A Profile is a collection of these files, creating a WebSphere run time environment. Product files is like an template on the basis of which Administrator creates profile as per the requirements. Combination of product files and user files becomes a complete WebSphere Application Server installation.

What is the need of Profiles in WebSphere Application Server?

The WebSphere Application Server installation process simply lays down a set of core product files required for the run time processes. After installation, you need to create one or more profiles that define the run time to have a functional system.
Profiles derives the application binaries from Product files and it maintains separate configuration files. This is an efficient use of disk space. Also, with one set of binaries, updates to the code can be applied in one location per physical machine, even when multiple profiles are configured.

Types of Profiles in WebSphere Application Server are as follows

  1. Application server profile
    The application server profile defines a single stand-alone application server. Using this profile gives you an application server that can be run in unmanaged (stand-alone) mode or managed mode (by federating it with the administrative agent profile). The environment has the following characteristics:

      1. The profile consists of one cell, one node, and one server. The cell and node are not relevant in terms of administration, but you see them when you administer the server through the administrative console scopes.
      2. The server uses a dedicated, built-in administrative console.

    The primary uses for this type of profile are:

    1. To build a stand-alone server using the Base or Express installation packages.
    2. To build a stand-alone server in a Network Deployment installation that is not managed by the deployment manager (a test machine, for example).
    3. To build a server in a distributed server environment to be later federated and managed by the deployment manager. When you federate this node, the default cell becomes obsolete, the node is added to the deployment manager cell, and the administrative console is removed from the application server.

    Check How to create stand-alone application Server profile in WebSphere Application Server to create Application Server profile.

  2. Deployment manager profile
    The deployment manager profile defines a deployment manager in a distributed server environment. Although you can conceivably have the Network Deployment edition and run only stand-alone servers, this action bypasses the primary advantages of Network Deployment, which is workload management, failover, and central administration.
    In a Network Deployment environment, create one deployment manager profile for each cell. This setup gives you:

        1. A cell for the administrative domain
        2. A node for the deployment manager
        3. A deployment manager with an administrative console
        4. No application servers

    After you have the deployment manager, you can:

    1. Federate nodes built either from existing application server profiles or custom profiles.
    2. Create new application servers and clusters on the nodes from the administrative console.

    Check How to create DMGR profile to create DMGR profile in WebSphere Application Server 8.5

  3. Custom profile
    A custom profile is an empty node without any server instance that is intended for federation to a deployment manager. After federation, the deployment manager uses it as a target on which it can create, for example, application server profile instances.
  4. Cell profile
    A cell profile combines two profiles: a deployment manager profile and an application server profile. In this case, the deployment manager and application server reside on the same system, and the application server profile is already federated to the deployment manager cell.
    Using this type of profile is a good way to quickly set up a distributed server environment. It can be useful for test environments that can have all nodes on one test system.
  5. Administrative agent profile
    The administrative agent profile provides enhanced management capabilities for stand-alone application servers. An administrative agent profile is created on the same node as the stand-alone servers and can manage only servers on that node. The node configuration for each stand-alone server is separate from any other servers on the system, but it is managed using the administrative console on the administrative agent. When a base application server registers with an administrative agent, much of the administrative code that was in the base server is now consumed by the administrative agent.
  6. Job manager profile
    A job manager is defined by a job manager profile. The job manager’s primary purpose is to support flexible management of WebSphere Application Server profiles and to queue jobs to registered servers.

Profiles can be created at any time during or after installation using graphical or command-line tools. WebSphere Application Server provides the following profile management tools:

  1. The manageprofiles command: A command-line interface for profile management functions.
  2. Profile Management Tool (PMT): A GUI interface delivered by the WebSphere Customization Toolbox. This tool gathers user input and invokes the manageprofiles command-line tool to manage the profiles for you.
  3. Administrative console of the deployment manager or the job manager profile, which can create profiles on remote machines.

Hope now you have understood the concept of profiles in WebSphere Application Server.

If you find any missing point in here, please let us know in comment section or tweet us at@techienotecom. To get more articles like this, subscribe to our RSS feeds.

Profiles in WebSphere Application Server

Leave a Reply

Your email address will not be published. Required fields are marked *

Notify me of followup comments via e-mail. You can also subscribe without commenting.

Recommend on Google