This blog is outdated – see the blog on SL Toolset 1.0 SPS 20 instead:
https://blogs.sap.com/2017/05/22/sl-toolset-1.0-sps-20-improved-software-logistics-tools/

Overview on tools delivered with SL Toolset 1.0 SPS 19

Availability: SL Toolset 1.0 SPS 19 is available since February 7th 2017.
What’s in: compared with SPS 18, no new tool joined the SL Toolset 1.0

Further information on the SL Toolset SPS 19:

“nZDM for SAP NetWeaver Java” 1.0 SP 19

Offering

  • implement Support Packages, patches, updates, OS-, DB-, JVM-, hardware – changes and other for SAP Java-stack systems with minimal technical downtime
  • Target Products:
    • SAP Enterprise Portal 7.02, 7.3x, 7.4, 7.5
    • SAP Business Process Management and SAP Process Orchestration
      releases 7.3 incl. EHPs, 7.4 and 7.5 (see SAP Note 2039886; logon required)

Changes with SL Toolset SPS 19

  • Support for SAP Manufactuing Integration and Intelligence (MII)
    (currently restricted – check SAP Note 2336479 for latest information)

More information

Software Provisioning Manager 1.0 SP 19

Offering
With software provisioning manager, get latest SAPinst version that enables provisioning processes for several products and releases for all supported platforms – get support of latest products, versions and platforms, including latest fixes in tool and supported processes + benefit from unified process for different product versions.
Changes with SL Toolset SPS 19

General:

  • Improved documentation in the parameter file for unattended execution mode of Software Provisioning Manager
  • New platform versions (OS/DB) enabled and platform-specific improvements
    • Linux On Power LE (SAP HANA 2.0)
    • IBM DB2 for z/OS Call Level Interface (CLI) failover feature
  • Consistency Check for Software Provisioning Manager Data units

System copy:

  • Available option for SAP HANA, Oracle, SAP ASE, IBM DB2 and MS SQL Server to refresh database content only, without reinstalling the database or Kernel for ABAP systems
  • ABAP System Copy Export with separate Kernel now possible: The kernel of the system that is copied does not need to be replaced
  • Option to restrict access to the Database Export file

More information

Software Update Manager 1.0 SP 19

Offering

  • Modern user interface, downtime reduction capabilities for various scenarios
  • Business Downtime reduction: buffer import of customer transport requests for target release
  • Business Downtime reduction: Zero Downtime Option (ZDO) to reduce SUM related downtime to one re-start
  • Support of customer releases exclusively: no use of stack.xml, the SUM needs only buffer import of customer transport requests for target release
  • Combine SAP system update with migration to SAP HANA (DMO: database migration option)
  • System Conversion to SAP S/4HANA

Changes with SL Toolset SPS 19

  • “DMO without System Update” (see DMO guide and this blog)
  • DMO: combine update of SAP Solution Manager to 7.2 with migration to SAP HANA database
    scenario is now generally available (see this blog)
  • DMO: partitioning information can be provided via file (see DMO guide)
  • nZDM ABAP: full support for customer transport only scenario
  • ZDO: Check for blacklisted objects in customer transports added
  • ZDO: Support for Microsoft SQL Server added (available on request)

More information

Standalone Task Manager for Lifecycle Management Automation 1.0 SP 01

Offering

Stand-alone task manager for lifecycle management automation is a framework to execute below automated configuration templates

  • SSL configuration templates validates the SSL configuration settings both, for ABAP and for Java environments and generates HTML reports that can be used for further analysis. It also performs SSL configuration automatically and describes required manual tasks.(SAP Note 1891360)
  • SAP ERP <-> SAP CRM, template to establish connectivity between SAP ERP system and SAP CRM
  • Mobile Configuration templates for Backend, Gateway and SUP (SAP Note 1891358)
  • HANA user management and SLT (System Landscape Transformation) configuration (SAP Note 1891393)

Changes with SL Toolset SPS 19

  • No changes

More information

SAPSetup 9.0

Offering

SAPSetup offers easy and reliable functionality for installations of different scales:

  • Installation of frontend products without administrator permissions
  • Remote installations from Administration PC
  • Configuration and export of installation packages containing multiple products
  • Consistency check
  • Central log file analysis

Changes with SL Toolset SPS 19

  • SAPSetup with the latest corrections as outlined in the SAP Notes below, for example, remote installation re-designed

Further information:

CTS Plug-In 2.0 SP 19

Offering

  • Generic CTS to connect your non-ABAP applications with CTS
  • New user interfaces and new features for CTS
  • Central Change and Transport System (cCTS) as technical infrastructure for Change Request Management (ChaRM) and Quality Gate Management (QGM) in SAP Solution Manager 7.1 SPS 10 and higher

Changes with SL Toolset SPS 19

  • Improvements for CTS Plug-In are no longer delivered with SL Toolset, but will come with the respective SAP NetWeaver support packages, for more information see SAP Note 1665940
  • For SAP Solution Manager systems 7.1 and higher a CTS Plug-In is still required and therefore part of its software stack

More information

 

AddOn Installation Tool and Support Package Manager Version 7.x/0064

Offering

SPAM/SAINT provides easy access to lifecycle management processes by being part of the SAP NetWeaver AS ABAP stack and by being accessible directly via SAP GUI. This way you are able to control different kinds of implementation processes, such as installing, upgrading or updating ABAP software components. SPAM/SAINT Updates themselves can be applied to ABAP-based systems independent of underlying SAP NetWeaver component versions.

Changes with SL Toolset SPS 19 (SPAM/SAINT patch level 64)

  • Support deliveries that are bigger than 2 GB
  • Show ‘F’alse attributes in package tree
  • Extension of prerequisite SAP Notes check by optional minimal SAP Notes version
  • Adjustments/Weakening of Add-On compatibility checks (keep check) during add-on changes in SAINT

More information

Scenario “Up-to-date Installation”

Up-To-Date Installation refers to an enhanced process for the installation of new system at any chosen stack level. The new improved process enables complete planning in Maintenance Planner, which generates a consolidated stack XML and archives, which are later consumed by Software Provisioning Manager and Software Update Manager.

More information

Boris Rubarth

Product Management SAP SE, Software Logistics

To report this post you need to login first.

14 Comments

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

  1. Martin Rathke

    There is a bug in sum10sp19pl01 and pl02 with Oracle. sum10sp17pl10 works fine. All Client Settings were  verified and are correct.

    the KBA 2364655 was unspecific and dont help. An incident is open, but no specific help or Support.

    SAPup> Starting subprocess in phase ‘DBQUERY_PRE’ at 20170309130238
    *CENV: BR_ISP=1
    ENV: DBMS_TYPE=ora
    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
     *DBENV: ORACLE_HOME=J:\SUM\abap\tmp
    *DBENV: ORACLE_SID=KPC
    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    ENV: PATH=J:\SUM\abap\exe;H:\oracle\KPC\11204\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Dell\SysMgt\shared\bin;C:\Program Files (x86)\Dell\SysMgt\oma\bin;C:\Program Files (x86)\Dell\SysMgt\idrac;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\;C:\Program Files\NetApp\MPIO\;C:\Program Files\NetApp\Windows Host Utilities\;H:\usr\sap\KPC\SYS\exe\uc\NTAMD64
    ENV: RSEC_SSFS_DATAPATH=\\S500SAP003\sapmnt\KPC\SYS\global\security\rsecssfs\data
    ENV: RSEC_SSFS_KEYPATH=\\S500SAP003\sapmnt\KPC\SYS\global\security\rsecssfs\key
    *CENV: SAPCHECK=J:\SUM\abap\tmp
    *CENV: SAPDATA_HOME=J:\SUM\abap\tmp
    ENV: SAPSYSTEMNAME=KPC
    *DBENV: dbs_ora_schema=SAPRKU
    ENV: dbs_ora_tnsname=KPC
    ENV: rsdb_ssfs_connect=1
    *DBENV: (auth_shadow_upgrade)
    PWD: J:\SUM\abap\tmp

    EXECUTING J:\SUM\abap\exe\brconnect.EXE -u -c -f dbstate -RDB
    BR0801I BRCONNECT 7.40 (17)
    BR0280I BRCONNECT time stamp: 2017-03-09 13:02:38
    BR0262I Enter database user name[/password]:
    BR0280I BRCONNECT time stamp: 2017-03-09 13:02:38
    BR0301E SQL error -12557 at location db_connect-3, SQL statement:
    ‘CONNECT SYSTEM/**********@KPC’
    Error while trying to retrieve text for error ORA-12557
    BR0310E Connect to database instance KPC failed

    BR0280I BRCONNECT time stamp: 2017-03-09 13:02:38
    BR0804I BRCONNECT terminated with errors
    SAPup> Process with PID 9108 terminated with status 3 at 20170309130238!

     

    (1) 
    1. Boris Rubarth Post author

      Did you already check SAP Note 2328526, especially the section titled
      “SUM is not able to check the password of SYSTEM DB for specific setups”?

      (0) 
      1. Jean-François Petitbon

        Hello,

        We are facing the same issue as Martin. We are using SUM1.0SP09pl04, and the CHKSYSPWD has failed into the PREP_INPUT/DBQUERY_PRE Phase :

        $>  more CHKSYSPWD.LOG
        SAPup> Starting subprocess with PID 1787 in phase 'DBQUERY_PRE' at 20170412111209
          *CENV: BR_ISP=1
            ENV: DIR_LIBRARY=/users/apg00/SUM/abap/exe
            ENV: LD_LIBRARY_PATH=/users/apg00/SUM/abap/exe:/usr/sap/ZCI/SYS/exe/run:/oracle/client/11x_64/instantclient
            ENV: NLS_LANG=AMERICAN_AMERICA.US7ASCII
            ENV: ORACLE_BASE=/oracle
         *DBENV: ORACLE_HOME=/users/apg00/SUM/abap/tmp
         *DBENV: ORACLE_SID=ZCI
            ENV: PATH=/users/apg00/SUM/abap/exe:.:/users/login/zciadm:/usr/sap/ZCI/SYS/exe/run:/bin:/usr/bin:/sbin:/usr/sbin:/usr/ccs/bin:/usr/ucb
          *CENV: SAPCHECK=/users/apg00/SUM/abap/tmp
          *CENV: SAPDATA_HOME=/users/apg00/SUM/abap/tmp
            ENV: SAPSYSTEMNAME=ZCI
            ENV: dbms_type=ORA
         *DBENV: dbs_ora_schema=SAPR3
            ENV: dbs_ora_tnsname=ZCI
         *DBENV: (auth_shadow_upgrade)
            PWD: /users/apg00/SUM/abap/tmp
        [...]
        BR0301E SQL error -12154 at location db_connect-2, SQL statement:
        'CONNECT SYSTEM/*******@ZCI'
        ORA-12154: TNS:could not resolve the connect identifier specified

        The preceding check during Phase PROFREAD was ok :

        $> more CHKSYSPWD.SAV
        
        #!--------------------------------------------------------------
        #!---- MASKING file "/users/apg00/SUM/abap/log/CHKSYSPWD.LOG"
        #!---- TIME: 20170412111209  PHASE: PREP_INPUT/DBQUERY_PRE
        #!--------------------------------------------------------------
        
        SAPup> Starting subprocess with PID 26874 in phase 'PROFREAD' at 20170412105632
          *CENV: BR_ISP=1
            ENV: DIR_LIBRARY=/usr/sap/ZCI/SYS/exe/run
            ENV: LD_LIBRARY_PATH=/usr/sap/ZCI/SYS/exe/run:/oracle/client/11x_64/instantclient
            ENV: NLS_LANG=AMERICAN_AMERICA.US7ASCII
            ENV: ORACLE_BASE=/oracle
            ENV: ORACLE_HOME=/oracle/ZCI/112_64
            ENV: ORACLE_SID=ZCI
            ENV: PATH=/usr/sap/ZCI/SYS/exe/run:.:/users/login/zciadm:/bin:/usr/bin:/sbin:/usr/sbin:/usr/ccs/bin:/usr/ucb
          *CENV: SAPCHECK=/users/apg00/SUM/abap/tmp
          *CENV: SAPDATA_HOME=/users/apg00/SUM/abap/tmp
            ENV: SAPSYSTEMNAME=ZCI
            ENV: dbms_type=ORA
            ENV: dbs_ora_schema=SAPR3
            ENV: dbs_ora_tnsname=ZCI
         *DBENV: (auth_shadow_upgrade)
            PWD: /users/apg00/SUM/abap/tmp
        
        EXECUTING /usr/sap/ZCI/SYS/exe/run/brconnect -u -c -f dbstate -RDB
        [...]
        BR0342I Database instance ZCI is open
        [...]
        

         

        As pointed out by Martin, the BIG difference is located at the environment variable ORACLE_HOME:

        Phase PROFREAD:     ENV: ORACLE_HOME=/oracle/ZCI/112_64

        Phase DBQUERY_PRE:  *DBENV: ORACLE_HOME=/users/apg00/SUM/abap/tm

        I hope that SAP SUM support team will answer quickly to the incident we open, as we gave the root cause on a silver plate…

        Best regards,

        Jean-François Petitbon

        (0) 
        1. Boris Rubarth Post author

          Unfortunately neither Martin nor you did comment on the question if you have considered the section titled “SUM is not able to check the password of SYSTEM DB for specific setups” in SAP Note 2328526.

          (0) 
          1. Jean-François Petitbon

            Hello Boris,

            I apologize not to have tell anything concerning the SAP note 2328526, but we do have checked our Solaris 11 environment if /oracle/<sid>/112_64/lib was used instead of instant client, as described into the note, but we are not that case.

            So this proposed solution is useless for us, and I think that it was the same for Martin.

            Last thing, I don’t want to be rude, but I don’t understand why we customer we have to be very strict with our <sid>adm environment, if the SAP tool (SAP SUM into phase DBQUERY_PRE here) has the “right” to be less strict… Have you ever seen an ORACLE_HOME magically standing into a tmp directory of an ugrade tool ? Seeing you answer about reading a SAP note for such a light workaround for an issue where we pointed out a possible interesting root cause is disappointing.

            But we have an opened incident on that subject and I hope that the answer of the support will be better focused on the strange things we pointed out in detail in order to help to correct what may really be a bug on SAP SUM side.

            Best regards,

            Jean-François PETITBON

            (0) 
  2. Peter Barefield

    did you guys solve this ?

    SUM isn’t picking up variables in my case too :

     

    SAPup> Starting subprocess in phase ‘DBQUERY_PRE’ at 20170428131203
    *CENV: BR_ISP=1
    ENV: DBMS_TYPE=ora
    ENV: JAVA_HOME_CCR=f:\oracle\EBP\102\jre\1.5.0
    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
    *DBENV: ORACLE_HOME=D:\usr\sap\EBP\SUM\abap\tmp

    (0) 
  3. Hazem Gerafi

    Make sure TNS_ADMIN is there in your environment; pointing to the directory where tnsnames.ora is .

    You need to restart SUM after you add the environment variable.

     

    Thanks,

    Hazem

    (0) 
  4. Ina Warnke

    Hello SAP,

    do you have a solution for this error?

    I have the same problem.

    TNS_ADMIN=\\polvc510\sapmnt\C51\SYS\profile\oracle

    is correct.

    SAPup> Starting subprocess in phase ‘DBQUERY_PRE’ at 20170509132609
    *CENV: BR_ISP=1
    ENV: DBMS_TYPE=ora
    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
    *DBENV: ORACLE_HOME=e:\usr\sap\SUM\abap\tmp
    *DBENV: ORACLE_SID=C51
    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    ENV: PATH=e:\usr\sap\SUM\abap\exe;C:\Legato\nsr\bin;E:\oracle\C51\12102\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;E:\usr\sap\C51\SYS\exe\uc\NTAMD64
    ENV: RSEC_SSFS_DATAPATH=\\polvc510\sapmnt\C51\SYS\global\security\rsecssfs\data
    ENV: RSEC_SSFS_KEYPATH=\\polvc510\sapmnt\C51\SYS\global\security\rsecssfs\key
    *CENV: SAPCHECK=e:\usr\sap\SUM\abap\tmp
    *CENV: SAPDATA_HOME=e:\usr\sap\SUM\abap\tmp
    ENV: SAPSYSTEMNAME=C51
    *DBENV: dbs_ora_schema=SAPPOL
    ENV: dbs_ora_tnsname=C51
    ENV: rsdb_ssfs_connect=1
    *DBENV: (auth_shadow_upgrade)
    PWD: e:\usr\sap\SUM\abap\tmp

    EXECUTING e:\usr\sap\SUM\abap\exe\brconnect.EXE -u -c -f dbstate -RDB
    BR0801I BRCONNECT 7.40 (29)
    BR0280I BRCONNECT time stamp: 2017-05-09 13:26:09
    BR0262I Enter database user name[/password]:
    BR0280I BRCONNECT time stamp: 2017-05-09 13:26:09
    BR0301E SQL error -1 at location db_connect-3, SQL statement:
    ‘CONNECT SYSTEM/********@C51’
    Error while trying to retrieve text for error ORA-00001
    BR0310E Connect to database instance C51 failed
    SAPup> Process with PID 836 terminated with status -1073741819 at 20170509132610!

     

    Best regards, Ina

    (0) 
    1. Boris Rubarth Post author

      Hi Ina,

      please open an incident on component BC-UPG-TLS-TLA, and describe which steps you already checked, especially concerning the section in SAP note 2328526 .

      Thanks, Boris

      (0) 
  5. MDLZ INDIA OSS

    Hi Boris,

     

    Can you comment if it is possible to run multiple session of SUM on the same host on the newer version. If yes then how ?

     

    Regards,

    Subhash

     

    (0) 

Leave a Reply