Using the deployment tool to export object source and all its dependent objects
|Date:||21 December 2009|
|Abstract:||Using the deployment tool to export an object and all its dependent objects|
|Submitted By:||LANSA Technical Support|
|Last Review:||November 2010|
When reporting a LANSA issue to your local LANSA distributor, often pasting the source code into an email is not enough to give a reproducible test case. Mostly, this is due to missing objects i.e. a non-standard field from the LANSA repository which is referred to in the RDML or RDMLX, but the field definition has not been included.
In these cases, it is possible to use the Deployment Tool to make sure all objects are included (including objects that may have been forgotten along the way). Since version V11, the Visual LANSA Deployment Tool now includes the XDEVELOP template (Deploy to a Development System)
- Create an application which can be used for all
support exports (i.e. SUPPEXP)
- Create a package in this application using the XDEVELOP
template. Ignore all the Deployment Tool settings shown (they are not
necessary) and just add the initial Form or Function using the
"Select Repository Objects" toolbar button.
- Once the start form/function has been selected, ensure that
all the dependant objects are included in the package by
selecting the Cross References toolbar button from the object
selection screen. Also ensure that selection is cascaded. E.g. For a Component:
Note: The "Include file data" is unchecked. In a development export, OAMs are not shipped, so file data cannot be included (the package build will not succeed)
- Save the Package and then build it.
- Now to send the package to support, run Windows Explorer and navigate to
the packages directory of the LANSA
development environment - e.g.
(in V12 it is possible to right-click on the package in the deployment tool and select "Package Directory...")
- Add the Internal directory to a compressed folder (Zipped folder). All
other files/directories are not necessary.
- The resultant zip file can be moved to wherever necessary. End user just unzips this file and uses the standard LANSA LIMPORT facility to import the object definitions.