SAP Logical OMS & Commands Configuration
- Date: Nov 03, 2015
SAP Logical OMS & Commands Configuration3 Nov, 2015
To use SAP BC-XOM, at least one LOMS to be defined. LOMS definitions support the two types of interfaces – polling or callback. (Callback, if available, is preferred due to its lower overhead and greater customization potential).
1. From the SPAD Initial Screen, click on the Output Management Systems tab, then the Logical Output Management Systems Display button.
2. To define a new LOMS, click on the Create button. (Or double click on an existing LOMS entry to modify it.) This will bring up the LOMS definition screen.
Configuring a Polling LOMS:
Set the Logical OMS Name and Description as desired.
1. Select the OM Plus ROMS as the Real OMS.
2. Set a Command group letter to share a single set of command definitions (as defined below) across multiple LOMS definitions. All LOMS should reference this letter. Otherwise, leave the field blank. Enter the command definitions for each LOMS separately.
3. Select ‘Polling’ under the Jobs section.
4. If the ‘No info = error’ checkbox in the Jobs section is not visible, click on the ‘Extended config’ button. Clear the ‘No info = error’ checkbox. (This prevents SAP from marking output requests in error if OM Plus does not respond to a status poll in a timely manner. This could happen due to network errors.)
5. Status Dialog boxes may be set as desired.
6. The entries on the OMS configuration tab should be left blank.
Configuring a Callback LOMS:
1. Select the SAP configuration tab.
2. Set the Logical OMS Name and Description as desired.
3. Select the OM Plus ROMS as the Real OMS.
4. Select ‘Callback’ under the Jobs section. This should cause additional field(s) to display.
5. Enter the desired SAP instance in the Target for callback field.
6. Set a Command group letter to share a single set of command definitions (as defined below) across multiple LOMS definitions. All LOMS should reference this letter. Otherwise, leave the field blank. Enter the command definitions for each LOMS separately.
7. Set ‘Event report level’ to the desired level of reporting. (See text below.)
8. Select Devices/Queue query and Jobs/Query and Jobs/Can be deleted if it is desired to make these functions available for this LOMS in the SAP user interface. The query options will cause a Tasking Target to be requested. Enter the desired SAP server instance.
9. Status Dialog boxes may be set as desired.
10. Select the OMS configuration tab.
11. Set Send Period to the maximum interval that OM Plus should accumulate status events for before returning them to the SAP callback target. (see below)
12. Set Number of Events to the number of status events that can be allowed to accumulate before OM Plus returns status earlier than the Send Period. (see below)
13. Set the Callback Restart Interval to the number of seconds OM Plus should wait before retrying a failed callback target.
14. Attribute Record and OMS Configuration should be left blank for future use.
The settings of Event report level, Send Period and Number of Events can have major impact on speed of update and overhead in SAP and OM Plus. An OM Plus node periodically scans for ready events at the Send Period interval of any LOMS which are accessing it. If multiple LOMS are accessing an OM Plus node, scans may occur more frequently to accommodate the requested timing of each LOMS. The scan interval is limited to a minimum of 5 seconds and a maximum of 30 seconds. When a request or its associated destination changes status, this event is filtered by Event report level. If the event is at or above the reporting threshold, it is counted as ready. When a scan occurs, the event is reported to SAP if the Send Period has elapsed or the Number of Events has been reached.
The following describes the mapping of OM Plus request and destination status changes to SAP Event reporting level. Each successive reporting level allows additional triggering events for status callbacks to SAP, providing increased visibility for SAP users. The level of detail available for this processing depends on the configuration of the OM Plus destination. Maximum detail is provided by destinations configured in termserv mode, with SNMP and Bidirectional PJL protocols enabled.
SAP is only notified when a request completes successfully or is canceled. This setting (along with a Send Period of a minute or two) is appropriate when request and destination status is to be monitored solely in OM Plus and SAP needs no progress reporting, beyond a completion notification.
ALSO PROBLEMS (INTERACTION REQUIRED)
Adds conditions, such as Offline, where request processing generally cannot continue without some form or intervention in OM Plus or at the printer.
As of OM PLUS 2.4.0, this has no additional effect because SAP does not act sufficiently differentiate between Problem and Warning conditions and, in many cases, OM Plus cannot tell if a problem does or does not require intervention.
ALSO STATUS CHANGES
Adds request status transitions such as “ready” to “activ” and “Retry” conditions.
Adds changes in destination status.
ALL AVAILABLE INFORMATION
Adds confirmed (PJL) page count change.
Sap Logical OMS & Commands Configuration (Continued)
3. Save the LOMS definition. The above steps may be repeated to define multiple LOMS if desired.
4. From either a LOMS definition or the List of LOMS screen, Select the Commands
button. Select the entry corresponding to your system’s Operating System. (All Windows systems are considered to be ‘Windows NT’.)
5. Enter (or verify/correct) the OS Commands fields:
Set a Command group letter to share this set of command definitions across multiple LOMS definitions. All LOMS should reference this letter. (Otherwise, enter the command definitions for each LOMS separately.)
a. Operating system should be that of the current OS.
b. Enter the fully qualified path to the OM Plus bin directory in the command path. The defaults paths for Unix-based and Windows systems are:
c. Enter the dccsapsub command as shown below into the Submit line:
dccsapsub “&EI” &EG &P &F &o “&T” &C &Y &U “&E2” “&Es” “&E1”
(It is harmless to use quotes around all parameters. The ones shown are required.) The “&E1” parameter is new as of OM Plus release 2.3.2. It is required for callback, allowing dccsapsub to distinguish between polling and callback mode requests. If absent, polling will be assumed.
d. Enter the dccsapstat commands shown below into the remaining lines:
Polling: dccsapstat &P &EL
Queue query: dccsapstat -d &P
Job cancel: dccsapstat -c &EL
Job query: dccsapstat -j &EL
e. Save the Commands.