adpatch options=nocompilejsp

When you use adpatch options=nocompilejsp, the lengthy time spent in compiling out of date jsps is saved. The command to compile jsps outside of adpatch is:

perl -x $JTF_TOP/admin/scripts/ojspCompile.pl --compile

Here's how the output of the above command looks like:

starting...(compiling delta)
using 8i internal ojsp ver: 1.1.3.5.2
including compatibility flag -whiteSpaceBetweenScriptlet
synchronizing dependency file:
loading deplist...15409
enumerating jsps...15409
updating dependency...0
initializing compilation:
eliminating children...12318 (-3091)
searching uncompiled...8677
translating and compiling:
searching untranslated...0
compiling jsps... 12% complete: 1100/8677 ETA: 14m7s


Do not use --quite option, as you would not be able to know the progress.

Complete syntax is:

syntax: $JTF_TOP/admin/scripts/ojspCompile.pl COMMAND {ARGS}
COMMAND --compile update dependency, compile delta
--create rebuild entire dependency file
-delta.out update dependency, list delta to file
-dep.out update dependency, output heirarchy to file

ARGS -s matching condition for JSPs filenames
-p number of parallel compilations
-log to override logfile from ojspCompile.conf
You are
recommended to set the log file location
outside of any network file system shared (NFS) area/drive.
-conf to override ojspCompile.conf
--retry retry previously failed compilation attempts
--flush forces recompilation of all parent JSPs
--quiet do not provide an actively running progress meter
--fast instantly fail jsps that are *possibly* invalid

example1: ojspCompile.pl --compile -s 'jtf%' -p 20 --retry
example2: ojspCompile.pl --compile -s 'jtflogin.jsp,jtfavald.jsp' --flush
example3: ojspCompile.pl --compile --fast --quiet


jsps do compile on the fly, but that affects the application performance. So it is a good idea to compile them in advance, if you have not done it during adpatch itself.