VLF-WIN3, Step 4. Install the Deployment Material on the Target System

Step

 Activity

How to Do It

OK

Install LANSA for i on the target IBM i server

If LANSA for i is not installed on your target system, use the LANSA CD to install it.
Note that the LANSA system has to be on the same version and EPC level as the system on which the deployment material was created.
 
 

Follow the instructions in Install or Upgrade LANSA on IBM i Guide.
 

Prepare for VLF-ONE installation

Import AVLWEB to set up VLF-ONE folders.

In the LANSA Administration menu choose the Import option.
Scroll to AVLWEB and enter 7 to import it.
 

Import deployment material to the application server

Use LANSA's import facility to install everything from the save file Bnn_ALL to the appropriate partition on the target machine.
 
 

Use the option Import objects into this partition of the LANSA Housekeeping menu. Check that the import was successful.
You will have save files Bnn_IFS, Bnn_VLF and Bnn_VLFO, and possibly save files Bnn_OM1n etc. for any non-LANSA objects.
 

Restore RAMP-TS objects

If you are deploying a RAMP-TS application, you need to restore the RAMP-TS objects.

See WIN-RAMP-TS, Step 3. Install your RAMP-TS Screen Definitions at the Deployment Target.

Restore the non-LANSA objects

If your application contains non-LANSA objects, restore everything from the Bnn_OMn files into the appropriate IBM i library on the target system.

Use the RSTOBJ command to restore library-based objects from the save file. For example:
RSTOBJ OBJ(*ALL) SAVLIB(B01_OM1) DEV(*SAVF) SAVF(B01_OM1)
 

Verify the software installation was okay

Check the import job logs for any errors and warnings. If you encounter any errors or warnings you should resolve them before continuing.
 
If you have any applications that can be run in 5250 then you may test them now. If not, you will need to test everything when the Clients are set up.