Saturday, June 4
SAP EP - J2EE architechture
Introduction
This article will discuss about the important components of portal technical infrastructure.
I will talk mainly about the SAP WAS, ABAP and TREX. I will also dicuss about the minimal WAS java installation and a large cluster installation in which we use load balancer. Once you have a complete understanding of the J2EE infrastructure, you are in a position to design a optimal portal infrastructure which will have all the important features : high availability, scalability, performance, security, and so on.
Components of a Portal Infrastructure
Various systems and devices comprise or come together to form the technical infrastructure : operating systems, network systems, firewalls, high availability solutions, load-balancing devices, and storage devices etc…
Major components of a portal technical infrastructure are :
• Web clients
• Load balancer
• Web servers
• Web dispatchers
• Proxy servers
• Portal server
• Web AS database
• User Management Engine (UME)
• TREX components
In this post I shall discuss mainly about the J2EE architecture and the TREX components.
Web AS Java Architecture
We will have a look at components in a Web AS Java installation. A typical installation has
a central instance, a central services instance, a Java instance, and a database instance.
What does the central instance consist of ? it consists of a dispatcher, a server, and a Software Delivery Manager (SDM).
The central services instance contains the message service and the enqueue service
installed together on one machine.
The Java instance does not contain an SDM. The Java instance can contain a dispatcher and one or more J2EE server processes.
These various instances can be installed on separate physical machines and if they are installed in this way, scalability and availability of the system can be enhanced.
When we form a java cluster, more than one java instances can be there but only one central service instance. If there are more than one java instances then there has to be a load balancer such as a sap web dispatcher to distribute the load or the incoming requests to various java instances in the cluster.
A java instance has n number of server processes. The number of server processes available in a java instance depends upon RAM of the host on which that Java instance is installed.
Apart from server processes, a Java instance has something called java dispatcher.
It is a kind of load balancer that receives the client request and forwards it to the server process. Message service tells the java dispatcher as to which is the most suitable server process to which the request should be routed.
Server process will process the request and will store the user session.
The java instance in the cluster which has a SDM installed on it is called the central java instance.
There is something called Java Startup and Control Framework which is used for starting and stopping the Java instance. So it can be controlled and monitored using the SCF.
Related Articles :
This article will discuss about the important components of portal technical infrastructure.
I will talk mainly about the SAP WAS, ABAP and TREX. I will also dicuss about the minimal WAS java installation and a large cluster installation in which we use load balancer. Once you have a complete understanding of the J2EE infrastructure, you are in a position to design a optimal portal infrastructure which will have all the important features : high availability, scalability, performance, security, and so on.
Components of a Portal Infrastructure
Various systems and devices comprise or come together to form the technical infrastructure : operating systems, network systems, firewalls, high availability solutions, load-balancing devices, and storage devices etc…
Major components of a portal technical infrastructure are :
• Web clients
• Internet browsers
• PDAs
• Mobile solutions
• Web infrastructure• Load balancer
• Web servers
• Web dispatchers
• Proxy servers
• Portal server
• Portal platform
• Knowledge management
• Content management
• Collaboration platform
• J2EE engine• Web AS database
• User Management Engine (UME)
• TREX components
• Web server
• Retrieval and Classification Engine
• Retrieval and Classification Index
In this post I shall discuss mainly about the J2EE architecture and the TREX components.
Web AS Java Architecture
We will have a look at components in a Web AS Java installation. A typical installation has
a central instance, a central services instance, a Java instance, and a database instance.
What does the central instance consist of ? it consists of a dispatcher, a server, and a Software Delivery Manager (SDM).
The central services instance contains the message service and the enqueue service
installed together on one machine.
The Java instance does not contain an SDM. The Java instance can contain a dispatcher and one or more J2EE server processes.
These various instances can be installed on separate physical machines and if they are installed in this way, scalability and availability of the system can be enhanced.
When we form a java cluster, more than one java instances can be there but only one central service instance. If there are more than one java instances then there has to be a load balancer such as a sap web dispatcher to distribute the load or the incoming requests to various java instances in the cluster.
A java instance has n number of server processes. The number of server processes available in a java instance depends upon RAM of the host on which that Java instance is installed.
Apart from server processes, a Java instance has something called java dispatcher.
It is a kind of load balancer that receives the client request and forwards it to the server process. Message service tells the java dispatcher as to which is the most suitable server process to which the request should be routed.
Server process will process the request and will store the user session.
The java instance in the cluster which has a SDM installed on it is called the central java instance.
There is something called Java Startup and Control Framework which is used for starting and stopping the Java instance. So it can be controlled and monitored using the SCF.
Related Articles :
SAP EP - Standard Portal Services
Portal Eventing and Navigation
Portal Look and Feel - Branding the Portal
How to Develop Portal Applications
SAP EP-Developing portal content and assigning permissions
SAP EP-Role maintenance
SAP EP-How to make Enterprise Portal highly available
SAP Material Management Introduction
Portal Eventing and Navigation
Portal Look and Feel - Branding the Portal
How to Develop Portal Applications
SAP EP-Developing portal content and assigning permissions
SAP EP-Role maintenance
SAP EP-How to make Enterprise Portal highly available
SAP Material Management Introduction
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
You are welcome to express your views here...