Related Manuals for Novell IDENTITY MANAGER 3.6.1 - MANUAL TASK SERVICE DRIVER
Summary of Contents for Novell IDENTITY MANAGER 3.6.1 - MANUAL TASK SERVICE DRIVER
- Page 1 AUTHORIZED DOCUMENTATION Manual Task Service Driver Implementation Guide Novell ® Identity Manager 3.6.1 June 05, 2009 www.novell.com Identity Manager 3.6 Manual Task Service Driver Implementation Guide...
- Page 2 Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
- Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
- Page 4 Identity Manager 3.6 Manual Task Service Driver Implementation Guide...
-
Page 5: Table Of Contents
Contents About This Guide 1 Overview Modes of Operation ............11 1.1.1 Example: Subscriber Channel E-Mail, Publisher Channel Web Server Response . - Page 6 A.1.9 Name of Certificate (key alias)......... . 33 A.1.10 Certificate Password (key password) .
- Page 7 E.13 <resource> ..............56 E.14 <attachment>...
- Page 8 Identity Manager 3.6 Manual Task Service Driver Implementation Guide...
-
Page 9: About This Guide
For documentation on other Identity Manager drivers, see the Identity Manager Drivers Web site (http://www.novell.com/documentation/idm36drivers/index.html). Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark. - Page 10 Identity Manager 3.6 Manual Task Service Driver Implementation Guide...
-
Page 11: Overview
The e-mail message might simply be notification that something occurred in eDirectory, or it might be a request for data through a method other than the Publisher channel's Web server, such as Novell iManager, another application, or a custom interface. The following sections provide examples for each of these modes: Section 1.1.1, “Example: Subscriber Channel E-Mail, Publisher Channel Web Server... -
Page 12: Example: Subscriber Channel E-Mail, Publisher Channel Web Server Response
1.1.1 Example: Subscriber Channel E-Mail, Publisher Channel Web Server Response The following is an employee provisioning example scenario in which a new employee's manager assigns the employee a room number: 1. A new User object is created in eDirectory (for example, by the Identity Manager driver for the company's HR system). -
Page 13: Templates
Both the Subscriber channel and the Publisher channel of the Manual Task Service driver use templates to create documents. The Subscriber channel creates e-mail messages and the Publisher channel creates Web pages and XDS documents. The dynamic portion of a document is supplied via replacement data. Replacement data on the Subscriber channel is supplied by the Subscriber channel policies, such as the Command Transformation policy. - Page 14 <html xmlns:form="http://www.novell.com/dirxml/manualtask/form"> <head></head> <body> Dear $manager$,<p/> <p> This message is to inform you that your new employee <b>$given-name$ $surname$</b> has been hired. <p> You need to assign a room number for this individual. Click <a href="$url$">Here</a> to do this. </p>...
-
Page 15: Replacement Tokens
value="post_response.xml"/> <input TYPE="hidden" name="auth-style sheet" value="process_template.xsl"/> <input TYPE="hidden" name="auth-template" value="auth_response.xml"/> <input TYPE="hidden" name="protected-data" value="$protected-data$"/> You are:<br/> <form:if-single-item name="responder-dn"> <input TYPE="hidden" name="responder-dn" value="$responder-dn$"/> $responder-dn$ </form:if-single-item> <form:if-multiple-items name="responder-dn"> <form:menu name="responder-dn"/> </ form:if-multiple-items> </td></tr> <tr><td> Enter your password: <br/> <input name="password" TYPE="password" SIZE="20" MAXLENGTH="40"/> </td></tr>... -
Page 16: Replacement Data
HTML elements for HTML forms. The namespace used to qualify the elements is http://www.novell.com/dirxml/manualtask/form. In this document and in the sample templates supplied with the Manual Task Service driver, the prefix used is... -
Page 17: Publisher Channel Web Server
<item name="file">process_template.xsl</item> <url-query> <item name="template">form_template.xml</item> <item name="responder-dn" protect="yes">\PERIN-TAO\big-org\phb</ item> <item name="responder-dn" protect="yes">\PERIN-TAO\big-org\carol</ item> <item name="subject-name">Joe The Intern</item> </url-query> </url-data> </replacement-data> <resource cid="css-1">novdocmain.css</resource> </message> <message mime-type="text/plain"> <stylesheet>process_text_template.xsl</stylesheet> <template>txt_msg_template.xml</template> <replacement-data> <item name="manager">JStanley</item> <item name="given-name">Joe</item> <item name="surname">The Intern</item> <url-data> <item name="file">process_template.xsl</item> <url-query> <item name="template">form_template.xml</item> <item name="responder-dn"... - Page 18 The Publisher channel Web server is normally configured to allow a user to enter data into eDirectory in response to an e-mail that was sent by the Subscriber channel. A typical user interaction with the Web server is as follows: 1.
-
Page 19: Installing Driver Files
Installing Driver Files By default, the Manual Task Service driver files are installed on the Metadirectory server at the same time as the Metadirectory engine. The installation program extends the Identity Vault’s schema and installs both the driver shim and the driver configuration files. It does not create the driver in the Identity Vault (see Chapter 3, “Creating a New Driver,”... - Page 20 Identity Manager 3.6 Manual Task Service Driver Implementation Guide...
-
Page 21: Creating A New Driver
Creating a New Driver After the Manual Task Service driver files are installed on the server where you want to run the driver (see Chapter 2, “Installing Driver Files,” on page 19), you can create the driver in the Identity Vault. -
Page 22: Configuring The Driver
4 On the Import Information Requested page, fill in the following fields: Driver Name: Specify a name that is unique within the driver set. Driver is Local/Remote: Select Local if this driver will run on the Metadirectory server without using the Remote Loader service. Select Remote if you want the driver to use the Remote Loader service, either locally on the Metadirectory server or remotely on another server. -
Page 23: Starting The Driver
Password: Specify the user’s password. 4 Click OK. 5 Read the deployment summary, then click Deploy. 6 Read the message, then click OK. 7 Click Define Security Equivalence to assign rights to the driver. The driver requires rights to objects within the Identity Vault and to the input and output directories on the server. -
Page 24: Importing The Driver Configuration File
3.2.1 Importing the Driver Configuration File 1 In iManager, click to display the Identity Manager Administration page. 2 In the Administration list, click Import Configuration to launch the Import Configuration Wizard. 3 Follow the wizard prompts, filling in the requested information (described below) until you reach the Summary page. - Page 25 Prompt Description Define Security Equivalences The driver requires rights to objects within the Identity Vault. The Admin user object is most often used to supply these rights. However, you might want to create a DriversUser (for example) and assign security equivalence to that user. Whatever rights that the driver needs to have on the server, the DriversUser object must have the same security rights.
-
Page 26: Configuring The Driver Settings
If you created the driver in a driver set that has not been activated, you must activate the driver within 90 days. Otherwise, the driver stops working. For information on activation, refer to “Activating Novell Identity Manager Products” in the Identity Manager 3.6.1 Installation... -
Page 27: Upgrading An Existing Driver
Upgrading an Existing Driver If you are running the driver on the Metadirectory server, the driver shim files are updated when you update the server unless they were not selected during a custom installation. If you are running the driver on another server, the driver shim files are updated when you update the Remote Loader on the server. - Page 28 Identity Manager 3.6 Manual Task Service Driver Implementation Guide...
-
Page 29: Managing The Driver
Managing the Driver As you work with the Manual Task Service driver, there are a variety of management tasks you might need to perform, including the following: Starting and stopping the driver Viewing driver version information Using Named Passwords to securely store passwords associated with the driver Monitoring the driver’s health status Backing up the driver Inspecting the driver’s cache files... - Page 30 Identity Manager 3.6 Manual Task Service Driver Implementation Guide...
-
Page 31: A Driver Settings, Policies, And Templates
Driver Settings, Policies, and Templates Configuring the Manual Task Service driver usually consists of configuring two separate but related subsystems: the Subscriber channel policies and e-mail templates, and the Publisher channel Web server templates and policies. In addition, driver configuration settings such as the SMTP server name and Web server port number must be configured. -
Page 32: Dn Of The Document Base
For example, suppose that the document base DN is specified to be novell\Manual Task Documents and that there is a container under Manual Task Documents named templates. -
Page 33: Http Port
The value specified for HTTP IP address or hostname is used by the Subscriber channel mail handler to construct URLs if the hostname or address is not specified in the mail command element. If the Use HTTP server parameter is set to False, the HTTP IP address or hostname can be used to specify the address or name of a Web server to use in constructing URLs for mail messages. -
Page 34: Certificate Password (Key Password)
A.2.4 Additional Handlers If specified, this is a whitespace-separated list of Java class names. Each class name is a custom class that implements the com.novell.nds.dirxml.driver.manualtask.CommandHandler interface and handles a custom XDS element. The handler for < > is a built-in handler. -
Page 35: Additional Servlets
A.3.1 Additional Servlets If non-blank, this is a whitespace-separated list of Java class names. Each class name is a custom class that extends javax.servlet.http.HttpServer. Custom servlets can be used to extend the functionality of the Publisher channel Web server. Additional information about custom servlets is available in Appendix H, “Custom Servlets for the Publisher Channel,”... -
Page 36: Generating E-Mail Messages
It is important that eDirectory objects to be monitored by the Manual Task Service driver policies have an association for the Manual Task Service driver. Only objects that have an association have Delete, Rename, and Move events reported to the driver. In addition, Modify events on objects that do not have an association are converted to Add events after the Subscriber channel event transformation. -
Page 37: Publisher Channel Policies
The replacement tokens used in an e-mail template dictate the elements that must be <item> supplied as children of the < > element that is constructed by the Subscriber replacement-data channel policy that constructs the < > element. For example, if the e-mail template has the mail replacement token $employee-name$, there must be an <... -
Page 38: Publisher Channel Xds Templates
The Web page template also specified by the URL contains a replacement token $subject-name$. When the Web page template is processed by the style sheet to construct the Web page, the replacement token is replaced by Joe the Intern, which customizes the Web page for the employee whose User object creation caused the e-mail to be sent. -
Page 39: Trace Settings
The Web server then generates an < > replacement data item and an item name="association" < > replacement data item that are used when processing the XDS item name="room-number" template. The XDS document is generated by processing the XDS template with the style sheet specified in the POST data, then the XDS document is submitted to Identity Manager on the Manual Task Service driver's Publisher channel. - Page 40 Identity Manager 3.6 Manual Task Service Driver Implementation Guide...
-
Page 41: B Replacement Data
Replacement Data Replacement data is used with XML documents used as templates to construct e-mail messages, Web pages, and XDS documents. The actual replacement is accomplished by processing the template document with an XSLT style sheet that performs the replacement as part of constructing the output document. -
Page 42: Xml Elements
Web server performs will succeed. However, when the Publisher channel Web server receives the HTTP POST data, it fails to find “\PERIN-TAO\novell\wally” in the encrypted protected data and rejects the POST request. B.2 XML Elements The elements that make up a replacement data document are described below. If no XML attributes are described for an element, then none are allowed. -
Page 43: Replacement-Data
B.2.1 <replacement-data> element can appear in the following locations: <replacement-data> 1. As a child of the element under a Subscriber channel element. <message> <mail> The Manual Task Service driver processes the supplied element into a <replacement-data> standalone element for use in template processing. The following <replacement-data>... - Page 44 The Web server rejects any HTTP POST request that does not contain a responder-dn value and a password value. In addition, if the HTTP POST data does not contain a protected-data item, then the request is rejected. The Subscriber channel supplies one or more <item name=“responder-dn”...
-
Page 45: Url-Data
For the purposes of the Manual Task Service driver, URLs consist of five parts: 1. A scheme such as http, https, or ftp. 2. A host such as www.novell.com or 192.168.0.1. 3. A port number. This is a colon followed by a decimal integer. For example, :80 or :8180. -
Page 46: Url-Query
If the port item does not appear, the URL port defaults to the port on which the Publisher channel Web server is running. B.2.4 <url-query> element is a child of the element. It contains elements that <url-query> <url-data> <item> are used to construct the query portion of the URL used in the e-mail message. Each item that appears as a child of the element is placed in the query string in the <url-query>... -
Page 47: C Automatic Replacement Data Items
Automatic Replacement Data Items The Manual Task Service driver automatically supplies certain replacement data item elements. Section C.1, “Subscriber Channel Automatic Replacement Data,” on page 47 Section C.2, “Publisher Channel Automatic Replacement Data,” on page 47 C.1 Subscriber Channel Automatic Replacement Data The following data items are added automatically to replacement-data documents during processing by the Subscriber channel:... - Page 48 post-status: An element is created and added to the replacement- <item name=“post-status”> data document by the Publisher channel Web server during the processing of an HTTP POST request. An HTTP POST request to the Web server is a request to submit an XDS document to Identity Manager.
-
Page 49: D Template Action Elements
HTML elements for HTML forms. The namespace used to qualify the elements is http://www.novell.com/dirxml/manualtask/form. In this document and in the sample templates supplied with the Manual Task Service driver the prefix used is form. -
Page 50: Form:if-Item-Exists
D.2 <form:if-item-exists> element is used to conditionally insert data into the output <form:if-item-exists> document. The content of is processed only if the specified item appears <form:if-item-exists> in the replacement data. Attributes Name: Specifies the name of the replacement data item. If one or more examples of the replacement data item exist, then the contents of the element are <form:if-item-exists>... -
Page 51: Form:menu
Attributes name: Specifies the name of the replacement data item. If the named item appears exactly once in the replacement data, then the content of the element is processed. <form:if-single-item> Example <form:if-single-item name="responder-dn"> <input TYPE="hidden" name="responder-dn" value="$responder-dn$"/> $responder-dn$ </form:if-single-item> This example inserts an HTML INPUT element and some replacement text into the output document if there is exactly one replacement data item named “responder-dn”... - Page 52 Identity Manager 3.6 Manual Task Service Driver Implementation Guide...
-
Page 53: E
<message mime-type="text/html"> <stylesheet>process_template.xsl</stylesheet> <template>html_msg_template.xml</template> <replacement-data> <item name="manager">Pointy Haired Boss</item> <item name="given-name">Ashok</item> <item name="surname">the Intern</item> <url-data> <item name="file">process_template.xsl</item> <url-query> <item name="template">form_template.xml</item> <item name="responder-dn" protect="yes">\PERIN-TAO\novell\Provo\phb</item> <item name="responder-dn" protect="yes">\PERIN-TAO\novell\Provo\carol</item> <item name="subject-name">Ashok the Intern</item> </url-query> </url-data> </replacement-data> <resource cid="css-1">novdocmain.css</resource> </message> </mail> </input> </nds> Section E.1, “<mail>,” on page 54 Section E.2, “<to>,”...Element -
Page 54: Mail
Section E.12, “<replacement-data>,” on page 55 Section E.13, “<resource>,” on page 56 Section E.14, “<attachment>,” on page 56 E.1 <mail> element and its content describe the data necessary to construct an SMTP message. <mail> <mail> attributes src-dn: Contains the DN value of the eDirectory object that is triggering the e-mail. -
Page 55: Message
E.8 <message> element is a child of the element. Its content is used to construct a message <message> <mail> body for the SMTP message. At least one element is required. Multiple <message> <message> elements can be supplied when constructing an SMTP message with alternative representations of the message body (such as plain text and HTML, or English and another language). -
Page 56: Resource
E.13 <resource> > element is a child of the > element. Its content is treated as the name of <resource <message a file to be incorporated into the SMTP message a resource for the message body. For example, a style sheet for an HTML message body could be supplied as a resource. .css <resource>... -
Page 57: F Data Flow Scenario For A New Employee
Data Flow Scenario for a New Employee This section gives a step-by-step examination of the data flow in an example situation when hiring a new employee causes an e-mail message to be sent to the employee's manager. The e-mail message requests that the manager use a URL in the message to enter a room number value for the employee. - Page 58 3. The following event for the new User object is submitted to the Manual Task Service <add> driver Subscriber channel: <nds dtdversion="1.1" ndsversion="8.6"> <input> <add class-name="User" src-dn="\PERIN-TAO\novell\Provo\Joe" src-entry- id="281002" timestamp="1023314433#2"> <add-attr attr-name="Surname"> <value type="string">the Intern</value> <add-attr> <add-attr attr-name="Given Name"> <value type="string">Joe</value>...
- Page 59 Publisher channel Web server uses these data items when the URL is submitted to the Web server as an HTTP GET request. <replacement-data> <item name="manager">JStanley</item> <item name="given-name">Joe</item> <item name="surname">the Intern</item> <item name="template">form_template.xml</item> <item name="responder-dn">\PERIN-TAO\novell\Provo\phb</item> <item name="responder-dn">\PERIN-TAO\novell\Provo\carol</item> <item name="subject-name">Joe the Intern</item> <item name="association">1671b2:ee4246a561:-7fff:192.168.0.1</item> <item name="url-base">https://192.168.0.1:8180</item> <item name="url-file">process_template.xsl</item> <item name="protected-data">...
- Page 60 The document follows. The replacement tokens are replaced by the html_msg_template.xml value of the corresponding elements in the replacement data document. <item> <html xmlns:form="http://www.novell.com/dirxml/manualtask/form"> <head> </head> <body> <link href="cid:css-1" rel="style sheet" type="text/css"/> <p>...
- Page 61 SoFRkebvh2d5SqalF91ttjRY5lyyW5+/ FifOuDdYikYiDbOJb6607S0dPHjQzeVgu6ptIvGqaEQOEjBjDkY+i4VoVjUSXS3a8fiXB 8moMdPtLJ/GyE8QiwbT4xbkQy48i02k99F2vGmlenRpSP6dD31kZl3dpJ0mGgq2yL/ eFaynKyqnjkHLMexcqD8WlVooaRl1k2RPk5vDYvC8o2bn22OKKbOnSRM5YlPS0iWzxo0J VcnVVyt0AANQQkV0ABBQQkVXaXRoTUQ1QW5kREVT</item> <item name="template">form_template.xml</item> <item name="responder-dn">\PERIN-TAO\novell\Provo\phb</item> <item name="responder-dn">\PERIN-TAO\novell\Provo\carol</item> <item name="subject-name">Joe the Intern</item> <item name="url-base">https://192.168.0.1:8180</item> <item name="url">https://192.168.0.1:8180</item> </replacement-data> The Web server processes the document with the form_templates.xml style sheet. Replacement tokens and action elements are in process_template.xsl...
- Page 62 In addition, there is a replacement token, which retrieves the $query:roomNumber$ current value of the employee's roomNumber attribute (if any). <html xmlns:form="http://www.novell.com/dirxml/manualtask/form"> <head> <title>Enter room number for $subject-name$</title> </head> <body> <link href="novdocmain.css" rel="style sheet" type="text/css"/> <br/><br/><br/><br/> <form class="myform" METHOD="POST" ACTION="$url-base$/ process_template.xsl">...
- Page 63 <input TYPE="hidden" name="protected-data" value="rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA 1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXN BbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHVyAAJbQqzzF/ gGCFTgAgAAeHAAAAAPMA0ECIr9Z1iG+O3BAgEKdXEAfgAEAAAAuMU/ SoFRkebvh2d5SqalF91ttjRY5lyyW5+/ FIfOuDdYikYiDbOJb6607S0dPHjQzeVgu6ptIvGqaEQOEjBjDkY+i4VoVjUSXS3a8fiXB 8moMdPtLJ/GyE8QiwbT4xbkQy48i02k99F2vGmlenRpSP6dD31kZl3dpJ0mGgq2yL/ eFaynKyqnjkHLMexcqD8WlVooaRl1k2RPk5vDYvC8o2bn22OKKbOnSRM5YlPS0iWzxo0J VcnVVyt0AANQQkV0ABBQQkVXaXRoTUQ1QW5kREVT"> Indicate your identity:<br> <SELECT name="responder-dn"> <OPTION selected>\PERIN-TAO\novell\Provo\phb</OPTION> <OPTION>\PERIN-TAO\novell\Provo\carol</OPTION> </SELECT> </td> </tr> <tr> <td> Enter your password: <br> <input name="password" TYPE="password" SIZE="20" MAXLENGTH="40"> </td> </tr> <tr> <td> Enter room number for Joe the Intern:<br>...
- Page 64 SoFRkebvh2d5SqalF91ttjRY5lyyW5+/ FifOuDdYikYiDbOJb6607S0dPHjQzeVgu6ptIvGqaEQOEjBjDkY+i4VoVjUSXS3a8fiXB 8moMdPtLJ/GyE8QiwbT4xbkQy48i02k99F2vGmlenRpSP6dD31kZl3dpJ0mGgq2yL/ eFaynKyqnjkHLMexcqD8WlVooaRl1k2RPk5vDYvC8o2bn22OKKbOnSRM5YlPS0iWzxo0J VcnVVyt0AANQQkV0ABBQQkVXaXRoTUQ1QW5kREVT</item> <item name="responder-dn">\PERIN-TAO\novell\Provo\phb</item> <item name="auth-style sheet">process_template.xsl</item> <item name="response-style sheet">process_template.xsl</item> <item name="subject-name">Joe the Intern</item> <item name="url-base">https://192.168.0.1:8180</item> <item name="url">https://192.168.0.1:8180</item> </replacement-data> e. The Web server verifies that the value of item responder-dn matches a responder-dn value contained in the protected data.
- Page 65 </modify> </input> </nds> j. Identity Manager returns a result document. <nds dtdversion="1.1" ndsversion="8.6"> <source> <product version="2.0">Identity Manager</product> <contact>Novell, Inc.</contact> </source> <output> <status event-id="wfmod" level="success"></status> </output> </nds> k. The Web server adds the replacement data item post-status (and possibly the replacement data item post-status-message) to the replacement data document.
- Page 66 <item name="protected- data">rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1 lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNB bGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHVyAAJbQqzzF/ gGCFTgAgAAeHAAAAAPMA0ECIr9Z1iG+O3BAgEKdXEAfgAEAAAAuMU/ SoFRkebvh2d5SqalF91ttjRY5lyyW5+/ FifOuDdYikYiDbOJb6607S0dPHjQzeVgu6ptIvGqaEQOEjBjDkY+i4VoVjUSXS3a8fiXB 8moMdPtLJ/GyE8QiwbT4xbkQy48i02k99F2vGmlenRpSP6dD31kZl3dpJ0mGgq2yL/ eFaynKyqnjkHLMexcqD8WlVooaRl1k2RPk5vDYvC8o2bn22OKKbOnSRM5YlPS0iWzxo0J VcnVVyt0AANQQkV0ABBQQkVXaXRoTUQ1QW5kREVT</item> <item name="responder-dn">\PERIN-TAO\novell\Provo\phb</item> <item name="auth-style sheet">process_template.xsl</item> <item name="response-style sheet">process_template.xsl</item> <item name="subject-name">Joe the Intern</item> <item name="url-base">https://192.168.0.1:8180</item> <item name="url">https://192.168.0.1:8180</item> <status event-id="" level="success"></status> <item name="post-status">success</item> </replacement-data> l. The Web server processes the template with the post_response.xml...
- Page 67 m. The resulting Web page is returned as the result of the HTTP POST. The second row of the table is not present because the post-status-message referred to by the <form:if- element is not present in the replacement data document. item-exists>...
- Page 68 Identity Manager 3.6 Manual Task Service Driver Implementation Guide...
-
Page 69: G Custom Element Handlers For The Subscriber Channel
XML element that is submitted on the driver's Subscriber channel. The Java custom element handler must implement the com.novell.nds.dirxml.driver.manualtask.CommandHandler Java interface. The name of the custom element class is specified in the Additional Handlers item found in the Subscriber configuration parameters. -
Page 70: Constructing Message Documents By Using Stylesheets And Template Documents
The handler is implemented in the com.novell.nds.dirxml.driver.manualtask.samples.SampleCommandHandler class. The sample handler simply generates a document using style sheets and templates and writes the resulting document to a file. G.3.1 Compiling the SampleCommandHandler Class You can use any Java 2 compiler to compile the SampleCommandHandler class. -
Page 71: H Custom Servlets For The Publisher Channel
If you are using a URL generated by a command handler on the Subscriber channel, you must use the com.novell.nds.dirxml.driver.manualtask.URLData class to validate the URL to ensure that the responder-dn data item has not been tampered with. See the Javadocs for information on accomplishing this. -
Page 72: Compiling The Sampleservlet Class
Edit the Driver Parameters. In the item labeled , add the string Additional Servlets com.novell.nds.dirxml.driver.manualtask.samples.SampleServlet Add Telephone Number to the Publisher channel filter. Submit the following URL in a browser (assuming the browser is running on the same machine as the driver): https:localhost:8180/1.sample?dest-dn=username.container&attr-...