The basic rationale behind this blog is to make people accustomed with the logon screen and the widespread pit falls which we craft .For a start I thought this will be the classic way to begin as every thing in the portal begins with the logon par.
It is prudent to take the backup of the portal and the database before you make changes to the logon file.
Changing The branding Image :-
The Branding image can be change in two ways :-
a. The first method is a ghastly way of doing it .In this method we need copy the logon.par file and can change the image according to our desire.
1. Go to the file path
2. Open the folder
b. Navigate Till root folder through servlet-jsp/logon
c. Inside the root go to Layout folder
d. In the Layout folder there exists those branding images
e. Replace the branding Image (Keeping the same name of ur image as that of the existing one ).
3. Restart the J2ee engine and the Portal .
b. The second method gives us an option of customizing the Logon file the way we
i) The Logon screen files are in ( a zipped file) com.sap.portal.runtime.logon which can be copied from
b.) Choose the option PAR file. Select Next and a popup window
c) Fill in the details in the screen which poped up .
iv) If the Par file is imported without any errors then we are set to make changes in the jsp files and the images the jsp files can to seen in the NWDS navigate to the PORTAL-INF through the dist folder.
There are seven jsp files and four text files which comprises of basic functionality of the Logon Page.
The Links to all the jsp and the text files is through the UmLogonPage.Jsp , if any of the links has to be removed it can be done through this page(just remove the jsp tag for that particular page).
Changing The Text
Before we move on to changing the text it is necessary to know how does that text appear on the screen .The text is stored in umelogonbase.jar which is in the lib folder of PORTAL-INF.( There has to be two files umelogonbase.jar and com.sap.portal.runtime.logon_api.jar , if these files are not there ,then unzip the original par file and copy from them .If These files are not there then while deploying it will show Error).
Once you open the umelogonbase.jar file there are some properties file which define the messages according to the language.Locate logonLabels_en.properties which contains the message ¡§WELCOME¡¨ under xtit_WELCOME.
Change the message and save the file.
This message is called from umLogonTopArea.txt .This txt file is included in the UmLogon.
Deploying The New Par File :-
In order to Upload the new par we need to comfigure the deployment descriptor.For
this we will make use of the j2ee engine. STOP THE J2EE ENGINE AND PORTAL.
1. Open The offlinecfgeditor .bat under the directory
2. Switch to edit mode by clicking on the icon.it will open a confirmation dialog
3. Navigate till cluster_data/server/persistent/com.sap.security.core.ume.service
4. In the tree, select authschemes.xml and choose Download. Save the file (Since we
do not want to tamper the Initial setting swe will make Custoomized deployment
5. Open the file and replace the Occurrence of com.sap.poratl.runtime.logon with your par file name ( don¡¦t change the rest part such as basicauthentication),and save it with a new name.
6. Navigate till com.sap.security.core.ume.service. and choose create symbol from
the toolbar available.
Select the type File-entry.Click on the Upload and select the custom file (which
you have made).Press create and close the window.Check whether the new node
appears or not in the configuration tree.
„« Navigate till cluster_data/server/cfg/services.
„« Double click on the Property sheet of com.sap.security.core.ume.service.
„« Click on login. Authschemes.definition file .
„« Add the name of the xml file which you have created and Press apply custom.
„« Restart the Portal. That is often not done and the changes will not appear.
Common Errors :-
1) com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.ume.component.logon.SAPMLogonCertComponent of Portal Component my.new.logon.certlogon because: Could not find implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal..:– The Two jar files are umelogonbase.jar and com.sap.portal.runtime.logon_api.jar not available in the lib folder of PORATL-INF.
2) iView or component ¡VNA
The jsp tags has not been closed properly.