1.1.1 Functionality as an application execution platform
This functionality works as a platform for executing online businesses and batch businesses implemented as the applications. You choose functionality that you want to use according to the intended use of a system and your requirements.
You must determine whether you want to use functionality that serves as the execution platform for the applications, even before you perform the system building or application development.
The following are the classification-wise descriptions of functionality that serve as the application execution platform:
- Organization of this subsection
(1) Basic functionality to operate applications (basic development functions)
This functionality includes the basic functionality for operating applications (J2EE applications). This functionality is mainly the J2EE server functionality.
Application Server provides a J2EE server that supports Java EE 7. The J2EE server provides functionality that is compliant with the standard specifications and is independent of Application Server.
The basic development functionality can be further classified into three types according to the types of the J2EE applications for which you use functionality. The manuals for Application Server function guide have been separated according to this classification.
The following is an overview of each classification:
-
Functionality for executing the Web applications (Web containers)
This classification includes the Web container functionality that serves as the execution platform for Web applications and functionality executed by linking the Web containers and the Web servers.
-
Functionality for executing the Enterprise Bean (EJB containers)
This classification includes the EJB container functionality that serves as a platform for executing Enterprise Beans. This classification also includes the EJB client functionality for invoking the Enterprise Beans.
-
Functions used in both Web applications and Enterprise Beans (Container common function)
This classification includes functionality that can be used in the Web applications and the Enterprise Beans running on the Web containers and the EJB containers respectively.
(2) Functionality for developing Web Services
This includes the functionality for the execution and development environment of Web Services.
The following engines are provided with Application Server:
-
JAX-WS engine that binds the SOAP messages in accordance with the JAX-WS specifications
-
JAX-RS engine that binds the RESTful HTTP messages in accordance with the JAX-RS specifications
(3) Application Server independent functionality extended for improving reliability and performance (expansion functionality)
This includes the functionality extended independently on Application Server. This also includes the functionality implemented by using non-J2EE server processes such as batch server, CTM, and database.
On Application Server, various functionality are extended to improve reliability of the system and to implement stable operations. Furthermore, functionality is also extended to operate applications other than J2EE applications (batch applications) in the Java environment.
(4) Functionality for ensuring the security of a system (security management functionality)
This is the functionality used for ensuring the security of an Application Server-based system. This includes functionality such as the authentication functionality used for preventing unauthorized access and the encryption functionality used for preventing information leakage from communication channels.