Portal logon page custamization

[Former Member]

Hi friends

i am working on portal logon page custamization. i modified some content in logon par file place in pcd. i got exception below

[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:154)

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:240)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)

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:126)

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:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

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:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

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: Could not find implementation class

at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:242)

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)

... 35 more

Caused by: java.lang.ClassNotFoundException: com.sapportals.portal.ume.component.logon.SAPMLogonCertComponent

-

---

Loader Info -

---

ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@e557ec]

Parent loader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@7ba26f]

References:

not registered!

No resources !

-

---

at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:382)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)

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)

... 39 more

I didnt get my logon screen with original par also

please help me how to resolve this and how to modify par file and deoploy it on WAS.

Regards

narayana

[Former Member]

Thanks guys

[Former Member]

Hi,

In your portalapp.xml do you have an entry "<property name="ClassName" value="com.sapportals.portal.ume.component.logon.SAPMLogonComponent"/>"

If so, check out whether "com.sap.portal.runtime.logonapi.jar" is present in "..\dist\PORTAL-INF\exlib" in the custom par file

Regards,

Harini S

[javed_shaikh]

It seems that you have not changed the authschemes.xml file and directly deployed the changes on the original file, ok no matter,

copy the authschemes.xml file (as mentioned in Step 2 e ) form your developement or QA portal and overwrite the server where it is not working and depoly,

first ensure the your old std logon page is loading, once it is done then as mentioned below run the following steps and you will be sure able to customize the logon page.

Remember this time dont forget to change the name of the xml file as mentione in step 2 e.

Below are the steps to customise the portal login page:

Step I:

1. Copy PAR u201Ccom.sap.portal.runtime.logon.par.baku201D to local directory

2. Rename the PAR file.

3. Import the renamed PAR file into NWDS.

4. Add the jar file into directory dist\PORTAL-INF\Private\lib by unzipping the contents of the PAR file.

5. Make necessary modifications to the file u201CumLogonPage.JSPu201D, u201CumLogonBotArea.txtu201D.

6. Save the file. Rebuild Project.

7. Export the PAR file with the changed name.

Step II: Modification of Authschemes.xml to reference the new PAR file containing the modified logon UIs

http://Ensure that all dispatcher and server nodes in the cluster are shut down.

1. Start the Config Tool by executing <SAPJ2EEEngine_installation>\j2ee\configtool\configtool.bat.

2.Choose the symbol for Switch to configuration editor mode.

3.In the tree, navigate to cluster_data -> server -> persistent -> com.sap.security.core.ume.service.

4. To switch to edit mode, choose(Switch between view and edit mode).

5. In the tree, select authschemes.xml and choose (Show the details of the selected node).

6.Choose Download and save the file to a local directory.

7.Edit the file locally.

8.Create a new node in the configuration tree for the edited file as follows:

a. Select the node com.sap.security.core.ume.service.

b. Choose the symbol for Create a node below the selected node ( )

c. Select the type File-entry.

d. Choose Upload and select the file from your local directory.

e.Enter the name for the entry, for example, authschemes_productive.xml. By default, the name of the uploaded file is used.

f.Choose Create.

g. Choose Close window.

The new node appears in the configuration tree.

For UME to use the new file, you have to change the value of the property login.authschemes.definition.file to the name of the new authschemes file. http://Change the property as described in Editing UME Properties.

9. Restart the nodes in the cluster for the changes to take effect.

Step III: Editing UME Properties

Procedure

http://Ensure All cluster elements are shut down.

1.Start the Config Tool by executing <SAPJ2EEEngine_installation>\j2ee\configtool\configtool.bat.

2.Choose the symbol for Switch to configuration editor mode.

3. In the tree, navigate to cluster_data->server ->cfg ->services

4.To switch to edit mode, choose (Switch between view and edit mode).

5.In the tree, double-click on Propertysheet com.sap.security.core.ume.service.

6. Click on the property you want to change.

To enter a custom value, enter it in Custom and choose Apply custom.

To reset a value to its default, choose Restore default.

7. To save the changed properties, choose OK in the property sheet view.

8. Restart the nodes in the cluster for the changes to take effect.

Cheers!!

SJ.

[Former Member]

Hi SJ

My portal login error was resolved and i modified some text in umlogonpage.jsp. it is working.

i replaced all logon par file with original par files and xml file from other server

thank u

[javed_shaikh]

Hey thats gr8 felt good that your problem is solved and i was of some help to you.

Request you to please close the thread now.

Cheers!!

SJ.

[Former Member]

When you take the logon par file from the server and import into NWDS, 2 jar files that are part of original downloaded par file dont get imported into the project. The jar files are com.sap.portal.runtime.logon_api.jar & umelogonbase.jar exist in the original par file in the folder PORTAL-INF/lib. Copy these 2 jar files into the NWDS project into PORTAL-INF/lib, then compile your code and run it.

Pradeep