What is VF_Sy001_System_LastShipped.XML?

Date:25 September 2006
Product/Release:Visual LANSA Framework
Abstract:VF_Sy001_System_LastShipped.XML
Submitted By:LANSA Technical Support

The VLF Demonstration and Programming Examples - before CU3

Until LANSA CU3, VLF upgrades always renamed and then replaced the standard shipped demonstration system in XML file VF_SY001_System.XML with the very latest shipped demonstration version. This was done to make sure everybody got to view and use the latest demonstration and programming techniques material.

In CU3 this has changed so that the shipped demonstration application is now stored in a separate file and it will not override users own application.

The VLF Demonstration and Programming Examples - after CU3

An existing VF_SY001_System.XML file is no longer renamed and replaced by a VLF upgrade.

If it already exists it is left unchanged and the new shipped version is installed with the name VF_Sy001_System_LastShipped.XML instead.

Sounds like a solution that makes everybody happier?

Not quite...

So what's the downside to doing this?

When a user starts the VLF in an upgraded system they now use the same VF_SY001_System.XML file as they were using before the upgrade. They are using an "old" version that contains the "old" definitions of the demonstration and programming examples.

There are two significant downsides to this:

  1. Developers may not get to view and use the latest demonstration and programming examples because they are not defined in their "old" VF_SY001_System.XML.
     
  2. There may be incompatibilities between the newly upgraded demonstration filters and command handler programs and what is defined in their "old" VF_SY001_System.XML.

An example of (1) is the new "Advanced Instance List" examples. These are new to the CU3 version of the VLF. If you use an "old" version of VF_SY001_System.XML you will not see them and may never know they exist.

An example of (2) relates to the shipped example EMPLOYEE and SECTIONS business objects. In the CU3 version of the VLF the instance lists and relationships for EMPLOYEE and SECTIONS were significantly changed to demonstrate the new parent/child type relationships.

So if you start the demonstration system using an "old" version of VF_SY001_System.XML and execute the updated EMPLOYEE or SECTIONS business object filters or command handler programs, then you might see errors like:

'Invalid business object user name/type SECTIONS encountered in instance list".
'Invalid or Unknown user object EMPLOYEE encountered in instance list".

This is because the CU3 updated demonstration filters and command handler programs are pumping out instance list data in the "new" parent-child format .... but the "old" framework definition in VF_SY001_System.XML does not have these relationships defined ..... so it gets confused and starts issuing warning messages.

How to rectify this?

The easiest way to rectify this, if you have nothing of real value defined in your "old" VF_SY001_System.XML file, is simple:

  1. Locate VF_SY001_System.XML in your partition execute directory and delete it.
     
  2. Locate VF_Sy001_System_LastShipped.XML in the same directory and rename to VF_SY001_System.XML.
     
  3. Start the framework. You should now have the latest demonstration and programming techniques available and no warning messages should appear.

If you do have valuable things in your "old" VF_SY001_System.XML file that you need to keep then do the following:

  1. Start the framework as a designer and make a dummy change to a business object caption (say). Use the new (Framework) -> (Save As) option and save VF_SY001_System.XML using a different file name (eg: My_System.XML). Close down the framework.
     
  2. Check that XML file My_System.XML (say) has been created in your partition execute directory.
     
  3. Locate VF_SY001_System.XML in your partition execute directory and delete it.
     
  4. Locate VF_Sy001_System_LastShipped.XML in the same directory and rename to VF_SY001_System.XML
     
  5. Start the framework again. You should now be able to choose between starting VF_SY001_System.XML or My_System.XML.
     
  6. Start VF_SY001_System.XML. You should now have access to the latest demonstration and programming techniques material and no warning messages should appear.
     
  7. Start My_System.XML. Delete the demonstration and programming techniques applications from My_System.XML, leaving just your own application parts ready for further work.