8 Replies Latest reply: Nov 6, 2009 3:04 PM by Marc Hickmann RSS

To undeploy .sca

Ramesh Narayanan
Currently Being Moderated

Hi All,

           Is there any other way to undeploy .sca file apart from JSPM and SDM? If it is possible through telnet pl give the syntax.

 

 

Thanks,

Ramesh.N

  • Re: To undeploy .sca
    Rohanravindra Hardikar
    Currently Being Moderated

    You can do it through SDM. Login to the SDM tool for this.

  • Re: To undeploy .sca
    Muralidhar Chatla
    Currently Being Moderated

    Hi,

     

    Please go through

     

    [Thread|How to Undeploy SCA from NW CE 7.1;

     

    Regards,

    Muralidhar

  • Re: To undeploy .sca
    Ventsi Tsachev
    Currently Being Moderated

    Hello Ramesh,

     

    It is not possible to undeploy SCA file as a whole.

    The SDM and JSPM do not offer such option.

    Instead you have two options:

     

    1.     If your goal is to revert to previous version of the SCA you could deploy the older version and select the option update any version.

    2.     If your goal is to remove application, then you could select all SDA files that are part of the SCA and undeploy them.

     

    You should never try to undeploy the core SCA files because that will break the Java server.

     

    You could use the SDM command line to execute the undeployment.

    Please refer to the SDM command line guide at SDM/program/doc/SDMCommandLineDoc.pdf for through description of all SDM command line options.

     

    In short first you have to stop the SDM server and set it to stand alone mode.

    Then you could run:

    sdm undeploy list=<...> | { compname=<...> compvendor=<...> } [undeploydb=yes|no]

     

    The above mentioned document provides detailed instructions.

     

    You could also undeploy from the Telnet Administrator, but that is not recommended because that way the SDM server is bypassed and the SDM repository is not updated and it will became inconsistent. As result youu2019ll have troubles deploying the same SCA with the SDM/JSPM later.

     

    Regards,

    Ventsi Tsachev

    Technology Development Support (J2EE Engine)

    SAP Labs, Palo Alto, Ca (USA)

  • Re: To undeploy .sca
    Currently Being Moderated

    undeploy {vendor=<...> name=<...>}| list=<...>

                  [on_prerequisite_error = stop | skip_depending]

                  [on_undeploy_error = stop | skip_depending]

                  [workflow = safety | normal]

                  [- help]

     

     

     

     

    WHERE

     

    u2022     name = Specifies the name attribute of a development component.

     

    u2022     vendor = Specifies the vendor attribute of a development component.

     

    u2022     list = Absolute pathname of a xml file, which contains listed name and vendor of deployed components - SDAs and/or SCAs for undeployment. The command with this parameter undeploys one or many SDA and/or SCAs simultaneously.

    Note: u2018name=<...>u2019 and u2018vendor=<...>u2019 must be used together, but cannot be put together with u2018list=<...>u2019 as list must be separate from them.

     

    u2022     on_prerequisite_error - An optional attribute that controls the response to an error in a prerequisite check. Possible values are:

    o     stop - (default) stops the undeployment after the prerequisite check and before actual undeployment.

    o     skip_depending - sets to continue undeployment after an error but only for SDAs/SCAs that do not have other that depend on them. Currently it is used for errors in prerequisite check. For example, if a specified component has depending on it component, then the undeployment item will be skipped.

     

    u2022     on_undeploy_error - An optional attribute that controls the response to an error. Possible values are:

    o     stop - (default) stops the undeployment after the undeployment error. Any missing SDAs/SCAs are not undeployed.

    o     skip_depending - sets to continue undeployment after an error but only for SDAs/SCAs that do not have other that depend on them. Currently it is used for errors in actual undeployment. For example, if a specified component has depending on it component, then the undeployment item will be skipped.

     

    u2022     workflow - An optional attribute that controls the behavior of the J2EE Engine in case of offline undeployment and is similar to the deployment workflow strategies. Possible values are:

    o     normal - the J2EE Engine is restarted only one time in case of offline undeployment

    o     safety - the J2EE Engine is restarted two times in case of offline undeployment. First, the J2EE Engine is stop and started in 'safe' mode with action 'DEPLOY' and then after all the undeployments have been performed it is restarted in 'normal' mode with action NONE

     

     

     

     

    Examples:

     

    undeploy name=MyApp vendor=myvendor.com on_undeploy_error=stop

     

    undeploy list=C:\my\list\UndeployItems.xml on_undeploy_error=skip_depending on_prerequisite_error=skip_depending

     

    Thanks & Regards,

    Sangeetha

     

    Edited by: Lalith Sangeetha on Sep 4, 2009 8:10 AM

     

    Edited by: Lalith Sangeetha on Sep 4, 2009 8:17 AM

     

    Edited by: Lalith Sangeetha on Sep 4, 2009 8:18 AM