WEB2A, Step 2. Package the Deployment Material on the Source System

VLF Deployment Check Lists

 

WEB2A, Step 2. Package the Deployment Material on the Source System

 

Step

 Activity

How to Do It

ü

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.

 

 

 

Optionally include VLF.NET objects

If you want to compile the Framework as a .NET executable, you need to save it with the VLF.NET feature selected.

See <A HREF="webnet_0025.htm">Create VLF.NET Objects to be Included in the Deployment Package</A>.

 

 

Zip up  server objects

Create a zip file and include all standard server objects and your own server objects:

·      Images

·      Javascripts

·      HTML files

·      XML Files

·      CSS Files

·      Dlls

 

Create a .zip file called, for example, Bnn_Webserver.zip (where nn is your version number), and include files from the LANSA for the L4web <A HREF="javascript:void(0);openCHM('lansa048.CHM::/lansa/vlf1990.htm','main');">Images Folder</A> and your <A HREF="javascript:void(0);openCHM('lansa048.CHM::/lansa/vlf1995.htm','main');">Private Working Folder</A> (which normally resides under your images folder).

Make sure these files are included:

VF_*.*

FP_*.*

UF*.*

Also include your own server objects.

If you are deploying VLF.NET applications, see <A HREF="webnet_0030.htm">Add VLF.NET Objects to the Deployment Package</A>.

In a typical installation you would include all the files under the images folder (including the private working folder), so you may simply decide to zip up the entire contents of the images folder.

However, it is important that the objects end up in the right directories on the target machine, so if you are not using the same directory names, you may want to create two zip files - one containing the objects in the images folder (excluding the private working folder images) and another zip file containing the files in your private working folder.

 

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 the Deploy button. 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 Package. Fill in the package details and click OK.

The Package Control Panel is displayed

 

 

Set the Deployment  option

Set the deployment option of the package to Self-Extracting Zip.

If you select another deployment option, this check list may not work.

 

Display the Deployment Option window by clicking on the Deployment button.

 

 

Specify package settings

Because the package will be deployed to a system which already has Visual LANSA installed on it, you may choose the option to move the LANSA code over as well as the runtime objects:

·      Deploy to Development System

 

 

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

 

 

 

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.

Because you are deploying to a system that already has Visual LANSA installed on it, in general  you can use the default values.

 

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.

 

 

 

Configure the database

Specify a name for the database to be installed on the target system in the Data Source Name (DBII=) entry or check it as Prompt in Setup.

You should also confirm that the database user ID and password are correct.

Do not select the Check for Installed Database, Adaptive Server Anywhere Install, and the Ask Adaptive Server Anywhere options.

 

·     

 

 

Add LANSA programs

Add all the LANSA programs in your application.

Add forms starting with FP_*, UF_* and VF_*.

Add reusable parts starting with FP_*, UF_* and VF_*.

Add Web Components starting with FP_R*, UB*, VF_*and VFW*.

Add Weblets starting with FP*, UB* and VLF_LAYOUT .

 (If you want to be able to run the demonstration system, include all forms and reusable parts starting with DM_* and DW* and process DF_PROC, and the *.htm, *.bmp and *icon files required.)

Include process VF_PR001, VF_PR002, VF_PR004, UF_SYSWB, VF_PROX1 and UF_SYSBR with all their functions.

 

 

Click on the Select Repository Objects button. Drag the objects you want 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 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).

Add these files to the package (if you have saved your Framework definitions with other names, add the corresponding XML files):

·      vf_sy001_system.xml

·      vf_sy001_users.xml (if using)

·      vf_sy001_servers.xml

·      vf_sy001_tables.xml

If you want to deploy default Virtual Clipboard content, select VF_Framework_Virtual_Clipboard_Default.dat and/or VF_User_Virtual_Clipboard_Default.dat.

Bring up the Other Objects tab.

Double-click Non-LANSA Objects to browse for the objects. Make sure you are browsing in the LANSA system you are currently using.

Note that the Deployment Tool does NOT default to the current system and partition, you have to select them manually.

Select the objects and click OK.

Then set the path where the objects are to be installed:

·      Use DFTPATH as the Installation Path Id (for example *PART_DIR_EXECUTE)

 

 

 

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.

 

Click on the Select Repository Objects button on the toolbar.

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

 

 

 

Include your web server objects

Add the Bnn_Webserver.zip file or files that you created earlier to store the files from your images and private working folders.

Note that when you install the package on the target system, the zip file(s) will be placed in the partition execute folder of your target LANSA system.

Bring up the Other Objects tab.

Double-click Non-LANSA Objects to browse for the objects.

 

 

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:

·      Create Communications Administration Shortcut

·      Create ODBC Administration Shortcut

 

 

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.

Note that if you are working in a partition that has not been enabled for full RDMLX, you may see errors saying that the copy of some dlls has failed. Just ignore the messages.