Ifs *libl

[BMDUSA]

Is there a way to have Valence search multiple HTML PATHs to find the HTML source for Apps? The source would be found the same way as *LIBL works.

For example:

Search the QC path. If not found, search the Production path.
[HTML_QC_PATH]/examples/layouts/accordion.html
[HTML_Production_PATH]/examples/layouts/accordion.html

We are going to have at least two instances of Valence (Production and QC). The way it looks now is that both instances will have to have the full complement of HTML source to make each instance work.

[robert.swanson]

Unfortunately there's no library list equivalent for the front-end IFS directories that we know of. Though it would be possible to create logic for deriving the location of each Valence app's initial html file on the back-end (i.e., via VVCALL) so that the system would first try the QC directory, deferring to Production directory when not found, such a solution wouldn't work for every scenario. Any source file includes in the initial html file go straight through the Alias mappings in the Apache httpd configuration to a specific directory on the IFS. To our knowledge there is no way to get an Alias directive to work like a library list.

Because of that, we typically keep both a production version and a test version of the front-end source files on the systems we work on. Of course, for the back-end RPG programs you have the luxury of using the library list hierarchy for test programs (a feature we IBM i developers should never take for granted), but unfortunately such an option is not available for the front-end source. If you should happen to come up with a better solution we'd be interested in hearing about it!