Solution Manager 7.2 Configuration Steps
Solution Manager 7.2 Configuration Steps
Solution Manager 7.2 Configuration Steps
2 Configuration
System Preparation
1 Define System Role:
2 Check Prerequisites
Contd...
After performing Execute All it displays following errors that we have to
perform those displayed manually
As per the issue here we have to change the value for parameter from
T-code rz10, and create a parameter
icm/server_port<x>=PROT=SMTP,PORT=0,TIMEOUT=120,
PROCTIMEOUT=120 which is shown below
Another issue is we have to implement a SAP NOTE: 2294619 as the
issue is displayed below
We have to perform automatic activities and we have to perform
manual activities, for manual activities we have to navigate through
documentation provided in the section
Contd...
3 Setup Connections to SAP
Contd…
We have to provide SUID and password and click on Maintain
Connections
After that The anonymous certificate shall appear in the "Own
Certificate" section. Double click the entry and press the "Add to
Certificate List" button
Select Consumer Proxy and search for the proxy and open that proxy
Manual Activity
Configure SOAP Runtime
Call T-Code: SBGRFCCONF in SAP GUI
Choose Check specific client and enter the SAP Solution Manager local
client. Do not change the other settings.
The result gives you the status of the prerequisites to be fulfilled to use
the SOAP runtime.
For each red color status we have to follow the some procedure to fix
the issue
To activate required ICF nodes: Call T-Code: SRT_ADMIN
4 Apply Recent Corrections
4.2 Essential ABAP Corrections
As per below screenshot we have to implement a note from SAP GUI by
calling T-Code: SNOTE
Maintain Technical Users:
By clicking on Create All users all users will be created
Infrastructure Preparation:
1.1 SLD Connections:
Click on Create New Connection
Once selecting Create New Connection it prompts to give details
Register your ABAP system to the SLD of your system landscape
Go to T-Code: RZ70
Link:
https://help.sap.com/viewer/c413647f87a54db59d18cb074ce3dafd/7.2.
05/en-US/a5971735dd184f5c8d943c6cf423d13a.html
Initially we have to configure LMDB Object Server
In this step we have to provide details as mentioned below once
providing we have to click on check
Its processing
It thrown error that user has no authorization for that we have to assign
profile for the user in SU01 under Profile Tab we have to add profile
SAP_NEW
Click on Advanced Tab
Go next
1.3 LMDB Content Check
Provide the JAVA AS SID and "save and execute"
Error
LMDB Configuration
Call T-Code LMDB
Select Application Server ABAP and give SID and click on "create"
After clicking on Create button it appears as below
Provide these details and give next
Finally save
Its processing
Run T-Code:RZ70
We will find that error RFC SLD_UC and SLD_NUC by checking the
connection test, it will throw error as shows
And select Data Suppliers from there make a note of Gateway Host
and Gateway Port and maintain those things in RZ70
At the time of pushing data by using RZ70 one background job will be
created i.e. SAP_LMDB_NOTIFY_LDB_0000000001, it means
synchronization between SLD and LMDB,
Call T-code: LMDB
It will opens in browser, in that select Technical System
Now proceed the step 1.3 LMDB Content Check under Infrastructure
Preparation
1.3 LMDB Content Check
2.3 Diagnostics Agent Authentication
Have to Install Diagnostics Agent Authentication, you can have a look of
procedure on PageNo.61
In this step, you configure the connections between the Diagnostics
Agents and SAP Solution Manager.
In addition, you provide a root certificate so that Diagnostic Agents can
be authenticated when connecting to SAP Solution Manager.
Diagnostics Agents Connections
Observe the number of authenticated, unauthenticated, and
disconnected Diagnostics Agents:
Authenticated Diagnostics Agents are connected to SAP Solution
Manager
Unauthenticated Diagnostics Agents are connected to SAP Solution
Manager, but are not authenticated
To authenticate Diagnostics Agents:
1. Choose Manage Agents to open the Diagnostics Agent
Administration.
2. Under Agents, choose the Non-authenticated Agents tab page.
3. Select the agents that you want to authenticate and choose Trust
Agents.
For each selected Diagnostics Agent, a dedicated authentication
certificate is generated and assigned, using the root certificate.
Note: On the Connected Agents tab page, you can choose Offline Agents
to filter for unconnected agents. Check for entries that correspond to
Diagnostics Agents that you do not plan to connect again, because, for
example, the associated host has been dismantled or renamed. Remove
the entries, if required.
Agent Authentication Root Certificate
Use this screen area to provide a valid authentication root certificate.
The system uses the root certificate to create authentication certificates
for each of the Diagnostics Agents in the To authenticate Diagnostics
Agents step above.
You can either generate or upload a valid root certificate.
To generate a root certificate:
1. Choose Generate.
2. Enter an expiration date.
The metadata of the top-level authentication root certificate is
displayed.
If your company has a certification authority (CA), you can upload the
root authentication authority issued by this CA.
To upload a root certificate:
1. Choose Upload.
2. Provide the required information.
3 Set up BW
3.1 Confirm SAP BW
3.2 Maintain Users
Contd…
Click on Create all users, after that below screenshot shows that users
being created in background
Manual Activities
Activity1: Technically Upgrade Products
Use
In this activity, you execute the COM_PRODUCT_UPGRADE report as a
prerequisite for using CRM products (configuration items) in the current
SAP Solution Manager release.
Requirements
To execute this activity within a system landscape:
Some of the upgrade methods generate objects, such as database
tables, structures, or function modules, so the system prompts for a
transport request that can include the generated objects.
Transport the transport request to the follow-up systems in the system
landscape, before running the report in them.
Activities
Execute the COM_PRODUCT_UPGRADE report manually in transaction
SA38 because the system might request a transport request.
Contd…
Manual Activities:
Open SAP GUI and call T-Code: /N/IWFND/MAINT_SERVICE
Activate the following services:
AGS_FLP_INTEROP
AGS_FLP_PAGE_BUILDER_PERS
Basic Configuration:
By clicking on Execute All from above screen shot a batch job has
scheduled
Status:
2. Schedule Jobs
There are several jobs to be scheduled, those jobs will be schedule
under SOLMAN_BTC we have to perform those
Contd..
After giving the details then save, it will redirects to next page to
provide program, give as per the below screenshot
Service Content Update Configuration:
Enable Remote HTTP Connection:
Follow as per the SAP Note 592085
Setting up the service, maintaining the system data, and opening the
service connection in the SAP Support Portal (SAP Service Marketplace)
Log on to the SAP Support Portal using the following
URL: https://support.sap.com/remote-support/remote-connections.html
Creating Service:
Choose "Set up Connection types".
Click the icon in front of the service name to select the HTTP Connect
URLAccess connection service.
Save it
Maintain the relevant URL. Note that the URL must end with / (forward
slash) if it ends with the port.
Finally this activity is performed and change the status.
Enable Remote R/3 Connection:
Note :812732
It was done during SAP Router Configuration..
Schedule Application Log Cleanup:
Note:1911102
Start T-Code: slg2 and do as per the screenshot finally execute
Create Dialog Users:
Contd..
Once giving click on Create All users, it will ask for password as per
the below screenshot
It takes some time to create users and assigning roles to specified
users, in logs you can monitor the status. After that check in T-Code:
SU01 where those users created and roles assigned, in not assign the
roles to those users.
Users created
Provide the package path for SAPEXE.SAR SAPHOSTAGENT.SAR
SAPJVM6.SAR SAPDIAGNOSTICAGENT.SAR files
Error
Error
Provide Hostname
It ask to provide SID and drive, by default it will pick and go with next
Give the password it should be as in the format of B!smi@123
The above error showed that solman_admin was locked, for that we
have to unlock the user.. If it shows again give cancel