Follow these steps when your application is ready to be deployed.
Step | Activity | How to Do It | OK |
Start the Deployment Tool | Logon to Visual LANSA and start the Deployment Tool. | Start Visual LANSA and logon to the partition containing the application to be deployed. |
Create a Deployment Tool application and package | Create an application and a package using the Deployment Tool. | Click on the New Application button on the tool bar or select the New command from the Application menu. |
Specify package settings | • Deploy to Client Without Local Database | Click on the Package Settings button on the toolbar to display the Package Settings window. |
Configure the application to use remote database | Because you are deploying for access to a remote database, you must configure the application not to use a specific database. In the Database section, set the database options to No and specify the DBMS Type (DBUT=) as No Database. | Double-click on the DBMS Type (DBUT=) parameter. |
Define the connection behavior | Accept the defaults in the Communications and SuperServer sections. |
Specify the start up form | Enter the name of the start-up form in your application. | Double-click on the parameter Form to Execute (FORM=) in the Required Execution Parameters area. |
Decide what execution parameters need to be prompted | If you want to prompt for a setup parameter when the package is installed, enable the prompting by selecting the parameter and checking the Prompt during installation option. | For example, to enable the Prompting of the Target Directory option, double-click the parameter and select the Prompt during SETUP check box in the window which is displayed. |
Add Framework objects | Add the Framework objects in your application. | Click on the Select Repository Objects button. Drag the objects you want to include to the area on the right. |
Add Other Framework Objects | Locate your XML files in the execute directory of your partition (for example C:\Program Files\LANSA\X_WIN95\X_LANSA\x_DEM\execute). | Double-click Non-LANSA Objects to browse for the objects. Make sure you are browsing in the correct LANSA system. |
Include your client-side objects | Add your objects (filters, command handlers, start-up forms, etc.), multilingual text variables, system variables, message files, files, processes, functions and images used in the client side of your application. | Ensure that all non-LANSA objects have correct installation paths specified for the target machine. |
Add an icon | Add an icon to be used with the shortcut created on the target machine when the package is installed. | Click on the Application Icon button on the toolbar of the Package Control Panel. Select an icon. |
Choose Desktop settings | Choose the Desktop settings depending on your preferences. | For example, you may want to select these options: |
Include RAMP-NL objects | If you are deploying a RAMP-NL client that will connect to an IBM i server, you need to add RAMP objects to the package. | Follow the steps in Check List => WIN-RAMP-NL. |
Save the package | Save the package definition. |
Include the host route for an Application | Include the host route for the server definition (the lroute.dat file) in the package. | From the Visual LANSA Deployment Tool Main window, select your application and then click on the Communications Administrator tool bar button. |
Build the package | Check and build the package. | Select the Check Package option in the Options menu. The message you receive should tell that no errors were encountered. |