SDM Deployment for SAP-XIAFC

Hi All,
I am trying to deploy SAP-XIAFC.sca using SDM. However, there are some dependent components which need to be deployed as a pre-requisite for this.
*com.sap.aii.af.ra.ms.sonic.client
com.sap.aii.af.jmsproviderlib
Can somebody please let me know where do iI find these pre-requisites ? Any help would be appreciated.
Thanks and Regards,
Pranav

Normally you would download the whole XI/PI service pack/stack and not the individual components, via here:
http://service.sap.com/swdc
SAP CAF 7.00
SAP CAF-UM 7.00
SAP J2EE ENGINE 7.00
SAP J2EE ENGINE CORE 7.00
SAP JAVA TECH SERVICES 7.00
SAP SOFTW. DELIV. MANAGER 7.00
SAP TECH S 7.00 OFFLINE
SAP_IKS_7.00
UME ADMINISTRATION 7.00
XI ADAPTER FRAMEWORK 7.00
XI ADAPTER FRAMEWORK CORE
XI CONNECTIVITY SE 7.00
XI CONTENT SAP_ABA 700
XI CONTENT SAP_BASIS 7.00
XI PCK 7.00
XI TOOLS 7.00
You then get all the pre-requisites.  We normally load all the SDA/SCA files into the SDM and then we don't get the issues

Similar Messages

  • Quick question on BOE deployment for SAP BW with 3 system landscape

    Client has SAP BW environment with 3 system landscape: Dev, QA, Production
    Should BOE be installed seperately on 3 different machines for each of them?
    Or is there any best practice for this?
    Thanks,
    Henry

    Hello Henry,
    yes - i would recommend this Setup. Technically there is no need for it but on an organisational/development/deployment level it makes more sence.
    I often saw it at customers that Dev and Q&A is on virtual machines and Prod is on a physically machines. Saves some Hardware costs.
    Regards
    -Seb.

  • SAP SDM Deployment failed

    Hello everybody i have a problem with my SAP ERP Installation the Error is :
    An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step :uncaught exception: nw.sdm.deploymentErrorWithLog: SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log for more information. (in script unknown, line 0:
    And here are my logfile , i hope you can help me for a solution. I have restart the SAP System and start it again and click retry but nothing happen, the same error comes again.
    Jan 19, 2010 7:34:14 AM  Info: Initial deployment: Selected development component 'tc/kmc/bc.uwl.ui/wd_pp'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'1' will be deployed.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'com.sap.portal.nav.ws.NavigationWSEar'/'sap.com'/'SAP AG'/'7.0014.20071210113331.0000'/'2' will not be deployed because containing software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210193159''/'2' will not be deployed.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'3' will not update currently deployed development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'2'.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'3' will not update currently deployed development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'1'.
    Jan 19, 2010 7:34:14 AM  Info: No action: Selected development component 'com.sap.prt.ws.container'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'2' will not be deployed because containing software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152356''/'2' will not be deployed.
    Jan 19, 2010 7:34:14 AM  Info: Ending deployment prerequisites. All items are correct.
    Jan 19, 2010 7:35:49 AM  Info: Saved current Engine state.
    Jan 19, 2010 7:35:49 AM  Info: Starting: Initial deployment: Selected development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3' will be deployed.
    Jan 19, 2010 7:35:49 AM  Info: SDA to be deployed: C:\usr\sap\DRC\DVEBMGS00\SDM\root\origin\sap.com\caf\eu\gp\ws\msosrv\MAIN_APL70VAL_C\3\963790\sap.com_cafeugpwsmsosrv.sda
    Jan 19, 2010 7:35:49 AM  Info: Software type of SDA: J2EE
    Jan 19, 2010 7:35:49 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jan 19, 2010 7:35:56 AM  Info: Begin of log messages of the target system:
    10/01/19 07:35:50 -  ***********************************************************
    10/01/19 07:35:51 -  Start updating EAR file...
    10/01/19 07:35:51 -  start-up mode is lazy
    10/01/19 07:35:51 -  EAR file updated successfully for 47ms.
    10/01/19 07:35:51 -  Start deploying ...
    10/01/19 07:35:51 -  EAR file uploaded to server for 32ms.
    10/01/19 07:35:56 -  ERROR: NOT deployed. The Deploy Service returned the following error:
                         For detailed information see the log file of the Deploy Service.
                         Exception is:
                         com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
                              at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
                              at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
                              at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
                              at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
                              at java.lang.Thread.run(Thread.java:534)
    10/01/19 07:35:56 -  ***********************************************************
    Jan 19, 2010 7:35:56 AM  Info: End of log messages of the target system.
    Jan 19, 2010 7:35:56 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jan 19, 2010 7:35:56 AM  Error: Aborted: development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071210153525''/'3':
    Caught exception during application deployment from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
    Exception is:
    com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
         at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
         at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
         at java.lang.Thread.run(Thread.java:534)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
    Jan 19, 2010 7:35:56 AM  Info: Starting to save the repository
    Jan 19, 2010 7:35:57 AM  Info: Finished saving the repository

    Hi,
    Check below thread:
    /message/441671#441671 [original link is broken]
    Thanks
    Sunny

  • How to deploy BI  on EHP1 for SAP NetWeaver Composition Environment 7.1

    Hello Gurus,
    i have installed SAP NetWeaver 7.01 SR1 SP3 ABAP Trial Version  at home on vista 32 bits.
    it's running well...
    next i have installed EHP1 for SAP NetWeaver Composition Environment 7.1 - Preview Version
    and follow this guide :
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b057d7e3-b89e-2b10-1e9e-c426e967f8e1
    the portal is running well....coooool.. ( http//:localhost:50100/irj/portal)
    after i follow this documentation to create some cubes on BI abap trail (client 001).
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4096b8fc-6be7-2a10-618e-b02a5e5e798f
    i create my report with the query designer,
    and i see my bi report with transaction RSRT and ABAP WEB tab ( http://localhost:80000)
    it's running well....whaooouuu !!!!
    Now i'm lost, i would like to deploy my bi report on the portal, but i don't know what i must do.
    ( and when i try with the query designer or rsrt + java web i have a error message )
    - perhaps create an user communication  between portal/bi abap  where ?
    - how to deploy bi java on portal (EHP1 for SAP NetWeaver Composition Environment 7.1)
    by the way, i can't find the bi post install template in the configuration wizard on the the portal...
    thank's for your help.
    Florent,
    Edited by: Florent BUTTY on Mar 24, 2009 1:43 PM

    Hi,
    Can you please tell me what is the diff between 7.01 & 7.1? if you can share any docs, is highly appreciated.
    Thanks,
    Kiran

  • Rapid Deployment Solution for SAP CRM - Landscape

    Hi
    For the first time we have applied the Rapid Deployment Solution for SAP CRM ITSDO into our new DEV system.  The activation of this RDS creates 2 transports  (one WORKBENCH, one CUSTOMIZING)
    I now need to apply the RDS to our QA and PRD systems - is it enough to just transport the 2 transports or do I need to do the entire activation again in both QA and PRD systems?
    I would really appreciate any assistance here.
    Thanks

    Hi Leigh,
    Just wondering how you got on with those transports.. Was it sufficient for you to release the Solution Builder transports to target system or did you need to carry out manual activities in the target system?
    Also, What did you do with regard to activating the reporting client in the target system? did the transport take care of everyting?
    Any assistance would be greatly appreciated.

  • How to configure Engine/SDM for SAP J2EE  Server

    Hi Experts,
    I deployed the EAR file on J2EE Server.
    This EAR file is linked to WebModuleProject (xyz)whic has a WAR file.
    This WAR file contains one JSP. (test_jsp.jsp)
    Then on following the URL
    <a href="http://server:port/xyz/test_jsp.jsp">http://server:port/xyz/test_jsp.jsp</a>
    i m getting the following error message:
    Nov 29, 2007 11:01:40 AM /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 !
    How do i configure engine/SDM?
    What is SDM engine?

    I configured the SDM/Engine successfully
    but still following the url
    <a href="http://server:port/xyz/test_jsp.jsp">http://server:port/xyz/test_jsp.jsp</a>
    i m getting the following error
    404   Not Found
      The requested resource /WebModuleProject/test_jsp.jsp is not available
      Details:   File [WebModuleProject/test_jsp.jsp] not found in application root of alias [/] of J2EE application [sap.com/com.sap.engine.docs.examples].
    Please experts help me to dig out this problem
    Can anybody suggest me why i m getting the error?

  • SDM deployment error during XI 3.0 installation

    (nobody in the PI forum replied, so I'm reposting here)
    I need to install a sandbox using this old version. Installation base is 6.40 WebAS plus Java addon SR1. System installs fine, however during final SDM deployment I get a problem during the J2EE engine restart:
    errors:
    service sld ================= ERROR =================
    Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
    and around 20 more services which have a dependency on sld
    sld does not start because:
    /Applications/SLD#sap.com/com.sap.lcr#com.sap.lcr.sagent.BuilderDirector#J2EE_
    GUEST#328####e4cd3451819411dec19c001d72bd0666#SAPEngine_Application_Threadimpl:3_0##0#0#Error#1#com.sap.lcr.sagent.BuilderDirector#Plain###Can't access http store#
    OR:
    SAPEngine_System_Threadimpl:5_32##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service sld error. Nested exception is: com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='sld_3012', A
    rguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key sld_3012
    at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:109)
    at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:78) ...........
    further suspicious warnings:
    Aug 5, 2009 12:51:17 AM Info: No action: Selected development component 'com.sap.aii.af.ms.svc'/'sap.com'/'SAP AG'/'3.0.0920041027171222.0000' will not be deployed because containing software component 'SAP-XIAFC'/'sap.com'/'SAP AG'/'1000.3.0.9.1.20041028052722' will not be deployed.
    and this for around 20 more components from comp.sap.aii*
    What went wrong, and, what can I do to fix this? Redeploy sld ? I could not find how.
    Java version is latest 1.4.2 x86_64 from IBM (1.4.2_13) for my architecture (x86_64 Linux RHEL5), DB is maxdb 7.6
    Any help is appreciated, Thanks.
    Sanjay

    Can you please check thet if you have given a central SLD then that SLD is up and running as you are getting the message.
    Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
    Please check this note it will solve your issue.
    Note 994433 - XI AF on J2EE Engine terminates with OutOfMemoryError
    you can manually start th services.
    Thanks Rishi Abrol

  • J2ee Admin User locked on SDM Deployment - BI 7.0 and EP 7.0

    Hi,
    We had a recent issue on BI iview publishing from the BEX WAD 7.0 in our Production Portal server.
    The BEX WAD had the error " Java communication error"
    " An Error occured during communication with the BI Components of the J2ee engine"
    We traced down to identify that the current stack NW 7.0 SP14 BI Components had issues and had to patch to the next level
    However, during deployment of the patch using SDM, the components (all) failed posting the following error. The SDM deployment got struck and the J2ee Engine user j2ee_admin was locked.
    Only a restart of the j2ee engine is allowing us to get the Visual Admin connected. But the SDM deployment again is failing and admin user gets locked. Is there any tested solution to solve this.
    Kindly help asap.
    Trace:
    SDM:
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxxx] with user name: [j2ee_admin]check your login information.
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]          
    J2ee Engine:
    Error while connecting
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: This call must be performed from a system thread.
         at com.sap.engine.services.security.login.SecuritySession.setExpirationPeriod(SecuritySession.java:479)
         at com.sap.engine.services.security.login.TicketGenerator.getSecuritySession(TicketGenerator.java:180)
         at com.sap.engine.services.security.login.SecurityContext.load(SecurityContext.java:313)
         at com.sap.engine.services.rmi_p4.Message.loadContextObject(Message.java:345)
         at com.sap.engine.services.rmi_p4.Message.parseMessage(Message.java:239)
         at com.sap.engine.services.rmi_p4.Message.getByteArrayInputStream(Message.java:314)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:212)
         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)

    Hi Anup,
    The restart unlocks the j2ee engine admin user and i am able to login to Visual admin and SDM and not otherwise (SDM is hanged and doesnot allow another session and hence only restart helps me to get into SDM again)
    Admin Pwds reset etc from config tool secure store and all possible solutions have been tried before restart.
    However, after restart, when we try to deploy again, the deploy fails saying the same msg
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxx] with user name: [j2ee_admin]check your login information.
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
    Any clues ?
    Regards
    Venkat.

  • Error in Deployment of SAP ESS 100 SP16 ess/au/addr

    Hello Gurus
    Greetings !..
    I am trying to Deploy SAP ESS 100 SP16 for Netweaver 2004s using SDM but getting error while i deploy in the phase ess/au/addr.
    Please check for the log below if any one can helpout soon....
    May 22, 2007 10:16:50... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:16:50... Info: Finished successfully: development component 'ess/at/fam'/'sap.com'/'MAIN_xss04VAL_C'/'680352'/'0', grouped by
    May 22, 2007 10:16:50... Info: Starting to save the repository
    May 22, 2007 10:16:52... Info: Finished saving the repository
    May 22, 2007 10:17:04... Info: Starting: Update: Selected development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'680388'/'0' updates currently deployed development component 'ess/at/pdata'/'sap.com'/'MAIN_ERP05VAL_C'/'766644'/'0'.
    May 22, 2007 10:17:04... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\at\pdata\MAIN_xss04VAL_C\0\680388\sap.com_essatpdata.sda
    May 22, 2007 10:17:04... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:04... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:06... Info: Begin of log messages of the target system:
    07/05/22 22:17:04 - ***********************************************************
    07/05/22 22:17:04 - Start updating EAR file...
    07/05/22 22:17:04 - start-up mode is lazy
    07/05/22 22:17:04 - EAR file updated successfully for 78ms.
    07/05/22 22:17:04 - Start updating...
    07/05/22 22:17:04 - EAR file uploaded to server for 219ms.
    07/05/22 22:17:05 - Successfully updated. Update took 734ms.
    07/05/22 22:17:05 - Deploy Service status:
    07/05/22 22:17:05 - Application : sap.com/essatpdata
    07/05/22 22:17:05 -
    07/05/22 22:17:05 - sap.com/essatpdata - WEBDYNPRO
    07/05/22 22:17:05 - ***********************************************************
    May 22, 2007 10:17:06... Info: End of log messages of the target system.
    May 22, 2007 10:17:06... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:06... Info: Finished successfully: development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'680388'/'0', grouped by
    May 22, 2007 10:17:07... Info: Starting to save the repository
    May 22, 2007 10:17:08... Info: Finished saving the repository
    May 22, 2007 10:17:21... Info: Starting: Initial deployment: Selected development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'681439'/'0' will be deployed.
    May 22, 2007 10:17:21... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\au\MAIN_xss04VAL_C\0\681439\sap.com_ess~au.sda
    May 22, 2007 10:17:21... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:21... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:25... Info: Begin of log messages of the target system:
    07/05/22 22:17:21 - ***********************************************************
    07/05/22 22:17:21 - Start updating EAR file...
    07/05/22 22:17:21 - start-up mode is lazy
    07/05/22 22:17:21 - EAR file updated successfully for 188ms.
    07/05/22 22:17:21 - Start deploying ...
    07/05/22 22:17:22 - EAR file uploaded to server for 859ms.
    07/05/22 22:17:24 - Successfully deployed. Deployment took 2547ms.
    07/05/22 22:17:24 - Application : sap.com/ess~au
    07/05/22 22:17:24 -
    07/05/22 22:17:24 - sap.com/ess~au - WEBDYNPRO
    07/05/22 22:17:24 - ***********************************************************
    May 22, 2007 10:17:25... Info: End of log messages of the target system.
    May 22, 2007 10:17:25... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:25... Info: Finished successfully: development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'681439'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0'
    May 22, 2007 10:17:25... Info: Starting to save the repository
    May 22, 2007 10:17:27... Info: Finished saving the repository
    May 22, 2007 10:17:39... Info: Starting: Initial deployment: Selected development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0' will be deployed.
    May 22, 2007 10:17:39... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\au\addr\MAIN_xss04VAL_C\0\681471\sap.com_essauaddr.sda
    May 22, 2007 10:17:39... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:39... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:40... Info: Begin of log messages of the target system:
    07/05/22 22:17:39 - ***********************************************************
    07/05/22 22:17:39 - Start updating EAR file...
    07/05/22 22:17:39 - start-up mode is lazy
    07/05/22 22:17:39 - EAR file updated successfully for 94ms.
    07/05/22 22:17:39 - Start deploying ...
    07/05/22 22:17:40 - EAR file uploaded to server for 297ms.
    07/05/22 22:17:40 - ERROR: Not deployed. Deploy Service returned ERROR:
    java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr..
    Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
    com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
    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: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
    at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
    at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
    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.deploy(DeployServiceImpl.java:552)
    ... 10 more
    For detailed information see the log file of the Deploy Service.
    07/05/22 22:17:40 - ***********************************************************
    May 22, 2007 10:17:40... Info: End of log messages of the target system.
    May 22, 2007 10:17:40... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:40... Error: Aborted: development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr..
    Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
    com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    May 22, 2007 10:17:40... Info: Starting to save the repository
    May 22, 2007 10:17:42... Info: Finished saving the repository
    May 22, 2007 10:17:54... Info: Starting: Initial deployment: Selected software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0' will be deployed.
    May 22, 2007 10:17:54... Error: Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0':
    Failed deployment of SDAs:
    development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0' : aborted
    Please, look at error logs above for more information!
    Hope for a prompt response.
    Reply awaited urgently....
    Thanks in Advance
    Thanks & Best Regards
    Ashish

    Hello Gerard Christopher
    Yes i got the problem solved, actually SAP ESS 600 & SAP MSS 600 are the component we have to use. As we were on WAS 7.00 and ERP 2005 so
    SAP ESS 600
    SAP MSS 600
    SAP PSS 600
    SAP ASR 600
    SAP PCUI_GP 600
    Try with this you will able to solve.
    Thanks & best Regards
    Ashish

  • SDM Deployment fails - Dependency caf/core/ear missing

    crosspost from: SDM Deployment fails - Dependency caf/core/ear missing
    deploying a DC from NWDS into SDM the following Exception is thrown:
    07.01.2008 16:20:38 /userOut/daView_category (eclipse.UserOutLocation) [ThreadDeploy Thread,5,main] INFO:
    002Additional log information about the deployment
    <!LOGHEADERSTART/>
    <!HELPManual modification of the header may cause parsing problem!/>
    <!LOGGINGVERSIONhttp://1.5.3.7185 - 630/>
    <!NAME[/usr/sap/IT1/DVEBMGS00/SDM/program/log/sdmcl20080107151422.log]/>
    <!PATTERNhttp://sdmcl20080107151422.log/>
    <!FORMATTERcom.sap.tc.logging.TraceFormatter(%24d %s: %m)/>
    <!ENCODINGUTF8/>
    <!LOGHEADEREND/>
    Jan 7, 2008 4:14:22 PM Info:
    Starting deployment
    Jan 7, 2008 4:14:22 PM Info: Error handling strategy: OnErrorStop
    Jan 7, 2008 4:14:22 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Jan 7, 2008 4:14:22 PM Info: Update strategy: UpdateAllVersions
    Jan 7, 2008 4:14:22 PM Info: Starting deployment prerequisites:
    Jan 7, 2008 4:14:23 PM Info: Loading selected archives...
    Jan 7, 2008 4:14:23 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23425innobis.dewkbtmetadata.ear'
    Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23426innobis.dewkbtear.ear'
    Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23427innobis.dewkbtdictionary.sda'
    Jan 7, 2008 4:14:25 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23428innobis.dewkbtpermissions.ear'
    Jan 7, 2008 4:14:26 PM Info: Selected archives successfully loaded.
    Jan 7, 2008 4:14:26 PM Error: Unresolved dependencies found for the following SDAs:
    1.: development component 'wkbt/ear'/'innobis.de'/'NetWeaver Developer Studio'/'20080107144202'/'0'
    dependency:
    name: 'caf/core/ear'
    vendor: 'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    Deployment will be aborted.
    Jan 7, 2008 4:14:26 PM Error: Prerequisites were aborted.
    Jan 7, 2008 4:14:27 PM Error: Error while creating deployment actions.
    system:
    sap.com/SAP-JEECOR 7.00 SP10 (1000.7.00.10.0.20061026144500)
    sap.com/SAP-JEE 7.00 SP10 (1000.7.00.10.0.20061026144500)
    I checked http://<srv>/sap/monitoring/ComponentInfo
    the missing 'caf/core/ear' is not listed, however several other CAFs are:
    sap.com caf/core null (964250) SAP AG MAIN_APL70VAL_C 20061212133926 sap.com/CAF
    sap.com caf/core/dict null (964586) SAP AG MAIN_APL70VAL_C 20061212131613 sap.com/CAF
    sap.com caf/core/gp/facade/backgroundco/ear null (964227) SAP AG MAIN_APL70VAL_C 20061212134201 sap.com/CAF
    sap.com caf/core/metadata null (963689) SAP AG MAIN_APL70VAL_C 20061212133653 sap.com/CAF
    etc....
    Is it possible to deploy this missing caf-ear component supplementary?
    I have the strange feelings caf/core/ear is something 7.1 CE only related....
    thanks for any hint!
    kai

    Kai, I didn't mean to offend you. But good forum practice is to avoid duplicate posts.
    Regards,
    \-- Vladimir

  • SDM deploy af atleast one item aborted

    Hi,
    We are not able to deploy ear file on server and getting exception "Deploy of atleast one item aborted". Till now we have tried below solutions for fixing the same:
    Restart SDM both from MMC and Console.
    Changed SDM password.
    Enable/Disable SDM from JCMON.
    Restart J2EE server.
    Changed NWDS workspace and deploy fresh ISA application.
    Tried to deploy from SDM GUI.
    After all these attempts we are still not able to deploy. Attached is SDM Log file for this problem.
    Looking forward for valuable thoughts on this......
    Dec 31, 2014 2:10:46 AM  Info: Start file transfer to E:\usr\sap\CRQ\JC00\SDM\program\temp\temp3728619115795722000Saltestapp_ear.ear Dec 31, 2014 2:10:47 AM  Info: File transfer of E:\usr\sap\CRQ\JC00\SDM\program\temp\temp3728619115795722000Saltestapp_ear.ear finished for 296 ms. Total file size is 30508322 bytes. Dec 31, 2014 2:10:47 AM  Info: The SDM client uses an old SDM client API. Dec 31, 2014 2:10:47 AM  Info: -------------------------- Starting deployment ------------------------ Dec 31, 2014 2:10:47 AM  Info: Error handling strategy: OnErrorStop Dec 31, 2014 2:10:47 AM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop Dec 31, 2014 2:10:47 AM  Info: Update strategy: UpdateAllVersions Dec 31, 2014 2:10:47 AM  Info: Starting deployment prerequisites: Dec 31, 2014 2:10:47 AM  Info: Loading selected archives... Dec 31, 2014 2:10:47 AM  Info: Loading archive 'E:\usr\sap\CRQ\JC00\SDM\program\temp\temp3728619115795722000Saltestapp_ear.ear' Dec 31, 2014 2:10:47 AM  Info: Selected archives successfully loaded. Dec 31, 2014 2:10:47 AM  Info: Actions per selected component: Dec 31, 2014 2:10:47 AM  Info: Initial deployment: Selected development component 'Saltestapp_ear'/'sap.com'/'localhost'/'2014.12.31.02.10.28'/'0' will be deployed. Dec 31, 2014 2:10:47 AM  Info: Ending deployment prerequisites. All items are correct. Dec 31, 2014 2:10:47 AM  Info: Saved current Engine state. Dec 31, 2014 2:10:47 AM  Info: Starting: Initial deployment: Selected development component 'Saltestapp_ear'/'sap.com'/'localhost'/'2014.12.31.02.10.28'/'0' will be deployed. Dec 31, 2014 2:10:47 AM  Info: SDA to be deployed: E:\usr\sap\CRQ\JC00\SDM\root\origin\sap.com\Saltestapp_ear\localhost\0\2014.12.31.02.10.28\temp3728619115795722000Saltestapp_ear.ear Dec 31, 2014 2:10:47 AM  Info: Software type of SDA: J2EE Dec 31, 2014 2:10:47 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) ***** Dec 31, 2014 2:10:54 AM  Info: Begin of log messages of the target system: 14/12/31 02:10:47 -  *********************************************************** 14/12/31 02:10:48 -  Start updating EAR file... 14/12/31 02:10:48 -  start-up mode is lazy 14/12/31 02:10:51 -  EAR file updated successfully for 2806ms. 14/12/31 02:10:51 -  Start deploying ... 14/12/31 02:10:54 -  EAR file uploaded to server for 2892ms. 14/12/31 02:10:54 -  ERROR: Not deployed. Deploy Service returned ERROR:                      com.sap.engine.services.rmi_p4.MarshalException: Exception when trying to read the original exception.; nested exception is:                      java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError                      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:732)                      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:714)                      at com.sap.engine.services.rmi_p4.Call.getResultStream(Call.java:200)                      at com.sap.engine.services.deploy.DeployService_Stub.deploy(DeployService_Stub.java:507)                      at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:709)                      at com.sap.engine.deploy.manager.DeployManagerImpl.deploy(DeployManagerImpl.java:513)                      at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:188)                      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:48)                      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:128)                      at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97)                      at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)                      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:331)                      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:683)                      Caused by: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError                      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1292)                      at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887)                      at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811)                      at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695)                      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288)                      at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887)                      at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811)                      at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695)                      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288)                      at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887)                      at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811)                      at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695)                      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288)                      at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887)                      at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811)                      at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695)                      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288)                      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:336)                      at com.sap.engine.services.rmi_p4.Call.getResultStream(Call.java:195)                      ... 32 more                      Caused by: java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError                      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1070)                      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364)                      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1336)                      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280)                      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068)                      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364)                      at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:376)                      at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:998)                      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:331)                      at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:837)                      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1326)                      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280)                      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068)                      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364)                      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1336)                      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280)                      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068)                      at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364)                      at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1336)                      at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280)                      at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068)                      at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:285)                      at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:147)                      at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:332)                      at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)                      at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)                      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:104)                      at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)                      For detailed information see the log file of the Deploy Service. 14/12/31 02:10:54 -  *********************************************************** Dec 31, 2014 2:10:54 AM  Info: End of log messages of the target system. Dec 31, 2014 2:10:54 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) ***** Dec 31, 2014 2:10:54 AM  Error: Aborted: development component 'Saltestapp_ear'/'sap.com'/'localhost'/'2014.12.31.02.10.28'/'0': Caught exception during application deployment from SAP J2EE Engine's deploy service: com.sap.engine.services.rmi_p4.MarshalException: Exception when trying to read the original exception.; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC) Dec 31, 2014 2:10:54 AM  Info: Starting to save the repository Dec 31, 2014 2:10:54 AM  Info: Finished saving the repository for 74 ms. Dec 31, 2014 2:10:54 AM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process. Dec 31, 2014 2:10:54 AM  Error: ---------------- At least one of the Deployments failed ---------------
    Kind Regards,
    Vishal Sobti

    Hi Vihsal,
    Can you please try to kill this from Operating System level. One more question, are you deploying this first time? Reason of asking this question is your below error code.
    "ERROR: Not deployed. Deploy Service returned ERROR:   com.sap.engine.services.rmi_p4.MarshalException: Exception when trying to read the original exception.; nested exception is:   java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException"
    Could you please also confirm about the database please.
    Please try the below step as well if not done yet
    Go to SDM Directory and enter the below
    sdm jstartup "mode=integrated"
    Thanks,
    Hamendra

  • Error in SDM-deploy Step

    <h5>Good Morning Gentleman,</h5>
    <h5>"When i'm trying to import a transport order to our productive system the import fails in step SDM-deploy with the following error:</h5>
    <h5>20120228122646 Info   :Starting Step SDM-deploy at 2012-02-28 12:26:46.0143 +0:00
    20120228122646 Info   :start deployment of archives:http://sapsps.sonaesierra.com:50004
    20120228122646 Fatal  :caused by Exception:com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.:The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
    com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
         at com.sap.cms.tcs.beans.deployer.DeployConnector.openConnection(DeployConnector.java:160)
         at com.sap.cms.tcs.beans.TCSDeployBean.performDirectDeployment(TCSDeployBean.java:194)
         at com.sap.cms.tcs.beans.TCSDeployObjectImpl0_0.performDirectDeployment(TCSDeployObjectImpl0_0.java:1342)
         at com.sap.cms.tcs.beans.TCSDeploy_Stub.performDirectDeployment(TCSDeploy_Stub.java:1296)
         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:331)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy225.performDirectDeployment(Unknown Source)
         at com.sap.cms.tcs.core.SDMDeployTask.processImport(SDMDeployTask.java:302)
         at com.sap.cms.tcs.core.SDMDeployTask.process(SDMDeployTask.java:366)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:447)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:176)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:113)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:648)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:620)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1640)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1637)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2817)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:1042)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2866)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         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:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    20120228122646 Info   :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2012-02-28 12:26:46.0306 +0:00"</h5>
    <h5>I'm new to NWDI and related subjects. I've already checked:</h5>
    <h5>1. Port 50004 is available in the productive system</h5>
    <h5>2. J2EE Visual Administrator in productive is accessible by j2ee_admin</h5>
    <h5>3. j2ee_admin isn't locked in productive system</h5>
    <h5>What more should i check? What could be the reason behind this error?</h5>
    <h5>Thank you.</h5>
    <h5>Best Regards,</h5>
    <h5>Pedro Gaspar</h5>

    Good Morning Kumar,
    If i tell you what happened you're going to laugh... But i'll tell you anyway.
    After watching your post i went to the CMS Landscape Configurator in order to look into the configuration. I noticed that the Selected Tool for deployment in the Productive Runtime system was configured as Deploy Controller (this is a NW 7.01 and as far as i've read before... in this version it's advisable to configure it as you told me in your post - SDM Deploy, thanks for that).
    So i tried to change it, but nothing happened, i've tried a second time, but the changes wouldn't take effect and no message was generated. I've spent a few hours trying to understand what was happening... So i told to myself, let me try it with another browser (was using Firefox 3.6.27, changed to IE 9.0.8112) and when trying to change the runtime system configuration a message outputs... "... More than one name server configured in SLD"
    Immediately searched and got SAP note 1118009 - SLD name-server configuration error in CMS. After executing note steps i was able to change the runtime system tool for deployment, and i could finish the transport.
    The difference a message and the browser version can do in your life
    Thanks for your reply, which helped me solve the problem.
    Best Regards,
    Pedro Gaspar

  • SDM deployment failed (DeployManagerException)

    Dear programmers,
    Since yesterday I'm trying to deploy an EAR file with NetWeaver Developer Studio. But, each time I get this error:
    Apr 25, 2007 10:59:54... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 25, 2007 10:59:56... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 25, 2007 10:59:56... Error: Aborted: development component 'NewsEAR'/'sap.com'/'localhost'/'2007.04.24.11.16.39':
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [cp22383-a] with user name: [admin]
                        Check your login information.
                        Exception is:
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Apr 25, 2007 11:00:33... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Apr 25, 2007 11:00:33... Error: -
    At least one of the Deployments failed -
    We did reset the SDM password in de Configtool and in the RemoteGui.bat. All processes seem to work, because they are green.
    We appreciate your help.
    Regards,
    Adri

    We found the solution while looking at my last question, which was almost the same. Thnx anyway
    If you go to User Administration and change the password there, when next time you log in, in the portal you will get an notification that the password is expired. Change it to your liking and your problem is solved
    Adri Kodde

  • How to find and install the Portal Development Kit (PDK) for SAP Enterprise

    Hi ,
    I have the following question regarding thePortal Development Kit (PDK) for SAP Enterprise Portal 6.0. We have Enterprise Portal 6.0 up and running.
    1> How Do I find whether we already have this inported in the EP environment: I have admin and super admin role and trying to find '*java' in the Role. But didn't find one. Does that mean we don't have this imported already?
    2> I have tried to Find out the PDK( which is also a Business Content) in SDN in the Portal Business content link (https://www.sdn.sap.com/sdn/contentportfolio.sdn) , but haven't found. Where from I download this business content?
    3> What are the special steps that need to be taken to import this and make it working?
    Thanks
    Arunabha

    Hi Arunabha,
    1. Note that the search is case sensitive. Therefore you should search for java and Java.
    2. Download from: https://www.sdn.sap.com/sdn/downloaditem.sdn?res=/html/PDK60_download.htm
    3. Deploy with SDM: http://help.sap.com/saphelp_nw04/helpdata/en/22/a7663bb3808c1fe10000000a114084/content.htm
    Hope that helps,
    Yoav.

  • SDM deployment

    i am trying to deploy some missing components and get the following error. I have checked the j2ee_admin in the abap stack for client 001 and the password is the same for visual administrator and in secure store. any ideas?
    ===========================================================================
    Deployment started Fri Feb 01 08:21:29 GMT 2008
    ===========================================================================
    Starting Deployment of com.sap.ip.bi.broadcasting
    Deployment of com.sap.ip.bi.broadcasting finished successfully (Duration 4781 ms)
    Starting Deployment of com.sap.ip.bi.broadcasting.kmmimes
    Deployment of com.sap.ip.bi.broadcasting.kmmimes finished successfully (Duration 4828 ms)
    Starting Deployment of com.sap.ip.bi.portalheartbeat
    Deployment of com.sap.ip.bi.portalheartbeat finished successfully (Duration 4594 ms)
    Starting Deployment of com.sap.ip.bi.portallogger
    Deployment of com.sap.ip.bi.portallogger finished successfully (Duration 4531 ms)
    Starting Deployment of com.sap.ip.bi.portalnavigation
    Deployment of com.sap.ip.bi.portalnavigation finished successfully (Duration 4515 ms)
    Starting Deployment of com.sap.ip.bi.portalrfc
    Deployment of com.sap.ip.bi.portalrfc finished successfully (Duration 4516 ms)
    Starting Deployment of com.sap.ip.bi.portalrfctest
    Deployment of com.sap.ip.bi.portalrfctest finished successfully (Duration 4484 ms)
    Starting Deployment of com.sap.ip.bi.biloggingconfig
    Aborted: development component 'com.sap.ip.bi.biloggingconfig'/'sap.com'/'SAP AG'/'7.0007.20060316173253.0000', grouped by software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.7.0.20060319093500':
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [OFCOMTOLS039] with user name: [J2EE_ADMIN]                     Check your login information.                     Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Deployment of com.sap.ip.bi.biloggingconfig finished with Error (Duration 6594 ms)
    Starting Deployment of BI-IBC
    Aborted: software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.7.0.20060319093500':
    No further description found.
    Deployment of BI-IBC finished with Error (Duration 3968 ms)

    Hello Mike,
    Your issue is described in note 997810:
    If deployment fails with the error:                                                                               
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.         
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [sapmef1d] with user name: [Administrator] Check your login information.                                        
    Exception is:
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext.
    [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)                                          
    Either the connection details in Secure Store are incorrect, or the j2ee engine is not running at all. First check the admin/port/<SID>entry in Secure Store and make sure it corresponds to the p4 port on the dispatcher. If the j2ee engine is not running (no jlaunch processes on os level), check the std_<XXX> and dev_<XXX> files in  the instance work folder, located on the same level as the j2ee one.
    Regards,
    Ventsi Tsachev
    Technology Development Support (J2EE Engine)
    SAP Labs, Palo Alto, Ca (USA)

Maybe you are looking for

  • How can I get my system in and out of DOS mode?

    How do I get my system in and out of DOS mode?

  • Settings wont open?

    ok so i have a white ipod touch 4g ios 5 and i just put a passcode on my ipod after a couple of minutes i tap settings and its just a blank page then i waited and it just went back on the home screen

  • Asset Doc Reversal

    Hi All, When i try to reverse an asset document by selecting from Ab08 & reversing it through AIST, sys is not picking the line item selected in AB08, instead it is selecting the last transaction which is settled in the asset i.e., the last line item

  • Install failed. Exit code 6

    Recently purchased and downloaded Premiere Pro CS5.5, however the install repeatedly fails. Here's the error report. Any clues as to a fix would be great. Thanks. Exit Code: 6 -------------------------------------- Summary ---------------------------

  • 24" Case Warping??

    My 24" iMac has a new problem, the white plastic on the front, directly above where the optical drive sits, has began warping. If i push on it up and down the length of the right side of the panel, it will go a few millimeters before it reaches the L