During the registration of the agent, you enter the required connection data in the central monitoring system. An RFC connection to the agent is automatically created in the central monitoring system during registration. Ensure before the registration that the required configuration files are available.
Features
Depending on the agent, you perform the registration using the following command:
Agent | Registration |
SAPCCMSR | sapccmsr –R [pf= |
SAPCM3X | sapcm3x -R [pf= |
SAPCCM4X | sapccm4x –R pf= |
With SAPCCM4X,
Activities
You enter the following data during the installation:
· System ID of the central monitoring system
· System IDs of up to four (optional) additional central monitoring systems (see Registering with Multiple Central Monitoring Systems)
· For every central monitoring system, you must also enter a valid SAP user that is used once to create an RFC connection to the agent in the central monitoring system.
This user requires the authorization to execute transactions RZ20/21 (S_RZL_ADM with authorization field ACTVT and value 01) and to enter an RFC destination using transaction SM59 (S_ADMI_FCD with authorization field S_ADMI_FCD and value NADM).
In detail, you enter the following user data (if there is a default value for an entry, this is shown in square brackets. If you want to use this default value, simply press the ENTER key):
· Client
· User name
· Logon language
· Host name of the message server in the central monitoring system
· Indicator of whether load balancing is to be used for logon
· Name of the logon group for logon (in the case of activated load balancing)
· Host name of the application server for logon (in the case of deactivated load balancing)
· System number of the application server for logon (in the case of deactivated load balancing)
· Host and port of the SAProuter in the format /H/
· Indicator for a trace (0 = no, 1 = yes)
· Password of the user; the password is only used for the single logon described above and is not stored
· For every central monitoring system, you require the connection data of the gateway (usually the message server of the central monitoring system) with which the CCMS agent communicates as an RFC server.
· Host name of the gateway
· System number of the gateway
If your central monitoring system has a release status of at least SAP Web AS 6.10, the CCMS agent automatically sends alerts to the central monitoring system as an RFC client; as of SAP Web AS 6.20, the agents also automatically report the monitoring attributes.
In both cases, the agent requires an automatically valid logon to the central monitoring system. The user used for this purpose can be purely an RFC user and need not possess any rights at all, as it only calls a precisely defined function module that does not perform any additional authorization checks itself. We recommend that you use the user CSMREG for this purpose (see Creating the CSMREG User).
In detail, you enter the following data for this CSMREG user for all central monitoring systems:
· Client
· User name; by default CSMREG
· Logon language
· Host name of the message server in the central monitoring system
· Indicator of whether load balancing is to be used for logon
· Name of the logon group for logon (in the case of activated load balancing)
· Host name of the application server for logon (in the case of deactivated load balancing)
· System number of the application server for logon (in the case of deactivated load balancing)
· Host and port of the SAProuter in the format /H/
· Indicator for a trace (0 = no, 1 = yes)
· Password for the user; the password for the CSMREG user is stored in the secure store in an encrypted file called passwd.
If you are registering the CCMS agent on a Microsoft Windows host, the agent is entered and started as a service during the registration. The agent is automatically restarted at every restart. Enter the following information for this:
· Indicator of whether the service is to be automatically started
· Account under which the service is to be started
If you are installing the CCMS agent SAPCCM4X, you must specify a profile path. This profile is usually accessed using a share. You must therefore ensure that the account under which the service for the agent is running has the required network authorizations. You can ensure this by specifying SAPService
If you have successfully completed the registration, the system displays the message EXITING with code 0; if an error has occurred, the system displays this.
No comments:
Post a Comment