Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
(Optional) Modifying the JSP files and the EAR file z/OS Cryptographic Services PKI Services Guide and Reference SA23-2286-00 |
|
After you update the template file, you can optionally perform additional customization on the PKI Services Web application by modifying the JSP files. You will probably want to modify the JSP files in the directory mod_inc. You can modify any line that is not marked with a comment saying that it cannot be modified. You also might want to modify JSP files in the directories Customers and PKIServ. You cannot modify JSP files in the directory not_mod_inc. For information about what files are contained in each directory, see Directories for JSP files. Example: This example shows how you could customize a JSP
file. notbefore.jsp is a JSP file in mod_inc.
The portion of this file that displays the prompt and the options
is shown in Figure 1, without
customization.
Figure 1. A portion of the JSP file notbefore.jsp,
without customization
You could customize this code to reword the prompt and add an
option of 7 days, as shown in Figure 2.
Figure 2. A portion
of the JSP file notbefore.jsp, with customization
An enterprise archive (EAR) file is a specialized Java™ archive (JAR) file, used to deploy Java EE applications to Java EE application servers. PKI Services ships a default EAR file in the directory /usr/lpp/pkiserv/pkijsp. If you make changes to the JSP files for the PKI Services Web application, you need to update the EAR file to include your changes. |
Copyright IBM Corporation 1990, 2014
|