1. Streamserve 5.6.1 Vista Plus Ouptut Manager Integration
Karim El Cheikh Product Manager
Oct 2013

2. What Does VPOM Do? Pain Solution Feature Lost Jobs
Distributed Environment
High # of helpdesk calls
Ensure Delivery
Central Control and Management
Optimize Efficiency and Increase Productivity
Track/Notification & Failover
Enterprise Control Station
Load-balance, notification, best device for job
Lost print jobs cost companies enormous amounts of time, money and lost business. User's time is consumed looking for printed output that never reached the intended device, then reprinting the job - taking more physical resources and network bandwidth. If a business document, like a shipping request, purchase order and the like does not reach its intended destination on time, the potential for the loss of a customer and revenue is enormous. Solution:QMaster ensures the delivery of output by monitoring printers to confirm availability, provide failover and automatically route the request to another device, tracking the request from submission to completion.
Distributed Environment:
The challenge for IT to centrally manage output across all managed systems in their enterprise from a single console has been a daunting task. The trends of corporations migrating from mainframe to client/server environments and the advent of distributed low cost laser printers has compounded the need for consistent and centralized control of users, jobs, devices and output.
Solution: QMaster allows IT departments to provide better customer service with a single view and centralized command and control over the entire report distribution environment. Whether ad-hoc or production printing, QMaster provides administrators a consistent view of the information gathered from multiple destination devices including the device and job state, number of jobs in a spool, number of pages in a job and more. With the intelligence of this information, administrators can dynamically track, hold, re-route, prioritize and kill jobs or set these capabilities up for policy-based automation. When problems or potential problems arise, administrators are alerted to the issue and can proactively drill-down to the root cause of the dilemma and fix it.
Help Desk calls
Up to 50% of help desk calls can be related to problems associated with printing. Reducing the inordinate amount of time spend on trouble shooting print related help desk calls, can result into significant cost savings to your organization. Some of these situations could be easily resolved by empowering the end-users to make informed print decisions at the time of job submission.
Solution: QMaster addresses these issues by, allowing users to take proactive control of their output requests throughout the lifecycle of the job, thereby off-loading calls to the helpdesk. QMaster's allows users to view the current status of a device’s availability, such as on or off-line, toner and paper levels and the volume of other jobs in the queue, all from their own desktop. Employees with proper rights can also take action on their output with functionality to re-route, pause and kill jobs, further freeing IT staff to focus on other higher priority issues

3. Vista Plus Output Manager Merge, Convert, Deliver, Route
Convert/Merge
PCL, Postscript etc
PDF, HTML, Tiff etc
PDF, HTML, Tiff etc
Applications , i.e StreamServe
VPOM
Mail/Fax/Web Server
IDP Projects
Control and deliver your corporate information to printers and other destinations across the enterprise.

4. Output Manager High Level Features
Centralized Management of Jobs and Devices
Re-run, re-route, delete, hold
Tracking, Notification and Failover
Forms Management
Bursting and Bundling
Clustering
1-to-many, 1-to-many by page
Interrogate and Apply Rules
Auditing for Chargeback and Trending
At a high level, some of QMaster’s features include:
The Centralized and consistent views of all the jobs and destination devices in your enterprise. The QMaster consoles allow administrators to have complete command and control to re-run, re-route, re-prioritize, delete and hold jobs. Different levels of administration can be set up based upon function and include; global administrators, help desk personnel or departmental and regional administrators.
QMaster ensures delivery of output to its intended destination, whether it’s to a printer, fax or mail server, multi-function device, electronic repository, Archive or other enterprise information management tool. If a device is down, QMaster will automatically re-route the job to the next available device and continue while notifying users and administrators of the new location of their job output.
QMaster also supports Forms Management – with the ability to intelligently and dynamically apply a pre-defined form, such as an invoice, to a job for proper formatting at its final destination.
To further ensure that output is generated in its proper form, the bursting and bundling features allows multiple reports, or sections of reports, to be burst apart and bundled together, eliminating the need to manually rip and decollate reports by hand.
QMaster also supports the clustering of two or more printer devices together so they appear as a single “Super” printer. This increased efficiency and printing power can help reduce your production runs and batch windows significantly by breaking up a single job across multiple printers, or dispersing multiple copy requests of a job to multiple printers.
QMaster’s parsing technology allows you to interrogate the datastream to dynamically apply rules on access, usage, etc. Your business’ policies are automatically enforced based on attributes such as job size and name, device type, user, date, time, etc. This allows QMaster to apply business logic to ensure the correct users and jobs are using the right resource.
Our Auditing capabilities track a user’s device usage. This information can be used for chargeback purposes or tracking which users and departments are utilizing which resources. Additionally, these log files are a good resource for trending purposes, allowing IT to project future usage or re-assign resources to improve Service Levels and the most efficient use of output devices. *

5. Example of Charge Back reports
The logp utility pulls the qme.log information that can be used to get i.e. auditing statistics:
WHO Executed print job ‘ABC123’
WHEN did this print job start
WHEN did this print job finish
HOW many successful records processed
HOW many failed
At a high level, some of QMaster’s features include:
The Centralized and consistent views of all the jobs and destination devices in your enterprise. The QMaster consoles allow administrators to have complete command and control to re-run, re-route, re-prioritize, delete and hold jobs. Different levels of administration can be set up based upon function and include; global administrators, help desk personnel or departmental and regional administrators.
QMaster ensures delivery of output to its intended destination, whether it’s to a printer, fax or mail server, multi-function device, electronic repository, Archive or other enterprise information management tool. If a device is down, QMaster will automatically re-route the job to the next available device and continue while notifying users and administrators of the new location of their job output.
QMaster also supports Forms Management – with the ability to intelligently and dynamically apply a pre-defined form, such as an invoice, to a job for proper formatting at its final destination.
To further ensure that output is generated in its proper form, the bursting and bundling features allows multiple reports, or sections of reports, to be burst apart and bundled together, eliminating the need to manually rip and decollate reports by hand.
QMaster also supports the clustering of two or more printer devices together so they appear as a single “Super” printer. This increased efficiency and printing power can help reduce your production runs and batch windows significantly by breaking up a single job across multiple printers, or dispersing multiple copy requests of a job to multiple printers.
QMaster’s parsing technology allows you to interrogate the datastream to dynamically apply rules on access, usage, etc. Your business’ policies are automatically enforced based on attributes such as job size and name, device type, user, date, time, etc. This allows QMaster to apply business logic to ensure the correct users and jobs are using the right resource.
Our Auditing capabilities track a user’s device usage. This information can be used for chargeback purposes or tracking which users and departments are utilizing which resources. Additionally, these log files are a good resource for trending purposes, allowing IT to project future usage or re-assign resources to improve Service Levels and the most efficient use of output devices. *

6. Output Manager Process
VPOM WS
WS notification WS branded to VPOM

7. StreamServe VPOM integration
5.6.1 GA (earliest at KC July 1st)
5.6.1 Cum. Fix
(Sept 27th )
VPOM 5.5 GA
Release Date planned for End of October (LA available from End of September for Dev/Test)
VPOM Multithreaded Job Submission
WebService support
Authentication
VPOM Job and Device Status Notification WS based on Call Back interface
Be able to delay Strs top job completion after delivery from output connector so that an outside system can set the job to completed
WS Client for job and device notification to the StreamServe notification WS
Device level Notification end points GUI.

8. Job Status Change

9. Device Status Change

10. StreamServe Job Submission
Create Webservice Profile

11. StreamServe Job Submission
Create VPOM connector

12. StreamServe Job Submission
Configure your Output Connector VPOM variables- Corresponds to the options provided by the VPOM server.

13. StreamServe Notification
Configure your Service Request Connector for receiving VPOM notifcations

14. Two New SXD to use in a MessageIN event for mapping all the notification variables
<?xml version="1.0"?>
<!--
StreamServe XML Dictionary
Created: , 17:00:00
-->
<strsdictionary version="2.0" name="VPOMDeviceNotification">
<field id="NotificationSender" fieldlength="0" variable="NotificationSender" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="TopicNamespace" fieldlength="0" variable="TopicNamespace" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="TopicID" fieldlength="0" variable="TopicID" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="ChangeID" fieldlength="0" variable="ChangeID" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="ChangeName" fieldlength="0" variable="ChangeName" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="ChangeValue" fieldlength="0" variable="ChangeValue" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="ChangeOldValue" fieldlength="0" variable="ChangeOldValue" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceName" fieldlength="0" variable="deviceName" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceStatusDescription" fieldlength="0" variable="deviceStatusDescription" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceOwner" fieldlength="0" variable="deviceOwner" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceDescription" fieldlength="0" variable="deviceDescription" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="printerForms" fieldlength="0" variable="printerForms" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="hostName" fieldlength="0" variable="hostName" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="device" fieldlength="0" variable="device" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceClass" fieldlength="0" variable="deviceClass" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceProbeLanguage" fieldlength="0" variable="deviceProbeLanguage" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceProbeInterval" fieldlength="0" variable="deviceProbeInterval" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceStatus" fieldlength="0" variable="deviceStatus" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceProtocol" fieldlength="0" variable="deviceProtocol" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="devicePort" fieldlength="0" variable="devicePort" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceType" fieldlength="0" variable="deviceType" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceProbeEnable" fieldlength="0" variable="deviceProbeEnable" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceAlertLevel" fieldlength="0" variable="deviceAlertLevel" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceProbeReserve" fieldlength="0" variable="deviceProbeReserve" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="deviceAccess" fieldlength="0" variable="deviceAccess" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="maxJobsRunning" fieldlength="0" variable="maxJobsRunning" type="Variable" alignment="Left" keepspaces="FALSE"/>
<field id="jobsScheduled" fieldlength="0" variable="jobsScheduled" type="Variable" alignment="Left" keepspaces="FALSE"/>
</strsdictionary>

15. Enabling VPOM Device Notification
Configure the notification setting for sending device state notifications

16. Delay StreamServe Top Job Completion
Job and Device Event based States sent from VPOM to the StreamServe Notification WS.
JOBPENDING 
JOBHELD 
JOBRUNNING
JOBSTOPPED 
JOBCOMPLETE 
JOBERRORCOMPLETE 
JOBKILLED 
JOBREQUEUE
JOBCONTINUE
JOBRESTART
JOBORPHAN 
JOBREMOVED
JOBSPOOLING 
JOBOFFLINE  
JOBCORRUPT
DEVICEUP 
DEVICEDOWN  
DEVICERESERVED
Job state in Red are set to completed in the StreamServe queue since VPOM will not SEND more JOB state updates for the job

17. Key Benefits of using VPOM versus Output Center
Addtional device support: i.e. Content Server, Vista Plus, , Fax, AFP
Several Probing protocol support i.e. IPP, device native protocol, customized
Simplified WebUI
LDAP support SSO
Advanced and Tailored Worklow Management
Active-Active Cluster Support
No RDBMS / Database Vendor depency
Quick Setup
Burst and Bundle
SAP X-OMS certified
Follow-Me printing customized implementation

18. What’s New in VPOM 5.5
New Operator User Type: intermediate between normal users and queue or device administrators.
New Region Display Option
Single Sign On (SSO) Support
Support for IPP Output Devices
Content Server Integration: new queue type and new commands to send files and metadata about them for capture to Content Server
StreamServe Integration:Using Output Manager’s new Web Service API.

19. What’s New in VPOM 5.5 New Web Service API
Standardized Field Lengths standardized field lengths across all clients so all clients can use the same API calls to the QDB
More Control Over the QWeb Display by setting restrictions on the qweb.ini
Support for New Operating System Versions:RedHat Linux 6.3 and 6.4
New Documents:
The Vista Plus Output Manager QWeb Client User Guide
Installing Vista Plus Output Manager

20. Demo – Job Submission, Notifications & VPOM

21. Karim El-Cheikh – Product Manager kelcheik@opentext.com