WebSphere Application Server

-






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

Application 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 typical diagram indicates application server located in the user requests.

typical digram

Supported Platforms


WebSphere Application Server is supported on following platforms.

 - AIX
- HP
- IBM i
- z/OS
- Linux
- Solaris
- Windows

WebSphere Editions


- WebSphere Liberty
- Express
- Base
- Network Deployment
- Hypervisor Edition
- z/OS
- Developers

WebSphere Topologies

According to the behavior of application and its requirement there are various topologies like below

 . Standalone
. Network Deployment
. Administrative Agent

1. Standalone:


 It’s basic topology where you install WebSphere on a single server. By implementing this, you will have Cell, Node, and Server (JVM) on a single machine, which has some of the following limitations.
Won’t be able to start server from admin console
No high availability
No load balancing
All administrative tasks by connecting to JVM
Probably this would be good for development or no critical non-production environment. Below is the typical server diagram for standalone topology.

Standalone Topology

2. Network Deployment topology:


 This topology can have multiple JVM running on the same server or different server.
This is supported only with WebSphere Application Server Network Deployment edition.
 you can have all administrative tasks done including starting the JVM through DMGR console.
In this topology – DMGR and Node agent run as a separate process and it supports clustering for high-availability. Below is the basic diagram of ND topology.

Network Deployment topology



3. Administrative Agent topology:


In this topology, an additional process called administrative agent is created which helps to manage multiple standalone servers registered to administrative agent.This allows an administrator to manage all registered nodes using administrative agent console.This becomes very useful when you have multiple standalone servers, and you wish to perform administrative tasks including starting JVM through a console. Below diagram illustrates a basic administrative agent topology.


Administrative Agent topology


WebSphere 8.5.5 Features: 


1. Java SE 7 support : WAS 8.5 have the option to support Java 7 SE
2. HPEL logging (High Performance Extensible Logging) : Binary logging which is faster than text logging. This helps in runtime performance.
3. Inbuilt health management :  Monitor the application server health and respond to the potential issues before an outage occurs.
4. Liberty profile
5. Intelligent routing
6. Dynamic clustering
7. JDBC 4.1 clustering
8. Web 2.0 support
9. SIP – Serviceability and troubleshooting enhancements to Session Initiation Protocol support more resilient processing of SIP sessions.
10. Application Resiliency – WAS 8.5 ND is integrated with WebSphere virtual enterprise.


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