Portal Logon Customization

Hello,

We are on EP 7.0 SP 18.

In order to customize the portal login screen as per client requirement, instead of uploading the server on the server (which in our case is in a different continent) can I not do the following

1. Make the modifications to the jsp files

2. create the par file using winzip utility

3. go to system admin -- > support --> portal runtime --> admin console

4. Deploy the par using the archive uploader

Is a portal restart required for the changes to take effect and is the above mention steps good enough ?

Also is there a way to preview the changes made to the login screen before uploading it to the portal or everytime a small change is made the whole process of uploading the par to the portal is required ?

regards,

Sunil

SAP Managed Tags:
SAP Enterprise Portal

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (2)

Hi,

yes it is possible to view the changes made. For that add the Java deveoper role to your user and then Go to Java Develper->Portal Componenet Starter and viewer and then look for you deployed Par file and click on start. you will be able to view the changes you made.

Hope this Helps

~Hussain

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello,

Thanks for the response.

I am aware of all the blogs and articles on Logon Screen Customization.

However all of them refer to the approach of downloading the existing logon.par file and opening it in NWDS , making the modifications and then uploading it back to the server.

I wanted to know the following

a) is there a way to test the updated login page

b) instead of uploading the modified logon.par to the server can i not upload it on the portal itself using the archive uploader facility available under System Admin --> Support ?

Regarding the Java developer role I see the following 4 in my portal which one do i need to assign to test the login.par component ?

SAP_JAVA_NWADMIN_CENTRAL Central NetWeaver Administrator UME Database

SAP_JAVA_NWADMIN_CENTRAL_READONLY Central NetWeaver Administrator, read-only UME Database

SAP_JAVA_NWADMIN_LOCAL Local NetWeaver Administrator UME Database

SAP_JAVA_NWADMIN_LOCAL_READONLY Local NetWeaver Administrator, read-only UME Database

SAP_JAVA_SUPPORT Support role for using Solution Manager Diagnostics UME Database

Many thanks.

Regards,

Sunil

Hi,

a) is there a way to test the updated login page

Yes the above Procedure I mentioned can be used to test the Updated Login Page.

b) instead of uploading the modified logon.par to the server can i not upload it on the portal itself using the archive uploader facility available under System Admin -

As u mentioned you can do it from sys admin->support.

The roles mentioned by you will not help you. You need to have the Java Developer Role for that. For Java Developer role you need the Install the PDK ( Portal Development Kit ).

For More Infromation about PDK refer the below thread.

~Hussain.

I clicked on the link to download the PDK

Since we are on EP7.0 which PDK version I need to download

PDK 6.0 SP2 or PDK 6.0 SP14

So to recap, I can make the changes to the login.par and actually use the same name itself and upload it back using Archive uploader. This way no need to change the authen.xml file as it already points to the existing logon.par file ?

Ofcourse I make a backup of the existing logon file .

Now to test the change, I just download the correct version of the PDK and follow the instructions to get the java developer role.

I am wondering isn't this a better way of doing it as most articles talk about opening it in NWDS and then uploading it back to the server and restarting it.

Surely when modifying the logon page one needs adhoc previews esepcially since there is html involved. It would be rather tedious to each time upload it to the server and restart the engine ?.

Regards,

Sunil

Hi Sunil,

Do have a look at this page. It describes modifying the logon page and changing the authschemes.xml file as well.

http://help.sap.com/saphelp_nw70/helpdata/en/23/c0e240beb0702ae10000000a155106/content.htm

Since the logon page has jsp + html code you would have to deploy it to have a look at the changes you've done.

Thanks,

GLM

I am not very sure which version you have to download.

So to recap, I can make the changes to the login.par and actually use the same name itself and upload it back using Archive uploader. This way no need to change the authen.xml file as it already points to the existing logon.par file ?

yes the above can work. But the best way to do it is to rename the file and uplaod and then change the auth schmes file. So that you dont overwrite the standard file.My suggestion is use a different name as suggested in all the Blogs.

I am wondering isn't this a better way of doing it as most articles talk about opening it in NWDS and then uploading it back to the server and restarting it.

yes you can do it either ways. But I found it convinent to upload it from Support desk from Portal.

~Hope this Helps

Hussain.

Edited by: Hussain on Jul 9, 2009 12:22 PM

Hello,

I have seen all the help pages concering login screen customization.

I was wondering if there is another alternative as the one suggested.

1. Using the Portal Archiver facility in the portal itself to upload the modified logon.par (keeping the same name ofcourse thus eliminating the need to update the authenschemes.xml file)

This way atleast all modifications can be previewed very quickly without having to each time follow the steps of putting in the server physically etc as per the help files.

Regards,

Sunil

I guess the reason I was saying that I keep the same name as the standard login file was essentially as follows

1. Make 2 backup copies of the standard login.par file on my machine.

2. Modify the 1st backup copy with the relevant jsp and txt files.

3. Recreate the par file with the same name using the winzip utility

4. Goto System Admin --> Support -->Support Desk ~~> Portal Runtime~~>Administrator Console

5. Under Archive Uploader I upload the newly created par file with the same name.

6. Logoff the portal and clear the cache

7. The new logon screen should appear.

However, one question I have on this is do i need to delete the existing com.sap.portal.runtime.logon from Archive Remover and then perform the above step 5. The reason I say this is because yesterday I tried the above with first deleting the existing com.sap.portal.runtime.logon and for some reason the changes did not take effect. I am wondering if the Archive Remover will be an essential step before Archive uploader to ensure no cache issues exist.

Regards,

Sunil

If you are making changes to the original par file then you would just have to upload the new par file and refresh the screen to view the changes. If you have created a new par file with a new name and done the needed changes in authscheme.xml then the new UI from the new par file will be rendered to you. If you dont see the changes, try clearing the browser cache.

Thanks,

GLM

Actually i did try that by making a small test.

I removed the Welcome Text

Created the par file using Winrar

Uploaded the par file with the same name

cleared all the browser cache and the cache under System Admin --> Navigation

logged off the portal

logged back in

The Welcome text was still there.

I was wondering if before uploading the modified logon.par (same name as standard) I need to remove the existing logon.par using the archive remover. Perhaps this might help.

I am just hesitant to that as there is a risk that the logon page doesn't appear only. Has anyone tried this before successfully ?.

Since this is an alternative, I do not to see too many post or articles suggesting this approach which might be a lot quicker. Wonder why ?

If you are modifying the original par file then the par file is over written. Hence you don't have to delete it. Once your upload is done, try downloading the par file and check for the changes you've done.

Thanks,

GLM

Is there a way to download the par from the portal itself rather than requesting basis to download from the server ?

Regards,

Sunil

Hello,

To download the file from portal,

Go to Sys admin->Support->Portal runitme->Browse Deployment->root->web inf->deployment->pcd.

Here you will find the PAR file.

~Hussain.

Hello,

I tried downloading from the location mentioned

However when I click download it saves it as this file

com.sap.portal.support.browse.default

Strange ??

Infact any of the par files I attempt to download see to download it as com.sap.portal.support.browse.default instead of as

expected : com.sap.portal.runtime.logon.par.bak

Regards,

Sunil

Hi,

There is nothing wrong with that. It is the defualt name that it takes automatically. However the file will be correct... just check it by opening it in NWDS.

~Hussain.

I tried opening the file in NWDS.. It had all wierd characters. No luck

I would assume that there should be a away to download the par file directly in .par format itself and then open the file in winzip without having to use NWDS.

regards,

Sunil

What procedure did you follow to open the par file. I hope you have followed this.

1.Downloaded the file.

2.Unzip it.

3.Remove the .bak extension so that it becomes .par file.

4.Import the file in NWDS using FIle->Import->Par File.

Just try this..

~Hussain.

I tired the following:

1. Download the file.

2. It stores the file as com.sap.portal.support.browse.default on my local desktop.

3. So there is no question of unzip it as it does not get downloaded as .par.bak extension.

4. I still try to change the com.sap.portal.support.browse.default manually to com.sap.portal.com.sap.portal.runtime.logon.par in the hope that when opening it using winrar it should work. But no luck.

There is something not right. When I click download it should save it as com.sap.portal.runtime.logon.park.bak on my desktop and that is not happening.

regards,

Sunil

Sounds Starange. I dont know why are you not able to unzip it. when you dowload the file it will be com.sap.portal.support.browse.default. Unzip the file then you will be able to find com.sap.portal.runtime.logon.par.bak file in it. then remove the .bak extension and Import it.

Hope this time it works for you.

~Hussain.

How does one unzip a file which doesnt appear to be in zipped format to begin with...

com.sap.portal.support.browse.default

Do I rename the extension as com.sap.portal.support.browse.default.zip ?

Sunil

Hi,

Not reqired to rename it. Right click on file and see if you can get any options like Extract here or Extract File or open archive.

~Hussain.

unfortunately I do not get any option to extract or otherwise that might indicate it being a zip file.

Regards,

Sunil

Some more info. I was browsing throuh SDN and came across a thread which is essentially the same problem i am facing.

the comment from Chris Bahr is exactly my problem.

Regards,

Sunil

Hi,

Please have a look at this link,

https://wiki.sdn.sap.com/wiki/display/EP/Portalloginpage+modification.

Regards,

krishna.

Hello,

I am aware of these WIKIS.

However, I am seeking an alternative approach using the portal itself as I do not have access to the server file location.

Regards,

Sunil

I had same problem and found the answer when browsing other threads.

Here is what you should do:

1. download the file as com.sap.portal.support.browse.default

2. unzip com.sap.portal.support.browse.default and extract com.sap.portal.support.browse

3. unzip com.sap.portal.support.browse and extract yourparfile.par.bck.

4. rename yourparfile.par.bck to yourparfile.par.

Now you can do whatever you want to do with your par file.

Good luck.

Jane

Refer these,

http://jsbi.blogspot.com/2006/09/how-to-customize-login-screen-in-sap.html

http://www.saptechies.com/how-to-customize-the-sap-login-screen/

Regards,

Ravi

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Ask a Question

Top Q&A Solution Author

User

Count