Right-click the controller icon for which you want to create an MQAcq application. Select New | MQAcq. The new MQAcq, named MQAcq1, appears below the selected controller and in the right pane.
Double-click MQAcq1 in the right pane or right-click MQAcq1 in the tree view and select Properties. The MQAcq Properties window appears.
Complete these fields on the General tab to define the MQAcq application:
Active – select this option to enable the application.
Tracking – automatically set the working directory identical to the name of the MQAcq.
Name – the system defines this field as MQAcqn, indicating an MQAcq application and its associated instance. You can modify this name to be consistent within your own environment.
Working Directory – unselect Tracking to enable the Working Directory text box and enter the working directory or accept the default, which matches the ODL application name. This directory tells the e-Biz Impact executable where to find the configuration information for this ODL application once the configuration files are deployed to the server.
Project – enter the path and file name of the AIM project files generated by MSG-IDE that are associated with this AIM.
Command Line – enter any optional parameters into your MQAcq application. These arguments can be accessed by the MQAcq application by using clGetArgc() and clGetArgv().
Log Limit (KB) – defines the log file limit. There is no predefined limit, but the default setting of 1024 (1MB) provides a useful log file without using too much disk space.
Depth – the number of copies of the log file that e-Biz Impact maintains. The default setting of 2 indicates that e-Biz Impact creates an additional file when the main activity log reaches its maximum size. If the second file reaches the limit, e-Biz Impact rolls back to the first file, overwriting the content.
Complete these fields to define route information:
Route Type – select how transactions are submitted to the router. Select:
Route – to route a transaction using route_vrec, which sends the transaction directly to the MQDel AIM, or through all production objects currently available to the router.
Prod – to route a transaction using route_vprod, which sends a transaction to the router application and through a single production object.
Engine – to route a transaction using route_veng, which sends a transaction to the router application for routing to the MQDel AIM, or through a specific production object, or through all the production objects currently available to the router application
Router Flavor – identify the flavor of the router that will handle transactions acquired by this application.
Source Name – identify the source from which to accept the transaction.
Route Name – identify the transaction ID. The default is ENGINE. This is the engine defined to hold all production objects used for this transaction.
Identify the number of instances of this MQAcq application that may be run within this cluster.
Click Apply to save the entries.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
