Solution manager - Tracking service message's Status.
Hi Friends,
COuld any one u help me to find out the way
to Track the status of service messages in solution manager.
the status will be initialy : open.
then in process then etc...
i need track the dates when the status became open to in-process.
Ram
Hey Guru,
Within the support message itself, there is facility for Change Documents, which stores whatever you desire...
Just open any support message, on then the menu bar, GO to Extras and then click on change documents....
Do reward for usefull answer....
Regards,
Anand...
Similar Messages
-
Does Solution Manager support Service Report for non-abap?
Does Solution Manager support Service Report for non-abap?
We can schedule and view reports for ABAP but for all the non-ABAP such as J2EE stack (PORTAL) we can not pull out a report.
If the answer is yes please let me know where I can get the documentation of how to setup SLA for PORTAL or non-ABAP.
I found a document on EWA non-abap but non for SLA.Hi
actually i am in task of setting up ewa for portal.
i had already done with abap components (ewa and sla)
i stronly believe one of the pre-requiste to get sla is EWA.
so i think if u can setup ewa for portal then you can get sla too.
Regards,
Vijay. -
Need help in Solution Manager System Monitoring-activating Instance Status
I would like to use System Monitoring with Solution Manager.
The agents CCMSPING and SAPCCM4X are installed on the monitored system and CCMS is configured
I've already created a solution and a logical component. Now i would like to activate Instance Status in the tree when i enter in Setup System Monitoring .... but i get a red alert an the following Message Instance status is no performance alert. Thresholds have been deleted ... how can i activate this Instance Status?
I am going my first steps in SAP SolMan and tried to solve this problem but i had no success. Can someone please help me? What i am doing wrong?
thanks...
Edited by: Satish Machavarapu on Dec 15, 2009 12:46 PM
Edited by: Satish Machavarapu on Dec 15, 2009 1:04 PMHi,
If you want to monitor the Availability status of the instance then check the below docs
[http://help.sap.com/saphelp_nw70/helpdata/EN/38/9e100dd7980fffe10000009b3810a5/frameset.htm]
[CCMSPING config|http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/d547f687-0901-0010-07a9-ce64cc044215]
[CCMS Agent config|http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/40ef0688-814a-2a10-afb1-89b40d83d0e0]
regards
Naveen
Edited by: Naveen Kumar on Dec 15, 2009 1:07 PM -
Queries on SAP Solution Manager ChaRM & Service Desk
Hi All,
I have couple of queries on ChaRM and Service Desk. Request your expert advice.
1. As we know it is possible to create a change request from service desk ticket. Now I want to know if it is possible to have a dependency between the Service Desk ticket and corresponding ChaRM request so that till the time the change request is not closed/ Abandoned, the service request cannot be closed.
2. Can a ChaRM change request can have multiple change documents attached to it and if yes how the status of the change request is determined. If we can create only one change document then is it the case that we can handle changes in only one satellite system with one change reuest. Example u2013 2 change requests are required if changes required in ECC & BI system for same incident.
Thnaks.
Best regards, VithalHi Sanjai & all,
Now I want to know some of the scenario where we are required to have multiple change documents. As we know once the change document has got created it is not possible to change the change request. Also in the change document we have certain actions (e.g. quality team approval) which we get on change level and not for each document. Please let me know how this will be possible in case we have multiple change documents getting created (say one for development team, other for customizing team and one for security team).
So in all we have a scenario where some actions are happening at change request level - then some changes at change document level (have multiple change documents)u2013 then again some actions which we want to do on the collective change (will not mind in doing at change document level).
Thanks for all your pointers.
Best regards,
Vithal -
Solution Manager J2EE services.
Hello !!
There are a lot of J2EE services to install or to patch SolMan 7.0 , i.e ADSSAP , BI_MMR,BI_UDI,CAF , CAF-UM, KM-KW_JIKS, LM-SERVICE,LM-TOOLS , UME etc.
Does it exist a wiki or such a document which describes these services , at least to know what they serve exactly, and what functional scenario they are used. Thanks...can you please check RFC status and also concern SM21 logentries.
regards
nag -
Solution Manager Diagnotics Services Definitiion File Update
Hi,
I'm looking for a way of upgrading the SMD Services Definition File. (see /smd/services - Configuration tab).
We are at SPS15, but it says SPS12...I guess we have to upgrade that part too.
Thank you,
Jerome M.For those interested, I found the answer, you have to import the XML attached to the SAP Note: 976054
-
Support Desk Message Creation in SOLUTION MANAGER through External Emails
Hello Experts,
I am a ABAP Developer , as mentioned in subject, my part is to Create support desk message in solution manager,through external Emails like outlook Express . To do this task i am in need of more information about some componenets which are used in solution manager support desk Message.
My Doubts are,
1) What is the use of Ibasecomponent in Message Creation?
2) What if the ibasecomponent is mentioned as a defaut value ' 24 ' ( i.e is the ibasecomponent for solution manager - support desk ) ?
3) To track the system from which the message is created , is ibase required or the SAP component will give those information?
If anyone has already worked with this subject, please give me some suggestions ASAP.
Thanks in Advance,
MohanaHello Mohana,
Let see if I can explain this well:
1) What is the use of Ibasecomponent in Message Creation?
When you define a Solution in the SOLMAN, you need to update your Ibase
Edit->Initial Data transfer for Ibase
This create a tree structure in the ibase IB52, as you can see in the attachment.
You get a componet number for SID-Client
You can configure the SOLMAN in a way that when a message arrives from
<System ID> <Installation Number> <Client> <User Name>
this is what solman knows from a message comming from a satellite, them you
know directly from which component/ibase the message has been received.
This is important data, the component/ibase, for reporting issue, for assigning this component to a sold-to-party (being in IB52, left tree, select a system and go to Goto->Partner you can assign a Sold-to party BP there for example)
2) What if the ibasecomponent is mentioned as a defaut value ' 24 '
By default the SOLMAN system has a Intalled base 01 already created for being used and maintained "automatically":
being in dswp, solution : Edit->Initial Data transfer for Ibase
If not you msut maintain the ibase manually from IB52, this is also possible.
The Ibase 01 is a prconfigured iBase for being used for the SOLMAN application.
Tink that the SOLMAN system is built up a CRM system, so the IBase is CRM matter. SOLMAN is only using some CRM applications to build the Service Desk scenario for example.
I3) To track the system from which the message is created , is ibase required or the SAP component will give those information?
Ibase is required
Hope this helps,
Dolores -
Create New Service Session at Solution Manager = Product System missing
We have installed SAP EHP 1 for SAP Solution Manager 7.0 last year but not really use it.
We have setup in the system landscape:
Server (ecc6sbx)
Databases (MCD)
Product System (MCD) => SAP ERP
Assigned them to logical component (eg ZECC6DEV)
RFC destination for MCD was generated
SDCCN Administration at solutions manager display MCD with SDCCN status in green color.
At the satellite system MCD, SDCCN Maintenance job was created and scheduled. Initial single run was also done.
There were no issue. Connection to SDCC_OSS was fine.
Back to the SOLUTION_MANAGER transaction, we created a new solution ECC ERP - Development.
In the Solution Landscape => Solution Settings, we have assigned the Logical Component into the System Group.
However when we expand the tree, and click on the Servers folder it did not display anything.
Click on the Product Systems also did not display anything.
We have another Solution Manager which display information on those Servers and Product Systems folder for satellite system.
Going back to the Solution Manager for the Solution ECC ERP - Development, I tried to Create New Service Session for EarlyWatch Alert. When I click on the Create button, I could only see SAP EarlyWatch Alert for Solutions, there is no SAP EarlyWatch Alert for the Reference Object MCD (<installation number). I could not create a session for MCD.
Does anyone have ideas what I am missing here? I am trying to attached a document which have print screen for reference while creating this message, but there is no such function here.
Adding to link to the document file contain print screen
[Wihtout System and EarlyWatch Selectable.doc|http://www.easy-share.com/1915633524/Wihtout System and EarlyWatch Selectable.doc]
[With System and EarlyWatch.doc|http://www.easy-share.com/1915633514/With System and EarlyWatch.doc]
Edited by: Steven Foo on May 24, 2011 8:00 AM
Edited by: Steven Foo on May 24, 2011 8:18 AMAnyway, in the solution manger how to we setup earlywatch alert for the SM SID host itself (source system)?
I have the information on the below from our solution manger
The data for this session is overdue. Data has not yet been transferred from the associated satellite system.
Go to the Service Data Control Center (transaction SDCCN) in the satellite system and check why the data has not been sent.
Typical sources of errors are:
The RFC connection for the SAP Solution Manager system is not working.
The 'Task Processor' background job, which collects the session data, has been changed.
Problems arose while data was being collected (see the detail log for the task that collects the session data).
A periodic 'SDCC Maintenance Package' task has not been scheduled to check whether your SAP Solution Manager system requests session data.
I tried to go SDCCN on the solution manager itself and look at the Maintenance Service Definitions:
I get the information:
No suitable RFC Destination found in SDCCN settings.
When I click ok I get the following
No RFC destionation to source system of service definitions available
Delete Service Definitions (radio button selected).
I did not continue and cancel it as I did not want to delete anything.
I check the Task Processor background job is running at SM host itself.
I managed to get the Maintenance Package job running. However it failed with the following
Error refreshing service definitions from destination SM_SSMCLNT001_BACK
Source and target system may not be identical SSM
The source and target system is the same ==> SSM, will this be an issue? -
End User Role for Service Desk in Solution Manager
Hey,
I am launching the Service Desk functionality for my End Users. One thing that i want to know of is the role that I should assign my user in Solution Manager to access his message. E.g.
I have a user 'A' who creates a message from any system in my landscape:Test, QA, Dev or Production. Now this message reaches in Solution Manager and is assigned to a certain Support Team according to the rules I defined. Now the personnel of Support Team needs some feedback from the end user who created the message. For that the user 'A' has to log into Solution Manager, access his message and enter the details which the Support Team requested.
I want to know that what Role should i give to this user 'A' so that he is able to access ONLY the messages that he created i.e. "Reported by" field showing user 'A'; and is able to view and edit them.
If I give him the role SAP_SUPPDESK_CREATE and SAP_SUPPDESK_DISPLAY, he is just able to see the messages, all of them, but is not authorized to edit any. Please help me out in this matter as i need a solution asap.
Regards,
Bilal NazirHi Nazir,
Create a role and add this t-code manually.
CRM_DNO_MONITOR - Transaction Monitor
This is will definitely solve your problem.
Feel free to revert back.
Thanks and Regards,
Ragu
ERP,
Suzlon Energy Limted, Pune
Extn: 2638
+919370675797
I have no limits for others sky is only a reason -
Error in Solution Manager - Service desk
Dear all Hi,
i need your help please.
i try to create o service desk message from an ERP system -> Solution manager.
when i have SAP_ALL (for the user in the Solution Manager system) the message is created fine
and i can see it and proccess it fine.
when i take off SAP_ALL i get the following error : 'Because of error 513, no message was created in Support Desk System'., even though i have the following authorizations to the user:
SAP_S_RFCACL
SAP_SMWORK_INCIDENT_MAN
SAP_SUPPDESK_CREATE
SAP_SUPPDESK_DISPLAY
SAP_SV_FDB_NOTIF_BC_CREATE
can someone please help ???
thank you in advance.
GeorgePlease find the following points which cause error 513.
1. The client was not completely created by the copy of Client 001.
2. The BCOS_CUST table was not maintained correctly.
3. Missing authorizations for message creation (correct: roles copied from SAP_SV_FDB_NOTIF_BC_CREATE and SAP_SOL_SERVTRANS_CREATE or SAP_SUPPDESK_CREATE).
4. Incorrect action profile assigned for the message type SLF1 (correct: SMSD_ABA_MLDG_SERVICEVORGANG or SLFN0001_STANDARD_DNO).
5. Number ranges are not assigned correctly.
6. The logical system is not defined.
7. Modification of the standard settings of the message type SLF1.
Thanks,
Venkat -
J2EE Service in Solution manager can not be started
Dear Guru,
I have a problem with my Solution manager J2EE Service. The J2EE can not be started. It's returned code is "-11113". My Solution Manager Server Specification is:
- SAP Solution Manager 4.0
- Software component:
SAP_BASIS 700 0013
SAP_ABA 700 0013
PI_BASIS 2006_1_700 0003
ST-PI 2005_1_700 0005
SAP_BW 700 0015
SAP_AP 700 0009
BBPCRM 500 0009
CPRXRPM 400 0009
BI_CONT 703 0007
ST 400 0013
ST-A/PI 01K_CRM560 0000
ST-ICO 150_700 0009
ST-SER 700_2007_1 0004
- OS: Ms Windows 2003 32 Bit
- Database: ORACLE 10.2.0.2.0
- RAM = 1 GByte
The following is the error message when J2EE service is fail to run:
Developer Trace:
trc file: "D:\usr\sap\SMA\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
node name : ID3244050
pid : 7532
system name : SMA
system nr. : 00
started at : Mon Feb 25 16:13:39 2008
arguments :
arg[00] : D:\usr\sap\SMA\DVEBMGS00\exe\jlaunch.exe
arg[01] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[02] : -DSAPINFO=SMA_00_server
arg[03] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=1130
arg[06] : -DSAPSYSTEM=00
arg[07] : -DSAPSYSTEMNAME=SMA
arg[08] : -DSAPMYNAME=BKKT031A_SMA_00
arg[09] : -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 2320] Mon Feb 25 16:13:39 2008
[Thr 2320] *** WARNING => INFO: Unknown property [instance.box.number=SMADVEBMGS00bkkt031a] [jstartxx.c 841]
[Thr 2320] *** WARNING => INFO: Unknown property [instance.en.host=BKKT031A] [jstartxx.c 841]
[Thr 2320] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]
[Thr 2320] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties]
-> ms host : BKKT031A
-> ms port : 3901
-> OS libs : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> Admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
Instance properties
-> ms host : BKKT031A
-> ms port : 3901
-> os libs : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID3244000 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID3244050 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID3244000 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] ID3244050 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
[Thr 2320] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 2320] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1544] JLaunchRequestFunc: Thread 1544 started as listener thread for np messages.
[Thr 8088] WaitSyncSemThread: Thread 8088 started as semaphore monitor thread.
[Thr 2320] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 2320] CPIC (version=700.2006.09.13)
[Thr 2320] [Node: server0] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_14
[Thr 2320] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
JStartupIReadSection: read node properties [ID3244050]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_14
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=192M -XX:PermSize=192M -XX:NewSize=86M -XX:MaxNewSize=86M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
-> java vm version : 1.4.2_14-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> init heap size : 512M
-> root path : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50021
-> shutdown timeout : 120000
[Thr 2320] JLaunchISetDebugMode: set debug mode [no]
[Thr 5408] JLaunchIStartFunc: Thread 5408 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -XX:MaxPermSize=192M
-> arg[ 10]: -XX:PermSize=192M
-> arg[ 11]: -XX:NewSize=86M
-> arg[ 12]: -XX:MaxNewSize=86M
-> arg[ 13]: -XX:+DisableExplicitGC
-> arg[ 14]: -verbose:gc
-> arg[ 15]: -Xloggc:GC.log
-> arg[ 16]: -XX:+PrintGCDetails
-> arg[ 17]: -XX:+PrintGCTimeStamps
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Dsun.io.useCanonCaches=false
-> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 24]: -Dstartup.mode=SAFE
-> arg[ 25]: -Dstartup.action=UPGRADE
-> arg[ 26]: -Dsys.global.dir=D:\usr\sap\SMA\SYS\global
-> arg[ 27]: -Dapplication.home=D:\usr\sap\SMA\DVEBMGS00\exe
-> arg[ 28]: -Djava.class.path=D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 29]: -Djava.library.path=C:\j2sdk1.4.2_14\jre\bin\server;C:\j2sdk1.4.2_14\jre\bin;C:\j2sdk1.4.2_14\bin;D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs;C:\oracle\SMA\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\OpenSSH\bin;C:\Program Files\System Center Operations Manager 2007\;D:\usr\sap\SMA\SYS\exe\uc\NTI386
-> arg[ 30]: -Dmemory.manager=512M
-> arg[ 31]: -Xmx512M
-> arg[ 32]: -Xms512M
-> arg[ 33]: -DLoadBalanceRestricted=no
-> arg[ 34]: -Djstartup.mode=JCONTROL
-> arg[ 35]: -Djstartup.ownProcessId=7532
-> arg[ 36]: -Djstartup.ownHardwareId=Y0571960686
-> arg[ 37]: -Djstartup.whoami=server
-> arg[ 38]: -Djstartup.debuggable=no
-> arg[ 39]: -DSAPINFO=SMA_00_server
-> arg[ 40]: -DSAPSTART=1
-> arg[ 41]: -DCONNECT_PORT=1130
-> arg[ 42]: -DSAPSYSTEM=00
-> arg[ 43]: -DSAPSYSTEMNAME=SMA
-> arg[ 44]: -DSAPMYNAME=BKKT031A_SMA_00
-> arg[ 45]: -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
-> arg[ 46]: -DFRFC_FALLBACK=ON
-> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 48]: -DSAPSTARTUP=1
-> arg[ 49]: -DSAPSYSTEM=00
-> arg[ 50]: -DSAPSYSTEMNAME=SMA
-> arg[ 51]: -DSAPMYNAME=BKKT031A_SMA_00
-> arg[ 52]: -DSAPDBHOST=BKKT031A
-> arg[ 53]: -Dj2ee.dbhost=BKKT031A
Mon Feb 25 16:13:40 2008
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
[Thr 5408] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 7188] Mon Feb 25 16:13:58 2008
[Thr 7188] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 7188] Mon Feb 25 16:14:02 2008
[Thr 7188] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 7188] JLaunchISetClusterId: set cluster id 3244050
[Thr 7188] Mon Feb 25 16:14:03 2008
[Thr 7188] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 7188] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 5436] Mon Feb 25 16:16:34 2008
[Thr 5436] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 5436] **********************************************************************
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 5436] Mon Feb 25 16:16:35 2008
[Thr 5436] JLaunchCloseProgram: good bye (exitcode = -11113)
trc file: "D:\usr\sap\SMA\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
node name : ID3244050
pid : 14568
system name : SMA
system nr. : 00
started at : Mon Feb 25 16:16:46 2008
arguments :
arg[00] : D:\usr\sap\SMA\DVEBMGS00\exe\jlaunch.exe
arg[01] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[02] : -DSAPINFO=SMA_00_server
arg[03] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=1130
arg[06] : -DSAPSYSTEM=00
arg[07] : -DSAPSYSTEMNAME=SMA
arg[08] : -DSAPMYNAME=BKKT031A_SMA_00
arg[09] : -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 14572] Mon Feb 25 16:16:46 2008
[Thr 14572] *** WARNING => INFO: Unknown property [instance.box.number=SMADVEBMGS00bkkt031a] [jstartxx.c 841]
[Thr 14572] *** WARNING => INFO: Unknown property [instance.en.host=BKKT031A] [jstartxx.c 841]
[Thr 14572] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]
[Thr 14572] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties]
-> ms host : BKKT031A
-> ms port : 3901
-> OS libs : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> Admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
Instance properties
-> ms host : BKKT031A
-> ms port : 3901
-> os libs : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID3244000 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID3244050 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID3244000 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] ID3244050 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
[Thr 14572] Mon Feb 25 16:16:47 2008
[Thr 14572] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 14572] JLaunchRequestQueueInit: create pipe listener thread
[Thr 14664] JLaunchRequestFunc: Thread 14664 started as listener thread for np messages.
[Thr 14668] WaitSyncSemThread: Thread 14668 started as semaphore monitor thread.
[Thr 14572] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 14572] CPIC (version=700.2006.09.13)
[Thr 14572] [Node: server0] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_14
[Thr 14572] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
JStartupIReadSection: read node properties [ID3244050]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_14
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=192M -XX:PermSize=192M -XX:NewSize=86M -XX:MaxNewSize=86M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
-> java vm version : 1.4.2_14-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> init heap size : 512M
-> root path : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50021
-> shutdown timeout : 120000
[Thr 14572] JLaunchISetDebugMode: set debug mode [no]
[Thr 14716] JLaunchIStartFunc: Thread 14716 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -XX:MaxPermSize=192M
-> arg[ 10]: -XX:PermSize=192M
-> arg[ 11]: -XX:NewSize=86M
-> arg[ 12]: -XX:MaxNewSize=86M
-> arg[ 13]: -XX:+DisableExplicitGC
-> arg[ 14]: -verbose:gc
-> arg[ 15]: -Xloggc:GC.log
-> arg[ 16]: -XX:+PrintGCDetails
-> arg[ 17]: -XX:+PrintGCTimeStamps
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Dsun.io.useCanonCaches=false
-> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 24]: -Dstartup.mode=SAFE
-> arg[ 25]: -Dstartup.action=UPGRADE
-> arg[ 26]: -Dsys.global.dir=D:\usr\sap\SMA\SYS\global
-> arg[ 27]: -Dapplication.home=D:\usr\sap\SMA\DVEBMGS00\exe
-> arg[ 28]: -Djava.class.path=D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 29]: -Djava.library.path=C:\j2sdk1.4.2_14\jre\bin\server;C:\j2sdk1.4.2_14\jre\bin;C:\j2sdk1.4.2_14\bin;D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs;C:\oracle\SMA\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\OpenSSH\bin;C:\Program Files\System Center Operations Manager 2007\;D:\usr\sap\SMA\SYS\exe\uc\NTI386
-> arg[ 30]: -Dmemory.manager=512M
-> arg[ 31]: -Xmx512M
-> arg[ 32]: -Xms512M
-> arg[ 33]: -DLoadBalanceRestricted=no
-> arg[ 34]: -Djstartup.mode=JCONTROL
-> arg[ 35]: -Djstartup.ownProcessId=14568
-> arg[ 36]: -Djstartup.ownHardwareId=Y0571960686
-> arg[ 37]: -Djstartup.whoami=server
-> arg[ 38]: -Djstartup.debuggable=no
-> arg[ 39]: -DSAPINFO=SMA_00_server
-> arg[ 40]: -DSAPSTART=1
-> arg[ 41]: -DCONNECT_PORT=1130
-> arg[ 42]: -DSAPSYSTEM=00
-> arg[ 43]: -DSAPSYSTEMNAME=SMA
-> arg[ 44]: -DSAPMYNAME=BKKT031A_SMA_00
-> arg[ 45]: -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
-> arg[ 46]: -DFRFC_FALLBACK=ON
-> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 48]: -DSAPSTARTUP=1
-> arg[ 49]: -DSAPSYSTEM=00
-> arg[ 50]: -DSAPSYSTEMNAME=SMA
-> arg[ 51]: -DSAPMYNAME=BKKT031A_SMA_00
-> arg[ 52]: -DSAPDBHOST=BKKT031A
-> arg[ 53]: -Dj2ee.dbhost=BKKT031A
Mon Feb 25 16:16:48 2008
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
[Thr 14716] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 6068] Mon Feb 25 16:16:58 2008
[Thr 6068] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 6068] Mon Feb 25 16:17:01 2008
[Thr 6068] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 6068] JLaunchISetClusterId: set cluster id 3244050
[Thr 6068] Mon Feb 25 16:17:02 2008
[Thr 6068] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 6068] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 14728] Mon Feb 25 16:18:33 2008
[Thr 14728] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 14728] **********************************************************************
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 14728] JLaunchCloseProgram: good bye (exitcode = -11113)
trc file: "D:\usr\sap\SMA\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
node name : ID3244050
pid : 13172
system name : SMA
system nr. : 00
started at : Mon Feb 25 16:18:41 2008
arguments :
arg[00] : D:\usr\sap\SMA\DVEBMGS00\exe\jlaunch.exe
arg[01] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[02] : -DSAPINFO=SMA_00_server
arg[03] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=1130
arg[06] : -DSAPSYSTEM=00
arg[07] : -DSAPSYSTEMNAME=SMA
arg[08] : -DSAPMYNAME=BKKT031A_SMA_00
arg[09] : -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 16204] Mon Feb 25 16:18:41 2008
[Thr 16204] *** WARNING => INFO: Unknown property [instance.box.number=SMADVEBMGS00bkkt031a] [jstartxx.c 841]
[Thr 16204] *** WARNING => INFO: Unknown property [instance.en.host=BKKT031A] [jstartxx.c 841]
[Thr 16204] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]
[Thr 16204] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties]
-> ms host : BKKT031A
-> ms port : 3901
-> OS libs : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> Admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
Instance properties
-> ms host : BKKT031A
-> ms port : 3901
-> os libs : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID3244000 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID3244050 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID3244000 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] ID3244050 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
[Thr 16204] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 16204] JLaunchRequestQueueInit: create pipe listener thread
[Thr 15796] JLaunchRequestFunc: Thread 15796 started as listener thread for np messages.
[Thr 14860] WaitSyncSemThread: Thread 14860 started as semaphore monitor thread.
[Thr 16204] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 16204] CPIC (version=700.2006.09.13)
[Thr 16204] [Node: server0] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_14
[Thr 16204] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
JStartupIReadSection: read node properties [ID3244050]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_14
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=192M -XX:PermSize=192M -XX:NewSize=86M -XX:MaxNewSize=86M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
-> java vm version : 1.4.2_14-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> init heap size : 512M
-> root path : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50021
-> shutdown timeout : 120000
[Thr 16204] JLaunchISetDebugMode: set debug mode [no]
[Thr 16180] JLaunchIStartFunc: Thread 16180 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -XX:MaxPermSize=192M
-> arg[ 10]: -XX:PermSize=192M
-> arg[ 11]: -XX:NewSize=86M
-> arg[ 12]: -XX:MaxNewSize=86M
-> arg[ 13]: -XX:+DisableExplicitGC
-> arg[ 14]: -verbose:gc
-> arg[ 15]: -Xloggc:GC.log
-> arg[ 16]: -XX:+PrintGCDetails
-> arg[ 17]: -XX:+PrintGCTimeStamps
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Dsun.io.useCanonCaches=false
-> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 24]: -Dstartup.mode=SAFE
-> arg[ 25]: -Dstartup.action=UPGRADE
-> arg[ 26]: -Dsys.global.dir=D:\usr\sap\SMA\SYS\global
-> arg[ 27]: -Dapplication.home=D:\usr\sap\SMA\DVEBMGS00\exe
-> arg[ 28]: -Djava.class.path=D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 29]: -Djava.library.path=C:\j2sdk1.4.2_14\jre\bin\server;C:\j2sdk1.4.2_14\jre\bin;C:\j2sdk1.4.2_14\bin;D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs;C:\oracle\SMA\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\OpenSSH\bin;C:\Program Files\System Center Operations Manager 2007\;D:\usr\sap\SMA\SYS\exe\uc\NTI386
-> arg[ 30]: -Dmemory.manager=512M
-> arg[ 31]: -Xmx512M
-> arg[ 32]: -Xms512M
-> arg[ 33]: -DLoadBalanceRestricted=no
-> arg[ 34]: -Djstartup.mode=JCONTROL
-> arg[ 35]: -Djstartup.ownProcessId=13172
-> arg[ 36]: -Djstartup.ownHardwareId=Y0571960686
-> arg[ 37]: -Djstartup.whoami=server
-> arg[ 38]: -Djstartup.debuggable=no
-> arg[ 39]: -DSAPINFO=SMA_00_server
-> arg[ 40]: -DSAPSTART=1
-> arg[ 41]: -DCONNECT_PORT=1130
-> arg[ 42]: -DSAPSYSTEM=00
-> arg[ 43]: -DSAPSYSTEMNAME=SMA
-> arg[ 44]: -DSAPMYNAME=BKKT031A_SMA_00
-> arg[ 45]: -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
-> arg[ 46]: -DFRFC_FALLBACK=ON
-> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 48]: -DSAPSTARTUP=1
-> arg[ 49]: -DSAPSYSTEM=00
-> arg[ 50]: -DSAPSYSTEMNAME=SMA
-> arg[ 51]: -DSAPMYNAME=BKKT031A_SMA_00
-> arg[ 52]: -DSAPDBHOST=BKKT031A
-> arg[ 53]: -Dj2ee.dbhost=BKKT031A
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
[Thr 16180] Mon Feb 25 16:18:42 2008
[Thr 16180] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 15648] Mon Feb 25 16:18:48 2008
[Thr 15648] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 15648] Mon Feb 25 16:18:50 2008
[Thr 15648] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 15648] JLaunchISetClusterId: set cluster id 3244050
[Thr 15648] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 15648] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 14068] Mon Feb 25 16:19:57 2008
[Thr 14068] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 14068] **********************************************************************
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 14068] JLaunchCloseProgram: good bye (exitcode = -11113)
trc file: "D:\usr\sap\SMA\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
node name : ID3244050
pid : 15808
system name : SMA
system nr. : 00
started at : Mon Feb 25 16:20:03 2008
arguments :
arg[00] : D:\usr\sap\SMA\DVEBMGS00\exe\jlaunch.exe
arg[01] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[02] : -DSAPINFO=SMA_00_server
arg[03] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=1130
arg[06] : -DSAPSYSTEM=00
arg[07] : -DSAPSYSTEMNAME=SMA
arg[08] : -DSAPMYNAME=BKKT031A_SMA_00
arg[09] : -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 15880] Mon Feb 25 16:20:03 2008
[Thr 15880] *** WARNING => INFO: Unknown property [instance.box.number=SMADVEBMGS00bkkt031a] [jstartxx.c 841]
[Thr 15880] *** WARNING => INFO: Unknown property [instance.en.host=BKKT031A] [jstartxx.c 841]
[Thr 15880] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]
[Thr 15880] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties]
-> ms host : BKKT031A
-> ms port : 3901
-> OS libs : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> Admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
Instance properties
-> ms host : BKKT031A
-> ms port : 3901
-> os libs : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID3244000 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID3244050 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID3244000 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] ID3244050 : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
[Thr 15880] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 15880] JLaunchRequestQueueInit: create pipe listener thread
[Thr 12672] JLaunchRequestFunc: Thread 12672 started as listener thread for np messages.
[Thr 15460] WaitSyncSemThread: Thread 15460 started as semaphore monitor thread.
[Thr 15880] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 15880] CPIC (version=700.2006.09.13)
[Thr 15880] [Node: server0] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_14
[Thr 15880] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
JStartupIReadSection: read node properties [ID3244050]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_14
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=192M -XX:PermSize=192M -XX:NewSize=86M -XX:MaxNewSize=86M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
-> java vm version : 1.4.2_14-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> init heap size : 512M
-> root path : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50021
-> shutdown timeout : 120000
[Thr 15880] JLaunchISetDebugMode: set debug mode [no]
[Thr 12716] JLaunchIStartFunc: Thread 12716 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -XX:MaxPermSize=192M
-> arg[ 10]: -XX:PermSize=192M
-> arg[ 11]: -XX:NewSize=86M
-> arg[ 12]: -XX:MaxNewSize=86M
-> arg[ 13]: -XX:+DisableExplicitGC
-> arg[ 14]: -verbose:gc
-> arg[ 15]: -Xloggc:GC.log
-> arg[ 16]: -XX:+PrintGCDetails
-> arg[ 17]: -XX:+PrintGCTimeStamps
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Dsun.io.useCanonCaches=false
-> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 24]: -Dstartup.mode=SAFE
-> arg[ 25]: -Dstartup.action=UPGRADE
-> arg[ 26]: -Dsys.global.dir=D:\usr\sap\SMA\SYS\global
-> arg[ 27]: -Dapplication.home=D:\usr\sap\SMA\DVEBMGS00\exe
-> arg[ 28]: -Djava.class.path=D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 29]: -Djava.library.path=C:\j2sdk1.4.2_14\jre\bin\server;C:\j2sdk1.4.2_14\jre\bin;C:\j2sdk1.4.2_14\bin;D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs;C:\oracle\SMA\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\OpenSSH\bin;C:\Program Files\System Center Operations Manager 2007\;D:\usr\sap\SMA\SYS\exe\uc\NTI386
-> arg[ 30]: -Dmemory.manager=512M
-> arg[ 31]: -Xmx512M
-> arg[ 32]: -Xms512M
-> arg[ 33]: -DLoadBalanceRestricted=no
-> arg[ 34]: -Djstartup.mode=JCONTROL
-> arg[ 35]: -Djstartup.ownProcessId=15808
-> arg[ 36]: -Djstartup.ownHardwareId=Y0571960686
-> arg[ 37]: -Djstartup.whoami=server
-> arg[ 38]: -Djstartup.debuggable=no
-> arg[ 39]: -DSAPINFO=SMA_00_server
-> arg[ 40]: -DSAPSTART=1
-> arg[ 41]: -DCONNECT_PORT=1130
-> arg[ 42]: -DSAPSYSTEM=00
-> arg[ 43]: -DSAPSYSTEMNAME=SMA
-> arg[ 44]: -DSAPMYNAME=BKKT031A_SMA_00
-> arg[ 45]: -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
-> arg[ 46]: -DFRFC_FALLBACK=ON
-> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 48]: -DSAPSTARTUP=1
-> arg[ 49]: -DSAPSYSTEM=00
-> arg[ 50]: -DSAPSYSTEMNAME=SMA
-> arg[ 51]: -DSAPMYNAME=BKKT031A_SMA_00
-> arg[ 52]: -DSAPDBHOST=BKKT031A
-> arg[ 53]: -Dj2ee.dbhost=BKKT031A
Mon Feb 25 16:20:04 2008
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
[Thr 12716] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 15780] Mon Feb 25 16:20:09 2008
[Thr 15780] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 15780] Mon Feb 25 16:20:11 2008
[Thr 15780] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 15780] JLaunchISetClusterId: set cluster id 3244050
[Thr 15780] Mon Feb 25 16:20:12 2008
[Thr 15780] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 15780] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 4828] Mon Feb 25 16:21:17 2008
[Thr 4828] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 4828] **********************************************************************
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 4828] JLaunchCloseProgram: good bye (exitcode = -11113)
trc file: "D:\usr\sap\SMA\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
node name : ID3244050
pid : 7528
system name : SMA
system nr. : 00
started at : Mon Feb 25 16:27:52 2008
arguments :
arg[00] : D:\usr\sap\SMA\DVEBMGS00\exe\jlaunch.exe
arg[01] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[02] : -DSAPINFO=SMA_00_server
arg[03] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=1130
arg[06] : -DSAPSYSTEM=00
arg[07] : -DSAPSYSTEMNAME=SMA
arg[08] : -DSAPMYNAME=BKKT031A_SMA_00
arg[09] : -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 7060] Mon Feb 25 16:27:52 2008
[Thr 7060] *** WARNING => INFO: Unknown property [instance.box.number=SMADVEBMGS00bkkt031a] [jstartxx.c 841]
[Thr 7060] *** WARNING => INFO: Unknown property [instance.en.host=BKKT031A] [jstartxx.c 841]
[Thr 7060] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]
[Thr 7060] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties]
-> ms host : BKKT031A
-> ms port : 3901
-> OS libs : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> Admin URL :
-> run mode : safe
-> run action : UPGRADE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
Instance properties
-> ms host : BKKT031A
-> ms port : 3901
-> os libs : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
-> admin URL :
-> run mode : safe
-> run action : UPGRADEHi Bruyneel,
I've solved the problem. I think while doing kernel or component upgrade SAP clear all configuration that connected from ABAP and JAVA. You can re-config from config tool.
1. Goto \usr\sap\<SID>\<SIst.Num>\j2ee\configtool and execute go.bat
2. cluster-data -> global server configuration -> services -> com.sap.security.core.ume.service.
3. Configure:
ume.login.guest_user.uniquefields with J2EE_GUEST, and make sure the user is already exist in ABAP
ume.persistence.data_source_configuration dataSourceConfiguration_abap.xml
ume.r3.connection.master.ashost
ume.r3.connection.master.client
ume.r3.connection.master.passwd : with SAPJSF user's password
ume.r3.connection.master.sysnr
ume.r3.connection.master.user : SAPJSF User
Refer for this link for help: http://help.sap.com/saphelp_nw04s/helpdata/en/20/361941edd5ef23e10000000a155106/frameset.htm
Thanks & Best Regards,
Yan -
How to Use Solution Manager to collect Status Reports from Consultants
Hi,
I am planning to use Solution Manager for collecting the weekly status reports from my consultants and maintain it as a repository . Please let me know the best way of doing this in SOLMAN. There should be mailing options too.
BR,
RajHi Rajasan,
to be able to meet this requirement, you need to set up plan working load in admin tab for your resource, they need to update actual data based on the work completion, you will get status of work,
if you require email, you need to set-up scot, then develop a program with execution scheduling
please check and revert
Anil -
Solution Manager prepared for the Remote Service Delivery?
In preparation of GoingLive Session, we received a mail with some questions. Among them the following:
Is your Solution Manager prepared for the Remote Service Delivery? Yes/No
Is the solution transferred to SAP?: Yes/No
What does the first question mean? what should be done to prepare the Solman for session delivery?
How do I check if the solution is transferred to SAP?
Thanks a lot,
DinoHello Dino,
The SAP Solution Manager is a platform for the delivery of services for the following areas:
● Risk minimization
● Optimization of SAP solutions
● Knowledge transfer
Services in the SAP Solution Manager are services which help you to monitor and optimize the performance and availibility of your system landscapes and minimize your system operation risks.
You can have the support services performed by SAP or perform them yourself:
● Remote Services
SAP experts deliver this service type via a remote connection (SAP Safeguarding Services, e.g. SAP GoingLive Check).
For checking whether solution manager is prepared for remote service delivery u need to check the following.
Prerequisites
You have:
● created a solution.
● set-up a connection to the SAP Service Marketplace (Explorer).
Procedure
1. Choose the transaction SOLUTION_MANAGER.
2. Choose Delivery of SAP Services ® Service Plan, in Operations.
3. Choose Order Service from SAP.
You go to the Service Catalog.
4. Choose the link to the service.
The system goes to the catalog entry of the service, in the SAP Service Marketplace.
5. Follow the procedure described in the SAP Service Marketplace.
=============================================
Solution transfered to SAP means that the u have done the configuration, testing and validation of the SAP system components and then transfered this to the satellite systems connected to Solman. Please note that solman is the central point of access for supporting implementation activities and the satellite systems are SAP systems comnected to solman in the landscape.
Hope this helps. Please assign points and let me know if u need anything specific.
Rgds
Manish -
Solution Manager Service Management
Hi ,
I am working on solution manager, Can any one send me the solution manager <b>service management</b> document for my referance,it would be greatful for me.
Pls do the needful ASAP.
Thanks,
Gopinath.Download all documentation yourself at
http://service.sap.com/solutionmanager
Everything you need is there.
Markus -
Difference between Solution manager and ASAP
Hi All,
Can anyone tell me what's the difference between SAP solution manager and ASAP?
Regards
SarojASAP stands For Accelerated SAP........its a SAP implementation methodology. It consists of Five phases---
1. Project Preparation
2. Business Blueprint
3. Realization phase
4. Final preparation phase
5. Go live and Support
For Solution manager u can follow this link:
http://www.sap.com/services/pdf/BWP_SB_SAP_Solution_Manager.pdf
ASAP and Solution Manager are tools used for managing SAP implementation and roll out project. Both supports sevral stages of the project as mention by Raj.
The main Difference between three tools (ASAP, VSAP and Solution Manager) are as follow:
ASAP:
- Offline CD set with tools, content and a methodology for component-based implementation projects
VSAP:
- Offline CD set with tools, content and methodologies for Evaluation, Implementation and Continuous Business Improvement
- ASAP CD set is used as a tool platform. ASAP content is included to cover the implementation phase
Solution Manager:
- Onsite platform to support key implementation actitivities
- Including key ASAP concepts and tool features
- Enhanced concepts to encompass the specifics of mySAP.com implementations
- Integrated platform to support Implementation and operation of mySAP.com
- Solution Manager is server based tool.
More informaiton you can find from the following links:
ValueSAP : https://www.service.sap.com/valuesapupdates
Solution Manager: http://service.sap.com/solutionmanager
some documents what is the duty of asap and solution manager i think with u can understand the difference.
asap means,
ASAP
ASAP stands for Accelerated SAP. Its purpose is to help design SAP implementation in the most efficient
manner possible. Its goal is to effectively optimize time, people, quality and other resources, using a proven
methodology to implementation.
ASAP focuses on tools and training, wrapped up in a five-phase process oriented roadmap for guiding
implementation.
The road map is composed of five well-known consecutive phases:
Phase 1 Project Preparation
Phase 2 Business Blueprint
Phase 3 Realization
Phase 4 Final Preparation
Phase 5 Go-Live and support
In today's post we will discuss the first phase.
Phase 1 : Project Preparation
Phase 1 initiates with a retrieval of information and resources. It is an important time to assemble the
necessary components for the implementation. Some important milestones that need to be accomplished
for phase 1 include
Obtaining senior-level management/stakeholder support
identifying clear project objectives
architecting an efficient decision-making process
creating an environment suitable for change and re-engineering
building a qualified and capable project team.
Senior level management support:
One of the most important milestones with phase 1 of ASAP is the full agreement and cooperation of the
important company decision-makers - key stakeholders and others. Their backing and support is crucial for a
successful implementation.
Clear project objectives:
be concise in defining what your objectives and expectations are for this venture. Vague or unclear notions of
what you hope to obtain with SAP will handicap the implementation process. Also make sure that your
expectations are reasonable considering your company's resources. It is essential to have clearly defined
ideas, goals and project plans devised before moving forward.
An efficient decision making process:
One obstacle that often stalls implementation is a poorly constructed decision-making process. Before
embarking on this venture, individuals need to be clearly identified. Decide now who is responsible for
different decisions along the way. From day one, the implementation decision makers and project leaders
from each area must be aware of the onus placed on them to return good decisions quickly.
Environment suitable for change and re engineering:
Your team must be willing to accept that, along with new SAP software, things are going to change, the
business will change, and information technology enabling the business will change as well. By
implementing SAP, you will essentially redesign your current practices to model more efficient or predefined
best business practices as espoused by SAP. Resistance to this change will impede the progress of your
implementation.
Building a qualified project team:
Probably the most important milestone early in assembling a project team for the implementation. If you are
implementing the materials management and plant maintenance modules, you need to include people from
both of these departments. The team should also represent management as well as non management or
"functional" personnel. Sometimes management is less aware of the day-to-day functions of an organization,
including how implementing SAP will tactically influence those function
ASAP- Second Phase- Business Blueprint
SAP has defined a business blueprint phase to help extract pertinent information about your company that is
necessary for implementation. These blueprints are in the form of questionnaires that are designed to probe
for information that uncovers how your company does business. As such, they also serve to document the
implementation. Each business blueprint document essentially outlines your future business processes and
business requirements. The kinds of questions asked are germane to the particular business function, as
seen in the following sample questions:
1) What information do you capture on a purchase order?
2) What information is required to complete a purchase order?
Accelerated SAP question and answer database:
The question and answer database (QADB) is a simple although aging tool designed to facilitate the creation
and maintenance of your business blueprint. This database stores the questions and the answers and
serves as the heart of your blue print. Customers are provided with a customer input template for each
application that collects the data. The question and answer format is standard across applications to
facilitate easier use by the project team.
Issues database:
Another tool used in the blueprinting phase is the issues database. This database stores any open concerns
and pending issues that relate to the implementation. Centrally storing this information assists in gathering
and then managing issues to resolution, so that important matters do not fall through the cracks. You can
then track the issues in database, assign them to team members, and update the database accordingly.
ASAP Phase- 3 - Realization:
With the completion of the business in phase 2, "functional" experts are now ready to begin configuring SAP.
The Realization phase is broken in to two parts.
1) Your SAP consulting team helps you configure your baseline system, called the baseline configuration.
2) Your implementation project team fine-tunes that system to meet all your business and process
requirements as part of the fine tuning configuration.
The initial configuration completed during the base line configuration is based on the information that you
provided in your blueprint document. The remaining approximately 20% of your configuration that was not
tackled during the baseline configuration is completed during the fine tuning configuration. Fine tuning
usually deals with the exceptions that are not covered in baseline configuration. This final bit of tweaking
represents the work necessary to fit your special needs.
Configuration Testing:
With the help of your SAP consulting team, you segregate your business processes into cycles of related
business flows. The cycles serve as independent units that enable you to test specific parts of the business
process. You can also work through configuring the SAP implementation guide (IMG). A tool used to assist
you in configuring your SAP system in a step-by-step manner.
Knowledge Transfer:
As the configuration phase comes to a close, it becomes necessary for the Project team to be self-sufficient
in their knowledge of the configuration of your SAP system. Knowledge transfer to the configuration team
tasked with system maintenance (that is, maintenance of the business processes after Go-live) needs to be
completed at this time.
In addition, the end users tasked with actually using the system for day-to-day business purposes must be
trained.
ASAP Methodology - Phase 4 - Final Preparation:
As phase 3 merges into phase 4, you should find yourselves not only in the midst of SAP
training, but also in the midst of rigorous functional and stress testing. Phase 4 also
concentrates on the fine tuning of your configuration before Go-live and more importantly, the
migration of data from your old system or systems to SAP.
Workload testing (including peak volume, daily load, and other forms of stress testing), and
integration or functional testing are conducted to ensure the accuracy of your data and the
stability of your SAP system. Because you should have begun testing back in phase 2, you do
not have too far to go until Go-live. Now is an important time to perform preventative
maintenance checks to ensure optimal performance at your SAP system.
At the conclusion of phase 4, take time to plan and document a Go-live strategy. Preparation for
Go-live means preparing for your end-users questions as they start actively working on the new
SAP system.
ASAP - Phase 5 - Go-live and Support:
The Go-live milestone is itself is easy to achieve; a smooth and uneventful Go-live is another
matter altogether. Preparation is the key, including attention to what-if scenarios related not only
to the individual business processes deployed but also to the functioning of technology
underpinning these business processes and preparation for ongoing support, including
maintenance contracts and documented processes and procedures are essential
solutionmanager means,
SAP Solution Manager
Purpose
The SAP Solution Manager supports you throughout the entire lifecycle of your solutions, from the Business Blueprint thru configuration to production operation. It provides central access to tools methods and preconfigured content, that you can use during the evaluation, implementation, and productive operation of your systems.
Features
Implementation of the mySAP Business Suite
All phases of the implementation project (Business Blueprint, Configuration) are performed centrally in the Solution-Manager system.
Central project documentation repository in the Solution Manager
Integrated Project Administration allows you to manage planning schedules, human resources and other project data.
Customizing Synchronization
The Customizing Scout, with which you can compare customizing in various SAP components, e.g. an ERP system with SAP MDM
The Customizing Distribution, with which you can synchronize customizing in various SAP components.
Test
You can use the Test Workbench to organize and perform tests at the end of a project phase.
Reuse of the project structure for process-oriented tests
Global rollout
Integrated authoring environment, with which customers and partners can create their own templates, which they can reuse in subsidiaries, e.g. in a global rollout
E-Learning management
Creation of training material and learning maps (computer-supported self-tuition courses) to train end users after the implementation of new functions
Solution Monitoring
Central system administration
Analyze your system landscape with Service Level Reporting
System monitoring in real time
Business Process Monitoring
Services
Access to programs and Services, which help you to monitor and optimize the performance and availability of your system landscapes, and minimize your operational system risks
Service Desk
Solution support with workflow to create and handle problem messages
Change Management
Management of change requests, with workflow for the monitoring and audit of changes and transports in your system landscape, with the Change Request Management.
See also:
Projects
Solution Monitoring
SAP Solution Manager Roles
Authorization Concept
Project Authorizations
The following composite roles contain the authorizations required for the tasks to be performed in a project:
○ Project Leader
○ Application Consultant
○ Development Consultant
○ Technical Consultant
There are individual roles for Roadmap administration.
Production Authorizations
Production authorizations are in individual roles for the functions:
○ Solution Directory
○ Solution Monitoring
○ Service Data Control Center
○ Service Desk
○ Corporate Functionality
○ Solution Manager Diagnostics
○ Solution Reporting
Use
Adjust the SAP Solution Manager roles to your requirements.
Overview of Roles in Solution Manager
If you use trusting-trusted RFC connections, assign the authorization profile S_RFCACL to the user, as well.
Scenario Role
Implementation and Distribution SAP_SOL_PM_COMP
SAP_SOL_AC_COMP
SAP_SOL_BC_COMP
SAP_SOL_TC_COMP
SAP_SOL_RO_COMP
SAP_SOL_RE_COMP
SAP_SOL_LEARNING_MAP_DIS
SAP_DMDDEF_DIS
Implementation and Distribution (Roadmaps) SAP_RMDEF_RMAUTH_EXE
SAP_RMDEF_RMAUTH_DIS
Implementation and Distribution (E-Learning Management) SAP_SOL_TRAINING_EDIT
Service Desk (Service Desk) SAP_SUPPDESK_ADMIN
SAP_SUPPDESK_PROCESS
SAP_SUPPDESK_CREATE
SAP_SUPPDESK_DISPLAY
Service Desk (Corporate Functionality) SAP_SUPPCF_ADMIN
SAP_SUPPCF_CREATE
SAP_SUPPCF_PROCESS
Service Desk (Issue Tracking) SAP_SV_SOLUTION_MANAGER
SAP_SV_SOLUTION_MANAGER_DISP
SAP_SUPPDESK_ADMIN
SAP_SUPPDESK_PROCESS
SAP_SUPPDESK_DISPLAY
Change Request Management (Schedule Manager; Service Desk, cProjects)
SAP_CM_CHANGE_MANAGER
SAP_CM_DEVELOPER_COMP
SAP_CM_TESTER_COMP
SAP_CM_OPERATOR_COMP
SAP_CM_PRODUCTIONMANAGER_COMP
SAP_SOCM_REQUESTER
SAP_CM_ADMINISTRATOR_COMP
Solution Monitoring
(Service Data Control
Center)
SAP_SDCCN_ALL
SAP_SDCCN_DIS
SAP_SDCCN_EXE
Solution Monitoring
(Solution Directory)
SAP_SOLMAN_DIRECTORY_ADMIN
SAP_SOLMAN_DIRECTORY_EDIT
SAP_SOLMAN_DIRECTORY_DISPLAY
Solution Monitoring
(Operations)
SAP_SV_SOLUTION_MANAGER
SAP_SV_SOLUTION_MANAGER_DISP
SAP_SETUP_DSWP
SAP_SETUP_DSWP_SLR
SAP_SETUP_DSWP_SM
SAP_SETUP_DSWP_BPM
SAP_SETUP_DSWP_CSA
SAP_OP_DSWP
SAP_OP_DSWP_SLR
SAP_OP_DSWP_SM
SAP_OP_DSWP_EWA
SAP_OP_DSWP_BPM
SAP_OP_DSWP_CSA
Solution Reporting SAP_SOL_REP_ADMIN
SAP_SOL_REP_DISP
Solution Manager Diagnostics SAP_SMDIAG_WIZARD
SAP_SMDIAG_TEMPLATE
Cf.:
● Overview of Roles and Profiles in Satellite Systems
● SAP Solution Manager 4.0 configuration guide
● SAP note 834534
● SAP note 803142
Overview of Roles and Profiles in the Satellite Systems
Use the profiles below for SAP R/3 Release before SAP Web Application Server 6.10. Use the profiles below from SAP R/3 Release SAP Web Application Server 6.10.
If you use a trusting-trusted RFC connection, assign the authorization profile S_RFCACL to the user, as well.
Scenario Roles (Release > 6.10) Profile ( SAP_S_CUS_CMP S_CUS_CMP Data read access
SAP_S_CMSREG S_CMSREG Central system repository data
SAP_S_BDLSM_READ S_BDLSM_READ SDCCN data
Adjust Roles and Profiles
Before you assign SAP standard roles and profiles to users, copy and specify them.
SAP delivers roles and profiles with default values. If they are missing, you must set the values in the authorization objects yourself. Proceed as follows:
1. Load the roles/profiles from client 000 into your target client. You can:
○ Transport client 000 into your target client (roles and profiles)
○ Upload und Download (for roles in transaction PFCG)
○ RFC connection in transaction PFCG (for roles; menu path: MENU ® READ FROM OTHER SYSTEM WITH RFC). In this case, you must have set-up the RFC connection (transaction SM59).
2. Copy the roles/profiles into your namespace.
a. Choose Role Maintenance (transaction PFCG).
b. Enter a role name and choose Copy Role.
c. Enter the name of the new role in the To Role field.
d. Choose Copy All.
e. Save.
3. Complete missing values in the authorization objects.
a. Choose the Authorizations tab.
b. Choose ChangeAuthorization Data.
c. Enter your own values for the authorization objects, or double-click on the yellow traffic light.
The authorization objects appear with a green traffic light.
d.
When you double-click on the yellow traffic light, the value * appears. This grants full authorization for this field of the authorization object.
e. Save.
f. Generate the authorization profile.
4. Assign the role to users.
a. Choose the Users tab.
b. Enter the user names.
c. Choose User Adjustment.
d. Save.
You can also assign the roles to the users, in the user maintenance (transaction SU01).
e.
Project Authorization
Roles
The roles in the SAP Solution Manager are composite roles, which contain individual roles, which in turn contain authorizations for individual functions, e.g. for the Business Blueprint.
The following composite roles contain the central authorizations which they require for projects, and can be tailored to suit individual projects:
● Project leaders are responsible for organizing and planning the project, and monitoring costs and deadlines.
● Application consultants consultants are responsible for business content and the documentation of operational activities. This composite role has limited authorization and is intended for project members who need to be adjusted individually.
● Development consultants are responsible for the development of customer-specific programs and authorizations.
● Technical consultants are responsible for installing systems and providing technical support to users.
● Display user/Read only : contains SAP Solution Manager display/read only authorization.
● Read authorization depending on status in Document Management : only contains read authorization per status in Knowledge Warehouse Document Management
See also:
● Solution Manager Roles Overview
● Overview of Roles and Profiles in Satellite Systems
● SAP Solution Manager 4.0 configuration guide
● SAP note 834534 (Roles in the Solution Manager)
● SAP note 803142 (Roles in Satellite Systems)
Project Manager
Technical name: SAP_SOL_PM_COMP
Tasks
Project managers are responsible for the realization of the desired project results and the daily management of the project. They anticipate deviations from the project direction and carry out the necessary corrective measures immediately. Project managers should also understand the integration of the business processes within the enterprise.
Project managers are also members of the steering committee. They have decision-making authority in matters concerning the program and budget. He forwards strategic questions to the sponsor in order to make joint decisions.
Activities in SAP Solution Manager
The main responsibilities of the project manager include:
Organizing the entire project
Developing strategies and procedures for an efficient SAP implementation
Developing and maintaining the time schedule for the implementation project
Finalizing and managing the project scope, budget and deadlines in accordance with the approved plans
Assigning and managing resources
Monitoring project progress on a weekly basis
Carrying out evaluations and analyses
Carrying out a formal review at the end of each phase
Clarifying open issues in good time
Reporting regularly to the review committee on the progress and status of the project
Representing the project internally and externally
Giving status updates to the whole project team
Project managers can also copy content from a ValueSAP Edition 2 project into an SAP Solution Manager project. See the migration tool documentation.
Notes on Tailoring
If you require additional authorization, you can use the role SAP_BC_CUS_ADMIN: It contains authorization for the administration of customizing projects in the component systems.
The SAP Solution Manager configuration guide contains further information about authorizations in the component systems.
Integration
The project manager defines the content and the time frame of an implementation project, manages resources and monitors project progress. The application consultant reports to him and supports him in an administrative function.
Application Consultant
Technical name: SAP_SOL_AC_COMP
Tasks
Application consultants are responsible for making sure that the Business Blueprint and software configuration are tailored to the business processes and that analysis and report requirements are fulfilled. They use their knowledge of proven business procedures to support them in these tasks. Application consultants also function as advisers and work closely with the rest of the project team.
They also work in close cooperation with legacy system experts, when extraction of legacy data is necessary.
Activities in SAP Solution Manager
The main responsibilities of the application consultant include:
Supporting definition and modeling of business processes
Checking how the business model works with the SAP products
Configuring the software to suit the required business processes and to meet analysis and report requirements
Determining the global and local standardization requirements
Determining requirements for organizational change in the enterprise
Supporting knowledge transfer to other project team members
Supporting organization and performance of tests
Defining requirements for authorization profiles and access authorizations
Analyzing statistical performance and passing on recommendations for improvement to support
Creating and developing data solutions and strategies to meet the requirements of the corresponding SAP component (for example, APO, BW, CRM)
Creating end user training materials for the new functions
The application consultant is not responsible for:
The technical implementation of the solution
The programming of interfaces and other developments
Recurring problems with the quality of data (problems with data quality should be passed on to the project manager)
Notes on Tailoring
This role only contains basic functions. The following roles are available for additional authorizations:
SAP_BC_CUS_CUSTOMIZER contains authorizations for working with IMG activities.
The following role is useful for the application components:
SAP_BC_CUS_CUSTOMIZER
Integration
Application consultants are responsible for the development of business content and the documentation of operative activities in accordance with the appropriate standards. The development consultant develops customer-specific programs and their authorizations.
Development Consultant
Technical name: SAP_SOL_BC_COMP
Tasks
Development consultants work with the project manager and the application consultant on the planning and organization of the authorization concept. They also perform developmental tasks and customer-specific developments.
Activities in SAP Solution Manager
The main responsibilities of the development consultant include:
Organizing authorizations
Developing ABAP programs, for example, interfaces, forms, or modifications
Working with the ABAP Workbench
Notes on Tailoring
The following roles are available for additional authorizations:
SAP_BC_DWB_ABAPDEVELOPER contains authorization for implementing new applications and enhancements and for changing and modifying standard applications using the tools and services provided in the ABAP Workbench.
SAP_BC_TRANSPORT_ADMINISTRATOR contains all authorizations for the Change and Transport System
Integration
Development consultants work for the project manager and the application consultant and carry out programming tasks, in contrast to technical consultants who act as system administrators and are responsible for installing systems and providing technical support to users.
Technical Consultant
Technical name: SAP_SOL_TC_COMP
Tasks
Technical consultants plan the technical requirements for a project with the project manager and the manager of the technical team and then carry out the required technical tasks in the system.
Depending on the scope and complexity of the implementation, technical consultants may work in several areas, for example, system administration, database administration, network administration, operating system administration, development of cross-application components, or ABAP development.
For international projects, technical consultants also manage consultancy in the following areas:
Country-specific business requirements and country-specific SAP software requirements
Language-specific or codepage-specific requirements
Time-zone issues
Activities in SAP Solution Manager
The main responsibilities of the technical consultant include:
Setting up and installing the system landscape
Managing the system landscape and the corresponding transport landscape
Providing support and advice in all technical questions during an implementation project
Giving daily updates on the technical direction of the project including communicating deviations in the project
Developing and realizing the Cutover Plan before going live
Communicating effectively with the business process team
Transferring knowledge effectively to employees in system administration
In order to be able to carry out these tasks, the technical consultant should meet the following requirements:
A sound knowledge in the areas of databases, networks, programming and Internet technology
A sound knowledge of the SAP solutions
Notes on Tailoring
The following roles are available for additional authorizations:
SAP_BC_RRR_SAA_ADMIN provides the authorization for executing all the tasks in the System Administration Assistant.
Integration
The technical consultant acts as a system administrator and is responsible for installing systems and providing technical support to users, in contrast to the basis consultant who works under the instruction of the project manager and the application consultant and carries out programming tasks.
Read Authorization by Document Status
Technical name:
Use the specified individual role to:
● display business process scenarios, business processes steps, etc. of your solution, in the Solution Directory.
Integration
Use the Solution Monitoring role SAP_SV_SOLUTION_MONITORING_DISP to display the Solution Directory and sessions in Solution Monitoring.
Adjustment
Adjust Roles and Profiles
Solution Monitoring Roles
Tasks
Authorizations specified for the Solution Monitoring in the SAP Solution Manager:
for the Solution Monitorin sessions, classified by the areas Operations Setup and Operations
general individual role to display all sessions
Display all Sessions
general individual role to edit all sessions
Edit all Sessions
Activities
Authorizations are assigned to the roles. Specify user access to the session. There are the following authorizations:
A The user with the role has full authorization for the transaction or session.
D The user with the role can call the transaction or session in display mode.
N The user with the role has no authorization for the transaction or session.
Operations Setup session authorizations
Individual role Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_SETUP_DSWP A A A A
SAP_SETUP_DSWP_SLR A N N N
SAP_SETUP_DSWP_SM N A N N
SAP_SETUP_DSWP_CSA N N A N
SAP_SETUP_DSWP_BPM N N N A
Operations session authorizations
Individual role Early Watch Alert Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_OP_DSWP A A A A A
SAP_OP_DSWP_EWA A N N N N
SAP_OP_DSWP_SLR D A N N N
SAP_OP_DSWP_SM N N A (1) N N
SAP_OP_DSWP_CSA N N N A (1) N
SAP_OP_DSWP_BPM N N N N A
SAP_SV_SOLUTION_MANAGER_DISP session authorization
Individual role Early Watch Alert Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_SV_SOLUTION_ MANAGER_DISP D D D D D
SAP_SV_SOLUTION_MANAGER session authorization
Individual role Early Watch Alert Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_SV_SOLUTION_ MANAGER A A A A A
(1) from Release 3.20 SP02
Cf.:
Overview of Roles and Profiles
SAP Solution Manager 3.2configuration guide
SAP note 625773
Notes on Tailoring
You can use and combine the individual Solution Monitoring roles individually, according to your requirements.
Special authorizations for specific checks in individual sessions, are described in the online documentation of the sessions:
See also:
Set-Up Central System Administration
Using business process monitoring
Integration
If you need authorization for specific areas in the SAP Solution Manager, in addition to the authorizations for Solution Monitoring, use the associated individual roles with the specific authorizations:
Change Request Management
Service Desk
Service Data Control Centre
Solution Directory
General Administration and Display Authorization
Technical name: SAP_SV_SOLUTION_MANAGER
Technical name: SAP_SV_SOLUTION_MANAGER_DISP
Tasks
Authorizations are assigned to the roles. Specify user access to the session. The following authorizations are available for your project:
A The user with the role has full authorization for the transaction or session.
D The user with the role can call the transaction or session in display mode.
N The user with the role has no authorization for the transaction or session.
Activities in
Both individual roles have full authorization for the sessions in their areas.
If you only assign one of the roles to a user, the system only offers the user this area in the system interface.
They have display authorization for other transactions, according to the requirements of the session types:
■ SDCCN (Service Data Control Centre) for SAP EarlyWatch Alert and Service Level Reporting
■ SOLMAN_DIRECTORY (Solution Directory) for business process monitoring
Special authorization objects
Authorization Object Activity Meaning
D_SOL_VIEW 20 (Operations) Determines which area can be processed and displayed in the SAP Solution Manager.
D_SOLMANBU A (Bundle ID) Restricts processing by sessions.
■ SDCCN (Service Data Control Centre) for Service Level Reporting
■ SOLMAN DIRECTORY (Solution Directory) for business process monitoring
Special authorization objects
Authorization Object Activity Meaning
D_SOL_VIEW 10 (Operations Setup) Determines which area can be processed and displayed in the SAP Solution Manager.
D_SOLMANBU A Restricts processing by sessions.
Activities in the session type roles
●
Functional roles
Role Technical name Bundle ID Further explanation
Operations Setup
Service Level Reporting SAP_SETUP_DSWP_SLR EWA_CUST Additional display authorization for the transaction SDCCN (Service Data Control Centre)
System monitoring SAP_ SETUP DSWPSM SOL_MON Additional authorization to call the Solution Manager Diagnostics wizard
Central System Administration SAP_ SETUP_DSWP_CSA SOL_CSA Authorization object S_SAA_ADMI controls authorizations for customizing
checks.
Business process monitoring SAP_SETUP_DSWP_BPM BPM_JOBM
CP_BPM
CP_BPM_R
SOL_BPMO
Additional display authorization for the Solution Directory
Operations
SAP EarlyWatch Alert SAP_OP_DSWP_EWA EW_ALERT Additional full authorization for the transaction SDCCN (Service Data Control Centre)
Service Level Reporting SAP_OP_DSWP_SLR EW_CONS Additional display authorization for the transaction SDCCN (Service Data Control Centre)
Central system
administration
SAP_OP_DSWP_CSA SOL_CSA
System
monitoring
SAP_OP_DSWP_SM SOL_MON Additional authorization to call the Solution Manager Diagnostics wizard
Business process
monitoring
SAP_OP_DSWP_BPM BPM_JOBM
CP_BPM_R
SOL_BPMO
Additional display authorization for the Solution Directory
■
Adjustment
You can adjust the roles to your requirements.
If you also need authorization to display the Business Process MONITORING session, as well as the functional role for Service Level reporting in Operations , to check the business processes for the Service Level report, you can:
i. copy the authorization object D_SOLMANBU into the role and adjust it to your requirements (activity: 1; bundle ID: BPM_JOBM; CP_BPM_R; SOL_BPMO)
ii. give the user the role and adjust the authorization object D_SOLMANBU to your requirements (activity 1).
Integration
You can combine the functional roles with other roles in the area:
● Service Desk
● Change Management
●
If you want to create a Service Desk message from a Business Process MONITORING session, you need the role for the user in a message system , as well as the functional role for business process monitoring .
The online documentation for the sessions describes the scenarios in more detail.
Solution Reporting Roles
Technical name: SAP_SOL_REP_ADMIN
Technical name: SAP_SOL_REP_DISP
Tasks
The individual roles administer and display Solution Reporting.
Activities in
Tasks
The specified role sets up service connections to SAP.
Adjustment
Adjust Roles and Profiles
Simple way to differentiate is ASAP is a methodology for SAP Project Implementation where as Solution Manager is a document repository to store the documentation that u will create during all phases of the project.
Maybe you are looking for
-
"not all variables bound" error in a BI publisher report
Hi, I'm getting a "ORA-01008: not all variables bound" error in my BI publisher report. The SQL query looks like this: select ...--a bunch of rows from tbl1,tbl2,...,tblk where ...--and conditions performing inner joins and (('*') in &p_SomeParameter
-
Hi All, I have a requirement that i need to execute query having dynamic number of columns using Ref Cursor e.g. v_string := 'PO_NUMBER , ORG_ID' ; v_query := 'SELECT '|| v_string || 'FROM table_name'; Can someone please quide me how to define Type d
-
My friend have a macbook pro and she have the option to make her keyboard shine to see the letters in the dark Do I have that option on my simple macbook?and if yes...how can I reach it? thanks!!!!
-
Batch job to print GRs from a single plant
We have a requirement to set up a daily batch job to print all GRs for one of our plants. The others will be printed as they currently are (immediately when saving) but for one plant we want to delay all printing until a certain time of day and then
-
Lightroom 3 - Flickr Publish Bug
I am experiencing an issue where when I publish images to Flickr they immediately show up as "Modified Photos to Re-Publish" and will not ever move to the "Published" section even though I have not changed a thing. Anyone have any ideas as to what I