About ESS/MSS -Undeployment

Hi to All
I have undeployed ESS but still in the EP server its showing the roles and workset of ESS
how to remove that what is the process for undeploment
thank you
pavan

When you undeploy ESS/MSS business package it will remove the actual application but will not remove the pcd content( likeiviews/worksets ) automatically, You need to remove the corresponding ESS/MSS folder itself.

Similar Messages

A question about ESS / MSS implementation.

Hi All,
Just a brief again about our landscape as:
1. We have an ERP ECC5.0 system which has J2EE6.40(add-in) without the 'EP' usage type and the present Support package level of the relevant ESS and MSS components are as follows:
a. J2EE6.40 Support Package level is '17'.(We are going to deploy the XSS components here)
b. ERP ECC5.0 system's Software Components details are as follows:
SOFTWARE COMPONENTS RELEASE LEVEL HIGHEST SUPPORT PACKAGE APPLIED
SAP_BASIS 640 0016 SAPKB64016
SAP_ABA 640 0016 SAPKA64016
SAP_APPL 500 0009 SAPKH50009
SAP_HR 500 0019 SAPKE50019
EA-HR 500 0005 SAPKGPHC05
2. We have a separate NW2004s(Dual stack(ABAP7.0+J2EE7.0) installation having EP7.0 with Support Package level is '16'. (We are going to deploy the Business Package for ESS & MSS here).
Here are my questions?
1. what is the best 'Support Package' level recommendation or combination is applicable for all the components(J2EE6.40,SAP_BASIS,SAP_ABA,SAP_APPL,SAP_HR,EA-HR...etc.,) involved in this type of mixed landscape - ESS & MSS implementation?
2. If we apply the higher Support Packages 'only' for the ERP ECC5.0 software components such as: SAP_BASIS,SAP_ABA,SAP_APPL,SAP_HR,EA-HR - what other ERP ECC5.0 software components would get impacted from functionality prespective ?(let us say if we keep the current Support Package level for other software components as untouched)
3. Is there any dependency exist from the Support Package point-of-view between the ESS MSS Business Packages and with XSS components(PCUI_GP; ESS; MSS)
4. Is there any dependency exist from the Support Package point-of-view between XSS components and ERP ECC5.0 software components such as "SAP_BASIS,SAP_ABA,SAP_APPL,SAP_HR,EA-HR"
Kindly address my above concerns.
Regards,
Vijay

Hi Vijay
To answer your questions
First you should check note 1007341 which helps consultants proposing this type of landscape
To answer some of your questions
1) For SPs you have to patch ERP 2004 components following ERP 2004 stack and patch
    ERP 2005 components following the ERP2005 stack recommendations at www.service.sap.com/sp-stacks
    in terms of equivalence levels I would select SP levels from each stack with similiar release dates
2) Presumably you will be using ERP2004 components in the front-end in some capacity therefore these
    ERP2004 components must be patched in line with ECC 500 stacks
3) There is dependancies between Business Packages and XSS
4) There is dependancies between back-end components SAP_HR and EA_HR and XSS/BP
    SAP_HR and EA_HR also have their own dependancies with the other back-end components listed
Best wishes
Stuart

Help about ESS/MSS - Deploy error and landscape question

Hi.
I read a lot of post about this topic, but I continue something confuse about them.
I want to configure ESS and MSS.
My landscape is:
- J2EE 7.0 with Portal 7.0 (2004s) in a server A.
- ECC 5.0 ( with HR component SP05) in a server B.
Server B, has only stack Abap.
Server A is the latest version of Netweaver today. (stack j2ee and stack abap, BI, XI, Portal, etc)
I download and deploy in server A (J2EE 7.0), this components:
- BP ESS for erp2004
- BP MSS for erp2004
When I deploy the ESS BP, the deployment break raising this kind of error with the most of components, for example:

===========================================================================
Deployment started Tue Apr 10 12:01:57 ART 2007
===========================================================================
Starting Deployment of ess/au/addr
Aborted: development component 'ess/au/addr'/'sap.com'/'MAIN_xss04PAT_C'/'1178669'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04PAT_C'/'1000.100.0.15.1.20070309085432''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr.. Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of ess/au/addr finished with Error (Duration 5187 ms)
Starting Deployment of SAP_ESS
Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_xss04PAT_C'/'1000.100.0.15.1.20070309085432''/'0':
Failed deployment of SDAs:
development component 'ess/au/addr'/'sap.com'/'MAIN_xss04PAT_C'/'1178669'/'0' : aborted
Please, look at error logs above for more information!
Deployment of SAP_ESS finished with Error (Duration 4781 ms)

Obviously, for this reason the most of iviews raise errors. A few of these works ok.
I assign role, and others configuration steps, this part I thinks that is OK
I configured the Jco, the role in Portal, the profile in ERP for ESS, etc.
My principal question is:
Can I use Portal 7.0 against ECC 5.0 in order tu use ESS/MSS based on webdynpro, without stack j2ee in ECC server (B) ?
Is necesary install J2ee stack in my server B ? or not?
Where I need to deploy the XSS 500 components ? in the J2EE 7.0 ?
Why when I deploy have this problem and the most of components cant deploy it?
For my landscape, which is the recommended setup ?
thanks in advance.!
Leandro.

My principal question is:
Can I use Portal 7.0 against ECC 5.0 in order tu use ESS/MSS based on webdynpro, without stack j2ee in ECC server (B) ?
You can use Portal 7.0 against ECC 5.0
Is necesary install J2ee stack in my server B ? or not?
You don't need to install J2EE stack on ECC system
Where I need to deploy the XSS 500 components ? in the J2EE 7.0 ?
Deploy XSS on Portal server not on ECC.
Why when I deploy have this problem and the most of components cant deploy it?
There won't be any issue. Go for ERP 2005
For my landscape, which is the recommended setup ?
As per the landscape mentioned by you, I will suggest go for ERP 2005 & XSS 600.
If you have further queries, mail me at [email protected]

Information required about ESS MSS forms

Please let me know following points:-
1.As per my understanding HCM Processes and Forms ( Hiring, Transfer ,Maternity leave ,Termination ) needs
Hr administrator Role it not present in portal box so please let me know if we need it?.
2.It belongs to ESS/MSS Package or it is a seprate business package?.
3.If possible kindly let me know complete Iview names for above mentioned forms.
Please let me know about it.

Laxmikant,
The forms should be available with if you install the EA-HR component in ECC and there is BP for HR Admin which contains the iViews like Start Process etc.
You can find the package :- Click to goto [SAP Portal Content Portfolio|https://www.sdn.sap.com/irj/sdn/contentportfolio] --> Business Packages for Specialists --> Business Package for HR Administrator (mySAP ERP)
And documentation regarding it is available [http://help.sap.com/saphelp_erp2005/helpdata/en/98/32e842cd990121e10000000a155106/frameset.htm]
Once you this, you will need Adobe License (check note : 736902) and need to configure ADS if you plan to create new forms.
Chintan

Global information about ESS/MSS

I would like to have a global overview about the different existing versions on SAP using ESS/MSS portal:
Different versions(e.g: R/3 4.6, ECC 5.0-ECC 6.0 EP5.0 etc..) /Technical installation
System requirements
Fonctionalities
Can someone provide more information ?
Thanks in advance.

Look at the information in http://help.sap.com for EACH version you are interested in. Also, keep in mind that most are backwards compatible (so, theoretically even on ECC5, you could run 4.6c ITS services if you so desired). For installation information, also check the documents on http://service.sap.com (can not post here because they are copywritten and part of the Marketplace access).

About ESS & MSS Packages

Hi,
I am new to EP in our trainning schedule we are going with ESS & MSS business packages.Can anyone explain me about these packages and about HomePage Framework in detail and any material regarding ESS&MSS aswell as, HomePage Framework and how important these things in real time.
Please help me!!!!!!!!
Thank you,
Rahul

Hi Rahul
Please check this :
[http://wiki.sdn.sap.com/wiki/display/ERPHCM/HCMESS|http://wiki.sdn.sap.com/wiki/display/ERPHCM/HCMESS]
[http://wiki.sdn.sap.com/wiki/display/ERPHCM/HCMMSS|http://wiki.sdn.sap.com/wiki/display/ERPHCM/HCMMSS]
ESS and MSS Role u2013 [A Step by Step SPRO Configuration Document|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e05d564f-6e1c-2d10-42b2-9e21a211950d]
Look for articles/blogs/elearnig for more detials.
Best Regards
Arun Jaiswal

About ESS/MSS -deployment

Hi to all
what are the other components are required for ESS and MSS configuration
thank you
pavan

Hello Pavan,
Please check the below link for the components to download and install.
https://www.sdn.sap.com/irj/sdn/wiki?path=/pages/viewpage.action&pageid=31476
Also check below SAP Notes to get the exact version of component to download.
Note:-1004528
Note:- 908569
Regards
Deb

E-Learning regarding ESS/MSS & HomePage FrameWork

Hi,
Can Anyone provide me E-Learnings Regarding ESS & MSS packages and HomePage Framework i am unable to find them.
Thanks,
Rahul

Hi Rahul,
Check out this thread
about ESS & MSS Packages
It holds a lot of information. Hope it will be useful to you. Search for similar threads in SDN
Regards
Anand Sekar

Basic Information on ESS/MSS

Hello Guru's,
Kindly send me basic details about ESS/MSS.
Edited by: Prashanth Doggali on Nov 27, 2010 2:07 PM

Hi,
Please read this which is helpful....
ESS = Employee Self Service
It was designed to provide employees with a front-end user friendly way of maintaining their own details critical to HR operations
The idea was to reduce the amount of data entry which would need to be performed by HR (administrators or back office staff)
Employees could maintain or change their own details to ensure accuracy
The core components are
CA-ESS-WD
CA-ESS-ITS
PA-ESS-OCY/US/DE
PA-ESS-XX
These cover mainly the ESS screens for basic PA infotype updates and the back-end handling
ESS also provides a guided procedure application called Life and Work Events
Life and Work Events is a step by step workflow for employees particularly new employees (commonly known as My First Days) to maintain their details or document changes in their working life.
This is specifically for US customers however I believe customers can adapt it for their own countries
For further information see
Architecture of ESS
ESS environment consists of a front-end and a back-end system
The ECC system is the back-end R/3 system which contains HR master data and ESS related back-end code and customizing
The Portal is a J2EE server handling browser enquiries from front-end users - it provides the front-end environment for the end user
The front-end communicates with the back-end via a JCO connection JCO is a method of RFC communication between ABAP and JAVA
ESS is viewable via a browser (Internet Explorer etc)
The possibilities of usable browser versions depend on the Portal versions recommendations
A user is given a role which contains a workset, pages and iviews
An example of a role is the Employee Self Services tab in a Portal
An example of a workset is Overview tab in Portal
An example of a page would be the Overview Page
The layout of ESS is determined mostly by Homepage Framework (HpF) customizing in the Implementation Guide (IMG)
HpF is supported by component CA-GTF-TS-XSS
other things you need to configure like AREA GROUP PAGE , AREA PAGE , SUB AREAS, SERVICES, RESOURCES..
thanks
rafi

Label Modifications in ESS/MSS DCs -- question about *.xlf files

Hello,
I have seen this question in other places and all the answers did not quite make sense and were sometimes conflicting.
We have been trying to modify some text labels in an ESS/MSS web dynpro DC. We make the changes in the View properties, save metadata, reload, rebuild, and deploy. The changes are showing in design time, but not runtime. I have seen some postings from people saying to change the *.xlf file, but then I have also seen other documentation from SAP help saying not to change the *.xlf files (b/c they are generated at build time). Also, the generic *.xlf file appears to be changed at build time, but the language specific one (in our case en) is not, which I would guess is why the runtime changes are not showing up. What is the correct solution and process to make these changes appear? Is there an additional step for regenerating a language specific *.xlf?
I also know that you can change these labels via content admin in EP7, but we want to change them at design time.
Thanks in advance.

Hello,
I have seen this question in other places and all the answers did not quite make sense and were sometimes conflicting.
We have been trying to modify some text labels in an ESS/MSS web dynpro DC. We make the changes in the View properties, save metadata, reload, rebuild, and deploy. The changes are showing in design time, but not runtime. I have seen some postings from people saying to change the *.xlf file, but then I have also seen other documentation from SAP help saying not to change the *.xlf files (b/c they are generated at build time). Also, the generic *.xlf file appears to be changed at build time, but the language specific one (in our case en) is not, which I would guess is why the runtime changes are not showing up. What is the correct solution and process to make these changes appear? Is there an additional step for regenerating a language specific *.xlf?
I also know that you can change these labels via content admin in EP7, but we want to change them at design time.
Thanks in advance.

Function modules or BAPIs for ESS MSS

Hi Experts,
I am new to HR (ESS/MSS & who's who). I am looking for standard BAPI's and Function Modules that would give me information about an employee's upper level's and lower levels (reporting).
My requirement is to build an Webdynpro Application with taking employee id as user input and display his uplevel's and downlevel's. Also, hyperlink on employee should help me to further navigate to the corresponding employee's information.
Note: I tried to search this forum, but unable to narrow down the required business functions that i require.
Thanks,
Gaurav.

https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=190743879
RH_GET_MANAGER_ASSIGNMENT

SAP IDES ECC 6.0 configuration for ess/mss

Hi,
Iam new to sap . i want to practice various scenarios in ess/mss in my own pc which is installed with ecc 6.0 . what are the configuration to be made in ecc 6.0 for maintaining about 10-20 users for using ess/mss scenarios. i have a knowledge on webdynpro java and little knowledge on ep and using r/3 server. The 10-20 users created should be able to use ess/mss through portal .
So, list the steps configuring for 10-20 users for using ess/mss in ecc ides 6.0 server.
Thanks & regard
prasad

<< Do not post the same question across a number of forums >>

Portal runtime error, when click on ESS MSS

Dear Gurus,
Whenever I click on any link of MSS, it gives me runtime error. Please see the screenshot.
Portal runtime error
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID 03:38_14/05/14_0019_13493050
See log file for details about this exception
Screen shot
- SSO steps configured
- ESS/MSS roles given in both of ABAP and JAVA side
ITS, connector and WEB AS test successfully (screen shot maintaned below)
Only Alias defined : SAP_R3_HumanResources
Detalied Error Log;
Failed to invalidate cached entry for user a368ecb2db6411e3a030000000cde33a Exception:java.rmi.RemoteException: Cannot clear ICM server cache by [a368ecb2db6411e3a030000000cde33a] etag.; nested exception is:
com.sap.bc.proj.jstartup.icmadm.IcmAdmException: interface disabled
[EXCEPTION]
java.rmi.RemoteException: Cannot clear ICM server cache by [a368ecb2db6411e3a030000000cde33a] etag.; nested exception is:
com.sap.bc.proj.jstartup.icmadm.IcmAdmException: interface disabled
at com.sap.engine.services.httpserver.server.CacheManagementInterfaceImpl.clearCacheByEtag(CacheManagementInterfaceImpl.java:33)
at com.sap.netweaver.rtmf.serverimpl.users.RTMFUser.clearICMCache(RTMFUser.java:231)
at com.sap.netweaver.rtmf.serverimpl.users.RTMFUser.doLogout(RTMFUser.java:296)
at com.sap.netweaver.rtmf.serverimpl.users.UserList.removeUser(UserList.java:123)
at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.doLogout(UserManagerService.java:590)
at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.activeActionMethod(UserManagerService.java:100)
at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.onMessageArrived(UserManagerService.java:71)
at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.onUserMessageArrived(UserManagerService.java:698)
at com.sap.netweaver.rtmf.messagingimpl.messages.RTMFMessageDispatcher.sendMessageToService(RTMFMessageDispatcher.java:45)
at com.sap.netweaver.rtmf.serverimpl.core.MessageDispatcher.sendMessageToService(MessageDispatcher.java:46)
at com.sap.netweaver.rtmf.serverimpl.core.MessageDispatcher.handleRequest(MessageDispatcher.java:72)
at com.sap.netweaver.rtmf.serverimpl.core.dispatch.dispatchers.SendDispatcher.dispatch(SendDispatcher.java:37)
at com.sap.netweaver.rtmf.serverimpl.core.RTMFCore.handleSendRequest(RTMFCore.java:190)
at com.sap.netweaver.rtmf.serverimpl.core.RTMFCore.handleRequest(RTMFCore.java:154)
at com.sap.netweaver.rtmf.serverimpl.server.RTMFServer.handleRequest(RTMFServer.java:89)
at com.sap.netweaver.rtmf.servlet.ServletWrapper.doPost(ServletWrapper.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
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.MonitoringFilter.process(MonitoringFilter.java:29)
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.SessionSizeFilter.process(SessionSizeFilter.java:26)
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.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: com.sap.bc.proj.jstartup.icmadm.IcmAdmException: interface disabled
at com.sap.bc.proj.jstartup.icmadm.IcmAdm.getInstance(IcmAdm.java:77)
at com.sap.engine.lib.http.cache.CacheAdmin.getInstance(CacheAdmin.java:53)
at com.sap.engine.lib.http.cache.CacheAdmin.invalidateCacheEntries(CacheAdmin.java:30)
at com.sap.engine.services.httpserver.server.CacheManagementInterfaceImpl.clearCacheByEtag(CacheManagementInterfaceImpl.java:29)
... 56 more
LOG OVERVIEW

After implementing the PCUI_GP , ESS is not empty anoymore but it is giving error like this ;
Detailed Error ;
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session O8h94DN06FMAxZD*frJ44w--szntRnBBZbpD5Fsc0H8XnA--/pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.areagroup_overview/com.sap.pct.erp.ess.overview/sap.com/pcui_gp~xssutils/XssMenu/base/. The causing exception is nested. RID=50ba7f52dc4311e3bf72000000cde33a
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:663)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:349)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:62)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:39)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:46)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToAppContext(ExecutionContextDispatcher.java:68)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:53)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:244)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callRequestManager(JavaApplicationProxy.java:1244)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callEmbeddedApplication(JavaApplicationProxy.java:1122)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$StartCommand.doExecute(JavaApplicationProxy.java:1575)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$AbstractCommand.execute(JavaApplicationProxy.java:1488)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.execute(JavaApplicationProxy.java:1028)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.execute(JavaApplicationProxy.java:859)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.start1(JavaApplicationProxy.java:637)
at com.sap.tc.webdynpro.portal.pb.impl.JavaApplicationProxyAdapter.create(JavaApplicationProxyAdapter.java:166)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1661)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:408)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:638)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:1087)
at com.sap.portal.pb.PageBuilder$PhaseListenerImpl.doPhase(PageBuilder.java:2091)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:251)
at com.sap.tc.webdynpro.clientserver.phases.PortalDispatchPhase.execute(PortalDispatchPhase.java:50)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:894)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
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.MonitoringFilter.process(MonitoringFilter.java:29)
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.SessionSizeFilter.process(SessionSizeFilter.java:26)
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.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: com.sap.tc.webdynpro.services.exceptions.ApplicationFaultException: wdDoInit: exception thrown in this user coding area
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:164)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:258)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:590)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1457)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:660)
... 78 more
Caused by: com.sap.tc.webdynpro.progmodel.context.DictionaryException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getScalarType(DictionaryHandler.java:378)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:126)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:438)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:1002)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:294)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:974)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:978)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:67)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:205)
at com.sap.tc.webdynpro.progmodel.components.Component.getCustomControllerInternal(Component.java:668)
at com.sap.tc.webdynpro.progmodel.components.Component.getController(Component.java:597)
at com.sap.tc.webdynpro.progmodel.components.Component.getController(Component.java:552)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:275)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:190)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:204)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:105)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:161)
... 84 more
Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
at com.sap.tc.webdynpro.services.datatypes.core.DictionarySetup$1.fillSldConnection(DictionarySetup.java:51)
at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:437)
at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:361)
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:198)
at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:161)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:96)
at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:75)
at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:63)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:230)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getScalarType(DictionaryHandler.java:370)
... 100 more
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:153)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:161)
at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:64)
at com.sap.tc.webdynpro.services.datatypes.core.DictionarySetup$1.fillSldConnection(DictionarySetup.java:32)
... 109 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load client to connect to SLD. Please check your SLD connection settings using the Visual Admin.
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:626)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getClient(SystemLandscapeFactory.java:619)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.readJCODestinationFromSLD(JCOClientConnection.java:458)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:396)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:237)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:84)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:151)
... 112 more
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Getting CIMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:93)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:623)
... 120 more
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:75)
... 121 more

Linkage between ESS/MSS Resource Server -- Resource Object in ERP 2004

Dear all,
I have a question about settings in the backend configuration of ESS/MSS:
In the IMG activitiy, you define Resource Servers. And then you can choose a specific server for a Resource Object. Though, when I look into an already setup ESS/MSS-solution at customer site, I cannot find that any of the resource objects in use have a specific server entered - only relative paths.
How does this work then? How does the system know where (on which portal system) to find a specific portal page/image object that a resource object links to? Is there a 'default' resource server used?
Your help is much appreciated!
//Christine

Hi Prakash
This is the end of the dev_jrfc.trc from the abap/j2ee webdynpro server:
Error file opened at 20050608 101523 British Summer Time Rel 6.40
Error> occured >Wed Jun 08 10:15:23,406< >RfcGetException rc (7) message: The system is unable to interpret the SSO ticket received
<RfcGetException
Error> occured >Wed Jun 08 10:17:28,544< >RfcGetException rc (7) message: The system is unable to interpret the SSO ticket received
<RfcGetException
The portal dev_jrfc.trc does not report any errors.
Other information I should have mentioned: EP uses LDAP for user directory, the ABAP system uses its own user management, the J2EE on the ABAP server uses its own user management. The user I am testing with is the same name in all 3 systems and has full admin permissions in each.
Thanks, Fergus

ESS/MSS assert violation dump

Hi everyone,
When i try to access the personel data in the general information tab in ESS/MSS portal.
I am facing the below dump.I have searched in all sites but am not clear about this dump.please help me out.
Team...and then General Information
Unexpected exception when calling RFC from Profile-Application 'General Data'
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: The ASSERT condition was violated., error key: RFC_ERROR_SYSTEM_FAILURE.
Thanks,
Shalini
Edited by: salini bhimireddy on Jan 5, 2011 11:24 AM

the issue is either due to mismatch of use cases with time contraints in table below
1) The time constraints in T591A have been modified and the
   use case and time constraint combination is not consistent
   The recommended use case and time constraint combinations are
   TC1 can use A1,A4,B1,B4
   TC2 can use A1,A2,A3,A4,A5,B1,B2,B4,B5
   TC3 can use A6,B3
   It is also not recommend to modify time constraints as not
   only may it make the use case combination inconsistent but it
   may cause data inconsistencies

About ESS/MSS -Undeployment

Similar Messages

Maybe you are looking for