Skip to Content

Hi All,

Sometimes happend that you’re going to patch the system, or deploying an upgrade… and something critical goes wrong.

You would like to re-deploy the package again, but the system cannot be started again, and neither the JSPM works… so…

This is an alternative way to deploy packages on a SAP system, rather using the JSPM tool:

  1. Loging in to Telnet Administrator from your SAP system on OS level (with your <sidadm> user)
    1. Command: telnet localhost 5<SystNumber>08
    2. Login with your <j2ee_admin> user


  1. Create a file “deploylist.txt” on your file system and on separate lines enter the full path anf file name of the package which you wish to deploy: SERVERCORE, ENGINEAPI, BASETABLES, J2EEAPPS, J2EEFRMW, etc…
    1. Example:     /usr/sap/trans/EPS/in/
  2. Run Command:deploy list=\<path>\deploylist.txt version_rule=all
  3. System should start the deployment (Java Stack will be rebooted)
To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Andy Silvey

    Hi Simone,


    this is a very useful blog, I use the command line deployment a lot as it is much faster for small sda’s and patches.


    A few more tips, in NW 7.1 onwards, the command line deployment is made using the TextConsole which is located in:






    (another tip, I have observed with new 7.31 installations that the file contains bad ^M characters at the end of each line, these characters need to be removed otherwise the will not execute)


    regarding the actual deploy command, the switch at the end, version_rule=all is used to OVERWRITE any version, so be careful with that one.


    Also, this OSS Note


    OSS 1677600 – How to undeploy the BI4.0 application from SAP Netweaver 7.3


    discusses using the same tool for undeployments.


    And one more thing, it is not necessary to list your sda’s in a text file you can directly point to your sda with the deploy command.


    All the best,



      1. Andy Silvey

        Hi Simone,




        it really is a useful tool, I use it a lot, and if you need to do small patches, .sda’s ,  .ear’s  , non-core sca’

        s  then it is great and fast


        if you deploy core sca’s with it, eg wdruntime etc, and the sca requires an instance restart then you will lose focus on the tool and have to login again


        All the best,



  2. Hemanth Kumar



    If the system doesn’t start, then even telnet would not work.

    In that case only the extramile tool would be useful.

    Also check:

    sap note 1715441 – How to deploy .SDA files on J2EE servers on

                       Netweaver release 7.1 and higher




  3. Former Member

    Hi Simone,


    can you please tell me in case of an error during a deployment using telnet where can I find the logs ?!


    Thank you and best regards!

    1. Hemanth Kumar

      Hi ,



      Hope you are doing good.

      You will get more info in:

      -> the telnet log itself.
      ->the deploy* files in the work directory
      -> and as Andy mentioned, in the default traces.



      Thank you!




      Kind Regards,




      SAP AGS


Leave a Reply