SDCC Scheduled Installing & Updating Early Watch

7/31/2019 SDCC Scheduled Installing & Updating Early Watch

http://slidepdf.com/reader/full/sdcc-scheduled-installing-updating-early-watch 1/7

SDCC

Scheduled Installing & UpdatingEarlywatch

Owner: Bobby Jagdev Status: Draft

Version: 1.0 Date: April 2005 Comments: Steve Parker - First draftfor discussion

1.1 May 2005 Paul Ellis - Update

1.2 June 2005 Bobby Jagdev –Installation/ST-APIinstallation steps added

2.0 September2005

Bobby Jagdev – Procedureoverhaul to accommodatewith SAP router change.Installation stepsmodified.

1. Forward

Note: The predecessor version ST-A/PI 01E* will still be valid for service preparationuntil 10th june 2005.If you are on ST-A/PI 01E*, you can also wait until this date and then implement the01F* version together with the next version of addon ST-PI .

2. SDCC - Introduction

In addition to pre-Go Live checks, a similar level of checking can be automated usingthe SDCC transation.

Full details are available from sapnet via http://service.sap.com/earlywatch

OSS notes 144864 and 91488 describe the full setup process.

3. Earlywatch Upgrade/Installation Steps

The following tasks must be completed for a new install:

1.SDCC Installed

2.SAP Note 69455 installed, and relevant patch updates installed

3.ASM (Automated Session Manager) setup/configured to run daily

4.Dynamic EarlyWatch alert session created in SDCC

The following tasks must be completed for an upgrade:

1.RFC and SAPOSS connections verified

2.Relevant patch updates installed as notified when running program RTCCTOOL

3.ASM (Automated Session Manager) setup/configured to run daily

4.Dynamic EarlyWatch alert session created in SDCC

Page 1 / 7

http://service.sap.com/earlywatch

http://service.sap.com/earlywatch



SDCC


4. SDCC – New Installation

Installation should be carried out in client 000 as a user with SAP_ALL.

First step is to run ABAP “RTCCTOOL” from transaction SE38.

If the SDCC tool has never been installed / initialised in this system, then a screensomething like that shown below will be presented.

At this point the tool is suggesting that OSS note 91488 should be followed to installthe tool.

All 91488 says about a new installation is that note 69455 (“Add-on ST-A/PI –RTCCTOOL”) should be followed. This note is regularly updated, so the latest versionon SAPNET/OSS should be reviewed each time, but the key element is the table insection 1 which indicates which version of the ST-A/PI addon should be download fromSAPNET and installed.

Page 2 / 7



SDCC


OSS69455 specifies that the add-on should be downloaded fromhttp://service.sap.com/supporttools, but this is no longer the case as of December

2004. They should now be obtained from the general software distribution centre athttp://service.sap.com/swdc.

The latest Add on Release, ‘01F_’ can be found in the ‘EarlyWatch Rollout’ directory.Each directory contains the add on release for the specific version of SAP.

4.0B 01F_R3_40B

4.5B 01F_R3_45B

4.6A 01A_BCO46A

4.6B01F_R3_46B -> for R/3 4.6B standard systems (SAP_APPL 46B)

01F_BCO46B -> for all other systems on 4.6B basis

4.6C01F_R3_46C -> for R/3 4.6C standard systems (SAP_APPL 46C)

01F_APO30A -> for APO 3.0A systems (SAP_APO 30A)

01F_BCO46C -> for all other systems on 4.6C basis

4.6D01F_APO310 -> for APO 3.10 systems (SAP_APO 310)

01F_BCO46D -> for all other systems on 4.6D basis

6.1001F_CRM300 -> for EBP/CRM 3.00 systems (BBPCRM 300)

01F_BCO610 -> for all other systems on 6.10 basis

6.20

01F_R3_470 -> for R/3 Enterprise systems (SAP_APPL 470)

01F_CRM315 -> for CRM 3.1 or EBP 3.5 systems (BBPCRM 310 or 350)

01F_CRM400 -> for EBP/CRM 4.00 systems (BBPCRM 400)

01F_SCM400 -> for SCM/APO 4.00 systems (SCM 400)

01F_BCO620 -> for all other systems on 6.20 basis

6.40

01F_ECC500 -> for ERP 2004 / ECC 500 systems (SAP_APPL 500)

01F_SCM400 -> for SCM 4.10 systems (SCM 410)

01F_BCO640 -> for all other systems on Netweaver04 / Basis 640

Example search for the Add On Release obtained from OSS69455. IE, “01E_R3_46C”to download the appropriate add-on for R/3 standard 4.6C (SAP_APPL 46C). Pleasenote it is advisable to search on ST-A/PI

to obtain this screen

Page 3 / 7

http://service.sap.com/supporttools

http://service.sap.com/swdc

http://service.sap.com/supporttools

http://service.sap.com/swdc



SDCC


Click into the release displayed, and navigate to the “Install” section of the pop-uppresented:

Download the CAR file in the usual way and apply using SAINT as per section 2 of OSS69455.

Page 4 / 7



SDCC


5. SAP Router Validation (for updating an install)

Goto SM59 and test the connection to the following RFC connections:

- SAPNET_RFC

- SAPNET_RTCC

- SAPOSS

If the connection does not work follow the procedure below.

a. Configure the SAP Router

- Goto transaction OSS1

- Goto Parameter > Technical Settings

- Click on Change

- Change the IP address of SAPRouter 2 to 163.164.21.34

- Save

- Run transaction OSS1 again

- Click on ‘Logon to SAPNet’

- Continue using group 1_Public

- Once you have a SAP GUI was started notification on the

status bar and a new window opens, close the new windowdown and go to the next step.

- If this connection test does not work, attempt toping/tracert 163.164.21.34 on the server. The ping may notwork due to a firewall restriction. If the tracert isunsuccessful, log a call with the server management teamto create the routes to it. Servers hosted in Bridgend willrequire a CPMS to be raised.

b. Configure SM59 Connections

- Edit SAPOSS

- Change the Load distribution to No and press enter

- Change the target host to:

/H/<DEV System IP Address>/S/sapdp99/H/163.164.21.34/S/sapdp99/H/194.117.106.129/S/sapdp99/H/oss001

- Change the system number to 01.

- Replicate this change on SAPNET_RTCC and SAPNET_RFCand perform a connection test.

6. SDCC – Updating a Previous Installation

Before attempting this section please ensure section 5 has been followed.

Page 5 / 7



SDCC


If the SDCC tools have previously been installed and configured, then a screen morelike this will be presented when running RTCCTOOL.

In this example, as all the traffic lights are green, then the updates against them havebeen applied.

Use the “Refresh from SAPNET” option under the “List” pulldown of the above screento connect to the OSS knowledge base and check for any required updates. If any arefound, then installation instructions are displayed in an updated version of the screenabove.

Page 6 / 7



SDCC


7. SDCC – Scheduling periodic checks

Once the ST-A/PI add-on is installed / configured, they are accessed via transaction

SDCC.

From here, the collector and transmitter jobs (that gather Earlywatch data and sendto SAP) can be displayed via the Session pulldown menu and the Display -> Jobsoption.

The ”Automated Session Manage” (ASM) pulldown controls the scheduling of these jobs.

“Control” allows setup of the central ASM job itself.

“Settings” allows automated setup of the other required jobs.

8. SDCC – Retrieving Reports

Once a report has been produced from the uploaded data, it is delivered to thecustomer’s SAPNET Inbox .

Go into “Search Options” and “Service Messages”

Click on the desired “SAP EarlyWatch Alert Service” session to retrieve the report.

Page 7 / 7

Documents

SDCC Scheduled Installing & Updating Early Watch