HP Performance Team

Page 1

Installation & Configuration Guide for the

Trend Analysis Measurement Data Collector

ERP, BW, BWA, JAVA – Release >= NW 7.00

TeCS SAP & Performance Team

Installation Manual (/HPCS/)

Version Date Authors/modified by

1.0 30th May 2011 Andreas Guhr

1.1 10th November 2011 Andreas Guhr

HP Performance Team

Page 2

The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this material. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. This document contains proprietary information and Microsoft VBA programs, which is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced or translated to another language without the prior written consent of Hewlett-Packard Company. © 1996-2011 by HP Company.

HP Performance Team

Page 3

Table of Content 1 Introduction ___________________________________________________________________ 4

1.1 Contact and useful document shares ___________________________________________ 4 2 Service Architecture and Workflow ________________________________________________ 5

2.1 Architecture _______________________________________________________________ 5 2.2 Collected Metrics ___________________________________________________________ 6 2.3 Restriction for Database Metrics: ______________________________________________ 6 2.4 Download *.tam files and download directories _________________________________ 6

3 Transports and SAP Releases _____________________________________________________ 7 4 Available Transactions and Reports after Installation of the Transport ____________________ 8 5 TAM-Service Workflow _________________________________________________________ 9

5.1 Importing the SAP Transport _________________________________________________ 9 5.1.1 Import ______________________________________________________________ 10 5.1.2 Verifying that the Import was completed ___________________________________ 10

5.2 Setting up a SAP User _____________________________________________________ 11 5.3 Starting the Data Collection _________________________________________________ 11 5.4 Dialog Transaction /HPCS/TAMS_COLL for ERP systems _________________________ 12

5.4.1 Section ‘Download Collection’ ___________________________________________ 12 5.4.2 Section ‘Download Data’ _______________________________________________ 12 5.4.3 Run the download _____________________________________________________ 13

5.5 Dialog Transaction /HPCS/TAMS_COLL_BW for BW systems _____________________ 14 5.5.1 Section ‘Download Collection’ ___________________________________________ 14 5.5.2 Section ‘Download Data’ _______________________________________________ 15 5.5.3 Run the download _____________________________________________________ 15

5.6 Dialog Transaction /HPCS/TAMS_COLL_BWA for BW systems with BW Accelerator _ 16 5.6.1 Section ‘Download Collection’ ___________________________________________ 16 5.6.2 Section ‘Download Data’ _______________________________________________ 16 5.6.3 Run the download _____________________________________________________ 17

5.7 Dialog Transaction /HPCS/TAMS_COLL_JAVA for Systems with a Java Stack _______ 18 5.7.1 Section ‘Download Collection’ ___________________________________________ 18 5.7.2 Section ‘Download Data’ _______________________________________________ 19 5.7.3 Run the download _____________________________________________________ 19

5.8 Batch mode ______________________________________________________________ 20 5.8.1 Creating a variant ____________________________________________________ 20 5.8.2 Defining and Scheduling the TAMS Background Job ________________________ 23

6 Transferring the TAMS data (.tam file(s)) from the Customer to HP _____________________ 28 7 Troubleshooting and Known Problems ____________________________________________ 29

HP Performance Team

Page 4

1 Introduction The Trend Analysis Measurement Collector is a collector set, which allows the consultant to extract important performance and configuration metrics in an easy way from any SAP system with an underlying SAP NetWeaver 7.0 and higher. The collector consists of a SAP Transport that contains all necessary programs and functions, and they are written and deployed in an own namespace “/HPCS/”. The advantage is that there are no conflicts with other developments, e.g. in the Z- and Y-namespace. The collected metrics can be used as basis for performance services like the

• Trend Analysis Measurement Service – TAMS This document includes a short introduction to the service architecture and the workflow of the TAM-Service, and then it describes the installation and collection schedule of the TAMS collector in detail. Note: This manual is intended to assist the technical HP Customer contact, typically the Account Support Manager (ASM), during the setup of the TAM-Service. Nevertheless it could be useful for the customer, too, although then specific links, FTP servers, etc. will not work properly.

1.1 Contact and useful document shares EMEA TeCS SAP & Performance Team Berliner Straße 111 40880 Ratingen Germany Tel. +49 (0) 2102 90 9442 E-Mail: performance.team@hp.com Useful document shares and links (some are only HP-internal):

Links Description http://bender.gsr.hp.com HP Customer Service - Performance Team http://bender.gsr.hp.com/hpservices/tams.aspx HP Performance Team – TAMS Info http://bender.gsr.hp.com/eservice HP Performance Team – Report Generation http://bender.gsr.hp.com/forum HP Performance Team – Discussion Forum performance.team@hp.com HP Performance Team – Mail

More information about other HP Services is available on http://www.hp.com/hps

HP Performance Team

Page 5

2 Service Architecture and Workflow

2.1 Architecture

The Service Architecture is split into 2 parts: 1. Customer Site

SAP system with applied ABAP transport for TAMS SAP GUI Front End to setup the automatic TAMS data collection or to download manually

2. HP Site Web-Server for the upload of the TAM-files Report Generation Report delivery via E-Mail Support infrastructure

HP Performance Team

Page 6

2.2 Collected Metrics Metrics out of the following SAP monitors are collected:

General configuration data ST06 - Operating system metrics ST03 - Workload statistics & Top Transactions ST02 - SAP buffer and memory configuration ST04 - Database metrics & Top SQL statements DB02 - Table space and Table History BW - BW application data, like Workload Statistic, OLAPMODE, Cube Information… BWA - Accelerator application data, Operating system metrics of the Blades …

2.3 Restriction for Database Metrics: Currently, the collector supports the following database management systems System Oracle MSSQL DB2/DB6 ERP X X X BW X Partly, some metrics will not be

collected no

BWA X Partly, some metrics will not be collected

no

JAVA X X X If a certain DBMS is not supported, the collector runs properly, but doesn't collect any DB metrics.

2.4 Download *.tam files and download directories During a data collection the metrics will be stored in a .TAM file. This file could be created in two different ways.

- Dialog GUI: During a manual download the file could either be stored on the user’s Desktop (default is ‘c:\temp’) or on the SAP application server (default is /usr/sap/’SID’/SYS/global for UNIX).

- Background Report: The default directory is /usr/sap/’SID’/SYS/global on the SAP application server, but could be changed in the program variant.

Data of multiple .TAM-files can be summarized in one report. Duplicated metrics will be removed during the data processing on the TAMS web page and the report generation.

HP Performance Team

Page 7

3 Transports and SAP Releases The TAMS transport could be used for the following Applications - Standard ERP Systems (Unicode and Non Unicode) - BW Systems (Unicode and Non Unicode) - BWA Systems - Java System with ABAP Stack (Unicode and Non Unicode) The following table gives an overview on the Transport files.

SAP Basis release (ERP and JAVA)

BW Release (BW and BWA)

Transport Zip file name

NetWeaver >= 7.00 (Non/Unicode)

BW >=7.00 + BWA (if available)

G11K9100xx TAMS_X01.xx.zip

Updated May 03, 2011 ERP = Enterprise Resource Planning BW = Business Warehouse BWA = Business Warehouse Accelerator All Applications are covered with one transport. How to install the transport is described later in the report.

HP Performance Team

Page 8

4 Available Transactions and Reports after Installation of the Transport

The following transactions and reports are available: ERP >= 7.00: Transaction: /n/HPCS/TAMS_COLL Report: /HPCS/TAMS_COLL BW >= 7.00: Transaction /n/HPCS/TAMS_COLL_BW Report /HPCS/TAMS_COLL_BW BWA >= 7.00: Transaction /n/HPCS/TAMS_COLL_BWA Report /HPCS/TAMS_COLL_BWA JAVA >= 7.00: Transaction /n/HPCS/TAMS_COLL_JAVA Report /HPCS/TAMS_COLL_JAVA

IMPORTANT:

For the JAVA report a special transport with the used Queries needs to be imported. This transport could be provided by the consultant performing the service.

Please note: In contrast to the old /HPOV/ versions of the transports the reports for dialog and background processing are the same now. Please use the listed transactions to start the collector in dialog mode and enter your input into the selection-screen rather than starting the report itself. The runtime of the data collection report mainly depends on the analysis time frame and the amount of available data in the SAP system; typically it could be up to 1000 seconds.

HP Performance Team

Page 9

5 TAM-Service Workflow This chapter describes the steps that have to be processed for the TAMS Service. The major steps are: • “Step 1: Importing the SAP Transport” • “Step 2: Setting up a SAP User” • “Step 3: Starting the data collection” • “Step 4: Transferring the TAMS data”

5.1 Importing the SAP Transport Importing the TAMS data collector is the same well-known task as any other SAP transport, providing new or updated functionality. The procedure for this task differs according to the operating system installed on the SAP servers you want to monitor. This paragraph explains the necessary steps for HP-UX/Linux servers; on Windows servers the path names are different. Alternatively, the import can be executed via the transaction /nSTMS, import overview (F5), choose system.

Figure 1: Screenshot from transaction STMS, only an example

The appropriate SAP transport for the TAMS Service can be found on the SAP & Performance Team HP Intranet Web Page http://bender.gsr.hp.com/hpservices/tams.aspx. Follow the link ‘TAMS Tools’ on the right-hand side under “Support” and select the ‘TAMS Toolset Depot’ with the transport files and further information.

HP Performance Team

Page 10

5.1.1 Import Import the SAP transport by executing the following commands as user <SID>adm after copying the file beginning with “K” into the transport directory /usr/sap/trans/cofiles (UNIX) and the file beginning with “R” into the transport directory /usr/sap/trans/data (UNIX): cd /usr/sap/trans/bin (UNIX) or disk:\usr\sap\trans\bin (windows) tp addtobuffer <Transport_Number> <SID> <pf=profil> (Windows example: disk:\usr\sap\trans\bin>tp addtobuffer G119100xx SID client=001 pf=TP_DOMAIN_SID.PFL) tp import <Transport_Number> <SID> <client_number> <pf=profil> (Windows example: disk:\usr\sap\trans\bin>tp import G11K9100xx SID client=001 pf=TP_DOMAIN_SID.PFL) where <Transport_Number> is G11K9100xx If for any reason an error occurs, you can clean the import buffer using the following command: tp cleanbuffer <SID>

5.1.2 Verifying that the Import was completed For SAP NetWeaver 7.00 and higher:

1. Call transaction /nSE01. 2. Select the following menu item:

Request Display individually Enter the <Transport_Number> in the Request/Task field.

3. Click the [Transport Logs] button to investigate further.

Note: The return codes 0 (zero) or 4 indicate a successful completion of the tp addtobuffer command. Any other return code indicates that the command completed with errors, which require further investigation.

HP Performance Team

Page 11

5.2 Setting up a SAP User You might need to ask your SAP administrator for assistance for the creation of a suitable SAP user:

1. Log in to SAP System as SAP administrator. 2. Call the transaction: /nSU01. 3. Create a new user named HPPERF. Select the Users Create menu item and specify the

following parameters: User type: DIALOG Initial password: <Password> Authorization profile: S_A.ADMIN

Note: You can also use each existing SAP user with sufficient authorizations for the service delivery. Note: Your exact actions here depend on the SAP NetWeaver version. The fields mentioned above are available in the ‘Logon Data’ and ‘Profile’ tabs. .

5.3 Starting the Data Collection You have the choice to run the data collection either in dialog mode using one of the following transactions: - /n/HPCS/TAMS_COLL for ERP - /n/HPCS/TAMS_COLL_BW for BW - /n/HPCS/TAMS_COLL_BWA for BWA - /n/HPCS/TAMS_COLL_JAVA for JAVA or to run the collector in background mode using one of the following reports with an appropriate variant in transaction SE38:

- /HPCS/TAMS_COLL for ERP - /HPCS/TAMS_COLL_BW for BW - /HPCS/TAMS_COLL_BWA for BWA - /HPCS/TAMS_COLL_JAVA for JAVA In background mode the frequency of the data collection should be 20 days for ERP, BW and Java, because the SAP system retains detailed data on the CPU and memory consumption only for the last 20 days. However, if you prefer to run the job always on the same weekday, you could schedule a 21 days frequency (i.e. missing 1 day for the above figures every time). On BWA the frequency of the collection run should be 7 days. With this setup, we can ensure a complete coverage with all data over a longer time period.

IMPORTANT:

To avoid errors during the data collection you have to logon in English (“EN”) and also specify this language for the ABAP program step of the background job.

HP Performance Team

Page 12

5.4 Dialog Transaction /HPCS/TAMS_COLL for ERP systems With this dialog transaction you are able to start the TAMS collector online for any SAP ERP system with an underlying NetWeaver release 7.00 and higher.

5.4.1 Section ‘Download Collection’ Two download scenarios are available (refer to the screenshot below):

• ‘Frontend collection’: The collected data is downloaded to the Frontend server where the GUI is started. The default download path is: C:\TEMP\TAMSCOLL_SID_YYYYMMDD_hhmmss.TAM. The default period for the data collection (“Analysis Period”) is 31 days backwards, starting from today. The default download path and/or the start date of the data collection period can be changed manually.

• ‘Server collection’: The collected data is downloaded to the server where the current SAP instance is running. The default download path is defined by the SAP instance parameter ‘DIR_CT_LOGGING', which is typically /usr/sap/’SID’/SYS/global/TAMSCOLL_SID_YYYYMMDD_hhmmss.TAM on UNIX systems (the same on Windows: replace ‘/’ by ‘\’) and can be changed manually. The default period for the data collection is 31 days backwards, starting from today and can’t be changed.

Figure 2: Screenshot of Transaction /HPCS/TAMS_COLL

5.4.2 Section ‘Download Data’ In the block ‘Download data’ you can select the performance and configuration metrics. For the TAM-Service please use the default (i.e. all options are flagged).

HP Performance Team

Page 13

5.4.3 Run the download Please note: If you type in the transaction code in the GUI, you need to add a preceding ‘/n’, otherwise you would switch on the ABAP debugger with the ‘/h’ of the transaction ‘/hpcs/tams…’ So, the complete transaction code to enter in the GUI is ‘/n/hpcs/tams_coll’. After specifying all options (or keeping the defaults) you can start the transaction and the selected data will be downloaded to the specified path. The runtime and the size of the download file vary depending on the chosen settings and on the analyzed SAP system (e.g. the number of servers and instances and the retention periods of the workload data). Typically the data collection takes 5 to 15 minutes.

IMPORTANT:

To avoid errors during the data collection you have to logon in English (“EN”) and also specify this language for the ABAP program step of the background job.

HP Performance Team

Page 14

5.5 Dialog Transaction /HPCS/TAMS_COLL_BW for BW systems With this dialog transaction you are able to start the TAMS collector online for any SAP BW system with an underlying NetWeaver release 7.00 and higher. The only difference to the transaction /HPCS/TAMS_COLL for ERP systems (see above) is the additional option in the ‘Download Data’ section: “Business Warehouse”. With this option activated certain BW figures are downloaded in addition to the ERP figures. For the TAM-Service please use the default (i.e. all options are flagged). Please refer to the screenshot below.

5.5.1 Section ‘Download Collection’ Two download scenarios are available (refer to the screenshot below):

• ‘Frontend collection’: The collected data is downloaded to the Frontend server where the GUI is started. The default download path is: C:\TEMP\TAMSCOLL_SID_YYYYMMDD_hhmmss.TAM. The default period for the data collection (“Analysis Period”) is 31 days backwards, starting from today. The default download path and/or the start date of the data collection period can be changed manually.

• ‘Server collection’: The collected data is downloaded to the server where the current SAP instance is running. The default download path is defined by the SAP instance parameter ‘DIR_CT_LOGGING', which is typically /usr/sap/’SID’/SYS/global/TAMSCOLL_SID_YYYYMMDD_hhmmss.TAM on UNIX systems (the same on Windows: replace ‘/’ by ‘\’) and can be changed manually. The default period for the data collection is 31 days backwards, starting from today and can’t be changed.

Figure 3: Screenshot of Transaction /HPCS/TAMS_COLL_BW

HP Performance Team

Page 15

5.5.2 Section ‘Download Data’ In the block ‘Download data’ you can select the performance and configuration metrics. For the TAM-Service please use the default (i.e. all options are flagged).

5.5.3 Run the download Please note: If you type in the transaction code in the GUI, you need to add a preceding ‘/n’, otherwise you would switch on the ABAP debugger with the ‘/h’ of the transaction ‘/hpcs/tams…’ So, the complete transaction code to enter in the GUI is ‘/n/hpcs/tams_coll_bw’. After specifying all options (or keeping the defaults) you can start the transaction and the selected data will be downloaded to the specified path. The runtime and the size of the download file vary depending on the chosen settings and on the analyzed SAP system (e.g. the number of servers and instances and the retention periods of the workload data). The runtime is slightly higher compared to the ERP transaction, because the BW figures are downloaded additionally.

IMPORTANT:

To avoid errors during the data collection you have to logon in English (“EN”) and also specify this language for the ABAP program step of the background job.

HP Performance Team

Page 16

5.6 Dialog Transaction /HPCS/TAMS_COLL_BWA for BW systems with BW Accelerator

With this dialog transaction you are able to start the TAMS collector online for any SAP BW system with an underlying NetWeaver release 7.00 and higher and with an attached BW Accelerator.

5.6.1 Section ‘Download Collection’ Two download scenarios are available (refer to the screenshot below):

• ‘Frontend collection’: The collected data is downloaded to the Frontend server where the GUI is started. The default download path is: C:\TEMP\TAMSCOLL_SID_YYYYMMDD_hhmmss.TAM The default period for the data collection (“Analysis Period”) is 8 days backwards, starting from today. The default download path and/or the start date of the data collection period can be changed manually.

• ‘Server collection’: The collected data is downloaded to the server where the current SAP instance is running. The default download path is defined by the SAP instance parameter ‘DIR_CT_LOGGING', which is typically /usr/sap/’SID’/SYS/global/TAMSCOLL_SID_YYYYMMDD_hhmmss.TAM on UNIX systems (the same on Windows: replace ‘/’ by ‘\’) and can be changed manually. The default period for the data collection is 8 days backwards, starting from today and can’t be changed.

Figure 4: Screenshot of Transaction /HPCS/TAMS_COLL_BWA

5.6.2 Section ‘Download Data’ In the block ‘Download data’ you can either select the figures for a TAM-Service – “Business Warehouse Accelerator (BWA)” – or the figures for the separate ‘BWA Health Check’ service.

HP Performance Team

Page 17

For the TAM-Service please use the default (i.e. “Business Warehouse Accelerator (BWA)” is flagged).

5.6.3 Run the download Please note: If you type in the transaction code in the GUI, you need to add a preceding ‘/n’, otherwise you would switch on the ABAP debugger with the ‘/h’ of the transaction ‘/hpcs/tams…’ So, the complete transaction code to enter in the GUI is ‘/n/hpcs/tams_coll_bwa’. After specifying all options (or keeping the defaults) you can start the transaction and the selected data will be downloaded to the specified path. The runtime and the size of the download file vary depending on the chosen settings and on the analyzed SAP system (e.g. the number of servers).

IMPORTANT:

To avoid errors during the data collection you have to logon in English (“EN”) and also specify this language for the ABAP program step of the background job.

HP Performance Team

Page 18

5.7 Dialog Transaction /HPCS/TAMS_COLL_JAVA for Systems with a Java Stack

With this dialog transaction you are able to start the TAMS collector online for any SAP system with a double-stack system (i.e. ABAP and Java) based on NetWeaver release 7.00 and higher. The only difference to the transaction /HPCS/TAMS_COLL for ERP systems (see above) is the additional option in the ‘Download Data’ section: “Java”. With this option activated certain Java figures are downloaded in addition to the ERP figures. For the TAM-Service please use the default (i.e. all options are flagged). Please refer to the screenshot below.

5.7.1 Section ‘Download Collection’ Two download scenarios are available (refer to the screenshot below):

• ‘Frontend collection’: The collected data is downloaded to the Frontend server where the GUI is started. The default download path is: C:\TEMP\TAMSCOLL_SID_YYYYMMDD_hhmmss.TAM. The default period for the data collection (“Analysis Period”) is 31 days backwards, starting from today. The default download path and/or the start date of the data collection period can be changed manually.

• ‘Server collection’: The collected data is downloaded to the server where the current SAP instance is running. The default download path is defined by the SAP instance parameter ‘DIR_CT_LOGGING', which is typically /usr/sap/’SID’/SYS/global/TAMSCOLL_SID_YYYYMMDD_hhmmss.TAM on UNIX systems (the same on Windows: replace ‘/’ by ‘\’) and can be changed manually. The default period for the data collection is 31 days backwards, starting from today and can’t be changed.

HP Performance Team

Page 19

Figure 5: Screenshot of Transaction /HPCS/TAMS_COLL_JAVA

5.7.2 Section ‘Download Data’ In the block ‘Download data’ you can select the performance and configuration metrics. For the TAM-Service please uses the default (i.e. all options are flagged).

5.7.3 Run the download Please note: If you type in the transaction code in the GUI, you need to add a preceding ‘/n’, otherwise you would switch on the ABAP debugger with the ‘/h’ of the transaction ‘/hpcs/tams…’ So, the complete transaction code to enter in the GUI is ‘/n/hpcs/tams_coll_java’. After specifying all options (or keeping the defaults) you can start the transaction and the selected data will be downloaded to the specified path. The runtime and the size of the download file vary depending on the chosen settings and on the analyzed SAP system (e.g. the number of servers). The runtime is slightly higher compared to the ERP transaction, because the Java figures are downloaded additionally.

IMPORTANT:

To avoid errors during the data collection you have to logon in English (“EN”) and also specify this language for the ABAP program step of the background job.

HP Performance Team

Page 20

5.8 Batch mode In general it is possible to run the reports in the background and for the data collection required for the TAM Service a regularly scheduled background job is a pre-requisite.

IMPORTANT:

To avoid errors during the data collection you have to logon in English (“EN”) and also specify this language for the ABAP program step of the background job. The variant must also be created in English (“EN”) and the job must be created and executed in English (“EN”). Otherwise, the job will not run properly.

5.8.1 Creating a variant If you want to change any settings for the data collection report (e.g. the download path), you need to create a variant. This must be done before you define the job. A default variant ‘TAMSCOLL’ is delivered with this transport for all reports. Please note: if the default settings are fine for you, depending on your SAP release you don't need to create a variant, but we recommend one for transparency reasons.

IMPORTANT:

The report name to be specified during the creation of a variant depends on the system type ERP, BW, BWA or JAVA-stack.

To create a new variant start transaction SE38 and specify the appropriate report name.

Press the button ‘VARIANTS’.

HP Performance Team

Page 21

Enter the variant name und press ‘CREATE’

Select the selection screen 9092 (only available in the namespace /HPCS/); this is the screen for Background processing. Then ‘CONTINUE’.

HP Performance Team

Page 22

In the screen above you can change the different options for the report.

- Analysis period: By default the collector collects data for the last 31 days (BW Accelerator 8 days). We recommend leaving the default setting unless you get time-out or other errors, which could be related to a too big data volume. In this case you can limit the analysis time period but have to increase the job frequency. Important note: Only complete weeks are downloaded by the collector. So, you need to make sure that no data gets lost, if you change the number of days! Handle this option with care!

- Download path: Here you can choose the path where to download the collected data. The default path is the value of SAP parameter DIR_CT_LOGGING.

- In the section ‘Download Data’ performance and configuration metrics can be selected for the collection. Disable metrics on request only, otherwise please keep the default.

- Additional performance and configuration metrics are available when selecting a different report depending on your SAP application like ‘Business Warehouse’, ‘Business Warehouse Accelerator (BWA)’ and/or ‘Java’.

IMPORTANT: Please note that the path must only be specified without the filename. The path must end with ‘/’ (Unix) or ‘\’ (Windows). The default (i.e. blank field) is

- /usr/sap/<SID>/SYS/global/ for UNIX and - G:\usr\sap\<SID>\SYS\global\ for Windows, where G: is the instance drive.

If the path field is blank, the default path (setting of parameter ‘DIR_CT_LOGGING’) will be taken.

HP Performance Team

Page 23

Press the ‘Back’ button (F3) and confirm with ‘Yes’.

In this screen give a Description and press the ‘Save’ button. Now you have created your variant and you can schedule the job as described in the next chapter.

5.8.2 Defining and Scheduling the TAMS Background Job The necessary job should be scheduled with the following frequency - 21 days, for ERP, BW and Java systems to get the operating system data on the required

detail level. Please check on BW systems how long the statistics in the tables RSDDSTAT* are held. This retention period depends on the schedule for job RSDDSTAT_DATA_DELETE (you might refer to SAP Note 1018114).If necessary, you have to run the BW job more often than every 21 days.

- 7 days for BWA

IMPORTANT:

To avoid errors during the data collection you have to logon in English (“EN”) and also specify this language for the ABAP program step of the background job.

To schedule the report in background, please use transaction SM36 and fill in the Job name, the Job class and the Target server name.

HP Performance Team

Page 24

Press button ‘START CONDITION’ and then ‘DATE/TIME’.

Enter the first start date and time as appropriate. Then, press the button ‘PERIOD VALUES’ to schedule the job on a regular basis as explained above.

HP Performance Team

Page 25

In ‘OTHER PERIOD’ fill-in 20 days for a complete coverage of the CPU and memory consumption statistics or 21 days, if you prefer to run the job always on the same weekday– or a lower number for BW systems as explained above. Press the ‘SAVE’ button 3 times for each window to get back to the start screen of SM36. Here you press the ‘STEP’ button to define the report and the variant:

HP Performance Team

Page 26

Now you have scheduled the job with the appropriate frequency and you need to add the report that should be started: /HPCS/TAMS_COLL for ERP, /HPCS/TAMS_COLL_BW for BW; /HPCS/TAMS_COLL_BWA for BWA or /HPCS/TAMS_COLL_JAVA for Java systems. Choose the default variant (TAMSCOLL) or the one you created before. SAVE again and then press the BACK button to get back to the overview screen.

SAVE once more and you are done with the job definition and schedule. In transaction SM37 you can verify your background job scheduling.

HP Performance Team

Page 27

Enter suitable selection values for the job and user names and for the ‘from’ and ‘to’ dates in the “Job start condition” box and press ‘EXECUTE’.

You should see your scheduled job.

HP Performance Team

Page 28

6 Transferring the TAMS data (.tam file(s)) from the Customer to HP Generally the following ways exist to send TAMS collection data for the service processing or report generation. Please note that a TAMS report can only be generated by an HP consultant. • Usage of the HP Insight Remote Support Advanced (ISRA) infrastructure; this is the preferred

method for HP-UX environments. Detailed information is available on the HP Intranet: http://enhanced1.sharepoint.hp.com/teams/SDA/InsightRSA/A.05.50ReleaseCommunication/IntegratingTAMSCCMonWithHPInsightRSA-A0550.pdf

• Via email to Performance.Team@hp.com or to the HP Performance Consultant.

This is the preferred method for Windows environments. When sending data via email please use the following subject: ’tams collection data, Customer name: <customer name>’. Note: The .tam files can be well compressed by common tools like ‘WinZip’.

HP Performance Team

Page 29

7 Troubleshooting and Known Problems Below you find the solution to some known problems:

1. Q: No data is collected. A: Please check if you are logged on in language “English”.

2. Q: The background Job is running endlessly. A: Please be aware that the Job was started in language ‘English’ and the variant is created in ‘English’.

3. Q: Where can I find news and postings? A: Please see the TAMS homepage on the HP intranet at

http://bender.gsr.hp.com/hpservices/tams.aspx or the FAQs at http://bender.gsr.hp.com/forum/forum.asp?FORUM_ID=19.

4. Q: If the amount of download data is very high, the collector took several minutes to finish. A: Depending on the number of servers and instances or the amount of tables in the

Database or the retention periods of the workload data the collector could run for more than 30 minutes. If the Gui dumped, please use the background mode.

5. Q: The BWA data will not be collected. A: Please be sure that the BWA destination is entered in table RSADMINA in field

TREX_RFC_DEST. This field fill be used to identify if a BWA is present.

6. Q: The transport could not imported to NW 7.02, NW 7.03 and NW 7.30 systems and you get the following error?

HP Performance Team

Page 30

A: The error could be ignored and the transport could be imported by using the unconditional mode. In transaction STMS under import the option the flag ‘ignore invalid component version’ could be set. Because the HPCS tool is only produced in the own namespace HPCS, no SAP or Basis function were changed.