Method for effecting a software service in a system of a software system landscape and computer system

• US 7,926,056 B2
• Filed: 10/27/2005
• Issued: 04/12/2011
• Est. Priority Date: 10/27/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Nogge, Wolfram, Lier, Karlheinz, Schulz, Volker
• Primary Examiner(s): Puente; Emerson C
• Assistant Examiner(s): Truong; Camquy
• Application Number:
  US11/262,326
• Publication Number:
  US 20060143614A1
• Time in Patent Office: 1,993 Days
• Field of Search: 718/102, 717/177
• US Class Current: 718/102
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

The invention concerns a method for effecting a software service in at least one of a plurality of logical systems of a software system landscape, wherein the logical systems are interconnected by logical transport paths, each logical system has associated therewith one of a plurality of system roles and the software service relates to at least one of the code and the data of the at least one system, is described. The method includes providing a transport track that defines a route for software services through logical systems in a particular order and specifies one source system, adjacent interconnected systems, and at least one target system; generating a task list in a central task system from the transport track and the system roles, the task list defining tasks for routing a software service from a starting system to the at least one system and for implementing the preliminary software service in the at least one system; and scheduling in a central control system the execution of the tasks stored in the central task system and monitoring task statuses from the central control system.

Claims

1. A method of effecting a software service, the method comprising:

in at least one of a plurality of logical systems of a software system landscape, the logical systems being interconnected by logical transport paths, each logical system having associated therewith one of a plurality of system roles and the software service relating to at least one of the code and the data of the at least one system, the method including;

providing system role types, each of the system role types comprising a group of system roles, the system role types including source systems, follow-on systems, and target systems, the follow-on systems including at least one of a training system, a testing system, and a quality assurance system;

providing a transport track that defines a route for the software service through logical systems in a particular order and specifies one source system, at least one of the follow-on systems, and at least one target system;

generating a task list in a central task system from the transport track and the system roles, the task list defining tasks for routing the software service from a starting system to the at least one system and for implementing a preliminary software service in the at least one system, the task list having hierarchy levels, the hierarchy levels including a transport track level, a system role type level below the transport track level, a system role level below the system role type level, a system level below the system role level, and a task level below the system level; and

scheduling in a central control system the execution of the tasks stored in the central task system and monitoring task statuses from the central control system.

2. The method of claim 1, wherein the scheduling comprises generating a schedule using predefined schedules for tasks and software service types.

3. The method of claim 1, wherein generating the task list comprises determining from the transport track which systems are affected, determining the system role type of each affected system, determining the software service type, and using predefined tasks associated to system role types and software service types.

4. The method of claim 3, wherein a preliminary software service type and a regular software service type are used as the software service types.

5. A computer system comprising:

a software system landscape comprising a plurality of logical systems that are interconnected by logical transport paths and each having associated therewith one of a plurality of system role types, the system role types comprising a group of system roles, the system role types including source systems, follow-on systems, and target systems, the follow-on systems including at least one of a training system, a testing system, and a quality assurance system;

a transport track that defines a route for the software service through logical systems in a particular order and specifies one source system, at least one of the follow-on systems, and at least one target system, the software service relating to at least one of the code and the data of at least one system;

a central task system;

means for generating a task list in the central task system from the transport track and the system roles, the task list defining tasks for routing a software service from a starting system to the at least one system and for implementing a preliminary software service in the at least one system, the task list having hierarchy levels, the hierarchy levels including a transport track level, a system role type level below the transport track level, a system role level below the system role type level, a system level below the system role level, and a task level below the system level;

a central control system; and

means for scheduling in the central control system the execution of the tasks stored in the central task system and for monitoring task statuses from the central control system.

6. The system of claim 5, wherein predefined schedules for tasks and software service types are provided for use by the scheduling means.

7. The system of claim 5, wherein the means for generating are designed to determine from the transport track which systems are affected, to determine the system role type of each affected system, to determine the software service type, and to use predefined tasks associated to system role types and software service types.

8. The system of claim 7, wherein a preliminary software service type and a regular software service type are provided.

9. A non-transitory computer-readable storage medium containing instructions that, when executed by one or more processors, perform a method of effecting a software service, the method comprising:

in at least one of a plurality of logical systems of a software system landscape, the logical systems being interconnected by logical transport paths, each logical system having associated therewith one of a plurality of system roles and the software service relates relating to at least one of the code and the data of the at least one system, the method including;

providing system role types, each of the system role types comprising a group of system roles, the system role types including source systems, follow-on systems, and target systems, the follow-on systems including at least one of a training system, a testing system, and a quality assurance system;

providing a transport track that defines a route for the software services through logical systems in a particular order and specifies one source system, at least one of the follow-on systems and at least one target system;

generating a task list in a central task system from the transport track and the system roles, the task list defining tasks for routing the software service from a starting system to the at least one system and for implementing a preliminary software service in the at least one system, the task list having hierarchy levels, the hierarchy levels including a transport track level, a system role type level below the transport track level, a system role level below the system role type level, a system level below the system role level, and a task level below the system level; and

scheduling in a central control system the execution of the tasks stored in the central task system and monitoring task statuses from the central control system.

10. A computer system comprising:

a software system landscape comprising a plurality of logical systems that are interconnected by logical transport paths and each having associated therewith one of a plurality of system role types, the system role types comprising a group of system roles, the system role types including source systems, follow-on systems, and target systems, the follow-on systems including at least one of a training system, a testing system, and a quality assurance system;

a transport track that defines a route for software service through logical systems in a particular order and specifies one source system, at least one of the follow-on systems, and at least one target system, the software service relating to at least one of the code and the data of at least one system;

a central task system;

a module, having one or more processors, to generate a task list in the central task system from the transport track and the system roles, the task list defining tasks for routing the software service from a starting system to the at least one system and to implement a preliminary software service in the at least one system, the task list having hierarchy levels, the hierarchy levels including a transport track level, a system role type level below the transport track level, a system role level below the system role type level, a system level below the system role level, and a task level below the system level;

a central control system; and

a module to schedule in the central control system the execution of the tasks stored in the central task system and to module task statuses from the central control system.