Skip to Content

Please find below details steps for customizing logon page on Portal 7.3.

1. Locate the WAR file.

First step is to get the WAR file delievered by SAP for logon page to customize it.

Copy the war file tc~sec~ume~logon~ui.war to your local machine from

<Installation drive>:\usr\sap\<SID>\J00\j2ee\cluster\apps\sap.com\com.sap.security.core.logon
\servlet_jsp\logon_ui_resources\tc~sec~ume~logon~ui.war

2. Import the WAR file

Next we have to import the WAR file into NWDS by going to: File –> Import –>Web –> War File

/wp-content/uploads/2012/05/1_100555.jpg

     Select the WAR file from the local system.

/wp-content/uploads/2012/05/2_100613.jpg

    As EAR format can be deployed on JEE server, corresponding EAR project has to be created.

   For this, check the “Add project to an EAR “checkbox as above and specify suitable name in “EAR project name “based on the

   WAR project name.

   Click Finish to create both WAR and EAR projects.

/wp-content/uploads/2012/05/3_100614.jpg

    Expand the WAR project.

/wp-content/uploads/2012/05/4_100615.jpg

At this point you will notice errors in the project. To remove these errors follow the next step.

3. Adding the required JAR file to remove the Errors.

     a. Next you need to locate the Jar file “tc~sec~ume~logon~logic_api.jar” on which the WAR file is dependent from the following location:

     <drive>\usr\sap\<SID>\J00\j2ee\cluster\apps\sap.com\com.sap.security.core.logon\servlet_jsp\logon_app\root\WEB-INF\lib

    

     Copy the tc~sec~ume~logon~logic_api.jar” file to the WebContent\WEB-INF\lib folder of the WAR project in NWDS.

/wp-content/uploads/2012/05/5_100616.jpg

    b. This Jar file has also to be added in the build path of WAR file.

         Right Click the WAR project and select Build Path –> Configure Build Path.

/wp-content/uploads/2012/05/6_100617.jpg

     c. Click on Libraries tab.Click on “Add External  Jars”  and select the JAR file “tc~sec~ume~logon~logic_api.jar” from local system and “Add” to   get   the following screen:

/wp-content/uploads/2012/05/7_100618.jpg

Once done you will notice that all errors have gone !!

4. Make Changes to Layout

     a.  Now its time to start making the desired changes to the layout. In our example we are changing the branding image

          on the Logon screen. We have copied the image “hearts.jpg” to the folder WebContent\layout

/wp-content/uploads/2012/05/8_100622.jpg

SAP delivered image  branding-image-portals.jpg has dimension  290X360 px . If you select a bigger image it will get truncated based on the mentioned dimensions. To change the dimensions you need to edit the element urBrandImage in css file

urBrandImage{overflow:hidden;width:290px;height:360px}

b. After the changes have been made, we need to be sure that WAR project is updated in the EAR project and latest changes are

   picked up. For this Right Click on WAR project and select Java EE Tools –>Update EAR Libraries.

/wp-content/uploads/2012/05/9_100623.jpg

5. Configuring deployment descriptors

         

          Next we need to configure 2 deployment descriptors of the EAR application as below:

         

          a. application-j2ee-engine.xml

          b. application.xml

/wp-content/uploads/2012/05/10_100624.jpg

     a.  Configuring application-j2ee-engine.xml

 

        In the EAR, view the General tab of the file <project_name>/EARContent/META-INF/application-j2ee-engine.xml. 

          i. Enter a provider name for your application.This is usually domain name of the client.

             The provider name defines your namespace where your applications reside on the AS Java.

              If you enter “example.com”, the application deploys to the following path: <ASJava_Installation>/j2ee/cluster/apps/example.com/<project_name>

        ii . Next we need to add reference to the standard application com.sap.security.core.logon

               Choose References and choose +  with the quick info text Add element

         iii.  Choose Create new and enter the required data.

   

Reference Data for the Logon Application

Field Name

Data

Reference target

com.sap.security.core.logon

Reference type

hard

Reference target type

application

Provider name

sap.com

/wp-content/uploads/2012/05/11_100625.jpg

This will generate the XML in background which can be displayed in the SOURCE tab :

<?xml version=”1.0″ encoding=”UTF-8″ standalone=”no”?>

<application-j2ee-engine

      xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance

      xsi:noNamespaceSchemaLocation=“application-j2ee-engine.xsd”>

      <reference

            reference-type=“hard”>

            <reference-target

                  provider-name=“sap.com”

                  target-type=“application”>com.sap.security.core.logon</reference-target>

      </reference>

      <provider-name>newLogon.com</provider-name>

</application-j2ee-engine>

  b.. Configuring application.xml

In the EAR, edit the file <project_name>/EARContent/META-INF/application.xml, and define the URL alias and for your custom logon UI.

Double click on application.xml and go to Modules tab . Select the WAR file and enter the “Context Root” field for example : new_logon

/wp-content/uploads/2012/05/12_100626.jpg

We have to provide this alias name later in NWA so please make a note of it.

6. Creating the deployable EAR file

     Next we need to create a deployable EAR file . For this right Click on EAR project and select Export –>SAP EAR file

/wp-content/uploads/2012/05/13_100627.jpg

7. Deploying the EAR file

     Right click on the EAR project and select Run As –> Run on server

     Enter the credentials of the server and file will get deployed on the server with a success message.

     You might get an Error screen in NWDS after deployment as below however you can ignore it.

/wp-content/uploads/2012/05/14_100628.jpg

8. Configuring UME properties in NWA

     Navigate to the following URL to modify UME properties through Netweaver Administrator

     http://<host>:<port>/nwa/auth

     a. Change the property Alias of the aplication for customizing login pages (ume.logon.application.ui_resources_alias)                

          to custom  application “ new_logon” which we mentioned previously  in the Context root of application.xml

     b.  Change the property Path or URL to the branding image (ume.logon.branding_image) to “layout/hearts.jpg”

/wp-content/uploads/2012/05/15_100629.jpg

/wp-content/uploads/2012/05/17_100632.jpg

Hurray!!!  We have successfully customized the Logon Screen …

9. Next aim is to have a custom text or Notice on the logon page. 

Please add the following code after line 44 in the logon.jsp.

<!– ********************************************* –>

    <!–  disclaimer notice                         –>

                <tr>

      <td class=”urLblStdNew”>

        <span ><b>Notice for All Users</b>

                      <br><br>Paste your content here.

        </span>

      </td>

    </tr>    

<!– ********************************************* –>

Save the new values and restart the portal server.

/wp-content/uploads/2012/05/18_100633.jpg

This finishes (or rather begins) our journey with the customization of Logon page …. !!!

To report this post you need to login first.

45 Comments

You must be Logged on to comment or reply to a post.

  1. Kiran Bhonsley

    Have you tried changing the Copyright message in logonLabels_<loclae>.properties files?Does not appear the changes take effect. Any suggestions?

    (0) 
    1. NS Hussain

      Hi kiran,

      I am facing the same problem

      tried changing the Copyright message in logonLabels_<loclae>.properties files..  But the changes are not appearing… Any suggestions?

      Regards,

      NS

      (0) 
  2. NS Hussain

    Hi,

    I am facing a problem

    tried changing the Copyright message in logonLabels_<loclae>.properties files..  But the changes are not appearing… Any suggestions?

    Regards,

    NS

    (0) 
    1. Boris Todorov

      If you’re doing this exercise in 7.31 you will face the issue of having errors even after adding the tc~sec~ume~logon~logic_api.jar file to the lib folder and the Java Build Path. This is due to having a mobile folder and some of the variables are already defined… NWDS cannot figure this out and thinks that the variables are not initialized although they are.

      Just ignore these errors and continue with the EAR and the rest of the step. When you deploy the changes you’ve done will be there.

      See this thread for more details on this issue: http://scn.sap.com/thread/3187490

      Regards,

      Boris

      (0) 
    2. Mahesh Chandra VVNS

      HI Kai,

      Do you find any solution to the mobile folder problem, i am getting the same error in NWDS 7.31 SP7, Added two Jar file but still errors in Mobile JSP files and Web INF JSp files..

      regards,

      mahesh

      (0) 
    1. Adam Tidwell

      Robert, thank you for this comment!  I spent two days trying to figure out why my changes weren’t showing up, and it was because I was using https.

      (0) 
  3. Hilco Broens

    The issue that changes to the logonLabels are not appearing is known and described in SAP Note 1072721 (Customized Logon UI Labels Ignored).

    The solution is to put them in the WEB-INF folder, after you have extracted them from tc~sec~ume~logon~ui_core.jar, which is inside tc~sec~ume~logon~ui.war file.

    Hilco

    (0) 
    1. Robert Altenstraßer

      Hi  Dan

      example: Impressum

      copy from tc~sec~ume~logon~ui~core.jar  the file logonLabels.properties

      to WebContent > WEB-INF

      Add this lines to the new copied file:

      IMPRESSUM=Imprint

      URL_IMPRESSUM=”myUrl_to_imprint_DE.html”

      in certLogonPage.jsp

      <a href=<%=logonLocale.get(“URL_IMPRESSUM”)%>target=”_blank”>                           <div class=”urCopyrightText”><%=logonLocale.get(“IMPRESSUM”)%></div> </a>


      Important:

      restart the logon App on the server:    /nwa/apps  > com.sap.security.core.logon



      Language topic:


      It will use the browser language..that means you have to add this lines in ALL language properties files… > see:tc~sec~ume~logon~ui~core.jar  > logonLabels_??.properties

      If you don´t do that, you get lot of errors on the portal ( in NWA > LogViewer > System Logs and Traces :    ” Resource (IMPRESSUM) not found in properties files-IMPRESSUM “

      The default properties file is  logonLabels.properties  ( means: if there is no properties file for the browser-language it will use this )

      Maybe someone in the SCN  knows how to de-activate the not used language so it have to use only the default properties file: logonLabels.properties.

      Robert

      (0) 
  4. chandan mishra

    Really helpful article for the all the Netweaver people.

    I have used your customization process and it worked well with Netweaver 7.3 But it is not working with 7.4. After adding JAR files: tc~sec~ume~logon~logic_api  and tc~sec~ume~logon~ui_core , Errors with WAR files in NWDS do not removed completely.

    Still I can see the errors with folder “Java Resources” and “files in mobile folder”

    Can you help me out on this.

    Regards,

    Chandan

    (0) 
      1. chandan mishra

        Hi Senol,

        Yes I have resolved the issue and deployed the WAR file back to production. Actually, you do not need to worry about the errors in JAVA files. Just comment all the errors lines as these are useless code and have no resembles in the process. You will have error in 5-6 files, open all the files and make them commented. Edit the file according to requirement and upload to the server.

        Please let me know if problem still persist.

        Regards

        Chandan

        (0) 
  5. Manuel-Jeremy Schaffner

    To add/use reset password functionality for end users (resetPasswordPage.jsp in the above mentioned tc~sec~ume~logon~ui.war of com.sap.security.core.logon), you can add the following code to certLogonPage.jsp (https) or logonPage.jsp (http):

    <!– logon help –>

    <tr><td align=”left” colspan=”3″>

    <span class=”urLblStdBar”><%=logonLocale.get(“LOGON_IN_PROBLEM”)%></span><a href=”j_security_check?helpActionPage=PASSWORD_RESET” class=”urLnk”><span class=”urTxtStd”><%=logonLocale.get(“REQUEST_PASSWORD_RESET”)%></span></a>                                                  

    </td></tr>

    This displays the password reset functionality under the respective application path FQDN/<appl-context-root>/j_securoty_check and requires only FQDN/logon_ui_resources/.. as an additional path – that might be helpful in scenarios where the webdynpro-resources are not open/accessible to public.

    Configuring Legacy Logon Help – Identity Management – SAP Library

    Using the new password reset functionality (“support link”: Enabling Users to Reset Their Own Password – Identity Management – SAP Library and Configuring Logon Help – Identity Management – SAP Library ) opens an new window and then displays a WebDynpro-application that looks quite different to the logon screen. That WebDynpro-application needs access to /webdynpro/dispatcher/sap.com/tc~sec~ume~wd~enduser/* and /com.sap.ui.lightspeed/* .

    Configuring the Logon Screen – Identity Management – SAP Library

    Regards,

    Manuel

    (0) 
    1. Kai Unewisse

      Remove the tag with your own or check if changing the key username in the property will has the value “User” and change to text what you need               .


      <sap:label type=”username” styleClass=”urLblStdNew” flagReqClass=”urLblReq”/>

      (0) 
  6. Kishore Yennam

    Hi Purav,

    I followed the steps and customized the logon page and while deploying the ear file, i was facing an issue “error during deployment”.

    Appreciate your help in this regard.

    Thanks,

    Gowri

    Logonpage error.jpg

    (0) 
    1. Kai Unewisse

      Hi,

      Can you please provide the fitting content from the <NWDS folder>\log\dc_log of the log or trc files .        

      Regards,

      Kai

      (0) 
      1. Kishore Yennam

        Hi Kai,

        Here I am attaching the log from the NWDS Log. However, to give more info. on this issue, I have done the changes in sandbox system and it was successful, When i am trying to deploy in DEV environment, it was giving the error. I have checked the P4 port.When i telnet the port, it was working fine. we have changed the profile parameter from SDEFAULT to DEFAULT and restarted the system.Deploy error.jpg

        <!–LOGHEADER[START]/–>

        <!–HELP[Manual modification of the header may cause parsing problem!]/–>

        <!–LOGGINGVERSION[2.0.7.1006]/–>

        <!–NAME[D:\NWDS7.3\eclipse\log\dc_log\deploy_api.log]/–>

        <!–PATTERN[deploy_api.log]/–>

        <!–FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %M %m)]/–>

        <!–ENCODING[UTF8]/–>

        <!–FILESET[0, 5, 10485760]/–>

        <!–PREVIOUSFILE[deploy_api.4.log]/–>

        <!–NEXTFILE[deploy_api.1.log]/–>

        <!–LOGHEADER[END]/–>

        Jul 2, 2015 12:09:04 PM  Info: com.sap.ASJ.dpl_api.001023 Deployment of [name: ‘tc~sec~ume~logon~uiEAR’, vendor: ‘pdoLogonPage.com’ (sda)] finished.

        Jul 2, 2015 12:09:05 PM  Error: com.sap.ASJ.dpl_api.001041 Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [pdoLogonPage.com_tc~sec~ume~logon~uiEAR] failed]

        Jul 2, 2015 12:09:05 PM  Error: com.sap.ASJ.dpl_api.001042 Deployment Items status: [

        —– Sorted Items —–

          1. Client path ‘D:\PDOLOGONWORKSPACE\tc~sec~ume~logon~uiEAR\tc~sec~ume~logon~uiEAR.ear’

          Deploy status is ‘Aborted’

          SDA : name ‘tc~sec~ume~logon~uiEAR’, vendor ‘pdoLogonPage.com’, location ‘localhost’, version ‘2015.07.02.12.08.51’, software type (‘J2EE’, sub type ”), csn component ”, dependencies :[( name ‘com.sap.security.core.logon’, vendor ‘sap.com’) ]

        —– Deployment Items —–

          1. Client path ‘D:\PDOLOGONWORKSPACE\tc~sec~ume~logon~uiEAR\tc~sec~ume~logon~uiEAR.ear’

          Deploy status is ‘Aborted’

          Description:’1. Exception occurred during ws clients deployment. Unable to extract ws clients deployment data for archive tc~sec~ume~logon~ui.war, application pdoLogonPage.com/tc~sec~ume~logon~uiEAR.

          -> Can’t transform a Source of type javax.xml.transform.stax.StAXSource’.

          SDA : name ‘tc~sec~ume~logon~uiEAR’, vendor ‘pdoLogonPage.com’, location ‘localhost’, version ‘2015.07.02.12.08.51’, software type (‘J2EE’, sub type ”), csn component ”, dependencies :[( name ‘com.sap.security.core.logon’, vendor ‘sap.com’) ]

          Time statistics( ms ):

          1.validate : -1

          1.1.Resolve dependencies : 1

          1.2.deployment : 846

          1.2.1.Notify:Event triggered : 118

          1.2.2.Bulk deployment : 719

          1.2.2.1.Perform delivery : 719

          1.2.2.1.1.Application Deployer : 712

          1.2.3.Notify:Event performed : 8

          1.3.Post process : 1

          1.3.1.Starting : 1

        ]

        Jul 2, 2015 1:45:00 PM   Info: com.sap.ASJ.dpl_api.001023 Deployment of [name: ‘tc~sec~ume~logon~uiEAR’, vendor: ‘pdoLogonPage.com’ (sda)] finished.

        Jul 2, 2015 1:45:00 PM   Error: com.sap.ASJ.dpl_api.001041 Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [pdoLogonPage.com_tc~sec~ume~logon~uiEAR] failed]

        Jul 2, 2015 1:45:00 PM   Error: com.sap.ASJ.dpl_api.001042 Deployment Items status: [

        —– Sorted Items —–

          1. Client path ‘D:\PDOLOGONWORKSPACE\tc~sec~ume~logon~uiEAR\tc~sec~ume~logon~uiEAR.ear’

          Deploy status is ‘Aborted’

          SDA : name ‘tc~sec~ume~logon~uiEAR’, vendor ‘pdoLogonPage.com’, location ‘localhost’, version ‘2015.07.02.13.44.53’, software type (‘J2EE’, sub type ”), csn component ”, dependencies :[( name ‘com.sap.security.core.logon’, vendor ‘sap.com’) ]

        —– Deployment Items —–

          1. Client path ‘D:\PDOLOGONWORKSPACE\tc~sec~ume~logon~uiEAR\tc~sec~ume~logon~uiEAR.ear’

          Deploy status is ‘Aborted’

          Description:’1. Exception occurred during ws clients deployment. Unable to extract ws clients deployment data for archive tc~sec~ume~logon~ui.war, application pdoLogonPage.com/tc~sec~ume~logon~uiEAR.

          -> Can’t transform a Source of type javax.xml.transform.stax.StAXSource’.

          SDA : name ‘tc~sec~ume~logon~uiEAR’, vendor ‘pdoLogonPage.com’, location ‘localhost’, version ‘2015.07.02.13.44.53’, software type (‘J2EE’, sub type ”), csn component ”, dependencies :[( name ‘com.sap.security.core.logon’, vendor ‘sap.com’) ]

          Time statistics( ms ):

          1.validate : -1

          1.1.deployment : 533

          1.1.1.Notify:Event triggered : 39

          1.1.2.Bulk deployment : 486

          1.1.2.1.Perform delivery : 486

          1.1.2.1.1.Application Deployer : 485

        (0) 
        1. Kai Unewisse

          HI, there are some changes with service/protectedwebmethods

          I noticed that, when updating to 7.31.14 :

          A fix was :

          service/protectedwebmethods = SDEFAULT –ParameterValue


          Since this is not related to the customization, change the value or check SAP notes.

          For further questions, open a discussion thread.


          Regards,

          Kai

          (0) 
  7. rakesh singh

    Thanks! for the article Purav 🙂

    Explained nicely in detail with screens! It will surely help as some new changes happened after 7.3.

    Regards,

    Rakesh

    (0) 
  8. Philip Johnston

    Thanks for sharing these instructions.  Do these instructions also cover the process for 7.4?  Performing these steps, I receive 206 JSP errors related mostly to device type.  thanks, Phil

    (0) 
          1. Thruna Shanmuga

            Hi,

            We are on NW 7.4.

            I followed the steps as per this blog to change the branding image and change the URL for Get Support link in the logon page (logonPage.jsp & certLogonPage.jsp).

            I successfully deployed on the server.

            Modified UME properties in NWA. Removed the “/”.

            I can see the new branding image only in http://<>/nwa/auth logon page not the portal logon page (no image at all). Get support link changes also not appearing in the Portal logon page.

            Thanks

            Thruna

            (0) 
  9. Fisher Yu

    Hi all, after `7deploying…`, I’ve got an error:

    providename. com/com.sap.security.core.logon  not found in the admitted batch items and repository…

    Appreciate any help

    Thanks

    (0) 
  10. sha sk

    Hi Team,

    1.I have customized logon page SAP EP 7.3 in DEV sys.

    Download the ear file from <installation driver>user/sap/sid/j00/j2ee/cluster/apps/sap.com

    Import into nwds and changes and deployed the ear file.

    working fine in dev what i have customized.no issue from dev but i want to find where it is stored ear file and jar file.

    i am not able to find the deployed ear file.using UNIX

    Could you please guide on this?


    2.the file moved and deployed into QA here is not displayed what i have made changes in logon page but instead of customized logon page here displayed SAP standard logon page.

    dev is successfully displayed.

    i am not able to find the issue

    Could you please guide on what is issue in QA?

    urgent requirement..

    (0) 

Leave a Reply