Skip to Content

Modifying The Logon Par(or customising the Logon Screen)—Part2

In my last blog whatever I wrote was an elementary kind of thing if you gaze at the word customizing .Iam just going to focus on  how does the Umlogon.jsp takes care of the complete working of the logon screen and also the common mistake which we make.Before I begin please go through the structure of the Logon.par

I have almost written what I intended  ,any mistakes please let me know so that I can rectify It next time.

You must be Logged on to comment or reply to a post.
  • Manually copying files to folders under \usr\sap\\JCnn\j2ee\cluster\serverN\ should be avoided! If you add another server node, you won’t get them and if you install a dialog instance you won’t get them. I am surprised the files cannot be put into the PAR file…

    • Hi Michael,

      I know thats not one of the best practices,thats why i have mentioned that in the blog itself.I just wanted to give an alternative if anything of this sort happens.Aslo Michael if we just copy the “work” folder ,the rest of the folder structure is genreated when the par is coverted to bak .

  • Hi

    I don’t agree with copying files into the work folder. Also, the easiest method of changing the logon screen is to simply download the par file from the portal, unzip it and then import this par file into the NWDS. There are no java classes associated with this par file, as far as I can tell, and it simply consists of jsp files, stylesheets, javascript, and the .txt files you mentioned.

    You can easily change these text files and include your own HTML, as long as you know about HTML. All the .txt files are doing are providing a single place to add code, instead of having the same code in multiple places. Therefore, you can very easily change the complete layout, and even completely remove the import of the .txt files and create your own HTML layout.

    As for all of the files in the /irj/root/WEB-INF/portal/portalapps/ folder is because these files are located in the PORTAL-INF folder of the par file, and therefore during the import they are placed in the correct folder, exactly the same as the portalapp.xml file.

    You “SHOULD NEVER” have to copy files anywhere, which will generally not work very well in NW04 anyway because when the portal is started the binaries are synchronised from the database, and can easily be deleted at any time.


    • HI Darrell,

      Like i mentioned this is not one of the practises but can you just tel me what does these files do and the corresponding file do ,( Automatically generated by PRT JSP Engine).Also i do agree if we are using NWDS its quite easy to do .The purpose of Mine writing this blog was to give an alternative how to change it.
      Iam not diagreeing to whatever you have written thats absolutely correct.Also you forget to mention that it has jar files also which play a major role.

      • Hi,

        file “” is simply an automatically generated Java servlet based on JSP file “umLogonPage.jsp”. It will be updated automatically, whenever changed to the JSP file it is based on are detected.

        And, me, too 🙂 , I encourage you to simply import the PAR file in NWDS, perform your changes there and create a new file. This also has the benefit of being much easier transportable to another system (QA, PRD …)


      • As Dominic mentioned the work folder is created because any J2EE servlet, including webas and Tomcat basically compile a JSP into a servlet. It cannot simply run a JSP page. So, they engines normally have some sort of JSP compiler, which the compile the JSP pages into a .java and .class file. You can generally delete the work folder any time you like, and normally the next time you access any JSP files, the work folder will be re-created for you.

        Also, there don’t seem to be any jar files in my installation of NW04 for the component.

        • HI Darell,

          Thanks, I knew this but in my case it was like these files were not being generated at the runtime so the jsp were not functioning properly.
          Also i presuume we have and umelogonbase.jar which provides the Ume right (are there inside the poratl-inf/lib)