WIN3, 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. |
|
|
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. |
|
Include RAMP-TS objects |
If you are deploying a RAMP-TS application you need to add more files to the deployment package. |
See <A HREF="winrampts003.htm">WIN-RAMP-TS, Step 2. Prepare Your RAMP-TS Screen Definitions for Deployment</A>. |
|
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 server-side LANSA objects in the export list |
Include your own server-side LANSA objects if any.
|
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. |
|
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 file FPTAB. |
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 enroll the administrator in VFPPF06/07. From then on the administrator can enroll users using UF_ADMIN.
|
|
|
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 |
|