Moving customizations to another environment

When working with Genie, all customizations for a particular screen are stored in an IFS file. There is one file per screen. The name of the file is the name of the screen that has been customized. The extension is .scn.

By default, a screen is given the name of the first field marked as an identifier, but can be changed to a more logical (but unique) name.

Open

In addition to storing 1 file per screen, Genie also maintains a global list file to keep track of all identifiers. The name of this file is screens.lst.

All files are stored in the Screens subdirectory of the Skin. For example, if the name of your Profound UI instance is PROFOUNDUI (the default name) and the name of your skin is MYSKIN, the customization files will be stored here: /www/profoundui/htdocs/profoundui/userdata/genie skins/MYSKIN/Screens.

When copying a screen from one Skin to another, both the .scn file must be copied and the screens.lst file must be updated. If you use the Genie Administrator to copy screens, this happens automatically. However, the Genie Administrator can only copy screens between Skins configured under the same HTTP instance.

Copying screens between different instances can be done manually. However, if you copy a new screen file into the screens directory from another environment manually, you will also need to update or rebuild the references in the screens.lst file. Profound UI provides a program to do this automatically. The syntax to call this program is as follows:

CALL PGM(PUI0002103) PARM('/www/PROFOUNDUI/htdocs/profoundui/userdata/genie skins/MYSKIN/Screens')

Where PROFOUNDUI is the name of the instance and MYSKIN is the name of the skin for which you are rebuilding the list file.