Enable Team calender page navigation option

Hello Experts,
When a manager open Team calender application table is very big and need to scroll alot becasue manager having 150 direct employee.
So to void scroll bar we are done in setting in spro V_PTARQ_TCALE as 15 rows w.r.t rule group . But when we run the application these setting are not refelecting .
We are in EHP 6 and using WDA application.
application name:hrmss_team_page
Application configuration:HRMSS_TEAM_PAGE
is it possible to make pagenation enable in team calender ? if yes how ?
Regards
Malli

yes, it's not restricting based on that configuration i.e no.of line items per page. It's only working for WDJAVA based application.
For this you have to enhance the component of Select Team Members as below marked screen shot.
Here by default it's Display All employees.
You can enhance to this and set the default option to display Absent only option

Similar Messages

How to achieve Page Navigation in af:table component

I am using JDeveloper 11.1.1.3.
I have a requirement for which i dont know how to proceed. Please guide me on the below requirement.
I have an af:table component which displays a list of all the employees from the database. The total number of records in my database is 300(employee table).
So my af:table component while displaying the Employee view object displays all the 300 employees when i scroll down the list.
But i dont want the user to scroll down to see all the employees. In the af:table footer i want the page navigation option to be shown which will allow the user to see 10 records per page. When the user clicks on the next button , the af:table should display the next 10 records of the view object.
Kindly help me or guide me to some reference material on how can i achieve this.
Zeeshan

There is no out-of-the-box table pagination in ADF 11g, the scroll-table is the way to go. New content is fetched only as needed when the user scrolls down the list. You can use the table's column filters or a separate search query component to make it easier to find employees on the list.
See previous discussions, e.g. Urgent!! Pagination in ADF 11g.. and ADF Faces - Table Navigation in 11g

In OBIEE mobile apps designer there is no option for multi select prompts?The navigation page gives option only for single select?Is there a work around for this?

In OBIEE mobile apps designer there is no option for multi select prompts?The navigation page gives option only for single select?Is there a work around for this?

Nic, for me the iTunes window looks like this, when I connect my iPad 3:
I select the iPad in the "devices" section of the Sidebar (use: "View > Show Sidebar" if the sidebar is hidden).
Click the "Apps" tab in the "Devices" pane.
Scroll all the way down in the Devices pane to "File Sharing" "Apps" section.
Then do I click "GarageBand" to select the documents in the right panel.
Which part is different for you? Perhaps you could post a screenshot?
Regards
Léonie

ADF 10.1.3 : no mean to put off the option "display all" in page navigator

Hi everybody,
In top right of a table componenent, there is a page navigator (1-10 of 1000, 11-20 of 1000 and so on).
The first option of this sub-component is "Display all of 1000".
I'd like to put off this option but i haven't seen any property to allow that ?
Otherwise, is there a mean to forbid this action ?
Christophe,
Edited by: cpierres on Aug 11, 2009 9:34 PM

cpierres wrote:
This is a good idea.
Unfortunately, it sounds like a "all or nothing" solution.
but very interesting idea.
Thank you very much for your answer,Not necessarily all or nothing - if you can find a directive that does what you want, you can put it in your skin's CSS file like this:
noDisplayAll {
# directive to tell af:table to disallow display all
}Then set the table attribute styleClass="noDisplayAll" for any table to which you want to apply this.

JSF 2.0 page navigation vs direct page access

I've been experimenting with JSF for some time now and I still don't understand the page navigation part. I know that in JSF, if you aren't using the redirect option in navigation that the URL is one page behind the page you are on.
I've seen articles where people say you should put your pages in a directory under WEB-INF to protect against directly accessing the page. I don't understand how you can create an application that is multiple pages using that option, because won't you run into the problem of having a form with an action URL of WEB-INF/somepage.xhtml?
I've also read articles that say the way to fix this is to add security-constraints to web.xml that prevent "direct access" to pages, when you want your user to follow a page flow, such as start on page1.xhtml, then page2.xthml, then end on page2.xhtml. If page3.xhtml depends on page2.xhtml, the articles I've read say that a security constraint prevents users from simply requesting page3.xhtml out of sequence.
And what happens if the page you are on encounters an error or the session times out, which page handles that? The one you're on, or the one from before that forwarded you to the page you're on?
In this example, should page2.xhtml and page3.xhtml go in the root of the webapps directory, or in a directory under WEB-INF?
Webapps
index.xhtml
page1.xhtml
page2.xhtml
page3.xhtml
WEB-INF
    faces-config.xml
    web.xml
    page-directory
      page2.xhtml
      page3.xhtml

A session timeout should actually net a view expiry exception.
You do know that JSF 2.0 made page navigation that bit easier by not requiring you to do the XML configuration? There is now a convention built in plus some new components to add GET enabled requests to the JSF lifecycle (notably h:button and h:link). If you have an action method that returns the following:
public String doSomething(){
return "something";
}then JSF will by default want to render a view 'something.xhtml' when you don't define any navigation rules. If you want to make that a redirect you can do this:
public String doSomething(){
return "something?faces-redirect";
}(of course this is a prime target to turn into a utility method on a backing bean base class).
Navigation rules are still necessary when you want to put views in a subdirectory, but at least this way you can greatly simplify general cases. Other than that I can only say: research research research because this material is vital to understand if you want to be productive using the framework; navigation and the 6 JSF lifecycle phases are two items you should put on the top of your list to hammer out until you really get it. A good JSF book will help you immensely there. Balusc's blog is also a good source of deeper understanding:
http://balusc.blogspot.com/
Most of his articles are on JSF 1.2 but most of the information still applies.
Oh and its no surprise that you're a bit confused - this framework is not easy to pick up especially when you don't know any other web frameworks. If you keep running into a wall you should consider checking out something else like Wicket or Play framework. It might just be that JSF simply isn't the tool for the job you're trying to do.

Regarding Leave & Team calender

Hi ESS/EP Gurus,
We are working SAP ESS/MSS with ECC6.0 and EP7.0,and the patch leave in the portal is SPS13 and we deployed business pakages for ESS and MSS for 1.0, configured all necessary steps in the backend for leave request its working fine all the services.
Recently we dployed support package for ESS 1.2 i dont what happent Leave request and team calender not working it throwing some error, can you please help me for this.
please find the the error messages for bith:
Leave request::
java.lang.NullPointerException
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
    at com.sap.xss.hr.lea.model.Pt_Arq_F4Help_Sickcode_Input.<init>(Pt_Arq_F4Help_Sickcode_Input.java:51)
    at com.sap.xss.hr.lea.form.FcForm.wdDoInit(FcForm.java:143)
    at com.sap.xss.hr.lea.form.wdp.InternalFcForm.wdDoInit(InternalFcForm.java:1994)
    ... 67 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Wed Dec 05 20:34:49 IST 2007
J2EE Engine 7.00 patchlevel 109044.44
Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en
Time of Failure Thu Feb 07 14:46:36 IST 2008 (Java Time: 1202375796874)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
     at com.sap.xss.hr.lea.model.Pt_Arq_F4Help_Sickcode_Input.<init>(Pt_Arq_F4Help_Sickcode_Input.java:51)
     at com.sap.xss.hr.lea.form.FcForm.wdDoInit(FcForm.java:143)
     at com.sap.xss.hr.lea.form.wdp.InternalFcForm.wdDoInit(InternalFcForm.java:1994)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:760)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:919)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:890)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1083)
     at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:254)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCale.onInit(InternalVcBlockCale.java:275)
     at com.sap.xss.hr.lea.blockcale.VcBlockCaleInterface.onInit(VcBlockCaleInterface.java:163)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface.onInit(InternalVcBlockCaleInterface.java:144)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface$External.onInit(InternalVcBlockCaleInterface.java:220)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     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)
Team Calender::
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: no jcoMetadata found for RFC function 'PT_ARQ_F4HELP_SICKCODE'! Please verify, that your model is consistent with the ABAP backend: 'HR6'.
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo.getOrCreateClassInfo(DRFCModelInfo.java:217)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo.<init>(DRFCModelInfo.java:164)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo$Cache.getModelInfo(DRFCModelInfo.java:103)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModel.<init>(DynamicRFCModel.java:112)
    at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.<init>(LeaveRequestAdaptiveModel.java:381)
    ... 79 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Wed Dec 05 20:34:49 IST 2007
J2EE Engine 7.00 patchlevel 109044.44
Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en
Time of Failure Thu Feb 07 14:50:37 IST 2008 (Java Time: 1202376037482)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: failed to create or init instance of model 'com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel' in scope APPLICATION_SCOPE with instanceId 'null'
     at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getOrCreateModelInstanceFromScopeMaintainer(WDModelFactory.java:341)
     at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:155)
     at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:102)
     at com.sap.xss.hr.lea.utils.Utils.getModelInstance(Utils.java:34)
     at com.sap.xss.hr.lea.selectionlist.FcSelectionList.onInit(FcSelectionList.java:223)
     at com.sap.xss.hr.lea.selectionlist.wdp.InternalFcSelectionList.onInit(InternalFcSelectionList.java:382)
     at com.sap.xss.hr.lea.selectionlist.FcSelectionListInterface.onInit(FcSelectionListInterface.java:115)
     at com.sap.xss.hr.lea.selectionlist.wdp.InternalFcSelectionListInterface.onInit(InternalFcSelectionListInterface.java:340)
     at com.sap.xss.hr.lea.selectionlist.wdp.InternalFcSelectionListInterface$External.onInit(InternalFcSelectionListInterface.java:392)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:921)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:890)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1083)
     at com.sap.xss.hr.lea.selectionlist.VcSelectionList.onInit(VcSelectionList.java:219)
     at com.sap.xss.hr.lea.selectionlist.wdp.InternalVcSelectionList.onInit(InternalVcSelectionList.java:330)
     at com.sap.xss.hr.lea.selectionlist.VcSelectionListInterface.onInit(VcSelectionListInterface.java:162)
     at com.sap.xss.hr.lea.selectionlist.wdp.InternalVcSelectionListInterface.onInit(InternalVcSelectionListInterface.java:144)
     at com.sap.xss.hr.lea.selectionlist.wdp.InternalVcSelectionListInterface$External.onInit(InternalVcSelectionListInterface.java:238)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
     at com.sap.portal.pb.PageBuilder.wdDoApplicationStateChange(PageBuilder.java:301)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoApplicationStateChange(InternalPageBuilder.java:197)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doApplicationStateChange(DelegatingComponent.java:139)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doApplicationStateChange(ClientComponent.java:667)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doApplicationStateChange(ClientApplication.java:537)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:120)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     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.sap.tc.webdynpro.progmodel.model.api.WDModelException: failed to create instance of model 'com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel'
     at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getNewModelInstance(WDModelFactory.java:392)
     at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getOrCreateModelInstanceFromScopeMaintainer(WDModelFactory.java:329)
     ... 70 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: no jcoMetadata found for RFC function 'PT_ARQ_F4HELP_SICKCODE'! Please verify, that your model is consistent with the ABAP backend: 'HR6'.
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo.getOrCreateClassInfo(DRFCModelInfo.java:217)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo.<init>(DRFCModelInfo.java:164)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo$Cache.getModelInfo(DRFCModelInfo.java:103)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModel.<init>(DynamicRFCModel.java:112)
     at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.<init>(LeaveRequestAdaptiveModel.java:381)
     at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.<init>(LeaveRequestAdaptiveModel.java:356)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:308)
     at java.lang.Class.newInstance(Class.java:261)
     at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getNewModelInstance(WDModelFactory.java:386)
     ... 71 more
Regards,
Sambaiah.
Edited by: Sambaiah Muvva on Feb 7, 2008 10:17 AM

Hi Sambaiah,
Sorry for the late reply. Did you get a solution for the problem. This defineitely seems to be a compatibilty problem with the frontend (ESS business package, XSS sca files (ess, mss, pcuigp) and backend r3 (EA-HR, SAP-HR).
As the error clearly points out com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: no jcoMetadata found for RFC function 'PT_ARQ_F4HELP_SICKCODE'! Please verify, that your model is consistent with the ABAP backend: 'HR6'.
Also, please chek the stack level recommendations for all the components Also, chek note 761266.
Chuckie,Please let us know if you get a reply from the OSS message, as this might be useful to many more of us who are yet to face this issue
Best Regards
Reshma

Why I dont see Pinned Items in Team home page ?

Hello,
I am team administrator, however I dont see pinned items on team home page.
Also, I don't get "Pin to homepage" option on right click of query as well as on chart !!! Why so ?
Would you please tell me the reason and how can I resolve it ?
Thank you in advance !
Dipti Chhatrapati

Hi!
You may pin a query that in the Team Favorites
https://msdn.microsoft.com/en-us/library/jj920199.aspx:

Team Calender only shows 1 week in retropsect

Hi,
We use team calender in ESS in our portal, but we are unable to view records in retrospect further than one week.
I have looked in IMG under ERP, but these options are not available:
- Personnel Management ® Employee Self-Service ® Service-Specific Settings ® Working Time ® Team Calendar.
- Integration with Other SAP Components ® Business Packages / Functional Packages ® Manager Self-Service (mySAP ERP) ® Working Time ® Team Calendar.
I then looked at business functions and found that EA-HR isnt turned on (and when attempting activation tells me that it isnt necessary) and HCM_ESS_CI_1 doesnt even seem to exist!!
Does anyone have any idea what is going wrong?!
Many thanks

team calendar customisation comes from this table
V_PTARQ_TCONSTR., Please check for many months it is specified here
customisation is possible , please check in trans code ptarq, you ll find all the customisaiton for portal
Edited by: Siddharth Rajora on Jun 7, 2011 5:40 PM

Applications Start Page Profile Option Causing Issues

Hello Oracle Gurus,
I'm having an issue in a 12.1.3 instance that I think may be related to the "Applications Start Page" profile option.
For testing purposes, we set the profile to a specific Self-Service page at the Site level. We eventually removed the Site level profile and added it at the user level just for specific users, but since the Site-level profile was set, every time we click the Home link in the upper right-hand navigation, we get an "unexpected error." If we attempt to log in as a user that does not have the Applications Start Page profile defined, we also get an unexpected error.
After getting the error using either of the methods listed above, if we then try to navigate back to the login page, the instance throws a 500 Internal Error.
If we close the browser and navigate to the instance again, we're able to log in without any issues with user accounts that have an Applications Start Page profile defined.
Our "Self Service Personal Framework Mode" is set to "Framework Only" at the site level.
Bouncing Apache seems to resolve the issue temporarily, but then it comes back again a few hours later...
We've opened a Service Request, but has anyone else run into this before / have any ideas on how to fix it?
Here are some related Metalink notes from 11.5.10:
729375.1 (About the Applications Start Page profile option)
331814.1 (Error on Personal Home Page when returning to 'Home' link)
Thanks!
Anne

The issue is not specific to a responsibility or application.
Here is the error:
Fatal NI connect error 12170.
VERSION INFORMATION:
     TNS for Linux: Version 11.1.0.7.0 - Production
     Unix Domain Socket IPC NT Protocol Adaptor for Linux: Version 11.1.0.7.0 - Production
     Oracle Bequeath NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production
     TCP/IP NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production
Time: 27-JAN-2011 09:46:02
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=172.30.31.107)(PORT=1502))
Thu Jan 27 09:53:30 2011
Incremental checkpoint up to RBA [0x42.e3635.0], current log tail at RBA [0x42.e37e1.0]
Thu Jan 27 10:13:31 2011
Incremental checkpoint up to RBA [0x42.e602b.0], current log tail at RBA [0x42.e6146.0]
Thu Jan 27 10:33:33 2011
Incremental checkpoint up to RBA [0x42.e7bc9.0], current log tail at RBA [0x42.e7d51.0]
Thu Jan 27 10:53:35 2011
Incremental checkpoint up to RBA [0x42.e995f.0], current log tail at RBA [0x42.e9ac9.0]
Thu Jan 27 11:13:37 2011
Incremental checkpoint up to RBA [0x42.ec163.0], current log tail at RBA [0x42.ec3f7.0]
Thu Jan 27 11:23:48 2011
Starting background process CJQ0
Thu Jan 27 11:23:48 2011
CJQ0 started with pid=8, OS id=17239
Thu Jan 27 11:33:39 2011
Incremental checkpoint up to RBA [0x42.ee08f.0], current log tail at RBA [0x42.ee216.0]
Thu Jan 27 11:53:41 2011
Incremental checkpoint up to RBA [0x42.efd07.0], current log tail at RBA [0x42.eff13.0]
Thu Jan 27 11:54:02 2011
Stopping background process CJQ0
Thu Jan 27 12:13:43 2011
Incremental checkpoint up to RBA [0x42.f25c0.0], current log tail at RBA [0x42.f2e4b.0]
Thu Jan 27 12:33:45 2011
Incremental checkpoint up to RBA [0x42.f4cae.0], current log tail at RBA [0x42.f4e4b.0]
Thu Jan 27 12:53:47 2011
Incremental checkpoint up to RBA [0x42.f6e8a.0], current log tail at RBA [0x42.f6fb7.0]
Thu Jan 27 13:13:50 2011
Incremental checkpoint up to RBA [0x42.fa3d0.0], current log tail at RBA [0x42.fa845.0]
Thu Jan 27 13:33:52 2011
Incremental checkpoint up to RBA [0x42.fc7d9.0], current log tail at RBA [0x42.fc989.0]
Thu Jan 27 13:53:55 2011
Incremental checkpoint up to RBA [0x42.fed4e.0], current log tail at RBA [0x42.ff12e.0]

How to get the page navigation buttons back at the bottom of the page?

After upgrading to Acrobat X I discovered that there is only one option for the page navigation buttons - at the upper left. I'm mystified as to why they put them there. Most users are right-handed. With the buttons at upper left it's awkward to reach up there, across the page, with the mouse cursor for every page turn (yeah, I know you can use the PgUp/PgDnkeyboard keys, but that requires taking your hand off the mouse every page turn).
What I really want is to be able to put a copy of these buttons back down at the bottom center of the page, which was an option in previous versions. Is there some way to get those back at the bottom?

Hi terpenoid,
Have you tried Read Mode yet ( under the View menu)? It displays a nivagation bar at the bottom of the PDF with next/previous page, zoom in/out, etc.
Hope this helps,
Dimitri
WindJack Solutions
www.windjack.com
www.pdfscripting.com

Page navigation or Auto_incremental php url

I need a page navigation with links to first previous next and last i know that there is an option to add page navigation through dreamweaver from the inset data tab
But the problem is that when ever I add the navigation bar to the page and view it in the browser it gives an error with the number of the line which caused the error and when I view that line I find that the codes which were there are deleted.
the line actually contains some recordset codes which I can't remove as I have worked hard to make them do a specific thing.
So I decided to creat a navigation bar myself the and i made a url parameter to do that here it is
.index.php?categories_id=1&pageNum_Recordset1=1
this link causes the page to show the next set of posts but the problem is it just shows all the posts on the second page as the value of pageNum_Recordset1 on the first page is zero(0)
Now the portion in the red is the problem I want it to be auto_incremental such that the value of pageNum_Recordset1 should change from 1 to 2 to 3 and so on plz help I thins its qute easy but I m not getting it and I have tried my best to explain the problem but if u r not able to then let me know I will explain again.

Several components are action components. You can associate these components with action methods. When a user clicks on the action component the page is submitted to the server and the associated action method (if any) is called and the result of that action method (the return value) determines where to go next.
The hyperlink offers the option of a url or an action handler . If you specify an action handler then the hyperlink works like any action component, as described above.
However, if you specify a url instead, then the page is not submitted. The server simply serves up the page specified by the url.
Because the page is not submitted, no action methods or any other methods get invoked.
Have I explained that clearly?
If not, here is more information: http://developers.sun.com/prodtech/javatools/jscreator/learning/tutorials/2/about_components.html#action
Chris

How to use Partial Page Navigation

according to Web User Interface Developer's Guide for Oracle Application Development Framework section 7.4.1 How to Use Partial Page Navigation,
I set 'oracle.adf.view.rich.pprNavigation.OPTIONS' to 'on' in the web.xml.
and in the jspx, I use af:commandNavigationItem to navigation and set the tag 'partialSubmit' attribute to true.
But it does not work. does anybody know how to use this feature?

Hi,
the question is "what does not work". Partial Page Navigation is there to improve performance on page navigation. So if you navigate from page1 using a navigation case to end up at page 2 then the outcome of the command action's action property should match the navigation case name.
Frank

How do i enable the diagnostic pages for OER 11.1.1.3.0?

I'm currently trying to enable the diagnostic pages for OER 11.1.1.3.0. In the documentation the following is stated:
In Oracle Enterprise Repository 11g release, Oracle Enterprise Repository Diagnostics page is disabled, by default. Navigate to http://host_name:port/application_name/diag/index.jsp (replace host_name with the appropriate location).*
When you open the Diagnostics page in the default mode, the following message is displayed:*
Diag pages are currently disabled. Please contact your Oracle Enterprise Repository Administrator.*
To enable the Diagnostics page, the vm-argument diagPagesEnabled parameter must be set to true when the system is started.*
It is recommended to only enable when necessary and disable once the system is running without any issues.*
But with which argument do i place the diagPagesEnabled_ parameter on the startup arguments of my managed server?

Already found the answer.
Didn't see the setOERdomainEnv.sh within the ${DOMAIN_HOME}
In there is the option OER_DIAG_OPTION. Only needed to remove the *'#'* and restart the server.
+# The following option is disabled by default. Enable this parameter in order to enable the OER Diagnostic pages+
OER_DIAG_OPTION="-DdiagPagesEnabled=true"*

Is it possible to laod navigation options after querry is displayed

Hi
I have a question concerning the display of a query. Us ut possible to display a query and load the navigation options after the query has been displayed (in other words in the background)?
[I am talking about the query property on how to load a query with option A, H and X]
If yes, does it provide a relevant performance benefit in the case of using large hierarchies?
Thx,
Nana

There is, but the preferred way to do something like this is through
the action reference expression which is attached to a UCommand
component. So you could do something like the following:
1. set up a class which extends javax.faces.Action:
import javax.faces.Action;
public class RegisterAction extends Action {
public String invoke() {
return checkUserName();
Set up an accessor method (javabean convention) in your business
object bean that returns the Action instance:
public class Register {
public Action getRegisterAction() {
return registerAction;
2. set up a mapping for the Navigation Handler (assume user.jsp
is the page where the user enters data, and welcome.jsp is
the page that gets displayed on successful outcome). Set this up
in your faces-config.xml:
<navigation-rule>
<from-tree-id>/user.jsp</from-tree-id>
<navigation-case>
<from-outcome>success</from-outcome>
<to-tree-id>/welcome.jsp</to-tree-id>
</navigation-case>
<navigation-case>
<from-outcome>failure</from-outcome>
<to-tree-id>/user.jsp</to-tree-id>
</navigation-case>
</navigation-rule>
Make sure that the checkUserName() method above, returns a string
that matches the "from-outcome" element in your navigation mapping
(in this case - "success" or "failure").
3. attach the actionRef expression to your button component as follows
in your jsp. Something like:
<h:command_button commandName="register" actionRef="Register.registerAction"/>
Hope this helps, Roger.

When i am logging to my company intranet site for every page navigation it is asking for credentials

When i am logging to my company intranet site for every page navigation it is asking for credentials

Also, if the navigation works most of the time but you are prompted for every single image, I suggest restarting Firefox and trying again.
The following also might help in that situation: When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.
(1) Bypass Firefox's Cache
Use Ctrl+Shift+r to reload the page fresh from the server.
Alternately, you also can clear Firefox's cache completely using:
orange Firefox button (or Tools menu) > Options > Advanced
On the Network mini-tab > Cached Web Content : "Clear Now"
If you have a large hard drive, this might take a few minutes.
(2) Remove the site's cookies (save any pending work first). While viewing a page on the site:
* right-click and choose View Page Info > Security > "View Cookies"
* Alt+t (open the classic Tools menu) > Page Info > Security > "View Cookies"
Then try reloading the page. Does that help?

Enable Team calender page navigation option

Similar Messages

Maybe you are looking for