WEB2B, 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>.

Include your own non-LANSA objects

If your application contains non-LANSA objects, create save files containing them. Non-LANSA objects are:

·      RPG Programs

·      DDS Files

·      Cobol Programs

·      DB2 files

·      Data Areas

·      Data Queues

Create as many IBM i save files named Bnn_OM1, Bnn_OM2, etc as required to contain other non-LANSA IBM i objects.

Save all non-LANSA objects into the Bnn_OM1, 2, 3 … n save files files using the SAVOBJ command.

Create an IBM i Export List

Create a LANSA export list named Bnn_ALL.

Use the option Work with lists of objects to be exported of the LANSA Housekeeping menu to create the export list.

Include your own LANSA objects in the export list

Include your own LANSA objects such as filters, command handlers etc.

Use the options in the Work with Export List menu to make sure all the objects used in your application are included in the export list.

Include save files in the export list

Include the save files you have created in the export list

Use option Add other/non-LANSA objects to the list.

Use F20 to find the files.

Include all the standard Framework objects in the export list

Use F8 to make generic selections when adding objects to the export list.

Fields:

FP_E*

FP_R*

UB*

UF_*

VF_*

Files (Include data in the files)

FPTAB

FPTABU

VFPPF06

VFPPF07

Processes/functions:

UF_*

VF*

Other/non-LANSA: (Type *SRVPGM)

U_BIF985

Web HTML components:

FP_R*

UB_*

VF_*

Weblets:

FP*

UB*

VLF_LAYOUT

Visual LANSA components:

FP_*

VF_AW*

VF_LW*

VF_SW*

VFW*

Review the export list and make sure included objects are exported compiled (if applicable).

Specify Y in the Comp Form column of processes, functions, VL components etc.

Save the list (F19).

Export the list

Create a save file Bnn_ALL for your export list using the CRTSAVF command.

Export your export list to the save file using option 7 (= Export) in the Work with Export Lists menu

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.