Roadmap of portals

Hi Experts,
I need a document on Road MAP of  portals.
I would highly appreciate if i get one.
Thanks in Advance,
Dhaarani

Hi Dhaarani,
Please check the below documents..
1. Enterprise Portal Roadmap
( Enterprise Portal Roadmap )
2. Enterprise Portal Blueprint
( Enterprise Portal Blueprint )
Hope this info will help you.
Please let us know if you want more information.
Thanks,
Ramakrishna

Similar Messages

  • Remove Roadmap from Portal page

    hi All,
    i want to remove Roadmap from our portal page which carrying hirarchy in ess-benifits & payments-open enrollement-shows roadmap and other. i want this page is without roadmap.Can anybody have any idea about this?
    or can you suggest me how code flows for this in webdynpro? i am trying on this but still without any clue.please help me out.
    thanks.
    Nutan

    Sai,
    For the page in question, ensure that you select the "fixed", check box to resolve the issue.
    Good Luck!
    Sandeep Tudumu

  • Appraisal process roadmap does not appear

    Hi Guys,
    When we open an employee's appraisal document via ESS or MSS, the 'appraisal process roadmap' / 'appraisal document header' is not appearing. The area that corresponds to this header is blank. Rest all is fine. Can you guys please let me know if there is anything that needs to be done from my side. We are on EhP5.
    Thanks,
    Ranjith

    Hi Siddhartha,
    I wanted to know whether there is an Authorization Object fir Displaying the Process Roadmap on portal.
    I have configured it for a form and assigned the standard role to the user. The form is visible, but not the process roadmap.
    When i assign sap_all to the user, the roadmap is displayed.
    Can you help me with this?
    Regards,
    Shweta

  • Portal Implementation Roadmap not available

    Hi all,
    Can anybody let me know why the below link for Portal Implementation Roadmap is not available.
    <a href="https://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_EP/Enterprise%20Portal/index.htm">https://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_EP/Enterprise%20Portal/index.htm</a>
    kindly let me know the documents available for the SAP EP-ASAP.
    eagerly waiting for replies.
    Regards,
    Venkat

    Hi Rizwan,
    The Roadmap which is available @ SMP you have download and save in your local PC. Then you can access the documentation by the start page inside one folder , which will be accessed on browser.
    Again that is getting accessed form ur local system, u cant access over web.
    Priyabrata

  • Portal Sizing and Roadmap

    Hi,
    I need some suggestions in portal sizing since I am new to this field. We have a external-facing portal with an user base of around 2000. Concurrent users would be 100. Portal is integrated with ECC, BW and BOBJ (around 9 reports).
    I have read about Quick Sizer tool. For 100 concurrent users, what should I use: user sizing or throughput sizing? Is it recommended to follow the results from this tool? What if the user base increases in future? Is there any other approach to work on portal sizing?
    Also, what are the things I need to take into considerations for the future road-map (Scalability, maintenance, etc) ?
    Thanks,
    Sham

    Hi Sushil,
    Thanks for sharing the link. But it doesn't help much.
    I tried using quick sizer tool and found the total SAPS as 2000 (DB SAPS: 500, App SAPS: 1500). Where do I find the relevant hardware for 2000 SAPS? I checked in SAP Benchmark results (Two-Tier Internet Configuration). Am I looking at the right place?
    We were thinking of going for 2 core / 8 GB RAM.
    Regards,
    Sham

  • Disable Security question tab in Roadmap step from Logon help window of Portal

    Hi Experts,
    After Upgrade of my portal server to NW 7.3, I see Security Questions as a Road map Step in inactive status.Before the upgrade it was not showing.
    Because of this, Users will be confused seeing an inactive tab showing up.
    Please refer the attached screen shot and advise how to remove this"Security question" from road map.
    Thanks in advance,
    Regards,
    Suresh Babu

    Hi Rishi,
    Thank you for your reply, Our portal version is Netweaver731 SPS07, Here we didn't find the parameter “ ume.logon.logon_help” said by you, but instead of this we have “ume.logon.logon_help.security question”, and its already have value "false". We also found security question option disabled under user admin options.
    Here screen shots are for your reference.
    Note: In our case "security question" showing in the road map but it’s not active and not asking for security question while resetting the password, and this issue is after upgrading from NW7.0 Ehp2  SPS11 to Netweaver731 SPS07.
    Thanks & Regards,
    Suresh Babu

  • Enterprise Portal Roadmap

    Goodday guys,
    How's everyone doing? need your guidance here. i've been doing remote support work on EP for the past year plus. recently, i've switched jobs venturing into EP implementation. Since, it is a very big scope, is there a documentation on the breakdown of specialization in implementing EP (who does what and when). Obviously, as a long term goal, i wish to master to entire cycle of EP implementation. However, i'm trying to set a realistic short term goal on the areas that i could start out with. Please shed some light here, i would really appreaciate it.

    Hi John
    1) Attend EP training from SAP or their educational partner
    2) Install EP from your system config and your requirement ( JAVA or ABAP)- Check the requirement and download from here
    https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/cfc19866-0401-0010-35b2-dc8158247fb6
    3) refer help document (http://help.sap.com/ep/)
    4) Intract with sdn froum (www.sdn.sap.com)
    Hope it goes smooth
    Cheers
    Jawahar Govindaraj
    PS:Reward points

  • LSO Portal - Course Follow-up Warning Message in Portal

    Hi Gurus
    When i try to do the course follow-up in portal , i get a warning message after i complete the attendance & course assessment of the participants and when roadmap status is at completed , i get a warning message on top of the roadmap that "Your Course Follow-Up could not be saved". This happens in the LSO portal from administrators role.
    We have setup the right control options at course type level.
    Please help with your inputs.
    Regards
    Reddi.

    Hi Amit
    I have checked the master data and found that everything is fine.
    When i try to follow up from R/3 , i get a error message in the last step of follow up activity as "Error While data was intserted in the database".
    Strangely this happens for the course which got over on 12-Aug-10 , but the same course which was on 13-Aug-10 , we were able to follow up the course from the portal without any errors.
    I have checked the relationships , schedules,  correspondence infotype etc , all the data items are maintained identical and all the participants are active in the system.
    Am i missing something here.
    Please help.
    Reddi.

  • OnPlus Top 10 and Roadmap - What do you think?

    Thank you all so much for your great feedback! During the past few months, we’ve met and talked to quite a bit of you on shows, events and here on our Support Community, and listened to your comments and requests.
    Following these discussions and the feedback given on our previous announcement on our Top 10 list of features (here), we internally got together to think of ways on how to address those in our roadmap, so we’re happy to share our plan with you here.
    And as always – comment away! You’re feedback is most valuable.
    Coming soon…
    Here are the features we have planned for the next few months out…
    More supported platforms – as you requested, we’re looking into adding support for more Cisco products. Mainly we are looking at adding support for the following:
    Catalyst 2K and 3K Switches
    Additional ISR G2 platforms
    Co-Branded OnPlus – many of have told us how cool it would be if you could demonstrate your managed services to your existing or prospective customer, with your logo on it, so you can create more of an identity for your company. In the next few months, we’ll be working on a Co-Branded service. You will be able to upload your logo to OnPlus, and we will populate that on the portal and in OnPlus reports.
    Telnet/SSH – this feature was on our previous Top 10 list, and we kept it here, not only because many of you asked for it, but also since we’ll be adding more Cisco devices with a CLI.This feature will enable you to create, through OnPlus a Telnet or SSH tunnel directly into the device you’d like to manage, with the same experience as you could connect to a device’s GUI.
    Customer Access to OnPlus – soon you’ll be able to invite your customers to (only) view their accounts on OnPlus, so they can stay up-to-date with your service.
    Multi-site/network management – many of you have customers with multiple sites, but now, each is represented as a separate site.
    We’ll be working on a more consolidated view, where you’ll be able to manage customers with multiple networks in an intuitive manner. More to come on this in the future…
    Wireless Practice – reports dedicated to the wireless network in your customer networks will be coming as part of an offering linked to new Cisco Access Points coming in the spring.
    Device Credentials Test – when you enter credentials for a device in its window in OnPlus – we’ll test them for you and let you know if they’re correct or not.
    Turn off monitors on selected devices – Since many of you use an RMM, we’ve heard this request quite a bit – can you turn off the monitors on only a selected number of devices or category? This feature will offer you the ability to configure which devices will, or will not be monitored.
    More on PSA integration – we’re looking at a deeper integration both with Autotask and Connectwise, mainly in the ticketing system:
    Upload device configuration into the ticket – for a failed device, we will upload the last device configuration to the ticket, for your convenience.
    Embed a device window link in a ticket – in any ticket that’s opened, a link to the failing device’s window wll be provided so you can open it directly through your PSA.
    ISP Speed test – here you will quickly be able to gauge how your service provider is doing, as more means to troubleshoot from afar.
    Other features coming in the pipeline:
    Here are some more features we will be looking into in the upcoming months, but will be noticeable only later on. Some have remained from our original list, and others have been added following your feedback.
    Network Assessments - placing the ON100 network agent at a potential customer site and running a network assessment can give you enough information about that site, in order to give your prospective customer a proposal. This could be especially useful when using a tablet at that customer’s site, and showing the results on the fly.
    Network Health dashboard – a dedicated health tab will provide you with details regarding your customer network, as well as some more troubleshooting tools you can utilize for further investigation
    OnPlus recommendations - receive recommendations from OnPlus that pertain to the devices on the networks you manage – from notifications on configuration adjustments to promotions and suggestions. This could be a great way to initiate a discussion with your customer on additions, changes, replacements and much more.
    RMM Integration - we are looking closely at integrating functionality with the some Remote Management and Monitoring tools, mainly Level Platforms and Kaseya.  More on that to follow…
    IPv6 – for networks that have already adopted, or are beginning to adopt IPv6 - OnPlus would discover, assess, manage and advise you, same as you know it today.
    Managing different subnets and VLANs – we are looking at ways to discover other subnets and VLANs other than the one that the network agent is on.
    Access privileges to agents - when adding a sub-agent in your account on the OnPlus portal, you'd be able to assign different privileges for each agent, per customer. Meaning, if agent 'John' supports customers A, B and C, and agent 'Jane' support customers X, Y and Z; John would have Read-Write access to only A, B and C but Read-Only access to X, Y and Z and vice versa for Jane. It would be up to the master agent to determine this privilege allocation
    More integration with Cisco Services – through OnPlus you’d be able to see your active Service Requests and RMAs and their history, and also file for an RMA through OnPlus.
    Extension of Service contracts and Warranty – we’re looking at ways for you to extend your service contracts and warranties through OnPlus, without the need to call Cisco or your distributor.
    As always, please don’t hesitate to let us know your comments, thoughts and wishes. We listen to everything!
    Thanks,
    The OnPlus Team

    As a T&M and managed services provider for the small business market (average business customer has 1 to 5 locations and anywhere between 2 and 50 total devices, including computers and printers, per location), we are looking for a drop-in one-box does-it-all type of management and monitoring device.  With this said for perspective, here is the my reaction to the proposed Top 10 list.
    "More supported platforms – "  The full line of Cisco "Built for Small Business" Routers/Firewalls, Switches, Unified Communications, and Wireless Access Points should be supported fully by OnPlus.  These devices should be able to store their configuration files and firmware on the device.  Support for these devices should take precedence over supporting Cisco Enterprise Grade hardware because the OnPlus device is billed as a small business network management product.
    "Co-Branded OnPlus –" This is a good idea, but additional reporting capabilities and full line of Cisco "Built for Small Business" product support should take priority over Co-Branding.
    Telnet/SSH – I'm not sure I understand this is a new feature.  We are currently able to use the generic connection capability to connect to Telnet and SSH.
    Customer Access to OnPlus – We should be able to provide customers with either read-only or full-control access to their network as our contracts stipulate.  We have some customers in both categories.
    Multi-site/network management – This feature will be very helpful to our customers that have some on-staff IT support.
    We’ll be working on a more consolidated view, where you’ll be able to manage customers with multiple networks in an intuitive manner. More to come on this in the future…  -- Waiting to see the details
    Wireless Practice – Good to know. 
    Device Credentials Test – We are looking forward to receiving instant feedback about whether a device has proper credentials (please include snmp in the credentials test) or not.
    Turn off monitors on selected devices – Yeah!!
    More on PSA integration – I'd like to see integration with Spiceworks in addition to the items below.
    Upload device configuration into the ticket – for a failed device, we will upload the last device configuration to the ticket, for your convenience.
    Embed a device window link in a ticket – in any ticket that’s opened, a link to the failing device’s window wll be provided so you can open it directly through your PSA.
    ISP Speed test – here you will quickly be able to gauge how your service provider is doing, as more means to troubleshoot from afar.
    There are some things that are important to our customers that aren't on the top 10 list.  Here are some of those items.
    A.  More network health reporting options and graphs.  It would be nice to be able to run a report that prints out the network Latency and Jitter and Packet Loss metrics that show up on the OnPlus' Wan Monitor Tab.  It would also be nice to include an accurate WAN speed graph in the same report.  It would also be nice to run reports on supported switches that show packet errors, Spanning Tree misconfiguration, etc.
    B.  Configure the OnPlus Device to act as a syslog server
    C.  Im in agreement with some of the thoughts above about being able to capture more WMI data and/or event log/syslog data for Windows/Linux/MAC devices and provide some reporting options for that data.  Our clients have a limited budget, so anything we can provide for them in a single drop-in appliance in the realm of network and device management is appreciated.
    D.  Voicemail backup mentioned above is a great idea
    E.  Support for Spiceworks Ticketing/Reporting Integration
    F.  Additional support for non Cisco Devices -- Most of our cleints have heterogenous networks, so being able to support devices from multiple vendors is important.  Being able to back up the network config of any SNMP capable network device could be very beneficial.
    G.  Selective VLAN listening scope from the OnPlus.  Reduces the amount of switch configuration needed to deploy the OnPlus in environments where we only need to monitor devices on some VLANS.
    H.  Selective global enablling or disabling of remote device connectivity for a customer's site or sites.
    I.  Ability to connect to multiple remote management sessions concurrently from the OnPlus.  This and #H could work together to enable a range of remote connectivity options between maybe 0 and 5 concurrent sessions and could possibly be a factor in service level pricing to the customer.  And, a report could be created that showed the customer the times when someone accessed their devices remotely through the OnPlus.
    As for general direction for the OnPlus --- I hope it doesn't go down the road of only or primarily being a management device for Cisco Enterprise IOS based products.  There appear to already be specialized Cisco Management products available for the Enterprise IOS based line of products.  I want to see OnPlus continue to support Service Providers who have clients on the smaller side of the SMB market.  In the part of the country where we work, the SMB clients, simply don't have resources for Cisco Enterprise IOS products, so it is great be able to offer a low cost drop-in appliance that fulfills general network and device monitoring and management needs.

  • LDAP users Faicng Error While Accessing the ESS Iviews in Portal

    Hi,
    My Portal is SAP EP 7.0 SP20 And ECC 6.0 SP16.
    UME users able to access the ESS MSS Iviews.But only one LDAP User only access ESS/MSS Iviews Other getting the Below error.
    Critical Error
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.     
    Please contact your system administrator     
    Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE     
    Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE:
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
                    at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit(ModelHandler.java:205)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit(InternalModelHandler.java:428)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber(FcXssMenu.java:570)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit(FcXssMenu.java:292)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit(InternalFcXssMenu.java:455)
                    at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit(FcXssMenuInterface.java:165)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface.onInit(InternalFcXssMenuInterface.java:389)
                    at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface$External.onInit(InternalFcXssMenuInterface.java:546)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
                    at com.sap.pcuigp.xssutils.navi.FcNavigation.onInit(FcNavigation.java:314)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigation.onInit(InternalFcNavigation.java:358)
                    at com.sap.pcuigp.xssutils.navi.FcNavigationInterface.onInit(FcNavigationInterface.java:145)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface.onInit(InternalFcNavigationInterface.java:142)
                    at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface$External.onInit(InternalFcNavigationInterface.java:278)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
                    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
                    at com.sap.pcuigp.xssutils.roadmap.VcRoadmap.onInit(VcRoadmap.java:188)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmap.onInit(InternalVcRoadmap.java:162)
                    at com.sap.pcuigp.xssutils.roadmap.VcRoadmapInterface.onInit(VcRoadmapInterface.java:153)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface.onInit(InternalVcRoadmapInterface.java:144)
                    at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface$External.onInit(InternalVcRoadmapInterface.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:782)
                    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
                    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:869)
                    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
                    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
                    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
                    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
                    at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
                    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
                    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:782)
                    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
                    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
                    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:386)
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
                    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
                    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.sap.aii.proxy.framework.core.BaseProxyException: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                    at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
                    at com.sap.pcuigp.xssutils.xssmenu.model.MenuModel.hrxss_Ser_Getmenudata(MenuModel.java:171)
                    at com.sap.pcuigp.xssutils.xssmenu.model.Hrxss_Ser_Getmenudata_Input.doExecute(Hrxss_Ser_Getmenudata_Input.java:137)
                    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
                    ... 76 more
    Thanks & Regrads,
    Subba Rao

    Hi,
    Now every user facing the same error while accessing ESS Iviews from Portal.
    in ST22 Dump is created.
    What happened?                                                                                |
    Error in the ABAP Application Program
    The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "CL_XSS_CAT_BUFFER=============CP " in include
    "CL_XSS_CAT_BUFFER=============CM00C " in
    line 50:
    ""L_CATSDB" and "L_CATSDBCOMM" are not mutually convertible. In Unicode"
    " programs, "L_CATSDB" must have the same structure layout as "L_CATSDB"
    "COMM", independent of the length of a Unicode character."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
    terminated because it has
    |    come across a statement that unfortunately cannot be executed.
    What we need to resolve the above issue.
    Thanks & Regards,
    Subba Rao

  • Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

    Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
    A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
    Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
    * Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
    * Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
    The guide can be downloaded here:
    http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
    To help internet searches locate this document, the table of contents is reproduced below:
    Introduction
    1.1. Prerequisites...................................................................... 8
    1.2. Applicable Versions............................................................ 8
    1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
    1.4. JSF Portlet Support Roadmap ........................................... 9
    1.5. Whitepaper Structure ....................................................... 10
    1.6. Look Before You Leap ..................................................... 10
    1.7. For More Information........................................................ 10
    Part 1: Converting JSF Applications into Portlets
    2. IDE Support for JSF Portlets Chapter ...................................... 12
    2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
    2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
    3. Introduction to JSF Portlets Chapter ........................................ 18
    3.1. Creating Your First JSF Portlet......................................... 18
    3.2. Essentials of JSF Portlet Views........................................ 21
    3.3. WebLogic Portal Artifacts................................................. 22
    4. Configuring JSF within WebLogic Portal Chapter..................... 24
    4.1. JSF Library Modules in WebLogic Server ........................ 24
    4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
    4.3. JSF Configuration Settings............................................... 27
    4.4. Configuring JSF 1.2 ......................................................... 29
    4.5. Building an Unsupported JSF Implementation Library Module 31
    4.6. Faces Configuration is Web Application Scoped.............. 31
    5. Navigation within a JSF Portlet Chapter................................... 33
    5.1. Navigating within a Portlet with the JSF Controller ........... 33
    5.2. Redirects.......................................................................... 34
    6. Namespacing Chapter ............................................................. 35
    6.1. Namespacing Managed Bean Names.............................. 35
    6.2. Client ID Namespacing with the View and Subview Components 35
    6.3. Client ID Namespacing with the WLP NamingContainer .. 36
    7. Logging, Iterative Development, and Debugging Chapter ........ 39
    7.1. Logging............................................................................ 39
    7.2. Iterative Development ...................................................... 39
    7.3. Debugging ....................................................................... 40
    8. Custom JavaScript Chapter ..................................................... 42
    8.1. DOM Manipulation within a JSF ....................................... 42
    8.2. Form Validation within a JSF Portlet ................................ 45
    9. Preparing JSF Portlets for Production Chapter ........................ 46
    9.1. Configuration.................................................................... 46
    9.2. Performance and Scalability............................................. 47
    9.3. Security............................................................................ 49
    9.4. Localization...................................................................... 50
    Part 2: Interacting with the Portal Environment
    10. Native Bridge Architecture Chapter ...................................... 54
    10.1. Container Architecture Overview.................................. 54
    10.2. Container Architecture.................................................. 54
    10.3. Container Interactions .................................................. 55
    11. Interportlet Communication Chapter .................................... 56
    11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
    11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
    11.3. Notifications ................................................................. 60
    11.4. Comparison of the IPC Approaches ............................. 60
    12. Scopes Chapter ................................................................... 62
    12.1. Conceptual Scopes for Standard JSF Applications ...... 62
    12.2. Conceptual Scopes for Portal Applications................... 63
    12.3. Implementation Patterns for Portal Scopes .................. 63
    13. State Sharing Patterns Chapter ........................................... 66
    13.1. State Sharing Concepts ............................................... 66
    13.2. HttpSession Versus HttpServletRequest ...................... 66
    13.3. Base Code for HttpSession Patterns ............................ 67
    13.4. Single Portlet Pattern ................................................... 68
    13.5. Multiple Portlet Patterns ............................................... 69
    14. Rendering Lifecycles Chapter .............................................. 77
    14.1. WLP and JSF Lifecycles .............................................. 77
    14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
    14.3. Accessing WLP Context Objects from JSF Managed Beans 78
    15. Portal Navigation Chapter .................................................... 80
    15.1. Programmatically Constructing JSF Portlet URLs ........ 80
    15.2. Changing the Active Portal Page.................................. 80
    15.3. Redirects within a Portal............................................... 83
    16. Ajax Enablement Chapter .................................................... 85
    16.1. Ajax in JSF Portlets...................................................... 85
    16.2. Partial Page Rendering Pattern.................................... 85
    16.3. Stateless API Request Pattern ..................................... 86
    16.4. Portlet Aware API Request Pattern .............................. 87
    16.5. Controlling the WLP Ajax Framework........................... 91
    17. Additional WLP Features Chapter........................................ 93
    17.2. Portlet Container Features ........................................... 93
    17.3. Portal Container Features ............................................ 98
    18. Example: Implementing a Login Portlet Chapter .................. 99
    18.1. Login Portlet Motivation................................................ 99
    18.2. Login Portlet Design..................................................... 99
    18.3. Login Portlet Implementation...................................... 101
    Part 3: Integrating Third Party Libraries
    19. Integration Overview Chapter............................................. 111
    19.1. Types of Libraries....................................................... 111
    19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
    20. Using the Facelets View Technology Chapter.................... 113
    20.1. Introduction to Facelets .............................................. 113
    20.2. Configuring Facelets Support ..................................... 113
    21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
    21.1. What is Apache MyFaces Tomahawk? ...................... 115
    21.2. Support for Tomahawk in WLP................................... 115
    21.3. Tomahawk Component List........................................ 116
    21.4. Installing and Configuring Tomahawk......................... 119
    21.5. Resolving the Duplicate ID Issue................................ 120
    21.6. Referring to Resources .............................................. 120
    21.7. forceId Attribute.......................................................... 124
    21.8. File Upload................................................................. 125
    22. Using the Apache Beehive Navigation Controller Chapter . 126
    22.1. Apache Beehive Page Flow ....................................... 126
    22.2. JSF and Page Flows .................................................. 126
    22.3. Configuring the JSF Integration with Page Flows ....... 127
    Appendices
    23. Appendix 1: Consolidated List of Best Practices ................ 130
    24. Appendix 2: Known Issues and Workarounds.................... 132
    24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
    24.2. CR342124: IllegalStateException due to duplicate client-id 132
    24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
    24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
    24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
    25. Appendix 3: The JSFPortletHelper Class ........................... 135
    26. Appendix 4: The CleanupPhaseListener Class .................. 147

    Hi Peter!
    First, I wish to thank you for the great work.
    We followed your whitepaper and managed to deploy a JSF portlet on WLS.
    But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
    An error occurred while trying to refresh the provider. (WWC-43190)
    An error occurred during the call to the WSRP Provider:
    java.rmi.RemoteException: serialization error: serialization error:
    unexpected null value for literal data; nested exception is:
    serialization error: serialization error: unexpected null value for literal data
    com.sun.xml.rpc.encoding.SerializationException: serialization error:
    serialization error: unexpected null value for literal data
    com.sun.xml.rpc.encoding.SerializationException: serialization error:
    unexpected null value for literal data
    Java stack trace from root exception:
    unexpected null value for literal data
    at
    oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
    at
    com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
    at
    com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
    at
    oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
    at
    com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
    at
    com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
    at
    com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
    at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
    at
    oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
    at
    oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
    Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
    Thank you and best regards,
    PaKo

  • SAP PI Roadmap for future release

    Hi,
    Can anybody give some idea/link about SAP PI roadmap for next 2-3 years.
    Regards,

    HI,
    As you might be knowing current SAP PI release is of PI 7.1.
    now as per my understanding there will be SAP Enhancement Packages in future instead of new releases.
    SAP had introduced the enhancment package strategy.
    Please refer below links
    Overview SAP Enhancement Packages
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/ehp/overview%252bsap%252benhancement%252bpackages
    enhancement package strategy
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50b84668-3e61-2b10-9db9-9f45dd9bd361
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/enterprise-resource-planning/enhancement%20packages/using%20sap%20enhancement%20packages%20for%20sap%20erp.pdf
    Thanks
    Swarup
    Edited by: Swarup Sawant on Dec 29, 2008 8:10 AM

  • Restarting or Reloading Webdynpro ABAP(FPM) application in Portal

    Hi All,
    I have created a ABAP webdynpro application in FPM framework which is run in the portal. The application has got a roadmap that contains 7 steps. In the last step there is a button 'save and exit'. When the user reaches the last step and presses the 'save and exit' button, one popup will appear with a 'close' button. When the user pressed that 'close' button, the application should restart i.e., the user should be taken to the first step. I tried using the method 'NAVIAGATE_ABSOLUTE' where I hardcoded the PCD path which takes the user to the first step but it is not helpful ( All Relative navigation links and Detailed navigation links were missing in portal ) in my case as it is not actually restarting the application. Could anyone help me out in getting the application restarted in the portal on click of a button.
    Note: We tried with Exit-Plug as well, which is not applicable ( helpful) for portal integration.
    Please suggest.
    Thanks
    Deepak

    Hi Deepak,
    Well we have few webdynpro applications with multiple views, by design, on the last step after save, we disable all other button and display a new button called 'RESTART' with only available choice. On click of this button
    1. We initialize all the data of component.
    2. Clear stored variable parameters & internal table used by assistance class
    3. if everything was fine fire navigation to the FirstDefaultView of the webdynpro application.
    Thus its almost restart of the application.
    So design wise have a method  INIT_COMP  in the component controller of webdynpro component. and then at the last step when call to RESTART is made reinitialize all the data of your webdynpro component.
    method onactionrestart.
    wd_assist->reinit_my_obj_tables( ).
    wd_this->fire_to_v_Start_plg(  ).
    endmethod
    Greetings
    Prashant

  • ABAP WebDynPro tutorials for Roadmaps and drop-down list box

    Hi Experts,
        I need some tutorials on Roadmaps and drop-down list box in ABAP WebDynPro which will show me step by step process how to create application using this. 'help.sdn' pages do show the procedures for implementing those ui elements.
    And also the previous threads refer to some expired documents.
    Thanks in advance.....
    Plz help....
    Edited by: Akashdeep Basu on Aug 9, 2008 9:30 AM

    Hi
    [SAP BLOG on ABAP-WEBDYNPRO|https://www.sdn.sap.com/irj/sdn/nw-development?rid=/webcontent/uuid/512040e1-0901-0010-769c-c238c6ca35d9]
    [Step-By-Step Approach|http://help.sap.com/saphelp_nw04s/helpdata/en/79/002c2a0d43e645a39a89dd662b5f68/content.htm]
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a282c952-0801-0010-1eb5-87953e036712
    Regards
    Pavan

  • SAP Roadmap

    Hi,
    I am new to SAP AS and SAP technology.
    I am interested in NetWeaver and did basic initial JSP / Servlet / EJB projects on latest SAP AS.
    I am quite comfortable in J2EE without any SAP background.
    Please let me know further roadmap in SAP world.
    Thanks in Advance.

    Hi,
    Since you have good background in J2EE. couple of technologies you can expore are
    Enterprise Portal
    Webdynpro.
    MDM
    CAF.
    xMII
    and XI.
    Try to get some basic idea on R3 and then concentrate on these products. This will take you to a solid carrier
    regards
    Vivek Nidhi.

Maybe you are looking for