Flags reference for generating digitally signed documents, digitally signing templates, and verification

Refer to this table for a list of the flags and properties that you can use in when generating digitally signed documents, digitally signing templates, and verifying the signed documents and templates. These flags are mandatory for remote document generation.
Table 1. Flags
Flag Value Description
-Dcom.ibm.rational.rpe.keystore.location A file path The location of the key store that Rational® Publishing Engine looks in to digitally sign a document template. The key store must contain private keys for digitally signing templates.
-Dcom.ibm.rational.rpe.keystore.type Text The type of the key store.
-Dcom.ibm.rational.rpe.keystore.password Text The password to read the keys from the key store
-D.com.ibm.rational.rpe.keystore.private.key.alias Text The private key that is used from the key store to digitally sign a template.
-Dcom.ibm.rational.rpe.keystore.private.key.password Text The password for reading the private key from the key store to digitally sign a template for the selected private key alias.
-Dcom.ibm.rational.rpe.run.digitally_signed_templates_only true, false

Default value: false

Example: -Dcom.ibm.rational.rpe.run.digitally_signed_templates_only=true

When set to true, forces document generation to continue if all the templates with a document specification are digitally signed and the signature can be verified. The same setting can be forced through Rational Publishing Engine Central Administrative remote services under the Settings asset type.
-Dcom.ibm.rational.rpe.digital.signature.certificate.location A file path The location of the certificate that Rational Publishing Engine looks in to verify a digitally signed document.
-Dcom.ibm.rational.rpe.digital.signature.password Text The password to read the certificate.
-Dcom.ibm.rational.rpe.digital.signature.comments Text Optional
-Dcom.ibm.rational.rpe.digital.signature.location Text Optional

Feedback