The Serena Release Control user interface runs as a custom shell on top of the SBM native interface. The display details are implemented using an HTML file hierarchy, with a wrapper file, wrapper.html, defining the common display elements and tabs. The wrapper file references separate files that define the details of each page.
A custom shell for an SBM application is a set of customized templates, styles, scripts and images plus SBM server-side scripts that put these elements together. SBM uses a templating engine to embed tags, for example $TAGNAME(), to obtain environment information dynamically from a process app.
Serena supplies a default shell to use with the SBM-based Serena Release Control UI to provide a user-friendly look and feel. You invoke the shell when you access Serena Release Control by specifying shell=customShellName at the end of the URL, where customShellName is by default rlm. For example:
http://server:port/tmtrack/tmtrack.dll?shell=rlm
When you install Serena Release Control, there are a set of shell folders in the SBM application folder, for example:
C:\Program Files\Serena\SBM
Containing custom templates, style sheets, and scripts. These are:
Templates:
…\Application Engine\template\shell\customShellName
Style Sheets:
…\Application Engine\bin\styles\shell\customShellName\
Images:
…\Application Engine\bin\images\shell\customShellName\
Scripts (if used):
…\Application Engine\bin\javascript\shell\customShellName\
In a default installation of Serena Release Control, customShellName is rlm.
To create your own custom shell, you need to create a corresponding set of folders with the name of your custom shell, and invoke it by adding shell=customShellName at the end of the URL when accessing the Serena Release Control UI.
It is necessary to create the folder under template for your custom shell name, but it is optional for the other folders, as the process application will search in the top-level folders under \bin for styles, JavaScript and images. However it is recommended that you use these folders. You will need to provide relative paths for elements other than templates in your pages and styles.
When displaying a customized page, SBM will first look for the page inside:
…SBM\Application Engine\template\shell\customShellName\
If the page is not found there, the page from the default location:
…SBM\Application Engine\template\"
will be used.
For example, when SSO is disabled, SBM uses loginform.htm as the login page. This page is stored in
…SBM\Application Engine\template\
To create custom login screen, put your own version of loginform.htm into
…SBM\Application Engine\template\shell\customShellName\