Web WorkFlo and WorkFlo Services require that you digitally sign custom step processor Java ARchive (JAR) with either a Netscape Object Signing Certificate or a Sun Java Object Signing Certificate.
Developers who create custom step processors can obtain a digital certificate to sign their JAR files from either VeriSign Inc. (http://digitalid.verisign.com/developer/nos_pick.htm) or Thawte Consulting (http://www.thawte.com/). (The default JAR files are signed with a Netscape Object Signing Certificate.) Custom signing has been tested in custom step processor JAR files with this type of certificate. A Netscape Object Signing Certificate is the recommended option. With a single certificate, developers can create and sign as many custom step processor JAR files as needed.
The following procedure details how to create a JAR file signed with the Netscape Object Signing Certificate. The procedure describes how to use the Netscape signing tool (signtool) in a general fashion. For more information, visit the Netscape Developer's Site (http://developer.netscape.com/software/signedobj/jarpack.html).
Note If you purchase a Sun Java Object Signing Certificate, you must use the Sun Microsystems JAR signing tool: jarsign. You must use a different procedure from that listed below. (Sun offers an on-line tutorial demonstrating how to use the jarsign tool at http://java.sun.com/docs/books/tutorial/jar/sign/index.html.)
C:\certificate\signtool -d"C:\certificate" -k"<Your_company_name>" -Z"<Your_jar_file_name>" -p"<Your_password>" sign
where <Your_company_name> is replaced by the company name as stated by your certificate provider, <Your_jar_file_name> is replaced by the name you wish to give the JAR file, <Your_password> is replaced by your password supplied by your certificate provider, and sign is the name of the directory containing the files your wish to have in the signed JAR file.
C:\certificate\signtool -d"C:\certificate" -w Your_jar_file_name
where <Your_jar_file_name> is replaced by the name you wish to give the JAR file.