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.

Similar Messages

SAPOSCOL does not start with SAP Host Agent processes

Dear all,
on one of our servers the SAPOSCOL process is not running. The latest SAP Host Agent is in place - automatic updating has been finished sucessfully but after the restart of the host agent processes SAPOSCOL returned the following entry in log dev_saphostexec:
[Thr 01] Fri Nov 25 11:23:30 2011
[Thr 01] *** WARNING => /usr/sap/hostctrl/exe/saposcol -l -w60 pf=/usr/sap/hostctrl/exe/host_profile exit with status 4 [OsCollectorW 171]
It is only a warning but as a consequence no SAPOSCOL process is running.
Any ideas? Your quick response will be very much appreciated
Regards,
Mattias Umlauf

Hi
if
/usr/sap/hostctrl/exe/saposcol -status
shows no PID but shared memory attached either cleanipc
or try to force start saposcol
/usr/sap/hostctrl/exe/saposcol -f
Regards
Stanislav

Metric: SAP Host Agent Availability doubt

Hello folks!
I have a problem in technical monitoring from Solution Manager, and i would be happy, if someone could help me with this.
1 - SAP Solution Manager is trying to ping a IP that doesnt exists
2 - In the screenshot, the line is: "Ping to listener: xxx.xxx.xxx.xxx:port not successful".
Let's call the host of my managed object as "$HOST_NAME", and the IP as "$HOST_IP".
1 - The IP of $HOST_NAME is one, and the IP xxx.xxx.xxx.xxx that SolMan is trying to ping, is another, the ip doesnt even exists, because i can't reach him from anywhere. Is it not wrong? I think the "Listener" should be the $HOST_IP, not another...
2 - The correction for this problem, would be the adjustment of the "Listener" to the $HOST_IP? How could i do this?
Thanks already

Hi,
Host agent runs on physical machine.
Can you goto agent admin and find host name and IP from there.
Divyanshu

SAP Host and Diagnostic agent

Dear Experts,
We are running ECC 6.6 and Portal on Net Weaver 7.31 ,and have Soution Manager 7.1,As I have read many places that host agent get installed automatically with Net Weaver Installation.
In My Portal server I am able to see hostctrl folder and SAPHostControl service related to host agent, but there is no such service or folder in R/3 server.So do I need to install Host Agent separately for R/3 system.
One more Question do I need to have Host agent mandatory for Diagnostic agent installation(SMD)?
Thanks
Chander

Hello
In our R/3 system Kernel release is 720 ,and we doesn't have SAP host agent,But for Java with same kernel release we have SAP host agent.
If this is an ECC system upgraded from an old R/3 system then you might have ignored to install SAP Host Agent as I have seen the upgrade guides suggesting to install SAP Host Agent starting from EHP5.
When we installed Net Weaver 7.31 for java portal SAP Diagnostic agent installed automatically and with that SAP host agent also came.
Read my previous reply. All new installation bring in SAP Host Agent.
My main purpose to install Diagnostic agent for R/3 for E2E analysis ,so i want more clarity regarding SAP host and diagnostic agent.
R/3 is on Net Weaver 7.31( ECC 6.6), So which version of diagnostic and host agent need to be installed and are they installed separately .
Follow the SAP note I have given above. The latest version is SAP HOST AGENT 7.20
Here is the SAP note once again 1031096 - Installing Package SAPHOSTAGENT
Regards
RB

Cannot install Host Agent

Hi All,
I am facing a problem for SAP host agent. I have download the newest version of SAPHOSTAGENT. Decompression and run installation command.
<Path>saphostexec -install
Install service
Check Installation Path ...ok
Copy Executable ...
Service SAPHostExec is Stopped
Copying...ok
Generate Profile ...ok
Check Upgrade ...ok
Install windows service ...Service SAPHostExec registered!
ok
Check for saphostcontrol ...
Please enter password for user .\sapadm: ********
Register sapstartsrv: "C:\Program Files\SAP\hostctrl\exe\sapstartsrv.exe" -r -soap -p "C:\Program Files\SAP\hostctrl\exe\host_profile" -s SAP -n 99 -U .\sapadm -q -P ********
[ERROR] saphostcontrol registration failed wit exitcode -1
[ERROR] Failed
I have tried different version of SAPHOSTAGENT but still has the same error.
Please suggest.
Regards

Hi,
Please follow SCN links SAP Host Agent - Frequently Asked Questions
Downloading and Installing Package SAPHOSTAGENT - SAP NetWeaver Landscape Virtualization Management, Standard - SAP Libr…
Regards,
Gaurav

Host agent check errors for host

Dear All,
We have recently installed PI 7.4 system. While configuring in SolMan 7.1. i am facing issue that "Host agent check errors for host "
Managed System Configuration - >Assign Diagnostics Agents.
Kindly help me out..
Regards
Jay

Hi Jay,
Please confirm ownership & permission for directory /usr/sap/hostctrl .For ref please follow SCN link Problem with connecting SAP Host Agent
After that retry the phase.
Regards,
Gaurav

Wily host agent issue

Hi Experts,
I have an ongoing issue regarding setting up managed systems in Solution Manager.
My solman system is SP21 and everytime I go to setup a system via Managed System Configuration --> Diagnostics Configuration. I get the same error no matter what the managed system is. The latest version of the ISAgent has been installed via SDM and LMService is up to date. I have stopped and restarted the agents in order to try resolve this but this did not work. I have searched through the forum but have yet to come up with a solution, could this be a bug with SP21?
The error below is what I see during this step:
" Wilyhost Agent configuration finished without errors, but on Enterprise Manager (chsmpci.cbapps.int:6001) no Wilyhost Agent was detected from host cbppici. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
Step Wilyhost Agent Details
Created destination PPI|cb102p29_PPI_11
Created destination SapHostAgent_cb102p29
Created destination SapStartSrv_cb102p29_PPI_11
Created action PPI - PPI AbapSystem
Created action PPI|cb102p29_PPI_11 - PPI|cb102p29_PPI_11 AbapInstance
Created action SAP OsCol - SapHostAgent_cb102p29
Created action PPI|cb102p29_PPI_11 - SapStartSrv_cb102p29_PPI_11
Created 4 action(s).
0 Wilyhost Agent(s) from host cbppici are connected to the EM.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (chsmpci.cbapps.int:6001) no Wilyhost Agent was detected from host cbppici. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level. "
Could you help me on this issue as it is holding the project up.
Thanks
Stephen

Hi Pascal,
I have users Admin and Guest as default users in file users.xml and in the file domain.xml I have the following information:
        <grant user="Admin" permission="read"/>
        <grant user="Admin" permission="run_tracer"/>
        <grant user="Admin" permission="live_agent_control"/>
        <grant user="Admin" permission="historical_agent_control"/>
        <grant user="Guest" permission="read"/>
        <grant user="sapsupport" permission="full"/>
Regards
Stephen

Is Multiple SDM agents in one Host supported?

Hi Experts
I know about the rule of one SDM agent per host. Is it possible to install 2 different SDM agents in one host...
Does SAP supports this? Is there any documentation supporting this.
For Example...
I want my Development systems connected to my both Solution Managers ( Production and Development ). I want to have the possibility to start monitoring from either one of them.
Or, I want an SDM agent pointing to an external service provider to monitor my landscape throught their SolMan, And I want to keep one SDM agent configured to my own Solman Server.
Again
Should/Can I install an additional SDM agent in every system?
Do you have a particular documentation that support this scenario?
Regards and thanks
Henry Lopez

Hi,
first, if you mean SMD Agent, then yes, the diagnostics concept from SAP needs only one diagnostics agent per host.
Big negativ impact on this SAP concept is, that if you implement monitoring with SAP Solution Manager, you have a single point of failure = the SAP Solution Manager itself,
In former days, there was CCMS and primary / secondary target servers possible.
Now with SMD you may have a agent with instance 98 (older versions had 97 as default) which "reacts" to the prod Sol Man and an additional agent with a diffent number which "reacts" to the non-prod Sol Man and so on.
This "single point of failure" in the E2E / SMD concept is for me not acceptable.
Everytime there is a Sol Man downtime, you and your complete "monitoring" will be BLIND.
Sometimes the Java Agent turns from Green to Yellow, then the blindness is for all compontents on that host.
If any alerts (MAI) etc come up, the SolMan down, you will not know / auto-react it until SolMan downtime is over or you restarted the Yellow agent.
That's the reason and solution why the making a SPOF to a "halt/two point of failure" might be better on larger landscapes.
Raymond

Wilyhost Agent(s) from host hostname are connected to the EM

Hi All!
I tried complte setup managed system/. And received following message:
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (host:port) no Wilyhost Agent was detected from host SSM. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
in jvm_smdagent.out:
11/12/09 03:40:40 PM GMT+03:00 [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
11/12/09 03:40:40 PM GMT+03:00 [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
Error Message is :com.sap.guid.GUIDGeneratorFactory
11/12/09 03:40:41 PM GMT+03:00 [INFO] [IntroscopeAgent] Started Error Reporting service
11/12/09 03:40:42 PM GMT+03:00 [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at host:port,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "HOST", Process = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
Error Message is :com.sap.guid.GUIDGeneratorFactory
Could anybody help me resolve it?
Thanks for your advance,
Alexander

Hi,
we also have the same error...
LM-SERVICE 7.01 SP5 (1000.7.01.5.2.20091211060559)
LM-TOOLS 7.01 SP4 (1000.7.01.4.2.20090723091137)
My problem is that I don't get any data of our KWP ABAPsystem in Wily. The Agent is running and is well connected (The lights in agent administration are all green). Also in the logs I don't see any probs.
I have restarted the agent 1000 times..., reseted the server name and ran the agent setup again... I also registered it via
./smdsetup.sh sldconf hostname:"solman" port:"59500" user:"username" pwd:"xxxxx"
./smdsetup.sh managingconf hostname:"sapms://solman" port:"8196" user:"SMD_ADMIN" pwd:"xxxxx"
Do u have any ideas???
Regards
Johannes

Introscope Host Agent for ABAP only instance, fails with java.lang.NullPoin

Hello,
I'm trying to configure the Introscope Host Agent Adapter for ABAP 7.02 instance.
Solman Version is 7.1 ST 4, BASIS SP9.
I did created the Trust relationship between DAA and hostctrl and
also the same setup working find for Java Instance or ABAP+java Instance,
I'm not sure whether IS Adapter can be installed for ABAP only Instance.
Log file from Solman:
java.lang.NullPointerException
at com.sap.smd.server.manager.SMDPluginProperties.setProperty(SMDPluginProperties.java:119)
at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.setJCoUserAndPwd(AgentConfigWriter.java:1085)
at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.setLogonData(AgentConfigWriter.java:1075)
at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.createJcoDestinationVO(AgentConfigWriter.java:677)
at com.sap.sup.admin.wily.hostagent.config.AgentConfigWriter.prepareSapAgentConfiguration(AgentConfigWriter.java:284)
at com.sap.sup.admin.wily.hostagent.Setup.setupAgentConfiguration(Setup.java:272)
Thanks
Srikanth M

Hi
I am sure, it is logically incorrect, how you deploy byte code agent in abap only instance
Introscope Bytecode Agent runs on managed systems based on J2EE engines to report data to the Introscope Enterprise Manager, so it has to be setup only for Java Stacks.
Please check with the wily config guide again.
I am watching this thread for further view from others.
Thanks,
Jansi

SAP Conversion Agent for PI 7.1 EHP 1 and Windows 2008 Support

Hello
I have read that some people were able to run SAP Conversion Agent on a PI 7.1 EHP1 Installation on Windows 2008 Sever. But in the Product Availability Matrix there is no support for 2008 yet.
In the SAP Library (http://help.sap.com/saphelp_nwpi71/helpdata/en/43/fc39c16bfb025ee10000000a1553f7/frameset.htm) under the release notes for SAP Conversion Agent there is still version 8.5, but when I install the actual Support Package I have Conversion Agent 8.6 running and according to information on the informatica.com site this version is running under 2008!
Has anybody clear and actual information about which OS the newest SAP Conversion Agent for PI 7.1 EHP1 supports? Or has anyone experiance on Conversion Agent and Windows 2008 Server?
Thanks
Christoph

Hi Mark
Thanks for your reply! Fact is that in the actual Package (SP06) the version of Conversion Agent Engine supplied is not 8.5.5 as in the SAP Note mentioned, it is version 8.6.0:
C:\Documents and Settings\pi1adm>CM_console -v
Engine-Version: 8.6.0(Build:30)
Engine-Syntaxversion:4.00.10
I will oben a ticket for that ...
Regards
Christoph

Solution manager configuration diagnostic host agent

Hi experts,
I am configuring the solution manager 7.1 SP9, I have one doubt whether our systems contains diagnostic host agent or not.
in sapmmc at the time of restarting the sap services i found that DAA is there.So i got this doubt. Please clarify what is diagnostic host agent and SAPHost agent and also please provide any material for solution manager configuration. I am not getting clarity from google.
Thanks&Regards,
Patan Thavaheer.

Hi,
I executed the given command successfully in daaadm user.In command prompt it is showing that "task completed with status success".But in solution manager it is not getting visible. I checked in log file SMDsystem.0.log , i found exception in the log.
find the exception
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       Detect possible changes in runtime.properties, reload data and restart the agent connection.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       SLD configuration not found to register the agent, SLD Agent Registration is skipped.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       Reconnection in progress...
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       [SMDConnector.reset] in progress ...
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       [SMDConnector.reset] invalid the agent handle com.sap.smd.agent.AgentHandle@1db9b30c.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       Reading JStartup environment...
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       'SAPLOCALHOST' found, The value 'MIGDev' will be used to determine the Agent name.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       InetAddress Resolving for 'MIGDev' - FQN: migdev.milltec.com SQN: MIGDev IP: 192.168.140.45
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       InetAddress Resolving for localhost - FQN: migdev.milltec.com SQN: MIGDev IP: 192.168.140.45
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       [SMDConnector.reset] Done.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Sep 16, 2014 10:56:45 AM [Thread[Connector,5,main]                     ] Error      Failed to connect to SMD server - user: basisadm
Sep 16, 2014 10:56:45 AM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://migsolman.milltec.com:8001 failed - error counter: 19 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Sep 16, 2014 10:57:51 AM [Thread[Connector,5,main]                     ] Error      Failed to connect to SMD server - user: basisadm
Sep 16, 2014 10:57:51 AM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://migsolman.milltec.com:8001 failed - error counter: 20 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Sep 16, 2014 10:58:56 AM [Thread[Connector,5,main]                     ] Error      Failed to connect to SMD server - user: basisadm
Sep 16, 2014 10:58:56 AM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://migsolman.milltec.com:8001 failed - error counter: 21 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Regards,
Patan Thavaheer.

How to download SAP Conversion Agent 7.1 by Informatica

Hi Gurus,
I tried to download SAP Conversion Agent 7.1 by Informatica from following location
Sap Software Download Center---->Browse Our Download Catalog----->Installations and Upgrades----->Adapters----->Informatica----->SAP CA For SAP Netweaver 7.1
but its showing No data available. Can anybody help me how to get this conversion agent.

Well, I see it like this and everything work for me:
Are you logged in with your S-user account? Also I think you have to be authorized for downloading the software. Can you check under your profile, if you have some authorizations?

Wily host agent

Hello,
Could you please advice how is it possible to install and potentionaly configure host agent for Wily EM without using remote installation via SMD? I can see in Wily inst. guide only notice to remove EPAgent and activate hostAgent via SMD wizard (since SMD SP13). At the moment I can see only data from Introscope java agent and no data from host-level agent like Garbage collection frequency and duration etc...
Thx a lot in advance

Dear Julius,
Yes, both Wily IS Agent have to be deployed using SMD.
1. You install the ISAgent (ISAGENTSMD8SP01_00-10007435.SCA for example) in Solution Manager ONLY.
    You do not have to install it on any managed systems !
2. Using SOLMAN_SETUP procedure guided :
    2.1. Initial Configuration is done ...
    2.2. Basic Configuration is done ...
    2.3. Start the Managed System Configuration
    In 3rd phase of the SOLMAN_SETUP guided procedure, you have "Wily Introscope Configuration" steps.
    Here, you have the activity "Configure Wily Introscope Agent".
When we talk about Wily ISAgent, it includes 2 agents :
1. Wily Introscope Java Agent which monitors all applictions on JAVA level.
2. Wily Host-Level Introscope Agent (ABAP)
Hope it helps ?
Best regards
Pascal Cuennet
Why do we have 2 Wily IS Agent :
1.

Configure com.sap.smd.agent.application.portalactivityreport

Hi,
I am trying to use the solution manager diagnostics and the portal activity reports to gather some information about our portal utilization. I have my portal system connected using SMD agent, I am able to run other monitoring application within SMD but when I try to execute the portal activity report I get the following error:
Portal Activity Reporting - Form
Could invoke portal activity report web service properly, please check the configuration
On the configuration of the application there are not parameters to configure, and the agent application seems to be running and deployed:
com.sap.smd.agent.application.portalactivityreport 7.0010.20061020144811.0000 7.0010.20061020144811.0000 Running
If somebody has implemented this functionality or have had the same problem let me know with any idea of pointer.
Thanks in advance for the help,
Zareh Vazquez

Hello,
You have to follow the SAP Note 893101 to set the security zone to Everyone on the Portal Activity Report web service on the portal.
And you need to restart the service com.sap.portal.activity.report.core.
Best regards,
Paula

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

Similar Messages

Maybe you are looking for