Understanding Dynamic Prompting Support - Lexmark C792 Manual

Developing workflow solutions
•
The LDD system is online.
You can access the interface of the Job Sumbission Web Service at http://loadbalancer:
9780/lmc/services/JobSubmission?wsdl, where loadbalancer is the computer where your load
balancer is installed.
The following table lists the methods used with the Job Submission Web Service:
Method Target
Load
start
balancer
WebDAV
post
metadata LDD
Server

Understanding dynamic prompting support

When a profile is selected, solutions usually either prompt you for information or start a job. Many solutions involve
submitting jobs with related information (such as account numbers, passwords, or processing options) that is obtained
through prompting. Where possible, prompting should occur before submitting the job. This gives you the opportunity
to cancel jobs when prompted for information they don't have at the moment.
The Job Submission Web Service provides prompting capability to Lexmark Document Server Printer Port clients. From
the port monitor, the following prompts are supported:
•
MessagePrompt
•
BooleanPrompt
•
IntegerPrompt
•
ListPrompt
•
ArrayPrompt
•
PasswordPrompt
Description Parameters
Initiate a job
•
resolver—The resolver used to determine
submission
the device group, solution, and task settings.
session
The default resolver uses clientIP and
profileName only.
• protocol—The protocol used to extract
prompt answers from the metadata. The
default is webdav.
• authId—The client user name
•
clientIP—The client IP address
•
deviceGroup—The device group
associated with the job
•
profileName—The profile used for the job
Submit files in See the WebDAV documentation.
response to
ScanPrompt
Provide answers
• continue—Indicates more metadata
for other prompts
follows
•
scan.x.file.y—The path of a scanned
file in the WebDAV repository. x indicates the
sequence number of a scan prompt, and y
indicates the sequence number of a file from
that scan prompt. x and y are both
zero‑based.
50
Return values
•
sessionID—The
session ID, which must
be used in later calls
•
tomcatIP—The
address of the LDD
server, which must be
the target for later calls
•
scanUrl—The
WebDAV folder where
documents are
submitted
Reserved