Modification made in Portal Logon Page

[Former Member]

Hi ,

I have made changes on Logon Page of portal and its working fine.

now when the portal is updated (patch upgradation) the portal page is reflected to the older page.

this means i will have to again change the Logon page.

does this process need to be done after every patch upgradation????

or is there any solution to this problem???

The process of Patch Upgradation will take place after every 6-7 months .....

[Former Member]

Adding Leite's reply,

Go thru this link

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/371e9d90-0201-0010-c39c-fd295615...

1. What you have to do is, Dont name the PAR file as of SAP's rename it to your own PAR ie., (not com.sap.portal.runtime.logon.par but com.yourcomp.xyz.portal.logon.par)

2. Then update the authschemes.xml which is residing in the portal server. Using Visual Administrator or by direct editing.

This way you are making sure that your own Portal Logon PAR is used in your portal logon. So no matter what ever changes made to SAP's PAR your is not touched and there would be no need to redeploy the PAr for every patch to portal.

Thanks,

Raags

PS: if helpful reward points

[Former Member]

Hi,

After 04S upgrade ( EP6.0 to EP7.0 ) we have to replicate the same changes with the new par file as the SAP standard log on application has changed.

But no need to do the same for every support pack.

So, we have got the new par from 7.0 installation and replicated the modification with new name and deployed.

Thanks,

Abdul Raheem S

[daniel_davinci]

You should really be comparing the code changes for each support pack.

Changing the name space avoids the content being over written but also you don't get any code changes that may have been made.

I suggest using a file comparison tool to perform this task (compare the code for modifications) and upgrade your custom module with each SP as required.

[Former Member]

Thanks for all ur Inputs. We have made a custom PAR file and dewployed it on Server. It is being referred by AuthScheme XML file. It is this file which is getting replaced. So everytime after patch uprade, this XML file reverts back pointing to standard SAP PAR file. Now I belive the stratergy should be to use a Custom AuthScheme XML file which should be mentioned in Visual Admin Tool to be used to refer my custom PAR file. Is this the correct way ?

Regards

[Former Member]

Hi Sanjyoti,

Yes, thats the way you should be doing.. You should infact create a custom Authscheme.xml file - which would point to the Custom PAR file that you have developed. The name of your custom Authschemes file must be entered in property sheet ->com.sap.security.core.umeservice

-Ashwini.

[luciano_leitedasilva]

Hi,

Let me know how did you change the logon page?

Lets to supose that you have changed the current portal logon application...in this case you have to change every time after the upgrade.

If you have created a new logon application, this procediment isn't necessary.

Regards,

Luciano