Select the General tab and complete these fields to define the SFM application:
Debug – write more verbose debug information to the SFM xlog. If you select this option, you may want to increase the size of the xlog file on the Logs tab. See “Log Files tab”.
Active – make the SFM active. When the cluster is started, only active applications are started.
Tracking – automatically set the SFM working directory to the name of the SFM.
Name (function) – defined by default as “SFMn” (where “n” increments starting with 1), indicating an SFM application and its associated instance. You can modify this name to be consistent within your own environment.
Flavor (function) – enter an integer between 1 and 4292967295 to use for data routing. The SFM flavor must be unique in the e-Biz Impact cluster.
The combination of function Name and function Flavor
makes a function unique. Flavor allows functions of the same name
to appear more than once, in different applications, which enables
dynamic routing. For example, your code calls foo,
and at runtime, you determine which foo to use
according to the flavor.
Timeout – the time, in seconds, for a calling application to wait before it times out. Timeout relates to all the DFC entry points to an SFM:
route_rec |
route_prod |
route_veng2 |
route_rec2 |
route_vprod |
sfmping |
route_recx |
route_vprod2 |
sfmayt |
route_vrec |
route_veng |
sfmproc |
route_vrec2 |
Serial Dispatch Mode – allow the SFM to serially dispatch transactions based on a transaction’s sequence (the first transaction entered is the first transaction processed; second entered, second processed, and so on). A transaction is processed only when its predecessor has completed processing. This is known as transactionality.
To define transactionality based on productions objects (that is, a transaction must qualify for and be processed by one production object before a subsequent transaction can be qualified and processed), use RO_ SERIALDISPATCH in the route_recx DFC of your acquisition AIM.
WARNING! When an SFM receives a transaction that has a priority set, it ignores serialization options and processes the prioritized transaction first.
Availability – define when the SFM can receive data. This parameter works on all distributed function calls used as entry points by acquisition AIMS such as route_recx, route_rec, and so on.
Select Availability, then in the drop-down box, select Any,
Wk (week), or a day of the week. In the next two boxes, enter the beginning
and ending time in the format hh:mm (hours:minutes),
for example 9:00 to 12:00.
00:00 to 12:00 is AM, and 13:00 to 24:00 is PM.
Click Add to add the availability you defined. Select a time and click Delete to remove that availability. Select a time and click Modify to change an availability. Click Clear to erase the entire availability list.
Complete these fields on the General tab to override the predefined function names of all delivery AIMs for this SFM:
servayt – the name of the function used to ping the delivery AIM. The default is servayt (“server are you there”), but can be any user-defined name.
servproc – the name of the DFC function used by SFM when routing a translated transaction to the delivery AIM. The default is servproc (“server process”), but can be any user-defined name.
Complete these fields on the General tab to configure SFM directories:
Dynamic Table Reload – reload the ODL lookup tables during runtime if changes are made to the table files.
Working – unselect the Tracking option to enable the Working Directory text box and enter the working directory or accept the default, which matches the SFM name. This directory tells the e-Biz Impact executable where to find the configuration information for this SFM once the configuration files are deployed to the server.
All project files (.prj) in this directory will be loaded.
Project – the location where the production object project files reside.
Table – the location of production object tables, if used.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
