Step 1 Enable Framework for Client Server

Step 1. Enable Framework for Client/Server

VFW130 – Set up the VL Framework for Client/Server Operation

This step concerns changing settings at framework level.

1.  Start the Framework as Designer. Open the Framework Properties dialog:

2.  Select the User Administration Settings tab.
In the Sign on Settings group box, in the End Users must Signon to this Framework dropdown list, select in MS-Windows applications only.

3.  Select the radio button, Users Sign on to a Remote Server to Use the Framework.

4.  Save and Restart the VL Framework.

5.  On the Log On form, click the Work Offline button:

6.  When the framework has started, select Servers from the Administration menu.

7.  Click on the New button to define a server:

8.  On the Identification tab, give the server definition any suitable Caption such as Test Server.

9.  Select the Icon tab and give the server definition any suitable icon.

10. Select the Server Details tab.
Click on the LANSA Comms. Admin button to find the Partner LU to use for the IBM i server.

     If necessary, first define the server in the LANSA Communications Administrator.
To do this you must know the server name or IP address and the port number used by the LANSA Listener.

     A routing table entry enables LANSA communications to connect to a LANSA Listener on a server using the required Qualified Name and Port.

11. Set up the server details shown based on your own server. For example:

Server Type	LANSA for System i
Server Name	EARTHD12
Partition	TRN
Partition is enabled for RDMLX	Yes
Upper and Lower Case Password	Yes

 

     If necessary change the settings shown to suit your partition definition and password standards.

12. Close the Servers dialog and Save and Restart the Framework.

13. In the Log On dialog enter your User ID and Password for the IBM i. If you are completing these exercises using a Slave Workstation installation, you should use your Visual LANSA User ID and Password.

14. When your framework has started, your application will now access all files on the IBM i server.

     The local files in the Microsoft SQL Server database will no longer be accessed.

15. Close your framework which will currently produce errors if you access your iii HR Application.