3.3.1 Configuration of an application and the access points

(1) Application consisting of servlets and JSPs

The servlets and JSPs are components for dynamic generation of the presentation displayed on the Web browser of a client machine. They are accessed from the Web browser (that acts as a client) through the Web server using HTTP or HTTPS protocols.

In an application consisting of servlets and JSPs, servlets or JSPs deployed in the front form the access point components as seen from the client side.

The following figure shows an application consisting of servlets and JSPs:

Figure 3‒8: Application consisting of servlets and JSPs

Note: For other legend items, see 3.2 Description of the system configuration.

Other components, such as JavaBeans and Java class, can be invoked from servlets or JSPs. Session Beans and Entity Beans can also be invoked. In such cases also, servlets or JSPs deployed in the front form the access point components as seen from the client side.

Figure 3‒9: Access points when other components are invoked from servlets and JSPs

Note: For other legend items, see 3.2 Description of the system configuration.

This application mainly runs on the Web front-end system.

To Page Top

(2) Application consisting of Session Beans and Entity Beans

Session Beans and Entity Beans are components for implementing the business logic. They are accessed from the EJB client by RMI-IIOP. EJB client is a general name for the components used for invoking the Enterprise Bean. These components include the EJB client applications running on the client machine and the servlets, JSPs, Session Beans, Entity Beans, or Message-driven Beans running on another J2EE server.

In an application consisting of Session Beans and Entity Beans, the Session Beans or Entity Beans deployed in the front form the access point components.

The following figure shows an application consisting of Session Beans and Entity Beans:

Figure 3‒10: Application consisting of Session Beans and Entity Beans

Note: For other legend items, see 3.2 Description of the system configuration.

Other components, such as JavaBeans and Java class, can be invoked from the Session Beans or Entity Beans. Other Session Beans and Entity Beans can also be invoked. In such cases also, the Session Beans or Entity Beans deployed in the front form the access point components as seen from the client.

Figure 3‒11: Access points when other components are invoked from the Session Beans or Entity Beans

Note: For other legend items, see 3.2 Description of the system configuration.

This application mainly runs on the back-end system.

To Page Top

(3) Application configured with Message-driven Beans

The Message-driven Beans are components for implementing the business logic in a message-driven system. The access can be in any of the following ways:

• Access through Cosminexus JMS provider

• Access through TP1/Message Queue and TP1/Message Queue - Access

• Access through the database (HiRDB or Oracle) and Cosminexus RM

• Access through TP1 inbound integration

In a system configuration with the Message-driven Bean as the access point, you require any one of the following as a resource adapter:

• CJMSP resource adapter^#

• TP1/Message Queue - Access

• Cosminexus RM^#

  Use Cosminexus RM in combination with the DB Connector for Cosminexus RM^#

• TP1 inbound adapter^#

# Resource adapter provided by Application Server.

In the case of an application consisting of Message-driven Beans, the Message-driven Beans form the access point components.

The following figures show an application consisting of Message-driven Beans:

Figure 3‒12: Application configured with Message-driven Bean (through Cosminexus JMS provider)

Note: For other legend items, see 3.2 Description of the system configuration.

Figure 3‒13: Application configured with Message-driven Bean (through TP1/Message Queue - Access)

Note: For other legend items, see 3.2 Description of the system configuration.

Figure 3‒14: Application configured with Message-driven Bean (through Cosminexus RM)

Note: For other legend items, see 3.2 Description of the system configuration.

Figure 3‒15: Application configured with Message-driven Bean (through TP1 inbound integration)

Note: For other legend items, see 3.2 Description of the system configuration.

Other components, such as JavaBeans and Java class, can be invoked from the Message-driven Beans. Session Beans and Entity Beans can also be invoked. In such cases, component that is the access point as seen from the client, is the Message-driven Bean. The following figure shows an example:

Figure 3‒16: Access point when invoking other components from Message-driven Bean (through TP1/Message Queue - Access)

Note: For other legend items, see 3.2 Description of the system configuration.

Figure 3‒17: Access points when other components are called from the Message-driven Beans (through Cosminexus RM)

Note: For other legend items, see 3.2 Description of the system configuration.

This application mainly runs on the back-end system.

To Page Top