Create a custom WebSphere Application Server

Article title: create a custom WebSphere application server. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.

Based on the open-source project Apache Geronimo, was ce is a fully qualified application server that complies with Java EE 5 specifications. This article describes how to customize a lightweight server based on was ce, and describes the steps and methods for server customization through examples, and how to further expand the features of custom servers.
Introduction

WebSphere Application Server Community Edition (was ce) is an Application Server fully compliant with Java Platform and Enterprise Edition 5 (Java EE 5) specifications. That is to say, was ce contains all components that support Java EE 5 implementation: the environment required for developing and running Java EE applications, such as Web containers, EJB containers, message services, and command line management.

However, under some specific business requirements, some users may only need some functional components in was ce. for example, they only need Web containers instead of EJB containers, or you need an EJB container instead of a cluster. In this case, if the user uses the complete Java EE 5-certified was ce server, there will be a lot of functional modules that are not used in their own applications, this results in a waste of hard disk space and memory resources. At the same time, it also brings about disadvantages such as waiting for the startup time of the application server and the large number of packages bound to the application server.

So how can we solve these problems to make the application server more flexible to meet different business needs? The concept of custom servers also emerges. By using custom servers, you can extract the components necessary to manage and run your own applications, and customize a server that is lighter and faster to start. Was ce v2.1 and later versions can help you achieve this dream.

Was ce/Geronimo Architecture Overview

Before getting a deeper understanding of custom servers, we need to first understand how to manage components in was ce. Next we will briefly introduce the was ce system architecture and Plugin management mechanism.

Based on the Geronimo kernel and Plugin mechanism, the was ce application server provides interfaces (SPI) through the common services provided by GBean in the kernel, maximizing the reuse of existing Java EE modules, (These modules exist in the form of Geronimo Plugin was ce.) for example, the Web server adopts Tomcat, the EJB server adopts Apache OpenEJB, and the JMS message service uses ActiveMQ, implement the various features required in the JSR-244 (Java EE 5) specification.

It is also worth mentioning that for the dependency management of Geronimo, a module on the server should work normally. First, the other modules on which it depends must be started properly, the Geronimo Plugin dependency is defined in the geronimo-plugin.xml. Taking WASCE Plugins, Welcome: Tomcat as an example, one of the dependent Geronimo Plugins is defined in the geronimo-plugin.xml in the following form:

Configuration 1. geronimo-plugin.xml

Org. apache. geronimo. configs
Tomcat6
2.1.4
Car

That is to say, the WASCE Plugins, Welcome: Tomcat Plugin should work normally. the Plugin corresponding to the module org. apache. geronimo. configs/tomcat6/2.1.4/car must also exist.

The server customization function of was ce is implemented based on the above Geronimo architecture and dependency management. In was ce, any module in the form of plugin can be assembled by customizing the server. to ensure that the server can run and start properly, the Geronimo kernel is essential, the plugin corresponding to the was ce server is WASCE Assemblies: Boilerplate Minimal. All these plug-ins exist in the was ce plugin repository (that is, the repository directory under the was ce installation path. During the assembly process of the custom server, when a plugin is extracted from the was ce plugin repository, other plugins on which it depends will also be extracted, together, the plug-in is assembled into a custom server to ensure that the plug-in can run properly with the support of the Geronimo kernel.

The following sections describe how to customize servers, how to customize servers, and how to expand the functions of custom servers.

[1] [2] [3] [4] [5] [6] [7] [8] Next page