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.

Include your own non-LANSA objects when required

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

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 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.
Note that if your deployment package does not contain files, you can simply move your save files to the target system without using Import/Export.

Include your files in the export

If you want to include files in the deployment package, add them to the export.

Include the data in the files.
If you are using Framework Users and Authorities, export files VFPPF06 and VFPPF07.

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.

Add LANSA objects

Add some LANSA VLF internal objects in your application.
Include function VFU0038 from process VF_PR001.
Include process UF_SYSBR and all its functions. The functions will be named like UFUnnnn.
If you have created your own IIP functions and snapped them into your Framework, do not forget to include them.

Use the option Add process/functions to the list in the Work with Export List menu to make sure these objects are included in the export list.
 

Include RAMP-TS objects

If you are deploying a RAMP-TS application you need to add more files to the deployment package.

See WIN-RAMP-TS, Step 2. Prepare Your RAMP-TS Screen Definitions for Deployment.

Add Framework Files

If the end-user will be storing user information in DBMS tables VFPPF06/07, you need to include them.
If you are using code tables, include the code table data files FPTAB and FPTABU.

Use the option Add other/non-LANSA object to the list.
Use F20 to find the files.
 

Include file data

Include data in the files you have selected.
Note that you would not normally ship all the development user data in tables VFPPF06/07.
However, if no one in the target environment can use UF_DESGN, and the Framework is deployed with security switched on, you might ship the user files containing a single administrative user. A profile for that administrator would have to exist already or be created on the target server.
If a user at the target environment has access to UF_DESGN, the files can be shipped without data, and the person with UF_DESGN can enrol the administrator in VFPPF06/07. From then on the administrator can enrol users using UF_ADMIN.
 

Export the list

Create a save file Bnn_ALL for your export list using the CRTSAVF command.
 
CRTSAVF Bnn_ALL
 
Export your export list to the save file using option 7 (= Export) in the Work with Export Lists menu.