Abap+java OR java only for EP6.0
abap+java OR java only for EP6.0
Hi charles,
you question is not clear.
If I correctly understood you are you asking the skills required to work on EP6.0?
If it is so I cam more java skills required and if you want to develop customized iview you may require bit of ABAP too.
Hope it helps.
Regards,
B.Guru Subramaian
Similar Messages
-
Is Java Studio Creator only for very little projects?
Hi
I'm developing a large program with about 100-pages. I found terrible to navigate by ApplicationOutline, Property Binding and Page Navigation.
1. ApplicationOutline should show subfolder structure hierarchically
2. Property Binding should open the page of the binding element, and hierarchical property should be alphabetically sorted
3. Graphical Page Navigation is just a game. I need only a tree view with add/delete management
of navigation-rule
Thanks
Nicola Grippaldi"Sun Java Studio Creator 2, Early Access
Please be aware of the following issues:
* There are a number of known issues with the Refactoring feature.
Before using it:
- Make a backup of your project
- Read the full Release Notes referenced below
* Avoid using subfolders for your web pages.
* You might have deployment problems, such as:
- OutOfMemory exceptions
- Theme switching not taking effect
- Some other deployment failure
If you do have these deployment problems, then:
1) Undeploy.
2) Stop the Application Server.
2) Clean the build.
3) Start the Application Server and redeploy.
* Projects created in Creator 1.0 can be imported, but you cannot
use the new components on the imported pages. We are investigating
creating a conversion utility to the new page structure.
The Sun Java Studio Creator 2 Installation and Release Notes provides
information on installing and uninstalling the product and describes
known bugs and issues. The document is located at:
http://developers.sun.com/prodtech/javatools/jscreator/ea/jsc2/reference/docs/Installation_ReleaseNotes-ea.html
Thank you for evaluating our Early Access release."
This is the content of the README.html.
Creator is only a preview and you should not try to use it with large web sites. The tool has so many bugs and performance lacks, many features seem not to be tested by Sun that it would be a waste of time. -
ABAP+Java Kernel and only Java Kernel
Hi Friends,
Is there any difference in ABAP+Java Kernel and only Java Kernel?
Can we use the kernel for above both from the same location as below?
1#
Support Packages and Patches> Additional Components> SAP Kernel> SAP KERNEL 64-BIT UNICODE> SAP KERNEL 6.40 64-BIT UNICODE
Following Files
DB Dependent - ORACLE
SAPEXEDB_175-20000227.SAR
DBATL640O92_44-20000227.SAR
Database Independent
SAPEXE_175-20000226.SAR
Assuming above SAR files contain R3trans, R3load, tp ,... also.
2#
As per my knowledge SAP has given one more path to download J2EE SP's which contains Kernel and J2EE Support Packages.
http://service.sap.com/patches --> Support Package and Patches -> Entry by Application Group -> SAP NetWeaver -> SAP NetWeaver -> SAP NetWeaver 04 -> Entry by Component -> Application Server Java -> SAP J2EE Engine 6.40 -> J2EERT19_0-10001982.SAR/J2EERT20_0-10001982.SAR (OS Independent) and CTRLDB219_0-20000114.SAR(OS Dendependent)
What is the difference between above two kernels?
1# contains R3trans, R3load, tp ...etc which is exclusively used by ABAP Stack related functions. The startsap script used here would check R3trans -d authentication successful before starting database and then only it starts the database from sidadm. I observed OPS$ users available in only ABAP schema SAPSID but not available in SAPSIDDB. If I use the kernel downloaded from 1# for Java Stack only system, startsap would fail as R3trans authentication fail as there is no ABAP schema in Java systems.
This applies well for ABAP+JAVA or only ABAP based systems.
If I use only JAVA Stack based system can I use the kernel downloaded from 1# . What is the kernel and SP available in 2#? Is this also contains the same kernel given in 1# or it is different. I also observed in JAVA they are not calling Kernels by Patch No like 154, 175... they call it by SP19. Please correct me if I am wrong.
Did anyone come accross this type if issue? I would appreciate if anyone can clarify my questions given above.
My main target is to have clear strategy for ABAP+JAVA, ABAP, JAVA kernels to avoid mess up. Which one to download? What is best practice? Differences?
Thanks and Regards
PrasadHi Sacha,
Thank a lot for your answer I am clear now. Before rewarding points to you.
I have final question.
You mean that there is not seperate kernel for Java Stack Systems.. When we apply SP11 or SP19 by default it applies Kernel and also support packages w.r.t the SP. Do we have option to seperate Kernel and Support package while applying SP's for Java System?
If we take for example SAP NW 2004 (WAS 640) latest kernel is 175 (I mean ABAP+JAVA). If I want to know the latest kernel for Java Stack system, Do I need to say it is at level SP19 or check the sapwebdisp -V (Resepctive patch level)?
For ABAP system we check disp+work -V to get the source kernel version. How to justify the source kernel version for Java System?
As per SAP Note: 710914 - Upgrading the J2EE Engine Startup Framework after applying SP for Java System, Do we need to upgrade J2EE Startup Framework?
Thanks and Regards,
Prasad -
Java Add-In installation for Abap
Hello Friends,
I have installed NW2004s Abap stack for use BW features.
Now, I need to install Java Add-In (including EP and BI Java to use BEX and Integrated Planning) in this same installation.
In SAPINST (Additional Software Lifecycle -> Java Add-in for Abap), have 3 steps to install J2EE Add-in:
1 - Install SCS
2 - Install database Instance
3 - Install Central Instance
Is this correct? I really necessary to execute these steps? (for example, I have NW2004s database Abap running. Why I need to install database instance again?)
Anybody can help me in this procedure?
Thanks,
CarlosHi Everyone.
My scenario is similar with one important difference.
I upgraded from BW 3.5 to BI 7.0. However we never had a java stack on BW before and i did not install one during the upgrade. now the guys want a java stack.
I read the message about putting in a BI Java add in to existing ABAP system. however our hardware for the Abap system is not very good. is it then possible to put the Java add in on another machine ?
What steps are required. Specifically do i run sapinst on the new hardware and what options do i specify.
I have worked in Basis for a long time but am new to this Java stuff, so as much details as possible would help.
Regards
Shirish Joshi -
Is WebDyn ABAP or WebDyn JAVA better for developing Adobe forms ?
Hi Experts,
For our project development we have to decide the option of using Webdynpro ABAP and Webdynpro Java for developing Interactive forms.
What are the pros and cons when it come to select between Webdynpro ABAP and Webdynpro Java for developing Interactive forms.
Can someone provide the advantages and disadvantages over each other.
Thanks in advance.
Edited by: VINAY on Jun 17, 2010 12:45 PM
Edited by: VINAY on Jun 17, 2010 12:48 PMHi Vinay,
It depends on various factors. one is skill availability. IF client has Strong ABAP Development team, Client can go with WebDynpro ABAP, but if client has more Java skills, no issue in going with WebDynpro Java.
In HR, If you choose to use WD-ABAP, you can use many standard WD-ABAP components as search helps. ( WD-abap components HRRCF_C* , HRASR_C* etc )
But do keep in mind that, even if you go with WD-ABAP, you cannot do away with scripting using FormCalc or Javascript in Adobe Form depending on the complexity & UI elements/Search helps etc.
I personally prefer WD-ABAP & would strongly recommend WD-ABAP. Afterall, it is the language of SAP :).
Thanks,
Phani -
I can not get ny updates and therefore not use Java, as it only run updates for MAC 10.7. and later. How do i get the updates to install and use JAVA ?
In Snow Leopard you update Java from Software Update (in the Apple menu). You can check your version by opening Terminal and typing
java -version
(don't get creative and type anything else)
The latest version is 1.6.0_65. -
Mysql database only for one java project
Hello,
Can anyone tell me if somehow I can connect mysql only for one java project.
For e.g. I'm building a swing application I need to use database for some purposes. I want to have all in one. That my project will contain database only for it and nothing else. The user could not be able to connect to that mysql which I'm using for my project.
Any ideas how to make this work?Paulius wrote:
Yes. I want that the database would be implemented in my program (project). And it must be used only with this project and nothing else.Then you'll probably want to use one of the In-memory databases. There was one that came with Java these days too, JavaDB or similar I think.
You can't embed MySQL (AFAIK) in your project. -
Funny: Oracle Jinitiator = Java-Plugin ONLY for MS Windows
Oracle seems to have an agreement with Microsoft.
The product Oracle Jinitiator, which installs a java-plugin, can only be used on MS Windows OS.
And MS Internet Explorer seems to be the preferred browser.
But there is a nice SOD.
If i want to deploy my webforms - all users with netscape and Linux / Mac client platform have no simple installation
or no support.
Does somebody really work with Webforms and Linux-/ or Mac-Clients successfully in production?
Sorry if i express my anger.Peter,
Oracle is looking for a better support of the other client platforms. However, before certifying a native VM or a Plug-in on a platform, we do run regression tests that need to be passed by the VM before getting the certification. In the past we had no luck with other platforms, though we tried the Java plug-in for Linux, Netscape native VM and did certify the MRJ for Macintosh.
Moving forward Oracle's strategy is to certify Sun's Java Plug-in, thus going away from our own Jinitiator development. If this works out, and we are working together with Sun on this, then you can run Forms on any plattform that has a Java 1.4 plugin available. So although we do not have a solution yet, it will be there soon.
Btw, we fully understand your anger about the solely support for the MS platform. It is not our intention to sell Microsoft stocks and we are looking forward to the cange mentioned above.
Frank
Forms Product Management -
Please not another ABAP vs. Java-Thread, BUT ...
Hi, folks!
I already had several inspiring discussions about the need for 2 different languages within one Enterprise System, but right now I' d like to take a more personal approach to this matter.
I' m working within SAP business for about 3 years now and started as a trainee for SAP Java development in a small consulting company . In my first year, I was some kind of geek freaking out on each new SAP technology that arose or was only announced. Web Dynpro Java, ESA/eSOA, Portal, Mendocino/Duet, Business Client, Enterprise Search, Widgets a.s.o. I did a lot of presentations and technical workshops for SAP Pros - NWDI, WDJ, Interactive Forms - and you know what? Nobody was interested in any of these. Interactive Forms? We just switched to Smartforms. WDJ? When will it be available for ABAP. NWDI? We spent a fortune on ABAP courses. Widgets? We have SAP GUI. Business Client? We have SAP GUI. Portal? We have SAP GUI.
Now I' m working as a simple ABAP programmer in HR. No web enablement, cause web apps are realized completely outside SAP. No SOA-enablement, cause all SAP functionality needed outside is either already provided via BAPIs or put in RFC modules. No Java at all, cause there is and will be only an ABAP stack. None of all the new stuff, but a great need for knowledge of standard programs, their configuration possibilities and use.
So, to come to the conclusion: What I realized in my work life is that daily business is pretty innovation-resistant and I personally don' t think that even half of all the "emerging technologies" will make it for the next 5 - 10 years. What I also realized is that a lot of time and work has to be spent by developers to keep in touch with new development techniques, which could be used better for clearing white spaces in classical ABAP as well as module programming environments. If developers would focus more on ABAP and module knowledge than on the newest Modelling-techniques many SAP systems probably wouldn' t be spoiled by poor custom developments, enhancements and modifications as they are today!
Regards,
ThomasSo, to come to the conclusion: What I realized in my work life is that daily business is pretty innovation-resistant and I personally don' t think that even half of all the "emerging technologies" will make it for the next 5 - 10 years.
Yes - it is indeed. If a company invested quite lots of money to get a certain application (or a part of it) working they won´t switch to a different technology just because it´s "hip" at the moment. For new customers it is certainly a very nice alternative to use the new technologies instead of the "old ones".
And to quote the example I said already a few times: If ABAP was so bad, why would SAP themselves switch certain applications back to WD-ABAP (speaking of Travel Management in Enhancement Pack 2 e. g.).
What I also realized is that a lot of time and work has to be spent by developers to keep in touch with new development techniques, which could be used better for clearing white spaces in classical ABAP as well as module programming environments. If developers would focus more on ABAP and module knowledge than on the newest Modelling-techniques many SAP systems probably wouldn' t be spoiled by poor custom developments, enhancements and modifications as they are today!
What I´ve heard the new paradigma is
- Service provisioning: ABAP
- Service consumption: Java
Whatever this means in detail.
I can hardly imagine removing the SAPGUI out of our e. g. sales department and replace it by e. g. a nice "guided procedure" using NWBC. In maybe 5 % of the todays cases this would be enough, the other 95 % still need the full featured transaction with all the tabs, fields and editing functionality.
And what I find the most interesting in that area is: SAP internally I always see SAPGUIs on the (supporters, sales dep.) desks, the "backend OSS/CSN" is still accessed by GUI and not by web, guess why...
Markus -
We are implementing a project on XI.
We need to freeze on one mapping.
I feel ABAP Mapping provides the following advantages:
1.SXI_MAPPING_TEST is a very good transaction for debugging and testing mapping environment of XI.Iam not sure wether java mapping can be tested after deploying it on XI.
2.ABAP Mapping is well integrated with the XI and also version control becomes very easy as it is provided by the SAP transport system.
3.ABAP also provides user rich/simple API's as java.
4.Support of XI in ABAP would make sustanenace easy as it is going to be a more SAP product and ABAPers are more available in ERP background.
Java punters,Please provide inputs.Hi,
all of the step in the message flow after a message enter
the IS will be done by the abbap stack e.g. Receiver
determination, interface determination, ... The only one
step that is executed in J2EE-Stack is the mapping.
In the pipline the system jump from the abap stack to
Java stack to execute the mapping if the mapping is done
in Java (message mapping, java mapping, xslt,...).
But if the the mapping is done by abap the the runtime
has not to jump to the java stack to execute the mapping.
Because there is no java code to execute. To clarif: if
you have only abap-mapping the the compete process step
do not include the jump to the j2ee-stack of XI. So in
this case the abap mapping is more performant cause the
runtime stay in the abap stack through the complete
message processing.
But if you have mix mapping e.g. first step abap and
second step java then the j2ee-stack will be used as
well.
regards,
Ly-Na Phu -
Direct Connection ABAP Proxy and Java Proxy possible ????
Hi Folks ,
As i read as direct connection possible between 2 SAP systems only ..
and also i read as WS Direct Connection u2013 (Java) ..
What it means ?? is it ABAP Proxy to Java Proxy using Direct connection ?? Like Java Client Proxy and ABAP Server proxy
I am not clear on this.. Could you please explain or help me on this . ??
Siva..Hi ,
+You can do both for java proxies as well Abap proxies.+
As per the following points
1. Point-to-point connection is a new capability available with SAP NW PI 7.1. It allows applications or systems to send messages using WS-RM without going through a middleware, e.g. PI, but still using a centralized tool to design and
configure the interfaces and connection properties.
2. SAP XI 3.0/PI 7.00 or higher releases can be licensed based on the total volume of messages in
gigabytes (GB) that is processed per month. The size of the payload is determined in the integration
server. The information is then aggregated according to sender and receiver system.
Question :
1. If Message exchange between 2 SAP applications using direct connection .. Then dont we need to consider about licencing cost for volume of messages per month ?
2. So if i use ABAP Client Proxy to Java Server proxy scenario.. can i use direct connection ? Eg., SAP ECC to java application ?
In both the cases PI Runtime is not required .. Am i right ?
Please clarify..
Siva.. -
Java.rmi.RemoteException: Only Administrators
Hello all,
I am running Solution Manager 4.0 as Central Systems Installation (ABAP + Java System) with Oracle 10.2 on Windows Server 2003 Standard Edition. I recently downloaded new support package stack 08 to SP16 and then tried to update using JSPM. The Kernel, System using <SID>adm user account. And, i got other some updates( JSPM, SAP Kernel, IGS, SAP_JAVASL, BASETABLES, CORE-TOOLS, JLOGVIEW, SAP-JEE, SAPJEECOR and SAP_JTECHF ) applied successfully with other remaining updates (ADSSAP, BI_MMR, KM-KW_JIKS, CAF-UM, SAP_JTECHS, BI_UDI, CAF, LM-TOOLS, UMEADMIN and LM-SERVICE). I am facing problem at ADSSAP with the error message.
I already done below things.
1) I have updated JSPM version to latest.
2) User J2EE_ADMIN have role of SAP_J2EE_ADMIN in SU01
3) I tried to deploy with SDM, but failed with same error
4) i am not able to login to Visual admin(with default connection j2ee_admin)
5)J2EE_ADMIN user is not locked in SU01
6) I tried to open http://<HOSTNAME>:50100/useradmin, but throwing below error
503 Service Unavailable
Application cannot be started.
Details: com.sap.engine.services.deploy.container.ExceptionI nfo: Naming error.
7) Server_ID142442 --->Services ---> com.sap.security.cor e.ume.service ---> ume.persistence.data_source value is
dataSourceConfiguration_r3_rw.xml
SDM Error Log:
===================================================
==========================================================================
Deployment started Mon Sep 24 08:53:57 GMT+05:30 2007
===========================================================================
Starting Deployment of tc/smd/cptdict
Finished successfully: development component 'tc/smd/cptdict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'1'
Deployment of tc/smd/cptdict finished successfully (Duration 11203 ms)
Starting Deployment of SAP_BUILDT
Finished successfully: software component 'SAP_BUILDT'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071117141300''/'1'
Deployment of SAP_BUILDT finished successfully (Duration 9485 ms)
Starting Deployment of tc/smd/datamgmt/dict
Finished successfully: development component 'tc/smd/datamgmt/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'1'
Deployment of tc/smd/datamgmt/dict finished successfully (Duration 7922 ms)
Starting Deployment of tc/smd/server/service
The SDM will now stop SAP Web AS Java cluster instance(s) processes in order to perform offline deployment. After that the deployment will proceed.
It could take some time, so please be patient.
Finished successfully: development component 'tc/smd/server/service'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/smd/server/service finished successfully (Duration 23375 ms)
Starting Deployment of tc/webadministrator/ccrep/dict
Finished successfully: development component 'tc/webadministrator/ccrep/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/ccrep/dict finished successfully (Duration 15579 ms)
Starting Deployment of tc/webadministrator/ewa/dict
Finished successfully: development component 'tc/webadministrator/ewa/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/ewa/dict finished successfully (Duration 8453 ms)
Starting Deployment of tc/webadministrator/fvrep/dict
Finished successfully: development component 'tc/webadministrator/fvrep/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'1'
Deployment of tc/webadministrator/fvrep/dict finished successfully (Duration 9171 ms)
Starting Deployment of tc/webadministrator/httpanalysis/dict
Finished successfully: development component 'tc/webadministrator/httpanalysis/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'1'
Deployment of tc/webadministrator/httpanalysis/dict finished successfully (Duration 7843 ms)
Starting Deployment of tc/webadministrator/lib/dict
Finished successfully: development component 'tc/webadministrator/lib/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'1'
Deployment of tc/webadministrator/lib/dict finished successfully (Duration 7985 ms)
Starting Deployment of tc/webadministrator/lib/dbc
Finished successfully: development component 'tc/webadministrator/lib/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'1'
Deployment of tc/webadministrator/lib/dbc finished successfully (Duration 7547 ms)
Starting Deployment of tc/webadministrator/logviewer/dict
Finished with warnings: development component 'tc/webadministrator/logviewer/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'1':
No further description found.
Deployment of tc/webadministrator/logviewer/dict finished with Warning (Duration 7922 ms)
Starting Deployment of tc/webadministrator/navigation/dict
Finished successfully: development component 'tc/webadministrator/navigation/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/navigation/dict finished successfully (Duration 8907 ms)
Starting Deployment of tc/webadministrator/navigation/dbc
Finished successfully: development component 'tc/webadministrator/navigation/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/navigation/dbc finished successfully (Duration 9500 ms)
Starting Deployment of tc/webadministrator/scheduler/dict
Finished successfully: development component 'tc/webadministrator/scheduler/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/scheduler/dict finished successfully (Duration 8203 ms)
Starting Deployment of tc/webadministrator/screp/dict
Finished successfully: development component 'tc/webadministrator/screp/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/screp/dict finished successfully (Duration 8672 ms)
Starting Deployment of tc/webadministrator/screp/dbc
Finished successfully: development component 'tc/webadministrator/screp/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
Deployment of tc/webadministrator/screp/dbc finished successfully (Duration 7500 ms)
Starting Deployment of tc/webadministrator/selfcheck/dict
Finished successfully: development component 'tc/webadministrator/selfcheck/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'1'
Deployment of tc/webadministrator/selfcheck/dict finished successfully (Duration 7969 ms)
Starting Deployment of tc/webadministrator/selfcheck/dbc
Finished successfully: development component 'tc/webadministrator/selfcheck/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'1'
Deployment of tc/webadministrator/selfcheck/dbc finished successfully (Duration 7719 ms)
Starting Deployment of DocumentServicesLicenseManager
The SDM will now start SAP Web AS Java instance processes in order to perform online deployment. After that the deployment will proceed.
It could take some time, so please be patient.
Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'800.20070306123954.374077'/'4', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071118055147''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of DocumentServicesLicenseManager finished with Error (Duration 160515 ms)
Starting Deployment of AdobeDocumentServices
Deployment of AdobeDocumentServices was skipped (Duration 7453 ms)
Starting Deployment of tc/ads/grmg
Aborted: development component 'tc/ads/grmg'/'sap.com'/'SAP AG'/'7.0010.20061002104728.0000'/'4', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071118055147''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/ads/grmg finished with Error (Duration 8438 ms)
Starting Deployment of ADSSAP
Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071118055147''/'1':
Failed deployment of SDAs:
development component 'AdobeDocumentServices'/'com.adobe'/'Adobe Systems'/'800.20070708051308.406522'/'4' : skipped
development component 'tc/ads/grmg'/'sap.com'/'SAP AG'/'7.0010.20061002104728.0000'/'4' : aborted
development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'800.20070306123954.374077'/'4' : aborted
Please, look at error logs above for more information!
Deployment of ADSSAP finished with Error (Duration 7907 ms)
Starting Deployment of bi/mmr/browser_ea
Aborted: development component 'bi/mmr/browser_ea'/'sap.com'/'SAP AG'/'7.0011.20070124085018.0000'/'2', grouped by software component 'BI_MMR'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072334''/'2':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of bi/mmr/browser_ea finished with Error (Duration 8437 ms)
Starting Deployment of bi/mmr/cwm_1.0_source
Aborted: development component 'bi/mmr/cwm_1.0_source'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'2', grouped by software component 'BI_MMR'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072334''/'2':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of bi/mmr/cwm_1.0_source finished with Error (Duration 9375 ms)
Starting Deployment of bi/mmr/miniMetaModel
Aborted: development component 'bi/mmr/miniMetaModel'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'2', grouped by software component 'BI_MMR'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072334''/'2':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of bi/mmr/miniMetaModel finished with Error (Duration 8172 ms)
Starting Deployment of bi/mmr/mini_md350
Aborted: development component 'bi/mmr/mini_md350'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'2', grouped by software component 'BI_MMR'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072334''/'2':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of bi/mmr/mini_md350 finished with Error (Duration 8000 ms)
Starting Deployment of BI_MMR
Aborted: software component 'BI_MMR'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072334''/'2':
Failed deployment of SDAs:
development component 'bi/mmr/mini_md350'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'2' : aborted
development component 'bi/mmr/miniMetaModel'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'2' : aborted
development component 'bi/mmr/browser_ea'/'sap.com'/'SAP AG'/'7.0011.20070124085018.0000'/'2' : aborted
development component 'bi/mmr/cwm_1.0_source'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'2' : aborted
Please, look at error logs above for more information!
Deployment of BI_MMR finished with Error (Duration 7844 ms)
Starting Deployment of caf/um/metadata/actions
Aborted: development component 'caf/um/metadata/actions'/'sap.com'/'MAIN_APL70VAL_C'/'1077265'/'3', grouped by software component 'CAF-UM'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062847''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/metadata/actions finished with Error (Duration 8125 ms)
Starting Deployment of caf/um/metadata/content
Aborted: development component 'caf/um/metadata/content'/'sap.com'/'MAIN_APL70VAL_C'/'1497172'/'3', grouped by software component 'CAF-UM'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062847''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/metadata/content finished with Error (Duration 8094 ms)
Starting Deployment of caf/um/metadata/example
Aborted: development component 'caf/um/metadata/example'/'sap.com'/'MAIN_APL70VAL_C'/'963657'/'3', grouped by software component 'CAF-UM'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062847''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/metadata/example finished with Error (Duration 8094 ms)
Starting Deployment of caf/um/metadata/testwd
Aborted: development component 'caf/um/metadata/testwd'/'sap.com'/'MAIN_APL70VAL_C'/'963659'/'3', grouped by software component 'CAF-UM'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062847''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/metadata/testwd finished with Error (Duration 8047 ms)
Starting Deployment of caf/um/relgroups/admin
Aborted: development component 'caf/um/relgroups/admin'/'sap.com'/'MAIN_APL70VAL_C'/'963666'/'3', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/relgroups/admin finished with Error (Duration 8328 ms)
Starting Deployment of caf/um/relgroups/test
Aborted: development component 'caf/um/relgroups/test'/'sap.com'/'MAIN_APL70VAL_C'/'963945'/'3', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/um/relgroups/test finished with Error (Duration 7703 ms)
Starting Deployment of CAF-UM
Aborted: software component 'CAF-UM'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062847''/'1':
Failed deployment of SDAs:
development component 'caf/um/metadata/example'/'sap.com'/'MAIN_APL70VAL_C'/'963657'/'3' : aborted
development component 'caf/um/metadata/content'/'sap.com'/'MAIN_APL70VAL_C'/'1497172'/'3' : aborted
development component 'caf/um/metadata/testwd'/'sap.com'/'MAIN_APL70VAL_C'/'963659'/'3' : aborted
development component 'caf/um/metadata/actions'/'sap.com'/'MAIN_APL70VAL_C'/'1077265'/'3' : aborted
development component 'caf/um/relgroups/test'/'sap.com'/'MAIN_APL70VAL_C'/'963945'/'3' : aborted
development component 'caf/um/relgroups/admin'/'sap.com'/'MAIN_APL70VAL_C'/'963666'/'3' : aborted
Please, look at error logs above for more information!
Deployment of CAF-UM finished with Error (Duration 7532 ms)
Starting Deployment of tc/km_tc/kw
Aborted: development component 'tc/km_tc/kw'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'1', grouped by software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/km_tc/kw finished with Error (Duration 8188 ms)
Starting Deployment of tc/km_tc/sapiks
Aborted: development component 'tc/km_tc/sapiks'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'1', grouped by software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/km_tc/sapiks finished with Error (Duration 7891 ms)
Starting Deployment of tc/km_tc/sapirexthelp
Aborted: development component 'tc/km_tc/sapirexthelp'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/km_tc/sapirexthelp finished with Error (Duration 7953 ms)
Starting Deployment of tc/kw_tc
Aborted: development component 'tc/kw_tc'/'sap.com'/'SAP AG'/'7.0015.20080123135455.0000'/'1', grouped by software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of tc/kw_tc finished with Error (Duration 8828 ms)
Starting Deployment of KM-KW_JIKS
Aborted: software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'1':
Failed deployment of SDAs:
development component 'tc/km_tc/kw'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'1' : aborted
development component 'tc/km_tc/sapiks'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'1' : aborted
development component 'tc/km_tc/sapirexthelp'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'1' : aborted
development component 'tc/kw_tc'/'sap.com'/'SAP AG'/'7.0015.20080123135455.0000'/'1' : aborted
Please, look at error logs above for more information!
Deployment of KM-KW_JIKS finished with Error (Duration 7657 ms)
Starting Deployment of SQLTrace
Aborted: development component 'SQLTrace'/'sap.com'/'SAP AG'/'7.0013.20070703111935.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of SQLTrace finished with Error (Duration 8016 ms)
Starting Deployment of com.sap.aii.util.rb
Aborted: development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'7.0012.20070328121059.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.aii.util.rb\SAP AG\3\7.0012.20070328121059.0000\aii_util_rb.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.aii.util.rb\SAP AG\3\7.0012.20070328121059.0000\aii_util_rb.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.aii.util.rb finished with Error (Duration 7969 ms)
Starting Deployment of com.sap.aii.util.misc
Deployment of com.sap.aii.util.misc was skipped (Duration 7125 ms)
Starting Deployment of com.sap.aii.util.xml
Deployment of com.sap.aii.util.xml was skipped (Duration 7250 ms)
Starting Deployment of com.sap.aii.ibtranslationclient
Deployment of com.sap.aii.ibtranslationclient was skipped (Duration 7125 ms)
Starting Deployment of com.sap.aii.ibtransportclient
Deployment of com.sap.aii.ibtransportclient was skipped (Duration 7250 ms)
Starting Deployment of com.sap.aii.proxy.framework
Deployment of com.sap.aii.proxy.framework was skipped (Duration 6907 ms)
Starting Deployment of com.sap.engine.class.download
Aborted: development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'7.0012.20070328121153.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.engine.class.download finished with Error (Duration 7891 ms)
Starting Deployment of com.sap.engine.customizing.ccms
Aborted: development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'7.0014.20071029094615.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.engine.customizing.ccms finished with Error (Duration 7938 ms)
Starting Deployment of com.sap.engine.docs.examples
Aborted: development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'7.0014.20071029094615.0000'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.engine.docs.examples finished with Error (Duration 12546 ms)
Starting Deployment of com.sap.engine.heartbeat
Aborted: development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'7.0012.20070328121153.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.engine.heartbeat to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.util.monitor.grmg; java.rmi.RemoteException: Only Administrators have the right to perform this operation.; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.engine.heartbeat to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.util.monitor.grmg; java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.engine.heartbeat finished with Error (Duration 7641 ms)
Starting Deployment of com.sap.jdo
Aborted: development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'7.0013.20070703111940.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.jdo finished with Error (Duration 8062 ms)
Starting Deployment of com.sap.lcr.namealloc
Aborted: development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'7.0013.20070703113613.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.lcr.namealloc\SAP AG\3\7.0013.20070703113613.0000\namealloc.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.lcr.namealloc\SAP AG\3\7.0013.20070703113613.0000\namealloc.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.lcr.namealloc finished with Error (Duration 7796 ms)
Starting Deployment of com.sap.lcr.saprfc
Aborted: development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'7.0013.20070703113613.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcr.saprfc to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient; java.rmi.RemoteException: Only Administrators have the right to perform this operation.; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcr.saprfc to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient; java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.lcr.saprfc finished with Error (Duration 7937 ms)
Starting Deployment of com.sap.lcrabapapi
Aborted: development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'7.0013.20070328121631.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcrabapapi to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient; java.rmi.RemoteException: Only Administrators have the right to perform this operation.; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcrabapapi to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient; java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.lcrabapapi finished with Error (Duration 8000 ms)
Starting Deployment of com.sap.mobile.clientinfo
Aborted: development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'7.0013.20060719095239.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.mobile.clientinfo.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.mobile.clientinfo.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineLib620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.mobile.clientinfo finished with Error (Duration 7813 ms)
Starting Deployment of com.sap.pmi.adm
Aborted: development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'7.0014.20071029095144.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.pmi.adm finished with Error (Duration 7812 ms)
Starting Deployment of com.sap.rprof.dbprofiles
Aborted: development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'7.0014.20070328121706.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.rprof.dbprofiles\SAP AG\1\7.0014.20070328121706.0000\dbprofiles.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.rprof.dbprofiles\SAP AG\1\7.0014.20070328121706.0000\dbprofiles.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.rprof.dbprofiles finished with Error (Duration 7735 ms)
Starting Deployment of com.sap.lcr
Deployment of com.sap.lcr was skipped (Duration 7172 ms)
Starting Deployment of com.sap.rprof.remoteProfile
Deployment of com.sap.rprof.remoteProfile was skipped (Duration 6922 ms)
Starting Deployment of com.sap.security.core.admin
Aborted: development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'7.0014.20071029094847.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.security.core.admin finished with Error (Duration 9187 ms)
Starting Deployment of com.sap.util.monitor.jarm.ccms
Aborted: development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'7.0013.20051128142456.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.ccms.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.ccms.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineLib620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.util.monitor.jarm.ccms finished with Error (Duration 7719 ms)
Starting Deployment of com.sap.util.monitor.jarm.j2ee
Aborted: development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'7.0013.20051128142456.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.j2ee.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.j2ee.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineLib620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of com.sap.util.monitor.jarm.j2ee finished with Error (Duration 7672 ms)
Starting Deployment of com.sapmarkets.mesyncjco
Deployment of com.sapmarkets.mesyncjco was skipped (Duration 7532 ms)
Starting Deployment of com.sapportals.htmlb
Deployment of com.sapportals.htmlb was skipped (Duration 7187 ms)
Starting Deployment of com.sap.engine.services.webservices.tool
Deployment of com.sap.engine.services.webservices.tool was skipped (Duration 7172 ms)
Starting Deployment of com.sapportals.htmlb.ear
Deployment of com.sapportals.htmlb.ear was skipped (Duration 7204 ms)
Starting Deployment of sl.ut.content.nw
Aborted: development component 'sl.ut.content.nw'/'sap.com'/'SAP AG'/'7.0014.20071123054250.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of sl.ut.content.nw finished with Error (Duration 7750 ms)
Starting Deployment of sl.ut.infoprovider
Aborted: development component 'sl.ut.infoprovider'/'sap.com'/'SAP AG'/'7.0014.20071123054250.0000'/'3', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\sl.ut.infoprovider\SAP AG\3\7.0014.20071123054250.0000\sap.com~sl.ut.infoprovider.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\sl.ut.infoprovider\SAP AG\3\7.0014.20071123054250.0000\sap.com~sl.ut.infoprovider.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of sl.ut.infoprovider finished with Error (Duration 7391 ms)
Starting Deployment of sl/ut/info
Deployment of sl/ut/info was skipped (Duration 7125 ms)
Starting Deployment of tc/SL/CMS/Util
Aborted: development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'7.0014.20071002095021.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'1':
Caught exception during library deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\tc\SL\CMS\Util\SAP AG\1\7.0014.20071002095021.0000\CMSutil.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Exception is: ; nested exception is: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform actiupdate please..??
Edited by: Pratyusha on Sep 25, 2008 10:58 AM
Edited by: Pratyusha on Sep 26, 2008 10:25 AM -
Java Add-In Installation for EHP4 ERP system
Hello!
we successfully upgraded our SAP ERP system to EHP4 for SAP.
Our system has only ABAP stack.
Question
1) Is it possible to install a Java Add-In instance for the existing EHP4 system?
2) If yes, can this be done on the same Windows server?
Thank you very much!Specific Requirements
Take the following specific requirements of the new installation process into consideration:
- The previous SAPInst installation service Java Add-In in SAP ERP 6.0/SAP NetWeaver
7.0 was able to add Java usage types such as EPC, or EP, to existing ABAP-only
systems. This was possible only, if you added AS Java at the same time. The option of a
Java Add-In installation is not any longer available as of the enhancement package 4 for
SAP ERP 6.0. Thus, it is not any longer possible, for example, to add EPC and EP
together with AS Java to an ABAP-only system.
[SAP Enhancement Package 4 for SAP ERP 6.0|https://websmp201.sap-ag.de/~sapidb/011000358700000772192007E]
There are many links on SDN discussing ERP EHP 4 dual stack:
[Re: EHP4 Dual stack;
[ECC 6.0 - EHP4 - Client Import;
Hope this helps.
Thanks,
Naveed -
Restoring Web AS ABAP+JAVA or JAVA to different host
Dear forum,
We have a disaster recovery plan by using another host (call it as the backup host) to run SAP in case the main host is failed.
The backup was done separately for DB, IFS and authorization, as well as the restore. After the restore, the profile parameters were changed to be pointing to the new host.
We did a restore of ABAP+ JAVA and JAVA only systems from the backup that was performed on the main host to the backup host.
In the JAVA part for both ABAP+JAVA and JAVA, I found a lot of things to change in configtool which are still pointing to the old host. I have tried to change the parameters that I found, but it didn't help.
I could get the ABAP part up and running by maintaining WRKSRVTBLE and some SQL packages issues, but not for the JAVA part.
Can I do a system copy from the main host to the backup host and in case of a disaster, the action is only restoring the DB part? Or any other suggestions?
Thanks before,
Agoes
Message was edited by:
Agoes Boedi PoerwantoHi Agoes,
Let me make sure I understand what you are trying to do. Your backup system is basically a copy of your production system running on a different host. If the production system fails then you will restore the data from the most recent backup to the system running on the backup host. Is that the scenario?
If you are just trying to copy the system to a new host and get it up and running, I would recommend an officially supported method such as a homogenous system copy to do this. However, the attached document in SAP note 568820 "iSeries: Implementing an Independent ASP (iASP) System" has an entire section on modifying an SAP system to run on a different host.
You may want to consider taking your HA strategy one step further by implementing an iASP. Your HA solution that you describe is very similar to the iASP solution, but I think an iASP will better meet your needs.
Kolby -
Displaying both ABAP webdynpro and Java Webdynpro tasks in the UWL
Hi,
We have two an issue when trying to get the UWL to process two different types of workflow tasks : ABAP webdynpro and Java webdynpro.
Examples of these tasks are:
TS12300097 u2013 LeaveRequestApprover u2013 Java Webdynpro
TS17900100 - ASR_PROCESS_EXECUTE u2013 ABAP webdynpro
We have two backend systems configured
SAP_ECC_Financials u2013 This has the WAS host pointing to the java stack (xxx:50000)
SAP_ECC_Workflow u2013 This has the WAS host pointing to the ABAP stack (xxx.80xx)
In transaction SWFVISU all the tasks which use Java webdynpro have been configured to use the u2018Javau2019system (SAP_ECC_Financials) using the SYSTEM_ALIAS parameter
In the UWL configuration the system SAP_ECC_Workflow has been registered
In addition to this all u2018Javau2019 tasks have had an extra UWl config XML created to ensure that the SYSTEM_ALIAS is set to SAP_ECC_Financials
The system SAP_ECC_Workflow has been re-registered
The UWL cache has been cleared
However when we try to launch the java webdynpro tasks the system is trying to access the ABAP stack (It is still trying to access the Web AS location for the system SAP_ECC_Workflow even though the system alias was specified as SAP_ECC_Financials )
The ABAP webdynpro tasks (in this case a HCM process and form) are launched correctly
If we try the reverse (i.e register the Java system SAP_ECC_Financials and change the SYSTEM_ALIAS parameter for the ABAP webdynpro tasks to system SAP_ECC_Workflow) then the reverse happens. The java tasks can be launched and the ABAP tasks cannot.
Does anyone have a solution to this problem. Surely other people have implemented both ABAP and Java webdynpro workflows?
Any help much appreciated
AndrewThanks a lot for all your replies..
The workitem type registration has been done already, but still it doesn't work..
But here is the actual problem...
There is a link 'Execute Workitem' in the inbox of the approver, or the second level manager...
In the leave application, when we click on this link it is taking to the portal as the task is the Webdynpro Java application task. Whereas, when using ABAP webdynpro application task, it is taking to R/3 - which means that the user cannot access this link without R/3 access. The users are given only portal access, they don't have access to backend R/3.
The requirement is that the link has to take the user to portal directly instead of R/3 - i.e it should ask only for the portal id and password.
Since it was working fine with leave application, I changed the task to Java webdynpro task, but I think the Java Webdynpro application is not deployed in the server.
Please can anybody suggest.
Best Regards,
Sushmitha
Maybe you are looking for
-
An error occurred while applying SQL script for the feature BackendStore.
Hello, I am using my AD in Windows Azure VMs. I created new VM of A3 (4 cores, 7 GB Memory) Windows Server 2012 R2, Port 1433 MSSQL added, made it a member of Domain and planned to install first Lync Server 2013 on it. In "Setup or Remove Lync Server
-
Comments about Aperture and DNG
I bought a copy of Aperture a while ago and recently purchased a computer capable of running it. So now that I am becoming acquainted with it I have some comments for Apple: • I am amazed by the flexibility of the interface, and at the same time surp
-
Videos on Justin.tv won't play!!!!
Only started having this issue today..had no problems until today..I went to this site http://http://www.justin.tv/nosequeponer24/b/343569580 and the video just won't play it says that if I wanna watch this video I have to have the Adoble Flash Playe
-
Hi , I am trying to export a data within a table and its graph to PDF . I recieve an error message that the graph size must be smaller than the page size minus the left and right margins . The error reffers me to "Printable PDF" settings . There i ad
-
Application error during release to LiveCache
Hi Experts. I got some orders stucked in my Outbound Queue in ECC side as SysFail with the error "Application error during release to LiveCache". When I click to activate the queue the order is released and transferred to APO. The question is Why is