Profiles And Fedration

Profile:

A profile defines the run-time environment. The profile includes all the files that the server processes in the run-time environment and that you can change.
The manageprofiles command-line tool defines each profile for the product.
Run the Profile Management Tool or the manageprofiles command each time that you want to create a profile.
You can run the Profile Management Tool or the command-line tool to create a new profile on the same machine as an existing profile. Define unique characteristics, such as profile name and node name, for the new profile. Each profile shares all runtime scripts, libraries, the Java SE Runtime Environment 6 (JRE 6) environment, and other core product files.

Profile types:
1. Deployment manager server (DMGR):
The basic function of the deployment manager is to deploy applications to a cell of application servers, which it manages. Each application server that belongs to the cell is a managed node.

2. Administrative agent server:
The basic function of the administrative agent is to provide a single interface to administer multiple unfederated application servers.

3.  Job manager server:
The basic function of the job manager is to provide a single console to administer multiple base servers, multiple deployment managers, and do asynchronous job submission.

4. Application server profile:
 The ability to scale up a standalone application server profile by adding the application server node into a deployment manager cell. Multiple application server processes in a cell can deploy an application that is in demand.

5. Cell profile:
Creation of a cell profile generates a deployment manager and a federated node in one iteration through the Profile Management Tool. The result is a fully functional cell on a given system.

6. Custom profile:

A custom profile does not include default applications or a default server like the application server profile includes. A custom profile is an empty node. Add the node to the deployment manager cell. Then, you can use the administrative interface of the deployment manager to customize the managed node by creating clusters and application servers.

 7. Secure proxy profile

Use the secure proxy server to take requests from the Internet and forward them to application servers. The secure proxy server resides in the DMZ.

* We can create a WebSphere Application Server profile in two ways.
a) GUI – using Profile Management Tool
b) Silent – using manageprofile.sh script

 A) GUI – using Profile Management Tool

 Step 1) Login to server where WAS is installed.
Go to the path if windows: IBM WebSphere > IBM WebSphere Application Server > Tools > Profile Management Tool
if linux: Default installation location, it will be /app/IBM/WebSphere/AppServer/bin/ProfileManagement)
Launch Profile Management Tool

 ./pmt.sh

Step 2) It will open a “WebSphere Customization Toolbox” window, click Create

Step 3) On Profile Management Tools, Environment Selection, highlight the Application server environment type.


 Step 4) Click the Next button.

Step 5) On Profile Creation Options, select the Typical profile creation radio button.









(Note: choosing Typical profile creation uses the default configuration settings. It assigns unique names to the profile, node, and host. The tool also assigns unique port values.

Alternatively, you can choose Advanced profile creation to specify your own values for settings such as the location of the profile and names of the profile, node, and host.)

Step 6) Click the Next button.

Step 7) On Administrative Security, clear the Enable administrative security checkbox.










Step 8) Click the Next button.
Step 9) On Profile Creation Summary, review the information for accuracy and click the Create button. 

















The progress screen is displayed. Wait for the progress to complete 100%, which may take several minutes.

Step 10) Optionally, on Profile Creation Complete, you can select the check box for Launch the First steps console.













Step 11) Click the Finish button.

Step 12) If you chose to run First Steps, on WebSphere Application Server, First steps, select the first option, which is entitled: Installation verification.






















Step 13)Verify that the installation verification completed successfully. You should get the message entitled: The installation verification is complete.













Step 14) Close the screen for the First steps output.

Step 15) Verify that you can sign on to the Administration Console. For example:http://host:9060/ibm/console

B. Silent – using manageprofile.sh script

Dmgr Profile:

./manageprofiles.sh -create -profileName Dmgr01 -profilePath /app/IBM/WebSphere/AppServer/profiles/Dmgr01 -templatePath /app/IBM/WebSphere/AppServer/profileTemplates/dmgr

Application Server Profile:

./manageprofiles.sh -create -profileName AppSrv01 -profilePath /app/IBM/WebSphere/AppServer/profiles/AppSrv01 -templatePath /app/IBM/WebSphere/AppServer/profileTemplates/default

Custome Profile:

./manageprofiles.sh -create -profileName AppSrv01 -profilePath /app/IBM/WebSphere/AppServer/profiles/AppSrv01 -templatePath /app/IBM/WebSphere/AppServer/profileTemplates/managed

Fedration:

Add the application server node to a deployment manager cell. Adding the application server node to a cell is known as federation. Federation changes the standalone application server node into a managed node. You use the administrative console of the deployment manager to manage the node.

AddNode command:

./addNode.sh localhost_of_dmgr 8879(soap port number of Dmgr)
e.g.
[root@localhost~]./addNode.sh localhost 8879

If security is enabled then: 
[root@localhost~]./addNode.sh localhost 8879 -username abcd -passsword xxxxxx

Comments

Post a Comment

Popular posts from this blog

Understanding SSL

Image
Understanding SSL: There are many ways to go about creating an SSL connection between servers,  and the best one for your situation will depend upon the type of protocol you're planning to tunnel through it. As you probably know, the Secure Sockets Layer (SSL) allows the use of encryption to protect data sent via a TCP/IP connection. The most commonly used implementation of SSL is the HTTPS protocol: a secure encrypted alternative to HTTP for transferring information over the Web. Secure Sockets Layer ( SSL ) is a computer networking protocol for securing connections between network application clients and servers over an insecure network, such as the internet. Due to numerous protocol and implementation flaws and vulnerabilities, SSL was deprecated for use on the internet by the Internet Engineering Task Force ( IETF ) in 2015 and has been replaced by the Transport Layer Security ( TLS ) protocol. While TLS and SSL are not interoperable, TLS is backwards-compatible with
Read more

Session Management Part-1

Image
WebSphere Application Server Session Management Session support allows a Web application developer to maintain state information across multiple user visits to the application.  We will cover below points 1. HTTP session management 2. Session manager configuration 3. Session identifiers 4. Local sessions 5. General properties for session management 6. Session affinity 7. Persistent session management 1.HTTP session management: When an HTTP client interacts with a servlet, the state information associated with a series of client requests is represented as an HTTP session and identified by a session ID. Session management is responsible for managing HTTP sessions, providing storage for session data, allocating session IDs, and tracking the session ID associated with each client request through the use of cookies or URL rewriting techniques. 2.Session manager configuration: Session management in WebSphere Application Server can be defined at the follow
Read more

WebSphere Application Server

Image
What is WebSphere Application Server  ? WebSphere is a set of Java-based tools from IBM that allows customers to create and manage sophisticated business Web sites. The central WebSphere tool is the WebSphere Application Server (WAS), an application server that a customer can use to connect Web site users with Java applications or servlets. IBM released WebSphere Application Server 8.5 in June 2012 and 8.5.5 in June 2013 A pplication Server provides the infrastructure to host enterprise application. It handles application operation between user request to backend business application like a database, messaging, etc. Enterprise application, which is usually transactional based or heavily used, must have an application server with built-in redundancy, high availability, and performance oriented like WebSphere Application Server. Application Server usually sits between Web Server and Database or another backend like messaging, etc. Below is the typic
Read more