To configure the properties of an application, right-click the application node and select All Tasks > Configure.
The following configuration option pages are available for each application:
Audit Logging
Use these options to define how activities and transactions are logged to the Audit log:
Log Activities – Select to log the activities of the application.
Log Transactions – Select to log the transactions of the application.
Log Transactions in NOF format – Select to log the transactions of the application with the ispec data values logged as a single string value in the NOF format.
File Path – Specify the location of the log file.
File Size (kb) – Specify the maximum size of the log file.
Number of Backups – Specify the number of backup files that can be created once the log file has reached its maximum size.
Every record written to the audit log (and other log files such as the System.log) contains a standard log record header with the following information:
<date/time> <process> (<process id>:<thread id>) [<user id>]
Where,
<date/time> is in the format YYYY-MM-DD hh:mm:ss.ttt (<ttt> = thousandths of a second).
<process> is the name of the process executing the activity/transaction and is generally dllhost for on-line activities or transactions and “ReportContainer” for report activities.
<process id>:<thread id> is the current process ID and thread ID.
<user id> is the user ID under which the process is running. For online transactions this is generally the client user from which the transaction was submitted. For audit records written from reports, this user ID is always the Application User. For an accurate record of the client users actually performing online and report activities and transactions refer to the user ID as recorded within the audit <event> part of the record as described below.
Activities logging
If the “Log Activities” option is set, events such as user log on or log off and report start or finish is logged. The format of these log messages is:
<standard log record header>; <event>
Where,
<event> can be,
LOGON <domain user id> <#session id> SUCCESS
ISPEC HI USER <domain user id> <#session id>
LOGOFF <domain user id> <#session id>
REPORT START <report name>@<session id> USER <domain user id> LANGUAGE <language name> PA <parameter value>
REPORT FINISH <report name> @<session id>
Transaction Logging
Transaction Logging includes the logging of all on-line system transactions including Ispec transactions and Messenger (XML) transactions.
If the “Log Transactions” option is set, all transactions is logged.
If the “Log Transactions in NOF Format” option is set, all transactions will be logged and Ispec transactions will be logged with the Ispec data as a single string value in the NOF format.
Note: You can only set either of these options if the “Log Activities” option is also set. For Messenger transactions the logged record includes the standard event data (such as user, session) but does not include the actual XML message content.
The format of these log messages is:
<standard log record header>; <event>
Where,
<event> can be:
<direction> <Ispec/Messenger name> USER <domain user id> <#session id> STATION <station name> [<txn data>]
<direction> can be one of the following values:
IN - normal transaction input
OUT - normal transaction output
HUBIN - HUB transaction input
HUBOUT - HUB transaction output
RECEIVE Messenger transaction input
RESPOND Messenger transaction output
<txn data> For an Ispec this consists of the data that is input/output to/from the ispec. This data can be in one of two formats determined by whether the “Log Transactions” or “Log Transactions in NOF Format” option is set.
For a Messenger transaction the format of <txn data> is as follows:
[STATUS = <Status value>] [ERROR (<Error string length>) = <Error string value>]
Where,
<Status value> is one of the following:
‘0’ (success)
‘1’ (error)
‘2’ (invalid session)
‘3’ (invalid Messenger class name)
‘4’ (invalid message format)
‘5’ (invalid message data)
<Error string value> is the text of a returned error message.
<Error string length> is the length of the error message.
If the Messenger response includes more than one error message there will be multiple [ERROR ...] sections.
STATUS and ERROR are only included in the output message; that is, RESPOND.
Log Transactions
This specifies the standard format which consists of a comma separated list of field name/value pairs for all input/output ispec fields, with each in the format:
[<field name> (<data value length>) = <data value>]
The <data value> is masked with the mask definition (* by default) specified in the model (MaskDefinition property) if an attribute has the EnableMaskDefinition configuration property set to true.
This is an example of an input transaction event for the ispec “SalesRep” by the user “UNISYS\Smith”:
IN SalesRep USER UNISYS\Smith #2 STATION UNISYS\Smith [[_ISPEC (8) = SalesRep], [_SOURCE (1) = T], [_TRANNO (6) = 000001], [_INPUT_DATE (7) = 27APR09], [_ACTMTH (4) = 0904], [_UserMAINT (3) = ADD], [SalesRep_Id (2) = S1], [Name (10) = John Smith], [Area (9) = “Australia”], [Return (0) = ]]
Log Transactions in NOF Format
This specifies an alternative format in which the ispec field data is logged as a NOF string. The NOF string value is where all ispec field values are concatenated together into a single string. The format of this NOF string is defined in a “field description” XML file for each ispec. These “field description” files are located in the <System>\Interfaces\ProtocolAdaptors folder for each deployed system.
The <ispec data> part of a NOF format audit log record has this format:
[NOFDATA (<NOF string length>) = <NOF string value>]
The <NOF string value> is a NOF formatted message containing the ispec data. This is a serialized version of the Ispec data with the field data sequenced according to the NOFOrder property value for each attribute.
The <NOF string value> is masked with the mask definition (* by default) specified in the model (MaskDefinition property) if an attribute has the EnableMaskDefinition configuration property set to true.
If an output Ispec message contains a single status line message or a single user/error message, this value is part of the <NOF string value> (appended to the end). However, if the output message includes multiple user/error messages, then these messages are formatted into a separate MESSAGEDATA tag. This will have the format:
[MESSAGEDATA (<Message string length>) = <MESSAGEDATA string value>]
The <MESSAGEDATA string value> consists of all messages formatted as 80 character values appended together.
This is an example of an input transaction event for the ispec “SalesRep” by the user “UNISYS\Smith” that is logged in the NOF format:
IN SalesRep USER UNISYS\Smith #2 STATION UNISYS\Smith [NOFDATA (58) = SREP T00000127APR090904ADDS1 John Smith Australia]
High and Low Account Months
High – Specify the High Account Month for the application.
The High Account Month value prevents the application from accepting any transactions that have a later date (specified by the built-in attribute ActMth). The default value is the year and month that the application was initiated.
Any valid High Account Month value remains in effect until a new one is specified, or until the application date becomes greater than the current value, at which time its value is increased automatically. The High Account Month value is stored in the application database.
Low – Specify the Low Account Month for the application.
The Low Account Month prevents the application from accepting any transactions that have an earlier date (specified by the built-in attribute ActMth). The default value is the year and month that the application was initiated.
Any valid Low Account Month remains in effect until a new one is specified. The value of the Low Account Month is stored in the application database.
Use this page to enable or disable external automatic entries (HUB) for an application.
Before you can enable external automatic entries, the HUB protocol adapter must be running for the current environment.
While HUB is activated, this page displays the statistics on requests sent and received.
Refer to HUB (External Automatic Entries) for more information on how to use HUB.
Use this dialog page to configure print properties required to format the print output for a Report/Outputstream.
These parameters are described in the following table:
| Name | Type | Description | Default Value | Rules |
|---|---|---|---|---|
| | Tab Panel | Used to configure print properties for Reports/Output Streams | N/A | Selecting the Print tab, the drop down lists “View/Change Settings”, for reports and output streams are re-populated to have the latest list of entities which are configured for printing. |
| View/Change Settings for reports | Combo box | Contains all the Reports added to the list for configuring print properties | “All Reports” | The list of Reports will not be pre-populated. The user can add selected reports to the drop-down list by clicking on the “Add Report/Output Stream List” button. This opens up the “Add Report/Output Stream” dialog through which the reports can be added. All Reports and Outputstreams defined in the system are available to be added. You should only add those Reports and Outputstreams for which you need to configure print properties. |
| View/Change Settings for OutputStreams | Combo box | Contains all the OutputStreams added to the list for configuring print properties | “All OutputStreams” | The list of OutputStreams will not be pre-populated. The user can add selected OutputStreams to the drop-down list by clicking on the “Add Report/Output Stream List” button. This opens up the “Add Report/Output Stream” dialog through which the OutputStreams can be added. All Reports and Outputstreams defined in the system are available to be added. You should only add those Reports and Outputstreams for which you need to configure print properties. |
| Add Report/Output Stream List | Button | To add a Report/Output Stream to the list | NA | N/A |
| Delete Report/Output Stream List | Button | To delete a Report/Output Stream from the list | NA | The report/outputstream selected in the “View/Change Settings” combo box for reports and output streams are deleted from the drop-down list and also the configured values for this entity is lost. |
| Use Default | Check box | When checked, the default value for the property is used. The default value indicates the value inherited from up the hierarchy. | Checked | N/A |
| Page Depth | Text box | View or modify the page depth value. This results in the print font size being set such that the defined number of lines fits onto a single page. | 60 | Positive values only are accepted. The value range is 0-9999. |
| Page Width | Text box | View or modify the page width value. This results in the print font size being set such that the defined number of characters fits across the printed page. | 132 | Positive values only are accepted. The value range is 0-9999. |
| Horizontal Margin | Text box | View or modify the horizontal margin value | 0 | The value range is 0-9999. Any value above 25 is rounded off to take the default value, that is, 0. |
| Vertical Margin | Text box | View or modify the vertical margin value | 0 | The value range is 0-9999. Any value above 25 is rounded off to take the default value, that is, 0. |
| Page Orientation: Portrait | Radio button | Sets the page orientation to portrait | Selected | N/A |
| Page Orientation: Landscape | Radio button | Sets the page orientation to landscape. | Not Selected | N/A |
| Font | Combo box | Select the desired font name for printing. The drop-down list shows the font names available on that particular machine. | LincDefault New | The font you select here is used for all the reports. To use a different font for specific reports:
|
| Configure Printer Names | Button | To set the Default Printer name and the EOM Printer name | N/A | On clicking this button, the “Configure Printer Names” Dialog box is opened for configuring the Default Printer name and EOM Printer Name. |
Adding Reports/OutputStream
It is possible to add the set of Reports/OutputStreams existing in an AB Suite application, for which the print property values need to be configured. Use the Add Reports/OutputStream dialog box to add a Report/OutputStream to the existing Report/OutputStream list of Print Properties. You can specify the options listed in the following table, using this Interface.
| Name | Type | Description | Default Value | Rules |
|---|---|---|---|---|
| Report Name | Combo box | Lists all the available reports. The user can select the desired Report by typing the name | All Reports | NA |
| OutputStream Name | List box | Lists all the OutputStreams available within the selected report. Multiple OutputStreams within a report can be selected and added at once. | List of all OutputStreams within the system (All Reports). | NA |
Configuring Printer Names
Use the Configure Printer Names dialog box to specify the name of the Default Printer and the EOM Printer. The User Interface has the two options listed in the following table:
| Name | Type | Description | Default Value | Rules |
|---|---|---|---|---|
| Default Printer | Text box | Accepts the name of a printer to be used as the default printer. No validation for the printer name is performed. In a case where GLB.Station is not set to any value, then the printer configured through this dialog is used as the station for printing. | Empty | NA |
| EOM Printer | Text box | Accepts the EOM printer name. No validation for the printer name is performed. | Empty | This feature of configuring EOM Printer name is currently not implemented and thus the EOM Printer text box is disabled. |
Note: You can delete the configured values for a report/outputstream when they are not required.
The Report page lets you specify the number of times an online report is automatically recovered when a report run failure is encountered.
The Report page lets you specify the number of times an online report is automatically recovered when a report run failure is encountered.
By default, the Allow Automatic Recovery for Online Reports option is enabled.
The Number of Retries option can be set to a value from 1-99, both inclusive.
The Report Session Manager restarts the report automatically for the specified number of retries if a report using automatic recovery terminates unexpectedly. Refer to Recovering Reports for more information about report recovery.
Default Report Print Type
For reports that send output to a printer, this option will determine the behaviour of the print spooling operation.
Synchronous - With this option, the print spooling operation will be included as a synchronous part of the overall report execution. Control will not be returned to the calling script or program until the print spooling operation is complete.
Asynchronous - With this option, the print spooling operation is started as an asynchronous task that runs in parallel with other tasks. At the end of the actual report logic execution an asynchronous task to perform the print spooling is started, and then control is immediately returned to the calling script or program. This allows the calling script to run other reports in parallel with the print spooling.
A situation where 'Asynchronous' printing can be advantageous is where a script executes a series of reports in sequence. In this case, the script is able to run subsequent reports while printing is going on for previous reports in parallel. This can result in the overall elapsed time for the complete series of reports being much less with more tasks running in parallel.