IP Library › Granted Patent US 12,613,735
Granted Patent B2
US 12,613,735 · App. 18/141,676 · Granted Apr 28, 2026

System, method, and utility for SAP start/stop automation

Inventor: Bradley Dees (Galveston, TX)
Assignee: Insight Direct USA, Inc.
G06F9/485
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,613,735
App. No.
18/141,676
Filed
May 1, 2023
Granted
Apr 28, 2026
Kind
B2
Art Unit
2197
USPC
718/102
Abstract

A method of starting and stopping SAP processes across a plurality of servers via an SAP start/stop utility is presented. A system-scale SAP start/stop script is executed by specifying an action and a type, the action identifying one of START, STOP, and RESTART, the type identifying categories of server to be stopped or started, the categories comprising database servers, message servers, and application servers. In response to the action including STOP or RESTART, the system-scale SAP start/stop script halts, in order and among servers in categories matching the type: application servers, message servers, and database servers. In response to the action including START or RESTART, the system-scale SAP start/stop script then starts, in order and among servers in categories matching the type: database servers, message servers, and application servers.

Claims (45)

1 . A method of starting and stopping System Analysis Program Development (SAP) processes across a plurality of servers on an SAP platform via an SAP start/stop utility, the method comprising:

executing a system-scale SAP start/stop script by specifying an action and a type, the action identifying one of START, STOP, and RESTART, the type identifying categories of server to be stopped or started, the categories comprising database servers, message servers, and application servers;

halting, via the system-scale SAP start/stop script and in response to the action including STOP or RESTART, in order, among servers in categories matching the type: application servers, message servers, and database servers; and

subsequently starting, via the system-scale SAP start/stop script and in response to the action including START or RESTART, in order, among servers in categories matching the type: database servers, message servers, and application servers.

2 . The method of claim 1 , further comprising:

evaluating, via the system-scale SAP start/stop script, a status of each server in a category matching the type; and

reporting to an administrator user interface, via the system-scale SAP start/stop script, the status of each server in a category matching the type.

3 . The method of claim 1 , further comprising, prior to executing the system-scale SAP start-stop script:

executing a system group-scale SAP start/stop script by specifying an action, a type, and an system group; and

identifying systems within the system group via the group-scale SAP start/stop script; and

wherein executing the system-scale SAP start/stop script comprises separately executing an instance of the system-scale SAP start/stop script local to each of the identified systems, using the action and type specified when executing the system group-scale SAP start/stop script.

4 . The method of claim 3 , wherein identifying systems within the group comprises comparing the system group to a record of systems, by group, using the system group-scale SAP start/stop script.

5 . The method of claim 4 , wherein the system group is a software environment, and the record of systems, by group, is a record of systems belonging to each environment.

6 . The method of claim 4 , wherein the record of systems further specifies at least one of a message server type and a number of application servers associated with each of the systems.

7 . The method of claim 3 , further comprising:

generating, via the system-scale SAP start/stop script, a confirmation key; and

prompting a user to reproduce the confirmation key; and

confirming that the user has reproduced the confirmation key before halting any of the plurality of servers.

8 . The method of claim 1 , further comprising confirming HugePage settings before starting a database server.

9 . The method of claim 3 , wherein:

an instance of the system-scale SAP stop/start script is saved locally within a database server of each of the systems; and

the system group-scale SAP start/stop script is executed from an SAP admin terminal on the SAP platform but external to the systems.

10 . The method of claim 1 , wherein halting application and message servers via the system-scale SAP start/stop script comprises executing a stop/clean subscript for each such server, the stop/clean script configured to first terminate SAP processes on the respective server, then extirpates any residual inter-process communication (IPC) processes on the respective server.

11 . A System Analysis Program Development (SAP) platform comprising a plurality of servers, the SAP platform comprising:

a plurality of software environments, each of the plurality of software environments comprising at least one system encompassing a database server, a message server, and an application server, all from among the plurality of servers;

an SAP admin terminal communicatively coupled to all of the plurality of servers, the SAP admin terminal including a user interface; and

an SAP start/stop utility distributed across the SAP admin terminal and each of the database servers, the SAP start/stop utility configured to:

receive arguments via the user interface specifying an action and a server type;

halt SAP processes on a subset of the plurality of servers matching the server type, in response to the action specifying STOP or RESTART; and

start SAP processes on the subset of the plurality of servers matching the server type, in response to the action specifying START or RESTART.

12 . The SAP platform of claim 11 , wherein the database server is an Oracle database server.

13 . The SAP platform of claim 11 , wherein the message server is an SCS or ASCS server.

14 . The SAP platform of claim 11 , wherein the SAP start/stop utility is further configured to:

generate a confirmation key;

prompt a user to reproduce the confirmation key via the user interface; and

confirm that the user has reproduced the confirmation key before halting any of the plurality of servers.

15 . The SAP platform of claim 11 , wherein the arguments received by the SAP start/stop utility via the user interface further specify at least one environment from among the plurality of environments, and wherein the SAP start/stop utility halts and/or stops only SAP processes on servers within systems falling within the at least one environment.

16 . The SAP platform of claim 15 , wherein the SAP start/stop utility is additionally configured to report a status of each system falling within the at least one environment.

17 . The SAP platform of claim 15 , wherein the SAP start/stop utility comprises:

a system-scale SAP start/stop script configured to start and halt SAP processes; and

a system group-scale SAP start/stop script configured to identify systems falling within the at least one environment, and call instances of the system-scale SAP start/stop script for each system falling within the at least one environment.

18 . The SAP platform of claim 17 , wherein both the system-scale SAP start/stop script and the system group-scale SAP start/stop script are directly runnable from the SAP admin terminal user interface, such that the system scale SAP start/stop script can be executed either directly by an administrator via the user interface, or indirectly by the system group-scale SAP start/stop script.

19 . The SAP platform of claim 17 , wherein:

an instance of the system-scale SAP start/stop script is distributed to each of the database servers, such that execution of the system-scale SAP start/stop script for a particular system comprises running the system-scale SAP script stored locally on a respective database sever of the particular system.

20 . The SAP platform of claim 17 , wherein the system group-scale SAP start/stop script identifies systems walling within he at least one environment by reference to a record identifying the system makeup of each environment.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 1, 2023
From: DEES, BRADLEY
To: INSIGHT DIRECT USA, INC.
Reel/Frame 063495/0020 →
Continuity (2)
Provisional Application 63459502 · Apr 14, 2023
Related Publication 20240345871A1 · Oct 17, 2024
References Cited (26)
US 7533163B1 · Zenz et al. · 2009 [cited by applicant]
US 7917629B2 · Werner · 2011 [cited by applicant]
US 7925764B2 · Charters et al. · 2011 [cited by applicant]
US 8015541B1 · Srinivasan et al. · 2011 [cited by applicant]
US 8290998B2 · Stienhans et al. · 2012 [cited by applicant]
US 9209992B2 · Nelke et al. · 2015 [cited by applicant]
US 9785516B2 · Schefe et al. · 2017 [cited by applicant]
US 9994438B2 · Sahiner · 2018 [cited by applicant]
US 10496677B2 · Voss et al. · 2019 [cited by applicant]
US 10747730B2 · Dimitrov et al. · 2020 [cited by applicant]
US 11068241B2 · Swope et al. · 2021 [cited by applicant]
US 11507897B2 · Partridge · 2022 [cited by applicant]
US 20030172002A1 · Spira et al. · 2003 [cited by applicant]
AT 451780T · 2009 [cited by applicant]
CA 2795756C · 2020 [cited by applicant]
CN 104484730B · 2018 [cited by applicant]
CN 111240950B · 2022 [cited by applicant]
CN 110222960B · 2022 [cited by applicant]
CN 110989983B · 2022 [cited by applicant]
CN 115048205B · 2023 [cited by applicant]
EP 1250669A4 · 2006 [cited by applicant]
FR 3075528B1 · 2019 [cited by applicant]
JP 2003529952A · 2003 [cited by applicant]
KR 102392359B1 · 2022 [cited by applicant]
TW I335533B · 2011 [cited by applicant]
ZA 201805385B · 2022 [cited by applicant]