on 07-18-2013 3:33 PM
Hello,
We have recently upgraded to NW 7.3. We have a custom login page in NW 7.0. I am trying to migrate the cutom login par to NW 7.3. Here is what I did:
1. Convert the logon.par to .logon.ear using the EP Par migration tool.
2. Import the ear file into NWDS as a Enterprise portal EAR.
3. Deploy the .ear file to EP 7.3
4. Change the authschemes.xml to point to logon.ear
5. Restart the server nodes.
After restarting, my changes did not take effect. Am I missing something here? Or is it that we cannot use the logon.par from NW 7.0 in the current NW 7.3 system? Kindly advice.
Thanks
Shaila
Hello Shaila,
could you please check into the NWA (http://<portal:port>/nwa).
Go to "Configuration > Authentication and Single Sign-On > Properties".
On that page in the middle section you find the following:
Do you have the standard entry there (like in my screenshot) or does it point to your custom logon? Also, a nice cache clearing always helps.
As far as I read (I don't have personal experience in this, because we don't customize our login-page that much) the only "problem" is that you have to convert your file, but you did that. I haven't read, that you can't use it.
Regards,
Steffi.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Steffi,
Thanks for your response. After you mentioned, I changed the Alias to point to my custom login page. Say my login application is CustLogon.ear, I changed this property to /CustLogon. I restarted sap and now when I try to go to the login page, I just get a black page with no errors or nothing. I dont even see any error logs being written. Any clue?
Thanks
Shaila
Hi Steffi,
I imported my .ear file as a Enterprise portal EAR into NWDS and so it only has a portalapp.xml file. The alias in the portalapp.xml is CustLogon and thats what I entered in that property. Not sure if I have to import my ear as a J2ee/EAR or Portal/EAR into NWDS. But now I am stuck with an empty login page.
Thanks
Shaila
Hello Shaila,
you can set back the default for the alias. Just go back to the NWA and there "Configuration > Authentication and Single Sign-On > Properties", click on modify and right next to your modified entry you should see the enabled button "Reset to default" to put back the default entry.
You don't have to restart the portal for this either. Just reset to default and your normal login-page is back (I just tested this, so this one I know for sure. ). This way at least you can login properly again.
Regards,
Steffi.
Hello Shaila,
that's strange. oO I tested it by putting an alias that doesn't exist to get the blank login-page and then called up nwa again to set it back to default, no problem.
But as long as you can see some login-request again...
Hmm, like I said. Sadly I have no hands-on experience with this. I just know about the conversion and that some people had problems with the migration, but I didn't read anywhere that you can't do it period.
If you don't have that much custimized, I would suggest to just do it again in the new version. This way you can be sure, everything will work as expected with 7.3.
Nontheless it would be nice to know, what's missing in your case here. I'm sorry, I couldn't be of much help for you, but at least I learned some more through this.
Regards,
Steffi.
Hi Laxmi,
the runtime behaviour you describe can be caused by errors on implementing your custom logon page. Do you have any attendant exceptions in your log files? I have done this task also in the past and would like to advise you to build your custom logon starting from the original one on your target system. As Im still looking for a possibility to debug jsp´s, I have done this step by step, if I remember correctly.
regards
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.