Deployment of Webservice in J2EE Engine.

Hi All:
I am created a webservice and want to deploy it in SAP J2EE engine. But when I am trying it I am getting below Error Message:
/userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[002]Deployment aborted
Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !
I also checked the SAP J2EE parameters in NWDS and its perfect:
Preference>SAP J2EE Engine>
Message Server Host : given host name
Message Server Port : 3900 (Even I tried 3600). I am not sure but I think 3900 is a default port for it??
If some one face the same problem and solved it please share it with me...
When Webservice receive the SOAP message from XI= XI is exploring or consuming it..i am confused on this:)
Thanks & Regards,
Farooq Farooqui.

you can ask ur basis guy about the same or else if u have access to sap management console u can check it out urself.
steps;
sap mmc -- > goto ur server instance list in left frame
                --> goto process list
                   --> in the right frame right click on msg-server.exe select developer trace.
in that trace  ull find a statement like
I listen to internal port  xxxx*** where xxxx is ur port.
regards
fariha
reward if useful

Similar Messages

  • Error deploying WS to remote J2EE engine

    Any help with what I am doing wrong here would be GREAT!
    I'm getting this message after I create a WS from a EJB:
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/ProdCatWsEAR..
    Reason: Webservices deployment exception! The reason is: Error occured, trying to generate web services deployment files for application sap.com/ProdCatWsEAR. . The error refers to application: none, jar: , web service: .; nested exception is:
    Any one have an idea?
    Regards,
    Mike Jakeway
    Whirlpool Corporation

    Anilkumar,
    Still no luck.  I am not using any complex data types and the developer studio and J2EE engine are both at SP09.
    Is there anything special I must do when deploying to a remote J2EE engine?  I am running NDS on Windows box and attemtping to deploy to an AIX box the J2EE engine.  I can deploy with no problem a simple J2EE app like the Calculator example.  I only receive this error when I attempt a WS deploy.
    Regards,
    Mike

  • Deployment Error on sap-j2ee engine

    Hi
    I build an EJB project,Web project and added these to EAR project and built an '.ear' file. When i tried to deploy on sapj2ee engine. I got the following deployment error.
    My j2ee engine is up and running. What went wrong?
    Help me,
    Thanks
    ==========
    May 24, 2006 5:39:51 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [003]Deployment aborted
    Settings
    SDM host : sapep
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp22811JCP_EAR.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp22811JCP_EAR.ear
    Aborted: development component 'JCP_EAR'/'sap.com'/'localhost'/'2006.05.24.15.58.19':
    Caught exception during access of archive "D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear":
    java.lang.RuntimeException: ERROR: Cannot initialize EARReader: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear to J2EE 1.3.Exception is: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear to J2EE 1.3.
         at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:185)
         at com.sap.engine.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:444)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.initDeployManager(EngineApplOnlineDeployerImpl.java:300)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:134)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
         at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
         at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
         at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
         at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
         at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:119)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:88)
         at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
         at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
         at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
         at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
         at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
         at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
         at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
         at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: java.io.IOException: The following archives that aredescribed in the ear descriptor are not found in the ear:      JCP_EJB.jar,Please check the ear content.
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.checkDescriptor(ExtendedEARReader.java:805)
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.getDescriptor(ExtendedEARReader.java:324)
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.<init>(ExtendedEARReader.java:87)
         at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:85)
         ... 30 more
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
    Deployment exception : The deployment of at least one item aborted

    Hi Amol!
    The password is admin for SDM, i redployed by building '.ear' file again.
    You suggested to deploy the ear file on SDM remote gui, how to do that?
    help me
    Thanks
    ==========
    I got the error as:
    May 25, 2006 11:22:11 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : sapep
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp11022JCP_EAR.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp11022JCP_EAR.ear
    Aborted: development component 'JCP_EAR'/'sap.com'/'localhost'/'2006.05.25.11.17.51':
    Caught exception during access of archive "D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear":
    java.lang.RuntimeException: ERROR: Cannot initialize EARReader: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear to J2EE 1.3.Exception is: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear to J2EE 1.3.
         at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:185)
         at com.sap.engine.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:444)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.initDeployManager(EngineApplOnlineDeployerImpl.java:300)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:134)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
         at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
         at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
         at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
         at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
         at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:119)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:88)
         at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
         at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
         at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
         at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
         at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
         at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
         at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
         at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: java.io.IOException: The following archives that aredescribed in the ear descriptor are not found in the ear:      JCP_EJB.jar,Please check the ear content.
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.checkDescriptor(ExtendedEARReader.java:805)
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.getDescriptor(ExtendedEARReader.java:324)
         at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.<init>(ExtendedEARReader.java:87)
         at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:85)
         ... 30 more
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
    Deployment exception : The deployment of at least one item aborted

  • Cannot deploy app files to j2ee engine in NWDS

    Hi,
      I`ve got NWDS ver. 2.0.15 and I am trying to deploy some files to app server but I got message
    Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !
    I am almost 100%  it`s because I need to use proxy to connect the server. I set up proxy settings in window->preferences->workbench->proxy but I think this option doesn't affect to j2ee engine connection. Cause for example I can access portal on port 50000 using my browser (with set up proxy), but I cannot deploy PAR file what`s more the settings window->preferences->SAP Enterprise portal are correct and the same which I used to connect portal using web browser.
      I was thinking about other way to check the connection and SDM Remote GUI came on my mind. Does anybody know how to set up proxy in this program?

    Rich,
      I did it and I am absolutley sure that host and message server are correct. I think that the problem is that to connect server the connection should be via proxy. And I think beacuse of it connection desnt work.
    Look at my example I can connect portal via web browser with configured proxy, but I cannot deploy PAR file using NWDS with the same port and host as I used in browser.
    I have configured proxy in NWDS (window->preferences->workbench->proxy) but I am affraid that this setting doesnt take affect to j2ee engine settings and Enterprise portal deployment settings.
    Now I am looking for tool which gives me possibility to connect SDM some other way with proxy. Or maybe there is some soft that allows me to set all outgoing network connections to go via proxy.

  • Error while deploying .EAR on to J2EE Engine..

    HI all,
    I was trying to deploy a .EAR file on to the nw04s J2ee Engine.But it is getting aborted and it is throwing the following error.
    Caught exception during application deployment from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.MissingSubstitutionException: Missing substitution value for variable [com.sap.dc_name].
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC
    Can someone help me out on what could be the reason for this error.
    Best regards,
    Vijaya Sai.
    Message was edited by: Vijayasai

    Hello Vijayasai,
    Could you please send me the .Ear([email protected])in question or if this is not convenient for you, at least the SAP_Manifest, so we can investigate the issue.
    Best Regards,
    Elena

  • Deployment getting aborted on J2EE Engine from NWDS

    Hi,
    While i am trying to deploy the Java WebDynPro code on J2EE Engine its giving me the following error.
    Apr 9, 2008 10:24:53 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : sghrdpr7
    SDM port : 50118
    URL to deploy : file:/C:/DOCUME1/NUZHAT1/LOCALS1/Temp/temp21573sap.comfixedtoolbar.ear
    Deployment exception : Server sghrdpr7 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server sghrdpr7 at port 50118: sghrdpr7
    Inner exception was :
    Server sghrdpr7 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server sghrdpr7 at port 50118: sghrdpr7
    The deployment is getting aborted.
    I have tried telnet for the port number from my end and that is successfull.
    Now i dont where the problem is????????
    Please help urgently

    Hi,
    Have you checked whether the deployment with the SDM directly works or not ? (not through NWDI).
    Also, for the SDM deployment to function correctly, make sure of the following :
    Please make sure to set :                                                                               
    - the P4 host to localhost in the Secure Store (setting localhost is a workaround if you have multiple hostnames (virtual/physical)
    - the secure store should have the correct password for the j2ee_admin(in case of dual stack) or administrator(in case of java only) as SDM server takes the password from secure store for the login to j2ee engine as administrator which is required for the deployment.
    - SAPLOCALHOST, SAPGLOBALHOST, and SAPGLOBALHOSTFULL value in the SCS &
    JC profiles must point to the desired hostname/IP. If they don't exist 
    please create and set accordingly.        
    - in the sdmrepository.sdc file, the following                         
    values are set expected with expected host :                           
          <mshost>                                                         
            *hostname**                                                  
         </mshost>                                                         
         <msport>                                                          
            **port -can be found in dev_ms file*                         
         </msport>                                                                               
    Please restart the cluster.                                                                               
    Try to deploy using SDM without the workaround.                                                                               
    If the deployment fails, please paste the exception/error from the lastest sdm log from SDM\program\log directory and corresponding exception from the latest defaultrace file from server0\log directory.
    Hope the above helps.
    Regards,
    Snehal

  • How during deployment my user id has been checked by J2EE engine

    Hi,
    If I want to transport my application, Do I need a valid user ID created in J2EE engine UME. If it is, How during deployment my user id has been checked by J2EE engine.
    Thanx for your time.
    Cheers,
    Sam

    Hi,
    to deploy your application to the J2EE engine you normaly use SDM (Software Deployment Manager). You need a password (no user Id) to deploy via SDM. This password was set up during installation of the Web AS. You can reset this password via SDM command line tool. Have a look at the SDM documentation for details.
    SDM uses the deploy service of the J2EE engine to deploy the application. Therefore SDM connects to the J2EE engine via a username and password that are stored in the secure store (Configtool -> Secure Store). This user is normally identical with the administration user. If you change the password of the administrator you also have to change the password in the secure store. Oterwise you cannot deploy via SDM.
    Regards Helmut

  • How to deploy an EAR or WAR into our J2E(J2EE Engine of SAP)

    I got a solo WAR but I don't know how to deploy it into our J2EE Engine(J2E). If you have any same or similar experience,can you give me some help?
    Any advice is popular. Thanks!

    Hello,
    If you use 6.20 release of J2EE Engine then have a look at  <j2ee root directory>/docs/deploymanual.pdf.
    If you have J2EE Engine 6.40 and an already built war file then most probably the easiest way to assemble it and deploy it will be to use the deploy tool (http://help.sap.com/saphelp_nw04/helpdata/en/35/e3ee3da7138e5be10000000a114084/frameset.htm) Usually we use the NetWeaver Developer Studio to build and deploy J2EE Applications (http://help.sap.com/saphelp_nw04/helpdata/en/fe/a3996fa314f94f8a0c3475b08636d0/frameset.htm).
    Best Regards
    Vyara

  • How to create simple JSP and deploy to J2EE engine?

    Hi,
    I need to create simple JSP pages and deploy it to SAP J2EE engine.. what is the procedure?...I may later add some businness logic but not needed for now.
    Please help
    Thanks,
    Jai

    Gabrie,
    Here are Simple steps,
    In the NWDS
    1) create J2EE -> Web Module Project    (XYZ)
    2) create/add your JSP pages to the project
    3) Right click on your project root and click on 'Build Web Archive' from the context
    3) create J2EE -> Enterprise Application project(EAR)
    4) Right click on your Web Module Project root and click on 'Add to EAR Project' from the context, select the EAR you just created in step 3.
    5)Right click on your EAR project root and click on 'Build WebApplication Archive' from the context
    6)Expand the EAR project node, and right click on the *.ear file, click on 'Deploy to J2EE Engine'.
    7)Enter your SDM password  when prompted,
    You can access you JSP at this url
    http://server:port/xyz/a.jsp
    - Dileep

  • Deployment while the J2EE Engine not getting Connected

    Hello Group,
    Versions : EP6.0 SP14, WAS 6.4 AND NWDS 2.0.9
    I'm new to WD and developed a Welcomecomponent
    and deploying the component using J2EE Engine and given the settings as follows..
    in NWDS -> WINDOWS-> PREFERENCES->SAP Engine Installed on Remote Host->
    Message Server Host: sapep.xxxx.com
    Message Server Port:52100
    and applied all the changes at the time i got a error message "<b>Deployment Aborted</b>"
    The Error Message as follows:
    <b>Dec 8, 2005 12:08:49 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !</b>
    I will apreciate how will let us give mea reply for this
    Thanks in advance also
    Sreedhar

    Hello Deban,
    Thanx for u r reply.,
    My settings Like this:
    sapplm.xxxx.com
    3621
    And i made sapmsI21 3621/tcp entry in my host file also
    and i started the SDM aslo and i refreshed J2EE Engine many times but it's still Depolyment Aborted.
    <b>"Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly "</b>
    Thanks in advance
    Bye

  • Configuration of J2EE engine in NWDS 7.1

    Hi All,
    I need to develop a webdynpro application in NWDS 7.1 and deploy it onto a J2EE engine which is installed on a remote host.
    In NWDS 7.0, in Window> Preferences>SAP J2EE Engine,
    I could specify the remote Remote Server Host and Remote server Port.
    How do I do the same in NWDS 7.1?
    I dont see the "SAP J2EE Engine" option in Window-->Preferences ; in NWDS 7.1.
    Please help in configuring the J2EE server in NWDS 7.1 so that i can deploy my webdynpro application.
    Thanks and Regards,
    Sunil

    Hi Satish,
    I followed the steps you mentioned.
    But I got an "Invalid Syntax error" in the Web browser when I deployed and ran the application.
    The url when i run an application from NWDS 7.0 in the same server starts with
    http://<server_name>:50200/webdynpro/dispatcher/.......
    But the url when i run the application from NWDS 7.1 (with the configurations suggested by you) starts with
    http://<server_name>:-1/webdynpro/dispatcher/.......
    I have followed the steps you suggested.
    Do I have to specify the Port number somewhere? or is there any other configuration which I need to do?
    Please guide me in this.
    Thanks and Regards,
    Sunil

  • Problem in Configuration of J2EE Engine

    Hi All!
    I want to run a program I' ve made but I can't. When I try to run it I get the following message:
    "The J2EE Server name and port number are not configured correctly. Check your settings under 'Preferences>>SAP J2EE Engine'."
    When I go to the settings I write on Message Server Host : "localhost" and on the Message Server Port "8080".
    Does somebody know how to fix this?
    Thanks!
    Alejandro.

    hi,
    Ask your admin Message Server Host  and give that And Message servert port number is you can give 3601.
    Then u can go window-showView - j2eeengine then there displayed the J2ee engine nodes there all three nodes are colored green then the server is UP otherwise ask your admin up the server.
    Then you can deploy ur applcaition in J2ee engine,
    Thanks,
    Lohi.

  • JCO connection tab in disabled mode in sap J2EE engine/webdynpro/local/proj

    Dear all,
    I'm developing the simple webdynpro object using netweaver developer studio, but when i deploy it to sap J2ee engine and go there to set the JCO connection, I find the jco connectiuon tab in the diabled mode. I need to configure the new jco connection in order to run the project. Please suggest.
    thanks,
    Anup.

    Hi Anup,
    You can find service "SLD data supplier" under server->services list.
    Refer following links for configuring SLD and JCO connections:
    Re: Web Dynpro - Problem with (SLD) JCO Connection
    Re: Configuration of SLD
    Regards,
    Bhavik

  • Developer J2EE Engine prerequisite

    Hi,
    We are configuring a development environment for a Ecommerce project. A J2ee engine is installed on developer machine so that, developer can build their own EAR file and deploy in their own J2EE engine. All the developer are using central NWDI.
    My question is, is it enough to install the J2EE engine? wether SCA files related to Ecommerce projects are also needs to be deployed?
    with out any SCA files, on a core J2EE engine, I deployed the Ecommerce project EAR file and tried to configure the XCM settings, but, I am not able to see the navigation tree Links for XCM or others on the admin application.  I just able to see the frame structure of the XCM administration page.
    Thanks & Regards,
    Kiran K Vemula.

    Hi Kiran,
    If you do not deploy required SCA files you will face problem just like which you are facing right now.
    Read Dev. & Ext. Guide. You will come to know which SCA files you need to deploy on your Local J2EE engine to run standard B2B/B2C application. To see XCM admin you also required to deploy supporting files along with other EAR files.
    If you deploy only eCommerce EAR file you will not see XCM admin because files for XCM admin you have not deploy.
    So First deploy all require SCA files as per your Back end CRM/ECC. You will get list of require SCA files from Dev. Ext. GUIDE.
    Once it is done then you deploy your custom eCommerce EAR file. You will see XCM Admin screen.
    I hope this info. will help you to resolve your issue.
    eCommerce Developer

  • Error in Online Deployment patching J2EE Engine

    Hi,
    We are installing the J2EE engine in a BW server with Windows S.O. In step "Deploy Online" we obtain the following error:
    Sep 13, 2006 8:23:22 AM  Info: Start logging to console
    Sep 13, 2006 8:23:22 AM  Info:
    Sep 13, 2006 8:23:22 AM  Info: ============================================
    Sep 13, 2006 8:23:22 AM  Info: =   Starting to execute command 'deploy'   =
    Sep 13, 2006 8:23:22 AM  Info: ============================================
    Sep 13, 2006 8:23:22 AM  Info: Starting SDM - Software Deployment Manager...
    Sep 13, 2006 8:23:23 AM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000
    Sep 13, 2006 8:23:24 AM  Info: SDM operation mode successfully set to: Standalone
    Sep 13, 2006 8:23:25 AM  Info: Initializing Network Manager (50017)
    Sep 13, 2006 8:23:25 AM  Info: Checking if another SDM is running on port 50018
    Sep 13, 2006 8:23:25 AM  Info: -
    Starting deployment -
    Sep 13, 2006 8:23:25 AM  Info: Error handling strategy: OnErrorStop
    Sep 13, 2006 8:23:25 AM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Sep 13, 2006 8:23:25 AM  Info: Update strategy: UpdateLowerVersions
    Sep 13, 2006 8:23:25 AM  Info: Starting deployment prerequisites:
    Sep 13, 2006 8:23:31 AM  Info: Loading selected archives...
    Sep 13, 2006 8:23:31 AM  Info: Loading archive 'E:\18_0-20000118_directory\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'
    Sep 13, 2006 8:23:38 AM  Info: Selected archives successfully loaded.
    Sep 13, 2006 8:23:39 AM  Info: Actions per selected component:
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'1' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060426183247.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'1' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172955.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818153022.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' will not update currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101310.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'1' updates currently deployed development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060119145451.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'1' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101332.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027104030.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050121164722.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'2' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101310.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' will be deployed.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027104030.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606164207.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818152118.0000'/'1' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818152118.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'1' will not update currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101532.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050331133205.0000'/'1' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050331133205.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413100235.0000'/'1' updates currently deployed development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100235.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101532.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818150135.0000'/'1' updates currently deployed development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818150135.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111540.0000'/'1' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101350.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164103.0000'/'1' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606164103.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050121164722.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119123705.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060119123705.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4018.00.0000.20041104140331.0000'/'1' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4017.00.0000.20041104140331.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:40 AM  Info: Ending deployment prerequisites. All items are correct.
    Sep 13, 2006 8:23:41 AM  Info: Saved current Engine state.
    Sep 13, 2006 8:23:41 AM  Info: Starting: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:41 AM  Info: SDA to be deployed: E:\usr\sap\SBD\DVEBMGS00\SDM\root\origin\sap.com\com.sap.lcr.saprfc\SAP AG\1\6.4018.00.0000.20060706111625.0000\lcrsaprfc.ear
    Sep 13, 2006 8:23:41 AM  Info: Software type of SDA: J2EE
    Sep 13, 2006 8:23:41 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Sep 13, 2006 8:24:03 AM  Info: Begin of log messages of the target system:
    06/09/13 08:23:57 -  ***********************************************************
    06/09/13 08:23:59 -  References from application sap.com/com.sap.lcr.saprfc to its loaders done.
    06/09/13 08:23:59 -  Start updating EAR file...
    06/09/13 08:23:59 -  start-up mode is lazy
    06/09/13 08:23:59 -  EAR file updated successfully for 94ms.
    06/09/13 08:23:59 -  Start updating...
    06/09/13 08:24:00 -  EAR file uploaded to server for 719ms.
    06/09/13 08:24:03 -  ERROR: Not updated. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Exception in operation update with application sap.com/com.sap.lcr.saprfc..
                         Reason: com/sap/mw/jco/JCO$Function; nested exception is:
                              java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:682)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              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:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
                              at java.lang.Class.getDeclaredMethods0(Native Method)
                              at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
                              at java.lang.Class.privateGetPublicMethods(Class.java:1778)
                              at java.lang.Class.getMethods(Class.java:832)
                              at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getWithNotSpecifiedMethodInterface(MethodsExtractor.java:121)
                              at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getAllMethodsInBean(MethodsExtractor.java:103)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.getMethodXml(EJBJarParser.java:1168)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processContainerTransaction(EJBJarParser.java:1023)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processAssemblyDescriptor(EJBJarParser.java:924)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:156)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:297)
                              at com.sap.engine.services.ejb.EJBAdmin.buildAppDescriptorBeforeUpdate(EJBAdmin.java:408)
                              at com.sap.engine.services.ejb.EJBAdmin.needUpdate(EJBAdmin.java:341)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.getContainersWhichNeedUpdate(UpdateTransaction.java:537)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.getConcernedContainers(UpdateTransaction.java:493)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:263)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:670)
                              ... 10 more
                         For detailed information see the log file of the Deploy Service.
    06/09/13 08:24:03 -  ***********************************************************
    Sep 13, 2006 8:24:03 AM  Info: End of log messages of the target system.
    Sep 13, 2006 8:24:03 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Sep 13, 2006 8:24:03 AM  Error: Aborted: development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Exception in operation update with application sap.com/com.sap.lcr.saprfc..
    Reason: com/sap/mw/jco/JCO$Function; nested exception is:
         java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Sep 13, 2006 8:24:03 AM  Info: Starting to save the repository
    Sep 13, 2006 8:24:04 AM  Info: Finished saving the repository
    Sep 13, 2006 8:24:04 AM  Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' will be deployed.
    Sep 13, 2006 8:24:04 AM  Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1':
    Failed deployment of SDAs:
    development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' : aborted
    Please, look at error logs above for more information!
    Sep 13, 2006 8:24:04 AM  Info: Starting to save the repository
    Sep 13, 2006 8:24:04 AM  Info: Finished saving the repository
    Sep 13, 2006 8:24:04 AM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Sep 13, 2006 8:24:04 AM  Error: -
    At least one of the Deployments failed -
    Sep 13, 2006 8:24:05 AM  Info: Summarizing the deployment results:
    Sep 13, 2006 8:24:05 AM  Error: Aborted: E:\18_0-20000118_directory\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA
    Sep 13, 2006 8:24:05 AM  Error: Processing error. Return code: 4
    Regards,

    Hi everybody,
    Well, after of the last post where it commented that the possible solution would be to update Java to version 12, the issue continues.
    Now, we have the following error after SAP recommended to deploy the file manually with SDM Tool, the file is lcrsaprfc.ear and show the following error:
    Manifest attributes are missing or have badly formatted value:
    attribute keylocation is missing
    attribute keyname is missing
    attribute keyvendor is missing
    attribute keycounter is missing
    Maybe can be a problem with the file?, format?, build?.
    Thanks for your help and patience.
    Regards,
    Rafa R.R.

Maybe you are looking for