Configuring and Monitoring SAP Environment - eG … Implementer's Guides... · CONFIGURING AND...

Configuring and Monitoring SAP Environment eG Enterprise v5.6

Restricted Rights Legend

The information contained in this document is confidential and subject to change without notice. No part of this document may be reproduced or disclosed to others without the prior permission of eG Innovations, Inc. eG Innovations, Inc. makes no warranty of any kind with regard to the software and documentation, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.

Trademarks

Microsoft Windows, Windows NT, Windows 2000, Windows 2003 and Windows 2008 are either registered trademarks or trademarks of Microsoft Corporation in United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Copyright

© 2012 eG Innovations, Inc. All rights reserved.

Table of Contents CONFIGURING AND MONITORING THE SAP R/3 SERVERS......................................................................................................1

1.1 CONFIGURING THE SAP R/3 SERVER FOR MONITORING BY THE EG ENTERPRISE SUITE...............................................................1 1.2 ADMINISTERING THE EG MANAGER TO WORK WITH A SAP R/3 SERVER .....................................................................................2 1.3 MONITORING THE SAP R/3 SERVER ...............................................................................................................................................9

CONFIGURING AND MONITORING THE AGATE COMPONENT OF THE INTERNET TRANSACTION SERVER (ITS).....................................................................................................................................................................................................................16

2.1 ADMINISTERING THE EG MANAGER TO WORK WITH THE AGATE COMPONENT ..........................................................................16 2.2 MONITORING THE AGATE SERVER................................................................................................................................................21

CONFIGURING AND MONITORING THE SAP WEB APPLICATION SERVER (SAP WEB AS)..........................................22 3.1 CONFIGURING THE SAP WEB AS..................................................................................................................................................22 3.2 ADMINISTERING THE EG MANAGER TO WORK WITH THE SAP WEB AS......................................................................................23 3.3 MONITORING THE SAP WEB APPLICATION SERVER ....................................................................................................................29

CONFIGURING AND MONITORING THE MAX DB SERVER.....................................................................................................30 4.1 CONFIGURING THE MAX DB SERVER ...........................................................................................................................................30 4.2 ADMINISTERING THE EG MANAGER TO WORK WITH THE MAX DB SERVER ...............................................................................30 4.3 MONITORING THE MAX DB SERVER.............................................................................................................................................32

CONCLUSION..........................................................................................................................................................................................33

Table of Figures

Figure 1.1: Selecting a SAP R/3 server for monitoring................................................................................................................................3 Figure 1.2: Managing a SAP R/3 server .......................................................................................................................................................3 Figure 1.3: The list of unconfigured tests for the SAP R/3 server ...............................................................................................................4 Figure 1.4: Configuring the R3Buffers test ..................................................................................................................................................4 Figure 1.5: Opening the SAPlogon tool........................................................................................................................................................5 Figure 1.6: Clicking on the Logon button.....................................................................................................................................................6 Figure 1.7: Logging into the SAP Easy access console ...............................................................................................................................6 Figure 1.8: Accessing the Client Maintenance node ....................................................................................................................................7 Figure 1.9: The Clients list............................................................................................................................................................................7 Figure 1.10:Accessing the Control Panel in the CCMS tool........................................................................................................................9 Figure 1.11: The Server Name list ................................................................................................................................................................9 Figure 2.1: Adding an AGate server ...........................................................................................................................................................17 Figure 2.2: The list of unconfigured tests for the SAP R/3 server .............................................................................................................17 Figure 2.3: Configuring the AGateServer test ............................................................................................................................................17 Figure 2.4: Configuring the AGateAccess test ...........................................................................................................................................18 Figure 2.5: Configuring the AGateStatus test.............................................................................................................................................19 Figure 2.6: Configuring the AGateTrans test .............................................................................................................................................20 Figure 3.1: Adding a SAP Web Application server ...................................................................................................................................24 Figure 3.2: The list of unconfigured tests for the SAP Web Application server .......................................................................................24 Figure 3.3: Configuring the SapWasBeans test ..........................................................................................................................................24 Figure 3.4: Starting the Visual Administrator ............................................................................................................................................26 Figure 3.5: Loggin into the Visual Administrator ......................................................................................................................................26 Figure 3.6: Identifying the cluster ID of the Dispatcher.............................................................................................................................27 Figure 3.7: Identifying the cluster ID of the Server ...................................................................................................................................28 Figure 4.1: Adding a MaxDB server...........................................................................................................................................................31 Figure 4.2: The list of unconfigured tests for the MaxDB server ..............................................................................................................31 Figure 4.3: Configuring the DbConnection test .........................................................................................................................................31

C o n f i g u r i n g a n d M o n i t o r i n g t h e S A P R / 3 S e r v e r s

Configuring and Monitoring the SAP R/3 Servers This chapter will elaborately discuss the steps involved in configuring and monitoring the SAP R/3 server, which is the middle-tier application server that hosts the business logic components of SAP.

1.1 Configuring the SAP R/3 Server for Monitoring by the eG Enterprise suite

In Windows installations of the SAP R/3 server, ensure that the following steps are adhered to before attempting to monitor the SAP R/3 server:

1. Download the SAPJCO API from the SAP Marketplace.

2. The API will be available in the SAP Marketplace as a zip file. After downloading the API, extract the following files from the zip:

sapjcorfc.dll

librfc32.dll

sapjco.jar

3. Copy the extracted files to the <EG_INSTALL_DIR>\lib directory on the eG agent host. The classpath is already set for this jar file.

Chapter

1

Note:

The eG Enterprise suite requires SAPJCO 2.0 for monitoring the SAP R/3 server. This inturn needs JRE 1.2 or higher. If SAPJCO 2.1 is downloaded instead, then ensure that aminimum of JRE 1.3 is available.

The eG agents use the BC-XAL interface to connect to SAP R/3 for monitoring. Thisinterface is compatible only with SAP R/3 release 4.5b and higher.

1


For SAP installations on Unix, follow the steps given below:

1. Download the SAPJCO API from the SAP Marketplace.

2. Extract the following files from the zipped API and copy them to the /opt/egurkha/lib directory:

libsapjcorfc.so (in AIX systems, this would be libsapjcorfc.o)

librfccm.so (in AIX systems, this would be librfccm.o)

sapjco.jar

3. The path of these files should be set in LD_LIBRARY_PATH variable.

4. Finally, restart the eG agent.

1

T

1

2

Note: The SAP_R3_server component of the eG Enterprise suite also monitors the SAP Messagingserver, using the following tests: SapMsgTest, SapMsgInfoTest, and SapGroupLbTest. Inorder for these tests to function smoothly, the following pre-requisites will have to befulfilled.

These tests use an lgtst command to extract critical statistics from the SAPMessage server. With this command, you can check the active instances of yourSAP System and check existing logon groups directly at the operating systemlevel. To ensure that this test functions smoothly, the lgtst command needs tobe copied to the /opt/egurkha/bin directory (on Unix, or the <EG_INSTALL_DIR>\bin onWindows).

Another pre-requisite for the smooth execution of this test is that, in thetransaction SMLG, the External RFC Permitted attribute will have to be definedfor any one of the logon groups on the SAP Message server.

2

.2 Administering the eG Manager to Work with a SAP R/3 Server

o achieve the above, do the following:

. Log into the eG administrative interface.

. If a SAP R/3 server is already discovered, then directly proceed towards managing it using the COMPONENTS - MANAGE/UNMANAGE page (Infrastructure -> Components -> Manage/Unmanage). However, if it is yet to be discovered, then run discovery (Infrastructure -> Components -> Discover) to get it discovered or add the component manually using the ADD/MODIFY COMPONENTS page (Infrastructure -> Components -> Add/Modify). Remember that components manually added are managed automatically. Discovered components, however, are managed using the COMPONENTS - MANAGE/UNMANAGE page. Figure 1.1 and Figure 1.2 clearly illustrate the process of managing the SAP R/3 server.

For more details on managing components, refer to Configurinhg and Monitotring

Web Servers document.


3

Figure 1.1: Selecting a SAP R/3 server for monitoring

Figure 1.2: Managing a SAP R/3 server

4. Then, try to sign out of the eG administrative interface. Upon doing so, Figure 1.3 will appear listing the unconfigured tests for the SAP server.


4

Figure 1.3: The list of unconfigured tests for the SAP R/3 server

5. Click on the R3 Buffers test in Figure 1.3 to configure it. Figure 1.4 will then appear.

Figure 1.4: Configuring the R3 Buffers test

6. The R3 Buffers test reports statistics relating to the SAP R/3 server's buffers. The goal of buffer setting is to have a sufficiently large buffer to maintain a high hit rate and to do so with a low rate of swapping and a minimal effect on operating system paging. The test contains values for the following SAP buffers, sorted by application server:

Name of the MTE Contents of the Buffer

Program Compiled SAP programs

Generic Key Wholly or partly buffered database tables

SingleRecord Individual records from utilized database tables

Screen Screen pages from ABAP programs

CUA Menus and pushbuttons from the ABAP screen pages

TableDefinition Table Definitions from the SAP R/3 Repository


5

FieldDescription Field descriptions from the SAP R/3 Repository

InitialRecords Initial record layout (initial values for the fields of a database segment) for a table

ShortNameTAB Combination of TTAB and FTAB buffers

7. In Figure 1.4, specify the following:

TEST PERIOD - How often should the test be executed

HOST - The host for which the test is to be configured

PORT – The port at which the SAP R/3 server listens

CLIENTNAME - Specify the ID of the client system that is connecting to the R/3 server. To view a list of client IDs to choose from, do the following:

i. From any SAP client, execute the SAPlogon tool using the menu sequence: Start -> Programs -> SAP Front End -> SAPlogon (see Figure 1.5).

Figure 1.5: Opening the SAPlogon tool

ii. Click on the Logon button in the dialog box that appears (see Figure 1.6), and login to the SAP R/3 server using a valid user name and password (see Figure 1.7).


6

Figure 1.6: Clicking on the Logon button

Figure 1.7: Logging into the SAP Easy access console

iii. Using the tree-structure in the SAP Easy Access console that appears (see Figure 1.8), navigate to the Client Maintenance node. The node sequence to be used is: SAP menu -> Tools -> Administration -> Client Administration -> Client Maintenance.


7

Figure 1.8: Accessing the Client Maintenance node

iv. A Display View "Clients" page will appear (see Figure 1.9), which will display the details of SAP clients. Any of the values of the Client column in this page, can be provided as the value of the CLIENTNAME parameter.

Figure 1.9: The Clients list

SAPUSER - Provide a valid user name for logging into the SAP R/3 server. In order to enable the eG Enterprise suite to effectively monitor SAP, the name of a SAPUSER with either of the following profiles need to be specified here: S_A.SYSTEM (super administrator) or SAP_ALL (all authorizations for SAP).


8

PASSWORD - password of the specified SAPUSER

SYSNO - An indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the SYSNO will be '00'. Similarly, if the SAP server port is 3201, the SYSNO will have to be specified as '01'. Therefore, in the SYSNO text box specify the system number of the SAP server with which the specified client communicates.

ROUTER - If the SAP client with the specified CLIENTNAME exists in a network external to the SAP server, then a router will be used to enable the server-client communication. In such a case, specify the IP of the router in the ROUTER text box. If both the client and the server exist in the same network, then specify 'none' against the ROUTER text box.

ISPASSIVE - If the value chosen is YES, then the server under consideration is a passive server in a SAP R/3 cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable’ by the agent if the server is not up.

TIMEOUT - Specify the duration (in seconds) for which this test should wait for a response from the SAP R/3 server. By default, this is set to 120 seconds.

INSTANCENAME - Specify the name of the SAP R/3 instance to be monitored. To view the complete list of instances to choose from, do the following:

o Login into the SAP Easy Access console with the procedure mentioned in the CLIENTNAME measure.

o Using the tree-structure in the SAP Easy Access console, navigate to the CCMS tool (see Figure 1.10) available under the TOOLS option. The node sequence to be used is: SAP menu -> Tools -> CCMS -> Control/Monitoring -> Control Panel.

Note: The user name has to be provided in upper-case.

Note: The password has to be provided in upper-case.


9

Figure 1.10:Accessing the Control Panel in the CCMS tool

o Double-click on the Control Panel node. A Display Server Statuses and Alerts page will appear (see Figure 1.11), which will display the details of the SAP Servers. Any of the values of the Server Name column in this page, can be provided as the value of the INSTANCENAME parameter.

Figure 1.11: The Server Name list

8. Finally, click the Update button in Figure 1.4.

9. Now, when you try to signout of the administrative interface, you will be prompted to configure the New alerts in the last measure period test.


10

Figure 1.12: Configuring the New alerts in the last measure period test

10. Specify the following in Figure 1.12.


HOST - Host name of the server for which the test is to be configured

PORT - Enter the port to which the specified HOST listens

CLIENTNAME – Specify the ID of the client system that is connecting to the R/3 server. To view a list of client IDs to choose from, follow the procedure discussed in Page Error! Bookmark not defined..

SAPUSER - Provide a valid user name for logging into the SAP R/3 server. In order to enable the eG Enterprise suite to effectively monitor SAP, the name of a SAPUSER with either of the following profiles need to be specified: S_A.SYSTEM (super administrator) or SAP_ALL (all authorizations for SAP).

PASSWORD - The password of the specified SAPUSER.

CONFIRMPASSWORD - Confirm the password by retyping it here.

SYSNO - An indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the SYSNO will be '00'. Similarly, if the SAP server port is 3201, the SYSNO will have to be specified as '01'. Therefore, in the SYSNO text box specify the system number of the SAP server with which the specified client communicates.

ROUTER - If the SAP client with the specified CLIENTNAME exists in a network external to the SAP server, then a router will be used to enable the server-client communication. In such a case, specify the IP of the router in the ROUTER text box. If both the client and the server exist in the same network, then specify 'none' against the ROUTER text box.

MONITOR DETAILS - Provide the list of monitors for which alerts are to be reported. The pattern for your specification should be as follows: Monitor Set name:comma-separated list of monitors. For example, your specification can be: SAP CCMS Monitor Templates:Database,Dialog per Application Server. If you want to configure monitors that belong to multiple monitor sets, your specification should be: <Monitor Set 1>:<comma-separated list of monitors>;<Monitor Set 2>:<comma-separated list of monitors>;. . .


11

For example, SAP CCMS Monitor Templates:Database,Dialog per Application Server; Monitor Collection for Certification:Test Monitor Dialog

While configuring the MONITOR DETAILS , you may want to know the exact names of the monitors and monitor sets that form part of your specification. To determine this, follow the procedure discussed in Section 1.3 of this document.

XMI AUDIT LEVEL - The XMI interface is a general framework for the CCMS external system management interfaces. This interface contains essential function modules and structures that coordinate connections between external system management tools and individual CCMS interfaces, and writes messages in the R/3 XMI log on behalf of the external tool. The XMI log is a table containing English message texts. The messages can have various degrees of detail. The audit level determines the degree of detail to which messages in the XMI log are written - i.e., whether the message should always be logged, or is simply a message which supplies further detail (higher detail degree). The XMI log contains messages from external tools and also messages which arise in SMAPI functions. To indicate to the test the degree of detail to which messages from the eG agent are to be written in the XMI log, you need to specify the XMI AUDIT LEVEL. By default, this parameter is set to 0, which indicates that all calls that modify the database are to be logged. The other values this parameter can take and their implications are discussed below:

1: Logs all calls that modify the database and error messages

2: Logs all calls that read from the database, modify the database, and error messages

3: Logs all calls and all messages (full trace)

TIMEOUT - Indicate the duration (in seconds) for which this test should wait for a response from the SAP R/3 server. By default, this is set to 120 seconds.

DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

o The eG manager license should allow the detailed diagnosis capability

o Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

11. Now, click on the Update button in Figure 1.12 and signout of the eG administrative interface.

1.3 Determining the names of the Monitors and Monitor Sets

1. While configuring the MONITOR DETAILS , you may want to know the exact names of the monitors and monitor sets that form part of your specification. To determine this, do the following:

2. Open the SAP Logon tool using the Start -> Programs -> SAP Front End -> SAP Logon menu sequence.


12

3. Pick a system from Figure 1.13 that appears, and click on the Logon button therein to connect to the chosen sysem.

Figure 1.13: Selecting a system to login to

4. Then, login to the chosen system by providing the required Client, User, and Password credentials. Once the Password is provided, press the Enter key on your keyboard to login (see Figure 1.14).

Figure 1.14: Logging into the chosen system

5. Upon logging in successfully, the SAP Easy Access interface will appear (see Figure 1.15). In the tree-structure in the left panel of the interface, follow the node sequence, SAP Menu -> Tools -> CCMS -> Control/Monitoring. Then, double-click on the RZ20-CCMS Monitor Sets sub-node under the Control/Monitoring node.


13

Figure 1.15: Double-clicking on the CCMS Monitor Sets sub-node

6. This will invoke Figure 1.16, where the complete list of monitor sets will be displayed. Expand a monitor set to view the monitors within. Use these details to configure the monitor set:monitors in the MONITOR DETAILS text box.


14

Figure 1.16: Viewing the monitor sets and monitors

1.4 Monitoring the SAP R/3 Server To monitor the server, do the following:

1. Login as a monitor / supermonitor user.

2. Click on the COMPONENTS option in the menu bar, and select the Servers option from the COMPONENTS menu.

3. From the COMPONENT LIST page, click on the SAP R/3 server being monitored.


Note: While collecting metrics from the SAP R/3 server, you will find that the values always appear asinteger values, though they may be floating point values. Follow the configuration steps providedhere to change this occurrence.

Run transaction SE11 from the SAP menu.

Type "ALPERFOB" in the "database tables" field, in the screen that appears.

In the "DECIMALS" field the value will be 0. Press the "Change" button and changethe value.

15

C o n f i g u r i n g a n d M o n i t o r i n g t h e A G a t e C o m p o n e n t o f t h e I n t e r n e t T r a n s a c t i o n S e r v e r ( I T S )

16

Configuring and Monitoring the AGate Component of the Internet Transaction Server (ITS) In this chapter, we will delve deep into the intricate procedures involved in monitoring the AGate component of ITS.

2.1 Administering the eG Manager to work with the AGate Component

To achieve this, do the following:

1. Log into the eG administrative interface.

2. If a AGate server is already discovered, then directly proceed towards managing it using the COMPONENTS - MANAGE/UNMANAGE page (Infrastructure -> Components -> Manage/Unmanage). However, if it is yet to be discovered, then run discovery (Infrastructure -> Components -> Discover) to get it discovered or add the component manually using the ADD/MODIFY COMPONENTS page (Infrastructure -> Components -> Add/Modify). Remember that components manually added are managed automatically. Discovered components, however, are managed using the COMPONENTS - MANAGE/UNMANAGE page. Figure 2.1 clearly illustrates the process of adding an AGate component.

For more details on managing components, refer to Configuring and Monitoring Web

Servers document.

Chapter

2


17

Figure 2.1: Adding an AGate server

3. Then, try to sign out of the eG administrative interface. Upon doing so, Figure 2.2 will appear listing the unconfigured tests for the SAP server.

Figure 2.2: The list of unconfigured tests for the SAP R/3 server

4. Click on the AGate Server test in Figure 2.2 to configure it. Figure 2.3 will then appear.

Figure 2.3: Configuring the AGate Server test

5. The AGate Server test reports performance statistics pertaining to the AGate component of the Internet Transaction Server (ITS). Using Figure 2.3, specify the following:



PORT – The port at which the HOST listens

LOGFILEPATH - This test extracts the performance metrics from the performance.log file present in the {ITS_INSTALL_DIR}\6.20\{Directory corresponding to the ITS instance}\logs directory. Therefore, in the LOGFILEPATH text box, provide the full path to the performance.log file in the following format: {Instance Name}={Path to the log file}. For example, if the log file for an instance named 'ADM' is to be monitored, and ITS is installed in the C:\Program Files\SAP\ITS directory, then the LOGFILEPATH specification


18

should be as follows: ADM=c:\Progra~1\SAP\ITS\6.20\ADM\logs\performance.log. To monitor the performance.log files associated with multiple instances, provide the LOGFILEPATH as a comma-separated list. For example, ADM=c:\Progra~1\SAP\ITS\6.20\ADM\logs\performance.log,ITS1=c:\Progra~1\SAP\ITS\6.20\ITS1\logs\performance.log.


7. Once again, try to signout of the administrative interface, but this time click on the AGate Access test in the list of unconfigured tests , to configure it. Figure 2.4 will then appear.

Figure 2.4: Configuring the AGate Access test

8. The AGate Access test reports the number of succesful logins to the AGate component of the Internet Transaction Server (ITS). Specify the following in Figure 2.4:



PORT - The port at which the HOST listens. By default, this is NULL.

LOGFILEPATH - This test extracts the performance metrics from the access.log file present in the {ITS_INSTALL_DIR}\6.20\{Directory corresponding to the ITS instance}\logs directory. Therefore, in the LOGFILEPATH text box, provide the full path to the access.log file in the following format: {Instance Name}={Path to the log file}. For example, if the log file for an instance named 'ADM' is to be monitored, and ITS is installed in the C:\Program Files\SAP\ITS directory, then the LOGFILEPATH specification should be as follows: ADM=c:\Progra~1\SAP\ITS\6.20\ADM\logs\access.log. To monitor the access.log files associated with multiple instances, provide the LOGFILEPATH as a comma-separated list. For example, ADM=c:\Progra~1\SAP\ITS\6.20\ADM\logs\access.log,ITS1=c:\Progra~1\SAP\ITS\6.20\ITS1\logs\access.log.

DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eG Enterprise system embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.



o Both the normal and abnormal frequencies configured for the detailed


19

diagnosis measures should not be 0.

9. Click the Update button in Figure 2.5 and proceed to signout of the administrative interface yet again. The tests configuration table will appear once again, but this time ensure that the AGate Status test is chosen for configuration. When this test is clicked, Figure 2.5 will appear

Figure 2.5: Configuring the AGate Status test

10. The AGate Status test reports whether any errors occurred in the AGate component during the last measurement period. To configure this test, specify the details requested by Figure 2.5:




LOGFILEPATH - This test extracts the performance metrics from the diagnostics.log file present in the {ITS_INSTALL_DIR}\6.20\{Directory corresponding to the ITS instance}\logs directory. Therefore, in the LOGFILEPATH text box, provide the full path to the diagnostics.log file in the following format: {Instance Name}={Path to the log file}. For example, if the log file for an instance named 'ADM' is to be monitored, and ITS is installed in the C:\Program Files\SAP\ITS directory, then the LOGFILEPATH specification should be as follows: ADM=c:\Progra~1\SAP\ITS\6.20\ADM\logs\diagnostics.log. To monitor the diagnostics.log files associated with multiple instances, provide the LOGFILEPATH as a comma-separated list. For example, ADM=c:\Progra~1\SAP\ITS\6.20\ADM\logs\diagnostics.log,ITS1=c:\Progra~1\SAP\ITS\6.20\ITS1\logs\diagnostics.log.

DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eG Enterprise system embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.




11. After updating the configuration, if you attempt to exit the admin interface again, the tests


20

configuration table will reappear prompting you to configure the Agate Transactions test. Click on the test to configure it.

12. Figure 2.6 will subsequently appear.

Figure 2.6: Configuring the AGate Transactions test

13. The AGate Transactions test monitors the access requests serviced by the ITS instance. To configure this test, specify the values for the parameters displayed in Figure 2.6.




LOGFILEPATH - This test extracts the performance metrics from the diagnostics.log file present in the {ITS_INSTALL_DIR}\6.20\{Directory corresponding to the ITS instance}\logs directory. Therefore, in the LOGFILEPATH text box, provide the full path to the diagnostics.log file in the following format: {Instance Name}={Path to the log file}. For example, if the log file for an instance named 'ADM' is to be monitored, and ITS is installed in the C:\Program Files\SAP\ITS directory, then the LOGFILEPATH specification should be as follows: ADM=c:\Progra~1\SAP\ITS\6.20\ADM\logs\diagnostics.log. To monitor the diagnostics.log files associated with multiple instances, provide the LOGFILEPATH as a comma-separated list. For example, ADM=c:\Progra~1\SAP\ITS\6.20\ADM\logs\diagnostics.log,ITS1=c:\Progra~1\SAP\ITS\6.20\ITS1\logs\diagnostics.log.

14. Once the configuration is updated, make one more attempt to log out of the admin interface. This time, you will be prompted to configure the Processes test of the AGate server.

For more details on configuring the Processes test, refer to Configuring and

Monitoring Web Servers document. For details on configuring the Mail test, refer

to Configuring and Monitoring Mail Servers document.

15. Finally, log out of the administrative interface


21

2.2 Monitoring the AGate Server To monitor the server, do the following:


2. Click on the Components option in the menu bar, and select the Servers option from the Components menu.

3. From the COMPONENT LIST page, click on the AGate server being monitored.

C o n f i g u r i n g a n d M o n i t o r i n g t h e S A P W e b A p p l i c a t i o n S e r v e r ( S A P W e b A S )

22

Configuring and Monitoring the SAP Web Application Server (SAP Web AS) This chapter elaborates on the procedure to configure, administer, and monitor the SAP Web Application server component of the SAP Netweaver.

3.1 Configuring the SAP Web AS

3.1.1 Configuring SAP Web AS Versions Prior to v7.3 Before attempting to monitor a SAP Web AS that is of a version prior to v7.3, ensure that the following files are copied to the /opt/egurkha/lib directory (in Unix; on Windows, this will be the <EG_INSTALL_DIR>\lib directory):

com_sap_pj_jmx.jar

exception.jar

logging.jar

sapj2eeclient.jar

While the sapj2eeclient.jar is available in the {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\j2eeclient directory, the other 3 jar files reside in the {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\admin\lib directory.

Once the files are copied, restart the eG agent on the SAP Web AS.

3.1.2 Configuring SAP Web AS v7.3 (and above) To monitor a SAP Web AS v7.3 (or above), do the following:

1. Copy the sap.com~tc~bl~pj_jmx~Impl.jar file from the <SAP_WAS_HOME_DIR>\<SID>\<instance name>\j2ee\cluster\bin\ext\tc~jmx\lib\private directory to the /opt/egurkha/lib directory (in Unix; on Windows, this will be the <EG_INSTALL_DIR>\lib directory) on the eG agent host.

2. Likewise, copy the following files from the <SAP_WAS_HOME_DIR>\<SID>\<instance ID>\j2ee\j2eeclient\ directory to the opt/egurkha/lib directory (in Unix; on Windows, this will be the <EG_INSTALL_DIR>\lib directory) on the eG agent host:

sap.com~tc~je~clientlib~impl.jar

Chapter

3


23

sap.com~tc~exception~impl.jar

sap.com~tc~logging~java~impl.jar

3. Then, rename all the four files so copied as indicated below:

File Name Rename as

sap.com~tc~bl~pj_jmx~Impl.jar com_sap_pj_jmx.jar

sap.com~tc~je~clientlib~impl.jar sapj2eeclient.jar

sap.com~tc~exception~impl.jar exception.jar

sap.com~tc~logging~java~impl.jar logging.jar

4. Once the files are renamed, restart the eG agent on the SAP Web AS.

3.2 Administering the eG Manager to work with the SAP Web AS



2. If a SAP Web Application server is already discovered, then directly proceed towards managing it using the COMPONENTS - MANAGE/UNMANAGE page (Infrastructure -> Components -> Manage/Unmanage). However, if it is yet to be discovered, then run discovery (Infrastructure -> Components -> Discover) to get it discovered or add the component manually using the ADD/MODIFY COMPONENTS page (Infrastructure -> Components -> Add/Modify). Remember that components manually added are managed automatically. Discovered components, however, are managed using the COMPONENTS - MANAGE/UNMANAGE page. Figure 3.1 clearly illustrates the process of adding a SAP Web Application server.

For more details on managing components, refer to Configuring and monitoring Web

Servers document.


24

Figure 3.1: Adding a SAP Web Application server

3. Then, try to sign out of the eG administrative interface. Upon doing so, Figure 3.2 will appear listing the unconfigured tests for the SAP Web Application server.

Figure 3.2: The list of unconfigured tests for the SAP Web Application server

4. Click on the SAP WAS Beans test in Figure 3.2 to configure it. Figure 3.3 will then appear.

Figure 3.3: Configuring the SAP WAS Beans test

5. The SAP WAS Beans test measures the efficiency with which the EJB Container Service manages the enterprise bean instances deployed on the server. The EJB Container


25

provides all the services that are required by an EJB application, such as transaction and security management, clustering, persistence, network distribution of remote clients, scalable management of resources, and so on. To configure this test, specify the following in Figure 3.3.

a. TEST PERIOD - How often should the test be executed

b. HOST - The host for which the test is to be configured

c. PORT - The port number to which the server is listening

d. USERNAME - This test connects to a specific SAP web application server instance, and extracts critical metrics from it. Therefore, in the USERNAME text box, provide a valid user name which the test should use for connecting to the server instance.

e. PASSWORD - Provide the PASSWORD that corresponds to the specified USERNAME.

f. CONFIRM PASSWORD - Confirm the password by retyping it in the CONFIRM PASSWORD box.

g. INSTANCENAME - Provide the application server instance to which the test should connect. For example, if you specify tpp here, then the test will use the login credentials (USERNAME and PASSWORD) provided here to connect to an instance named TPP, which is incidentally the central instance of the SAP web application server. To know the available server instances, use the Programs -> SAP Management Console menu sequence on the application server host, and open the SAP Management Console. In the tree-structure in the left pane of the console, you will find a SAP Systems node. When you expand the SAP Systems node, the available server instances will appear as its sub-nodes. Any one of the displayed instance names can be specified in the INSTANCENAME text box.

h. CONNECTORPORT - This test uses the P4 protocol for connecting to the SAP web application server. Therefore, the port at which the P4 protocol listens needs to be specified as the CONNECTORPORT. The default port number of the P4 protocol is 50004. However, if the P4 protocol listens at a different port in your environment, then specify the exact port number here. To know the P4 protocol port, first open the adminCFG.properties file in the {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\admin\classes directory. The value specified against the LOGIN_PORT parameter in that file, is the P4 protocol port.

i. DISPATCHERID - Specify the cluster ID of the j2ee dispatcher that needs to be monitored. To know the cluster ID of the dispatcher, do the following:

Start the J2EE Engine Visual Administrator tool (see Figure 3.4) by executing the command {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\admin\go.bat at the command prompt, if you use a Windows platform. If you use a Unix platform, execute the command {SAP_WAS_HOME_DIR}\usr\sap\TPP\DVEBMGS00\j2ee\admin\go at the command prompt.


26

Figure 3.4: Starting the Visual Administrator

Figure 3.5 will appear once you connect to the SAP J2EE Engine in Figure 3.4. Login to the J2EE Engine Visual Administrator (see Figure 3.5) using a valid user name and password.

Figure 3.5: Loggin into the Visual Administrator


27

Proceed to the Global Configuration tab that appears in the left panel of the

Visual Administrator as shown in Figure 3.6.

Figure 3.6: Identifying the cluster ID of the Dispatcher

Upon clicking on the Dispatcher node in Figure 3.6, the information pertaining to that dispatcher will appear in the right panel.

Pick the cluster ID that is displayed in that panel (see Figure 3.6) and specify in the DISPATCHERID text box.

j. AUTODISCOVERY – By default, the eG Enterprise suite allows administrators to configure bean groups using the eG administrative interface, and reports metrics pertaining to every group so created. Accordingly, by default, AUTODISCOVERY is set to NO. If you want beans to be discovered and monitored automatically, then select the YES option against AUTODISCOVERY. When this is done, the eG agent automatically discovers all the beans on the SAP web application server, and reports one set of measures for every bean hosted on the server.

k. SEVERIDS – Here, specify the cluster IDs of the servers that need to be monitored, as a comma separated list. To know the cluster ID of the servers, do the following:

Login to the Visual Administrator and go to the Global Configuration tab as mentioned in the DISPATCHERID measure

A list of servers will appear in the left panel of the Visual Administrator (see Figure 3.7). Upon clicking on a particular Server node, the information pertaining to that server, including its cluster ID, will appear in the right panel.

This way, you can determine the cluster ID of each of the servers to be monitored. Specify these cluster IDs as a comma-separated list in the SERVERIDS text box.


28

Figure 3.7: Identifying the cluster ID of the Server

Providing a comma-separated list of cluster IDs will ensure that these cluster IDs alone appear as the descriptors of the test. If need be, you can have server name-cluster ID pairs appear as the test descriptors. To achieve this, the specification in the SERVERIDS text box should be of the following format: Server name:Cluster ID of the server. For example, if the cluster ID of a server named Server0 is 12621850, then you can specify the SERVERID in the format: Server0:12621850.

l. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.





7. If too many EJBs have been deployed on the server, then managing the individual EJBs could become a cumbersome task. In such a case, you can use the eG administrative interface to group EJBs and manage the groups, instead. To create an EJB group, first, wait for the SapWasBean test to run once, and then proceed to Reconfigure the test. Upon clicking the Reconfigure button in the test configuration page, Figure 3.3 will reappear. This time, click on the Click here hyperlink displayed above the parameters of the SapWasBean


29

test, and proceed to create the EJB groups using the same procedure discussed for the WLEJBTrans test.

8. Once you are done configuring the EJB groups, signout of the eG administrative interface.

3.3 Monitoring the SAP Web Application Server To monitor the SAP Web Application server, do the following:



3. From the COMPONENT LIST page, click on the SAP Web Application server being monitored.

C o n f i g u r i n g a n d M o n i t o r i n g t h e M a x D B S e r v e r

30

Configuring and Monitoring the Max DB Server This chapter elaborates on the procedure to configure, administer, and monitor the Max DB server that provides backend support to all SAP applications.

4.1 Configuring the Max DB Server Before attempting to monitor the Max DB server, do the following:

1. Connect to the URL: http://dev.mysql.com/downloads/maxdb/7.6.00.html

2. Scroll down the page that appears next to view a section titled, MaxDB by MySQL - - SAP R/3 Cerfified.

3. In that section, click on the hyperlink representing the latest version of MaxDB.

4. Scroll down the page that appears next to view the list of downloads available for the latest version. From the list, download the JDBC Driver Binary to the local host.

5. A file named sapdbc-<version>.jar gets downloaded.

6. Next, copy the sapdbc-<version>.jar file to the /opt/egurkha/lib directory.

7. Once copied, rename the sapdbc-<version>.jar file to sapdbc.jar.

8. Restart the eG agent.

4.2 Administering the eG Manager to work with the Max DB Server



2. If a Max DB server is already discovered, then directly proceed towards managing it using the COMPONENTS - MANAGE/UNMANAGE page (Infrastructure -> Components -> Manage/Unmanage). However, if it is yet to be discovered, then run discovery (Infrastructure -> Components -> Discover) to get it discovered or add the component manually using the ADD/MODIFY COMPONENTS page (Infrastructure -> Components -> Add/Modify). Remember that components manually added are managed automatically. Discovered components, however, are managed using the COMPONENTS - MANAGE/UNMANAGE page. Figure 4.1 clearly illustrates the process of adding a Max DB server.

Chapter

4

http://dev.mysql.com/downloads/maxdb/7.6.00.html


31

For more details on managing components, refer to Configuring and Monitoring Web

Servers document.

Figure 4.1: Adding a Max DB server

3. Then, try to sign out of the eG administrative interface. Upon doing so, Figure 4.2 will appear listing the unconfigured tests for the MaxDB server.

Figure 4.2: The list of unconfigured tests for the Max DB server

4. Click on the Db Connection test in Figure 4.2 to configure it. Figure 4.3 will then appear.

Figure 4.3: Configuring the Db Connection test

5. The Db Connection test measures the availability and responsiveness of the MaxDB server. To configure this test, specify the following in Figure 4.3.


32

a. TEST PERIOD - How often should the test be executed

b. HOST - The host for which the test is to be configured

c. PORT - The port number to which the server is listening

d. DATABASENAME - The test connects to a database on MaxDB and extracts performance statistics from the system tables in the database. Therefore, provide the name of a database in the DATABASENAME text box.

e. USERNAME - Since users with the SYSDBA privilege alone are allowed access to system tables, specify the name of such a user against USERNAME.

f. PASSWORD - Provide the PASSWORD that corresponds to the specified USERNAME.

g. CONFIRM PASSWORD - Confirm the password by retyping it in the CONFIRM PASSWORD box.


7. Signout of the eG administrative interface.

4.3 Monitoring the Max DB Server To monitor the Max DB server, do the following:



3. From the COMPONENT LIST page, click on the Max DB server being monitored.

C o n c l u s i o n

33

Conclusion This document has described in detail the steps for configuring and monitoring the SAP Environment. For details of how to administer and use the eG Enterprise suite of products, refer to the user manuals.

We will be adding new measurement capabilities into the future versions of the eG Enterprise suite. If you can identify new capabilities that you would like us to incorporate in the eG Enterprise suite of products, please contact [email protected]. We look forward to your support and cooperation. Any feedback regarding this manual or any other aspects of the eG Enterprise suite can be forwarded to [email protected].

Chapter

5

mailto:[email protected]

Configuring and Monitoring SAP Environment - eG … Implementer's Guides... · CONFIGURING AND...

Documents

Transcript of Configuring and Monitoring SAP Environment - eG … Implementer's Guides... · CONFIGURING AND...