AW: Just in Time Install


Well, it is not recommended to do any JITIs on Terminal Servers. If you
deploy a package to a terminal server you have two possibilities to copy the
global table specs and data dictionary specs to the machine.

First of all you build the specs on a fat client with R92TAM for the data
dictionary and with R98CRTGL for the global tables. Run the report locally
(override location) on the fat client.
The R92CRTGL will cause several error messages for F98BLOB, F98720, F98740,
F98741, F98743, F98744, F98745, F98750, F98751, F98752, F98753, F98760,
F98761, F98762, F98768. Just ingnore them. There won't be any JITIs for
those tables on the Terminal Server.

If you want to include those specs in your package you have to copy the
newly created spec files from your fat client into the spec directory of
your new package. That only works properly if you have not compressed the
specs yet (option in package build). Because package compression happens at
the end of a client package build, you can copy the files on the fly into
the new spec directory on the DS while submitting the package. Or you don't
select package compression and copy the specs after the package build into
the new spec directory and resubmit the client package build with the
compression option. Don't delete the already build package!

Second possibility to put the specs onto the Terminal server is to first
deploy a normal package. And then copy the global table and data dictionary
specs from your fat client into your spec directory on the Terminal server.
If you deploy packages on many clients you have to copy them on each machine
manually. So it is easier to copy them directly into the spec directory of
your DS and include the files in the package.