Upload
magda
View
223
Download
7
Tags:
Embed Size (px)
DESCRIPTION
Streamserve 5.6.1 Vista Plus Ouptut Manager Integration. Karim El Cheikh Product Manager. Oct 2013. What Does VPOM Do?. Pain. Solution. Feature. Lost Jobs Distributed Environment High # of helpdesk calls. Ensure Delivery Central Control and Management - PowerPoint PPT Presentation
Citation preview
Copyright © OpenText Corporation. All rights reserved.
Streamserve 5.6.1 Vista Plus Ouptut Manager IntegrationKarim El Cheikh Product Manager
Oct 2013
2
What Does VPOM Do?
Lost Jobs
Distributed Environment
High # of helpdesk calls
PainEnsure Delivery
Central Control and Management
Optimize Efficiency and Increase Productivity
Track/Notification & Failover
Enterprise Control Station
Load-balance, notification, best device for job
Solution Feature
3
Vista Plus Output ManagerMerge, Convert, Deliver, Route
VPOM Mail/Fax/Web ServerApplications , i.e StreamServe
Convert/Merge
PDF, HTML, Tiff etc
PCL, Postscript etc
PDF, HTML, Tiff etc
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
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
6
Output Manager Process
VPOM WS
WS notification
WS branded to VPOM
StreamServe VPOM integration5.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 theoptions 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 DictionaryCreated: 2013-9-12, 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, Email, 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