SAP Basis SWPR Restart workflow after error - SAP Basis

Direkt zum Seiteninhalt
SWPR Restart workflow after error
Differentiation from SAP ABAP
The application layer is the central component of the SAP R/3 system. This layer is therefore also referred to by SAP as the actual base system. Within the layer there are application servers and a message server.

Many companies are struggling with the introduction and use of secinfo and reginfo files to secure SAP RFC gateways. We have developed a generator that supports the creation of the files. This blog post lists two SAP best practices for creating the secinfo and reginfo files to enhance the security of your SAP gateway and how the generator helps you do this. secinfo and reginfo Request generator Option 1: Restrictive procedure In the case of the restrictive solution approach, only in-system programmes are allowed. Therefore, external programmes cannot be used. However, since this is desired, the access control lists must be gradually expanded to include each programme required. Although this procedure is very restrictive, which speaks for safety, it has the very great disadvantage that, in the creation phase, links which are actually desired are always blocked. In addition, the permanent manual activation of individual connections represents a continuous effort. For large system landscapes, this procedure is very complex. Option 2: Logging-based approach An alternative to the restrictive procedure is the logging-based approach. To do this, all connections must be allowed first by the secinfo file containing the content USER=* HOST=* TP=* and the reginfo file contains the content TP=*. During the activation of all connections, a recording of all external programme calls and system registrations is made with the gateway logging. The generated log files can then be evaluated and the access control lists created. However, there is also a great deal of work involved here. Especially with large system landscapes, many external programmes are registered and executed, which can result in very large log files. Revising them and creating access control lists can be an unmanageable task. However, this process does not block any intentional connections during the compilation phase, which ensures the system will run non-disruptively.
Permanent tuning and performance monitoring in the aforementioned areas
In more complex system environments, thousands, if not tens of thousands, of SAP jobs can run per day. Their interdependencies create a high level of complexity. If administrators or admin teams want to maintain an overview, they have to rely on meaningful monitoring. It must be clear at all times which jobs are running and which are not, in order to ensure proper SAP operation. Ideally, one is informed of critical errors by e-mail or SMS. The trend towards internationalization, outsourcing and mixed operation with on-premise and on-demand systems means that SAP landscapes are often widely distributed. This makes monitoring more difficult and, at the same time, clarity must be maintained. Integrating SAP job management and job requests into a central system, such as SAP Solution Manager, therefore makes sense and is useful for supplementing IT service processes in a meaningful way and accelerating process flows.

SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis:

The application layer is the central component of the SAP R/3 system. This layer is therefore also referred to by SAP as the actual basis system. Within the layer there are application servers and a message server.

"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.

Many errors are avoided: Far fewer errors occur, e.g. when enhancement packages are installed, if this is done by SAP experts.

SAP Basis Operation is responsible for ensuring the technical functionality of an SAP system.

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
Zurück zum Seiteninhalt