- Simple - this involves the replacement of images, and changes to the CSS files used by the standard login page, without having to write a custom page. Generally this option is used for quick 'mock ups' but not the final restyled product.
- Complete - this involves writing a custom .jsp file to replace the standard page. This method requires more technical knowledge, and more time.
(Yellowfin\appserver\webapps\ROOT\customimages)with your customised versions:
You will need to clear your browser cache once replacing these images in order for them to appear.
Note: the images you wish to use as replacements will need to have the same name as the files listed above in order for the page to pick them up. You no longer have to overwrite the originals, simply place your new images in the custom directory. This will mean that they will not be overwritten during the upgrade process.
Firstly, you will need to rename the login file to something other than
index_mi.jsp, for example
login_companyName.jsp. You will then need to place your login file in the Yellowfin ROOT directory (
In order to ensure Yellowfin uses this file instead of the standard option, you will need to complete the following while Yellowfin is not running:
- Stop Yellowfin
web.xmlfile found in
Yellowfin\appserver\webapps\ROOT\WEB-INFand locate the following:
welcome-filenode to reference your new login page's name. For example:
- Save the changes to the
- Edit your new login page, locating any references to
index_mi.jspand update to your login page name. For example:
- Save the changes to your login page.
- In order to ensure your page is used once a user logs out, as well as the initial log in, a change needs to be made in the Yellowfin Configuration DB. In the DB:
Configurationtable, locate the record where
ConfigCode = 'LOGONPAGE'and update the
ConfigData = 'login_companyName.jsp'using:
- Restart Yellowfin