Could you please let me know how and where to start and complete this installation. I joined in this company newly and in previous company also i did not do any install on SAP side I need to install wily introscope on a separate system so do I need to install the DAA on the wily Introscope system?.. Do let me know that the procedure is.. Skip to Content. Former Member. April 19, 4 minute read. Diagnostics Agent : the Diagnostics Agent must be configured in Solution Manager for Root Cause Analysis function, It allows to perform a connection between SAP Solution Manager as the managing system and the managed system s and then to gather information from the managed systems and reports them to the Solution Manager system.
You can also install it as a standalone engine, for example if you want a non-SAP system to be managed by SAP Solution Manager Diagnostics To configure the agent in Solution Manager navigate to manage system configuration — configure system — step 3 assign diagnostics agents Install Diagnostics Agent Please read this note before installing the Diagnostics Agent, and make sure to use the latest available installer and corresponding setup guide: Note — Diagnostics Agent — Installer Versions Run sapinst from the installation directory The host name will show automatic SAP recommended that you choose Local Domain local installation for the diagnostics agent users Insert password Insert password Instance number Additional Information The Instance Number is a technical identifier for controlling internal processes such as assigned memory.
Test the registration The Adaptive Computing Controller provides a single point of control that allows your SAP software system administrator to visualize, monitor, and manage data center tasks for deployed SAP solutions.
Alert Moderator. Alerting is not available for unauthorized users. Assigned Tags. Similar Blog Posts. Related Questions. You must be Logged on to comment or reply to a post.
Very useful document!! Like 1 Share. Right click and copy the link to share this comment. V S Srirangarajan. Thank You. From Xenapp 7. The timeout can be increased by setting the following:. From About Citrix Receiver for Chrome 1. Create any missing registry keys. This applies to both virtual desktops and Remote Desktop Session Hosts. Citrix Policies also control graphics performance. This is similar to RDP drive mapping. When you reconnect, the client drives will be mapped as drive letters starts with V: and goes backwards.
By default, Non-Windows clients cannot map printers due to a missing print driver on the VDA machine. Unfortunately this does not work for Remote Desktop Session Host. The Blog Post also has links to additional KB articles on antivirus. These registries will allow a delay on the startup procedure of OSCE until the system has launched successfully.
This avoids deadlock situations during login. Citrix session hosts experience slow response and performance more noticeable while users try to log in to the servers. At some point the performance of the servers is affected, resulting in issues with users logging on and requiring the server to be restarted.
This issue is more noticeable on mid to large session host infrastructures. Trend Micro has provided a registry fix for this type of issue.
Create the following registry on all the affected servers. Ignore the XenApp 6 content and instead focus on the Windows content. Do not enable NtfsDisable8dot3NameCreation. Microsoft has compiled a list of links to various optimization guides. Usually such customizations include the following. With that said the certain practices are quite debatable and vary between actual real-world deployments.
Exact choices whether to disable this or that particular component depend on customer requirements and VDI usage patterns. Some customers rely heavily on particular UI functions and other can relatively easily trade them off for the sake of performance or standardization thus enhance supportability and potentially security. Though there are a number of such papers and even tools published either by the community or third parties. This Wiki page is aimed to serve as a consolidated and comprehensive list of such resources.
If this session host will be a master image in a Machine Creation Services or Provisioning Services catalog, after the master is fully prepared including applications , do the following:.
Session hosts commonly have DHCP reservations. Shut down the master image. You can now use Studio or Provisioning Services to create a catalog of linked clones. Wildcards are not supported. To blacklist multiple apps e. I recently had to blacklist Internet Explorer to prevent lockup issues when switching back to physical.
Having an issue after cloning a Win Xenapp7. We use Arcronis to clone the server. Symptom Editor finished execution half way of a replay without any error information. Solution Open EemEditor. Type it character by character again. Execute the script step by step to identify the EEM message which causes the issue by addressing an unknown UI element. Execute the script again till the point where the script would during next action.
Use the mouse to click on the UI element which should be addressed during a correct execution. The red square helps you to navigate in the UI components. For example Proceed with script execution to exit the script. The selection of the correct UI element with the mouse has created an availability check for this element. We do not need this check but it shows the component ID of the important UI element that is not pressed or activated during the exceptional script runs.
Compare the component ID from check with the component ID mentioned in the next message. In some cases the IDs differ. Try to execute the script with a corrected component ID in the message. Activate "hardcopy" and "Component Trace" and hit "Apply". Perform another replay of the script. During the replay the editor now captures screen-shots for every message and in addition a dump of the UI element hierarchy.
You can review this by clicking at single messages in the replay result. Reason The client plugin EEM recorder has a defect. Reason The web service in Java has been enhanced to provide a filter option when searching for robot candidates.
When deploying or uploading a script that cannot be started on the robot because of missing properties or an error the deployment throws the exception. Error Message after trying to deploy scripts to robots.
XML Parser has thrown exception while parsing input Resources cannot be uploaded. SoapFaultCode:5 Reader is not positioned on start element. Probably incorrect usage of stream parsing methods. Select tab Configurations in the lower pane. Select the logical port SMD and click Edit.
The context menu in the monitoring UI entries overview. The context menu in the monitoring UI can contain the following entries: Go to E2E Trace Analysis This entry is only selectable if system data or traces have been collected and if user has the authority to jump to the E2E Trace. This entry is only selectable if the system data is not available. It provides the possibility to collect the logs from the robot and analyze it in the EEM editor. See also Run Script with Trace This entry is only possible for a selected script and robot combination.
It triggers immediately an additional execution with provided trace level. Set Temporary Configuration The selected script on the selected robot is executed for the configured time frame with the specified trace level. Filter to Opens a new tab with just the selected script. Assign Steps Filter Opens configuration menu to assign a filter on step level. Collect Trace Triggers a trace collection immediately for the selected script execution.
The parameter "Expire in seconds" of temporary configuration should have a value higher than 60 seconds default 2. Check the log of the extractor. The Monitoring UI does not display any script executions. There could be several reasons: The user for sending the notifications is locked The user for sending the notifications is stored on each robot. If the password is changed in user master record SU01 and not in the setup application the robots use still the old password. But even if the password is changed in the the setup application it might happen that there is a small overlap when robots still using the old password until they receive the new password.
The user can be unlocked in SU The name of the user is specified with parameter wsnotify. Accepting notifications is disabled For 7. Robots are not available If robots are not reachable they are usually displayed at disconnected and they cannot send any notification. URL for sending the notification has been changed or is not correct The URL including protocol, host and port has been changed or is not correct.
This might happen if the URL is using a host name and port for the message server that is not reachable from the robot location. The URL can be adapted by adjusting the parameter wsnotify.
Notification is using https but iaik files are not installed. Exception: Could not create https handler:java. ClassNotFoundException iaik. Monitoring UI does not start.
There might be several reasons why the monitoring UI does not start. Missing authorization. The user does not have the correct role and authorization for this WS is missing. To verify this an authorization trace for the user in ST01 can be recorded when calling the monitoring UI.
The following screen shot shows the required settings when all authentication types should be used:. There are multiple possible reasons for this: There was some kind of timeout Just try again When executing a script the following exception is thrown: sun.
You are running a https script which aborts with "javax. UnsupportedOperationException" Solution Check if the script has a valid truststore or if the password for the global password is set. You are running a script which aborts with "java. ConnectException: Connection timed out: connect" Solution Check if a proxy is required to reach the url. When executing a https script you get the exception"java. Restart the agent.
Procedure You can change temporally the settings of the service to interact with desktop. Start services. Open tab 'Log On' and select 'Local System Account' and 'Allow service to interact with desktop' as shown on the screen shot below: Wait until the script will be executed and display the result. After the analysis you should change the setting back to its original value.
Solution To get the script running successfully you have the following options: Configure different users per robot.
Use for each script execution another user. This can be reached by setting the properties sapgui. This will prevent the pop-up for this user and as the advantage that the password will not expire. Allow multiple logons with same user in the backend systems. Synchronize executions in a way that a robot always logs out before another one tries a logon. See also Script Synchronization and Serialization.
Sending a notification fails with the following error message. Error java. Workaround Revert to http. EEM Robot does not show sapgui as supported protocol. There must be a message like "Scripting is installed". Check that property trace. If the property is set as in the screen shot below all executions are triggered with a trace and are therefore not reporting relevant.
Which roles are required when using the monitoring tools in Solution Manager? How much network traffic is generated by EEM robots? The network traffic depends on the type and number of scripts deployed to the robot and the frequency of script execution: In general, every script execution triggers a result notification to SAP Solution Manager.
Data volume for this is in the range of 1kB. HTTP scripts may be very sensitive to modifications. In particular, the following two aspects are relevant: Compression: Double check that the responses are compressed by looking at the response header content-encoding Static resources: Make sure that static resources images, javascript, style sheets are handled in the same way as for an end user in the browser.
Typically these resources are cached in the browser and thus should be deactivated in the EEM script.
0コメント