client for ICAN/eGate/CAPS/SRE needed? or are there other approaches?
hi *,
from the time i worked with tibco products i am used to haveing adapters on client side. mostly they were a stripped off component of a server side resource adapter (e.g. Batch file, SQL,...). in our company now and then it would make really sense to have such an adapter on e.g. an unix machine that is connected somhow to the EAI for starting any type of followup process s on the receiving machine. another problem is how to connect more than 2000-3000 computers to your system that are in general very stupid.
example:
3000 pcs do have a GUI client software that produces files in various formats. these files should be converted and sent as SQL statements to a central database.
how would you solve this in ICAN/CAPS?
does anyone have already implemented such "thin" clients?
regards chris
# 1
Chris,
The eGate API kit allows you to send messages to a SeeBeyond JMS server (eGate 4.x, SRE, ICAN and JCaps) from other programs. The API kit is available in Java, C, C++ and as an ActiveX component. If you can change the GUI program you could include the eGate API kit to send the message directly to a SeeBeyond message server instead of writing it to file and then picking up the file.
If you cannot change the GUI, you can create a java program that reads the file and sends it to the SeeBeyond message server. This program could be started from the GUI or maybe by the Windows scheduling service. Or you could run the program as a Windows service but then you need either a wrapper to start Java programs as a service (eGate 4.x and SRE use such a wrapper to run the SNMP agent as a service) or write your program in C/C++.
I use this approach to start jobs in JCaps from external schedulers such as cron, $Universe or Control-M.
