I'm facing issue regarding REFRESH functionality in WDP ..The issue is i have REFRESH(FPM Button) on my screen and when ever the user clicks on it , the screen should refresh(should come to initial state).

And on refresh button event, i'm launching the screen by using below code.

But, when appl'n is tested from portal, it is working incorrectly. If i pass parameter use_suspend_plug = ' ', first time on click of refresh button in portal,it is opening screen in portal it self, and on second click of refresh button in portal screen, it is opening screen in new window.

Is it better to launch the appl'n or to refresh/clear all the screen element values and bind it again?... Here i have one more probelm, the ex-developer of the component has declared some attributes(nearly 15 attributes) in view controller(which cannot be access in component controller) and i cannot read those view controller attributes in component controller. so that i can read those attributes and clear the values( which is not possible now).

Pls help me to achieve REFRESH(F5) functionality .

Thanks

↧

Portal Theme -> not able to replace horizontal divider

April 9, 2010, 12:13 am

Latest and popular articles on SAP ERP

≫ Next: Portal 7.3 & Web Dynpro iView, both accessed from Internet via Web Dispatch

≪ Previous: Refresh functionality in portal

Hi All,

I want to replace the blue colored bar under the TLN. But I am not able to do so.

I tried changing it through Theme -> Horizontal Divider but it takes the blue color again. (Separator.gif)

I am also trying to modify it thru com.sap.portal.navigation.toplevel.par but I am not getting where to change it. I am unable to find where exactly it refers to the bar.

Please guide where should I change in the par file . Any pointers will be helpful.

Regards

Shilpa Bhanot

↧

Portal 7.3 & Web Dynpro iView, both accessed from Internet via Web Dispatch

November 28, 2011, 8:02 pm

Latest and popular articles on SAP ERP

≫ Next: F4 is not working in Portal

≪ Previous: Portal Theme -> not able to replace horizontal divider

Hi guru,

I'd like to know the best (or the correct) way to configure the FQDN and required DNS setting to allow user access ABAP Web Dynpro iview from internet.

My setup here is very typical:

One EP 7.3 in intranet, having "ep.internal.mycomp.com" as FQDN (given during installation)
One SAP ECC in intranet, having "erp.internal.mycomp.com" as SAPLOCALHOSTFULL parameter
One Web Dispatcher in DMZ, having "service.mycomp.com", and listen to 80 port (later added 8000 port for AS ABAP).

User access my portal by using http://service.mycomp.com/irj, no problem.

But problem raised during access WD4A iview, here are my problem and questions:

[Problem]

At the beginning, we found that the WD4A iView can only be accessed in intranet, not from internet. Eventhough we register "service.mycomp.com" in public DNS. After some http level analysis, I was shock that the WD4A iview is provided directly by AS ABAP which running this WD4A, EP does not play a "relay" role. (Don't believe the URL bar in your IE, use Tamper Data or HTTP live to check the HTTP requests, you will get it). Since we DO NOT have "erp.internal.mycomp.com" in public DNS, so the iview cannot be displayed. But I DON'T want direct access to my ERP box.

I don't know a way to get rid of the "erp.mycomp.com" request generated by EP. So I tried to overcome the problem by leveraging the same Web Dispatcher used by EP. And I did make the WDisp -> ERP WD4A work using WDisp's FQDN (ie. service.mycomp.com:8000, also keep original service.mycomp.com:80 to EP), but the iview in EP does not use this FQDN. It use the SAPLOCALHOSTFULL parameter configured in backend ERP. WDisp does not do any URL replacement for me.

[Question 1]

Is there any way to hide WD4A iview in EP (server to server communication only)?

[Question 2]

If I can only have "service.mycomp.com" entry in my public DNS, should I change the SAPLOCALHOSTFULL in ERP to "service.mycomp.com"? I doubt that it may cause a "loop" situation between WDisp and ERP ?

[Question 3]

Is it possible to access WD4A on ERP by two different FQDNs (one for public via WDisp, the other for internal access w/o WDisp) ? I know there is only one SAPLOCALHOSTFULL configuration.

Anyone have done such integration ? please share your configuraiton. Thanks

↧

F4 is not working in Portal

April 9, 2014, 2:01 am

Latest and popular articles on SAP ERP

≫ Next: Parameter from iview to transaction

≪ Previous: Portal 7.3 & Web Dynpro iView, both accessed from Internet via Web Dispatch

Hi All,

I am running BEx Report in portal through - RSRT - Java Web .

Here my BW Query have Input variables and when I am trying to get F4 help , then list of values are not coming.

For same Query and variable - list of values are coming in Bex analyser.

Master data is available for characteristics.

IE version is 11.0

It is happenings for all queries in my BW system.

Here I tried to do F4 search for DIVISION and it got struck(Below Image)

Any suggestions.

Regards,

Vijay

↧

Parameter from iview to transaction

April 14, 2014, 7:13 am

Latest and popular articles on SAP ERP

≫ Next: Cannot process expression

≪ Previous: F4 is not working in Portal

Hi SDN,

How can I transfer a parameter from iview to a Z transaction ?

I've tried using application parameter but I suppose, on this case, the parameter must be a screen field. I don't want to use a screen field. Is there any other way?

Thanks

Maria João Rocha

↧

Cannot process expression

April 14, 2014, 9:36 am

Latest and popular articles on SAP ERP

≫ Next: Activate SSO with AD Kerberos

≪ Previous: Parameter from iview to transaction

I am getting below error when accessing Standard PPM contents using Webdynpro for ABAP iview from Portal. System Alias is defined properly.

Portal Version: NW 7.31 SP09

#2.#2014 04 14 09:54:29:815#0-600#Error#com.sap.portal.prt.runtime##EP-PIN- PRT#tc~epbc~prtc~api#C0000A0B024E19FD000000030176009A#595464950000000004#sap.com/com.sap.portal.runtime.system.hooks#com.sap.portal.prt.runtime#BPate

l#565##DC0A0FB0C3E711E3A07E0000237E12F6#10140ad2c3ed11e39b520000237e12f6#10140ad2c3ed11e39b520000237e12f6#0#Thread[HTTP Worker [@1635624791],5,Dedicated_Appl ication_Thread]#Plain## 09:54_14/04/14_0042_595464950

[EXCEPTION]

com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to parse template 'sap-cssurl=<LAF.StylesheetUrl[URL_ENCODE]>&<LessThemeParameter[IF_false PROCESS_RECURSIVE]>&sap-cssversion=<LAF.Version[URL_ENCODE]>&<TrayInformation[IF_false PROCESS_RECURSIVE]>'; the problem occured at position 11. Cannot process expression <LAF.StylesheetUrl>

.......

Caused by: com.sapportals.portal.appintegrator.template_processor.TemplateParserException: Unable to parse template 'sap-cssurl=<LAF.StylesheetUrl[URL_ENCODE]>&<LessThemeParameter[IF_false PROCESS_RECURSIVE]>&sap-cssversion=<LAF.Version[URL_ENCODE]>&<TrayInformation[IF_false PROCESS_RECURSIVE]>'; the problem occured at position 11. Cannot process expression <LAF.StylesheetUrl>

............

Caused by: java.lang.NullPointerException: while trying to invoke the method com.sapportals.portal.prt.service.laf.IThemePartInfo.getThemeType() of a null object returned from java.util.Map.get(java.lang.Object)

Bhavin

↧

Activate SSO with AD Kerberos

April 14, 2014, 5:18 am

Latest and popular articles on SAP ERP

≫ Next: TREX cluster

≪ Previous: Cannot process expression

Hello,

I installed a Netweaver 7.4 AS Java Portal with a MaxDB instance inside a test environment.

I would like to validate (amongst other features) the SSO capability.

To do so I created another Win 2008R2 server that I configured with an AD server.

Within the AD I created two users:

* "j2ee-RM1" where RM1 correspond to my netweaver instance.

* "viewer2" which purpose is to be a plain user to test the connection as SSO client.

In Netweaver, I configured the SPNEGO via it's dedicated wizard. (http://mysap_ip:50000/spnego) using the j2ee_RM1 ID and related domain.

Then I connected as "viewer2" on the Win AD server. Via Internet Explorer I navigated to the Netweaver portal URL.

I expected To be logged directly into the portal but instead I got the usual SAP Login frame.

I searched and digged into SCN, notes and other documentation, but I found nothing that was clear enough to help me in this validation process.

Who knows about a clear and complete documentation to setup this SSO stuff?

Renaud

↧

TREX cluster

April 14, 2014, 12:13 am

Latest and popular articles on SAP ERP

≫ Next: Cannot see the role immediately that is assigned to an user in SRM integrated EP portal 7.0

≪ Previous: Activate SSO with AD Kerberos

Hello colleagues,

I have two nodes in cluster, node A and node B. In the configuration nameserver I have the name C (cluster name)

In the node A the console Trexadmin the index is green. In node B the console Trexadmin the index dont exist.

How to configure properly? The find in EP dont work.

TREXADMIN node A

INDEX node A

SERVER STATUS TREX MONITOR

ERROR FIND IN PORTAL

Can you help me?

Thanks

↧

Cannot see the role immediately that is assigned to an user in SRM integrated EP portal 7.0

January 15, 2014, 4:13 am

Latest and popular articles on SAP ERP

≫ Next: UWL refreshes doesnt follow Delta Pull Channel Refresh Period (90secs), refreshes at random timings.

≪ Previous: TREX cluster

Hi Friends,

I have an issue related to SRM integrated EP portal 7.0

Whenever i create a new role or any existing role, I assign it to any user, I cannot see the role immediately in the home screen of the portal.

The role appears and reflects after 4-5hours on the home screen.

I am not able to find out the issue, I have cleared my cache and also tried to open portal in Mozilla but it doesn't seem to be a browser specific issue.

Can you guys please help me solve my problem.

Thanks & Regards,

Shumana Roy.

↧

UWL refreshes doesnt follow Delta Pull Channel Refresh Period (90secs), refreshes at random timings.

April 7, 2014, 7:52 am

Latest and popular articles on SAP ERP

≫ Next: Single Sign On problem

≪ Previous: Cannot see the role immediately that is assigned to an user in SRM integrated EP portal 7.0

Hi,

We are using SAP NW 7.3 ehp7.

The Delta Pull Channel Refresh Period is set to 90 seconds but the UWL refresh doesnt follow this timing interval.

The batch job for this is scheduled for every one minute , however the UWL refreshes at random intervals.

Can anyone please help in this?

Regards,

Arghya Samanta

↧

Single Sign On problem

April 15, 2014, 1:44 am

Latest and popular articles on SAP ERP

≫ Next: com.customer.afp.fromscratch modify ajax fwk l-shape api

≪ Previous: UWL refreshes doesnt follow Delta Pull Channel Refresh Period (90secs), refreshes at random timings.

Dear Suport,

We have one problem about Single Sign On in portal,the portal environment is cluster,we had configed Single Sign On, when i logon on A manchine to test Single Sign On that is ok,but when i logon on B manchine to test Single Sign On that is bad. I test jco and rfc that is ok.Pls help me.Thanks.

The errror msg as below:

PortalSystemLandscapeSource.getConnection(IUser,String,DestinationFilter,Map) Failed to get connection. Original exception: A nested exception occurredCould not initialize physical connection. Linked Exception: A nested exception occurredCould not create JCO connection. Linked Exception: \#\#\#\#\# SSO \#\#\#\#

[EXCEPTION]

com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection.

at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewConnectionFailedLocalizedException(SAPConnectorException.java:182)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:155)

at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:401)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:295)

at com.sap.engine.services.connector.jca.ShareableConnectionManager.allocateConnection(ShareableConnectionManager.java:54)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:173)

at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:401)

at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:354)

at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:305)

at com.sap.portal.connectivity.destinations.portal.PortalSystemLandscapeSource.getConnectionWithOverridingProps(PortalSystemLandscapeSource.java:120)

at com.sap.portal.connectivity.destinations.portal.PortalSystemLandscapeSource.getConnection(PortalSystemLandscapeSource.java:93)

at com.sap.portal.connectivity.destinations.impl.DestinationServiceImpl.getConnection(DestinationServiceImpl.java:185)

at com.sap.portal.connectivity.destinations.DestinationsService.getConnection(DestinationsService.java:102)

at com.sap.portal.comp.TestConnectionComp.isConnectionOK(TestConnectionComp.java:370)

at com.sap.portal.comp.wdp.InternalTestConnectionComp.wdInvokeMethod(InternalTestConnectionComp.java:212)

at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)

at com.sun.proxy.$Proxy775.isConnectionOK(Unknown Source)

at com.sap.tc.pp.adm.wu.system_landscape.SystemLansdcapeOverviewComp.testConn(SystemLansdcapeOverviewComp.java:717)

at com.sap.tc.pp.adm.wu.system_landscape.wdp.InternalSystemLansdcapeOverviewComp.testConn(InternalSystemLansdcapeOverviewComp.java:289)

at com.sap.tc.pp.adm.wu.system_landscape.SystLansdcapeOverviewCompView.testConnection(SystLansdcapeOverviewCompView.java:2256)

at com.sap.tc.pp.adm.wu.system_landscape.SystLansdcapeOverviewCompView.onActionTestConnection(SystLansdcapeOverviewCompView.java:758)

at com.sap.tc.pp.adm.wu.system_landscape.wdp.InternalSystLansdcapeOverviewCompView.wdInvokeEventHandler(InternalSystLansdcapeOverviewCompView.java:787)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)

at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)

at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingEmbedded(ApplicationSession.java:919)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:878)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:62)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:39)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:46)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:292)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToAppContext(ExecutionContextDispatcher.java:68)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:53)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:245)

at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callRequestManager(JavaApplicationProxy.java:1244)

at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callEmbeddedApplication(JavaApplicationProxy.java:1122)

at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$SendDataAndProcessActionCommand.doExecute(JavaApplicationProxy.java:1605)

at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$AbstractCommand.execute(JavaApplicationProxy.java:1488)

at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.execute(JavaApplicationProxy.java:1028)

at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.execute(JavaApplicationProxy.java:859)

at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.sendDataAndProcessAction(JavaApplicationProxy.java:468)

at com.sap.tc.webdynpro.portal.pb.impl.JavaApplicationProxyAdapter.sendDataAndProcessAction(JavaApplicationProxyAdapter.java:191)

at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1698)

at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:369)

at com.sap.portal.pb.PageBuilder$PhaseListenerImpl.doPhase(PageBuilder.java:2123)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:251)

at com.sap.tc.webdynpro.clientserver.phases.PortalDispatchPhase.execute(PortalDispatchPhase.java:50)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)

at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)

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

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

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

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

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

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)