e-Biz Impact applications are controller components. e-Biz Impact applications include:
Store and Forward Manager (SFM) User-developed applications that receive transactions from an acquisition AIM, store the transactions, perform various types of optional processing, then forward the transactions to a final destination in a form expected by the endpoint application.
See the e-Biz Impact TRAN-IDE Guide for instructions on developing SFM applications.
ODL AIMs User-developed applications that handle message-level data traffic between endpoint applications and e-Biz Impact. e-Biz Impact-provides the MSG-IDE tool for you to develop Object Definition Language (ODL) acquisition and delivery AIMs.
See the e-Biz Impact MSG-IDE Guide for instructions on developing ODL acquisition and delivery AIMs.
Java User-developed Java applications that handle message-level data traffic between endpoint applications and e-Biz Impact. See the e-Biz Impact Configuration Guide for instructions on configuring Java AIMs.
Before or after you configure a Java AIM, you must create the actual Java application plug-in code. See Java Support for e-Biz Impact for instructions.
Custom User-developed C\C++ applications that handle message-level data traffic between endpoint applications and e-Biz Impact. See Chapter 2, “Developing Custom Applications.”
Multisrv Applications that work with ODL to support multiple simultaneous connections on a single socket.
See the e-Biz Impact Configuration Guide for instructions on implementing Multisrv applications.
Dfcsrv Applications that communicate with applications running under a different cluster.
See the e-Biz Impact Configuration Guide for instructions on implementing Dfcsrv applications.
Router SFM applications running in “router only” mode that move transactions to and from WebSphere MQ messaging queues. MQAcq and MQDel applications work with router applications, rather than an SFM, to route messages. No log file maintenance is provided and the router is responsible only for synchronous routing of messages. See the e-Biz Impact Configuration Guide for instructions on configuring routers.
MQAcq and MQDel WebSphere MQ messaging queue acquisition and delivery AIMs. See Chapter 3, “Accessing WebSphere MQ Data.”
Each application has a configuration file <cluster_name>.<application_name>.cfg. In addition, each AIM and SFM has its own project file <project_name>.prj.
The remainder of this guide provides more detailed information about developing custom C\C++ applications and how to access IBM WebSphere MQ series messages from queues for use with e-Biz Impact.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
