Managed_Systems

Managed System Configuration

More e documentation for 7.0 EhP1 can be found in the System Landscape Setup Guide

Select system for configuration Connect system (ABAP only)

If the system is an ABAP system, we will have to create RFC connections to the system. Java systems will be connected later on using Diagnostics agent and Introscope agent. You have to provide the user and the password for the administrator in Solution Manager as well as in the managed system. The following RFC destinations will be created:

The READ Destination will be created on Solution Manager to read system data from satellite system. This RFC destination is essential for all scenarios and hence can not be skipped. The TMW Destination will be created on Solution Manager and will be used for the Change Request Management (Charm) functionality. You only need this RFC destination if you want to setup Change Request Management. The BACK Destination will be created on satellite system. This RFC will be used to send Service Data from the managed system to the SAP Solution Manager system and to get service definitions from Solution Manager. The TRUSTED or LOGIN Destination will be created on Solution Manager to jump to satellite system. This RFC will be used by dialog users in the SAP Solution Manager for connecting to managed systems when using Operation tools, Implementation Tools, or Change Manager functionality. If you want to create trusted RFC destinations the administration user in the satellite system as well as in Solution Manager needs the authorization object S_RFCACL. You have to maintain the SAP role SAP_S_RFCACL in transaction PFCG of both systems and assign it to the administrator users.

There will also be the RFC destination SM_<SID>CLNT<Client>_ TRUSTED in the satellite system. This RFC can be assigned as the RFC destination in table BCOS_CUST for sending service desk messages to the Solution Manager Service Desk. Sender requires an account in the Solution Manager to successfully send the message. Please make sure that the latest version of the Add-On ST-PI is implemented in the satellite system. Otherwise the generation of the RFC destinations will end with warnings. You can alsocreate the RFC destinations in transaction SMSY manually for the satellite system and skip this step, if you cannot implement the latest version of ST-PI.

Prerequisites check
In this step the prerequisites for the connection of the satellite system to Solution Manager Diagnostics will be checked. There is a list of prerequisites to be fulfilled on the managed systems in order to connect them to the Solution Manager Diagnostics. If the status turns red, check the prerequisites for managed systems accordant to SAP Note 1274287 and implement the minimum support packages and SAP Notes to the satellite system. Also, read SAP Note 1010428 and check if the managed system is supported for E2E Diagnostics according to the Solution Manager SP level. How to run:

1. Click Change

2. Click Execute All

3. The system will check the prerequisites. You need to refresh the page manually to see the results.

4. You must get a result like this:

Manual configuration
In the step Manual Configuration" several manual steps will be performed to prepare the diagnostics setup. If an activity ha s to be performed, depends on the system type of the satellite system. At first you have to install the diagnostics agent. The diagnostics agent establishes the connection between satellite systems and Solution Manager Diagnostics. The SMD agent needs to be installed on operating system level. The installation and

configuration of the diagnostics agent is described in a separate setup guide in great detail. You can find this guide on:http://service.sap.com/diagnostics -> Installation & Configuration -> Diagnostics Agent Setup Guide. When you install diagnostics agents you have to follow some rules regarding the installation of the several agents on one host and regarding the systems to be managed. First is, you should install only one agent per physical or virtual host. Second is, one agent can manage several systems if and only if the systems run on the same physical or virtual host as the diagnostics agent. So you have to plan your landscape carefully, to make sure that all rules are met and the diagnostics setup will run smoothly. As the Diagnostics agent belongs logically to the managed system it is updated automatically with the update of SAP Solution Manager. This means that in case of an upgrade, it is not needed to update the agent manually and you do not have to care about this. In the next activity you have to assign the diagnostics agent to the Solution Manager. This is done using the agent administration. In the agent administration you can find all agents that are found in the SLD of Solution Manager and attach them to the Solution Manager as managing system. During the installation of a diagnostics agent you have to provide the agent with the SLD data of the Solution Manager. There is a trick to bypass this manual agent attachment. During the installation you can also provide the direct connection to your Solution Manager via Message Server or P4 port. If you want to provide the Message Server data select "No SLD connection" during the installation. In this case the agent is assigned to Solution Manager automatically and you can skip the "Assign diagnostics Agent" activity. In the Maintain SAPRouter data activity you have to maintain the SAPRouter data for your managed system in the Service Market Place, so that a service connection can be opened for the maintenance case. The activity "Adjust HTTP Log Parameter" is only needed for ABAP and dual stack with ABAP and Java. We need to set this parameter in each system based on ABAP to enable the analysis of logs written by the Internet Communication Manager (ICM). Perform the activity as described in the IMG documentation and restart the ICM in transaction SMICM after the changes to the log parameters. On J2EE based systems or on dual stack with ABAP and Java we need to activate the flight recorder by adding a parameter to the J2EE instance profile. This parameters works like the black box in a plane and collects data also in case the J2EE system is crashing. So you can analyze the crash later on. On a dual stack system you can use transaction RZ10 to maintain the profile parameter, on a J2EE only system you need to enter the parameter manually to the J2EE instance profile in the file system. In the last activity you configure the DBA cockpit. The main purpose of the DBA cockpit is Database Monitoring and Analysis of all connected satellite systems centrally from the Solution Manager. You just need to open the DBA Cockpit Configuration Wizard from SOLMAN_SETUP and follow the instructions.

Diagnostics configuration
Now we can connect the satellite system to Solution Manager diagnostics. Before the Diagnostics Configuration is started, the system landscape information in transaction SMSY need to be prepared carefully! Check if the full qualified hostname is added to the host of the satellite system. To maintain SMSY correctly please follow the instructions from the linked guide in SAP Note 1265070, which describes for different system types, how they should be maintained in SMSY to work together with Diagnostics smoothly. There is some product specific configuration like configuration for MDM, Duet and PI. If necessary perform this configuration first. After performing the product specific configuration, open the Diagnostics Managed System Setup Wizard by clicking on the Configure Diagnostics" link. Select the system you want to setup from the list and expand the managed products tree. Initially all systems are set to not diagnostics relevant". Uncheck Not Diagnostics Relevant" and select the correct product version. Click on set to close the subtree. If your landscape has a red status alert, check what is wrong and correct it in SMSY.

After all settings are correct and you have all traffic light set to green select the button Setup <SID>" in the right lower corner to move to the next screen. On the next screen you have to add some information regarding the connection to the managed system and you have to assign an agent to the system. Enter the information properly and open the agent subtree to assign the agent. After you opened the subtree you can select a free agent from the list. If you have several agents installed on the physical host, because you may have several systems running on the host, make sure that you select the agent with the same hostname as your satellite system. Enter the required information on ITS and click on set" to assign the agent. Wait until the agent is assigned successfully. Click on refresh" to check the agent status. If you see an green flash in front of the agent, the assignment was finished successfully. Click on next" to switch to the next screen. Check if all necessary setup steps are selected and click on Setup" to start with the setup. The setup may take a while. When the execution of the wizard is finished, a report displays the status of the execution. Result of Setup steps can be reviewed at any time later on, using the "Setup results" link in the managed systems setup wizard

Introscope configuration
In this step the Wily Introscope is configured. Not all of these configuration activities are required for each system type. The IMG documentation tells you whether you must perform the configuration. The 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. To configure the bytecode agent select the Java Stack of your satellite system from the dropdown box and mark the checkbox in front of the introscope agent. Expand the autoprobe directives box and select the autoprobe directive appropiate for your system. Click on apply to configure the introscope bytecode agent with the right autoprobe directives. The Java Stack needs to be restarted after the introscope agent configuration.

Create logical components

In the last step you have to create a logical component or assign your system to an existing logical component. Usually the customers have a three system landscape for there products. That means they have one system of product version SAP ERP as development system, one as quality assurance system and one as productive system. Even if the systems are physically seperated they belong together in a logical way building a develoment line. To bring the systems together is a logical way the Solution manager uses the concept of logical components. The three systems of one development line are added to the same logical component, but with different system roles. A logical component assigns systems and clients with different system roles to a main instance of a product. The logical components will be added to solutions and projects later on. To assign your satellite system to a logical component select the right product version and main instance from the drop down lists. You can use an already extisting logical component and assign the system by clicking in the right system role column. You can also create a new logical component for you system. After doing this the managed system setup is finished. You have to perform this wizard for all of your managed systems. After creating a logical you can add you systems to solutions and projects.