Difference between TAFJJEE_EAR and Micro EE Deployment

This section describes the differences between TAFJJEE_EAR and Micro EE deployment.

Separated Artifacts

The deployable artifacts are available in the $TAFJ_HOME/appserver path within the micro sub-folder.

The minimal artifact to deploy in replacement of TAFJJEE_EAR.ear is TAFJJEE_Micro.jar (less than 100 KB JAR file).

No Deployment Descriptors

The application configuration is achieved through environment variables. There is no deployment descriptor anymore to edit in order to setup the appropriate OFS source and other parameters.

The minimal jboss-ejb3.xml is simply used to define specific “activation config” parameters to connect to a different broker than ActiveMQ.

All MDBs or EJBs parameters that are available in TAFJJEE_EAR are available either through:

• Environment variables
• System properties
• TAFJ configuration (database)

JMS Resources

In comparison with TAFJJEE_EAR, you need a bit of JMS configuration to deploy the Micro EE application. Each deployment defines the following generic JMS resources, which are bound at runtime to common or specific ActiveMQ resources:

• java:/queue/t24OnlineQueue -> is bound to specific Queue
• java:/queue/t24OnlineReplyQueue -> is bound to specific Queue
• java:/queue/t24EXECQueue -> is bound to common Queue
• java:/topic/t24ManagementTopic -> is bound to common Topic

In case of requirement of additional resources, the required resources can be added to the CLI script.

Shared Phantom Queue

A local “Exec queue” per deployment for Phantom processing is no longer required. The phantom queue can be shared across all instances by defining a message selector.

A unique ID per server can be assigned to the phantom_selector environment variable. This variable will be used at server startup to define a unique message selector for the PhantomListener (MDB).

When sending a message to the shared Exec queue containing a PhantomSelector JMS property, the listener with the corresponding phantom_selector message filter will treat the message.

In case of message with no PhantomSelector, any of the registered PhantomListener will consume the message.

When the environment defines a phantom_selector environment variable, any services targeting the Exec queue will set it as a JMS message property to ensure processing on same server instance.

Additional Module

Besides the usual global modules for Temenos Transact and TAFJ libraries, an additional module org.primefaces needs to be defined in case if JSF support is required when deploying the following artifacts:

• TAFJEE.war
• TAFJConfiguration.war
• TAFJTECMonitor.war
• TAFJCobMonitor.war

This module definition is part of the CLI scripts. The primefaces library is shared with the TAFJ_HOME/appserver/micro folder.