Professional Documents
Culture Documents
R22
TAFJ-CALLJE E
Amendment History:
Revisio
Date Amended Name Description
n
TAFJ Development
2 4th January 2018 Incorporated initial comments
Team
12th November
4 Dhanya J Changes to suppress message number
2019
Page 2
TAFJ-CALLJE E
Copyri g h t
Copyright © Temenos Headquarters SA 2009-2022
All rights reserved.
This document contains proprietary information that is protected by copyright. No part of this document may
be reproduced, transmitted, or made available directly or indirectly to a third party without the express
written agreement of TEMENOS UK Limited. Receipt of this material directly TEMENOS UK Limited
constitutes its express permission to copy. Permission to use or copy this document expressly excludes
modifying it for any purpose, or using it to create a derivative therefrom.
Temenos Headquarters SA
2 Rue de l’Ecole-de-Chimie,
CH - 1205 Geneva,
Switzerland
Please include your name, company, address, and telephone and fax numbers, and email
address if applicable. TAFJdev@temenos.com
Page 3
TAFJ-CALLJE E
Table of Contents
Copyright................................................................................................................................................ 3
Errata and Comments............................................................................................................................ 3
CALLJEE................................................................................................................................................ 5
Function parameters............................................................................................................ 5
jmsDestination................................................................................................................. 5
Message.......................................................................................................................... 5
CALLJEE –Suppress message number in TAFJ....................................................................................8
CALLJEE –timeToLive for JMS messages............................................................................................. 8
Page 4
TAFJ-CALLJE E
CALLJEE
CALLJEE function is used to send message(s) to JMS queue and eventually receive a response
depending on the message type and the options provided to the function.
Syntax:
Limitation:
Fun c t i o n para m e t e r s
jms D e s t i n a t i o n
The jmsDestination is a multi-valued field (@VM separated) which could define up to 3
parameters:
Destination queue – Mandatory parameter defining the queue name to send the
message to.
Reply queue – Optional parameter, defining the queue name to receive messages
from. Required when “SYNC” mode is enabled, refer to message section.
From a JEE naming perspective, JMS resources names could be JNDI names (physical
name) or EJB resource mapped name (logical name).
Me s s a g e
There are 2 message types,
Complex message: Multi-value field message with more than 10 fields (@FM
separated), defines the CALLJEE options and the message(s) to send or receive. A
single CALLJEE call could send multiple messages at a time.
Page 5
TAFJ-CALLJE E
The message type, used as a JMS message type on the queue. This gives the
consumer the opportunity to decide whether it wants to consume this type of
message or not. The consumer receiving a message can use the getJMSType()
method (see class javax.jms.Message) to retrieve the message type.
The function uses this prefix to set the JMS Correlation ID with the following
syntax:
<Correlation ID prefix>_<message number>
SYNC: the function send messages to destination and waits for a reply on the
response queue. See timeout attribute 4. Not suitable in a global transaction
context.
<4> Timeout
A total value in milliseconds specifying how long the function waits for all
messages to be processed.
Each property is added as message string property and can be extracted at receiver
level or act as a message filter criteria.
Page 6
TAFJ-CALLJE E
<8> RESERVED
<9> RESERVED
<10> RESERVED
<11> Message 1
<12> Message 2
<10+n>Message ‘n’
In case of guard queue or RECEIVE mode, the messages attributes <10+n> can be multivalued
attributes, following pattern:
<message>@VM<correlation.id>
Or
@VM<correlation.id>
Examples:
DESTINATION= "queue/t24OFSQueue@VMConnectionFactory"
DESTINATION1 = "queue/t24OFSQueue"
MESSAGE=
”TEXTMESSAGE@FM@FM@FM@FM@FMqueue/t24OFSQueueGuarded@VM20000@F
M@FM@FM@FM@FMENQUIRY.SELECT,,INPUTT/123456,%CURRENCY@VMtestCALLJ
EE_GUARDED_1@FMENQUIRY.SELECT,,INPUTT/654321,%CURRENCY@VMtestCALLJ
EE_GUARDED_2”
Page 7
TAFJ-CALLJE E
CALLJEE –Sup pr e s s m e s s a g e nu m b e r in
TAFJ
In case of jms connectors in Mule ESB, there is a limitation that the incoming message must
have the default correlation ID. The system does not recognise if the correlation ID is altered.
In TAFJ CALLJEE, the correlation IDs are generated with a unique message number suffixed
in case of complex messages. This is in case multiple messages are sent.
To overcome the limitation in Mule ESB where only a single message is sent in the 11th
position of the CALLJEE string, the below property is introduced which when set to true
would suppress the message number and send the correlation ID unaltered.
temn.tafj.runtime.suppress.correlation.message.number=false
Page 8