Multitenant Portal after NW2004s Ramp-up

Hi all,
I'm working in a project that was a perfect case to use a Multitenant Portal, but, as decribed in SAP Note 863837, “SAP decided to not release this scenario variant for general availability after SAP NW2004s ramp-up”.
The questions are:
1. Is there an alternative to Multitenant Portal? 
2. +The project scenario is:
The user must access content from different areas (through different URLs, or sending different parameters), but when accessing a specific area, the roles of other areas mustn’t been shown, and when the user authenticate himself, he must still see just the content he was seeing before and, more, his private content.
I thought creating a component that dynamically add the specific public roles of an area to the user and removes the roles from any other area would solve my problem (something based in the code of the following weblog: ). Does anyone have another idea?+
PS: Because of client requirements, the roles will be assigned direct to the users, and we won't use groups.
Thanks in advance,
André Ramos Souza

Hi André,
There is PCDFilter, which can be used to filter role and workset content depending on the context.
I think this can solve your usecase.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3367e690-0201-0010-d285-c69bd884c9f3
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/17968de1-0a01-0010-1f9f-c090fbc7001a
Greetings,
Praveen Gudapati
p.s. Points are always welcome for helpful answers

Similar Messages

  • Unable to log into the portal-After Upgrade from NetWeaver 7.0 to 7.3EHP1

    Dear Experts,
    We have poltal landscape(NW 7.0 Dualstack SPS27) with our customozed themes and par files(Company name,logos and colours)
    Recently we upgraded the one of portal from NW 7.0 to NW 7.3EHP1 . Upgrade has been successfilly completed with small issue.
    After upgrade all urls are working(/nwa, /sld) except /irj/portal.We know that NW 7.3 EHp1 accepts only ear file i.e we converted the our customized log on par file to ear file through par migration tool and the same was deployed successfully through NWDS 7.3 version.After deploying we are able to access the
    /irj/portal url with our customized par(means ear file) without issues,
    We are unable to log into the portal after giving the correct user id and password,getting the portal runtime error as foloows.
    Portal runtime error
    An exception occured while processing your request.Send the exception ID your administrator
    Exception id:
    see log files for details about this exception
    Default.trc log file(/server0/log)
    #EP-PIN-PRT#tc~epbc~prtc~api#C00061FD2733006C00000005000056CB#9034950000000004#sap.com/com.sap.portal.runtime.system.hooks#com.sap.portal.prt.
    runtime#J2EE_ADMIN#4##43E00B85A79911E380F800000089DCC6#3a483a0fa79911e3903000000089dcc6#3a483a0fa79911e3903000000089dcc6#0#Thread[HTTP Worker
    [@900472845],5,Dedicated_Application_Thread]#Plain##
    08:14_09/03/14_0005_9034950
    [EXCEPTION]
    java.lang.RuntimeException: Could not create Resource Repository root folder in PCD
    at com.sap.portal.resource.repository.ResourceRepositorySrv.initRepositoryRootContext(ResourceRepositorySrv.java:140)
    at com.sap.portal.resource.repository.ResourceRepositorySrv.init(ResourceRepositorySrv.java:93)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
    at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
    at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
    at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
    at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
    at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
    at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
    at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
    at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
    at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
    at com.sap.portal.resource.repository.WebResourceRepositorySrv.init(WebResourceRepositorySrv.java:71)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
    at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
    at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
            at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
            at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
            at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
            at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
            at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
            at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
            at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
            at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
            at com.sap.portal.resource.repository.WebResourceImportService$ResourceImporter.<init>(WebResourceImportService.java:248)
            at com.sap.portal.resource.repository.WebResourceImportService.importApplicationResources(WebResourceImportService.java:172)
            at com.sapportals.portal.navigation.NavigationMimeRepositoryService.loadAllPicsToWRR(NavigationMimeRepositoryService.java:186)
            at com.sapportals.portal.navigation.NavigationMimeRepositoryService.init(NavigationMimeRepositoryService.java:160)
            at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
            at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
            at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
            at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
            at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
            at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
            at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
            at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
            at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
            at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
            at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
    at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
            at com.sap.portal.pcm.iview.admin.PcmIviewCommon.getAdditionalAttributes(PcmIviewCommon.java:358)
            at com.sap.portal.pcm.iview.admin.PcmIviewCommon.initLayers(PcmIviewCommon.java:173)
            at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:177)
            at com.sap.portal.pcm.page.admin.AdminBasePage.getCustomImplementation(AdminBasePage.java:76)
            at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:642)
            at com.sapportals.portal.navigation.LightningHelperService.getFrameworkPageAttributesValues(LightningHelperService.java:143)
            at com.sapportals.portal.navigation.LightningHelperService.getFrameworkPageAttributesValues(LightningHelperService.java:171)
            at com.sapportals.portal.navigation.fpm.util.PhaseConfiguration.prepareAttributes(PhaseConfiguration.java:71)
            at com.sapportals.portal.navigation.fpm.util.PhaseConfiguration.storeRelatedAttributesInSharedStorage(PhaseConfiguration.java:35)
            at com.sapportals.portal.navigation.fpm.NavigationFpmListener.doFrameworkPhase(NavigationFpmListener.java:535)
            at com.sapportals.portal.navigation.fpm.NavigationFpmListener.doPhase(NavigationFpmListener.java:122)
            at com.sapportals.portal.pb.fpm.FPMContainer.distributeEvent(FPMContainer.java:63)
            at com.sapportals.portal.pb.fpm.FPM.doDocumentHook(FPM.java:179)
            at com.sapportals.portal.prt.service.document.DocumentHookMulticaster.doDocumentHook(DocumentHookMulticaster.java:100)
            at com.sapportals.portal.prt.service.document.DocumentHookService.doDocumentHook(DocumentHookService.java:119)
            at com.sapportals.portal.prt.service.document.DocumentHookServiceNew.doDocumentHook(DocumentHookServiceNew.java:186)
            at com.sapportals.portal.prt.connection.PortalHook.doDocumentHook(PortalHook.java:665)
            at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:183)
            at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:107)
            at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:141)
            at com.sap.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:206)
            at com.sapportals.portal.navigation.PortalLauncher.doContent(PortalLauncher.java:116)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:213)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:129)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
            at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
            at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
            at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
            at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
            at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: javax.naming.InvalidNameException: Character not allowed: ':' in 'pcd:resource_repository'
    at com.sapportals.portal.pcd.pl.PcdName.checkComponent(PcdName.java:64)
            at com.sapportals.portal.pcd.pl.PcdName.checkNameComponent(PcdName.java:39)
            at com.sapportals.portal.pcd.pl.PcdName.padd(PcdName.java:636)
            at com.sapportals.portal.pcd.pl.PcdName.add(PcdName.java:626)
            at com.sapportals.portal.pcd.gl.util.StringUtils.tokenizeIntoPcdName(StringUtils.java:112)
            at com.sapportals.portal.pcd.pl.PcdName.appendUrlInternal(PcdName.java:408)
            at com.sapportals.portal.pcd.pl.PcdName.<init>(PcdName.java:245)
            at com.sap.portal.resource.repository.ResourceRepositorySrv.initRepositoryRootContext(ResourceRepositorySrv.java:121)
            ... 132 more
    1)We are suspecting this issue is related to the theme issue.How to update the theme in the upgraded portal(have a backup of themes)
    2)Want to know if we update a theme where it stored at the operating system level(in NW 7.3 EHP1 as well as NW 7.0)
    3)Is there any post steps after portal upgrade.
    Request you suggest.
    Regards
    Maruthi

    Hi
    Refer the SAP Notes
    1942399 - Fix usage of unregistered class loader while processing HTTP request in an application being updated or stopped at the same time
    1744820 - Migration 7.3 fails while executing migration of pcd_upgrade
    1703578 - WPC migration stops during connection creation
    1918086 - ERROR: Unable to get iView
    Regards
    Ram

  • Follow-up webdynpro for abap using portal theme nw2004s, sp12

    Hello,
    I wanted to get a follow up to this thread,
    Re: webdynpro for abap using portal theme nw2004s, sp12
    We are having a problem with the way reports developed in Web Dynpro for ABAP displayed in the portal (the pop-ups and dropdowns look out of wack).  The issue appears when we wrap the reports into portal themes (either standard or custom).  As per the thread (the link for which I posted above), the suggestion was to apply WDFORCEEXTERNALSTYLESHEET parameter to the WDP, however our system doesn't have this parameter in the system, but it seems like I can create my own parameter. Can some on give me all of the properties assigned to WDFORCEEXTERNALSTYLESHEET in table WDY_APP_PROP_DEF.
    Thank you

    Hi Brad, I was trying to apply the note 1033496 but our ABAP servers does not have the WDFORCEEXTERNALSTYLESHEET parameter available in WDY_APP_PROP_DEF table.  All other notes are not applicable to our issue.
    The portal is NW2004s SP12, the ABAP server is NW2004 SP11
    Regards.
    Message was edited by:
            Aleks Ozerov

  • Can't Start Portal After Install

    After downloading and installing the of evaluation Portal 4.0 SP1, I get the following message upon startup when I enter the system password that I entered during installation:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: try to access method weblogic/management/internal/
    Helper.preloadMBeanInfos()V from class weblogic/management/Admin
    at weblogic.management.Admin.initialize(Admin.java:210)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    I even tried "weblogic" for the system password and I get the same message.
    What password should I use to start the server?

    I've followed the directions and am experiencing the exact same problem. Brand
    new installation of Weblogic server 6.1 SP2 with examples. That install is working.
    Then added Portal 4.0 SP1, updated the license file and I have the same issue
    with the Illegal access exception resulting in the "Fatal initialization exception"....
    Hmm!
    [email protected] (Bowrat) wrote:
    Below listed are the common errors you run into during installation
    process:
    - You need to have the correct version numbers of both the weblogic
    server and the portal server. For instance the portal server 4.0 (eval
    copy) will only run on WebLogic 6.1 SP1. So check the edocs for
    supported platforms
    - Make sure you have the installed the full version of the weblogic
    server (including examples)
    - Finally, you need to run the UpdateLicense.cmd file to update the
    license.bea under ur Bea Root
    Give it a shot after u have checked all of the above three - goodluck
    - Bowrat
    www.Bowstreet.com
    Steve Anderson <[email protected]> wrote in message news:<[email protected]>...
    From: Steve Anderson <[email protected]>
    Newsgroups: weblogic.support.install
    Subject: Can't Start Portal After Install
    References:
    NNTP-Posting-Host: 209.11.114.150
    X-Original-NNTP-Posting-Host: 209.11.114.150
    Message-ID: <[email protected]>
    Date: 13 Feb 2002 20:25:53 -0800
    X-Trace: 13 Feb 2002 20:25:53 -0800, 209.11.114.150
    Organization: BEA SYSTEMS Inc
    Lines: 18
    XPident: firewall-user
    Path: newsgroups.bea.com!209.11.114.150
    Xref: newsgroups.bea.com weblogic.support.install:9600
    After downloading and installing the of evaluation Portal 4.0 SP1,I get the following message upon startup when I enter the system password
    that I entered during installation:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.IllegalAccessError: try to access method weblogic/management/internal/
    Helper.preloadMBeanInfos()V from class weblogic/management/Admin
    at weblogic.management.Admin.initialize(Admin.java:210)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    I even tried "weblogic" for the system password and I get the samemessage.
    What password should I use to start the server?

  • What is multitenant portal?

    Hi Experts
    What is multitenant portal?
    Appreciate your response

    Hi..
    Refer your thread for good answers....
    [/thread/1043597 [original link is broken];
    Rewards via points appreciated....
    Thanks...

  • Portal Themes "broken" after NW2004S SPS06 package

    Hello - we recently applied SPS06 for NetWeaver 2004S Portal.  After doing this, our custom THEMES no longer function.
    The LOGO and BACKGROUND in the masthead has reverted back to the SAP standard.
    When we browse to the THEME utilities (Theme Editor, Theme Archive, Theme Administration, etc) we can see our themes.  But, if you try to edit one, nothing happens.
    At the filesystem level, the folder for our custom themes are missing.
    I've attempted to EXPORT / IMPORT them again - to no avail.
    I have a message open with SAP on this.  In the meantime, any advice?
    Thank you.
    Steve

    Thank you for your reply Ulmar.  Unfortunately, as I mentioned above, I attempted an EXPORT/IMPORT and that did not work, I am afraid.
    I have foudn that I can go into a different portal, and SAVE AS the theme to a new name (e.g. CHROME2).  And, then EXPORT / IMPORT this into our Portal. 
    However, that is kind of clunky. 
    Thanks in advance for your advice.

  • Problem with portal after upgrading to v3.0.9.8.3

    hi! i got the following message after applying the patch. it occured to my login page. urgent!please advise. thx
    An unexpected error occurred: ORA-06508: PL/SQL: could not find program unit being called (WWC-44082)

    hi! now they are reinstalling the portal again, but encounter some TNS error complaining about Database not listening. some say it's because need to grant some rights to the portal 30 user. any ideas?
    how can i connect to the portal via pl/sql to check?
    i'm afraid we'll encounter the same error after applying the patch. any advise?
    one of the requirement was that the DB must not have any DML statements running.
    does it mean cannot have any procedure that does insert values into table, even if they are executed only if users press the submit button on a dynamic page?
    thx.

  • 500 Internal server error when loging in to Enterprise portal after refresh

    Hi,
    We had a data base refresh of test system with production data. After the refresh, when users are trying to log in to portal test server, they are getting error as follows:
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
        at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
        at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:862)
    I have instaled the certificate after refresh, but still getting this error. I work on SAP ECC6. Thanks in advance for your help.

    Hi Bijoy,
    Do you have the specific error message that the system shows when SSO is not working?
    e.g. The system has received an expired SSO ticket
           Issuer of SSO ticket is not authorized
    Did you do a connection test for your system connector?
    You might want to check the following:
    1. Time difference between portal server and ECC server
    2. Parameters (e.g. login/accept_sso2_ticket = 1) in ECC have the correct value
    3. User account that you are using for testing exists and is valid in ECC.
    4. Portal certificate is still valid and has been added into certificate list and ACL of your ECC client (with the right SID and client number).
    5. System connector settings in portal are correct.
    Cheers.
    Best Regards,
    Zhi Liang

  • Issue in portal after abap stack upgrade

    Hi,
    Except travel and expenditure, everything is working fine after abap stack upgrade.  we have restarted abap and portal 3-4 times, we use abap ume. we are  getting error:
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 18:57_27/02/12_0004_16184750
    defaulttrace:
    \#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bc/webdynpro/&lt;WebDynproNamespace&gt;/&lt;WebDynproApplication&gt;/;sap-ext-sid=&lt;ESID[url_ENCODE]&gt;?sap-ep-iviewhandle=007&lt;ESID[HASH]&gt;&amp;sap-wd-configId=&lt;WebDynproConfiguration&gt;&amp;sap-ep-iviewid=&lt;IView.ShortID&gt;&amp;sap-ep-pcdunit=&lt;IView.PCDUnit.ShortID&gt;&amp;sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;sap-rtl=&lt;LAF.RightToLeft[SAP_BOOL]&gt;&amp;sap-ep-version=&lt;Portal.Version[url_ENCODE]&gt;&amp;sap-wd-tstamp=&lt;$TimeStamp&gt;&amp;&lt;FPNInfo[IF_false PROCESS_RECURSIVE]&gt;&amp;sap-explanation=&lt;User.Explanation[SAP_BOOL]&gt;&amp;&lt;StylesheetIntegration[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;&\#39;; the problem occured at position 310. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;\#39;SAP_LocalSystem&amp;\#39;,
    Attribute: &amp;\#39;client&amp;\#39;.
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         ... 29 more
    #1.5 #00144FF922BF006B00000028000021AF0004B9F256577D3A#1330350388639#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#J2EE_ADM_EDJ#73##ERPDEV_EDJ_16184750#J2EE_ADM_EDJ#d2df5090614511e1cbb100144ff922bf#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###07:16_27/02/12_0004_16184750
    [EXCEPTION]
    #1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bc/webdynpro/&lt;WebDynproNamespace&gt;/&lt;WebDynproApplication&gt;/;sap-ext-sid=&lt;ESID[url_ENCODE]&gt;?sap-ep-iviewhandle=007&lt;ESID[HASH]&gt;&amp;sap-wd-configId=&lt;WebDynproConfiguration&gt;&amp;sap-ep-iviewid=&lt;IView.ShortID&gt;&amp;sap-ep-pcdunit=&lt;IView.PCDUnit.ShortID&gt;&amp;sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;sap-rtl=&lt;LAF.RightToLeft[SAP_BOOL]&gt;&amp;sap-ep-version=&lt;Portal.Version[url_ENCODE]&gt;&amp;sap-wd-tstamp=&lt;$TimeStamp&gt;&amp;&lt;FPNInfo[IF_false PROCESS_RECURSIVE]&gt;&amp;sap-explanation=&lt;User.Explanation[SAP_BOOL]&gt;&amp;&lt;StylesheetIntegration[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;&\#39;; the problem occured at position 310. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;\#39;SAP_LocalSystem&amp;\#39;,
    Attribute: &amp;\#39;client&amp;\#39;.
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         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)
    #1.5 #00144FF922BF006A0000001E000021AF0004B9F25959F274#1330350439133#com.sap.mw.jco#sap.com/tcwddispwda#com.sap.mw.jco#ESSEMP2#288##ERPDEV_EDJ_16184750#ESSEMP2#907dd803614911e1968500144ff922bf#SAPEngine_Application_Thread[impl:3]_6##0#0#Info##Plain###[WD JCO API] WebDynproExtension.addClientPool(SAP_R3_SelfServiceGenerics_ESSEMP2_EN_useSSO_(J2EE16184700)ID1578814350DB10044082816827940554End_9513223) with lang 'EN' and languages vector {EN,EN}#
    #1.5 #00144FF922BF0062000016D7000021AF0004B9F26C7D264E#1330350760207#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Plain###Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF0062000016D9000021AF0004B9F26C7D286A#1330350760208#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
    #1.5 #00144FF922BF0062000016DB000021AF0004B9F26C7D2DAC#1330350760209#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
    [EXCEPTION]
    #1#Request failed due to failure of child requests
         at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
         at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
         at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
         at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
         at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
    #1.5 #00144FF922BF006200001777000021AF0004B9F26FD235FC#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF006200001779000021AF0004B9F26FD23863#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
    Please check CBS service parameters against manual.#
    #1.5 #00144FF922BF006600001720000021AF0004B9F26FFE4EC5#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF006600001722000021AF0004B9F26FFE50DC#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
    Please check CBS service parameters against manual.#
    #1.5 #00144FF922BF005F0000179B000021AF0004B9F2714FA0E9#1330350841110#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Plain###Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF005F0000179D000021AF0004B9F2714FA2FC#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
    #1.5 #00144FF922BF005F0000179F000021AF0004B9F2714FA854#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
    [EXCEPTION]
    #1#Request failed due to failure of child requests
         at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
         at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
         at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
         at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
         at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
    cbs.5:
    #1.5 #00144FF922BF006E00009D0900000EEE0004B9E196C2E0E9#1330278454976#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D1100000EEE0004B9E196C49580#1330278455088#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D1900000EEE0004B9E196C664FD#1330278455207#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D2100000EEE0004B9E196C81B65#1330278455319#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF00310000000000000DA90004B9F0155B9416#1330340708455#/Applications/CBS/Administration##com.sap.tc.cbs.service.CBSFrame#######SAPEngine_System_Thread[impl:5]_82##0#0#Info#1#com.sap.tc.cbs.service.CBSFrame#Java###Starting CBS service on node ...#1#16184750#
    Pls suggest

    Hi James Bond
    From the exception above, it can be seen that the AppIntegrator iView is trying to run on the "SAP_LocalSystem" where it should be running on a "real" backend system.
    Please check what is the System alias in this iView and make sure it points on a backend system which has the same alias in the Portal System landscape.
    Hope that helps,
    Robin Hood.

  • Issue in iSupplier Portal after upgrade from 12.1.1 to 12.1.3

    Hi
    After upgrade to 12.1.3, I am getting 'java.lang.NullPointerException' error when I navigate to Oracle iSupplier Portal -> 'Purchase Order' tab. I have pasted the error text below. I have also noted down the errors below, which were reported during the upgrade (since I don't know if they are connected to this issue, and could not fixed as yet).
    Environment_
    1. Oracle EBS = 12.1.3 (upgraded from 12.1.1)
    2. OS = OEL 5.7
    Any help will be really appreciated. Thanks.
    Exception Details.
    oracle.apps.fnd.framework.OAException: java.lang.NullPointerException at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:912) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:616) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:252) at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.processRequest(OAPageLayoutHelper.java:1182) at oracle.apps.fnd.framework.webui.beans.layout.OAPageLayoutBean.processRequest(OAPageLayoutBean.java:1569) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:968) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:935) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:659) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:252) at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processRequest(OAFormBean.java:385) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:968) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:935) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:659) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:252) at oracle.apps.fnd.framework.webui.beans.OABodyBean.processRequest(OABodyBean.java:353) at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:2607) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1940) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:543) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:431) at OA.jspService(_OA.java:212) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370) at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259) at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51) at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193) at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:284) at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198) at com.evermind.server.http.EvermindPageContext.forward(EvermindPageContext.java:395) at OA.jspService(_OA.java:221) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64) at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15) at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370) at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199) at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303) at java.lang.Thread.run(Thread.java:619) ## Detail 0 ## java.lang.NullPointerException at oracle.apps.pos.orders.webui.PosVpoMainCO.processRequest(PosVpoMainCO.java:151) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:600) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:252) at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.processRequest(OAPageLayoutHelper.java:1182) at oracle.apps.fnd.framework.webui.beans.layout.OAPageLayoutBean.processRequest(OAPageLayoutBean.java:1569) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:968) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:935) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:659) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:252) at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processRequest(OAFormBean.java:385) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:968) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:935) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:659) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:252) at oracle.apps.fnd.framework.webui.beans.OABodyBean.processRequest(OABodyBean.java:353) at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:2607) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1940) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:543) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:431) at OA.jspService(_OA.java:212) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370) at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259) at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51) at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193) at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:284) at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198) at com.evermind.server.http.EvermindPageContext.forward(EvermindPageContext.java:395) at OA.jspService(_OA.java:221) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64) at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15) at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370) at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199) at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303) at java.lang.Thread.run(Thread.java:619) java.lang.NullPointerException at oracle.apps.pos.orders.webui.PosVpoMainCO.processRequest(PosVpoMainCO.java:151) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:600) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:252) at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.processRequest(OAPageLayoutHelper.java:1182) at oracle.apps.fnd.framework.webui.beans.layout.OAPageLayoutBean.processRequest(OAPageLayoutBean.java:1569) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:968) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:935) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:659) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:252) at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processRequest(OAFormBean.java:385) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:968) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:935) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:659) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:252) at oracle.apps.fnd.framework.webui.beans.OABodyBean.processRequest(OABodyBean.java:353) at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:2607) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1940) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:543) at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:431) at OA.jspService(_OA.java:212) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370) at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259) at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51) at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193) at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:284) at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198) at com.evermind.server.http.EvermindPageContext.forward(EvermindPageContext.java:395) at OA.jspService(_OA.java:221) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64) at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15) at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370) at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199) at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303) at java.lang.Thread.run(Thread.java:619)
    Background of Upgrade*
    Following errors were reported during upgrades but we continued upgrade since they could not be fixed. There are several Invalid objects in the DB that starts with OKC but they still remain even after I tried to recompile them through 'adadmin' or through SQL prompt or 'frmcmp' command (as stated below).
    frmcmp module=%AU_TOP%/resource/OKEKAULN.pll userid=APPS/APPS output_file=%AU_TOP%/resource/OKEKAULN.plx module_type=library batch=no compile_all=special
    I beleive OKC schema is related to 'Oracle Contracts' module.
    The following Oracle Forms objects did not generate successfully:
    au resource OKEKAULN.pll
    au resource OKEDTSFM.pll
    au resource OKEKAUWB.pll
    au resource OKLCSAST.pll
    au resource OKLCSEQX.pll
    au resource OKLCSASD.pll
    au resource OKSPMSCH.pll
    au resource OKSAUCVT.pll
    au resource OKSAUDET.pll
    au resource OKCEXPOR.pll
    au resource OKCKSRCH.pll
    au resource OKSAUBLG.pll
    An error occurred while generating Oracle Forms library files.

    Thanks for replying. I have already applied the mega patch 9239090 to upgrade to 12.1.3. The metalink notes you have given refers to patches released prior to patch 9239090. How to check whether the new patch will not overwrite the one I have already applied and will not conflict with it? Will it be automatically taken care by 'adpatch' utility?adpatch should take care of that and it should not overwrite any file if the file version you have is higher than the one delivered by the patch.
    Thanks,
    Hussein

  • Sponsor Portal after upgrade ISE 1.2 - 1.3

    Hi,
    After upgrade ISE to version 1.3 I can't access to Sponsor Portal via ://ISE_IP:8443/sponsorportal/ as it was done in version 1.2 (error: [ 404 ] Sponsor Portal Resource Not Found. The resource requested cannot be found). I have to open it through ISE (Guest Access -> Configure -> Sponsor Portals -> Sponsor Portal (Default) -> Portal test URL). But then in address bar i can see the exact same address i tried to reach (://ISE_IP:8443/sponsorportal/) but it works.
    I deleted migrated portal from version 1.2 and now using only default one. Should I additionally activate it somewhere after this upgrade?

    Nice to hear that. I just want to add something to take into account:
    When you create the CSR directly from ISE, the documentation says for version 1.2 that you need minimum CN field. I did it and then I started having issues with Chrome Browser/ChromeBook which was triggering a certificate warning even though I had signed it with the correct CA Server and I had the Trusted Certificate Authority included in the browser list.
    When I was using 1.1.3, I did not have that problem when using ISE internal CSR feature and only using Common Name (CN) for the CSR.
    I tried using Openssl as usual to create the CSR for ISE running 1.2. Signed and imported it into the ISE and the problem was solved. I am using like you FQDN in the WLC URL Redirect on LWA or CWA with the corresponding entry into the DNS. One important thing I found is that openssl uses some additional fields which I included in the CSR and I think after reviewing the ISE 1.2 documentation we need to include those as well in the ISE CSR feature. Looks like also there is a sequence/order for those fields in the ISE when creating the ISE CSR. The list is the following:
    countryName       = optional
    stateOrProvinceName     = optional
    localityName            = optional
    organizationName  = optional
    organizationalUnitName  = optional
    commonName        = supplied
    emailAddress            = optional
    Finally, with Openssl I could create as well SAN Certificates and I included the IP of the PSN , PAN and MNT ISE's so I would not need the DNS Entry. This feature was added on version 1.2 of the ISE which helps a lot. I will give it a few more testing since that I have a lab deployment with 5 ISE's (PAN, MNT and 3 PSN's).

  • Login error in Portal after importing a new certificate into BI

    Hi Experts,
    Our certificate in BI expired last month and we were unable to login to the BEx reports due to this.
    I have created a new certificate using Visual Administrator and imported that certificate into BI using STRUSTSSO2 after deleting the old certificate from the system PSE.
    After which I have added this new certificate to the ACL for Single Sign On.
    Then rebooted the JAVA stack for the changes to take effect.
    Now, when I want to login to view reports on the Portal created by BEx Analyzer, I am getting this RFC_ERROR_LOGON_FAILURE exception.
    When checked in SM50, it shows SsfVerify failed and SSF_API_NOCERTIFICATE errors.
    Please help me out resolving this. Did I miss out on any of the steps?
    Also when I ran the report, RSPOR_SETUP, the step 5 shows SID_certificate.crt is not existing and the step 12 shows that BI certificate not imported, SAP BI User is not mapped to SAP EP User.
    Regards,

    Hi,
    Have a look at this [thread|The URL http://xxx was not called due to an error; as well as the [Wiki Link|http://wiki.sdn.sap.com/wiki/display/BSP/Logon].
    Hope this will be helpful for you.
    Regards,
    Varadharajan M

  • WebDynpro ABAP application issue from Portal after ECC 6 upgrade to SP14

    Hi,
       We have recently upgraded the Kernel, ABAP and Java stack of ECC 6.0 system to SP14. After the upgrade most of the WebDynpro ABAP applications doesn't load and just flickers when run from Portal as a WebDynpro iView, but they run perfectly fine when accessed directly using URL. These were running fine prior to the upgrade. Can someone suggest what can be going wrong.
       Will reward points for helpful answer.
    Regards
    Mukesh

    Hi Mukesh,
    As Gajendra said, restarting the service in SICF sometimes works for us, but not always.  We have also had to deactivate the entire Webdynpro node, and then reactivate it and all of the services below it.
    Obviously something changed in the SP, given that we now have to do this every time we create a new WDA application.
    Cheers,
    John

  • Changes not reflected in portal after successful import

    Hello,
    I am having trouble with some transports in NWDI. I made some changes to the ESS Address Details dynpro and tested them in the development portal. I then imported them into CONS and the import ran successfully. However I cannot see the changes in the portal. I then ran the TCS Deployer and there was a long list of entries in the list of deployments for my buildspace. I then triggered the auto deployment and waited a few hours. This did not help either. I also checked to confirm that SDM was up and running which it was. Is anybody able to give me some advice on this?
    Thanks a lot,
    Ashley Butterfield

    i have faced the same problem, but after 30 hours all the deployements are done, we got some thing around 511 deployement request on the consolidation server,
    Cheers,
    Apparao

  • Unable to access Admin Tools for portal after configuring LDAP realm

    After setting weblogic to use the LDAP realm I am unable to access the Administration Tools. It does not take the username "administrator" and password "password". I've created the SystemAdministrator Group in LDAP as well as the appropriate "administrator" user but it still does not let me access the Administratotion Tools.

    This thread is being discussed in the weblogic.developer.interest.portal
    newsgroup under the same title. You can cross-post to multiple groups in
    the future so that the thread develops in all newsgroups that you posted to.
    "Wendy Kajiyama" <[email protected]> wrote in message
    news:[email protected]..
    After setting weblogic to use the LDAP realm I am unable to access theAdministration Tools. It does not take the username "administrator" and
    password "password". I've created the SystemAdministrator Group in LDAP as
    well as the appropriate "administrator" user but it still does not let me
    access the Administratotion Tools.

Maybe you are looking for