Management Activities
This section deals with the EJB and system or tafj property for EJB warmup and tSA startup.
Some management activities can be triggered at server startup, based on system, tafj or ejb properties.
EJB Warmup
The EJB warmup is an initialisation process, which occurs at startup when any of the following properties is defined.

TAFJManagementBean EJB is configured in TAFJJEE_EAR.ear\TAFJJEE_EJB.jar META-INF\ejb-jar.xml within the <enterprise-beans> section.
<env-entry> <description>Run ejb warmup to create the specified number of session for the specified ejb at server startup - pattern is EjbName=size with semi-colon separator</description> <env-entry-name>ejbWarmup</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>OFSProcessingBean=0;BROWSERProcessingBean=0</env-entry-value> </env-entry>
The string parameter is used to define a set of EJBs to be initialised at server startup. This parameter must follow the pattern EJBName=size;EJBName=size. For example, if EJBName is the targeted ejb name as seen in the ejb-jar.xml for GCS ofs source channel, the command is:
<ejb-name>OFSProcessingBean</ejb-name>
The size is an integer value representing the number of sessions for the channel to be created. It can also be injected within the configuration following EJB-JAR configuration override instructions.
For example, management.ejbWarmup=OFSProcessingBean=10;BROWSERProcessingBean=5

The temn.tafj.appserver.ejb.warmup property can also be used to define the warmup pattern and will take precedence over the EJB property defined above. It can be set as a system property with the warmup pattern escaped between quotes or as an environment variable or integrated within TAFJ configuration.
-Dtemn.tafj.appserver.ejb.warmup=’OFSProcessingBean=2;BROWSERProcessingBean=3’
tSA Startup
The tSA startup allows sending tSA messages to phantom queue at server startup when any of the following properties is defined.

TAFJManagementBean EJB is configured in TAFJJEE_EAR.ear\TAFJJEE_EJB.jar META-INF\ejb-jar.xml within the <enterprise-beans> section.
<env-entry> <description>Send x tSA messages to EXEC queue at server startup - a String is used to inject null when needed and not override tafj property</description> <env-entry-name>tsaStart</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value></env-entry-value> </env-entry>
The string parameter is used to define number of tSAs to be initialised at server startup. It can also be injected within the configuration following EJB-JAR configuration override instructions.
For example, management.tsaStart=10

The temn.tafj.appserver.start.tsa property can be used to define the number of tSA messages to be sent for processing at server startup which will take precedence over the EJB property defined above.
It can be set as a system property, environment variable or integrated within TAFJ configuration.
-Dtemn.tafj.start.tsa=5
In this topic