Logon Par - redirect to new JSP

Hi,
I've to change the portal logon page.
My requirement is to redirect the logon page to test.jsp page.
from umLogonPage.jsp i'm trying to redirect to test.jsp in form method.
<FORM name="logonForm" method="post" action=test.jsp>
but the URL is not proper.
How can i pass the absolute URL for this.
Thanks and Regards
Puneet

Puneeth,
Its possible to redirect to a JSP page from portal logon Screen.
There are several ways of doing this:-
1. Create a separate portal component (JSP Dynpage) and set the authscheme property is anonymous (because you are calling a portal component from outside) ie.
<property name="AuthScheme" value="anonymous" />
You can follow this method If JSP componentu2019s functionality is Independent than any login functionality.
2. You can modify the SAPMLogonLogic.java file which contains flow logic of all jsp files. The SAPMLogonLogic file is present umelogonbase.jar.
The umelogonbase.jar is under lib folder of the logon par file. Just extract the logon par file and navigate to PORTAL-INF -> lib to get the umelogonbase.jar
Ram

Similar Messages

Not able to get JSP file in com.sap.portal.runtime.logon.par file

Hi everyone,
I have downloaded com.sap.portal.runtime.logon.par from portal. When i imported in NWDS , i am not able to find any JSP file.
In folder PORTAL-INF, there should be this file but its not there. what could be the reason.?

Hi Manu,
Copy com.sap.portal.runtime.logon.par from filesystem:
/usr/sap/<SID>/J<Instance number>/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/deployment/pcd/
if there is issue with downloading.
Please check this :-
Portal Customizations Intro - Login Part 1
http://wiki.sdn.sap.com/wiki/display/EP/ModifyingtheLogon+Page
Changing the welcome text in portal header (EP5.0)
Hope this will helps you.
Regards,
Arun

Problem With LOGON.par

HI
iam using NWDS 2.0.12 version as indicated i have moved the par file into the studio and edited the jsp tages according to my needs by the system is showing the error
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
The exception was logged. Inform your system administrator..
See the details for the exception ID in the log file
The foloowing steps i followed
The login page is part of the par file with the name com.sap.portal.runtime.logon.par
1) Copy the file with the above name from the following location (EP6 SP9 and higher). It has the additional ending ">\<SID>\<Instance>\j2ee\cluster\server<#>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd\
2) Import the PAR file into Netweaver Developer Studio:
3)Edited the file
4) while importing the lib directory was empty so i copied the files
1. com.sap.portal.runtime.logon_api.jar
2. umelogonbase.jar
into the lib directory
5) after that i made a par file using nwds and winzip.
6)Then i changed the authescemes .xml file
1. Start the Config Tool by executing <SAPJ2EEEngine_installation>\j2ee\configtool\configtool.bat.
2. Navigate to cluster_data>server>persistent>com.sap.security.core.ume.service.
3. Switch to edit mode by clicking on the pencil which is at the upper right area.
4. In the tree, select authschemes.xml and choose Download. Save the file to your local directory
5. Edit the local file: To select the new PAR file as the Logon page change the occurrence of all substrings com.sap.portal.runtime.logon to your
project/PAR file name. All com.sap.portal.runtime.logon should be substituted with something like com.company.portal.runtime.logon (or whatever you project name is). Dont remove the part behind it.
(These are the profiles in the portalapp.xml and have the names default, certlogon, basicauthentication, header, and anonymous).
6. Create a new node in the configuration tree in the Config-Tool for the edited file as follows:
a.Select the node com.sap.security.core.ume.service.
b. Choose the symbol for Creating a node below the selected node.
c. Select the type File-entry.
d. Choose Upload and select the custom file from your local directory.
e. Enter a name for the entry, for example, authschemes_myHR.xml. By default, the name of the uploaded file is used.
f. Choose Create.
g. Choose Close window.
h. The new node appears in the configuration tree.
i. Go to Global server configuration>services> com.sap.security.core.ume.service and edit the property login.authschemes.definition.file.
The value needs to be changed from authschemes.xml to authschemes_myHR.xml
j. Restart the Portal. That is often not done and the changes will not appear.
after doing all this the portal shows an error
can anyone tel me where am i going wrong what steps iam missing while changing the par file.aslo pls if any one can tel me where exacty the log file is stored and how do i check the exception id.

Hi Pankaj,
The steps seem to be correct.
The physical location of the log file is:
\usr\sap\<instance name>\JC01\j2ee\cluster\server0\log
You could check in the defaultTrace files here. Also note that the log entry could go into the Trace files in one of the Server in the clusters.
You could also look for the Log file from within the portal using Java Home-> Portal Log Viewer -> give the Exception id in the search
Regards,
Ashwini.

Problem in JNDI Lookup of Deployable Proxy from the logon par file

Hi,
I have customized the Logon par file and have a functionality to call a webservice when the Password Reset happens.
from the ResetPassword.jsp , SAPMLogonLogic.java is getting called ,and there is a method called performResetPassword().
I am calling a Deployable Proxy in that method by using the below code,
Gateway objGateway=(SMSGateway)ctx.lookup("java:comp/env/MailProxy");
MailGatewayViDocument objSMSGatewayViDocument=(MailGatewayViDocument )objGateway.getLogicalPort("wsPort_Document",MailGatewayViDocument.class);
objMailGatewayViDocument.sendMail(...);
I am getting the Exception,
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/MailProxy.
I have deployed the Deployable Proxy in the J2EE Engine and add this API Jar as the External Library (Project >Properties>Java Build Path ---> Add External jars...Added the .jar file generated in the Proxy Project).
Please let me know the possible solutions where i can call a deployable proxy inside the logon par file.
Thanks and Regards,
Sekar

Hi,
I have fixed this error by changing the lookup as follows.
InitialContext ctx=new InitialContext();
Gateway objGateway=(Gateway)ctx.lookup("wsclients/proxies/sap.com/GatewayProxy/com.ms.sap..GatewayProxy");
Just open Visual Administrator and look for the path under wsclients for proper naming.
Thanks and Regards,
Sekar
Edited by: Sekar M on Jan 16, 2008 6:10 PM

Redirect to the jsp page after user authenticated successfully

Here is the requirement
Im using JAAS Custom Login Module for user authentication.
I have few questions in Portal Logon process
1. Exactly at what point I can conclude that the user has been authenticated successfully, because I have to redirect the user to some other page for the first time logon to enter some information, subsequent logins shouldnt be redirected. (I can update flag upon entering information).
2. Where should I add my redirection code? Is it in my JASS Custom Login Module?
If yes, how can I do that ? Im more consider on where should I add it?
3. Do I need to change my UmLogonPage.jsp to complete my requirement?
4. Once after entering the Logon information, who will call my JASS Custom Login Module for authentication? If authentication has failed who will return the control back to the umLogonPage.jsp?
5. In my JASS Custom Login Module, I have no redirections except having logic for authentication process, and some Login Exceptions are thrown for failure logins.
6. Who will catch these exceptions for failure logins to redirect back to the umLogonPage.jsp.
7. Finally I like to know where can I add my redirection logic once the user has been authenticated successfully?
8. last but not least can any of the experts explain the whole login process (using JASS module)? How the control goes from one component to another?
Any kind of help is appreciated.
Points can be awarded for useful answers.
Thanks
MMK

Thanks a lot for your valuable reply.
yes what you said was correct, storing information in R/3 System and getting the details from FM using Connector framework.
You said i have to modify "header.jsp", can you please tell which .par file should i get to modify?
one more question to you ... i have provide custom logon error messages to the user ... i did all the modification in logon.par and deployed in EP 6 .. working fine .. i can able to see "User ID Missing" , "Password Missing" etc ..
when i place same peace of code in EP 7 it always displaying "User Authentication failed". can u guess what whould be the problem?
Thanks
MMK

Custom Logon PAR

Hello,
I am trying to access general information of logged in user from logon par file. For that I have created custom abstract portal component to access UME API and redirected umLogonPage.jsp to it.
My problem is after checking UME api user able to logged in to portal but it stuck in custom component.
Please help me out what am doing is right approach or is there any better way?
Thanking in advance.
Regards,
Pravin

Hi Pravin,
That was to retrieve user data thru java class and you can keep this retrieved user data inside a bean class and call the bean class from your jsp.
Otherwise, Pls try below code sample inside jsp -
<%
IPortalComponentRequest currentRequest = (IPortalComponentRequest) pageContext.getAttribute(javax.servlet.jsp.PageContext.REQUEST);
com.sap.security.api.IUser user = currentRequest.getUser();
String fName = user.getFirstName();
%>
Regards,
Sen

Need to download com.sap.portal.runtime.logon.par

hello friends
we need to chang the look and feel of the portal display pages and for that purpose we need com.sap.portal.runtime.logon.par file
can you all help us as to where we can find this par file so that we can download this file.
we have still not installed the portal platform,we'll be doing that in the following week.
Thnaking you,
Anurag.

Hi Anurag,
This post will explain the steps involved for each element.
No. Portal Login page related questions
1. What is the associated par file for portal login Page ?
2. How to import the PAR file into Netweaver Developer Studio?
3. What are the different pages and their associated files in logon.par?
4. How to change text seen in the logon page ?
5. What is authschemes.xml file? Do we need to change this file also ?
6. How to remove standard links like support, Register ...?
7. How to change or add new images ?
8. How to change only the branding image displayed in the logon screen of the Portal ?
1. What is the associated par file for portal login Page?
Answer : The par file related to login page of Netweaver Portal is com.sap.portal.runtime.logon.par. This is the standard
logon component containing the code and resources used by the logon screens is shipped in a portal archive (PAR) file named com.sap.portal.runtime.logon.par.
2. How to import the PAR file into Netweaver Developer Studio?
Answer : - Select File>Import .
- Choose the option PAR file. Select Next and a popup window appears.
- Select File>Import .
- Choose the option PAR file. Select Next and a popup window appears.
- In the window you have 3 text fields:
The location of the par file,
Project name (same as new par file name, preferably) and
location for project to be saved
3. What are the different pages and their associated files in logon.par?
Answer :
Logon page : umLogonPage.jsp
Problem page : umLogonProblemPage.jsp
Help (PW reset) page : umHelpPage.jsp
Reset Password : umResetPasswordPage.jsp
Change Password Page: changePasswordPage.jsp
Certificate Logon : umLogonCertPage.jsp
4. How to change text seen in the logon page ?
The text seen on the logon page is not in the JSP page, but in properties files which are called by tags like the
Welcome text : <%=logonLocale.get("xtit_WELCOME")%>
In order to change "Welcome" to "Welcome to MyTravel" you have to :
 - Unzip the file umelogonbase.jar which you can find under dist\PORTAL-INF\lib
 - Find the file "logonLabels_" which contains your language;
 e.g. logonLabels_de.properties for german language, *_en for English etc.,
The default is in the file logonLabels.properties .
- Find the key which is used in the tag and change the text after the equal sign.
- Save the changed file and create a updated JAR file using a zip program. The file needs to be named exactly umelogonbase.jar
- Put the JAR file back to location - dist\PORTAL-INF\lib
You are done on this now.
5. What is authschemes.xml file ? Do we need to change this file also ?
Changing the Authschemes.xml file is required only if you want to change com.sap.portal.runtime.logon.par.bak file and point it to different par file. This is more for anonymous logon with named anonymous users and using anonymous as the authentication scheme. The anonymous users are not issued a SAP logon ticket.
6. How to remove standard links like support, Register ...?
The standard links are controlled with the UM settings
 - ume.logon.logon_help
- ume.logon.selfreg
You could also just comment out the lines if you want to hide.
7. How to change or add new images ?
To exchange the two images, which are by default on the logon page, do the following steps:
 a. Copy the image(s) you want to use in your project in the the folder dist/layout
 b. Find the < img src="" > you want to work on in the umBotArea.txt
Change the src attribute in the img tag to src="<%=webpath + "layout/myPic.gif" %>". The webpath is already defined in the file logon_proxy.txt and ready to use. In the Netweaver portal 6.0 SP9 and higher you have 2 images on the right side.
8. How to change only the branding image displayed in the logon screen of the Portal ?
If you want to change only the branding image displayed in the logon screen, you can configure this using the user management property ume.logon.branding_image
Hope this helps the community in the launch of this ver 1.0, future versions could contain more changes and updations covering all other aspects of Netweaver Portal

Error while importing logon par file into NWDS.

Dear Friends ,
I m trying to customise the logon screen for my project. For this I have downloaded the "com.sap.portal.runtime.logon.par.bak" from portal server instance with the help of basis team. I have locally saved this file on my desktop[. I have renamed the file as .par and removed the .bak extension. Now I have tried to import the file onto NWDS in EP perspective by following File>Import>Par file. But its giving me this error:
error in opening zip file
Reason: Sorry, an error occured creating the new project.
The plugin "com.sap.portal.plugins.config-archiver caused an exception during the
"Unpack" Operation See log for more details.
In some of the solutions provided in SDN saying that after renaming the file to par open with zip if i done it is again showing the error as "Start of the central directory not found .Zip file corrupt.Possible cause :file transfer error."
Kindly suggest me the solution.
Thanks and regards.

Hi,
I think you have taken this file from a wrong path and hence this issue.
Pls download the par file from the below path and try importing it into EP perspective..
System admin> Support>Portal Runtime > Browse Deployment>
Browse through the following to find the com.sap.portal.runtime.logon.par.bak file:
WEB-INF u2013> deployment u2013> pcd
Root>WEB-INF>Portal>Portalapps> temp--> download the com.sap.portal.runtime.logon.par.bak
Regards,
Vijay.
Edited by: VijayKPappala on Sep 7, 2011 8:46 AM

Error deploying logon.par

Hi Experts,
I am trying to change the portal logon screen. I followed the insstructions in the documentation to modify the com.sap.portal.runtime.logon.par.bak
I exported an par file from nwds and copied to the apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd and apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp directory
Also i modified the authschemes.xml and set the corrext value in com.sap.security.core.ume.service via configtool.
The problem is when i restart the server the created .par file changes to .p.err and the following error log is created:
2007-05-16_14-54-15
Application upload failed: com.sap.test.logon.par
com.sapportals.portal.prt.runtime.PortalException: [ApplicationRepositoryService.putArchive] archive: com.sap.test.logon.par
 at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:328)
 at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:813)
 at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchives(DeploymentManager.java:599)
 at com.sapportals.portal.prt.deployment.DeploymentManager.populateRuntimeRepository(DeploymentManager.java:582)
 at com.sapportals.portal.prt.deployment.DeploymentManager.runtimeRepositoryDeployment(DeploymentManager.java:310)
 at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:404)
 at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
 at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:359)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:392)
 at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
 at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
 at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.pcd.pl.PlRuntimeException: unexpected SQLException when calling OpenSQLServices.isTransientSQLError()
Invalid connection type com.sap.engine.services.dbpool.cci.ConnectionHandle.
 at com.sapportals.portal.pcd.pl.BasicObjectsTable.isTransientSQLError(BasicObjectsTable.java:281)
 at com.sapportals.portal.pcd.pl.PlFactory.checkDeadlockResolution(PlFactory.java:2433)
 at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildAndNotify(XfsContext.java:1158)
 at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChild(XfsContext.java:1100)
 at com.sapportals.portal.pcd.gl.xfs.XfsContext.createSubcontext(XfsContext.java:856)
 at com.sapportals.portal.pcd.gl.xfs.BasicContext.createBasicSubcontext(BasicContext.java:190)
 at com.sapportals.portal.pcd.gl.PcdPersContext.createSubcontext(PcdPersContext.java:190)
 at com.sapportals.portal.pcd.gl.PcdFilterContext.filterCreateSubcontext(PcdFilterContext.java:253)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:145)
 at com.sapportals.portal.pcd.gl.PcdGlContext.createSubcontext(PcdGlContext.java:440)
 at com.sapportals.portal.pcd.gl.PcdGlContext.bind(PcdGlContext.java:369)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.bind(PcdProxyContext.java:469)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebindInt(PcdProxyContext.java:489)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:508)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:494)
 at com.sapportals.portal.pcd.gl.PcdGlContext.rebind(PcdGlContext.java:1254)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:549)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:736)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:741)
 at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.storeArchive(ApplicationRepositoryService.java:373)
 at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:299)
 ... 20 more
Caused by: com.sap.sql.log.OpenSQLException: Invalid connection type com.sap.engine.services.dbpool.cci.ConnectionHandle.
 at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
 at com.sap.sql.services.OpenSQLServices.isTransientSQLError(OpenSQLServices.java:742)
 at com.sapportals.portal.pcd.pl.BasicObjectsTable.isTransientSQLError(BasicObjectsTable.java:277)
 ... 40 more
looks like a problem with openSQL. In fact I have defined an additional vendor data source in visual admin that works properly with my application. Is my problem related to that?
Thanks in advance

Hi,
 Before cheking the entire steps at one shot, try step by step procedure.
First just edit the changes and try to deploy and run the new par from portalapp.xml. If the output is correct, then go ahead changing the actual logon page with your new page. Else it will be difficult to find the exact problem. Also make sure the logon par which u have taken for modiifcation comes from the server u r deploying and u use NWDS of same patch. Otherwise there can be mismatches.
Regards,
Vijai

Portal Runtime error when modifying: com.sap.portal.runtime.logon.par

Hello,
We need some help because we get 'Portal Runtime error: iView: N/A Component Name:N/A' error when trying to access portal logon screen.
This is what we've done:
We've modified com.sap.portal.runtime.logon.par file and we've uploaded it but it doesn't work. Because of the error, we've overwritten this file with the original one but now it's imposible to access portal.
The situation it seems to be like before the modification of the .par file but we get the same error and can't access portal.
Please, do you know what could be the problem?
Thanks in advance

Hi Belen,
Here are the steps you would need to take
1. import the original par file into the NWDS and name the project as
    com.sap.portal.runtime.logon
2. Make sure the project name is com.sap.portal.runtime.logon
3. use winzip/winrar to extract the com.sap.portal.runtime.logon.par file in
    a local directory
4.Under the lib you would find two jar files copy them and paste them in your project
   under dist>PORTAL-INF>lib directory
5.move the files cert....till umResetPass....jsp into the PORTAL-INF directory
6. export the par to the server in question
7. restart your server
This should solve your problem..
Thanks,
Gokul

Problem in JNDI Lookup of Deployable Proxy inside logon.par

Hi,
I have customized the Logon par file and have a functionality to call a webservice when the Password Reset happens.
from the ResetPassword.jsp , SAPMLogonLogic.java is getting called ,and there is a method called performResetPassword().
I am calling a Deployable Proxy in that method by using the below code,
Gateway objGateway=(SMSGateway)ctx.lookup("java:comp/env/MailProxy");
MailGatewayViDocument objSMSGatewayViDocument=(MailGatewayViDocument )objGateway.getLogicalPort("wsPort_Document",MailGatewayViDocument.class);
objMailGatewayViDocument.sendMail(...);
I am getting the Exception,
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/MailProxy.
I have deployed the Deployable Proxy in the J2EE Engine and add this API Jar as the External Library (Project >Properties>Java Build Path ---> Add External jars...Added the .jar file generated in the Proxy Project).
Please let me know the possible solutions where i can call a deployable proxy inside the logon par file.
Thanks and Regards,
Sekar

Hi Sekar!
Try this:
MailGateway objMailGateway=(MailGateway)ctx.lookup
("wsclients/proxies/sap.com/MailProxy/com.ms.sap.sms.MailProxy/wsPort_Document");
I have understood you're deploying a par file... if you are doing this way, don't forget to put a reference to the webservice in portalApp.xml:
<property name="PrivateSharingReference" value="SAPJ2EE::sap.com/com.ms.sap.sms.MailProxy"/>
Hope this can work.
Are you sure this destination is the one you are looking for?
sap.com/CHEPSMSProxy/com.ms.sap.sms.SMSProxy/wsPort_Document
It seems to be anther app. If this is the correct app then the JNDI should be:
MailGateway objMailGateway=(MailGateway)ctx.lookup
("wsclients/proxies/sap.com/CHEPSMSProxy/com.ms.sap.sms.SMSProxy/wsPort_Document");
If this fails and if you have have source code of the proxy app, check out the application.xml file, and look for Display name. Also look for the application-j2ee-engine.xml file, and look for the 'Vendor name', and post them please.
Eneko
Message was edited by:
Eneko Rodriguez

Can I launch a new JSP on a popup window, when cliking a HTMLB button ?

Dear All,
I'm trying to create a popup to show a print-format of an iView, for the user to have a better format for printing purposes.
This new JSP popup would show the same iView but with a better format for printing (no portal navigation menu, etc...)
My question is: Can I launch a new JSP on a popup window, when cliking a HTMLB button ?
Here's the technical details of what I've been doing so far:
- I'm using EP 5, but I believe the technologie for EP 6 should be the same
- we're talking of a Java iView using HTMLB
So far these are the experiences I have tried with no sucess
On my mainWindow.jsp I have this piece of code, but it doesn't work:
(etc...)
<%
ResourceBundle res = componentRequest.getResourceBundle();
IResource rs = componentRequest.getResource(IResource.JSP, "printFormat.jsp");
String JSP_URL = rs.getResourceInformation().getURL(componentRequest);
%>
(etc...)
<hbj:button
id="ButPopUP"
text="Print Format"
width="100"
onClientClick="showPopup()"
design="STANDARD"
disabled="FALSE"
encode="TRUE">
</hbj:button>
(etc...)
<script language="Javascript">
function showPopup(){
mywindow = window.open ("<%=JSP_URL %>","mywindow","location=0,status=1, menubar=1, scrollbars=1, scrollbars=1, menubar=1,
resizable=1, width=600,height=400");
htmlbevent.cancelSubmit=true;
</script>
(etc...)
Thank you very kindly for your help.

Hi Kiran,
sorry for the late reply.
Thank you so much for your JAR file.
Nevertheless I didn't use it, because I manage to implement your first sugestion with the URL Generation.
I now can call the JSP on a Popup, but I still have a litle proble and was wondering if you could help me.
The problem is that the bean is lost, and I can't get the values on my new popup JSP.
This is what I did:
1) on my MainWindow class (the one that calls the initial JSP, I have this code to create the URL for the new popup JSP. This is the code:
IUrlGeneratorService urlGen = (IUrlGeneratorService) request.getService(IUrlGeneratorService.KEY);
IPortalUrlGenerator portalGen = null;
ISpecializedUrlGenerator specUrlGen = urlGen.getSpecializedUrlGenerator(IPortalUrlGenerator.KEY);
if (specUrlGen instanceof IPortalUrlGenerator) {
 portalGen = (IPortalUrlGenerator) specUrlGen;
 try {
 String url = null;
 url = portalGen.generatePortalComponentUrl(request, "Forum_IS.popvalues");
 myBeanDados.setPopupURL(url);
 } catch (NullPointerException e) {
 log.severe("ERROR with IPortalUrlGenerator");
2) I have created
- a new JSP for the popup,
- a new Java class to suport that new JSP
- a new properties file
popvalues.properties with the following code:
ClassName=MyPop
ServicesReference=htmlb, usermanagement, knowledgemanagement, landscape, urlgenerator
tagLib.value=/SERVICE/htmlb/taglib/htmlb.tld
MyPop is the new class that is associated with the new JSP popup.
The problem now is that the bean was lost.
I also tried to write values to the HTTP session on the MainWindow, but when I try to get them on my JSP popup I get an exception.
How can I pass the values (or beans) to my new popup JSP ?
Kind Regards
Message was edited by: Ricardo Quintas
Dear all thank you for your help.
I have managed to solve the problem I had.
Here's the problem + solution sumary.
I have to remind you that we are talking of EP 5, PDK 5 (Eclipse version 2.1.0), with JAVA JDK 1.3.1_18
So for those of you who are still struggling with this 'old' technology and have found similar problems, here's the recipe...
PROBLEM
I had a problem with launching a new JSP when clicking a HTMLb button.
I wanted to create a JSP to present a 'print-format' of an iView.
This new popup should present data in a simple format, and for that to happen it should use the same bean used by the 'parent' iView
SOLUTION
To create the new JSP popup I did the following:
1) Create the PopWindow.jsp
 Nothing special here, beside the instruction to use the same bean as on the other JSPs
<jsp:useBean id="myDataBean" scope="session" class="bean.DataBean" />
 2) Create the associated JAVA class
MyPop.java. This class will be used to call the PopWindow.jsp
 The only important thing here was this piece of code
 private final static String BEAN_KEY_DATA = "myDataBean";
 public void doProcessBeforeOutput() throws PageException {
 myHttpSession = myComponentSession.getHttpSession();
 myDataBean = (DataBean) myHttpSession.getAttribute(BEAN_KEY_DATA);
 myComponentSession.putValue(BEAN_KEY_DATA, myDataBean);
 this.setJspName("PopWindow.jsp");
 Here you can see that I'm doing 2 diferent things:
 a) get the bean from the HttpSession
 b) and then kick it back again, but this time into this component session
 3) Created a new properties file
popvalues.properties. This file contains the follwing code:
 ClassName=MyPop
 tagLib.value=/SERVICE/htmlb/taglib/htmlb.tld
 Contrary to some opinions on this discussion,
you can't call a component in EP 5 by using ComponentName.JSPname.
Or at least that didn't work for me.
You nee to use an aproach like this one ComponentName.NewProperiesFileName
4) On my main class MainClass.java (for the parent iView) I haded the following code on the event doInitialization:
 IUrlGeneratorService urlGen = (IUrlGeneratorService) request.getService(IUrlGeneratorService.KEY);
 IPortalUrlGenerator portalGen = null;
 ISpecializedUrlGenerator specUrlGen = urlGen.getSpecializedUrlGenerator(IPortalUrlGenerator.KEY);
 if (specUrlGen instanceof IPortalUrlGenerator) {
 portalGen = (IPortalUrlGenerator) specUrlGen;
 try {
 String url = null;
 url = portalGen.generatePortalComponentUrl(request, "MyMainApplication.popvalues");
 myDataBean.setPopupURL(url);
 } catch (NullPointerException e) {
 etc...
 The idea here was to build dinamicaly a URL to call the popup.
 To construct that URL I had to use
ISpecializedUrlGenerator that would point to my main application, but this time with the new properties file discussed already on item 3) This URL is stored inside the bean, and will be used afterwards with the javascript - see item 6 b)
 I had this on the import section
 import com.sapportals.portal.prt.service.urlgenerator.IUrlGeneratorService;
 import com.sapportals.portal.prt.service.urlgenerator.specialized.IPortalUrlGenerator;
 import com.sapportals.portal.prt.service.urlgenerator.specialized.ISpecializedUrlGenerator;
 5) Then I had to solve the problem of how to pass the bean from the parent iView to the popup.
 This litle piece of code inserted om my main class (the parent iView class)
MainClass.java solved the problem:
 import javax.servlet.http.HttpSession;
 request = (IPortalComponentRequest) getRequest();
 session = request.getComponentSession();
 session.putValue(BEAN_KEY_DATA, myDataBean);
 myHttpSession = session.getHttpSession();
 myHttpSession.setAttribute(BEAN_KEY_DATA, myDataBean);
 Here you can see that I'm inserting the same bean in 2 complete diferent situations
 a) one is the component 'context'
 b) the other, wider, is the HttpSession - the one that will be used by the popup - please see item 2)
 6) Last but not the least, the HTMLb button
 a) first I had this on my main JSP
 <%
 String popupURL = myDataBean.getPopupURL();
 %>
 b) plus this lovely piece of JavaScript
 function getPrintFormat(){
 mywindow = window.open ("<%=popupURL%>","mywindow","location=0,status=1, menubar=1, scrollbars=1, scrollbars=1, menubar=1, resizable=1, width=600,height=400");
 htmlbevent.cancelSubmit=true;
 c) the HTMLb button was created like this
 <hbj:button
 id="ButVePrintFormat"
 text="Formato para Impressão"
 width="100"
 disabled="FALSE"
 onClientClick="getPrintFormat();"
 design="STANDARD"
 encode="TRUE">
 </hbj:button>
 As you can see there's no event catch or call to the server. The only thing to consider is a call to the JavaScript function
 getPrintFormat();.
 Está todo lá dentro.
 That's all there is to it.

Com.sap.portal.runtime.logon.par information in Authschemes.xml

Hello Portal gurus,
I am trying to customize the Portal logon page by modifying the com.sap.portal.runtime.logon.par file. I modified the par file. But after this change, I wanted to change the authschemes.xml file to reflect the par file changes.
When I downloaded the .xml file, I only found occurences of <frontendtarget>com.sap.portal.runtime.logon.certlogon</frontendtarget>, <frontendtarget>com.sap.portal.runtime.logon.basicauthentication</frontendtarget> and <frontendtarget>com.sap.portal.runtime.logon.header</frontendtarget>
Could anybody confirm, whether I have to rename these occurrences of com.sap.portal.runtime.logon with my customized logon .par file name between <frontendtarget> and </frontendtarget>?
Points will be awarded for correct answers and useful suggestions.
Thanks,
~~LB

Hi
Here is the procedure
1. Start the Config Tool by executing <SAPJ2EEEngine_installation>\j2ee\configtool\configtool.bat.
2. Navigate to cluster_data>server>persistent>com.sap.security.core.ume.service.
3. Switch to edit mode by clicking on the pencil which is at the upper right area.
4. In the tree, select authschemes.xml and choose Download. Save the file to your local directory
5. Edit the local file: To select the new PAR file as the Logon page change the occurrence of all substrings com.sap.portal.runtime.logon to your
project/PAR file name. All com.sap.portal.runtime.logon should be substituted with something like com.company.portal.runtime.logon (or whatever you project name is). Dont remove the part behind it.
(These are the profiles in the portalapp.xml and have the names default, certlogon, basicauthentication, header, and anonymous).
6. Create a new node in the configuration tree in the Config-Tool for the edited file as follows:
a.Select the node com.sap.security.core.ume.service.
b. Choose the symbol for Creating a node below the selected node.
c. Select the type File-entry.
d. Choose Upload and select the custom file from your local directory.
e. Enter a name for the entry, for example, authschemes_myHR.xml. By default, the name of the uploaded file is used.
f. Choose Create.
g. Choose Close window.
h. The new node appears in the configuration tree.
i. Go to Global server configuration>services> com.sap.security.core.ume.service and edit the property login.authschemes.definition.file.
The value needs to be changed from authschemes.xml to authschemes_myHR.xml
j. Restart the Portal. That is often not done and the changes will not appear.
Rgds
Srikanth

How is the com.sap.runtime.logon.par implemented?

Hi all
I want to make some changes to the logon.par file such that if the user authentication fails, I have to fire a custom RFC to check if the user exists in that backend system.
First of all, I have no clue about how I am going to implement this. Before jumping deep, I'd like to understand how the existing authentication works. Where does the logon get information about the user credentials?
Any information would be very helpful.
Thanks
J

Hi J,
The logon process is implemented through two layers, of which the one you have referred to is just representing the user interface, whereas the real logon process is implemented through login modules; for the latter see http://help.sap.com/saphelp_sm32/helpdata/de/46/3ce9402f3f8031e10000000a1550b0/frameset.htm
On both layers, you can determin if the logon worked or failed (to be concrete, the login module determins this by its own, whereas in the logon PAR you can determin the result of this process). So both layers could be used to implement this. As the login module is more generic, I would advise to use this, as this is also documented and supported, whereas in the login module you would have to modify the implemented logic (by decompiling or putting your logic into some existing JSP). The internal logic of the logon PAR is not documented (but not hard to understand when checking the JSPs and/or decompiling the code).
Hope it helps
Detlev

Modification of Logon Par

Hi Guys,
Does anyone of you encountered the error below after modifying the logon par? I already have changed authschemes.xml to point to the new component but still encountering the issue. please help.
com/sap/engine/applications/security/logon/LogonApplicationPermission.
Exception id: 03:14_03/03/09_0001_2206150
See the details for the exception ID in the log file
Thanks,
Robert

hi
check this this may be the one of the reason
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/297f35cf-0201-0010-00b2-fe2f3e23d360
https://ww2.avispublicsduparisien.com/irj/portalapps/com.sap.portal.pdk.srv.usermanagementengine40/docs/overview.html
bvr

Logon Par - redirect to new JSP

Similar Messages

Maybe you are looking for