Simple about SAP basis: SAP

Showing posts with label SAP. Show all posts

7/10/2020

SAP diagnostics agents

The diagnostics agent is a central component of the SAP Solution Manager system landscape. This page summarizes all relevant information on the agent and provides detail information on all relevant topics.Installation

General Information

Following documents are most relevant for installing and working with the Diagnostics Agent:

Refer to SAP Note 1365123 for the Diagnostics Agent installation strategy.

Refer to SAP Note 1833501 for information on Diagnostics Agent installer versions, and for an overview of SAP Notes related to Mass Deployment / Unattended Installation.

Refer to SAP Note 1858920 and the latest Installation and Setup Guide for:

Information on how to access the Product Availability Matrix (PAM) for the Diagnostics Agent

Instructions on how to download the Installation Media

Instructions on how to patch the Installation Media

Details on supported kernels

Description of the unattended/silent installation mechanism

SMD Setup Script (smdsetup.bat/smdsetup.sh) documentation

More detailed installation instructions

Download Paths

Artifacts required for Diagnostics Agent installations can be downloaded as follows (for detailed instructions and alternative paths refer to latest Diagnostics Agent Installation and Setup Guides):

Go to http://support.sap.com/sltoolset

Product Availability Matrix/PAM:  search for "Product Availability Matrix"

Documentation:  System Provisioning → System Provisioning Scenarios → Install a System using System Provisioning Manager → Installation Option of Software Provisioning Manager 1.0 → Installation Guides - Standalone Engines and Clients → Diagnostics Agent  → download the guide for your "Operating System Platform"

"installer":  System Provisioning → Download Software Provisioning Manager → SOFTWARE PROVISIONING MGR 1.0 → DOWNLOADS → → SWPM10SP*.SAR

For download of individual archives go to SAP Note 2253383

Check SAP Note 1858920 and the Product Availability Matrix for supported kernel versions

Diagnostics Agent and HA Support

Diagnostics Agent Maintenance Procedures

Which agent version should be used?

Please refer to the above mentioned Diagnostics Agent Installation Strategy SAP Note.

Where to install an agent?

Please refer to the above mentioned Diagnostics Agent Installation Strategy SAP Note.

Where to download the agent installation files?

Please refer to the General Information section above.

Connection Configuration

Refer to the installation procedures contained inside the Diagnostics Setup Guide.

Connection options

Before starting the installation make sure that you have identified which installation strategy you want to use. This means that you need to choose between the two following scenarios:

Direct Solution Manager Registration: In this scenario, the Diagnostics Agent establishes a direct connection to the Solution Manager system. Using this type of connection no SLD attachment is necessary especially since Solution Manager 7.1 SP05. Operational issues concerning Diagnostics Agents to Solution Manager connectivity can now be easily resolved via the “Non-authenticated Agents” list. (See Non Authenticated Diagnostics Agents).
Prerequisite: Diagnostics Agent was connected to a Solution Manager 7.1 SP05 system at least once.

SLD Registration: In this scenario, the Diagnostics Agent registers itself into the production SLD assigned to the managed system on which the Diagnostics Agent will be installed. This scenario should be used especially if Solution Manager is not yet installed.

SLD Registration - Remotely Connect DIagnostics Agents - Solution Manager 7.1

If you choose the "SLD Registration" strategy, the Diagnostics Agent should be visible using SOLMAN_SETUP transaction -> System preparation -> Step "Connect Agents". You must connect the relevant Diagnostics Agents to the current Solution Manager system in order to later be able to use them.

Agent reconnection may require waiting several minutes. It depends on settings which are set on the SMD Agent side. As soon as it detects that the association has been changed the SLD state is updated and the registration should proceed.

Direct Solution Manager Registration

If you want to perform the "Direct Solution Manager Registration" after the installation of the Diagnostics Agent, you will need to perform the smdsetup script action managingconf.

You can perform the direct connection to the solution manager in two ways, using the J2EE Message Server HTTP port (recommended). For more information about the smdsetup script refer to the Diagnostics Agent setup guide attached to the SAP Note for the most recent installer release (see SAP Note 1833501).

Example:

Connection by Message Server:

smdsetup managingconf hostname:"sapms://" port:"" [optional user:"<...>" pwd:"<...>"]

To run these script we will need to following information:

Full qualified solution manager hostname.

J2EE Message Server HTTP Port, like 81.

Diagnostics Agent system user: For more information about these user check the User Administration Guide.

Diagnostics Agent system user password.

Where to find the J2EE Message Server HTTP port.

J2EE Message Server HTTP: This port is usually 81XX (where xx is the SCS instance number: /usr/sap//SCS).

Make sure that you address the Solution Manager Java SCS Message Server with the above mentioned port number. URL.  Enter in the following URL: http://:/msgserver/text/logon
This shall display a P4 and/or P4S line, like here:

Having all necessary information, you have to perform the smdsetup script to connect the Diagnostics Agent to the Solution Manager system:

   1. Open a prompt command and navigate to the script folder inside of the agent path: usr/sap//SMDAXX/script
   2. Run the smdsetup script as the following examples:

Connection by Message Server:

     - smdsetup managingconf hostname:"sapms://solman.full.qual.host.name" port:"81XX" user:"SMD_ADMIN" pwd:"XXXXXXXX"

Afterwards, the command should finish successfully:

Then check at the “Agent Administration” if the agent is connected to the Solution manager. If the agent does not connect to the Solman system check the SMDSystem log for error. This log file can be found into the log folder at the agent path.

IMPORTANT: Note that SAP recommends to use the connection via the Solution Manager Java SCS Message Server. Trying out a direct connection via the P4 or P4S port, is only relevant in some very specific situations.

Connect the Diagnostics Agent to Solution Manager Using SSL

Please refer to the configuration wiki: Connect the Diagnostics Agent to the Solution Manager using SSL .

How to Configure the Different Ciphers on the Diagnostic Agent

Please refer to SAP Note 2849162.

Frequently Asked Questions and Trouble Shooting

Please refer to the FAQ Diagnostics Agent.

7/05/2020

SAP Basis - Remote Function Call

What is RFC?

To communicate between SAP systems, there is a need to define a mechanism. One of the most common ways is to define Remote Function Call (RFC Connection) between two systems. By creating a trusted RFC connection between two systems, it allows you to create trusted-trusting relationship between systems wherein, you can communicate and exchange information and data.

There are different types of trusted RFC connections.

Type 3 Connection

This connection type is used to specify connection between ABAP systems. Here, you need to mention the host name and IP address of source system and also the logon information. This is applicable for both type of RFCs, between ABAP systems and external calls to ABAP systems.

Type I Connection

This connection type is used to specify ABAP systems connected to the same data base as the current system. Let us take an example entry name — ws0015_K18_24

ws0015=host name

K18=system name (data base name)

24=TCP-service name

Type T Connection

This connection type helps connect destinations to external programs that use the RFC API to receive RFCs. This can be activated using start or registration.

SAP Basis - Deleting a Background Job

You can delete jobs from the SAP system. These jobs may no longer be required and may occupy a lot of space on the system. Jobs can be deleted in the following two ways −

Single Job
Multiple Jobs

Follow these steps to delete a single job −

Step 1 − Use transaction code — SM37.

Step 2 − Use * in the Job Name column and select the status to see all the jobs created by this user. Also enter the date range as per the requirement and then Execute.

Step 3 − Upon execution, all the jobs that have been created by the mentioned user and match the selection criteria are displayed.

Details like Job name, Job Created By, Status, Start date, Duration, Delay, etc. are shown. Select the job you want to delete from the database → Delete

Step 4 − To delete multiple jobs, use transaction code — SE38. Use report — RSBTCDEL2 (New version of RSBTCDEL). Old job logs will be deleted and will not show in the job overview. Enter program and click on Execute.

Step 5 − In the next screen, enter the details such as the Job Name you want to delete. You can put * to indicate all jobs. If you want to delete jobs from a specific user, enter the username.

Step 6 − Mention the status of Jobs to be deleted and the time period of deletion.

Step 7 − Specify Commit — Commit value is proportional to program performance. If the commit value is high, then job deletion will run faster. Recommended value is >= 1000.

Step 8 − Check Test run to simulate the deletion and this way jobs will not be deleted. When you are sure, uncheck the Test run and press Execute.

Step 9 − When you click on Test run, it will show you the list of all jobs matching the criteria. If there is any change you want to make, you can do it before completing the deletion.

SAP Basis - Monitoring a Background Job

Monitoring a background job is important in SAP system because once you schedule the job it might be cancelled due to some error.

Follow these steps to monitor a background job −

Step 1 − Use transaction code — SM37

Step 2 − Use * in the Job Name column and select the status to see all the jobs created by this user. Also enter the date range as per the requirement and then Execute.

Step 3 − Upon execution, all the jobs that have been created by the mentioned user and match the selection criteria are displayed.

Details like Job name, Job Created By, Status, Start Date, Duration, Delay, etc. are shown.

Step 4 − To check the job log, you can select the job and click on the Job Log button.

SAP Basis - NW System

SAP NetWeaver is a web-based, open integration, application platform that serves as the foundation for enterprise service-oriented architecture (enterprise SOA) and allows the integration and alignment of people, information, and business processes across business and technology boundaries. It allows the composition, provisioning, and management of SAP and non-SAP applications across a heterogeneous software environment.

The following table defines the Main Use Cases of SAP NetWeaver and its key area −

Use Case	Description
Data Warehousing	SAP BW
Building Integration scenarios	SAP Process Integration PI
Mobilizing Business Processes	SAP NetWeaver Mobile
Building Composite Applications	SAP Composition Environment
Integration with SAP Enterprise Portal	SAP Enterprise Portal
Application Development ABAP	ABAP Development on NetWeaver Application Server ABAP

To implement these use cases, SAP has provided mapping between use cases and SAP NetWeaver software components.

Consider the use case of data warehousing, it has multiple product instances and client tools to use NetWeaver for data warehousing.

Standalone Engines	Product Instance	Client Tool
Search and Classification (TREX)	AS ABAP BW ABAP AS Java NW Product Description [optional] AS Java Extensions [optional] BI Java [optional] EP Core – Application Portal [optional] Enterprise Portal	SAP GUI with Business Explorer (BI Add-On) SAP BusinessObjects Analysis, Edition for Microsoft Office* [optional] SAP BusinessObjects Crystal Reports [optional] SAP BusinessObjects Dashboards [optional] SAP BusinessObjects Web Intelligence [optional] SAP BusinessObjects Design Studio [optional]

SAP Basis - Hardware & Software Installation

To implement SAP ERP, we need to find out the minimum hardware and software requirements. The minimum system requirements should be met to perform the implementation successfully.

The following are the minimum requirements for SAP R/3 installation −

Minimum hardware requirements

CPU: Intel PIII 500 MHZ
HDD: 30 GB
RAM: 256MB
Ethernet Card for LAN connectivity

Minimum software requirements

Windows Server
Windows Server Service Pack
Internet Explorer
Database Software Ex: Microsoft SQL Server
SAP R/3 System
Report Data CD
Export CDs
SAP GUI
SAP R/3 Kernel CD
Dynamic Link Libraries or DLL
Active Directory Service Interface or ADSI
Microsoft Management Console or MMC

Hardware requirements to install SAP ECC 6.0

HDD − 250GB + 45GB Hard Disk Space
RAM − Minimum 4 GB of RAM — The more the capacity of RAM, the less time it takes for installation
CPU − Intel Dual Core or Core 2 Duo Processor — If you have a 64-bit processor, you can go for ECC 6.0 EHP4 instead of ECC 6.0 SR2.
CD Drive to copy the software

Software requirements to install SAP ECC 6.0

Windows server 2003 32-bit SP 2 or Windows Sever 2003 64-bit OS.
Driver CDs
Adobe Acrobat Reader for Installation Manual

SAP ECC 6.0 ides SR2 installation will be completed approximately in 20 hours with the above configuration. The installation time can be reduced further by upgrading hardware configuration like quad 2 core processor with 8 GB ram and 1 TB Hard Disk Drive.

Note − You can download SAP ECC 6.0 free trial from SAP Market place. It is also possible to integrate SAP ECC 6.0 trial using SAP Cloud Appliance Library ACL to AWS or other cloud environment service provider by providing user public cloud key.

Installation of SAP ECC 6.0

Follow these steps to install SAP ECC 6.0 −

Step 1 − Install database as per the requirement. Java JDK 1.4 is the minimum requirement. Copy the software to local drive and run sapinst.exe. Set up wizard will open.

Step 2 − Select the service you want to install — Central System Installation > Select Service Type – Typical or Custom > Next

Step 3 − Select the software units you want to install with ECC like Biller Direct and additional NW software units AS ABAP, etc.

Step 4 − Enter the SAP System ID and Installation drive. SAP System ID is a unique identifier for your SAP system. It must be unique throughout the system landscape. Enter master password which will be used for all user accounts to be created.

Step 5 − Enter Database parameters like DBSID for an existing database, host name, etc.

Step 6 − Perform perquisite check. You can click OK to perform check or cancel to move to next step.

Step 7 − In the next window, you have to provide the location of export files, oracle client and kernel files > Next > Enter OS passwords.

Step 8 − Enter the central instance number, which serves as the technical identifier for controlling internal processes such as memory. This number must be unique for this installation.

Step 9 − The system now shows you the port numbers.

Step 10 − Click Next and you will see the summary of installation.

Step 11 − Enter the Solution Manager key to continue the installation and upgrade process.

Step 12 − Once the installation is complete, you will receive the following confirmation.

Different Hardware and Software Components in SAP System

The following are the key components in SAP system −

Database Server
Application Server
Other Servers
Software components- NetWeaver
SAP GUI
License key and Maintenance Certificates
Enhancement Package
Upgrade plans
SAP Solution Manager Integration

In SAP system, to check the list of the currently installed software component versions, you can go to SAP GUI, select system.

Choose System in SAP logon> System > Status > click the Component Information icon under system data.

Go to SAP system data → Click on component magnifying glass.

You can see the following two options −

Installed software component versions
Installed product versions

Under installed software component, you can see all the installed software, support package, service pack, description etc. If you want to check the details of each component, you can select the component and go to details tab as shown above.

Go to Installed Product Versions, it will show you the version of the installed SAP NetWeaver.

System Landscape & Architecture

SAP system landscape is defined as an arrangement of SAP servers. Ideally, in a Sap environment, a three-system landscape exists. A system landscape consists of Development Server (Dev), Production Server (PROD), and Quality Assurance server (QAS).

SAP Architecture is defined as a technology framework of SAP system and it changes with time unlike the system landscape. SAP Architecture changes with new software like SAP ECC 6.0, the most recent one.

The following is a request in SAP System Landscape −

DEVELOPMENT >>>> Quality >>>> PRODUCTION

The following figure represents SAP three tier system landscape where work flows from Dev > QAS > PROD and not in backward direction.

Let us now discuss the system landscape −

Sandbox Server

When a project is implemented, at the initial stages, a sandbox server is used where all the customization, configuration is performed.

Development Server

Next is to save the configuration in development server and saved in workbench requests and this has to be transported to Production server.

Production Server

You can consider it as the final or the most refined stage where the work is done when project is in production/go live. All the changes that are required by the client are performed in the DEV environment and later, the request is transported to production.

SAP System 3 – Tier Architecture

The image given below shows 3-tier architecture of the SAP system. The presentation layer is the topmost one. This contains the device/application to control the SAP system. This can include mobile devices, end user systems or SAP GUI or web browser based client.

The presentation layer communicates with the application server to perform all the processing and which is known as brains of an SAP system.

An application server consists of multiple instances and communicates with the database layer of the three-tier architecture.

The bottom layer is called the database layer. This is responsible to store all the data. The database of SAP system is kept on a separate server for performance and security reasons.

The presentation layer consists of different components for ABAP and JAVA that enables the communication and processing of data in SAP system.

The key components of the presentation layer include the following −

Message Server − This is used to manage communication between distributed dispatchers in the ABAP system.

Message Server − This is used to manage server processes and JAVA dispatchers. It is used to manage communication within JRE.

Dispatcher Queue − This is used to store multiple work process types.

Dispatcher − This is used to distribute the requests to the work processes.

Memory Pipes − This is used to manage communication between ICM and ABAP work processes.

Enqueue Server − This is used to handle logical locks set by the executed Java application program.

Java Dispatcher − This is responsible to receive the client requests via presentation layer and forward to the server process.

Gateway − This is used to manage communication between SAP system and external systems.

ABAP Work processes − This separately executes dialog steps in R/3 applications separately.SAP system landscape is defined as an arrangement of SAP servers. Ideally, in a Sap environment, a three-system landscape exists. A system landscape consists of Development Server (Dev), Production Server (PROD), and Quality Assurance server (QAS).