[Viken Ohannessian]

If this is a simple http interface (no soap, no SSL), you can use the http-client protocol along with the httpQuery TPS proc supplied with cloverleaf.

Turn on “await replies” and set a time out, the proc has built in logic to use those keys out of the NetConfig.

The reply from the post will get passed back to the engine via the Inbound-Reply stack. You can use the recover33 procs, you may have to modify the IB-reply proc depending on how the reply is formatted.

[Viken Ohannessian]

I would suggest give it a try. We’ve successfully installed 5.6 on the latest versions of fedora and ubuntu. The only trick was to install tcsh from each dispos repository.

With that said, the client version is only officially supported on windows 🙁

[Viken Ohannessian]

You can do this by simply creating a Tcl proc using the tcl editor and just change the CONTINUE statement to OVER. Then place this proc in thread2’s Outbound data TPS. Then you’ll have to create a route from thread2 to thread3 which i assume you already have.

The OVER disposition will take the messages from the outbound data queue and place them in the opposite queue which in this case is the inbound data queue.

But why would you be using 3 threads in the first place?

[Author]

Replies