WORKLOAD.PROFILE refers to the number of agents that can be allocated to perform a job in the TSA.SERVICE.
The whole idea behind a service is that there will be multiple copies of the process running so that the load can be shared. How many such copies do you want running? That is defined in the field WORK PROFILE. This field holds the ID of the record in the TSA.WORKLOAD.PROFILE application, which specifies the number of copies (agents) that will actually execute.
Time Settings Linked with WORKLOAD.PROFILE
REVIEW TIME:
The job of the tSM (Task Service Manager) is to:
Read the TSA.SERVICE records where the SERVICE.CONTROL field is set to "START."
Read the relevant TSA.WORKLOAD.PROFILE records.
Check if the required number of agents are running.
If the required number of agents are running: Verify that they are performing their tasks.
If the required number of agents are not running: Instruct the user to start the required number of agents.
TIME OUT:
Every agent (tSA) must update the tSM to confirm that it is actively performing its assigned task.
The tSM waits for a stipulated amount of time for each agent to report that it is alive and working.
If the tSM does not receive a reply from an agent within the stipulated time, it considers the agent "dead."
The tSM will then stop the tSA process at the operating system level (kill the process) and start a substitute process.
The time given for every agent to report to the tSM is set in the field TIME.OUT (Specify the value in the COB record).
Working of the Service and WORKLOAD.PROFILE
The Description field holds the text that describes the TSA.SERVICE record.The Server Name field holds the IP address or hostname of the server where this tSM service needs to execute.
There can be only one tSM per T24 application server.
When the MS (Multi-Server) product is installed, this field can be multi-valued to include the IPs of all servers involved in running COB.
The Work Profile field holds the TSA ID in the TSA.WORKLOAD.PROFILE application, which defines the number of agents required to run this service.
For the record tSM, the number of agents should always be 1.
This field forms a multivalue set along with the Description and Server Name fields.
The User field holds a valid T24 username.
For the record tSM, this field has no significance.
For the record COB, it has significance.
Service Control:
This field controls the starting and stopping of the service.
If set to "START," T24 allows you to start the tSM by issuing the command START.TSM.
To stop the tSM, set this field to "STOP."
TSA.WORKLOAD.PROFILE
This application specifies the number of agents required. The number of agents in TSA.WORKLOAD.PROFILE can be set based on time.
For example:
Assume that the server will be busy at 11 PM due to incoming transactions from an interface.
You may choose to reduce the number of agents running COB during that period so that the server resources can be allocated to the interface.
This configuration can be defined in the TSA.WORKLOAD.PROFILE application.
The TSA.WORKLOAD.PROFILE application defines the number of tSAs required.
The ID of a record in this application can be any alphanumeric text.
TIME and AGENTS.REQUIRED:
These fields form an associated multivalue set that specifies the specific time and the number of agents required at that time.
The number of agents running on a server is directly proportional to the number of processors available.
While T24 supports multithreaded services, starting an excessive number of tSAs in the background can overload the server.
Thumb Rule: A maximum of 2 tSAs per processor is recommended.
TSA.PARAMETER
The parameter file has only one record, with the ID set to "SYSTEM."
Review Time:
This value is used if the REVIEW.TIME field in the TSA.SERVICE record is not specified.
The default value is 60 seconds.
Death Watch:
This value is used if the TIME.OUT field in the TSA.SERVICE record is not specified.
The default value is 300 seconds.
Highest Agent:
This is not an input field. It is updated by T24 with the total number of agents running on all T24 application servers.
Our team is there to provide T24 technical and functional trainings or optimize your core banking systems for speed and optimal throughput. Just reach out, we are there to help you.
Keep up the great work! Happy Performance Engineering!
#CoreBanking #T24 #TSAAgents #SystemManagement
Comments