1
2
3
I am going to describe
Prerequisites
Design Phase
Runtime
Workflow
4
Prerequisites to implement Java Framework are,
Client Should have R19 AMR or latest release of T24 Transact
JD Product must be installed in the SPF
Design Studio with latest binaries
T24 and TAFJ library jar files
Basic understanding of Java Programming Language
Experience in designing Screen and Enquiry in Design Studio and deploy the same in
T24 Transact along with UXP Browser
5
The field EXTENSIBLE.CUSTOMIZATION in SPF can be set with the values YES/NO.
If the JD product is not installed and the field EXTENSIBLE.CUSTOMIZATION is set to
NO then “Java Customization is not allowed”
If the JD product is installed and the field EXTENSIBLE.CUSTOMIZATION is set to NO
then “JBC and Java Customization is allowed”. This is for Upgrade Clients
If the JD product is installed and the field EXTENSIBLE.CUSTOMIZATION is set to YES
then “Only Java Customization is allowed”
6
Extensibility API framework extends the capabilities from the T24 Transact.
It uses the Temenos Libraries to expose the functionality to the L3 Development.
Third party services can use T24 Libraries and TAFJ libraries to extend the T24
Transact Functionalities
7
APIs are code Temenos has written that L3 developers can call
Hooks are code L3 developers have written that Transact can call
A developer can attach own logic to Transact to be called from core application exits
using HOOKS
Each hook has been provided with methods to carry out the task
8
• At the Design phase, Java Developer will use the Eclipse or Design Studio to create
the java Project.
• Java project will be referenced with the T24 Libraries and TAFJ Libraries
• The Java Class will extend Java API Supplied by T24 libraries and TAFJ Libraries.
• Deployment will be a JAR file. That will be understandable by TAFJ Environment
9
At Runtime, The Java User Exit Hook will call the Invoker.
Invoker will check if you SPF have JD product installed.
If yes, It will check for the field EXTENSIBLE.CUSTOMISATION in SPF, if it is set to YES,
then it will invoke ONLY the Java Method Defined in EB.API. If NO, then it will invoke
either BASIC or JAVA program
If No, Then there is no local development
10
Java Extensibility workflow,
1. Identify the Exit Point field that where do you want to attach your logic. Read the
help text to get EB.API record ID of the core invoker
2. Discover the hook method name to implement. Read the EB.API
3. Read hook method signature and abstract method from the Java document.
4. Implement hook method in java class that extends the method using Design
Studio/Eclipse
11
5. Make an entry in EB.API with the source type as method. Provide hook method
name, class and package name. This can be done using the T24 Browser
6. Link Hook method to exit point field using EB.API. Example: Attach the EB.API id to
the INPUT.ROUTINE Field in Version application
7. Run the T24 Application
12
I described
Prerequisites
Design Phase
Runtime
Workflow
13
14
15
