Follow these steps when using LANSA Version 14 SP1 or older versions.

Step

 Activity

How to Do It

OK

Assign a build number

Assign a build number nn to the version of your product being released. This number will be used in the following steps for a file naming convention.

See Create a Version in the Deployment Tool guide.


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.

Ensure that you use a user profile which is authorized to the objects that are being deployed.

From the Tools ribbon, select Deploy. The Visual LANSA Deployment Tool's main window will open.


Create a Deployment Tool application and package

Create an application and a package using the Deployment Tool.

Do not use any template.

Click on the New Application button on the tool bar or select the New command from the Application menu.

Fill in the application details.

Click OK. You are prompted to create a version. Fill in the package details and click OK.

The package maintenance window is displayed.

For more information, see Create an Application in the Deployment Tool guide.


Specify package settings

Click on the Package Settings button on the toolbar to display the Package Settings window.

We recommend these settings for most systems:



Please  ensure these settings are appropriate for your environment. See Settings in the Deployment Tool guide.


Add Framework objects


Start adding the Framework objects in your package:

Add reusable parts starting with VF_*.

Add the copies of the UF_* objects you have made (see Getting ready for deployment in VLF-ONE).

Include process VF_PR001 and VF_PROX1. Include all the functions in the processes.

Click on the Select Repository Objects button. Drag the objects to include to the area on the right.

Then select all the objects on the right and select the Cross-Reference icon above the selected components. A new dialog will open to allow you to select the cross-reference settings.

Ensure all required object types are selected.


Add these objects when deploying  to a Windows server

Server modules VF_SW*

Then select all the objects on the right and select the Cross-Reference icon above the selected components. A new dialog will open to allow you to select the cross-reference settings.


Add these files when your Framework uses  Framework security and you are deploying to a Windows server

Files:

VFPPF06

VFPPF07


Create an installation path for non-LANSA object types

Click Non-LANSA objects.

Create an installation path that points to the partition vl-web folder:

  • Click on the Set installation path icon.



  • Click on the Define installation path icon:



  • Create a path. Make the Id for example PARTVLWEB and set it to Partition VL-Web:



  • Click OK.



The Framework Engine file VLFONE_Engine.js


Click the Search icon to locate the VLFONE_Engine.js file in the partition’s \web\vl folder, for example:

<lansa root>\x_win95\x_lansa\x_<partition identifier>\web\vl



All VLFONE non-LANSA objects

Click the Get all files from folder at build icon and select the \web\vl\VLFONE folder, for example:

<lansa root>\x_win95\x_lansa\x_<partition identifier>\web\vl\VLFONE



Set the installation path for non-LANSA VLF-ONE objects.

Set the installation path to PARTVLWEB:


Decide what execution parameters need to be prompted

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.

For more information, see Execution Parameters in the Deployment Tool guide.


Configure the database to be installed on the target system



For more information, see Database in the Deployment Tool guide.


Include your objects

Add your objects (filters, command handlers etc.), multilingual text variables, system variables, message files, files, processes, functions and images used in the application.

Make sure you include your custom snap-in components. For more information please refer to VLF-ONE Snap-In Points Summary  in the Framework Guide.

Ensure that all non-LANSA objects have correct installation paths specified for the target machine.

See Configure the Non-LANSA Object Installation Path in the Deployment Tool guide.



The Framework definition with a name like:

XXXXXXXXX_LLLL_VLFONE_Definition.DAT 

where XXXXXXXXX is the Framework name

LLLL is the language.

Find this file in the partition execute folder, for example:

<lansa root>\x_win95\x_lansa\x_<partition identifier>\execute

Note that this file is a Non-LANSA object so you need to add it in the Non-LANSA objects node.


Optionally add a shortcut

You can create a desktop shortcut to launch the URL 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.

See Application Icon in the Deployment Tool guide.


Save the package

Save the package definition.



Build the package

Check and build the package.

Your application package is created in the X_APPS\PackageName directory, for example:

 C:\Program Files\LANSA\X_WIN95\X_LANSA\ X_APPS\PackageName).

Select the Check Package option in the Options menu. The message you receive should tell that no errors were encountered.

Click on the Build button. Wait for the package compilation to complete.