| 315 |
dpurdie |
1 |
#-------------------------------------------------------------------------------
|
|
|
2 |
# Documentation
|
|
|
3 |
#
|
|
|
4 |
|
|
|
5 |
=pod
|
|
|
6 |
|
| 361 |
dpurdie |
7 |
=for htmltoc CORE::
|
|
|
8 |
|
| 315 |
dpurdie |
9 |
=head1 NAME
|
|
|
10 |
|
|
|
11 |
JATS Installation Notes
|
|
|
12 |
|
|
|
13 |
=head1 SYNOPSIS
|
|
|
14 |
|
| 361 |
dpurdie |
15 |
Full Installation instructions are provided in L<MASS-00164 Installing and
|
|
|
16 |
Using JATS>.
|
|
|
17 |
This documentation serves as a short reminder.
|
| 315 |
dpurdie |
18 |
|
|
|
19 |
The JATS wrapper script is invoked via a machine specific script. This is
|
|
|
20 |
B<jats.bat> under Windows and B<jats.sh> under Unix. The startup script
|
|
|
21 |
contains sufficient information to startup the main, and common, JATS
|
|
|
22 |
program. The script specifies the environment on the machine and should not
|
|
|
23 |
affect the target build environment. It also isolates the JATS version changes
|
|
|
24 |
from the user.
|
|
|
25 |
|
|
|
26 |
=over 8
|
|
|
27 |
|
|
|
28 |
=item Windows
|
|
|
29 |
|
|
|
30 |
The startup script B<jats.bat> is intended to be user configured. It should be
|
|
|
31 |
copied into the users path and modified. It is intended that the script will not
|
|
|
32 |
change from version to version of JATS.
|
|
|
33 |
|
|
|
34 |
=item Unix
|
|
|
35 |
|
|
|
36 |
The startup script B<jats.sh> should be consumed directly from the JATS
|
|
|
37 |
installation. It is not intended to be user configured as configuration is
|
|
|
38 |
perform on a machine-wide basis.
|
|
|
39 |
|
|
|
40 |
A software link from C</bin/jats> to C<JatsInstalledDir/TOOLS/jats.sh> should be
|
|
|
41 |
created.
|
|
|
42 |
|
|
|
43 |
=back
|
|
|
44 |
|
|
|
45 |
=head1 RELATED DOCUMENTATION
|
|
|
46 |
|
|
|
47 |
=over 0
|
|
|
48 |
|
| 361 |
dpurdie |
49 |
=item * L<OverView|POD::OverView>
|
| 315 |
dpurdie |
50 |
|
| 361 |
dpurdie |
51 |
=item * L<EnvVars|POD::EnvVars>
|
| 315 |
dpurdie |
52 |
|
|
|
53 |
=back
|
|
|
54 |
|