T24 Extensibility in Java

Hi,

Do you have any documentation available for development in Java?
My t24 environment does not allow infobasic routines - I am having problems attaching a routine to a version due to EB.API issue. Temenos has confirmed that basic source cannot be used if the JD flag is set to Y in the SPF.
I am using design studio r19 and i am stuck on the flow/steps to follow in order to make my routines work.

Hi
Just curious - what SPF field contains that "JD flag"? Are you able to amend it to allow Basic again?

Hi,

In the SPF file you have a field called Extensible Customisation. This is a Yes / No type of Field.

If set to Yes then it means all your routines should be in JAVA only.
If set to blank or NO or blank then you can have both BASIC and JAVA routines.

Regards,
Kripesh

Hi
Yes I see it in my R19 SPF.. Set to blank. To topic starter: IMHO it's better to set it to blank as well rather than dive into Java :)))

Assuming this cannot be changed (since the client has bought the JD module), is there any material available that could help on how we should write a simple input routine, a nofile enquiry routine or a multi threaded batch routine?

Hi
Have you asked those who sold you that module? I mean Temenos.

I heard about the thing "basic replacement (by Java)" in TAFJ and even tried a sample during a training long time ago but I never seen it working in real life...

I have tried to write Input Routine, Enquiry Routine and NOFILE routine using JAVA and all the 3 worked well during my Training in R19 environment.

Hi
Maybe you can share some examples? Would be interesting to look at...

The JAVA code would be something like this for an Input Routine for Funds Transfer

package com.kripbank;

import com.temenos.api.TField;
import com.temenos.api.TStructure;
import com.temenos.api.TValidationResponse;
import com.temenos.t24.api.hook.system.RecordLifecycle;
import com.temenos.t24.api.records.fundstransfer.FundsTransferRecord;


/*
* to check if the DEBIT and CREDIT CURRENCY are the same
*/

public class FTVersionDemo extends RecordLifecycle {

@Override
public TValidationResponse validateRecord(String application, String recordId, TStructure record,
TStructure lastLiveRecord) {
FundsTransferRecord fr = new FundsTransferRecord(record);
TField f1 = fr.getDebitCurrency();
TField f2 = fr.getCreditCurrency();


if (!f1.getValue().equals(f2.getValue()))
{
f2.setError("CREDIT CURRENCY IS NOT EQUAL TO DEBIT CURRENCY");
}
return fr.getValidationResponse();
}

}


The Code is something like the one above and we need to create EB.API for it and attach it as Input Routine for an FT version.

Sir, I know INFOBASIC but now trying to learn java in temenos t24 but do not have any documentaion or any material regarding that. I'll be really greatfull if you can share some documentation regarding programming in Java in t24.

Hi Kripesh,

this java code is not about using TCS, TCC right ?

is temenos still using tcc, tcs for extensibility java ?
I'm sorry before, but did you have any document about using that ?
currently I'm working on third application to connect into t24 using java

Java Development is bascially for L3 development only. Temenos has developed some superclasses and methods to cater to anyone who wants to write Java code and attach it to Versions, Enquiries, Multi Thread service routines etc which was not possible in earlier releases where writing code had to be necessarily only in jBASE BASIC. This is my understanding.

Hi Kripesh,

Instead of hardcoding the error like
f2.setError("CREDIT CURRENCY IS NOT EQUAL TO DEBIT CURRENCY");

is there an option to use STORE.END.ERROR (as in infobasic to CALL STORE.END.ERROR) ?

I can see the class file is available under the package "com.temenos.t24" as class "com.temenos.t24.STORE_END_ERROR_cl;"

How do we use the class files under the package "com.temenos.t24" ?

Hi Guys,
This is kinda late reply but I was far for quite sometime :)
In fact, we faced the same issue when implementing R19 in production. In fact the MB R19 allows Infobasic code by default, wheras the Production Implementation did not as the SPF had the JD flag set to Yes. So it was an unexpected situation.
As a solution, we have requested a fix from Temenos to revert back that flag to "None" allowing us to use either Infobasic or Java code.
Regaards,

Yes there are options to NOT hard code the Error message and put the Errors in EB.ERROR file and call it inside the Java code.

NO
NO

Akash wrote:

Sir, I know INFOBASIC but now trying to learn java in temenos t24 but do not have any documentaion or any material regarding that. I'll be really greatfull if you can share some documentation regarding programming in Java in t24.
 

This is already available on TCSP portal with sample code and documentation

Great! this is helpful, thanks for sharing.