4.2.3 Migrating a Partition from a Slave to a VCS Master for Git in the Cloud

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:

2.  Click OK.

3.  Create a new Partition with the same name as the source system. Let's say it's called DEX (New/Partition). This partition is going to be replaced so the actual settings do not matter. You just need to be able to select it on the logon dialog.

4.  Close the Development Environment and select DEX and click OK.

5.  Leave that system running while you prepare the export from your source system.

Note that the export may be produced by an IBM i too

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 the settings as shown below. No other configuration is required.

7.  Save the Package and Build it.

8.  Once the Package is built, close the Package and go to the Package Folder. Now navigate to the internal directory of the package you have built. Something like this:
C:\Program Files(x86)\SlaveSystem\X_WIN95\X_LANSA\x_apps\export\x_pkgwrk\6.0.0\Build\internal

     Note: Choosing the Go To Folder option from the Deployment Tool will take you straight to
C:\Program Files(86)\SlaveSystem\X_WIN95\X_LANSA\x_apps\export.

     This export needs to be moved to the Cloud. An excellent way to do this is to use the aws command line tool: aws s3 sync. Refer to AWS documentation for more details to push the export to S3 and then to pull it down from S3 to your Cloud instance.

9.  Return to the Visual LANSA Independent System which is to be connected to your VCS Master.

10. Start the LANSA Import. Type the path to the export pulled down from S3 in the Filename field and click Open, then double click the lxxdir.del file. A dialog like the following will be displayed.

11. Click Import.


12. When the import completes, close down the Development Environment and restart it.

     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. 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 that you need to use.

Populate VCS Working Folder

1.  Once the Development Environment is displayed, expand the Repository List that was generated. Select all objects that you wish to add to version control.

Tip: To select all objects in a list, click the first item, scroll down to the last item, hold down the Shift key and click on the last item. Alternatively, make the list a favorite by right clicking on the list and selecting Is Favorite. Go to the Favorites view, click on the list, click on an object in the list and press Ctrl-A.

2.  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.

Pointing the Version Control System at the LANSA VCS Working Folder

Now you need to point the VCS at the LANSA VCS Working Folder. How you perform this step will depend on your Version Control System. The example used here is Git. The use of this as an example is not an endorsement that this particular VCS will suit your development and management style.

You may perform this step from within the Development Environment or using a Git user interface program such as Git Extensions.

To perform this step from within the Development Environment, see Version Control – Git Integration in the User Guide.

To perform this step using Git Extensions, do the following:

1.  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.

2.  Initialize a Git repository in this directory. There are various ways to do this. One way is to use Git Extensions. Open it up and on the first screen click on Create New Repository. Paste the directory into this dialog and click Create. (Note that if this is the first time you have run Git it will show you a list of global settings which must all be set up correctly before proceeding.

3.  You should see the Commit button on the toolbar with a tick in a red circle indicating there are changes to commit to Git.

4.  Click on Commit to display the Commit dialog. Stage all the changes and click Commit.

LANSA and the VCS are now linked up together.