You want to perform an upgrade between the following releases for a system.
Start Release: up to SAP NetWeaver 7.0 EhP 1 (inclusive)
Target Release: SAP NetWeaver 7.0 EhP 2 or as of SAP NetWeaver 7.1
This section describes what you need to take into account during an upgrade of this type with regard to monitoring with CCMS Agents, since the relevant infrastructure was significantly enhanced between these releases.
The following types of system are discussed:
Dual-stack systems (ABAP and Java)
During the activities described below, among other things, you need to move the contents of directories, since various directories for CCMS agents have changed after SAP NetWeaver 7.0 EhP 1. These directories have the following paths:
SAPCCMSR -j2ee (for monitored Java and TREX systems)
Working Directory (more information: Working Directory and Log Files of the CCMS Agents)
Up to SAP NetWeaver 7.0 EhP 1 (UNIX): /usr/sap/ccms/<SysID>_<SysNr>/sapccmsr
Up to SAP NetWeaver 7.0 EhP 1 (Microsoft Windows): [drive]:\usr\sap\ccms\<SysID>_<InstNr>\sapccmsr
As of SAP NetWeaver 7.0 EhP 2 / SAP NetWeaver 7.1: $DIR_LOGGING\sapccmsr, that is, by default <instance directory>\log\sapccmsr
Logmon Directory (more information: Monitoring Files with CCMS Agents):
Up to SAP NetWeaver 7.0 EhP 1 (UNIX): /usr/sap/ccms/<SysID>_<InstNo>/logmon
Up to SAP NetWeaver 7.0 EhP 1 (Microsoft Windows): [drive]:\usr\sap\ccms\<SysID>_<InstNo>\logmon
As of SAP NetWeaver 7.0 EhP 2 / SAP NetWeaver 7.1: $DIR_LOGGING\logmon, that is, by default, <instance directory>\log\logmon
SAPCCM4X (for monitored ABAP systems)
These directories do not change during the upgrade:
Working directory: $DIR_LOGGING\sapccm4x, that is, by default, <instance directory>\log\sapccm4x
Logmon directory: $DIR_LOGGING\logmon, that is, by default, <instance directory>\log\logmon
The procedure is as follows, depending on the release of the central monitoring system (CEN):
I. No CEN
You have not previously used central monitoring in the context of the CCMS monitoring infrastructure; that is, you have not registered any CCMS agents with CEN for the system for which you want to perform an upgrade. Perform the appropriate steps for the system type of the monitored system:
ABAP-only system/Java-only system/TREX
You do not need to perform any steps with regard to CCMS agents in these cases.
For a dual-stack system up to SAP NetWeaver 7.0 EhP 1, the CCMS agent SAPCCMSR -j2ee should always be registered with the local ABAP stack, even if you are not operating central monitoring. As of SAP NetWeaver 7.0 EhP 2 or SAP NetWeaver 7.1, you no longer require a local agent for this purpose; therefore, deregister the agent in the Visual Administrator of the AS Java before upgrading:
In the navigation bar, choose.
Choose the CCMS Agent Configuration button, and enter the passwords of the specified users.
II. CEN with SAP NetWeaver 7.0
You use a system with the release SAP NetWeaver 7.0 as a central monitoring system (for example, if you are using a Solution Manager). In this situation, you still need to use CCMS agents for central monitoring after upgrading your monitored system to SAP NetWeaver 7.0 EhP 2 or SAP NetWeaver 7.1 (more information: CCMS Agents: Central Monitoring for Components up to SAP NetWeaver 7.0).
Note that to monitor an ABAP or dual-stack system with release SAP NetWeaver 7.0 EhP2 or SAP NetWeaver 7.1 in this scenario, you still require the CCMS agent SAPCCM4X in any case; that is, registering the monitored ABAP stack using only RFC destinations (transaction RZ21, choose ) is not sufficient.
In any case, stop all CCMS agents for the monitored system before the upgrade with the command -stop; the executables are in the DIR_EXECUTABLE directory (more information: Controlling CCMS Agents).
You can determine all agents for a monitored system that are registered with a CEN by calling the topology browser in CEN. To do this, call transaction RZ21, and, in the Topology group box, choose the Agents for Remote Systems radio button and chose Display Overview (more information: Monitoring Agents in the Topology Display).
For a dual-stack system, you should also deregister the SAPCCMSR -j2ee agent as described above ( No CEN scenario). You should also perform the appropriate steps below for the system type of the monitored system:
After the upgrade, you can restart the agent with the command -DCCMS; the executable is in the same location as before the upgrade (more information: Controlling CCMS Agents).
Perform the following steps:
The working directory and the default directory for the logmon templates change for the CCMS agent SAPCCMSR -j2ee between SAP NetWeaver 7.0 EhP 1 and SAP NetWeaver 7.0 EhP 2. You therefore need to move the entire contents of the directory from the old directories to the new directories (the paths are listed above); if the directories do not exist in the target release, create them manually.
After the upgrade, you can restart the agent with the command -DCCMS; the executable is in the same location as before the upgrade.
Perform the following steps:
Move the contents of the logmon directory for the agent SAPCCMSR -j2ee in the start release to the logmon directory for the agent SAPCCM4X in the target release. If the target directory does not exist, create it manually at the specified path.
The functions of SAPCCMSR -j2ee are performed by SAPCCM4X after the upgrade. Therefore, if you have made manual settings in the SAPCCMSR.INI configuration file for SAPCCMSR -j2ee in the start release, you need to manually transfer these entries to the SAPCCMSR.INI configuration file for SAPCCM4X in the target release. The SAPCCMSR.INI configuration file is in the working directory of the relevant agent (more information: SAPCCMSR.INI: Configuration File for the CCMS Agents).
After you have performed the upgrade and transferred the content described above, you can restart the agent with the command -DCCMS; the executable is in the same location as before the upgrade.
Proceed as described in the TREX documentation, in the Monitoring with CCMS topic.
III. CEN with a release as of SAP NetWeaver 7.0 EhP 1
You are using a central monitoring system with a release as of SAP NetWeaver 7.0 EhP 1. This means that you no longer require any CCMS agents for this system after upgrading the monitored system. Perform the following steps:
Before the upgrade, deregister all CCMS agents for the relevant monitored system.
As of SAP NetWeaver 7.0 Eh2, all functions of these agents are integrated into the SAP NetWeaver Management Agents, meaning that CCMS agents no longer exist as standalone executables as of this release. However, the SAP NetWeaver management agents still take account of the information in the specified working and logmon directories of the CCMS agents. You should therefore move the contents of these directories as required for your system type, as specified above in the scenario CEN with SAP NetWeaver 7.0.
Since you have deregistered the CCMS agents, you cannot restart them. Therefore, register the monitored system with CEN again after the upgrade by calling transaction RZ21 in CEN, and choosing Registering SAP NetWeaver Components and Hosts in CEN).(more information: