Change the Portal Login Logo
Last Post 05/30/2012 12:00 PM by Greg Moeller. 17 Replies.
Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Woozy
Private
Private
Veteran Member
(2673 points)
Veteran Member
Posts:425


Send Message:

--
07/09/2009 9:47 AM
    Can anyone tell me how to change the logo image for the Portal Login page on 9.0.1?  I've been able to change the portal header logo (top left corner), but not the big logo on the http:///lawson/portal login page.

    I've seached MyLawson and found some articles relating to 3.x, but nothing for the later versions.

    I did a "view source" for the login page, and it appears to be pointing to $WEBDIR/lawson/portal/images/logo.gif, which is the same file used for the top left image, but this login page image didn't change.

    Any thoughts?  Thanks!
    Kelly Meade
    J. R. Simplot Company
    Boise, ID

    DB2-AIX LSF 9.0.1.11, S3 Apps 9.0.1.7, PFI 9.0.1, LBI
    Landmark 10.1.1.9, TM 10.2, IPA 10.1.1.9
    Gary Davies
    Veteran Member
    (738 points)
    Veteran Member
    Posts:248


    Send Message:

    --
    07/09/2009 10:13 AM
    It's a Portable Network Graphic (.png) called login.png in $WEBDIR/lawson/portal/images
    Woozy
    Private
    Private
    Veteran Member
    (2673 points)
    Veteran Member
    Posts:425


    Send Message:

    --
    07/09/2009 10:37 AM
    Thanks Gary!  I'll give that a try.
    Kelly Meade
    J. R. Simplot Company
    Boise, ID

    DB2-AIX LSF 9.0.1.11, S3 Apps 9.0.1.7, PFI 9.0.1, LBI
    Landmark 10.1.1.9, TM 10.2, IPA 10.1.1.9
    John Henley
    Private
    Private
    Senior Member
    (8777 points)
    Senior Member
    Posts:2943


    Send Message:

    --
    07/09/2009 11:11 AM
    Are you referring to /sso/login.png ... http://server/sso/login.png
    If so, you would have to change that image, and repackage/redeploy the .ear each time you patch LSF9...not a win.
    Thanks for using the LawsonGuru.com forums!
    John
    Norm
    Private
    Private
    Veteran Member
    (114 points)
    Veteran Member
    Posts:38


    Send Message:

    --
    07/20/2009 12:44 PM
    In simpler days (8.0.3 environment and before), all I had to do was replace a simple .gif file with my own. I didn't even attempt that when I moved to LSF9.0.0, figuring I had enough problems with my upgrade already.

    Looking at it today, it doesn't seem like it's as complicated as John says. I was able to replace the login.png file where it gets deployed in WebSphere (101 character path name, what are those loonies at IBM thinking of?!) with a slighted modified version and it appears to work.

    So, I'm not clear on John's statement about the need to repackage and redeploy the the .ear file. It's seems similar to what we already have to do to get our RSS customizations back in. Every time we patch/upgrade RSS, there's a series of files we have to copy into the deployed directories.

    John, I'm a WebSphere rookie, what am I missing?
    John Henley
    Private
    Private
    Senior Member
    (8777 points)
    Senior Member
    Posts:2943


    Send Message:

    --
    07/20/2009 2:14 PM
    First, I must pontificate. I've never understood the incessant need for clients to "change the logo" on a vendor-supplied product such as Lawson. Yes, I know it's free advertising for the vendor, but is it really that important? I can't begin to tell you how many meetings I've been in with clients who have it in their "showstopper" list when getting ready to go-live! When you install Office, do you change the Microsoft logo? When you buy a car, do you change the nameplate or the hood ornament? (Please don't answer that, I know there are some of you out there...).

    Now, Norm you are correct in that it is just a file that is located in the deployed directories. However, it does need to be done each and every time you deploy. That, of course, assumes you are a simple deployment, with just one node/App Server. The idea behind WAS "deployment" is that you deploy the package (the .ear file), and WAS places all of the files into their correct locations, perhaps on multiple physical / logical servers. For that reason, the "proper" way to do it would be to extract the package files to another location, replace the desired files, re-package the .ear file, and re-deploy it.

    Even using the "proper" way, it's the same bad idea as implementing a custom index on a Lawson table directly in the database--rather than in dbdef. It will be gone (and probably not documented) when you install a patch, upgrade, etc.
    Thanks for using the LawsonGuru.com forums!
    John
    Ben Coonfield
    Private
    Private
    Veteran Member
    (414 points)
    Veteran Member
    Posts:144


    Send Message:

    --
    07/20/2009 3:23 PM
    If anyone wants to update the logo file directly, note that if you reinstall a EAR file and change the application name, the directory path of the files will change too. I don't know how many Lawson sites use the option to rename the application, but I normally do so to add the environment name to the app name.
    Joe O'Toole
    Private
    Private
    Veteran Member
    (706 points)
    Veteran Member
    Posts:278


    Send Message:

    --
    07/20/2009 4:18 PM
    I just wrote a little script that we run after deploying a new ear file that put's our custom PNG with our logo in place of the Lawson delivered one.
    MTFF
    Veteran Member
    (144 points)
    Veteran Member
    Posts:50


    Send Message:

    --
    07/20/2009 6:32 PM
    Two points to make.

    1. What happened to Lawson's own slogan "simplier is better" ?

    2. From the point of minimizing technical debt, changing the logo is not a win. I agree w/ the argument that if we don't change the logo for MS Office, why change Lawson?
    Joe O'Toole
    Private
    Private
    Veteran Member
    (706 points)
    Veteran Member
    Posts:278


    Send Message:

    --
    07/21/2009 10:24 AM
    For application users, keeping the logo might not be a big deal, but branding is very important in our organization. With Self service deployed as an app to our remote users the logo must have continuity.
    Norm
    Private
    Private
    Veteran Member
    (114 points)
    Veteran Member
    Posts:38


    Send Message:

    --
    07/21/2009 4:36 PM
    John, thanks for additional info. Hadn't dawned on me about the multiple nodes/appservers issue which we currently don't face but will face in the future. No need to worry about pontificating about modifications. I am with you brother, AMEN!

    In our case, back in the 8.0.3 days, we were looking to throw some additional text on that initial login screen. Since we were in the neighborhood already, it wasn't a big stretch to add the mod for the logo. Not using it currently, wish I could say that about the other mods I'm forced to migrate.

    From a System Administrator's standpoint, it's increasingly difficult to maintain a modified Lawson system. Much simpler ten years ago when all we had was LID and I lost the argument about modifications. Once the decision was made, you can never go back and just have to deal with the technical challenges. As Joe mentioned, you become an expert in scripts to help keep things straight.
    andrew
    Private
    Private
    Veteran Member
    (185 points)
    Veteran Member
    Posts:99


    Send Message:

    --
    12/09/2009 1:00 PM
    I would say the only thing that a company may need is to change the pay stub information in ESS, and add the company logo there.
    Shane Jones
    Private
    Private
    Veteran Member
    (1185 points)
    Veteran Member
    Posts:439


    Send Message:

    --
    12/09/2009 6:58 PM

    This was an interesting thread...   However, I have to disagree about MS-Office logos and Lawson logos.   The Lawson system when using ESS and MSS is an HR portal that should display your Company image.   It has much more to do with your delivery of information to associates then some of the other "business" systems.   

    While an argument could easily be made that Lawson should be viewed as any other business system - I have found that HR systems that have portals for employees usually are viewed as your HR brand.   If you build any other system and include your company logos and colors then the Lawson system looks out of place and you get questions about why a system that costs hundreds of thousands can't easily provide a pleasent front end that syncs with other systems.  

    (I hate that I have a bunch of different systems that make our information delivery a bit schizophrenic in thier branding.)

    Shane Jones
    Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
    Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
    ** Teach others to fish...
    Colin
    Private
    Private
    New Member
    (3 points)
    New Member
    Posts:1


    Send Message:

    --
    04/19/2012 9:43 AM
    I couldn't agree more with Shane. And to take it even a step further, when you get into Candidate Space do you want people thinking that they're applying for a job with Lawson, or with your organization?
    David Britton
    Private
    Private
    Veteran Member
    (106 points)
    Veteran Member
    Posts:44


    Send Message:

    --
    05/18/2012 12:42 PM
    I changed it on our Development/Test system to read DEVELOPMENT in lime green letters on a bright red background to emphasize to users which system they are in. I also changed the background color on the forms in development to pink for the same reason.
    Greg Moeller
    Private
    Private
    Veteran Member
    (3160 points)
    Veteran Member
    Posts:1124


    Send Message:

    --
    05/18/2012 3:14 PM
    David: Is that a global change? We'd like to do that (change the background color on the forms) for the same reason!!
    David Britton
    Private
    Private
    Veteran Member
    (106 points)
    Veteran Member
    Posts:44


    Send Message:

    --
    05/30/2012 9:25 AM
    Greg
    Sorry for the delay in responding. I have attached a document showing the changes I made.
    I show PO20.1 and PO10.1 as samples to show it is global.
    Attachments
    Greg Moeller
    Private
    Private
    Veteran Member
    (3160 points)
    Veteran Member
    Posts:1124


    Send Message:

    --
    05/30/2012 12:00 PM
    Thanks, David! Change it in one spot, and it affects all forms! Just what I wanted to hear. I've made a similar modification to our environment here.
    You are not authorized to post a reply.