Page History
| Note |
|---|
Note: the most efficient way of installing a Visual LANSA Independent System to a VCS Master is to perform a Custom Install, and in the Initialize Database and Partitions options only choose Example Partition Definition. This is because the whole partition will be replaced. Other partition initializations such as Visual LANSA Framework need to be done after the partition has been replaced with the Slave data: |
1. Start the Visual LANSA Independent System which is to be connected to your VCS Master. If it's a completely new install the logon will display something like this:
...
6. On the Source System (which contains the COMPLETE and up-to-date partition), use the Deployment Tool to export your whole partition to your Independent System. Use the XEXPORT template to create an application and check that the settings are as shown below. No other configuration is required. Save the Package and Build it.
7. Once the Package is built, close the Package and go to the Package Folder.
...
10. Start the LANSA Import. Paste the path into the Filename field and click open, then double click the lxxdir.del file. A dialog like the following will be displayed:
- Check (select) Partition Definitions and User Objects.
- The System Objects are unnecessary.
- You MUST NOT import the System Definitions.
- Check (select) Save As Repository List.
...
| Note |
|---|
Note: Once the Job Status is completed, you do not need to wait for the Refreshing Repository to complete nor do you need to press F5. So at this point you can close the Development Environment: When you restart the Development Environment you will be prompted to initialize the partition if the import came from an older version of LANSA. Choose the options you need to use. |
...
Right click on a selected object and click Add to Version Control.
All selected objects will be saved into the VCS Working Folder. This can take quite a while for a large partition.
...
2. Go to the LANSA Development Environment and on the VCS tab right click on the Version Control folder and choose Show in Windows Explorer. Copy the whole of the path. Paste this path into the working folder in the VCS:
You should see the LANSA directories ghosted in the VCS Folder:
3. Right click on each ghosted folder and choose Add this Folder. You'll see something like this:
4. Right click on DEVPGMLIB and choose Get Latest Version. This ensures the file states are up to date. In particular it sets all files to read-only.
LANSA and the VCS are now linked together. All objects will be unavailable to edit as they are not checked out from the VCS. (This presumes you use the Check Out/Edit/Check In concurrent development style of version control). If you open an object it will display this message:
If you check it out from the VCS you will be allowed to edit it.
...