Portal Session Not Ended Immediately in Backend Causing ENQ Lock

Background:
We have a customized effort logging program running under Portal.  When the user decides not to save the change and just click "logoff" from portal to exit without change.
Normal Situation:
Normally, the user session will be terminated immediately in backend once the user logs off portal.  This will then automatically clean up all session buffer and application ENQUEUE via ABAP webdynpro Controller routine.
Problem Situation:
Occasionally, it is found that the session is not terminated immediately in ECC backend system.  The session still exists in ECC under SM04 and the previous ENQUEUE still exists in the ENQUEUE table under SM12.
When the user logs back into the portal to perform the effort logging again immediately after, the application will have error complaining the employee still locked in the ENQUEUE table by the previous transaction.   
Such leftover session will be automatically cleaned up by ECC backend system after 30 minutes timeout.  Even no action is done, the user can resume to the Effort Logging function after 30 min. after the record is locked.

Hello,
We are facing the same problem. Could you please let us know the solution for this issue?
Thank you,
Nikee

Similar Messages

  • Portal session not being terminated. browser "unload" event

    This line of code is in the portallauncher.default and eventually causes the problem:
    EPCM.subscribeEvent("urn:com.sapportals.portal:browser", "unload", releaseProducerSessions);
    releaseProducerSessions eventually calls a portal component
    WSRPSessionRelease.. which is causing the problem.
    When we upgraded from EP 6.0 to NW 2004, users started recieving the Netweaver Login Screen when they logged out and logged back in, in the same browser. We think this error occurs because NW 2004 implements Web Services Remote Portal functionality.
    We are using SiteMinder as a third party session management tool.
    What we found was that the Siteminder session was being killed but the Portal session was not. Therefore, when users logged back in they would see the generic Netweaver Login Screen, and they could actually just hit "enter" and continue to the portal.
    A successful logoff, users clicked the logoff button, the DSM terminator was being called, thus killing the portal session, then a form was submitted redirecting the users the the siteminder loggoff page, which logs the users off siteminder.
    When the logoff failed, we found that after the DSM Terminator was called
    and before the page was being redirected, a portal component
    (WSRPSessionRelease) was being called, which in turn, RECREATED the portal session. So the user never actually gets logged off from the portal.
    We found that the WSRPSessionRelease component is set to
    a "browser" "unload" event when the portallauncher.default component is first loaded. This is the same component that is being called when the user clicks the "X" to force close the browser.
    Not everytime is the WSRPSessionRelase component being called before the redirect to the siteminder logg off page. Sometimes this component is called after the redirect, and we find that this is a successful loggoff.
    The component is:
    irj/servlet/prt/portal/prtroot/com.sap.portal.wsrp.coreconsumer.WSRPSessionRelease

    Hello Michael,
    The 'log off' issue is a known issue with Portal since EP 6
    Had faced similar issue and SAP suggests to redirect the 'log off' link to another non-SAP site...like your company intranet site.
    This will help the session to break.
    There are 1-2 SAP Notes on this as well.
    Hope this helps.
    Regards,
    Ritu

  • Portal session not being terminated

    When we upgraded from EP 6.0 to NW 2004, users started recieving the
    Netweaver Login Screen when they logged out and logged back in, in the
    same browser. We think this error occurs because NW 2004 implements Web
    Services Remote Portal functionality.
    We are using SiteMinder as a third party session management tool.
    What we found was that the Siteminder session was being killed but the
    Portal session was not. Therefore, when users logged back in they would
    see the generic Netweaver Login Screen, and they could actually just
    hit "enter" and continue to the portal.
    A successful logoff, users clicked the logoff button, the DSM terminator
    was being called, thus killing the portal session, then a form was
    submitted redirecting the users the the siteminder loggoff page, which
    logs the users off siteminder.
    When the logoff failed, we found that after the DSM Terminator was called
    and before the page was being redirected, a portal component
    (WSRPSessionRelease) was being called, which in turn, recreated the
    portal session. So the user never actually gets logged off from the
    portal.
    We found that the WSRPSessionRelease component is set to
    a "browser" "unload" event when the portallauncher.default component is
    first loaded. This is the same component that is being called when the
    user clicks the "X" to force close the browser.
    Not everytime is the WSRPSessionRelase component being called before the
    redirect to the siteminder logg off page. Sometimes this component is
    called after the redirect, and we find that this is a successful loggoff.
    The component is:
    irj/servlet/prt/portal/prtroot/com.sap.portal.wsrp.coreconsumer.WSRPSessio
    nRelease

    Hi Michael, we are facing the same error. Have you found a solution?
    Thanks in advance and best regards

  • CR Server 2008 Sessions not ending

    At a clients installation, they have a CR 2008 server.  The parameter is set to close unused connections after 20 minutes.  Yet we just logged in, and there were 3 connections still active, one from November 29th, and two from yesterday.  Is there a registry or configuration in one of the xml files that needs to be changed to fix this?

    You're using unmanaged RAS.
    Have you specified the unmanaged RAS server listener port (command-line option -ipport), then specify that when setting the ReportAppServer ("xxxx.xxxx.xxx.xxx:port")?
    Sincerely,
    Ted Ueda

  • SM04 Session does not end.

    Hi all,
    I noted that SAP R/3 session does not automatically ended after a user logs off from the ESS Frontend. This will result in a increase in session in SM04 eventhough the users had logout from the portal.
    I have adjusted some timeout parameter in transaction RZ10 in R/3 including rdisp/plugin_auto_logout and restarted the services. To test, i accessed the ESS Portal and access some IAC IVIEW. Thereafter, i logged off the portal and observed the session created in R/3 (SM04) and noted that the session including the RFC connections are not released at all.
    Anyone face this issue before? How can i control so that after the user logoff from the portal, the session in SM04 is end.
    Thanks in advance

    Hi Sean,
    I found some note on the session which i attached below. However in my EP server have dozens of web.xml. Which one should i configure? Would you able to help me on this? Some of my IAC view does not end while some do. Any idea on that?
    Specifying HTTP Session Timeout
    Use
    You can specify a timeout period for HTTP sessions created in your Web application. If the session is inactive for this timeout period, it is invalidated by the Web container.
    If you do not specify such a timeout explicitly, a default one of 30 minutes is assumed.
    You can configure the HTTP session timeout using the web.xml descriptor.
    Procedure
    On the web.xml screen, proceed as follows:
    1. Open the General screen.
    2. To specify the timeout period, enter a value in the Session configuration – Session timeout field.
    The value is specified in minutes. If you enter a negative value in this field, HTTP sessions are never terminated because of a timeout. Instead, only an explicit logout by the user will terminate the corresponding session.

  • Portal will not initialize.

    Hello folks,
    I was working on adding an datasource (MSADS) to EP6SP2.
    I made the changes and restarte dthe serverce couple time I had errors. Now the portal will not initialize. I get the following error.
    What are my options now? How can I bring up the portal?
    Apr 21, 2006 7:47:06 PM # System_Thread_36     Fatal           [Portal.init] Application Broker - initialization failed.
    com.sapportals.portal.prt.runtime.PortalException: [Portal Application Broker] applications start failed
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1431)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1360)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3338)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2596)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:765)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:200)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.runtime.PortalException: [PortalServiceItem.startServices] initialisation failed:com.sap.portal.license.runtime|license
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:883)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1470)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1426)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1360)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3338)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2596)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:765)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:200)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException: Could not instantiate implementation class com.sapportals.portal.prt.service.license.LicenseService of Portal Service com.sap.portal.license.runtime|license because: could not load the service
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:689)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1470)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1426)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startCoreApplications(PortalAppBroker.java:1360)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:345)

    The last 10 lines is what I commented out as I was using multiple datasources. he following line
    ume.persistence.data_source_configuration=dataSourceConfiguration_ads_writeable_db.xml should be a different file.
    The server is set to MSADS mode but I commented out those lines. So the server does not find the file. Is there a way to fix this??
       SAP User Management Engine Configuration
       Logging settings
    ##The external class for the portal logger should be used.
    ##If trace file from native logging api should be used, set this property to "com.sap.security.core.util.imp.UMTrace_EX"
    ##and set properties "ume.trace.trace_level" and "ume.trace.debug_exception_level" to a severity level from 1 to 5.
    ume.trace.external_trace_class=com.sapportals.portal.prt.service.usermanagement.util.UMTrace_620_Portal
       Data source settings
    ##xml file that configures the persistence except roles
    ume.persistence.data_source_configuration=dataSourceConfiguration_ads_writeable_db.xml
    ##xml file that configures the roles persistence which are coming from the pcd
    NOTE: ume.persistence.pcd_roles_data_source_configuration AND ume.persistence.ume_roles_data_source_configuration
          mustn't be used together.  
    ume.persistence.pcd_roles_data_source_configuration=dataSourceConfiguration_PCDRoles.xml
    ##xml file that configures the roles persistence which are coming from the ume
    NOTE: ume.persistence.ume_roles_data_source_configuration AND ume.persistence.pcd_roles_data_source_configuration
          mustn't be used together.  
    #ume.persistence.ume_roles_data_source_configuration=dataSourceConfiguration_UMERoles.xml
    ##specification of the default cache
    ume.cache.default_cache=distributableCache
       LDAP settings
    ##specifies the servertype NOVELL oder SUN
    ume.ldap.access.server_type
    ##the ldap server name
    ##ume.ldap.access.server_name=NortDC.fngp.com,PlymDC.fngp.com
    ##the port of the ldap server
    ##ume.ldap.access.server_port=389,389
    ##the user used for connecting to the ldap server
    ##ume.ldap.access.user=FNGP
    ADSUser
    ##the password of the user
    ##ume.ldap.access.password=
       database settings
       R/3 settings (for use as Master datasource)
    Start of Required keys for R/3 connection
    2hNbedUUwhwiKCN6wpZqXw\=\=
    ##true if ssl is used, false if not
    ume.ldap.access.ssl=FALSE
    ##the path in the ldap server, where the users are found
    ##ume.ldap.access.base_path.user=OU\=FNGP,DC\=fngp,DC\=com
    ##the path in the ldap server, where the useraccounts are found; only nedded if a user object is not an account object
    #ume.ldap.access.base_path.uacc=
    ##the path in the ldap server, where the groups are found
    ##ume.ldap.access.base_path.grup=OU\=Portal Groups,OU\=FNGP,DC\=fngp,DC\=com
    ##the data for the connection pool
    ume.ldap.connection_pool.min_size=1
    ume.ldap.connection_pool.max_size=10
    ume.ldap.connection_pool.max_idle_connections=5
    ume.ldap.connection_pool.max_idle_time=600000
    ume.ldap.connection_pool.max_wait_time=60000
    ume.ldap.connection_pool.monitor_level=0
    ume.ldap.connection_pool.retrial=10
    ume.ldap.connection_pool.retrial_interval=10000
    ume.ldap.connection_pool.release_check_interval=120000
    ##specify if you want to user an internal or external connection pool
    ume.db.connection_pool_type=jdbc/sapep
    ##if you are using an internal connectionpool please use the following properties to configure the connections
    ##specify the database driver
    ume.db.jdbc_driver
    ##specify the database url
    ume.db.jdbc_url
    ##specify the database user
    ume.db.jdbc_user
    ##specify the user password
    ume.db.jdbc_password
    ##if you are using an external cnnectionpool
    ##(connection pool of the j2ee engine) please use the following properties to configure the connectionpool
    ##the context factory of the j2ee connection pool
    ume.db.connection_pool.j2ee.initial_context_factory=com.inqmy.services.jndi.InitialContextFactoryImpl
    ##the provider url of the j2ee connetion pool
    ume.db.connection_pool.j2ee.provider_url=localhost
    ##setting of the internal database connection pool
    ume.db.connection_pool.internal.minsize=1
    ume.db.connection_pool.internal.maxsize=30
    ume.db.connection_pool.internal.max_idle_connections=5
    ume.db.connection_pool.internal.max_connection_idle_time=600000
    ume.db.connection_pool.internal.max_wait_process_time=600000
    ume.db.connection_pool.internal.monitor_interval=500
    ume.db.connection_pool.internal.connect_retrials=0
    ume.db.connection_pool.internal.max_connection_usage_timel=600000
    ume.db.connection_pool.internal.max_connection_usage_time_check_interval=60000
    ume.db.connection_pool.internal.monitor_path=./
    ume.r3.connection.master.client
    ume.r3.connection.master.user
    ume.r3.connection.master.passwd=g8EnrAsDbQw\=
    ume.r3.connection.master.sysnr
    ume.r3.connection.master.useXML=false
    R/3 application name (only CRM and EBP are supported)
    ume.r3.connection.master.application
    End of required keys
    Start of required-optional keys
    One of following 3 options is required:
    Option 1: application host name
    ume.r3.connection.master.ashost
    Option 2:  (name used to map to the sapmsg.ini file.)
    #ume.r3.connection.master.r3name=
    Option 3: message server
    #ume.r3.connection.master.msghost=<message server>
    Required when options 2 and 3 are used  (e.g. PUBLIC)
    #ume.r3.connection.master.group=<group of message server>
    End of required-optional keys
    Start of optional keys
    ume.r3.connection.master.lang=EN
    number of connections to create in the connection pool
    ume.r3.connection.master.poolmaxsize=10
    Time in milliseconds to wait for available connection before error
    ume.r3.connection.master.poolmaxwait=10000
       Security Policy
    ume.logon.security_policy.useridminlength=6
    ume.logon.security_policy.useridmaxlength=20
    ume.logon.security_policy.userid_in_password_allowed=TRUE
    ume.logon.security_policy.oldpass_in_newpass_allowed=TRUE
    ume.logon.security_policy.password_min_length=6
    ume.logon.security_policy.password_max_length=10
    ume.logon.security_policy.password_mix_case_required=0
    ume.logon.security_policy.password_alpha_numeric_required=0
    ume.logon.security_policy.password_special_char_required=0
    ume.logon.security_policy.password_change_allowed=FALSE
    ume.logon.security_policy.lock_after_invalid_attempts=6
    ume.logon.security_policy.auto_unlock_time=60
    ume.logon.security_policy.password_expire_days=99999
    ume.logon.security_policy.cert_logon_required=FALSE
    ume.logon.security_policy.cookie_life_time=172800
       security parameters
    path of your IAIK keystore
    login.ticket_keystore=ticketKeyStore
    Key pair alias with the Keystore ('sapportal' recommended for new install)
    login.ticket_keyalias=TestKey
    login.ticket_lifetime=8
    url of the SAP trustcenter that signed the portal key (req. for RA functionality)
    trustcenter=https://tcs.mysap.com/invoke/tc/usercert
    logical adapter name of authenticating backend
    credentials are checked against this specified repository (see  repository_configuration_file)
    login.authentication_server=Corporate Authentication Server
    #authschemes conf xml file
    login.authschemes.definition.file=authschemes.xml
    ume.superadmin.activated=FALSE
    (Comma separated) list of role xml files
    #ume.roles.xml_files = *role.xml
    Self Registration  ################################
    to enable self registration process. (default: true)
    ume.logon.selfreg=true
    ume.admin.selfreg_company=false
    Notification Mails ################################
    mail host, separated by semicolon if several hosts
    ume.notification.mail_host=<mailhost1>;<mailhost2>;<mailhost3>
    ume.notification.mail_host=nort-smtpsrv-1.fngp.com
    Email sending mode
    asynchronous is preferred especially when many emails are sent out
    ume.notification.email_asynch=TRUE
    Sending an email on the below events can be switched on(default)/off
    ume.notification.create_request=true
    ume.notification.create_approval=true
    ume.notification.create_performed=TRUE
    ume.notification.pswd_reset_request=TRUE
    ume.notification.pswd_reset_performed=TRUE
    ume.notification.unlock_request=true
    ume.notification.lock_performed=TRUE
    ume.notification.unlock_performed=TRUE
    ume.notification.delete_performed=TRUE
    ume.notification.create_by_batch_performed=TRUE
    ume.notification.update_by_batch_performed=TRUE
    ume.notification.create_denied=true
       anonymous user
    Defines which mode of anonymous logon is to be used. Default value is 1.
    1 = Anonymous logon with named anonymous users is used.
    0 = Simple anonymous logon is used.
    ume.login.anonymous_user.mode=1
    Comma-separated list of guest users that are supported. These users must exist with this unique ids in the user repository. This parameter does only take effect if ume.login.anonymous_user.mode=1
    ume.login.guest_user.uniqueids=anonymous
       user admin
    ume.admin.search_maxhits_warninglevel=200
    ume.login.guest_user.defaultid=anonymous
    login.ticket_issuer=FNN
    ume.license.sysid=FNN
    #Additional properties
    #Sat Nov 13 17:49:49 EST 2004
    ume.r3.mastersystem=
    ume.r3.connection.master.r3name=
    ume.r3.connection.master.msghost=
    ume.r3.connection.master.group=
       LogOff
    ume.logoff.redirect.url=http://nortweb1.fngp.com/cleartrust/ct_logout.asp
    ume.logoff.redirect.silent=false
    #Additional properties
    #Fri Apr 21 18:34:00 EDT 2006
    #ume.ldap.access.server_port=389
    #ume.ldap.access.user=FNGPEXT
    adm_msb
    #ume.ldap.access.password=xDhj3ijP/xaX74LzqzAPJw\=\=
    #ume.ldap.access.server_name=Nortextdc.fngpext.com
    #Additional properties
    #Fri Apr 21 18:35:36 EDT 2006
    #ume.ldap.access.base_path.user=OU\=FNGPEXT,DC\=fngpext,DC\=com
    #ume.ldap.access.base_path.grup=OU\=FNGPEXT,DC\=fngpext,DC\=com

  • Can portal session cookies be used between two data centers

    OAS generates the following header information and session information for my application. However when I need to failover the originating OAS datacenter into my hot stand-by for maintenance or upgrades, the OAS in the other datacenter responds with a 503 web error. We are using Akamai's GTM to manage the liveness of the datacenter, so we would need the hot stand-by OAS portal in that datacenter to return a 302 error code. Is there some method that we can add to our portal application which would always return a 302 error code.
    See header information collected through wfetch. The 503 error is caused by the hot stand-by data center not accepting or recognizing the cookie. Both OAS datacenters are IDENTICAL in Oracle levels, application levels, web servers, portals and OS patches.
    resolve hostname "170.107.183.32"WWWConnect::Connect("170.107.183.32","80")\nsource port: 2182\r\n
    GET /portal/pls/portal/PORTAL.wwsec_app_priv.login?p_requested_url=%2Fportal%2Fpls%2Fportal%2FPORTAL.home&p_cancel_url=%2Fportal%2Fpls%2Fportal%2FPORTAL.home HTTP/1.1\r\n
    Accept: */*\r\n
    Accept-Language: en-us\r\n
    Accept-Encoding: gzip, deflate\r\n
    User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)\r\n
    Host: www.thomson-pharma.com\r\n
    Connection: Keep-Alive\r\n
    Cookie: ORA_WX_SESSION="10.225.8.30:80-1#2"; portal=9.0.3+en-us+us+AMERICA+3D66674E7EED0801E04400144F41424E+BBAA98EEB32D58C086231A8D6CBE2E5D402D89B0E79D83A18C668BB0CA7417B4044DEA389C8B50DD37D9272A24B4753B22F29978861DE14503F8B9BEDC2014654B26A434CF074F4D8749B88610ADADF5084A90ADBF749E2A; DATACENTER=EAGAN\r\n
    \r\n
    HTTP/1.1 503 Service Unavailable\r\n
    Cache-Control: private\r\n
    Content-Type: text/html\r\n
    Set-Cookie: ORA_WX_SESSION="10.237.138.33:80-1#2"\r\n
    Set-Cookie: portal=; expires=Wednesday, 27-Dec-95 05:29:10 GMT; path=/\r\n
    Connection: Keep-Alive\r\n
    Keep-Alive: timeout=5, max=999\r\n
    Server: Oracle-Application-Server-10g/10.1.2.0.2 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.0.2 (N;ecid=208440262161,0)\r\n
    Content-Length: 710\r\n
    Date: Fri, 26 Oct 2007 14:58:07 GMT\r\n
    \r\n
    Thanks -John

    Hi John,
    This question is probably more appropriate in one of the Portal forums, but perhaps you can take a look at the information in section C.5 Configuring the Portal Session Cookie in Appendix C of the Portal Configuration guide.
    Here is a link: http://download.oracle.com/docs/cd/B14099_19/portal.1014/b19305/cg_app_c.htm#sthref1907
    Regards,
    Peter

  • Portal Session content in BSP

    Hello,
    My BSP inside an iView is located in the xRPM content. What I now try to achieve is, to hand over the chosen project-id from the portal to the BSP - iView.
    request->get_cookies provides me with the cookie "sap-appcontext", which I think contains the portal session-id. Since BSP has it's own session-id, I somehow have to get the session - content of the portal, where I hope, the chosen project-id is stored.
    Am I on the right way?
    I would appreciate any help or suggestions.
    Thanks in advance.
    Daniel

    <i>How can I register such an event inside xRPM-content without modifying the standard-source? Or how can I find out, if there's an event fired I could use?</i>
    I see no real easy way. I have never seen the source code of xRPM, and know no developers inhouse to ask directly. Effectively portal eventing is just JavaScript code. To see if xRPM supports any events, why not look at the outputted HTML. Look for anything to do with EPCM, or search for events.
    <i>It's hard to understand, why it's not possible to access session-information of the portal from a BSP started in the same page...</i>
    What exactly session information do you wish to know. From my understanding, you have a BSP running inside the portal. Inside this BSP application you wish to know something. I assume not exactly session ids, but some other information from the portal. Maybe this helps us.
    At the low level of HTML is might be easier to understand. The portal renders the HTML page, and then starts the BSP inside an <iframe>. The BSP does not know anything about the surrounding environment. Of course you could use JavaScript to walk up the dom (document.parent) and look at things inside the other frames. But keep in mind you are in the browser, and not on the portal server, not in the ABAP stack (where BSP is). So you can only look at rendered code. And this can (and will) change per SP.
    At the end of the day it is all plain HTML in your browser, and this are what sets your limitations.
    brian

  • Not able to see backend material document number in SUS

    Hi,
    A GR is created in ECC. It is avaiable for disply in the supplier's login.  We are able to achieve this.
    The question is "We are not able to see backend (ECC) material document number anywhere on the screen. We are only able to see the SUS Confirmation number (i.e. as per the number range assigned to BUS2233). Is it standard behavior?
    Details: SRM7.0 SP07, ECC Ehp4, Using MM-SUS. Plan driven procurement.
    Ganapathi

    Dear Manjunath,
    Thanks for the response.
    We have noticed that, the back end (ECC) material documents are getting replicated to SUS as we are able to see this number in BBP_PD &  BBP_PDBEH-BE_OBJECT_ID.
    So, let me put the question this way.
    Our issue is with display of document in the portal (BSP Pages).
    For Example, in case of Invoice, the supplier can see the back end MIRO invoice document number with the "External Reference" Label, under Basic Data section. The case is NOT same with GR. The back end (ECC) material document number is NOT seen any of the layout (for end user, who has logged in as supplier).
    Is it standard behavior? If we want that, the suppliers should be able to see the material document number in the portal, when a GR is created in ECC, what settings we have to do?
    Ganapathi

  • Portal is not comming up after after adding param (element.resynch=force)

    Hi Team,
    Portal is not coming up after adding the parameter element.resynch=force in the bootstrap.properties under the location
    <j2ee-home>\cluster\bootstrap\bootstrap.properties  according to the note 710663.
    I am pasting the required log files ....
    default trace:-
    #1.#E41F13351581007C00001EF80006F0A000048E816A098C02#1282586387778#com.sap.engine.services.dbpool##com.sap.engine.services.dbpool#u:jobej#1019#####Thread[UWL Pooled Thread:1,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java#dbpool_0300##ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQP1DB" is stopped or not started, 2) Connector service is stopped or has not been started.#3#ResourceException#ConnectionFactoryImpl.getConnection()#com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQP1DB" is stopped or not started, 2) Connector service is stopped or has not been started.#
    #1.#E41F13351581007C00001EF90006F0A000048E816A098D28#1282586387778#com.sap.engine.services.dbpool##com.sap.engine.services.dbpool#u:jobej#1019#####Thread[UWL Pooled Thread:1,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQP1DB" is stopped or not started, 2) Connector service is stopped or has not been started.
            at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59)
            at com.sap.netweaver.bc.uwl.utils.db.ConnectionFactory.getConnection(ConnectionFactory.java:121)
            at com.sap.netweaver.bc.uwl.utils.db.ConnectionFactory.getConnectionForTransaction(ConnectionFactory.java:177)
            at com.sap.netweaver.bc.uwl.utils.db.Transaction.begin(Transaction.java:72)
            at com.sap.netweaver.bc.uwl.utils.db.Transaction.getConnection(Transaction.java:55)
            at com.sap.netweaver.bc.uwl.core.cache.CacheManager.onItemUpdated(CacheManager.java:2569)
            at com.sap.netweaver.bc.uwl.core.BaseItemManager.internalFillHollowAndBOAttributes(BaseItemManager.java:176)
            at com.sap.netweaver.bc.uwl.core.HollowAttributesThread$1.run(HollowAttributesThread.java:67)
            at java.security.AccessController.doPrivileged(AccessController.java:219)
            at javax.security.auth.Subject.doAs(Subject.java:477)
            at com.sap.netweaver.bc.uwl.core.HollowAttributesThread.run(HollowAttributesThread.java:53)
            at com.sap.netweaver.bc.uwl.core.ThreadManager$PoolWorker.run(ThreadManager.java:191)
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPQP1DB" is stopped or not started, 2) Connector service is stopped or has not been started.
            at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:195)
            at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51)
    dev_jcontrol  :-
    JControlStartJLaunch: program = /usr/sap/QP1/JC00/exe/jlaunch
    -> arg[00] = /usr/sap/QP1/JC00/exe/jlaunch
    -> arg[01] = pf=/usr/sap/QP1/SYS/profile/QP1_JC00_mepxq1cs01
    -> arg[02] = -DSAPINFO=QP1_00_bootstrap
    -> arg[03] = -nodeId=-1
    -> arg[04] = -file=/usr/sap/QP1/JC00/j2ee/cluster/instance.properties
    -> arg[05] = -syncSem=24117264
    -> arg[06] = -nodeName=bootstrap
    -> arg[07] = -jvmOutFile=/usr/sap/QP1/JC00/work/jvm_bootstrap.out
    -> arg[08] = -stdOutFile=/usr/sap/QP1/JC00/work/std_bootstrap.out
    -> arg[09] = -locOutFile=/usr/sap/QP1/JC00/work/dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=/usr/sap/QP1/SYS/profile/QP1_JC00_mepxq1cs01
    -> lib path = LIBPATH=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr/sap/QP1/JC00/exe:/usr/sap/QP1/JC00/exe:/tmp/sapinst_exe.454834.1268233847:/usr/sap/QP1/SYS/exe/run:/usr/java14_64/jre/bin/j9vm:/usr/sap/QP1/JC00/exe::/usr/lib:/usr/sap/QP1/JC00/j2ee/os_libs:/usr/sap/QP1/JC00/exe:/usr/sap/QP1/JC00/exe:/usr/lib:/lib:/usr/sap/QP1/SYS/exe/run
    -> exe path = PATH=/usr/java14_64/bin:/usr/sap/QP1/JC00/j2ee/os_libs:/usr/java14_64/bin:/home/qp1adm:/usr/sap/QP1/SYS/exe/run:/usr/bin:/etc:/usr/sbin:/usr/ucb:/home/qp1adm/bin:/usr/bin/X11:/sbin:.:/db2/db2qp1/sqllib/bin:/db2/db2qp1/sqllib/adm:/db2/db2qp1/sqllib/misc
    [Thr  1] JStartupICreateProcess: fork process (pid 532606)
    [Thr  1] Tue Aug 24 09:16:10 2010
    [Thr  1] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx_mt. 1642]
    [Thr  1] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)
    [Thr  1] JControlCloseProgram: started (exitcode = 66)
    [Thr  1] JControlCloseProgram: good bye... (exitcode = 66)
    dev_bootstrap :-
    [Thr 772] Tue Aug 24 09:16:08 2010
    [Thr 772] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [bootstrap]
    -> arg[  0]: com.sap.engine.bootstrap.Bootstrap
    -> arg[  1]: ./bootstrap
    -> arg[  2]: ID0092516
    [Thr 772] Tue Aug 24 09:16:09 2010
    [Thr 772] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 772] JLaunchIExitJava: exit hook is called (rc = 66)
    [Thr 772] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 772] SigISetIgnoreAction : SIG_IGN for signal 20
    [Thr 772] JLaunchCloseProgram: good bye (exitcode = 66)
    jvm_bootstrap :-
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:476)
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
            at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    com.sap.engine.frame.core.configuration.ConfigurationException: The property "rdbms.url" does not exist
            at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:242)
            at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
            at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:74)
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:473)
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
            at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.exception.standard.SAPIllegalArgumentException: The property "rdbms.url" does not exist
            at com.sap.engine.core.configuration.impl.utilities.PropertyUtil.getStringProperty(PropertyUtil.java:137)
            at com.sap.engine.core.configuration.impl.utilities.PropertyUtil.getStringProperty(PropertyUtil.java:160)
            at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:85)
            at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
            at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
            at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
            ... 11 more
    [Bootstrap module]> Problem occurred while performing synchronization.
    Quick response is really appriciated ***
    Thanks & Regards,
    Revanth Kumar Kadali

    Hi ,
    now the error status chaged in the logbootstrap_ID0092516.0.log_
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[../../work/log_bootstrap_ID0092516.log]/>
    <!PATTERN[log_bootstrap_ID0092516.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter([%24d] %m)]/>
    <!ENCODING[UTF8]/>
    <!FILESET[0, 2, 2097152]/>
    <!PREVIOUSFILE[log_bootstrap_ID0092516.1.log]/>
    <!NEXTFILE[log_bootstrap_ID0092516.1.log]/>
    <!LOGHEADER[END]/>
    [Aug 25, 2010 11:10:07...] -
    [Aug 25, 2010 11:10:07...] Bootstrap MODE:
    [Aug 25, 2010 11:10:07...] <INSTANCE GLOBALS>
    [Aug 25, 2010 11:10:07...]  determined by parameter [ID0092516].
    [Aug 25, 2010 11:10:07...] -
    [Aug 25, 2010 11:10:08...] Exception occurred:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:476)
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
            at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
            at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:365)
            at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:130)
            at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
            at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
            at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
            at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
            at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:74)
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:473)
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
            at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.sql.log.OpenSQLException: Could not load class com.sap.dbtech.jdbc.DriverSapDB.
            at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
            at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:99)
            at com.sap.sql.jdbc.direct.DirectDataSource.getPooledConnection(DirectDataSource.java:130)
            at com.sap.sql.jdbc.direct.DirectDataSource.getPooledConnection(DirectDataSource.java:110)
            at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:309)
            ... 15 more
    Caused by: java.lang.ClassNotFoundException: com.sap.dbtech.jdbc.DriverSapDB
            at java.lang.Class.forName(Class.java:119)
            at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:90)
            ... 18 more
    [Aug 25, 2010 11:10:08...] [Bootstrap module]> Problem occurred while performing synchronization.
    Thanks & regards,
    Revanth Kumar

  • Management Portal does not render content in IE10

    This appears to be a somewhat recent experience: I have logged on to the
    https://manage.windowsazure.com last month and all was working fine. Today I went and logged on via the ASC/ADFS SSO, and got the management portal with the top menu working, but just a spinner image in the body of the page. The spinner is stuck there after
    several minutes (see the attached image). I am running IE10.0.9200.17183 on Windows Server 2012 Datacenter Edition x64 (Version 6.2, build 9200). The portal opens just fine if I use Google Chrome browser. In IE10 I tried playing with browser compatibility
    mode in developer tools - same result. I've also tried in-private browser session to make sure I can exclude stale cache. No joy.
    I was wondering if this is a known issue, or perhaps an indication that Microsoft is shifting to using the new portal administration interface (it actually works in IE 10 no problem, I just don't like it as much). Thanks in advance.

    I got this problem a few times before. I just switched to use another browser and it would work. Then after a while IE will work again. Not sure of the root cause.
    Frank

  • Portal Session Memory Consumption

    Dear All,
                          I want to see the user sessions memory consumption for portal 7.0. i.e. if a Portal user opens a session, how much memory is consumed by him/her. How can i check this. Any default value that is associated with this?
    Backend System memory load will get added to portal consumption or to that specific Backend System memory consumption.
    Thanks in Advance......
    Vinayak

    I'm seeing the exact same thing with our setup (it essentially the same
    as yours). The WLS5.1 documentation indicates that java objects that
    aren't serializeable aren't supported with in-memory replication. My
    testing has indicated that the <web_context>._SERVLET_AUTHENTICATION_
    session value (which is of class type
    weblogic.servlet.security.ServletAuthentication) is not being
    replicated. From what I can tell in the WLS5.1 API Javadocs, this class
    is a subclass of java.lang.object (doesn't mention serializeable) as of
    SP9.
    When <web_context>._SERVLET_AUTHENTICATION_ doesn't come up in the
    SECONDARY cluster instance, the <web_context>.SERVICEMANAGER.LOGGED.IN
    gets set to false.
    I'm wondering if WLCS3.2 can only use file or JDBC for failover.
    Either way, if you learn anything more about this, will you keep me
    informed? I'd really appreciate it.
    >
    Hi,
    We have clustered two instances of WLCS in our development environment with
    properties file configured for "in memory replication" of session data. Both the
    instances come up properly and join the cluster properly. But, the problem is
    with the in memory replication. It looks like the session data of the portal is
    getting replicated.
    We tried with the simplesession.jsp in this cluster and its session data is properly
    replicated.
    So, the problem seems to be with the session data put by Portal
    (and that is the reason why I am posting it here). Everytime the "logged in "
    check fails with the removal of one of the instances, serving the request. Is
    there known bug/patch for the session data serialization of WLCS? We are using
    3.2 with Apache as the proxy.
    Your help is very much appreciated.--
    Greg
    GREGORY K. CRIDER, Emerging Digital Concepts
    Systems Integration/Enterprise Solutions/Web & Telephony Integration
    (e-mail) gcrider@[NO_SPAM]EmergingDigital.com
    (web) http://www.EmergingDigital.com

  • Closing and Killing Portal Session Error

    Hi Experts,
    I'm getting some problems with my killing sessions. We did some implements with Integrated Planning and repots are running in the portal. I have noticed a dramatic low performance in my portal and I realized that sessions are not closing in the portal. I've been trying log our from the portal session and the session still alive (I seem them in SM04 transaction). How Could it be possible if I'm logging out properly?..... Is there something I've been missing???? What else Could I do for fixing the problem???
    Thanks for your help (Any help would be rewarded).
    David

    Hi,
    As far as understand you are running reports from an ABAP backend system in the portal and the sessions in the ABAP backend system are not closed by the portal.
    Which technology are the reports based on (BSP, transaction) ?
    It seems to me the Distributed session management(DSM) in the portal is not working  and therefore not triggering the closing of the sessions in the backend when the user logs off or navigates to another page.
    (it might also be that the BSP is defined as stateful )
    See http://help.sap.com/saphelp_nw04/helpdata/en/ca/a9a7408f031414e10000000a1550b0/frameset.htm for more info on DSM
    Cheers
    Dagfinn

  • Logging of the OWA kills portal session

    Hi,
    I have integrated OWA iViews into Portal.
    The problem im facing is when im clicking the logoff button on the OWA
    iViews, the Portal session is killed.
    I confirmed this from the SAP Note 732911
    Could you please provide me with any updated solution or work around.
    whether the problem is rectified ??.
    Regards,
    Ricky

    The Problem has no solution as of now. It is confirmed when i raised an OSS Note for the same.
    According to the JSR page 63 line 25
    For portlets within the same portlet application, a portlet container must ensure that every portlet request generated as result of a group of requests originated from the portal to complete a single client request receive or acquire the same session.
    In addition, if within these portlet requests more than one portlet creates a session, the session object must be the same for all the portlets in the same portlet application.
    Hope this will help others immediately...without spending a long time by searching and raising OSS notes.
    Regards,
    Ricky

  • Role mapping between Portal and Back end systems

    I am new to SAP EP.
    I just want to know how the mapping between portal and back end system happens.
    Scenario : There is a role in ECC system...say FI India. Now there is a request by the FI team that they want to access this role from Portal. In this case, please tell me how the security team will do it. Because I guess, it has to be done by the security team.

    Hi,
    Usually the role from backend is uploaded to portal then it will be seen as Group and we need to assign our portal roles to this group. Please refer [this|http://help.sap.com/saphelp_nw73/helpdata/en/d6/7859ec80df46738e23ccb4f4c8c502/content.htm].
    Regards,
    Samir

Maybe you are looking for