xlate through tcl or java api calls?

[Vincent Tran]

In a TCL script or Java class, is it possible to do an Xlate of a message through the api calls?

From what I am reading, the answer seems to be no.

Topic

[garry r fisher]

Why would you want to?

Regards

Garry

[Vincent Tran]

So that the message won’t be queued for translation, then queued again to be sent. Removes a bit of the queuing delay for query type messages where the User is waiting for the response.

[Jim Kosloskey]

Vincent.

I have done Query/Response integrations via Clovleleaf(R) and did not notice any significant depreciation do to the queuing of which you speak.

Of course, we had a properly sized machine and a sensible implementation of the Query/Response paradigm.

Look, you (your employer to be correct) purchased an Integration Engine (a very good one), why in the world would you want to rewrite the essence?

I suspect if you are having performance issues you have an improperly sized platform (or perhaps the worng platform altogether) or the deployment of the Query/Response paradigm is improper.

Thanks,

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[garry r fisher]

Hi,

I agree with Jim:-)

We have a number of query/response interfaces and if they take longer than a second to respond then something is wrong. normally our users presses the button to initiate the search and the response is there before they can blink.

What problems (if any) are you experiencing with q/r?

Regards

Garry

[Vincent Tran]

Thanks for the advise, but I am just prototyping and brainstorming ideas regarding query response. So I don’t have any problems yet.

I was also thinking that if the xlate could be called through the API’s, I could use Cloverleaf to write Xlate’s for stand-alone translation applications.

[Vincent Tran]

Okay, so one of my prototypes involves a query response using a web service.

It takes about 1.25 seconds to call the web service through a Java UPOC. This places the results in memory so it can be read using a Read Java UPOC. Since the minimal time for a Read upoc is 1 second, it averages around 0.5 seconds to read the results. The queuing of messages in Cloverleaf adds another 1 to 2 seconds.

I’m trying to shorting the response time as much as possible, since one of the target query response times is three seconds (which may be impossible ~_~).

Currently I have an inbound and outbound thread. Perhaps since web service results come right after a method call, I can just use one inbound thread. After the xlate, I can call a post tps and do the web service query. Is it possible to place a message on the message queue to be sent back to the inbound client, even though your TPS code is being called on the thread outbound?

[Author]

Replies