Page History
...
- Open the Deployment Tool from the Tools ribbon.
- Using your initials for II, create an application: IIJITSRV:
Application: IIJITSRV
Description: JIT Server Personnel System
Company: II Systems - Click Create and the New Version dialog will open:
- Enter a Description: Version 1 and select the XAPPSV template.
- Click Create. The Package Maintenance dialog will open.
The XAPPSV template has configured most of the required settings. Settings groups which are not required have been hidden. Note that Install Listener: Yes is selected.
The Required Execution parameters include the special value *licenses for Process to Execute. This will start the Server License application to enable a SuperServer license to be loaded initially.
No changes are required to the Required Execution Parameters settings. Click on the Settings
button in the toolbar to open the Settings dialog.Note Note: The deployment is to a client without a local database. You would only require a database for a JIT server installation if this system is also the application / database server for the application system. In this case the server would run the applications as well as delivering upgrade packages to the desktop client part of the application. 
Click OK to close the Settings dialog.
The deployed JIT Server application will require a SuperServer licence, which enables the client applications to connect. A licence request for a machine (PC or Windows server) is generated by running the X_CPU licence utility, which generates a unique text file for your PC or server, which is submitted when requesting a licence. This licence utility executable and shortcut will be included by defining a File with Special Processing.
In the Package Maintenance window, click the Files with Special Processing
toolbar button. This will open the following dialog:
Complete one entry, with the following values:
Type: System
Language: ENG
Description: Licensing – X_CPU Utility
Path:
[dir_X_Win95.X_Lansa.Execute
...
]x_cpu.exe
...
The path
...
value
...
will
...
generate
...
a
...
path
...
for
...
the
...
installed
...
program,
...
such
...
as:
...
C:\Program
...
Files
...
(x86)\II
...
Systems\Just
...
in
...
Time
...
Server\X_Win95\X_Lansa\Execute
...
where:
...
II
...
Systems
...
is
...
your
...
Company
...
name
...
Just
...
in
...
Time
...
Server
...
is
...
your
...
Application
...
name.
...
Click OK to save this definition.
A shortcut will be created in a path such as: C:\ProgramData\Microsoft\Windows\Start
...
Menu\Programs\II
...
Systems\Just
...
in
...
Time
...
Server
...
You don't
...
need
...
to
...
review
...
this
...
now,
...
but
...
you
...
will
...
find
...
full
...
details
...
Save the package definition using the toolbar
button. Close the Package Maintenance dialog.The JIT Server will install a LANSA Listener. Before building the package, you need to complete the listener definition by selecting the IIJITSRV application and opening the Communications Administrator dialog using the
toolbar button.
Open the Listener dialog from the Advanced menu.
Set the listener Connection Identifier (it's a Port number). A suitable value will depend on what other listeners you already have defined on the target PC or Windows server. This exercise will install to your desktop. You probably already have your Visual LANSA listener set to the default setting of 4545. For the JIT Server set the value to 4547 or any other suitable value.
Click OK to close the Listener Information dialog.
Close the Route Information dialog. This will save a listener.dat file in your package definition which will be used to configure the listener when it is installed.
This change will prompt a message box, as shown:
You have completed the definition of your JIT server package.Select the Version 1 package in your IIJITSRV application. Check the package definition with the
toolbar button. This should report zero errors.Build your package using the
toolbar button.
After the build is completed, the Package build Log will be displayed.Filter to show All messages only and scroll to the bottom.
You should have no fatal messages. The one warning message concerns the allocation of a GUID to your package.Close the Package Build Log.