Skip to Content

SLT Installation on Netweaver 7.5

Dear all,

This is my first Blog post. I have 8 years of experience in SAP Netweaver Basis, HANA and Solman. I have a tremendous experience on both Implementation and Support projects. Recently I implemented the SLT solution for one of the customers and thought to share the knowledge with everyone. I am also thinking to publish blogs on SLT Configuration from SAP to non-hana target(rare scenario) and system replication setup & DR Invocation for HANA. Please stick around!!!

SAP Landscape Transformation Replication Server (“SLT”) is used for real-time or scheduled data replication from SAP or non-SAP source. This uses trigger-based technology to transfer the data from any source to SAP HANA in real-time. You can even transfer the data to non-hana target provided the source is SAP system.

The SAP LT Replication Server is technically based on SAP Netweaver 7.00 EHP02 (minimum support package 8) or higher. Always prefer to install the latest Netweaver Version.

I chose NW 7.5 SP9 and MS SQL 2012 for installation on OS Windows 2016.

Please use the maintenance planner to plan the new system. Add all the files to download basket.

1. Download the Required Software Files from SAP Market Place

  •  Kernel
  • SWPM
  • SUM
  • Installation Export
  • DB Installation DVD
  • SAP SPS, ST-A/PI and DMIS add-on

2. Run the Pre-Requisite Checker on the Operating System and meet the requirements.

Please put a check mark for DB, PAS and ASCS as below and ensure to configure the pre-requisites as shown by the checker.

3.  Install DB (MS SQL)

Kindly ensure to enable .NET Framework 3.5 before installing the DB.

 

Now run setup.exe from DVD(51047515 – MS SQL 2012)

 

 

 

Go on next by choosing the relevant data and finish the installation.

Please remember to choose Collation as “SQL_Latin1_General_CP850_BIN2” for Unicode. Kindly refer the installation guide for more details.

4. Install SAP

Run SWPM as an admin and choose the below selection in case you wanna install Standard System.

 

provide the System Name and FQDN accordingly and provide a master password.

Provide the Domain Model as per the Customer Policy and Provide the MS SQL DB instance details.

In the below screenshot, provide the kernel file path.

Choose the domain for Host agent and by default the SAP SID would be SAP.

Master Password will be picked

Provide the Installation Export path

Master Password will be picked automatically, you can still  choose your own password.

Mandatory to Enable for NW 7.5

Provide the instance number for ASCS and PAS and ensure the relevant SAP ports are not blocked.

 

Skip SLD registration or connect it to Solman.

Do not create Message Server ACL

Choose to install the gateway integrated in the ASCS

 

Finish the installation

 

5. Perform Post Installation Tasks

Run SGEN

Apply the license

Parameter Tuning

Configure Op modes

Configure OSS connection

Maintain the system details in saprouter

create a client if required and perform client copy

6. Upgrade Netweaver SP to N-1(SP 9)

Ensure to download SUM 2.0 as SAP NW 7.5 does not support SUM 1.0

Always download the latest version of SUM

Start SUM

 

Import Latest SPAM and provide the stack.xml

Provide the password for DDIC and SAPSERVICESID

Click Next

Apply the missing notes shown below via SNOTE and release the TR.

 

Ensure that the queue is calculated as expected

Skip the modification Adjustment

provide the shadow instance number and keep going further

Lock the Development

 

Please take a backup as mentioned in the SUM tool and proceed with the execution phase

Again take a backup at the end of Execution phase and proceed with post-processing.

Upgrade finished successfully.

 

Now run SGEN for all the components

7. Install SLT Component

Install DMIS 2011_1_731 for SAP NW 7.5. Choose the SP level as that of source.

Launch SAINT–> load from app server

Run the upgrade in background

Finish the installation and you should now be able to carryout with SLT configuration.

Also you can install the ST-A/PI component in the same way(Version 01S_731 for SAP NW 7.5)

 

 

To report this post you need to login first.

12 Comments

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

  1. Bartosz Jarkowski

    Hello,

    very nice first blog! Congratulations!

    I hope to see more soon 🙂

    Just one question – shouldn’t you install the SQL for SAP using a SQL4SAP script?

    Best regards

    Bartosz

     

    (1) 
  2. Lingarajkumar Nadagoudara Post author

    Dear Bartosz

    Thank you so much. Please find below my response on your question.

    Yes indeed, SQL4SAP script is the simplest way of installing MS SQL server. But the installation will use the C: drive by default for the entire DB Files. Thus preferred manual installation to choose different drives for Data, Log and Backups. Please refer the note “1923745 – Change installation drive during MS SQL Server installation” for complete details. Hope this answers:)

    (2) 
    1. Matt Fraser

      I completely agree. The SQL4SAP script is fine for small or non-production instances, but it won’t really do for anything larger or busier. Installing the database to the C: drive is, in my opinion, unacceptable. I wrote about this in a couple of blog posts three years ago: https://blogs.sap.com/2015/01/23/sql-server-2012-installation-recommendations/ and https://blogs.sap.com/2015/01/26/sql-server-configuration-pre-sap-installation/.

      Cheers,
      Matt

      (2) 
        1. Matt Fraser

          Well, that’s the point; I don’t think you can. Basically, avoid the SQL4SAP script and do it manually, following the instructions in the SAP installation guide (or better yet, in my blog! 🙂 ).

          (1) 
        2. Bartosz Jarkowski

          You can undermine any statement this way. How do you install Oracle with SQL4SAP script?

          Of course, you need to choose the methods accordingly to what are you trying to achieve. In the example from this post, there is no word about setting up any cluster.

           

          (1) 
          1. Yogesh Patel

            Well… if I go through SQL installation steps on this blog… its missing lots other more important information such as – What option to be selected under SQL feature? what are the post steps and so on. But this blog is not about SQL installation 🙂

            I just want to say that SQL4SAP script is not perfect solution. Everyone have their own way to do it according to requirements and SAP SQL installation guide also have section called – Installing the SQL Server XXXX Database Server Software Manually

             

             

            (2) 
      1. Bartosz Jarkowski

        The manual configuration of the SQL Server might be tricky, so the SQL4SAP should be used always when possible. Otherwise, you can easily run into issues, because you forget to, for example, set the correct collation. And instead of using 20 screens you can just execute one or two commands.

        BTW. Excellent blogs! I want more!

        (2) 
    2. Bartosz Jarkowski

      Hello,

      thank you for your reply.

      I have asked the question because I didn’t notice that you do anything special during the SQL installation – so in my opinion, it would be easier to use SQL4SAP. But now I understand your motivation.

      Looks like we have a nice technical discussion, which is great and unfortunately not so common on SAP Community.

       

      (2) 
      1. Yogesh Patel

        I am totally agreed with this comment. Well as I mentioned everyone have their own way to do things but end of the day – We want to have problem free DB instance up and running for SAP.

        Cheers,

        Yogesh

        (2) 
  3. Lingarajkumar Nadagoudara Post author

    Dear All..

    Many thanks for your feedback. This is really boosting me up!!!!! I wanted to keep the blog simple and cover the entire installation part, so skipped few of the screenshots.

    (0) 

Leave a Reply