The system name as displayed in such places as the title
of each page, mail notifications, as well as on login
and logout pages can be changed by an Ozibug
Administrator from within the system preferences page.
This allows the corporate name and/or purpose of the
Ozibug instance to be reflected.
The sequence for changing the system name can be seen
below.
Login as administrator and select the system
preferences option.
This is the represented by the following icon.
Change the system name preference field as required.
Select the update button and the
changes are saved. The title seen in the title
bar of your browser window should now be displaying
the new system name.
The images displayed at the left hand side of the top
navigation panel and in the center panel on a number of
pages (eg., login, welcome, logout) can be changed
by setting the corresponding system preferences. The
tooltip and url invoked from clicking on the header
image can also be changed. This allows additional
control of a corporate look and feel.
The sequence for changing the images can be seen below.
Place the custom image file(s) in the images
directory. Either a single image or two separate
images can be used, however inappropriate sized
images can adversely affect the presentation. The
default Ozibug header and body images are 128x40
and 128x332 pixels respectively.
This is the directory usually located under
the servlet context directory which will have
the following path
OZIBUG_HOME/images
where OZIBUG_HOME is the
directory where the Ozibug war file was
unzipped (or expanded) in.
Update the required preferences as described above.
Note: Only the relative filename
of the image(s) should be specified.
The header and footer of the login page can be changed
by setting the corresponding system preferences.
This feature allows additional information to be
included and displayed on the system wide login page,
such as links to other applications or projects or
perhaps some company specific information.
Note: you should never change the
original template files that are shipped with Ozibug.
You should create new files and change the configuration
so that you can always fallback to the shipped files.
The sequence for changing the login header or footer
can be seen below. The example shown here will add
a left hand sidebar containing hyperlinks to useful
CVS sites.
It will look similar to
this.
Create a login header file with the following
contents.
The tag <tag.1/> is used as a
placeholder for the title "System Name Login" which
defaults to Ozibug Login.
This tag does not need to be present.
Refer to
System Name
for details on how to change the system name.
Create a login footer file with the following
contents.
The footer forms the bottom of the table started
in the header which encapsulate the application
output.
The tags in this file are used as placeholders
for the following text.
<tag.1/> - System name
<tag.2/> - I18N phrase All rights reserved
<tag.3/> - Served by line
<tag.4/> - Current year
These tags do not need to be present.
Place the two files in the templates directory.
This is the directory usually located under
the servlet context directory which will have
the following path
OZIBUG_HOME/WEB-INF/templates
where OZIBUG_HOME is the
directory where the Ozibug war file was
unzipped (or expanded) in.
Update the header/footer preferences as described
above.
Note: Only the relative filename
of the template(s) should be specified.
Now try logging out and selecting the login page.
You should see your new handiwork displayed.
The header and footer of the logout page can be changed
by setting the corresponding system preferences.
This is very similar to customizing the login page.
Refer to Login Page for details.
The common footer is a snippet of html that is
responsible for the display of the footer while the user
is actually logged in and using the Ozibug application.
This can be changed by setting the corresponding system
preferences, which is very similar to customizing the
login page. Refer to Login Page
for details.
As the user will actually be inside the Ozibug
application then care should be taken to make sure that
any hyperlinks
included in this html open into a new browser window.
This can be done by specifying the value pair
target="_blank" inside the <a> element of
each link.
The following example shown will add some useful CVS
to useful CVS sites. This line is displayed above
the standard footer information. It will look similar
to
this.
