Prerequisites


For the comunication of your Solution Manager with SAP ,ensure that the following prerequisites are fullfilled

Transaction: OSS1



If you have problems with the connection test of SAPOSS you can check and maintain settings for the connection in transaction OSS1. The RCF SAPOSS will be adapted automaticlly after change of configuration in OSS1.



For transaction OSS1 and RFC connection SAPOSS in SAP Note 17285

S-user Authorizations

URL: http://service.sap.com/user-admin

You can check the authorization objects of your Solution Manager S-user with the „Authorization reports“. Please ensure that your S-user has at least the marked authorization objects.

Check of Prerequisites Support Package LevelsPlease ensure that all support package levels for the managed systems (satellite systems) are up to date according to SAP Note 1274287.
Please also check if the mentioned SAP Notes are applied in the managed systems.

Check of Prerequisites Client Copy

SAP delivers standard Solution Manager configuration in clients 000 and 001.
but it always recommended is to create a productive client and keep the master client original. It is also recommend to create an additional client for the BI Content because it is more secure to work only with communication users on BI data and it’s easier for root cause analysis in case of problems.

Therefore please create a new productive client (and also consider creating a separate BI Client) and perform the client copy using profile SAP_ALL with 000 as the source client and 001 as the source client for users

Check of Prerequisites Client Copy – Convert UME
After you created a new productive client you need to convert the Java user store to the new productive ABAP client. Please ensure that you entered 001 as “Source Client User Masters” for your Client Copy. Without the standard java users from 001 the Java engine will not start after converting UME!

You can find a detailed description in the IMG (Implementation Guide - transaction SPRO) in the tree Basic Settings -->General Settings -->Convert UME



Basic Settings - Initial Configuration

Here we do following steps :-

User Administration
Create an Solution Manager administration user
Create an Business Partner for this user

Technical Configuration
Initial technical configuration

SLD Configuration
Start the automatic SLD Configuration
Read System Data into Solution Manager SLD

Basic settings – General Configuration SAP Solution Manager IMG



t-code :- SPRO

The IMG tree contains all Basic Setting and Scenario- Specific Settings for your Solution Manager.
Always up to date implementation guideline
Automated configuration wizards can be used



The Central Correction Note is used to bundle all notes that are necessary for the scenarios set up by the basic configuration of SAP Solution Manager. It can be implemented at 1 with transaction SNOTE or as part of the automated procedure at tab Information:- Guided Procedure for Automated Basic Configuration.

Basic Settings - Initial Configuration New Guided Setup Wizard for Basic Configuration


New guided setup wizzard for Basic Configuration
Transaction: SOLMAN_SETUP



If you start the SOLMAN_SETUP for the first time, you will be asked to activate Web Dynpro Services to display the wizard in your browser screen.

Transaction: SOLMAN_SETUP


Start the activity “Initial Configuration – User Administration“
User Administration

Solution Manager Administration user will be created


User SOLMAN_ADMIN is created with the authorization profile ZSAP_SOLMAN_ADMIN

When the option Add Authorization for Note Implementation is selected,
it gives the specified user the authorization S_DEVLOP

If an administrator user already exists we can use that user and
adjust its authorizations using Only Update Authorizations
A Business Partner will be created for the user
The two roles Business Partner (Gen) and Employee will be assigned to
the user SOLMAN_ADMIN

Business Partners will be used for Solution Manager Scenarios like Service Desk
And Change Request Management



Ensure that SAP Note 1236420 is implemented and profile generation is filled
(transaction SU25 --> Initial Fill of Customer Tables).
Fill out the User data and click on “Execute”.
If a user already exists you can give the username and just click “Update Authorizations Only”
When CUA, is active you might get an error while creating/maintaining users.
In this case you can manually create a administrator user and assign the
role ZSAP_SOLMAN_ADMIN and skip this step



Transaction: SOLMAN_SETUP



Start the activity “Initial Configuration – Technical Configuration“

Technical Configuration

Some initial technical configuration will be done, for example modeling
the Solution Manager system in the system landscape or activating the
Service Data Control Center (SDCCN).



Just click on the button “Configure” to start the automatic Technical Configuration.

Check the Log area for warnings or errors.
Transaction: SOLMAN_SETUP


Start the activity “Initial Configuration – SLD Configuration“

To work with the tools of the Solution Manager we need technical information about the connected systems in the Solution Manager System landscape (SMSY)

To avoid manual maintenance, the Solution Manager uses its local SLD to read systems information like servers, databases, system component levels, application servers, support pack levels etc

You can connect the local Solution Manager SLD to a central SLD, which is the central information source for the system landscape. But the Solution Manager should be independent of the central SLD, to be available in the absence of SLD.

Configure Local System Landscape Directory
The Solution Manager uses its local SLD to read technical system information

Read data from SLD
Once the local SLD is configured you can read the data from the local SLD and update the system definitions in SMSY




Read SLD:
This step will reads data from the local SLD by running a background job RSGET_SMSY and updates the systems information in SMSY. Please remember that you have to ensure that the data is available in Solution Manager SLD before you can read the data for SMSY.





1. Provide ABAP and J2EE Administrator Users and Passwords

2. This step will create technical users for SLD

3. Deselect the option Generate Passwords and specify a password for
the technical SLD users.

4. Click Next to complete the SLD Configuration.

When you provide SOLMAN_ADMIN username/password make sure that you
logon as SOLMAN_ADMIN though SAP GUI and change the initial password.

After configuring the local Solution Manager SLD and before reading the SLD data for Solution Manager System Landscape (transaction SMSY) you have to think about how to get data in the Solman SLD.
That means at first you have to check if your system data is already available in a central SLD
(e.g. in an PI system) or if you like to use your Solution Manager SLD as central SLD.



Managed System Configuration for a ABAP system ---continued on next blog..