CCMS Configuration & Profile Maintenance

The Computing Center Management System (CCMS)allows you to monitor, control, and configure R/3. It provides functions for:
Profile maintenance
Unattended 24-hour system management using operation modes, instance definitions, and scheduling
Starting and stopping instances
Processing and controlling background jobs, scheduling database backups
Automatic reporting of system alerts
Dynamic logon load balancing
System and network monitoring and analysis


Set up the CCMS in the following steps:
Maintain R/3 profiles. Normally, you import the profiles of all active servers after installation. They are then automatically saved to the database and activated.
Define at least one operation mode.
Generate instance definitions for the instances created during R/3 System installation.
If necessary, assign instance definitions to operation modes and adapt the work process distribution.
Define the timetable for normal operation for a full 24-hour cycle.

PROFILE MAINTENANCE
In transaction RZ10, you can display administrative data for each profile, including profile name, type,version, operating system file, reference server, and modification and activation data.
There are two modes for editing profiles:
In basic mode, you can edit a set of parameters that are changed most frequently. You do not need to know the technical parameter names. Interdependent parameters are grouped together. If you change a parameter, any parameters that depend on it are adjusted automatically.
In extended mode, you can use a editing tool. You need to know the technical names of parameters and their dependencies.

The profile parameter values corresponding to resources (such as main memory, start profile, and instance profile) are created automatically during R/3 installation by the R/3 installation program R3SETUP.
When the first R/3 instance is installed, a default profile is generated in addition to the start profile and the instance profile. During installation of subsequent instances, the existing default profile is updated.
When the installation is complete, the profiles are used as parameter files for the R/3 instances and the instances are started using the values of the parameters in these profiles.
R3SETUP assigns shared memory on the server where the R/3 instance is installed.
In a distributed R/3 environment consisting of application servers of the same platform type, you should set up a global profile directory in a shared file system.
If you set parameters to incorrect values, you may find that your instances do not start. Always take care when changing parameter values and save the last version of your profiles.
After installation, profiles are stored at operating system level. Before you can change profiles for different application servers from a single screen, you must store the profiles in the database. To import them into R/3, from the profile maintenance screen, choose Utilities → Import profiles → Of active servers. All three types of profiles are imported and a first check on parameters is performed. The profiles are automatically saved in the R/3 database and are activated when they are written back to the operating system level. If you import single profile files or create profiles, you must check, save, and activate the profiles manually.

Before you leave either the basic or the extended maintenance mode, profiles changes are checked automatically and any errors or inconsistencies are displayed. After activation, all parameter changes are documented in the operating system file.
When you modify profile parameters, the changes do not take effect immediately. Dynamic switching (activation of parameters without system restart) is possible only for the memory management parameters of an instance profile.

After an application server has been started, an automatic check is performed to see whether the server's profile data as stored in the database still matches the active profiles at operating system level. If this is not the case, an alert is triggered in the Alert Monitor. This allows you to determine whether the operating system files have been changed manually. You can also perform this check manually.
Parameter attributes and documentation are available in transaction RZ11.