Solution Manager 7.2 Configuration Steps

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 76

Solution Manager 7.

2 Configuration

 First call the T-code "SOLMAN_SETUP" with production client (Eg.


100) and user solman_admin----> should be not created from SAP
level, as it will be created at the time of installation

 It will open in Web-Browser


 Select System Preparation under Mandatory Configuration

System Preparation


1 Define System Role:

 In the each step we have to change it in to edit mode and select


Production system

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

 3.1 RFC Connectivity


 
 Here Solution Manager will ask to connect SAP Service Marketplace by
using SUID and password

 Contd…
 We have to provide SUID and password and click on Maintain
Connections

 Once everything done click next


 3.2 Support Hub Connectivity
 Automatic Activities:
 This to be done

 Configure SSL Store:

 Call T-Code: strust



 First click on edit mode and right click on"SSL Client(Anonymous)" and
choose "create"
 After clicking on create it will ask as below screenshot use default
settings and validate


 After that The anonymous certificate shall appear in the "Own
Certificate" section. Double click the entry and press the "Add to
Certificate List" button

 Contd… Scroll down to find Add to Certificate List and click on it

 

 

 Configure Consumer Proxies and Log. Port


 Open T-Code: SOAMANAGER

 It will open in browser


 Select service administration tab and choose Web Service
Configuration

 Select Consumer Proxy and search for the proxy and open that proxy

 Once clicked select "Manual Configuration"


 Provide Logical port name and description, then give next

 Provide user name as solman_admin and password, then give next



 

 Manual Activity 
 Configure SOAP Runtime
 Call T-Code: SBGRFCCONF in SAP GUI

 Point to Define Supervisor Dest. Tab

 Call T-Code: SRT_ADMIN

 Choose Perform Check on Technical Settings and then execute


 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

 Choose manual step and select Make settings Checkbox and


execute

 To configure the IDP service: Call T-code: WSIDPADMIN

 Use the default values and choose schedule


 To create and register the inbound destination in client 000


 Login with 000 client
 Start T-Code: SRT_ADMIN
 Choose Automatic Setup and select the Perform Technical Setup
radio button


4 Apply Recent Corrections
 

 4.1 Corrections for SNOTE

 Implemented all these notes


 4.2 Essential ABAP Corrections
 As per below screenshot we have to implement a note from SAP GUI by
calling T-Code: SNOTE

 4.3 Java Corrections


 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
 

 

 As per the above there is some RFC connectivity is missing, we will


observe after LMDB Synchronization

 1.2 LMDB Synchronization


 For more information follow the documentation as per the below
navigation

 Link:
https://help.sap.com/viewer/c413647f87a54db59d18cb074ce3dafd/7.2.
05/en-US/a5971735dd184f5c8d943c6cf423d13a.html
 Initially we have to configure LMDB Object Server

 

 Next step is we have make Synchronization Connections between SLD


and LMDB, click on "Add"


 In this step we have to provide details as mentioned below once
providing we have to click on check

 After checking we it shows message as "Entries checked, no errors",


then we have to click on "Save and Activate"

 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

  

 Then close SAP GUI and come back to SOLMAN_SETUP in GUI(previous


session)

  
 Click on Advanced Tab

 Scroll down and monitor the status


 Now while Synchronizing LMDB this following Background job will be


scheduled i.e. SAP_LMDB_LDB_*

 Finally SAP_LMDB_LDB_* job finished it will take max up to 3days


 Go next
 1.3 LMDB Content Check

 Provide the JAVA AS SID and "save and execute"

 Error


 LMDB Configuration
 Call T-Code LMDB

 It will redirect in browser and appears as

 Click on "Technical Systems"

 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

 The next step is

 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

 For that we have register the program from OS Kernel Directory.


 The command which have to give is rfcexec -a <RFC_PROGRAM> -g
<HOST> -x sapgw00 & Example: rfcexec -a SLD_UC -g solman -x
sapgw00 &
 rfcexec -a SLD_NUC -g solman -x sapgw00 &

 

 After that we have to check connection test for SLD_NC SLD_NUC
 Connection Test for SLD_UC

 Connection Test for SLD_NUC

 After again that call a T-Code: RZ70


 Login to SLD by calling URL solman.<host>:50200/sld


 Choose Administration--->details

 And select Data Suppliers from there make a note of Gateway Host
and Gateway Port and maintain those things in RZ70

 Call a T-Code: RZ70 to pull the data


 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

 Choose Application Server ABAP give SID and select Edit


 Open Advanced and select as per the Screenshot

 So that all data will be Synchd.


 On the left hand side of LMDB screen select Software on the right hand
side click on Set Diagnostics Relevance, then save

 Now proceed the step 1.3 LMDB Content Check under Infrastructure
Preparation
 1.3 LMDB Content Check

 2 Set up Java Connectivity


 2.1 Define HTTP Connectivity
 Provide the mandatory details check Test Connectivity
  

 The result will be shown


 2.2 Enable Connectivity:

 Perform Automatic Activities


 After clicking Execute all a Background job will be scheduled named as


SMSETUP: AGS_IP_CONN
 Check in T-code SM37

 

 
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

 In SM37 we can check the status that user has created



 

 

3.3 Enable SAP BW:


 Steps are postponed
 
4. Define Introscope
Skipped.

6.Configure CRM Basics


 Initially we have to Perform Automatic Activities then later we have to
do Manual Activities.
 Once executing all a it will schedule in background and background job
will be created


 

 Finally automatic activities performed hence job also finished

 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.

 

 Now System prompts to create a TR.

 After creating TR it will show like this

 Activity2: follow note 635697


 Finished
7. Enable Gateway Services

 Contd…

 Scroll down and click on checkbox Select/Deselect all Gateway Services


and hit for prepare Activation
 Before that we have to create a Customizing Request by T-Code SE01 or
SE09

 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

 Search for the service AGS_FLP_INTEROP and select the service


and choose ICF Node ODATA and then Activate it.

 It will ask for Choose Package select Local Object

 Search for the service AGS_FLP_PAGE_BUILDER_PERS and select


the service and choose ICF Node ODATA and then Activate it.

Basic Configuration:

 1 Configure Basic Functions:


 By clicking on Execute All from above screen shot a batch job has
scheduled

 Status:

 These are the steps performed, in case if it doesn’t done automatically,


we have to perform manually

2. Schedule Jobs
 There are several jobs to be scheduled, those jobs will be schedule
under SOLMAN_BTC we have to perform those

 We can check that all jobs have been scheduled


3.Configure Manually------> for each activity we have to click on


Documentation for the steps to follow once it done change the
Execution status

 Configuration of Rapid Content Delivery


 Then change the Execution status to Performed


 Delete Session Documents and Download


 Contd..

 Finally save and execute from the screenshot


 Go to SM36 and schedule a job

 After giving the details then save, it will redirects to next page to
provide program, give as per the below screenshot

 Check the status in SM37


 Service Content Update Configuration:

 Check on Schedule in batch, then confirm

 Then change the Execution status to Performed



 After that we can see successful message as shows below

 Then change the Execution status to Performed

 

 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

 From the above screenshot click on Maintain Connections


 Choose the relevant system ID to select the required system.

 Creating Service:
 Choose "Set up Connection types".

 Click the icon in front of the service name to select the HTTP Connect
URLAccess connection service.

 Select a contact person and save

 Now use "Back" to navigate back to the following view:


 Creating the URL and maintaining the system data:


 Navigate to the "URLs" section and expand it.

 Choose "Create" to create a URL or choose the relevant link ("URL"


field) to change an existing URL.


 

 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

 *****SOLUTION MANAGER 7.2 CONFIGURATION


FINSIHED******
What is Diagnostics Agent in SAP Solution
Manager?

Answer: You can monitor Java components of your solutions, with


Solution Manager Diagnostics. The SAP Solution Manager passes the
solution data to the Solution Manager Diagnostics.

Installation of Diagnostics Agent


 Download latest SWPM from the above navigation based on your OS
 Open SWPM and expand Generic Options and select Install-Diagnostics
Agent


 Provide the package path for SAPEXE.SAR SAPHOSTAGENT.SAR
SAPJVM6.SAR SAPDIAGNOSTICAGENT.SAR files


Error
 

 For that we have to download the SAPHOSTAGENT 721 version patch


of 18 and replace the file

Error

 SAPDIAGNOSTICSAGENT.SAR file is missing or not supportable

 The path to download SAPDIAGNOSTICSAGENT.SAR file is below


screenshot

 After downloading rename the file to SAPDIAGNOSTICSAGENT.SAR


and replace the file to Kernel dump

 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

 

 

 

 Now restart the server to effect changes


 Initially there were only 2 Instances named as SOB, SOJ now After
restarting the server we can see one more new Instance named as DAA

You might also like