Portal 6 // Link existing 'iView' to Portal HMTL page

Hi,
I've an HTMl page where all SSO-Systems are kept:
Content Management >> documents >> PortalDocuments >> HTML >> SSOSystems.html
This SSO page is a simple HTML page (box) within the Portal's home page, containing URLs to all linked systems.
I now received a 'ready-to-go' package (*.epa) which I imported to the Portal. The package includes an iView, a Page, a Workset...
I now want to add an URL to the central SSO page which redirects to the iView??? and starts the external application. How to do?
Thank you.

Hi,
have you considered using [Image Maps|http://help.sap.com/saphelp_nw70/helpdata/EN/91/f9533dc1c0b60fe10000000a114084/frameset.htm]?
Romano

Similar Messages

Accessing KM Document Iview which contain .exe file from Portal logon page.

Dear All,
I was trying to access the KM document ivew(where I uploaded an .exe file in KM and created an ivew for that) in my portal logon page which is customized.
I am calling the ivew through an html command "href".
Now my issue is, while clicking on that link, that exe file is opening with the full portal ivew path name without any extension.
But the actual exe file of same size which is uploaded is getting downloaded and saved with out any extension. I always have to change the name and give .exe extension for that to open properly.
So, can some one suggest me how to open the actual exe file with the extension?
Cheers,
Anu.

Sorry Tom!
Your problem seems to be different, I've no idea.
But we already fixed our problem, I forgot to post. Here's our solution:
The solution was to create a KM Docs iView with anonymous authentication schema pointing to the download file. Then we created an URL iView pointing to this KM Doc with appending the filename AGAIN to the URL (because otherwise the iView ID will appear as filename). In the page a hyperlink now is pointing to the URL iView and after clicking it, the download starts with the correct filename.

Integrating two iviews in a single page in Portal

Hello all:
I am trying to integrate two iviews into a single page, in portal, but i am able to see one iview running fine and for other iview it says serivce not found.
But when i preview the iviews seperately they work fine.
please suggest me if i am missing something.
Thanks,
Ratna.

hi,
In second view properties, please select ENTRY POINT as Yes, then let me know
Regards
Srinivas

Adding a button/link in the portal logon page

Hi,
I am new to the portal related things. I am a web dynpro developer and familiar with the Java coding.
Now, i got a requirement to modify the portal logon page as below:
Need to insert one extra button/hyper link to reset the password.
when user clicks on this button, i need to call an RFC in R/3 by passing the entered user name. That RFC will generate a new password and send a mail to the respective email address(maintained in a custom table in R/3 itself).
If the user-id is wrong i need to show the error message returned from the RFC.
If the return-code of RFC is success, then need to show an information message conveying that the password reset was successful and refer to your mail inbox.
Please suggest me the best approach on this scenario.
I already imported the PAR file for logon page and can see the project in NWDS.
Note: we are using EP 7, NW2004s and R/3 is ECC 5.0
Thanks & Regards,
Kiran Chennapai

The Funktion Prem is suggesting can be turned on/off through the UME Properties which can be changed through the Config Tool.
More help under : http://help.sap.com/saphelp_nw04/helpdata/en/0b/50ad3e1d1edc61e10000000a114084/content.htm
Regards,
Kai

Controlling visibility of Web Dynpro Java iView in portal WDJ page

I should be able to use the WDPortalUtils interface in my Web Dynpro Java DC application to get the name of the iView in my Portal WDJ page using IWDPageService method getVisibleIViews(). My intent is to add another iView to this page and programmatically control the visibility of each iView from my WDJ application.
-> Instructions I have found through my online research indicate I should not have to specify a sharing reference because I am using the WDJ framework, but I tried it anyway. It didn't work.
-> I have added DC epbc.prtapi._api public part to my used DC's, and specified dependency at both Build time and Run time.
-> My portal page template is of type Web Dynpro Proxy Page.
-> My iView template is of type Web Dynpro Proxy iView.
-> The Page Content view of my page shows the 'visible' checkbox set for my iView.
The following statements in the wdDoInit() method of my DC's view controller should return the portal name of my iView:
IWDPageService pageService = (IWDPageService) WDPortalUtils.getService(WDPortalServiceType.PAGE_SERVICE);
String[] iViews = pageService.getVisibleIViews();
I get no compile time errors or runtime errors when I execute these statements.
BUT...
Instead of a String array, I get back a memory space pointer.
Example: [Ljava.lang.String;@664e664e
What am I missing?

Hi Jennifer,
That's what this forum is all about; finding solutions to hard-to-solve issues, which might also help someone who may face the same issue in the future. So I hope my input is valuable
The last thing I can think of is the method is been called before the portal page has been rendered completely, which may lead to the faulty results.
Is it possible to move the getVisibleIviews() to a method which is called later in the phase (for instance, at the bottom of wdDoModify or wdDoPostProcessing) or, even better, in an onAction event handler when a button is clicked?
If this doesn't work I'm afraid I'm running out of options and i would file an OSS message with SAP
Hope this helps!
Robin

Logoff and personalise link on custom portal home page

Hi,
I have created a PAR file in NWDS for Portal home page. In that i have created a header and a hover dropdown menu.
I want to add a logoff link and personalise link on it. i have tried to add the link using tag library <frm:logOffAnchor/>. bt this doesnt help.
please help.
Regards,
Rahul Doshi

did you reference html tags library for this? If no look at portal masthead par file to get information.

# in link goes to Portal home page??!!

Hi,
We have developed a page template with a drop-down menu. In this menu we have a <A> tag that is not supposed to be linked anywhere. We have therefore written a # in the href. ex: <a href="#....."></a>. In Portal this # takes us to the Portal Home page. Is there a way to avoid this?
We need the <A> tag because we use javascript events.
Regards,
Anniken & Lene

Hi
anchors (#) doesn't work because Portal puts a <bas href="path"> in the <head> section and this href is usually .../pls/portal
So when you want to go to your anchor x further down on the page the browser thinks you want to go to .../pls/portal#x an´d that ends you up on the portal home page.
There is a javascript fix for this. Search "HTML Anchor" in this forum (that is the title of the thread).
Kind regards
Tomas Albinsson

ADF Application and Oracle Portal Login Page

We have developed ADF application and deployed it in Oracle AS 10.1.2 along with the custom JAAS module, which is working fine with the application custom login page. As a next page, I want to use Oracle Portal login page for the authentication and authorization.
How can I accomplished it? Any idea?
Thanks,
AP

Shay,
1. I created blank ADF project
2. I copied myreport.jsp file (this one was generated by Oracle Report Builder) under ..ViewController/public_html directory
3. Created directory 'lib' under ViewController/public_html/WEB-INF/lib
4. Copied reports_tld.jar file under the directory created in 3.
5. Created simple jspx page with the af:link (btw af:goLink does not exists in JDev 12c), set 'destination' to myreport.jsp
After the steps above I could not even compile the application, many problems too many to list here, Basically JDev is trying to build the project with .jsp file generated in Report Builder and is unable to.
So to be sure we are on the same page: I am trying to embed JSP report files generated by Report Builder into ADF project, then create EAR file and deploy on standalone WLS. Finally execute JSP web only report.

Change labels on Portal Login page

Hi community,
We are running Portal 7.00 SP21 version and on Portal Logon page we have enabled Get Support link. Now we want to cutomize labels on page wich is shown through the Get Support Link (not welcome page).
If we unzip the file umelogonbase.jar, we can find under dist\PORTAL-INF\lib - we can find the file "logonLabels_" which contains the language we are using. Also we find the key which is used in the tag (for us it is LAST_NAME) and change the text after the equal sign. Then we save the changed file and create a updated JAR file using a zip program but named umelogonbase.jar, not umelogonbase.zip or umelogonbase.jar.zip. - Put again the JAR file back to dist\PORTAL-INF\lib. Restart server, Portal cache and temp files, we don't get applied this change.
This works ok for Welcome page, where by the same way, we can change labes and after restar/clear, we get applied those changes.
So, how can I change the labels on Get Suppot page??
We can not use NWDS....
Thanks !

Hi,
Thanks a lot for your answers.
First, on umResetPasswordPage.jsp I have found the code where "LAST_NAME" must take a value from other file (Could be from umelogonbase.jar?) so, maybe it is not the right place to change it, isn't it? or did you suggest by other way?? This is the code on the umResetPasswordPage.jsp file:
<td width="161" height="20">
        <label class=urLblStd for="logonlastnamefield">
          <%=logonLocale.get("LAST_NAME")%>
          <span class=urLblReq> *</span>
        </label>
      </td>
Second, On Portal Content there is not any Page/Iview wich manage this Support (LogonHelpApp) page openned by "get Support" link on Welcome Portal Page. At this time, I could not find if is it a webdynpro or other component Portal....

Calling portal framework page from non portal page

Hi,
We are having some difficulty in passing control from the non portal pages to
the Portal Pages.
To explain you more elaborately, I am writing down the scenario:
Both our portal and non portal pages reside under the same web application folder.
We have a Portal Page containing one portlet.Clicking on one of the hyperlink
on this portlet page takes us out of the portal environment where we are doing
some processing.
(Why we are going out of the portal environment is because we want to call the
existing pages as it is and our intention is not to make the existing pages portal
enabled to start with).
Somewhere down the journey on the non portal page, there is a requirement to call
the Portal Framework page.
We can call the portal Framework page from the non portal page by hard coding
the URL of the Portal page by writing something like this in href:
http://localhost:7501/application?origin=content.jsp&event=bea.portal.framework.internal.portlet.event&pageid=home&portletid=bachome_carsearchlink&wfevent=link.next
But this is not what we want. We want to call the portal page without hard coding
the URL.
If we use portlet tag in non portal page to call the Portal Framework page ( <a
href="<portlet:createWebflowURL event="link.next"/>">Next Page</a>), it throws
us error "Could not find current Portlet State" which is quite understandable,
because portlet state is now lost.
Is there any way we can achieve this .
Any suggestions or ideas?
Thanks
Ajay

Hi
i think you should use portal:createPortalPageChangeURL (you are effectively changing
your portal page) .
if you want to invoke a specific event in your portlet webflow you can either
write a RefreshControllerIP or use WebflowJSPHelper.createWebflowURL.
bear in mind if you have urls that directly go to an intermediate event in the
portlets webflow you may need
http://dev2dev.bea.com/codelibrary/code/portlet_pp.jsp
regards
deepak
"Ajay" <[email protected]> wrote:
>
Hi,
We are having some difficulty in passing control from the non portal
pages to
the Portal Pages.
To explain you more elaborately, I am writing down the scenario:
Both our portal and non portal pages reside under the same web application
folder.
We have a Portal Page containing one portlet.Clicking on one of the
hyperlink
on this portlet page takes us out of the portal environment where we
are doing
some processing.
(Why we are going out of the portal environment is because we want to
call the
existing pages as it is and our intention is not to make the existing
pages portal
enabled to start with).
Somewhere down the journey on the non portal page, there is a requirement
to call
the Portal Framework page.
We can call the portal Framework page from the non portal page by hard
coding
the URL of the Portal page by writing something like this in href:
http://localhost:7501/application?origin=content.jsp&event=bea.portal.framework.internal.portlet.event&pageid=home&portletid=bachome_carsearchlink&wfevent=link.next
But this is not what we want. We want to call the portal page without
hard coding
the URL.
If we use portlet tag in non portal page to call the Portal Framework
page ( <a
href="<portlet:createWebflowURL event="link.next"/>">Next Page</a>),
it throws
us error "Could not find current Portlet State" which is quite understandable,
because portlet state is now lost.
Is there any way we can achieve this .
Any suggestions or ideas?
Thanks
Ajay

Link to iview or page in content area

hello,
can i have links to iviews or pages in the content area? if yes, how do i do that?
thx
irina
points will be given for any answer that helps

Hi Galan,
One way that you can link to an iview is by using what's called a Quick Link. Open up the properties to the iview that you want to link to, give a name to your iview in the 'Quick Link' field, and then save your changes. Then, use a url like this to access your quick link:
https://portal.mydomain.com/irj/portal/MyQuickLink
For example, if we named our Quick Link 'MyApplication', our url would look like this:
https://portal.mydomain.com/irj/portal/MyApplication
Give it a try. I hope this helps!
-StephenS

Calling an existing iView/page

HI
How to call an existing iView/page from a jsp page.
Thanks
Shashank

Hi,
You can call the iview directly with an URL..URL format looks like below.
http://server:port/irj/servlet/prt/portal/prtroot/<PCD_LOCATION_URL>
Replace the server with your host name and port with you port number and copy the PCD URL of an iview after prtroot in the above URL and change the PCD URL as mentioned below
replace ':' with '!3a'
replace '/' with '!2f'
Hope this helps you..
Jojo

Unable to login from portal home page

We have installed oracle9iAS portal service. we got the portal home page but when we pressed
login link on this page we got an error saying
Error: You cannot login because there is no configuration
information stored in the enabler configuration table. (WWC-41439)
we just want to know furthur details about this.
will you please tell us details about this.?
Actually when we were installing oracle9iAS we got some messages saying that some queries could not
execute and asked for continuing with default settings. So we continued with default settings after
several RETRIES.
The database for oracle9iAS exists in different machine in the network.(I think this is not a problem)

run ssodatan.cmd (for NT)if this is your only node.
or
run ssodatax.cmd (for NT)if you are associating portal to an existing Login Server
The scripts reside in your %IAS_HOME%\portal30\admin\plsql directory

Error on Portal Logon Page

Hi Experts,
We are getting exception while calling the Portal URL.
Recently, we changed the password policy and made some customizations on the com.sap.portal.runtime.logon.par file.
After that when I tried to access the Logon page, it gave an exception.
I even replaced the customized logon par file with the original one but it did not help.
Please note that I deployed the logon par file with the same name, so I did not have to make any changes in the authschemes.xml file.
So ideally when I replaced the customized PAR file with the original one, it should have worked out.
Can it be because of some UME property "Password Policy change" or something like that which has been changed by our Basis team in the Config tool and which is creating issues now.
Is there any connection between the UME property and the Portal Logon page? I know that UME comes into picture once the user clicks on Login button after entering the login credentials but does it also come in picture at the portal logon page call?
We are not able to trace out the root cause as both Password Policy Change and deployment of PAR was done parallely due to which we are confused about the cause of the issue.
Please find below the trace against the exception ID:
#1.5 #5CF3FC5B7E1C00670000000300001B400004ACA7F25E4315#1315737232519#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#Guest#0##n/a##8b1ef68fdc6111e0a5840000061bff66#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Java###04:03_11/09/11_102498150 An error occured in iView: N/A in component: N/A##
#1.5 #5CF3FC5B7E1C00660000000100001B400004ACA7F2896FC1#1315737235348#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#0##n/a##184d79b1dc6111e087880000061bff66#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###Shutting down Application Brokerage...#
#1.5 #5CF3FC5B7E1C00660000000800001B400004ACA7F2940472#1315737236039#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#0##n/a##184d79b1dc6111e087880000061bff66#SAPEngine_Application_Thread[impl:3]_8##0#0#Error#1#/System/Server#Java###[PortalServiceItem.release] exception caught releasing com.sap.netweaver.coll.appl.rtc|RTCClientPollingService
[EXCEPTION]
#1#java.lang.NullPointerException
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.unsubscribe(RTMFMessaging.java:1040)
     at com.sap.ip.collaboration.core.api.rtmf.core.cluster.ClusterSystemManager.unsubscribe(ClusterSystemManager.java:133)
     at com.sap.ip.collaboration.core.api.semantic.services.RTCBaseService.destroy(RTCBaseService.java:146)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.release(PortalServiceItem.java:389)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1159)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:575)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:680)
     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)
     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)
     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)
     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:731)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)
     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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
#1.5 #5CF3FC5B7E1C006F00000002000016140004ACA819F31491#1315737896495#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#Guest#0##n/a##1647a148dc6311e0aaaa0000061bff66#SAPEngine_Application_Thread[impl:3]_9##0#0#Error##Java###04:14_11/09/11_102498150 An error occured in iView: N/A in component: N/A##
#1.5 #5CF3FC5B7E1C007000000000000016140004ACA81A149C1D#1315737898689#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Guest#0##n/a##18319b2cdc6311e092af0000061bff66#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server#Java###An error occured during authscheme computation.
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.runtime.logon.certlogon
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
     at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.getLogonIView(AuthenticationService.java:233)
     at com.sapportals.portal.prt.service.hook.SecurityHookService.doNodeHook(SecurityHookService.java:177)
     at com.sapportals.portal.prt.connection.PortalHook.doNodeHook(PortalHook.java:469)
     at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:138)
     at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:50)
     at com.sapportals.portal.prt.pom.PortalNode.createComponentNode(PortalNode.java:275)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:617)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.sap.portal.navigation.Gateway.service(Gateway.java:117)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.ume.component.logon.SAPMLogonCertComponent of Portal Component com.sap.portal.runtime.logon.certlogon because: Linkage error while loading implementation class
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
     at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
     at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
     ... 33 more
Caused by: java.lang.NoClassDefFoundError: com/sap/security/core/logonadmin/IAccessToLogic
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
     ... 37 more
Thanks & Regards.
Anurag

Hi,
Check if your portalapp.xml has an entry "<property name="ClassName" value="com.sapportals.portal.ume.component.logon.SAPMLogonComponent"/>"
If it is there, then I feel that this is an issue with jar files not getting imported properly.
Just try including these two jars (umlogonbase.jar and com.sap.portal.runtime.logon_api.jar) from
usr\sap\J2E\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.runtime.logon\lib
and copy manually to the lib folder under PORTAL-INF in your project.
Regards,
Vijay.

Portal Logon page repeating/ redirecting to itself on first attempt

All,
Apologies in advance if this is not the appropriate forum. We are in the process of migrating a NW7.0SPS13/EP7.0SPS13 installation from a remote site to a local site with a database only UME and SSO to an ECC6.0 backend. The new target installation has picked up a rather odd behavior. When loggin onto the portal, the logon page repeats/refreshes/redirects to itself with valid ID and password with no error message. The only apparent action is the clearing of the password field.
My only clue so far is the absence of this script in the http trace on the initial logon attempt which shows up on the second attempt:
http://<host>:51100/irj/portalapps/com.sap.portal.httpconnectivity.httpauthentication/scripts/CAManagerScript.js
I did find this related thread and attempted the suggestions with no luck:
Re: portal logon page coming again
I felt this might be the best place to post question since this may be an authentication/connectivity issue.
Thanks in advance,
Lee

You are correct, we are not implementing SPNego but at this point I will take any suggestions that might be conceptually related...
We are attempting to migrate/clone the entire server (OS,J2EE,MSSQL05...) from a remote hosted environment to a local network environment.
I checked the Everyone, Authenticated, and Anonymous groups for the correct roles/Java permissions and all seems to be in-line with the correctly functioning remote system with correct user assignment.
With some further log filtering I was able to where find this error:
The default keystore view [TicketKeystore] does not exist. Authentication stack: [ticket]. The possible reasons for that problem are: keystore does not exist or the user has no permission to read from the keystore view. You can delete the TicketKeystore and restart the engine so that the engine automatically re-creates it.
I suspect the SAPLogonTicketKeystore was recreated incorrectly... I will have the migration team recreate it again. FWIW, I am unfamiliar with the process of assigning user access to this object as the error suggests.
Thanks for the suggestions...

Portal 6 // Link existing 'iView' to Portal HMTL page

Similar Messages

Maybe you are looking for