In addition to the cool things mentioned by Rob that JspWiki/JZOS/Tomcat
can do on z/OS,
I also like that it uses a regular filesystem rather than a database for
page storage, which
makes it easy to manage/backup, etc.
JspWiki also keeps a complete version history of all pages that you can
use to see what/who/when something changed and allows you to roll back
changes.
We have used it very successfully as a repository for software
requirements and design.
Also, I would mention that with Rob's help we plan on using JspWiki as
one of the lab exercises
in one of the z/OS JZOS/Tomcat labs at SHARE in Baltimore.
The lab descriptions aren't quite up-to-date, but if you are interested
check
the session descriptions in a couple of weeks or drop me a note.
Finally, I would mention there are support forums at http://dovetail.com
for z/OS Java, JZOS, Tomcat, etc
that may be helpful as they contain the problems and solutions to scores
of issues
related to Java, JZOS, and Tomcat on z/OS.
Kirk Wolf
Dovetailed Technologies
Schramm, Rob wrote:
Jon,
It is pretty easy to setup.
The instructions about how to get Tomcat up and running in 1 hour are
really good... and how to get SAF working.
The JSPWiki install is pretty easy, since you can use the Tomcat Manager
to deploy the application.
We are using JSPWiki as a documentation repository for the system
programmers. All the information about procedures, hardware, software
etc etc are either contained within the wiki or are linked to from the
wiki.
There are a number of templates that have been contributed. I am
currently using a slight defunct one called "Power of Two"
http://www.jspwiki.org/wiki/Pow2Template
The other available templates are
http://www.jspwiki.org/wiki/ContributedTemplates
I have tried out various of the user contributed plugins. Some are
pretty cool... some have the potential to be cool. I originally wanted
the PDF plugin, since some of the areas want documentation in PDF
format... and I thought it was a waste of time to double maintain
documentation. The PDF plugin itself is still pretty rough. It does a
fine job with the exception of tables.
One of the nicest plugins is http://www.jspwiki.org/wiki/NewPageHandler
.. If you need to help yourself or your group out by creating a
structure for a page .. (i.e. new vendor software information page )
then this is pretty cool.
The thing that really sets Tomcat/JSPWiki apart on z/OS is JZOS and the
ability to use SAF to control update access to pages. Of course that is
a bit against the normally "open" wiki's ... but even if you choose a
resource that everyone has access to.. then their RACF/ACF2/TopSecret
userid is recorded as the updating user for a particular page.
The syntax for JSPWiki is pretty easy too.
http://www.jspwiki.org/wiki/EditPageHelp
Additionally, I would recommend a DVIPA and moveable mount points for
the JZOS/TOMCAT/JSPWiki information. If a system is going to be down
for a while, we just "move" the wiki to a new system.
//TCPCRVP EXEC PGM=MODDVIPA,REGION=0K,
// PARM='POSIX(ON) ALL31(ON)/-p TCPIP -c ip.add.res.s'
//SYSOUT DD SYSOUT=C
Needless to say, I am a pretty big fan of wiki's. Running it on z/OS is
equally cool. It demostrates use of java and generally available open
source on z/OS.
1) Jzos 1.2.1
2) Tomcat 5.0.28
3) JSPWiki 2.2.28
4) JVM 1.4.2 that comes with z/OS
5) Using mainframe ESM (external security manager) user ID and password
authentication.
6) typically used items like log4j. Except I am pretty sure the log4j
(http://logging.apache.org/log4j/docs/) folks would be surpised to see
the output of the logging tool being housed by JES2.
-Rob Schramm
Just entered the land of 40's.. so far so good
p.s. If you run into problems with JSPWiki on z/OS, drop me a note.. and
I will attempt to provide some assistance.
<snippage>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
