Configuring Banner Messages Using JSP and TXT Files
 |
It is highly recommended to use the Windchill UI to configure the banner notification. For more information, see Configuring Banner Messages Using the Windchill UI. If you need advanced configurations, you can continue using the legacy method.
|
You can create a system wide banner message that will display on all the pages within the Windchill application.
Turning on the alert banner feature
1. Put the following line code into <Windchill>\codebase\netmarkets\jsp\util\begin_custom.jspf
<%@ include file="/netmarkets/jsp/util/banner_custom.jspf"%>
2. Restart the Embedded Servlet Engine.
Character Encoding Considerations
On recent versions of Tomcat the following line should be added to begin_custom.jspf to ensure that the character set is set to UTF-8. Otherwise content may not display correctly.
<%@ page contentType="text/html; charset=UTF-8" %>
Displaying the alert message on the top of Windchill UI pages
Write the alert message with html format into the following file: <Windchill>\codebase\netmarkets\jsp\util\banner.txt
For example:
<div
style="float:left;
clear: both;
position: absolute;
margin: 2px 170px;
padding: 3px;
border: 1px solid #000;
background-color: #fff;
top: 3px;
color: #006600;
font-weight: bold;
font-size: 12px;
z-index: 1000">
<font face="verdana">
<!-- Banner begins here -->
Windchill server will be down 1/1 for maintenance
<!-- Banner ends here -->
</font>
</div>
style="float:left;
clear: both;
position: absolute;
margin: 2px 170px;
padding: 3px;
border: 1px solid #000;
background-color: #fff;
top: 3px;
color: #006600;
font-weight: bold;
font-size: 12px;
z-index: 1000">
<font face="verdana">
<!-- Banner begins here -->
Windchill server will be down 1/1 for maintenance
<!-- Banner ends here -->
</font>
</div>
Removing the alert message from Windchill UI page
Set <Windchill>\codebase\netmarkets\jsp\util\banner.txt as empty file.
Turning off the alert banner feature
1. Set <Windchill>\codebase\netmarkets\jsp\util\begin_custom.jspf as an empty file
2. Restart the Embedded Servlet Engine.