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

Similar Messages

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

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 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

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 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.

Upgrade introscope agent

Hi All,
I have currently below settings. EM is at version 8.2.3.5 and Introscope agents at version 8.1.0.0. Now i want to upgrade the version of the introscope agent via SDM in solution manager. For this do i need to undeploy the previous version first? or whether it will work without undeploying.
And for configuration i think i just need to run the setup for Introscope agent to deploy the new application version in satellite system from SMD. Let me know if i am wrong here.
Thanks,
Rohan

Hello
To update the ISAGENT on Solution Manager you can deploy the new version over your actual version using the force deployment method in SDM (Software Deployment Manager).
When you click on the deploy tab in the SDM, click on the + button browse to the ISAGENT SMD SCA file and confirm to add it. Next you have to expand the lower pane (push the arrow button to expand/subtract the pane) and choose "deploy any version".
Don't know if text is exact match but you have to choose the option that will enable you to deploy any version of the SCA file.
When choosing that option the current version is disregarded and the new SCA file is deployed anyway. You can even downgrade a Java component this way. In this case you deploy a newer version of course.
Don't forget to follow the post steps described in the SAP notes / Installation guide (Running upgrade in diagnostics setup for example).
To update individual Introscope Agents of your managed SAP systems you will have to redeploy those through the Introscope Agent setup.
Kind regards
Tom

Problem Remote Deploy Wily Introscope Agent

Hi,
I installed Wily Introscope EM and the Diagnostic Agent on Solution Manager (EhP1).
Now, if I understand it, I can do a remote deploy of Introscope Agent, for example on Enterprise Portal.
How can I do?
Best Regards.
Diego.

Hi Diego,
Do you also install an SMD agent on the portal system which one you want to managed via RCA? Also you need to run the Setup Wizard for Managed Systems for your portal.
Please check SAP Note 1365123 - Installation of Diagnostics Agents. In this note you will find an attachment Agent_Installation_Strategy.ppt - describe the installation strategy of SMD agents and all agent rules which you need to follow.
So one part is to get RCA running:
1. Install a SMD agent per managed host.
2. Define the technical system in SMSY Normal you have an SLD in your landscape and connect the Solution Manager to it or use the SLD from Solution Manager. After you define the technical system in SMSY or via SOLMAN_SETUP ->Managed System Configuration you go to Diagnostics Setup.
3. You access this via Diagnostics work center or direct link http://solman_fqdn:<port>/smd
4. Next go to Managed System -> Setup Wizard -> Select your to managed system <SID> - > check that system is Diagnostics Relevant (if not click on the managed products and set the relevant product for diagnostic u2013 also verify the Landscape setting light are green u2013 this means the technical system is well defined in SMSY)
5. Click Setup <SID> Button -> on next screen you need to fill out all Java / Abap connection parameters (for the setup of Java systems you need a userid with j2ee admin rights)
6. Please set the SMD agent in the right table u2013> Click on details arrow and then select the managed systemu2019s SMD agent and click on the set button. The SMD agent will now reboot wait until the agent is back -> Click on the Refresh button to see the status.
7. Click Next and on the next screen you get a Summary of all setup steps
8. Click on Setup. After the setup finished (all steps are green)
9. Click on quit.
Before your can deploy the IS agent from the Solution Manager you need to deploy the IS agent files via SDM to the Solution Manager. You can download the deployable IS agent from SAP Service Market Place:
Support Packages and Patches -> Entry by Application Group -> SAP Technology Components -> SAP SOLUTION MANAGER -> SAP SOLUTION MANAGER 7.0 EHP 1 -> Entry by Components -> Agents for managed systems -> select your version for your IS EM and download the deployable agent via SolMan Diagnostics (File name like ISAGENTSMD801_01-10007435.SCA)
Now you can start with the setup of the Introscope Agent (on the left menu bar under application selection).
On the selection screen select first your IS Enterprise Manager then the IS Agent settings the relevant system.
In the table select the J2EE node for which want you setup the agent (this need to be done for each Server node u2013 the IS agent runs inside of the J2EE node per server)
Then click on Setup Introscope Agent u2026 Button u2013> select the Autoprobe Directives and click the Apply button. If every steps doen you need to reboot your managed JAVA system.
Now you are ready to use the RCA tools and also see data in the IS Enterprise Manager.

Introscope agent -problem in ISAgent settings retrieval

Hi ,
I have installed a SMD agent for a pure and simple Java stack system.
The SMD agent installation and setup wizard ran fine with no problems.
How ever while trying to setup the introscope agent i have errors.
Diagnostics setup -Managed system -Introscope agent
The error is as following
"Operation failed - X01 - 123456789 - com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied: Please make sure the <user> and <password> parameters are correct.; nested exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]"
The SMD agent is up and running and im not clear which user id the above message is telling about.
The user ID and password of administrator which we give during running the setup wizard is correct.
Also i have installed the SMD agent with connection type "Lookup HTTP connection via message server"
So i understand that the above user id could be the user which the agent is using to connect to the JVM...but im not sure which is that user id or if im right or wrong .
Kindly advise if anyone has an idea how to resolve thsi problem.
Regards,
Sunanda

Hi Sunanda,
I had a similar problem with the ISAgent.
I did a manual installation as described in the Installation guide Wily Introscope, chapter 4.
After that, it worked.
Best Regards,
Jan
PS: Check if note 1149214 applies before restarting the system /if restarting the system fails.

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

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

Installation audit vault agent with RAC configuration

Hi at all,
I have a question about the installation of the agent on the RAC configuration. Where must I install the Audit vault agent, on all RAC nodes or is there a properly configuration?
Thanks
Vincenzo

By default when you install the agent on any single node the installation recognizes that it is a cluster and presents you with a list of available nodes from which to select.
With a RAC cluster you have one database and multiple instances. All instances will write to one, and only one AUD$ and FGA_LOG$ table so if you are using database auditing one node will suffice. Which node that is though depends on knowing which node is up at any one time so you could potentially choose a node that is dropped from the cluster or is down for patching and maintenance while the cluster is still running. With respect to REDO collection each node has its own redo thread so you definitely need to be collecting from every node.
Audit Vault has not been out long enough that I can tell you from experience what might be defined as "best practice" and often what we really need to study is "worst practice" to know what not to do. But in the case of RAC my instinct would be to first determine the collection type(s) and then decide. Erring on the side of collecting from all nodes makes a lot of sense.

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

Installation of Introscope Agent

Similar Messages

Maybe you are looking for