Change the Portal Login Logo

It's a Portable Network Graphic (.png) called login.png in $WEBDIR/lawson/portal/images

Thanks Gary!  I'll give that a try.

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.

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?

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.

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.

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.

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?

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.

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.

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.

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.)

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?

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.

David: Is that a global change? We'd like to do that (change the background color on the forms) for the same reason!!

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.

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.

Very helpful info. The lawform.css has changed quite a bit since 2012, but the basic change is the same.

Here is what we did to change the background color to 'pink': search for div.mainStyle and add the highlighted line.