cancel
Showing results for 
Search instead for 
Did you mean: 

Changes made in logon.jsp & default.css are not appearing on Infoview Page

Former Member
0 Kudos
Hi All,
Background:
Due project/ brand specific requirements we've modified our InfoView Logon Page with our own logos, custom messages & etc. as it’s very important for our company.
Issue:
Changes made in logon.jsp (Tomcat/WebApps/InfoViewApp) & defaultt.css (InfoViewApp/res/schema.blue) like adding background image on logon page, changing logon box frame size & etc. are not appearing on InfoView logon page after modifying.
Environment:
2 – CMS in cluster 3.1 SP3 on Windows 2003
2 – Web Layer (Apache 2.2+ Tomcat 5.5) on Windows 2003; It’s separately installed with Load Balancer & configured redirected URL.
2 – Reporting Server   

Testing & Observation
:
  1. All the changes made in logon.jsp, default.css & web.xml are working perfectly fine on our Development Environment which is running on a single box.
  2. Same changes copied on both the tomcats of UAT/ PROD Environments are not appearing.
  3. Noticed that changes made in web.xml of (UAT/ PROD) for app.shortname, CMS entries & etc are working fine; however logon.jsp & default.css changes it’s not picking up.
  4. Tried opening InfoView Page in many browsers, but got same results.
  5. Checked the view source option of the page from the browser after launching the InfoView page shows the entries of changes we made in the respective files, but background image, logon box alignment and etc. doesn’t get changed at all.

Question
:
Q1. Is this happening due to re-directed URL we are using on our UAT/ PROD?
Q2. What other configuration needs to be done to avail these changes in case of 2 tomcats running with Load balancer on a environment.
Q3. What could be the reason InfoView is not picking up the changes of logon.jsp & default.css?

Please help.

Nikhil

Accepted Solutions (0)

Answers (2)

Answers (2)

denis_konovalov
Active Contributor
0 Kudos

If you mention load balancer and apache web server, then you have minimum 4 pieces in this puzzle :
1. Load Balancer - typicaly will have nothing to do with this issue

2. Apache Web server - if you did split deployment (see Web apps deployment guide) and deployed static content to it - then changes you made in tomcat/webapps will not be enough.

3. Tomcat #1

4. Tomcat #2

Have you made changes on both Tomcats ?

Does your Apache has static content deployed ?

If you have LB - why do you have Apache Web server as well ?

Are you sure when you connect to LB URL your request goes to Tomcat server you have updated ?

Are there any other devices that might have old cached pages ?

Did you restart both tomcats after making a change ?

Former Member
0 Kudos

Nikhil,

The same changes are working fine in UAT so it means that your changes are correct. But in PROD if u hv load balencer, what is the webserver used for load balancing? if its Apache for example the the static contains will be there for infoview in apaches folder and that's why its not working.

Thank You,

Amol

Former Member
0 Kudos

Amol,

Thank you for your response.

The changes we have done/ tested are in DEV, which has BO + Tomcat on single box.

In case of UAT & PROD, we have Load Balancer and Web Server is Apache 2.2 are using on both of them.

Can you help with 'which static content/ folder you are referring to'?

Thank you,

Nikhil

CdnConnection
Active Contributor
0 Kudos

Nikhil,

    Some of the static content you need to look at is the BOBJ Logo's must be replaced.  Look for  login_banner_SAPBOBJ.gif and replace it with your custom logo file.

Regards,

Ajay Gupta

Hope this helps your issue.

Former Member
0 Kudos

Ajay,

I was referring to background image which we have added on Login Page (which should appear behind the logon box frame) by calling through a function in logon.jsp

Logos have been already replaced long back.

Thank you,

Nikhil

CdnConnection
Active Contributor
0 Kudos

Nikhil,

     All InfoView related logo's and images are located in \webapps\infoviewapp\res\schema.blue folder unless your CSS file is pointing to another location.  The default.css file is also located within the same folder.  You will need to copy all you changes Images and custom files from Tomcat to the Apache web container.

To make things easier their is an easier way to bridge Apache and Tomcat without coping any static pages to Apache.

Any reason why you are choose to copy static pages to Apache ?

Regards,

Ajay