General tab

Right-click the controller for which you want to create an MQDel application. Select New | MQDel. The new MQDel, named MQDel1, appears below the selected controller and in the right pane.

Double-click MQDel1 in the right pane or right-click MQAcq1 in the tree view and select Properties. The MQDel Properties window appears.

Select the General tab and complete the following fields to define the MQDel application:

Name – the system defines this field as MQDeln, indicating an MQDel 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 MQDel application name. This directory tells the e-Biz Impact executable where to find the configuration information for this MQDel application once the configuration files are deployed to the server.
Project – specify the location in which the project files reside.
Active – select this option to enable the application.
Command Line – enter any optional parameters into your MQDel application. These arguments can be accessed by the MQDel application using clGetArgc() and clGetArgv().
Log Limit (K) – defines the log file limit. There is no predefined limit, but the default setting of 1024 (1MB) is designed to provide 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.

Identify the minimum and maximum number of instances of this MQDel application that can be run within this cluster.

Configure the Mode, which controls which application (MQAcq, router, or MQDel) is responsible for performing commit and rollback operations on queues.

To allow the source application to perform commit and rollback operations on both input and output queues, select Inline mode for both the router application and the MQDel application to specify that all code execution will be done by the MQAcq AIM thread.

To let the destination application perform commit and rollback operations on output queues, select Queued mode for the MQDel AIM.

Select:

Inline – if the application should not have its own execution thread and should execute within the MQAcq thread. If you select this option, you should also select “Inline” for Mode on the General tab of the Router Properties window.

Inline is the required mode most of the time for MQ AIMs.
Queued – if the application should execute within its own thread and can queue up requests for more than one application.

Configure the WebSphere MQ context ID, queue, and Open Transport ID. This information is in the nnsyreg.dat file used to configure Open Transport.

Context ID – enter the value used to define OTContext.<Context1> in your nnsyreg.dat file. One context ID is allowed per thread.
Transport ID – enter the Open Transport ID associated with the queue name defined in the Queue Name field.
Queue Name – enter the name of the queue in to which MQDel put the transaction.

See Chapter 4, “Accessing WebSphere MQ Data,” in the e-Biz Impact Application Guide, the New Era of Networks Adapter for SAP R/3 3.9 User’s Guide, and the Open Transport documentation located on the e-Biz Impact SyBooks CD that comes with the product.

To configure sync_proc options, see the “DFC tab”.