HPOS 3.5 SAP - Configuring "Tasking Target" & "Target for Callback" fields

HP Output Server 3.5 1
Technical Note
Configuring the Tasking Target and
Target for Callback Fields in the SAP R/3
Spool System
This technical note provides information about configuring the Tasking target and Target for callback fields while
creating logical output management systems (LOMS). Configuring these fields facilitates receiving job delivery
notifications from HP Output Server at the correct SAP R/3 spool destination.
SAP BC-XOM is a generic interface to the R/3 spool system for external output management system (OMS), such as
HP Output Server. The output management system facilitates communication between BC-XOM and HP Output
Server.
HP Output Server is composed of two parts:
• The sending part, which resides on the R/3 host, is a set of scripts that enables R/3 users to deliver, monitor, and
control jobs sent to devices that HP Output Server manages.
• The receiving part, which resides on the HP Output Server host, is dzl_callbackd, the OMS callback. It
receives R/3 job and device notices from HP Output Server and routes these notices to R/3. The dzl_monitor
program restarts the OMS callback if it fails.
The LOMSes identify the callback target and the tasking target. One or more LOMSes need to be defined. A tasking
target is the R/3 spool server that delivers jobs. A callback target is the R/3 instance that receives callback messages.
Both tasking target and callback target need not reside on the same R/3 host.
When a job is sent through the R/3 spool system to HP Output Server for execution, HP Output Server sends across
the notifications on events, such as receipt of job and job completion. This notification reaches the R/3 spool system
through the BC-XOM generic interface present in the OMS. At this point, the OMS checks for the SAP system ID of
the particular callback target, which is set during creation of LOMS. The notification reaches the particular
destination specified in the callback target field.
Problem
During setup if the database Copy option is used to populate the LOMS and the real OMS (ROMS) in the R/3 spool
system, and if the unmodified Tasking target field and/or Target for callback field are retained, then OMS tries to
connect to a different R/3 spool system. Due to this, the notification gets delivered to some other R/3 spool system
instead of the correct spool system.