Drawback of the TAFJJEE_EAR Architecture

This section highlights a drawback of the TAFJEE_EAR approach with an example.

In TAFJJEE_EAR architecture, irrespective of the requirement, all services are deployed and started at application server startup.

For example, all online channels are present by default in a deployment; 18 OFS sources are defined and must be bound to 18 pairs of JMS queues. This would require a significant amount of listeners and resources.

The configuration can also be tedious since it is managed through deployment descriptors within the EAR file. In containerized environment, it means that the application image has to be amended depending on the expected configuration.

The following screen shows the original architecture of TAFJJEE_EAR: