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
Select the WAR file from the local system.
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.
Expand the WAR project.
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.
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.
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:
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
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.
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
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 |
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
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
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.
8. Configuring UME properties in NWA
Navigate to the following URL to modify UME properties through Netweaver Administrator
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”
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.
This finishes (or rather begins) our journey with the customization of Logon page …. !!!
- SAP Managed Tags:
46 Comments
