When you create an acquisition or delivery AIM, you populate it with message interaction objects, then save the application in a project file with a .prj filename extension. The project file is the file that runs the AIM.
You can organize a project in any of three ways:
Have one MSG-IDE project file (.prj) and domain that contains all the objects needed for each AIM. For a simple e-Biz Impact implementation, you would have a project file for the acquisition AIM and a project file for the delivery AIM. This is the simplest organization choice, and should be used whenever possible.
Have one MSG-IDE project file and multiple domains that contain the objects needed for the AIM. Organize the project in this manner when you require some objects to be static and other objects to be global.
Have a MSG-IDE project file with one domain and several child files (.fle), with or without domains, that contain the objects needed for the AIM. Use this method when you have data objects, functions, or other objects that are common to more than one project. This allows you to build the objects once, in a child file, then include the file in each project that requires the common objects.
The components of a message AIM are called message interaction objects. These objects interact with a communication process to gather data from and send data to endpoint applications. Message interaction objects include protocol, communications, message frame, and control flow objects. Supporting objects include data and functions.
e-Biz Impact provide the MSG-IDE tool To develop ODL acquisition and delivery AIMs, use the e-Biz Impact provided
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
