WIN2, Step 4. Install the Deployment Material on the Target System
Warning: Do not test your deployment package on your development system.
|
Step |
Activity |
How to Do It |
ü |
|
Server system is set up |
Before you start installing the client deployment package you must have deployed the server side of the application. |
|
|
|
Listener |
Make sure you have a listener running on the server.
|
|
|
|
Install the deployment material |
Install the package by double-clicking the package .MSI file. The setup program automatically launches the Framework. When the Framework is first launched executable files are copied and the Framework is displayed. The application is ready to be used. If you encounter problems during the installation, check the MSI*.log file in the end user's defined %TEMP% folder, for example: MSI2ce4c.log. As well as installing the Application, a standard Windows program menu folder will be created for each Application using the Company and Application descriptions as folder names. This means that every Application built with the same Company details and installed on the same PC will be grouped together. |
|
|
|
Optionally install RAMP-NL |
If you are installing a RAMP-NL application, follow the steps in <A HREF="WINRAMP_0010.htm">WIN-RAMP-NL, Step 3. Install the Deployment Material on the Target System</A>. |
|
|
|
If you are deploying a RAMP-TS application, verify IE settings |
Verify IE settings on every PC from which RAMP-TS is used. |
See <A HREF="javascript:void(0);openCHM('lansa050.chm::/LANSA/LANSA050_2525.htm','main');">Verify Internet Explorer Security Settings</a> in the RAMP-TS Guide. |
|