test

Sun Java System Portal Server 7.2 Technical Reference

File Lookup Scenario

The Portal Server software uses the lookup scenario outlined in this section to find the JSPs it needs. Use this order to decide the final location of your own JSPs.

Example 69–1 Template File Lookup Scenario


            
desktoptype_
            locale/
            channelname/
            clientPath

            desktoptype_
            locale/
            provider/
            clientPath

            desktoptype_
            locale/
            channelname

            desktoptype_
            locale/
            provider

            desktoptype_
            locale/
            clientPath

            desktoptype_
            locale

            desktoptype/
            channelname/
            clientPath

            desktoptype/
            provider/
            clientPath

            desktoptype/
            channelname

            desktoptype/
            provider

            desktoptype/
            clientPath

            desktoptype
default_
            locale/
            channelname/
            clientPath
default_
            locale/
            provider/
            clientPath
default_
            locale/channelname
default_
            locale/
            provider
default_
            locale/
            clientPath
default_
            locale
default/
            channelname/
            clientPath
default/
            provider/
            clientPath
default/
            channelname
default/
            provider
default/
            clientPath
default

            templateroot

If there is no clientPath specified, then the directory search order is as follows:

Example 69–2 Template File Lookup Scenario (no clientPath)


            
desktoptype_
            locale/
            channelname

            desktoptype_
            locale/
            provider

            desktoptype_
            locale

            desktoptype/
            channelname

            desktoptype/
            provider

            desktoptype
default_
            locale/
            channelname
default_
            locale/
            provider
default_
            locale
default/
            channelname
default/
            provider
default

            templateroot

The lookup scenario relies on the following parameters:

desktoptype

For example default (set in the administration console). Note that desktop type is now a comma separated string list and so the look up will be based on the desktop type(s) that are defined in the desktoptype attribute.

locale

Preferred locale is the user’s locale. For example, en_US (set by users through the administration console in the “User” setting)

clientPath

This is an optional file-path containing client-specific templates; for example, html (set through the administration console Client Detection service)

channelname

This is the name of the channel; for example, newSingleContainer (set in the display profile)

provider

This is the provider name; for example, JSPSingleContainerProvider (set in the display profile)

templateroot

This is defined in the desktopconfig.properties file. The root of the search directory (default value of /var/opt/SUNWportal/portals/<portal_id>/desktop/) can be changed by modifying the templateBaseDir property in the desktopconfig.properties file.