Page History
Show Contents List
You are here:
...
Any Just in Time configuration must include an Application Server.
All distributed Versions or Patches are stored on the Application Server.
...
The Application Server then receives requests for upgrades when a user starts the application on their PC.
...
Any new Versions or Patches (depending on your Upgrade Option UPGD) will then be sent to the client PC in response. As such, the Application Server is a simple file server, and does not require a powerful processor.
Installing an Application Server
An Application Server must have:
A Visual LANSA installation.
A listener installed and running to receive requests from any Client PCs.
A valid LANSA SuperServer license.
...
A single seat LANSA SuperServer license is usually sufficient as it is only used during the Just In Time Upgrade processing.
...
After any upgrade Versions or Patches have been downloaded the license will be made available again.
...
| Tip |
|---|
| Tip: |
...
| The |
...
| simplest |
...
| way |
...
| to |
...
| set |
...
| up |
...
| the |
...
| Application |
...
| Server(s) |
...
| is |
...
| to |
...
| install |
...
| Visual |
...
| LANSA. |
...
Applying
...
Packages
...
to
...
the
...
Application
...
Server
...
Each
...
Application
...
made
...
available
...
for
...
Just
...
in
...
Time
...
Package
...
Upgrade
...
deployment
...
on
...
the
...
Application
...
Server
...
must
...
include
...
a
...
directory
...
structure
...
like:
...
<sysdir>\x_apps
...
\[Client App Name...
]\...
This
...
directory
...
structure
...
is
...
a
...
mirror
...
of
...
the
...
directory
...
structure
...
on
...
the
...
deployment
...
system.
...
Within
...
the
...
[Client
...
App
...
Name
...
]
...
directory
...
only
...
the
...
MSI/MSP
...
to
...
be
...
deployed
...
is
...
required.
...
The
...
original
...
MSI
...
used
...
to
...
install
...
the
...
Application
...
must
...
be
...
included.
...
| Warning |
|---|
| Warning: |
...
| When |
...
| the |
...
| JIT |
...
| Application |
...
| Server |
...
| is |
...
| the |
...
| same |
...
| LANSA |
...
| system |
...
| as |
...
| the |
...
| Deployment |
...
| System |
...
| any |
...
| distributed |
...
| Package |
...
| will |
...
| be |
...
| available |
...
| to |
...
| be |
...
| downloaded |
...
| immediately. |
...
| For |
...
| this |
...
| reason |
...
| it |
...
| is |
...
| recommended |
...
| to |
...
| use |
...
| different |
...
| LANSA |
...
| systems |
...
| for |
...
| the |
...
| creation |
...
| and |
...
| deployment |
...
| of |
...
| Packages |
...
| to |
...
| facilitate |
...
| testing |
...
| of |
...
| the |
...
| Package |
...
| before |
...
| it |
...
| is |
...
| available |
...
| to |
...
| download. |
...
Use
...
Microsoft
...
SCCM
...
for
...
complex
...
deployments
...
such
...
as
...
these
...
.
...