Skip to Content
avatar image
Former Member

Autoinstall lot of ABAP application server

Good day, people!

I would like to know, if it is possible to somehow "simplify" my life in installing a large number of the same ABAP-dialogue application servers for a large number of machines of one stand. For example, just over 50 computers.

Is it possible to install a ABAP-dialog applicastion server on one of the machines using ./sapinst And the other 49 ABAP-dialog application servers get by copying separate directories from the previous reference machine and then editing the profiles?

Has anyone encountered similar problems? With what tools did this issue solve?

* Oh yeah, all machines from the Linux family

Or is the plan, that I see myself, banal and impracticable?

1) Write a .bash script for the preinstallation steps (Install the required packages, Create users with the same uid and password, Edit ulimit, Edit kernel parameters, Execute other SAP requirements for installing the ABAP instance, Mount NFS-folder from the shared database server and etc.)

2) Next, copy directories, such as /sapmnt, /usr/ sap from our reference machine, on which SAP ABAP was installed via ./sapinst to the rest of the machine colony.

3) Generate profiles for each of the ABAP instances

I would like to ask, is such a solution "workable"? If it is workable, it would be excellent.

It would be possible to distribute this script (First the reference server clones itself to another server, then these 2 servers clone themselves to 2 more servers, then 4 -> 4, 8 -> 8 and etc. =)

I am more interested in the 2nd step:

-- What are the main directories (it is important to include in the copying of directories) and what configuration files need to be corrected after the copying process?

I also want to "git" the key directories on the reference machine before installing ABAP via ./sapinst, then to see the changed directories/files so that 100% will not miss anything.

P.S.: I hope to receive your answer. If everything works out, I'm ready to share the solution with the end =)

P.P.S: I apologize for my English. I hope that you understood me =)

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Apr 04, 2017 at 11:09 AM

    Hello Igor,

    The installation of a dialog instance should not take that long.

    I agree that if you automate things with a script, you might be able to do it faster in the end.

    However, such "duplication process" using a script will not be supported by SAP, meaning that if the script does not work you would be on your own, and if the instance does not work correctly SAP would not help either.

    The only supported procedure (at least that I am aware of) is to use the SWPM ("sapinst") tool to install the dialog instances.

    About the sapmnt folder, it must exist "physically" at the SAP Global Host (usually the server where the ASCS/SCS instance is installed) and then it should be mapped (NFS-mounted) to all the application servers, so all instances access the same "/sapmnt" folder. The SAP system expects that all instances are accessing the same /sapmnt folder. If each instance has its own, local /sapmnt, unpredictable issues can occur.

    Best regards,


    Add comment
    10|10000 characters needed characters exceeded