Solman Notes, Solution Manager Notes

7/30/2019 Solman Notes, Solution Manager Notes

1/9

Basic Configuration

Attachments:7

Added by Michael Kloeffer, last edited by Michael Kloeffer on Apr 15, 2010 (view change)

Basic Configuration

Before you start with configuration, don't forget to switch to the edit mode.Project

In the first step a project for the Solution Manager configuration will be generated. This project

provides an configuration template which we can use to track all configuration steps of our SolutionManager. This functionality is similar to upgrade and implementation projects that means you canalso use powerful tools from transaction SOLAR01 and SOLAR02.

1. Enter the necessary information or take over the proposed defaults2. After you clicked on "Create" the following steps will be executed: At first: create a Project SOLMAN_CON Then create a Logical Component Z_SOLMAN_COMP and add Solution Manager System

: Third the Solution 'SAP Solution' is created The Logical Component Z_SOLMAN_COMP is added to Solution 'SAP Solution' and the project

SOLMAN_CONImport Note
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Basic+Configurationhttp://wiki.sdn.sap.com/wiki/display/SMSETUP/Basic+Configurationhttp://wiki.sdn.sap.com/wiki/pages/viewpageattachments.action?pageId=180159120&metadataLink=truehttp://wiki.sdn.sap.com/wiki/display/~ya6uoexhttp://wiki.sdn.sap.com/wiki/display/~ya6uoexhttp://wiki.sdn.sap.com/wiki/pages/diffpages.action?pageId=180159120&originalId=187172865http://wiki.sdn.sap.com/wiki/pages/diffpages.action?pageId=180159120&originalId=187172865http://wiki.sdn.sap.com/wiki/display/~ya6uoexhttp://wiki.sdn.sap.com/wiki/display/~ya6uoexhttp://wiki.sdn.sap.com/wiki/pages/viewpageattachments.action?pageId=180159120&metadataLink=truehttp://wiki.sdn.sap.com/wiki/display/SMSETUP/Basic+Configuration


2/9

In the next step you have to implement the central correction note. The central correction notecontains all corrections notes currently created for Solution Manager. If you implement the collectionNote for the very first time, it is an good idea to download the Note with SOLMAN_SETUP but startthe implementation with transaction SNOTE from ABAP world to avoid Webdynpro timeouts.Read the note relevant for your SP carefully to make sure that you do not miss any manual steps.The notes with manual steps are listed in section two of the central correction note. During the

implementation you may get various interactive prompts, such as object belongs to an SAP packageand inactive objects. Click the green check mark to continue when you get these.If a SAP Note needs manual activities you will get a new window with the advice. After implementingSAP Note set the status to "Performed". Perform Post Processing steps after implementation, e.g.starting clean-up reports.Please keep the note up to date. This is done in transaction SNOTE by clicking on the Downloadlatest version of SAP notes" button and reimplementing the note if a newer version exists.More Information on the concept of central correction notes in SAP Solution Manager Installation Check
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Central_Correction_Noteshttp://wiki.sdn.sap.com/wiki/display/SMSETUP/Central_Correction_Noteshttp://wiki.sdn.sap.com/wiki/display/SMSETUP/Central_Correction_Notes


3/9

In this step an installation check is performed for configuration-relevant parts of the installation. Theinstallation check runs the following checks

the Transport Management System configuration. If the check TMS configuration is not successful,the Transport Management System is not yet configured and you should configure a transportdomain controller for the Solution Manager system. To do this call transaction STMS.

the profile parameters. The Solution Manager uses WebDynpro applications and Business Server Pages (BSP), which need profile parameters for Single Sign-On (SSO). If this check is not

successful, maintain the profile parameters in transaction RZ10 as described in the IMGdocumentation for the activity. The system must be restarted to enable the parameters. the license key. This check verifies if a valid license is installed in the Solution Manager. If this check

fails request a license key for Solution Manager and apply it using the transaction SLICENSE.the diagnostics prerequisites on the managing system. This activity checks if the Solution Manager System satisfies all the Prerequisites for End-to-End Diagnostics. Depending on the version of SAPSolution Manager and the version of the managed system, a minimum version for different softwarecomponents and the corresponding correction notes are required. Go to SAP Note 1010428 andselect the attached note relevant for your SP level of SAP Solution Manager.

the system landscape parameters. This activity checks if the value Synchronize is set for the Cross-System Synchronization Settings field in SMSY. This setting allows the corresponding system datamaintained in Solution Manager to be synchronized with SAP Support Portal.

the service connection to SAP. Here is checked if the RFC SAPOSS works and the distributiongroup is set to EWAIf a check status turns red, check the IMG Documentation for information on how to solve theproblem.Repeat the check to make sure the problem is fixed. You can exclude checks by setting theexecution status to Postpone or Manual to run only the checks that turned red during the last run.

In this screen you can either


4/9

1. Perform all checks by clicking the "Execute All" button (2)2. Select appropriate exection status When selecting "Execute" the activity will be executed with all other "Manual" activities will be performed manually and not by the automatic execution "Postponed" postpones the activity, either because it is not possible or not choosen to be executed

now3. The "IMG Documentation" link provides access to more documentation of this step and how to

perform/check manually4. The "Navigation" column provides links to the appropriate transactions to perform the

configuration/checkUser Data

In this step several user settings are performed. At first you have to provide the S-User for SAP Back-end. This s-user will be maintained as theSolution Manager user in the global settings of Solution Manager. It will be used for the RFCconnections SAP-OSS and SAP-OSS-LIST-O01.The S-User for communication is the S-user that will be maintained in transaction AISUSER together with the Solution Manager administration user. This mapping is necessary to make sure that theSolution Manager administration user can access service marketplace.You can enter information on the BI configuration that will be used in this Solution Manager. It is upto you to activate the BI content in your productive client or if you want to use a separate client or system. We would recommend to use an separate client for BI because it is more secure to workonly with communication users on BI data and it's easier for a root cause analysis in case of problems.

Additionally several Solution Manager system users are created.The user CONTENTSERV is the user for HTTP services like Webdynpro and BSP.The user SOLMAN_BTC is the user for the execution of background jobs.The user SAPSUPPORT is the support user for E2E tools. Instead of creating the default users and


5/9

generating password you can also specify password or specify an existing user and password. It isrecommended to specify the password for the user SAPSUPPORT.Landscape Data

In the step Landscape data you will add information about Wily Introscope Enterprise Manager. Thisdata is required for Solution Manager Diagnostics to analyze the status of Java systems, e.g.performance data.The Wily Introscope Enterprise Manager has to be installed on operating system level of SAPSolution Manager or on a separate host, before it can be added here.The Enterprise Manager (EM) acts as the central repository for all Introscope performance data andmetrics collected in an application environment. The Enterprise Manager processes performancedata and makes it available to users for production monitoring and diagnosis. CA and SAP have anagreement allowing you to use Introscope with SAP-developed dashboards and instrumentation aspart of SAP Solution Manager. If you would like to increase the benefits of Introscope throughcustom dashboards and instrumentation, or extend Introscope's capabilities with Introscope


6/9

Powerpacks, those services and products are available from CA's Wily Technology Division. A guide on how to install EM can be found on http://service.sap.com/diagnostics under the link WilyIntroscope 8.0 Installation Guide".

After you installed the Enterprise Manager you can add the following information in the SolutionManager basic setup.Host-name of the Enterprise Manager installationThe Port for the communication between Enterprise Manager and the Introscope Agent. Per defaultthis port is 6001. The port can be changed during the installation of Enterprise Manager The user credential to log on to Enterprise Manager. The credentials can be found in the installationguide of the Enterprise Manager Information about the webview workstation. The port for the web access is per default port 8081.The port can be changed during the installation of Enterprise Manager too.The Enterprise Manager should always running on the system, therefore please ensure that theserver comes up again if you restart your server.Manual Configuration

Now you have to perform some manual activities in the Solution Manager. Every activity has an IMGdocumentation were you can find details on what has to be done during the activity.

The first activity is to activate the BI source system. We use the BI Content to store workloadinformation of satellite systems for the diagnostics part of Solution Manager.If you want to use the productive client as BI client you can just execute the activation by clicking onthe link "Activate BI Source System".

If you decided to use another client as BI client, you have to set the BI client first as described in theSAP reference IMG. The documentation can be accessed using the link to the IMG documentationor via transaction SPRO --> SAP Reference IMG --> Solution Manager --> Basic Settings --> BWsetup --> General Setting.To change the BI client call function module RS_MANDT_UNIQUE_SET in transaction SE37 andenter the BW client as the value for parameter "i_mand".Then choose Execute.

In the next activity is to adjust the BI authorization concept. In SAP Solution Manager, you need toconfigure BI to use a special authorization concept. This is needed for all reporting functionalities.
http://service.sap.com/diagnosticshttp://service.sap.com/diagnosticshttp://service.sap.com/diagnosticshttp://service.sap.com/diagnostics


7/9

To change the authorization concept log on to the configured BI client or system. Start transactionrscustv23 and select "Obsolete Concept with RSR Authorization Objects". Save your changes.

To prepare the diagnostics scenario we need to import the Wily Introscope Agent (IS agent). Theagent is responsible for collecting non-ABAP workload data for the Enterprise Manager and has torun on all J2EE server nodes. The diagnostics setup allows a central installation and configuration of

Wily Introscope agents from SAP Solution Manager without any operating system level access to themanaged systems. But to make this possible the agent must be deployed on Solution Manager JavaStack. To do this download the newest ISAGENT SCA from SAP Service Marketplace. Deploy theSCA to the SAP Solution Manager Java Stack using the Java Support Package Manager or Software Deployment Manager.

In the next activity you can connect a productive SLD to forward its data to SAP Solution Manager.You will now build up an bridge to the Solution Manager SLD to get all the system information. Toset up the bridge enter the productive SLD and add the Solution Manager under the section

Administration ? Data Supplier.

You can also link the on-line documentation to a central data source in your system landscape or to

the on-line help for SAP Solution Manager. The procedure for your Solution Manager system is thesame as for other ERP or Netweaver systems. Start the activity and refer to the IMG documentationfor further information.

Automatic Configuration

In this step of SOLMAN_SETUP the automatic configuration will be done. You can exclude activitiesfrom automatic configuration if necessary.


8/9

The first two activities are to activate basic BC sets and activate piece lists for Service Desk, IssueTracking and Maintenance Optimizer. Be careful with the activation of BC sets since existingcustomizing will be overwritten by the BC set activation. To activate BC sets no client in the SolutionManager systems must be set to productive. Check if the customer has already existing customizingfor e.g. Service Desk in the system. Then you must not activate the Service Desk BC set. In thiscase you have to activate the BC sets for Maintenance Optimizer and Issue Tracking manually usingthe documentation of the SAP Reference IMG in transaction SPRO.

The third activity activates the services for WebDynpro and BSP applications which you need for allSAP Solution Manager scenarios.

The Diagnostics configuration activity configures the diagnostics application that is used to performroot cause analysis across your solution landscape.The following steps are performed:1. Setup Single Sign On between ABAP and Java2. Update Wily Introscope Enterprise Manager connection information3. Store ITS connection information4. Generates a template for the SAProuter table to allow SAP AGS to access Root Cause Analysis

tools5. Stores BI connect information6. Run CCMSBISETUP routine to activate BI content7. Activate BI Web Template HTTP Services8. Start BI Housekeeping Jobs to cleanup old data in the BI Infocubes9. Create WEBADMIN RFC destination on J2EE side10. Create TCP/IP connections WEBADMIN and SOLMANDIAG on ABAP sideIf something went wrong during this step you can enter the managing system setup using the URLhttp://:/smd and run the managing system setup again.

In the next three activities Business Partners for key users and the business partner screen aregenerated. The business partner screen generation makes the necessary preparations to create

Business Partners. Business partners avoid having to create a separate user in the SAP SolutionManager system for every user who creates Service Desk Messages, Issues or Change Documents.Service Desk functionality requires some Business Partners for Persons with the roles general andemployee and one Business Partner for Organization. Some of the business partners that arecreated in this step include SAP Support, SAP Engagement Architect, SAP Support Advisor, SAPTechnical Quality Manager, SAP Backoffice and SAP Consulting.

In the activities schedule Background jobs and standard jobs different jobs are scheduled. TheBackground job that are scheduled are jobs for the housekeeping of SAP Solution Manager. Thestandard jobs are the same jobs as the jobs scheduled in transaction SM36 -- > Standard Jobs" andschedules jobs for general SAP housekeeping. Please make sure that the jobs are not alreadyscheduled in SM36 before executing this activity.

In the last activity the RFC SAP-OSS will be created as a copy of the RFC SAPOSS and the logondata will be updated with the S-User and Password provided in the step Basic Configuration-> User Data of SOLMAN_SETUP.

Complete


9/9

Follow SCN Contact Us

SAP Help Portal Privacy

Terms of Use

Legal Disclosure
http://scn.sap.com/docs/DOC-18476http://scn.sap.com/docs/DOC-18476http://help.sap.com/http://help.sap.com/http://www.sdn.sap.com/irj/scn/policy?view=PPhttp://www.sdn.sap.com/irj/scn/policy?view=PPhttp://www.sdn.sap.com/irj/scn/policyhttp://www.sdn.sap.com/irj/scn/policyhttp://www.sap.com/corporate-en/our-company/legal/impressum.epxhttp://www.sap.com/corporate-en/our-company/legal/impressum.epxhttp://www.sap.com/corporate-en/our-company/legal/impressum.epxhttp://www.sdn.sap.com/irj/scn/policyhttp://www.sdn.sap.com/irj/scn/policy?view=PPhttp://help.sap.com/http://scn.sap.com/docs/DOC-18476