Ca wily introscope version 8 installation guide for sap

Edit the workstation. I had issues in getting the wily workstation started, but it did not just work after apply the work around mentioned in Workstation webstart section about. We had to change the j2se version to our client java version which 1. In some cases the launch of the Workstation fails silently, in other cases an exception is shown. As a general note I have updated the page to point out that all problems are resolved for Introscope 9.

Technical Operations. Browse pages. A t tachments 2 Page History. Jira links. SAP-specific log configuration Expand source. RollingFileAppender log4j. PatternLayout log4j. JMX debug logging. No labels. Former Member. I had issues getting the workstation to start for Wily When using Java 1. Clear the browser and Java caches on the client desktop.

Relaunch the Webstart Workstation and the problem should be resolved. Permalink Apr 21, In addition, for the following Java patch levels work-arounds are available: Java 7 Update 71 Java 1. Introscope 7. The setup guide provides accounts and passwords to access Introscope. If you have taken part in the rampup phase of this agreement you now have to upgrade to Introscope 7. Please contact Viktor.

Kalapos; viktor. Introscope 8. Note: Please read all release notes referenced in this note before upgrading to the latest release. I think I know why this didn't work. Theres a small typo with this path during java options. Thanks Shiva. Hey Shiva, I dont see this typo. Hi Toby, In Step. But later I checked all the paths and found this one was a little bit off thanks, Shiva.

Thanks Shiva, I fixed the problem. Missy Mazzola. Peter Han. Hello Toby, My customer update BI4. Thanks, Peter. Hi Peter, Sounds like a bug. Pradeep Kumar.

Dear Experts, I am facing the issue in wily configuration. Thanks and regards, Pradeep. Hi Toby, The hyperlinks in the Console is not working. Thanks Priya. Hi Toby, Thank you for the response. Also, please provide the profile you are using for this. I have uploaded the logs. Regards Priya. Hi Priya, The logs don't seem to indicate a problem. Vaibhav Muralidhar Gore.

Hi Toby, I know this blog doesn't talk about solution manager but could you please suggest on how to use solution manager to trigger alerts in case thread count value for tomcat crosses certain threshold Regards, Vaibhav.

Hi Vaibhav You should be able to create a system monitoring alert against the same Tomcat metrics and monitor it via the Solman Alert Inbox. Cheers Toby. Link Text. Open link in a new tab. No search term specified. The property wrapper. Increase the value of adapt wrapper. Adapt lax. In particular, you have to do this in two cases: o Enter the path of a separately installed 64 bit Java 5 VM for platforms on which by default only a 32 bit VM is provided:.

Set the Java VM parameter —Djava. Otherwise, the Enterprise Manager will need an X server, i. Set the Java VM parameter —Dswing. SAR in the home directory of the Enterprise Manager installation, e. SAR As a result you will find one or more.

The newly installed management modules only become active after the Enterprise Manager is re- started. For Windows installations the Enterprise Manager is typically automatically launched as Windows Service.

This means you will have to restart the Windows Service for the Enterprise Manager. Launch Enterprise Manager as Windows Service To launch the Enterprise Manager automatically at system restart, it is registered as Windows service On Unix you should run it as background process.

To check, perform the following: 1. Start the service if it is not yet running. Make sure to use the correct user account when launching the EM:. It is not necessary to explicitly use nohup for EMCtrl. Consider launching the Enterprise Manager automatically at system startup. Typically, you will have to hook it into one of the operating system specific init scripts. To set this up, you have to run a set of commands.

This should be done ideally as the user that the Wily Introscope Enterprise Manager will run under. If this user is not authorized for some commands, do run the commands as user that is authorized e. Check that the Enterprise Manager has started. Look for the following line in the logfile:. Look for lines similar to the following in the logfile:. PostOfficeHub] Server listening for incoming default socket connections on port Note: The recommended procedure to install and customize the Introscope Agent is to use the setup wizard provided in Solution Manager Diagnostics.

If you do not have Solution Manager Diagnostics available follow the manual procedure described in the second section of this chapter below. This section explains the steps to run the setup. Before you can run the Introscope agent setup, the setup wizard for the managed system must have been executed.

Your screen will look similar to the image below:. Check the Enterprise Manager Settings at the top of the screen. These are the connection parameters that will be used by the agent to connect to the Enterprise Manager. In the pane Introscope Agent Setttings, select the system that you want to instrument with the agent. This will display the current status of the agent setup. To initially setup or update the agents, click Setup Introscope Agent …. This will open the setup dialog as shown below.

Select the desired agent version by default only one available and choose the profile. Next, check the desired instrumentation areas, and, in the case of AIX, review the AIX settings to match your environment J9 or classic mode. Finally, hit Apply to perform the necessary changes in the agent configuration. Agent config files will be adapted, an Autoprobe connector will be created if necessary, and the Java VM parameters will be set as required for the managed system.

For Netweaver 7. Use the Configtool to set the parameters as described. If the setup was successful, restart the managed system at your convenience, e. After the restart, the agent will be active and should show up in the Introscope UIs.

Manual Installation of the Introscope Agent This section describes the manual configuration of Introscope bytecode agent for Java. These steps are only required if the automated installation, described in the previous. The instructions in the following section work on both Windows and Unix systems, but the examples show Windows convention backslashes in the paths. The following steps are required to install and configure the Introscope Agent to report information to the Enterprise Manager: 1.

Extract the Introscope Agent files 2. Introscope-enable the application code by setting Java VM parameters. SAR 2. This guide will refer to the IntroscopeAgent. Note that this file contains SAP-specific customization. Furthermore, depending on the monitored solution you need to choose different profiles:. SAP provides two agent profiles for different use cases. Note that the profile names have changed starting with the 7.

You will need to configure the host name or IP address and port of the machine where the Enterprise Manager resides.

To configure the Introscope Agent: 1. Open the agent profile, e. Locate the property, introscope. Enter either the host name or IP address of the machine where Enterprise Manager resides. The value should be the port on which the Enterprise Manager listens for Agent connections. Default setting is The instrumentation is split into several JAR packages. You can customize the list of packages by modifying the property introscope. By default, the following packages are active: introscope.

There are additional instrumentation sections which are not active by default. You can add entries to the property, separated by comma:. Do not activate for Java 1. By default, the Introscope agents write log files to the subdirectory logs of the agent installation e. On Unix systems, make sure that the monitored systems user sidadm have read and write access to this directory write permission for group sapsys.

As an alternative, you can change the properties introscope. File to some other directories where the monitored systems have write access.

There are two ways to specify the JVM:. Typically, you will only want to activate the agent on the SAP J2EE server nodes, not on dispatchers and state controllers.

Furthermore, note the difference between Unix and Windows in the class path: The entries are separated by ; on Windows, but by : on Unix. SAP suggests the following naming convention for the agent name. 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.

Open the file:. Note: Note that for NetWeaver 6. Click the disk button to save. Repeat steps 2 - 4 for each server node. Restart the SAP instance.