SAPCCM4X Agent Installation

Hi!
I would like to set up the SAPCCM4X agent on the satellite system.
The installation with the commando >sapccm4x -R pf=... endes without any errors.
The problem is that the appropriate SAPCCM4X.03 Windows Service stops after 5 sec.
How can I solve this problem?
Thank you
Jürgen

Hi!
Many thanks for your answer.
The output on the CMD console is:
INFO: trying to register service SAPCCM4X.03 at Windows Service Control Manager
starttype of service:             manual/[auto] :
DomainName\UserName  or [<LocalSystem account>] :
INFO: Agent is running (no actual pid, but actual shared memory!)
WARNING: Service SAPCCM4X.03 already stopped. But agent is running!
WARNING: The following service is registered but could not be started
SAPCCM4X.03  
(command ["E:\usr\sap\SC3\SYS\exe\run\sapccm4x.exe" -Service
pf=E:\usr\sap\SC3\SYS\profile\SC3_DVEBMGS03_VMSAP01]   user <LocalSystem account>)
INFO: Updated config file E:\usr\sap\SC3\DVEBMGS03\log\sapccm4x\csmconf.
EXITING with code 0

Similar Messages

  • Installation problems with SAPCCM4X Agent

    Hi!
    I would like to install a SAPCCM4x agent on windows and have two problems.
    By one of the systems when i execute the commando for the installation sapccm4x -R pf=...
    I get the following error message:
    ERROR: Cannot open Monitoring Segment 0 rtc = 245
    Last reported error: 249 CCMS monitoring segment has wrong EYE CATCH: CCMS monitoring segment belongs to a non-ABAP
    SAPCCM4X of release 7.00 is to be used only to monitor ABAP instances of kernel release 7.00 (NW04s) or 6.40.
    By the second system I can install the SAPCCM4X agent, but the agent is stopped after 3 seconds.
    I have looked into the log files I do not detect any problems.
    Can some one help to solve the problems ?
    Thank you very much!
    regards
    Thom

    Hi,
    I could install XE in my (physical) machine with FC4 without any particular issue (just had to add some swap space); I also had to remove reference to ORACLE* environment variables prior to install the rpm (the rpm install warned me about both of the issues)
    I just miss the menu icons that are correctly installed in suse: did you manage to have them?
    Regards,
    Andrea

  • Installation of SAPCCM4X-Agent on Windows Cluster

    Hi!
    I woulld like to install SAPCCM4X-Agent on Windows Cluster.
    Does anyone know the procedure here (e.g. install the agent twice on both nodes, etc.)...
    Thank you very much!
    regards
    Thom

    Hello Thom,
    Here is a note that will help you out.
    SAP Note 536954 - OS data in a cluster environment for OS07
    As per the note
    The CCMS agent must be located on a shared disk, so that the cluster administrator software can start the service later.
    Regards,
    Siddhesh
    Edited by: Siddhesh Ghag on May 27, 2008 11:02 AM

  • FAM 8.0, Tomcat J2EE agent installation problem

    Hello:
    I was able to install FAM 8.0 in Tomcat 6.0.14 on Ubuntu (7.04) Linux. Everything seems fine. In the end, the applications I want to use with OpenSSO also make use of Tomcat 6.0.14. I noticed on the opensso users email list that the Tomcat 3.0 agent won't be available until early next year; but that the 2.2 agents should work with FAM 8.0. So, I got the the J2EE agent for Tomcat - SJS_Tomcat_Server_55_agent_2.2-01.tar.gz. The documentation makes no references to Tomcat 6, and I'm hoping this is due to the fact that Tomcat 6 was not available when the documentation was written.
    Does this agent work with Tomcat 6? I have this problem when installing the agent (agentadmin --install):
    $CATALINA_HOME environment variable is the root of the tomcat
    installation.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the $CATALINA_HOME environment variable: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
    Invalid directory specified for the $CATALINA_HOME environment variable
    Invalid CATALINA_HOME directory :
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14I can see in debug/agentadmin.log the following:
    [05/24/2008 13:06:37:684 PDT] FileSystemValidator : Is directory : /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14 valid ? true
    [05/24/2008 13:06:37:686 PDT] HomeDirValidator : Is $CATALINA_HOME directory /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14 valid ? false
    [05/24/2008 13:06:37:686 PDT] Invalid CATALINA_HOME directory : /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14This directory does indeed exist, and is accessible by the user I'm logged in as. It appears FileSystemValidator agrees with me, but HomeDirValidator has a problem. I tried this on both Ubuntu 6.04 and Mac OS X 10.5.2. Does this indicate that Tomcat 6 is not supported? Or is it indicative that neither OS on which I've tried to install the agent is officially supported?
    Thanks!
    Jeff

    Hi Denis:
    Before being redirected to another short term task, I did indeed get the Tomcat 6 agent to work. I probably won't be able to look at OpenSSO again seriously for another couple of months. :(
    I have the OpenSSO server running on Tomcat 6.0.14 on Ubuntu 6.x Linux running in a virtual machine on my Mac. I was not able to get the server to run directly on the Mac, and I cannot remember the reason at this time.
    But, as far as the agent goes, I run it again using Tomcat 6.0.14 on my Mac (Mac OS X 10.5.2), using the 1.5 JRE. I do have the agentapp war deployed as well as the agentsample web application to play with. In my catalina.out file:
    Jun 18, 2008 10:07:20 AM org.apache.catalina.core.StandardEngine start
    INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
    Jun 18, 2008 10:07:20 AM org.apache.catalina.startup.HostConfig deployWAR
    INFO: Deploying web application archive agentapp.war
    Jun 18, 2008 10:07:21 AM org.apache.catalina.startup.HostConfig deployWAR
    INFO: Deploying web application archive agentsample.war
    Jun 18, 2008 10:07:22 AM org.apache.coyote.http11.Http11Protocol start
    INFO: Starting Coyote HTTP/1.1 on http-8090
    Jun 18, 2008 10:07:22 AM org.apache.jk.common.ChannelSocket init
    INFO: JK: ajp13 listening on /0.0.0.0:8011
    Jun 18, 2008 10:07:22 AM org.apache.jk.server.JkMain start
    INFO: Jk running ID=0 time=0/16  config=nullI have no error messages is any Tomcat log file.
    I checked out the source code for the Tomcat v6 agent (2.2) on May 27, so I don't know how that compares to yours or what's been checked into CVS since my build. I also don't know what the OpenSSO NamingService is.
    I assume you used fully qualified domain names to specify the web application to be protected by agent as well as the OpenSSO server itself. The following is the output of the conversation when I run the agent installer script on my system. It has been redacted a bit (domain name and encryption key) to protect my client, but otherwise this is what I supplied to the installer:
    Enter the complete path to the directory which is used by Tomcat Server to
    store its configuration Files. This directory uniquely identifies the
    Tomcat Server instance that is secured by this Agent.
    [ ? : Help, ! : Exit ]
    Enter the Tomcat Server Config Directory Path
    [/opt/apache-tomcat-6.0.14/conf]: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf
    Enter the fully qualified host name of the server where Access Manager
    Services are installed.
    [ ? : Help, < : Back, ! : Exit ]
    Access Manager Services Host: login.opensso.example.com
    Enter the port number of the Server that runs Access Manager Services.
    [ ? : Help, < : Back, ! : Exit ]
    Access Manager Services port [80]: 8080
    Enter http/https to specify the protocol used by the Server that runs Access
    Manager services.
    [ ? : Help, < : Back, ! : Exit ]
    Access Manager Services Protocol [http]:
    Enter the Deployment URI for Access Manager Services.
    [ ? : Help, < : Back, ! : Exit ]
    Access Manager Services Deployment URI [/amserver]: /opensso
    Enter the fully qualified host name on which the Application Server
    protected by the agent is installed.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the Agent Host name: analysis.opensso.example.com
    $CATALINA_HOME environment variable is the root of the tomcat
    installation.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the $CATALINA_HOME environment variable: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
    Choose yes to deploy the policy agent in the global web.xml file.
    [ ? : Help, < : Back, ! : Exit ]
    Install agent filter in global web.xml ? [true]:
    Enter the preferred port number on which the application server provides its
    services.                          
    [ ? : Help, < : Back, ! : Exit ]
    Enter the port number for Application Server instance [80]: 8090
    Select http or https to specify the protocol used by the Application server
    instance that will be protected by Access Manager Policy Agent.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the Preferred Protocol for Application Server instance [http]:
    Enter the deployment URI for the Agent Application. This Application is used
    by the agent for internal housekeeping.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the Deployment URI for the Agent Application [/agentapp]:
    Enter a valid Encryption Key.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the Encryption Key [XXmyencryptionkeyXX]:
    Enter a valid Agent profile name. Before proceeding with the agent
    installation, please ensure that a valid Agent profile exists in Access
    Manager.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the Agent Profile name: testagent1
    Enter the path to a file that contains the password to be used for identifying
    the Agent.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the path to the password file: /Users/jas/Development/opensso/tryout/agent_password
    SUMMARY OF YOUR RESPONSES
    Tomcat Server Config Directory :
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf
    Access Manager Services Host : login.opensso.example.com
    Access Manager Services Port : 8080
    Access Manager Services Protocol : http
    Access Manager Services Deployment URI : /opensso
    Agent Host name : analysis.opensso.example.com
    $CATALINA_HOME environment variable :
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
    Tomcat global web.xml filter install : true
    Application Server Instance Port number : 8090
    Protocol for Application Server instance : http
    Deployment URI for the Agent Application : /agentapp
    Encryption Key : XXmyencryptionkeyXX
    Agent Profile name : testagent1
    Agent Profile Password file name :
    /Users/jas/Development/opensso/tryout/agent_password
    Verify your settings above and decide from the choices below.
    1. Continue with Installation
    2. Back to the last interaction
    3. Start Over
    4. Exit
    Please make your selection [1]: 1
    Updating the
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/bin/setclasspath.sh
    script with the Agent classpath ...DONE.
    Creating directory layout and configuring Agent file for Agent_001
    instance ...DONE.
    Reading data from file
    /Users/jas/Development/opensso/tryout/agent_password and encrypting
    it ...DONE.
    Generating audit log file name ...DONE.
    Creating tag swapped AMAgent.properties file for instance Agent_001 ...DONE.
    Creating a backup for file
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/server.xml
    ...DONE.
    Creating a backup for file
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/web.xml
    ...DONE.
    Adding SJS Tomcat Agent Realm to Server XML file :
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/server.xml
    ...DONE.
    Adding filter to Global deployment descriptor file :
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/web.xml
    ...DONE.
    Adding SJS Tomcat Agent Filter and Form login authentication to selected Web
    applications ...DONE.
    SUMMARY OF AGENT INSTALLATION
    Agent instance name: Agent_001
    Agent Configuration file location:
    /Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/config/AMAgent.properties
    Agent Audit directory location:
    /Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/logs/audit
    Agent Debug directory location:
    /Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/logs/debug
    Install log file location:
    /Users/jas/Development/opensso/tryout/tomcat_v6_agent/logs/audit/install.log
    Thank you for using Access Manager Policy Agent
    [jaslap:tryout/tomcat_v6_agent/bin] jas% Can you post the exception details you're getting. That might help someone diagnose the problem.
    Take it easy,
    Jeff

  • ZLM Agent IR2 agent installation fails

    Hi all
    I have installed ZLM 7.3 IR2 Server in SLES 10 SP2. The ZLM Server setup is not able to complete on sles11 server, the system hangs. Also when trying to install the ZLM 7.3 IR2 agent on SLED 11 OS, the installation starts & hangs in the middle.
    Some of the error messages are
    1)Error no 111 Connection Refused
    2) when executed the zlm-config file it displays the "OS is not supported version"
    The SuSEfirewall is set to stop & iptables rules were not set.
    I have tried the ZLM 7.3 IR2 agent installation in a freshly installed SLED 10 machine, but the machine is not able to contact the server (host name not found). I have not configured DNS service in the server machine. Please provide suggestions in the ZLM 7.3 IR2 agent installation.

    baranii,
    a few questions for my understanding:
    I have installed ZLM 7.3 IR2 Server in SLES 10 SP2.
    This is a running ZLM server and you try to register the other devices to this server. Correct ?
    The ZLM Server setup is not able to complete on sles11 server, the system hangs.
    SLES 11 or SLES 11 SP1 ? For SLES 11 SP1 you would need to use ZLM 7.3 IR3.
    Do you want to install another ZLM server on this SLES 11 server or just the agent ?
    I have tried the ZLM 7.3 IR2 agent installation in a freshly installed SLED 10 machine, but the machine is not able to contact the server (host name not found). I have not configured DNS service in the server machine.
    The agent must be able to resolve the dns name of the zlm server.
    You can either configure DNS or you can add an entry to the /etc/hosts file of the managed device. But you must make sure the device can afterwards ping the ZLM server by its name. (ping <ZLM Server Name>).
    It is possible to register the zlm server by its ip address and not by it's name, but5 I would recommend to use the dns name.
    So if you have fixed the name resolution and retry the agent installation, verify the zlm-install.log file if a installation fails. That log file is available in /var/opt/novell/logs/zenworks. Go from the end back and look for errors or warnings.
    Rainer

  • SAPCCM4X agents are shutting down by itself

    Hello Gurus
    A few SAPCCM4X agents are shutting down by itself and this is happening
    for systems which have a version 4.6c and 4.5B in our landscape like PCX.. Analyzing the log of one of this agents the
    message below is informed:
    Mon May 9 04:41:10 2011
    CCMCTRL: ERROR: csm_show_file: no permission to
    read /usr/sap/PCX/SYS/profile/PCX_G34_zonepcx
    CCMCTRL: ERROR: csm_show_file: Please check sapccmsr.ini
    I tried to find the profile mentioned in the warning but with no
    succes. The cause of the shutdown of the agent is that because the
    correct profile is PCX_DVEBMGS34_zonepcx instead of PCX_G34_zonepcx but
    why it is looking for the wrong one when everything is configured with
    the profile PCX_DVEBMGS34_zonepcx . I also checked sapccmsr.ini but
    found nothing.
    I  can start the agent normally choosing the correct parameter
    (PCX_DVEBMGS34_zonepcx) but sometimes the agent shutdown by itself
    after 3-4 days with the error message above.
    Why the agent search for the wrong profile and where can I change it to
    the right profile ?
    Or is there any other way to resolve it.
    Thanks and Regards
    Ashwini

    Thank you Mani, I will make this test in only one appl server and monitor.
    I will let you know the resul of my tests.
    Regards

  • Need Agent Installer for Solaris (SPARC)

    Hi All,
    I have downloaded Grid Control Agent Installer for Solaris from http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html.
    When I tried to extract the zip file, I am getting the following error message.
    "Can not open file. It does not appear to be a valid archive. If you downloaded this file, try downloading the file again."
    Even I tried using http://sac.us.oracle.com/download/index.html also but getting the same error.
    Please send me the location if you have,
    Thanks
    Sumathi

    Most commands are identical. Performance analysis, loading all are similar. Tape interaction, creation of tape devices is going to be pretty much the same.
    The differences show up a lot at the hardware level. HBAs aren't usually the same, many drivers (and their quirks) are different between the architectures. If you're debugging connectivity to a tape library, those differences may be critical.
    So you can't get as close as you may want, but I'll bet it would still be helpful.
    Darren

  • MBSA Windows Update Agent installation

    I'm implementing MBSA on our domain.  I've worked through the various firewall issues, etc.  Next I received a Security Update Scan Result that "Computer has an older version of the client and security database demands a newer
    version. Current version is and minmum required version is ."  This is pasted directly from the screen.  It appears information is missing from the message.
    Based on research of the message, I reran the scan with the "Configure computers for Microsoft Update and scanning prerequisites" option selected.  Then I get the result "Windows Update Agent installation succeeded.Restart
    the target computer to have Windows Update Agent updated completely."  Scanning the computer after a restart just repeats the same results.  Looking in the WindowsUpdate.log on the target computer, there are messages stating that 3
    CBS packages were evaluated and that each is not applicable.  "WUESTUP has finished.  Exit code is 0.  Reboot is NOT needed."  I have checked and the
    wuaueng.dll version is 7.6.7600.256, which I believe is the latest.
    I have seen this result on multiple Windows 7 computers I have tested.  None have worked so far.  What is causing MBSA to report one thing and the target to indicate something else?
    Ken Kemp Eddy County, NM IT

    At this point, no.  Since I didn't turn up an answer here, I've had to set this aside for more pressing matters.  I hope to get back to it at some point soon.
    If you are fortunate enough to find an answer, please be sure to share it here.
    Ken Kemp Eddy County, NM IT

  • Diagnostics Agent 711 - SAP Host Agent - Installation on a cluster environm

    Dear all,
    We have the following architecture in our productive environment :
    1. Cluster 01 is composed of 2 nodes.
       On Cluster 01, only "Database" and "Central Services" are running
       for 5 productive SAP systems.
    2. Cluster 02 is composed of 6 nodes.
       On Cluster 02, only "Central Instance" and "Application Server"
       are running for 5 productive SAP systems
    As read in "Diagnostics Agents installation Strategy", rules #4, slide 12 :
    ===================================================================
    - Do not install a Diagnostics Agent on host that only run Database
      or SAP Central Services.
    - Install a Agent on EACH host running a Central Instance (CI)
      and / or a Dialog Instance
    ===================================================================
    For our productive environment, we do have to install Diagnostics Agents 7.11 on cluster 02 where we have CI + AS running.
    Questions :
    1. How do we monitor "database" and "central services" data on cluster 01 (DB + CS) as far as no "Diagnostics Agents"
       are installed ?
    2. Do we have to install the new "SAP HOST AGENT" in our cluster 01 ?
    3. As written in "Downloading and Installing Package SAPHOSTAGENT"
       guide, "you only need to install the host agent host taht not have
       an SAP Component". Does it mean that the new "SAP HOST AGENT"
       will have to be installed on our cluster 01 to monitor "DB+CS" data ?
    4. What are for SAP a host that not have SAP Component ... ?
        "Database" and "Central Service" running for a SAP system should be consider as SAP Component or not ... ?
    5. What is the difference between the new "SAP HOST AGENT" delivered by SAP today 23.11.2009
        and the "Wily Host-Level Introscope Agent"
       delivered by CA ?
    Best regards
    PC

    Yes, it has to be installed.

  • Audit Vault Agent Installation issue

    Hi All,
    I have installed the following things
    1) Audit Vault Server (10.2.2.0.1) on a Windows 2003 Server
    2) I completed the post-installation tasks
    3) I am trying to install Audit Vault agent (10.2.2) on HPUX (11.11) machine.
    I start the AV Agent runInstaller, and fill the details like AVAgent name, Username, connect String etc, then click on next , it throws the following error:
    "error1: the AV server is expecting an agent with the given name to be installed on another machine"
    I am able to ping from Windows to HP machine and Vice versa (By IP Address and Hostname).
    Can anyone tell me where i am going wrong and how to solve it.
    Please mail to my email address ([email protected])
    Thanks & Regards,
    Rakesh

    Hi,
    The details of the installation done so far:
    1) I have installed "Oracle Audit Vault Server (10.2.2)" on a Windows 2003 machine providing the following details
    a) Audit vault Name
    b) Audit Vault Home
    c) Audit Vault Administrator
    d) Administrator Password
    e) Audit Vault Auditor
    f) Ausitor Password
    g) Database Vault Owner and Manager
    h) Created a Audit Vault Agent user and added the user to the udit Vault server using AVCA.
    2)I invoke the "Audit Vault Agent" Installer from a HP-UX machine and provide details viz.,
    a) Audit vault Agent Name (Same name when i executed the AVCA command above)
    b) Aduit Vault Agent Home
    c) Agent Username
    d) Agent Password
    e) Audit Vault Server Connect String (Provide the Database details as mentioned in Audit Vault Server (localhost:port:servicename)
    and when i click on the next button it throws me the following error:
    "error1: the AV server is expecting an agent with the given name to be installed on another machine".
    Hope this gives you a better idea. Waiting for your reply.
    Thanks & Regards,
    Rakesh

  • How to deployment for AV agent installation on RAC enviroment?

    before the AV agent installation on RAC , the agentname and agentuser should be added to av server first. only one agentname/agentuser for the two nodes, or one agentname/agentuser for each node ? also ,the agentusr and the avsrcusr account only one account for two node ?
    1. how to tell the agentname and agentuser account before agent installation ? more details are better.
    2.with the 9i RAC DB at AIX, need install CRS first?
    3. I setup an Linux cluster enviroment ,and a windows cluseter envirement(no CRS installed). but when install the agent , if the agentname set to hostname of the virtual IP ,the error is : ERR0R1: The av server is expecting the agent with given name to be installed in another machine. if input the agentname (which agenthost is node1) , it contiued,but no "node select GUI" comes up (according to the the GUI of Morgan's Library at: http://www.psoug.org/reference/audit_vault.html
    ),it executes a single agent installation on node1.
    I don't know it's wrong configuration of my linux or windows cluster enviroment , or there are some import steps missed ?
    it's urgent ,thanks!!
    --the node's hostname and  IP :
    #public
    192.168.0.11 node1
    192.168.0.12 node2
    #private
    192.168.8.11 node1-private
    192.168.8.12 node2-private
    #vip
    192.168.0.99 node
    agentname: agentwin with agenthost node
    agentname : agentwin01 with agentost node1
    Message was edited by:
    user634185

    It is not urgent ... no one is drowning, your house is not on fire, so please don't abuse this forum. Thank you.
    Audit Vault is auditing one database ... multiple instances. First create the RAC cluster the way you normally would. Then go to any single cluster node and install the agent. The agent installation will recognize that it is a cluster and ask you whether you want to install on one or all nodes and let you choose which ones.
    There is no need to perform separate installations on each node.

  • 11.1.0.1.0 agent installation failure

    I have successfully installed 11g grid control on Linux RHEL 5 x86_64
    While installing the agent using oms push on to other Linux RHEL 5 x86_64 machine in installation phase its getting failed. I am not able to figure it out how to resolve the issue.
    The errors in log specified are like these
    install.err Logfile content
    ls: /opt/oracle/product/11gagent//agent11g/cfgtoollogs/oui/: No such file or directory
    grep: /opt/oracle/product/11gagent//agent11g/cfgtoollogs/oui//: No such file or directory
    grep: /opt/oracle/product/11gagent//agent11g/cfgtoollogs/oui//: No such file or directory
    agentInstall.sh030211140140.log
    Agent installation on node linuxserver1 fails for default shiphome
    ********************************

    Hi ,
    could you please check if the directories
    /opt/oracle/product/11gagent//agent11g or /opt/oracle/product/11gagent/
    do exist at all?
    Have you installed an agent on the node before?
    Please check the logfile "OC4J~OC4J_EM~default_island~1" of the OMS
    for messages like
    'agentpush_Install_NotDefaultShiphome' failed orThe action 'agentpush_Install_CollectLog' failed.
    as well (could be found under $OMS_HOME/opmn/logs). If you have found those errors please let me know...
    HTH

  • CCMS agent installation

    Hi Experts,
    I am doing SAP CCMS agent installation to monitor a non-SAP system which will be monitored by a Central monitoring system.
    I have followed all the steps as:
    http://help.sap.com/saphelp_nw04/helpdata/en/a8/adf7409b9d8531e10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/e2/eff640fa4b8631e10000000a1550b0/frameset.htm
    1. communication user CSMREG in Central monitoring system.
    Created the CSMCONF start file for CCMS agents in monitoring system.
    2. CCMAGENT.SAR , SAPOSCOL.SAR ,  INSTALL_WIN.SAR
    And done the configurations required in the monitored system.
    3. Register the CCMS agent with CEN and start the agent. By following this step:
    <hostname>\saploc\prfclog\sapccmsr.exe -R*
    while registering the CCMS agent ,
    I ma getting this...
    This CCMS agent program sapccmsr is able to actively report alert data into the monitoring system[CEN], which is the central monitoring system.
    to enable this feature, you have to setup the user CSMREG in [CEN].
    After entering the RFC logon info for the user,
    client:001
    user:CSMREG
    language:EN
    host name:
    load balancing:n
    system number:01
    router sting :optionla
    trace lavel:0
    password for CSMREG user:********
    Its showing this error:
    ERROR: RFC error during logon: 105 DESTINATION_NOT_EXIST
    How to solve this?
    Do I have to do any RFC configuration in the Central monitoring system(as I want to monitor a non-SAP system)?
    urgently required.
    Any help will be appreaciated.
    Regards
    Manisha

    Hi Manisha,
    Yes you will have to create a RFC and a suitable RFC user in the Central Monitoring System (CEN) via txn RZ21 to monitor these remote systems.
    Please follow this link:
    http://help.sap.com/saphelp_nw04/helpdata/en/a8/adf7409b9d8531e10000000a1550b0/frameset.htm
    Please award suitably if helpful.
    Regards, Dibya

  • Registration of SAPCCM4x agent failed

    Hi!
    I would like to install a SAPCCM4x agent on the satellite systems host (Unix).
    If enter the data of CEN system, user and password the connection to CEN cannot be established and I get the following error:
    ERROR: RFC error: 104 RFC_ERROR_SYSTEM_FAILURE
    (see RFC trace file or SAP system log for more details)
    In file dev_rfc I could find:
    Connection to host <hostname>, service 3302 timed out
    Can some one help me to solve the problem?
    Thank you very much!
    regards
    Thom

    Hi Thom,
    sometimes you can ping from hostA to hostB , however you are unable to ping hostB to HostA.
    In this case, you need to check if both CEN and Satellite systems can ping each other.
    this can be done using the 'ping' command at the OS level.
    Check the page :
    http://en.wikipedia.org/wiki/Ping
    Also, I asked if you are able to use your SAP Logon pad to login into CEN using the same userid/password that you are using in the RFC destination.
    Regards,
    Siddhesh

  • Weblogic 81. portal server doesnot startup after the AM Agent installation

    Hi,
    I have a problem starting the weblogic server after I create the agent Authentication provider.
    I have cross checked the CLASSPATH values and the JAVA_OPTIONS values.. it is correct
    I get the following error
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authenticati:
    [java.lang.ClassNotFoundException: Can't load class: com.sun.identity.agents.weblogic.AmAuthProvider]
    at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:205)
    at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:262)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManagerDelegateIm)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManager)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelega)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManage)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDeleg)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:734)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:822)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
    at weblogic.Server.main(Server.java:32)
    Reason: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Auth:
    [java.lang.ClassNotFoundException: Can't load class: com.sun.identity.agents.weblogic.AmAuthProvider]
    Please help!!!
    -Karun

    Have you specify relative path or full of weblogic startup script? How's permission for user invoking startup script?
    Excerpt from the docs as below:
    Startup Script Location: Enter the full path to the startup script that is used to start your BEA WebLogic Server instance.
    Have you installed the agent on the admin server instead of the managed server? It should be managed server.
    Is this WebLogic clustered environment ? If it is a clustered setup; then you need to follow some specific steps to configure the managed servers. You are better off installing the agent on a managed server and copy the agent changes (CLASSPATH and JAVA_OPTIONS) to all the server instances. Some folks also prefer to copy these changes in commEnv.sh (easy way out) but we do not recommend this route since the server related JAVA_OPTIONS can be specific to each BEA server instance. Please note that the agent installer does not understand the template of admin server script. So, for a clustered environment :
    1. Remove the present agent, restore the admin server script.
    2. Install the agent on a managed server.
    3. If there are more than one managed servers, put the agent startup script related changes manually in each of the managed servers.
    4. Also note that you can start managed servers from console or command line. Depending on where you start managed servers, you will have to copy the agent changes to the respective files.
    If it is not a clustered environment; follow 1 and 2 only. Could try it out and let us know what are your findings? Jerry

Maybe you are looking for