Introscope agent registration

Dear All,
after SMD agent installation (SolMan 7, EHP1 SP3) the SMD service start without problems. Unfortunately the agent cannot be registered properly, in SMD Agent Candidates I can see it but it stays in status 'Waiting for agent registration'and sometimes there is a 'handshake denied' error.
In Diagnostics Setup -> Managed Systems -> Introscope Agent I can see the agent but withthe status: "Failed to connect to server: <name> - Please make sure SMD Agent is up and running".
Any idea what can be the reason? LM* has the latest version and SP.
Best regards,
Jakub

Did you ever get this resolved? I've looked for Notes but only found your message.

Similar Messages

I can not make a "Automated Installation of the Introscope Agent" (Managed System Configuration, p.7)

I can not make a "Byte Code Adapter Installation"
When I open meets both paragraphs in step Managed System Configuration is somewhat obscure situations that do not allow the automatic configuration Introscope agent and Introscope Manager
Please help to resolve a number of questions that might help me complete the setup :
1. Why has the status of Enterprise Manager : <No Enterprise Manager configured> ( see picture)
I set up Enterprise Manager in accordance with the installation instructions and complied with all the setting items . Since without any configuration can be associated with the appearance of this status ?
2 . Why Server Node is empty detail settings ?
JDK Location:
Enterprise Manager Host:
Enterprise Manager Port:
Introscope Agent Name:
Introscope Agent Profile:
Autoprobe Directives:
Wily Version:
Introscope Agent Version:
Introscope Agent Log Location:
3 . What a mistake ($ MC: DIAG_WILY_MSG: 032 : L), which appears when I click configuration "Configure Introscope Agent Setup ...", and what it can be linked ? ( see picture )
And the last question , which is also linked to the process of automatic configuration and refers to a phrase from the instruction (Introscope Version 9
Installation Guide For SAP July 2012) points out "Automated Installation of the Introscope Agent via SMD"
there is such an item:
2 . Deploy ISAGENTJ5 *. SCA which is the Introscope Java Agent 9 with SDM to Solution Manager. You may need to deploy also ISAGENT *. SCA which is Introscope Java Agent 8.
However, nowhere does it say where exactly ( on what the absolute path ) I must perform unloading and then what to do with this discharge

The problem was resolved a small manipulation - on stage Basic Configuration,
point 3 "Configure CA Introscope"
I forgot to add to the list of CA Introscope Enterprise Managers link to my manager.
Thus it is necessary to take into account that the path should be correct (usually for linux - /usr/sap/ccms/apmintroscope) and the directory should be applied appropriate privileges.
Then in paragraph "Byte Code Adapter Installation" - there are all the necessary data, and it starts to work correctly

Introscope Agent Settings does not show J2EE Nodes

Hi all,
we are using Solultion Manager Diagnostics for 4 systems and everything is all right. We no installed a PI 7.10 system (for migration from PI 7.00) on the same server as the PI 7.00 system is. Agents are running and configuration is almost done, just the last step is missing or not working.
Now I want to configure SMD as well for the PI 7.10 system but I can see the J2EE Nodes on the SMD: Diagnostics Setup -> Managed Systems -> Introscope Agent
I am not sure how we did it the last times, because everything run smooth. One thing I remember, we could not see the second Java Server node of the PI 7.00 system in here as well.
Any Ideas how to do this?
BR Markus

Hi Jan,
Could you please tell me how you reloaded the solution in SMD,i mean could you tell me the steps to reload the solution in SMD.
Regards,
Krithi

Wily Introscope agent settings

Hi,
After the recent EHP1 upgrade on Solution manager,when we go to introscope agent configuration(Diagnostics Setup->Managed Systems->Introscope Agent)and select the system,it can't able to retrieve the current settings(i.e.,J2ee node).
{through we have select right Enterprise Manager}
We have also completed the post installation activities and successfully completed both the Initial and Basic configuration in solman_setup.
Any inputs??????
Thanks and Regards,
Edited by: Venkata Nooney on Jan 28, 2010 5:10 PM

Hi,
You will need Enterprise Manager 8.x for Solution manager EHP1 SP3 and up.
check this Note: 1273028- Introscope 8 release Notes for more details.
Check if the wily agents on the managed systems are connected to Enterprise manager using the webview
http://hostname.publix.com:8081/webview
Thanks,
Harini

Introscope Agent Settings

Hi folks,
Quick question this one probably.
Can anyone tell me where this screenshot was taken from in Solution Manager please? I've looked and looked and just cannot find it.
Hopefully someone may recognise it??
Thanks

Hi Paul,
Use this URL
http://<fqdn>:<port>/webdynpro/dispatcher/sap.com/tc~smd~navigation/StandaloneApp?APP_ID=ADMIN_INTROSCOPE_AGENT
goto -SOLMAN_SETUP ----- Managed System Configuration, select your managed system and in step 5 select action 'Configure Wily Introscope Agent'
Divyanshu

Managed System Configuration - Introscope Agent Configuration Failed

I get the following error message when carrying out step Byte Code Adapter Installation.
Introscope Agent Configuration - Remote Operation Failed.
The Wily agelet is running in 711 mode.
VM Parameters update for node 268734950 Remote Operation Failed.
Failed to update VM parameters:- com.sap.smdagent.vmmanager.VMManagerException: Failed to use JMX service
Any help will be appreciated.

Hi Tariq,
Please check the following KBA:
1918621 - Wily Bycode Agent install error - Failed to use JMX service
Thanks
Vikram

Installation of Introscope Agent

Hi!
I would like to install Introscope Agent.
Neither the manual installation nor the installation via Setup Introscope Agent was succesfull.
case a) automatic installation via SMD Wizard
The erros of installation with SMD Wizard (Setup Introscope Agent):
The landscape definition of selected system is empty.
Operation has been aborted
case b) manual installation (uncar the file ISAGENT71...SAR)
With the manual installation of Setup Introscope Agent ISAGENT71*.SAR I have the following problem:
No folder /usr/sap/ccms/wily/logs exist
If I add Java settings in Config Tool, restart the system and open the file d:\usr\sap\<SID>\<instance>\j2ee\cluster\instance.properties
I can not find any entries added before.
Thank you for any helpful information
regards
Thom

Again case a)
Please verify your definition, and also you need to have the previous Managed Setup Wizard run successfully.
case b) I would not recommend it.
Best Regards,
Frederic

Introscope Agent 8.2.2.0 error

Hello All,
We are running on Solution Manager SP23. When I am doing automated setup of Introscope Agent from solution manager I am getting the error. Please find more details below
Intorscope Agent 8.2.2.0 successfully deployed on managing system Solution Manger
SMD Agent 7.11 installed successfully and running fine on managed system
During Automated setup of Introscope Agent getting the below error
java.lang.NoSuchMethodError: com.sap.smd.agent.util.RunExec.setCharSet(Ljava/lang/String;)V
        at com.sap.smd.vm.J9Detector.isJ9(J9Detector.java:179)
        at com.sap.smd.wily.WilyHandlerService.performCommonSteps(WilyHandlerService.java:749)
        at com.sap.smd.wily.WilyHandlerService._configureISAgent(WilyHandlerService.java:659)
        at com.sap.smd.wily.WilyHandlerService.configureISAgent(WilyHandlerService.java:550)
        at com.sap.smd.wily.WilyHandlerServicep4_Skel.dispatch(WilyHandlerServicep4_Skel.java:144)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
        at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
        at java.lang.Thread.run(Thread.java:664)
Thanks in advance
Akram

Hi,
Is the wily agent already deployed on the satellite system ?
then your SMD agent is not registered properly/ smsy details for the system are not maintained properly.
sometimes SMD Agent is shown green in the agent viewer, even the pls check if the logs are visible for that agent in the logviewer.
More checks better to try and start the uninstallation of the smd agent via sapinst,, in the second step it will either show the managing host name or not..
pls re-check and deactivate the wily agent and re-setup from the wily tab.
pls check if after the setup the OS contains the said Introscope agent.profile in the specified path.
Regards,
Kaustubh.
Edited by: Kaustubh Krishna on Aug 23, 2010 2:29 PM

Introscope agent setup

I have setup the SMD agent on the satellite system and installed Wily EM. Now I want to setup the introscope agent on the satellite system. I go to Diagnostics setup-> Managed Systems-> Introscope Agent-> I select the Systems - I dont see any J2ee node and when I click on setup introscope agent I get the error "The landscape definition of the selected system is empty. operation has been aborted"
please suggest

Hi ,
I think, you have not provided the correct login details in Step 5.
After executing step 4, in step 5 it will ask for SLD login details from there it will retrieve the list of all the systems.
OR
One of the reasons may be, provided login details are correct & all the system (managed system) are already registered on the SMD of SolMan. So that is why you are not able to find any entries there.
In that case, click on the SMD View tab in the newly opened window. You will find all the registered system there.
I hope this will help you.
Thanks & Best Regards,
Pradeep Bishnoi
Edited by: Pradeep Bishnoi on Dec 3, 2008 5:30 AM

Introscope Agent Setup Error

Hi,
I am trying to setup Introscope Agent. I have installed it with Software Deployment Manager with no issues and setting up the agent using Diagnostic Agent Setup -> Managed System -> Introscope Agent.
I am getting this error. Please suggest on this.
ISAgent Setup on node:
Operation Faile
   Introscope Agent Configuration
Remote Operation Failed
   Introscope Agent Extraction
Remote Operation Succeeded
   Detailed Information
Operation skipped - Introscope Agent is already deployed at : filesystem
\SMDAgent\applications.config\com.sap.smd.agent.application.wily\BytecodeAgent\ISAGENT.8.2.2.0-2010-04-22
   Updating Introscope Agent Profiles
Remote Operation Succeeded
   ISAgent Profile Generation: IntroscopeAgent.profile ,
Remote Operation Succeeded
   Detailed Information
Operation Failed - <SID> - 254006950 - java.lang.NullPointerException
Regards,
Sandeep

Hello Sandeep-
Please do as follows
Install IS Agent (Wiley Introscope agent) in Solution Manger systems
Make sure wily is not running by looking for unix/windows processes with strings like u201Cintrou201D, u201Cemu201D, u201Cwilu201D. Uninstall wilyintroscope 7.1 by renaming the wily directory.
and deploy it with SDM it should work
Start SDM - 9> RemoteGui.sh
(IS Agent file is /sapcds/SMD2/ISAGENTSMD72_02-10005468.SCA)
then hit next and deploy after that you should be good to go.
George
Edited by: george rayi on Jul 20, 2010 10:14 PM

Introscope agent Error

Hi,
I have setup the rootcause analysis. Everything working fine..
.But when Go to Introscope agent
Diagnostics Setup -> Managed Systems -> INtroscope agent
receive an error message below
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   com.sap.tc.webdynpro.progmodel.context.ContextException: Node(WilyAdmin.EMS): must not bind an empty collection to a Node of cardinality 1..1 or 1..n
    at com.sap.tc.webdynpro.progmodel.context.Node.checkCollection(Node.java:515)
    at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:415)
    at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:345)
    at com.sap.tc.webdynpro.progmodel.context.Node.createMappedElementList(Node.java:498)
    at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:393)
    ... 172 more
reagars
Thirumal

Hi I got the same error,
could you tell me how you solved it.
Thx very much in advance.
Genrich

Invalid agent registration password when trying to secure agent

Hi Guys,
looking for some help with an issue im having trying to secure a 10.2.0.4 agent against 10g OEM.
A little background, the agent has been running succesfully against an OEM server which is now being decomissioned. I have editied the emd.properties file in order to point to the new server. I can start the agent ok, so far, so good. however when I try to run "emctl secure agent" I get:
Enter Agent Registration password :
Agent successfully stopped... Done.
Securing agent... Started.
Requesting an HTTPS Upload URL from the OMS... Done.
Requesting an Oracle Wallet and Agent Key from the OMS... Failed.
Failed to contact the OMS at the HTTP URL set in /ford/app/oracle/OracleHomes/agent10g/sysman/config/emd.properties
The password im entering works when connecting to dbsnmp in the database.
The sysman/log/secure.log file contains this:
[main] ERROR sec.GetWallet - caught Exception java.lang.Exception: szOmsSeed exception java.lang.Exception: szOmsSeed error: ERROR:203:Invalid agent registration password
[13-03-2009 09:52:48] USERINFO :: Failed.
[13-03-2009 09:52:48] USERINFO ::Failed to contact the OMS at the HTTP URL set in /ford/app/oracle/OracleHomes/agent10g/sysman/config/emd.properties
[13-03-2009 09:52:48] USERINFO ::The Agent has not been secured.
Any ideas?

thanks for your responses guys.
as yet I dont have access to the GC environment at this stage, as the new oem is hosted and managed by a separate team. (sorry, would've helped to mention that).
Re firewall, it should be ok I think, I can telnet succesfully to 4889 & 1159, 3872 is open the other way.

Wily Introscope Agent does not start

Hi,
i am installing Solution Manager Diagnostics on a Solution Manger 7.0 System. At the moment i am on the point to install the Wily Introscop Agent and i have following problem:
At first i tried the automatic setup and deployed the agent with JSPM and it seemed to work. I see "ISAGENT" on the System Information -> All Compontents over http://0/smd/admin and there is no log directory in the wily directory?
Does anybody has an idea whats wrong?
Best Regards,
Stefan
Edited by: Stefan on Feb 17, 2009 8:57 AM
Edited by: Stefan on Feb 17, 2009 9:31 AM

Hello Stephan,
1. Wily IS Agent (2 agents) is installed ONLY in SOLMAN system.
2. Then, with SOLMAN_SETUP Guided procedure, in third phase (Managed System Configuration),
    you deploy the Wily IS Agent to your managed system.
To summarize :
1. Install the ISAGENTxxx.SCA in SOLMAN only !
2. Start the SOLMAN_SETUP guided procedure
3. Phase I - Initial Configuration
    Phase II - Basis Configuration
    Phase III - Managed System Configuration.
In Phase III, there are 6 steps :
1.     Connect Managed system
2.     Check Prerequisites
3.     Manual Configuration
4.     Diagnostics Configuration
5.     Wily Introscope Configuration
6.     Create Logical Components
The Wily IS Agent (2 agents : IS Agent wich monitored JAVA instance and Wily Host-level Agent which a sub-process of the SMD Agent) is configured and STARTED here.
So, you cannot start / stop by any OS command the Wily IS Agent.
You start it from SMD.
Hope it help you.
Best regards
Pascal Cuennet

Problems in Introscope Agent Setting

Hi all,
we are configuring ROOT CAUSE ANALYSIS on Solution Manager 7 EHP1 to manage SAP BPC 5.1 system.
On managed system, we installed Introscope_Agent_dot_net_8.1.0.0
During the Introscope Agent Configuration in SolMan (transaction solman_setup --> Managed System Configuration --> Configure System --> Step 4 (Wily Introscope Configuration) --> in section "Introscope Agent Settings" field "System" there is no entry to select.
Can you help us?
Best regards,
Alessandro

Hi Alessandro,
do you mean that everything is working and setup OK? If you look in Agent Administration, do you see the agent(s) online there?
Did the managed system setup also complete successfully?
Normally when performing the managed system setup, you assosciate the registered agent, to the system you are configuring for diagnostics. Therefore it's important that all agents are up and running and connected.
On the managed system, check the logfile /usr/sap/ccms/wily/logs/IntroscopeAgent*****.log to see if it is running correctly. Also make sure the SMD agent on this host is OK: /usr/sap/SMD/J98/SMDAgent/log
/usr/sap/SMD/J98/script/smdadmin.sh
Check if the instance is up and running.
Edited by: J. Hellemons on Oct 27, 2009 4:31 PM

Introscope Agent Installation

Hi
I am installing the Wily Introscope Enterprise Manager and one Agent according to the "Introscope Version 7.0 Installation Guide for SAP"
I got stuck with the installation instruction Below .. Can any one help me how to do the below
Agent Name
You should assign a unique name to each SAP J2EE node that is Introscope-enabled. This so-called agent name is assigned by an additional Java VM option (referred to as <agentName> below). SAP suggests the following naming convention for the agent name:
<agentName>=SID_Product_Nodename
Where the placeholder mean the following:
Placeholder Explanation Example
<b>SID</b> SystemID EPP, EPQ, EPD
Product Identifier for product usage EP, XI, IPC
<b>Nodename</b> J2EE node name / directory server0
Note: It is not necessary to integrate the host name into the agent name, since the host name is assigned automatically to the agent.
Using a unique naming convention for all agent installations helps to group agents that belong to the same installation together.
Please help me
Thanks

Hi,
The instructions on Introscope Installation Guide suggests a naming convention for the agent name to identify this agent in Introscope.
The SID is the system identifier of the host, where you have installed the agent.
The Product depends on the product installed in this server (Enterprise Portal- EP, Process Integration - XI...).
For the Nodename, you have to specify on which node you have installed the agent. As introscope agent has to be installed on each nodes if you have several nodes on your engine.
So if you have a J2EE engine with two servers nodes with Enterprise Portal product, and you install an agent on each nodes, you will have two agents named EPP_EP_server0 and EPP_EP_server1.
Hope it helps,
Regards,
Paula

Introscope agent registration

Similar Messages

Maybe you are looking for