Solution Manager 7.

1 (SP14) – Initial Setup
- All required support packages and add-on installations have been
installed (SOCO)
- SP 13
- You may have tried to perform solman_setup in SP1 and upgraded to
- No SLDs.

Pre-work (for SLD – last part) – required only if you copied client
001 to another client (e.g. client 100) and you wanted to use that
client as your productive client.
Do this in your new client:
- Create user CTC_NULL with password CTC_NULL
- You may need to create SLD_CS_USER, provide any password.
- Change user type of SLDDSUSER and SLDAPIUSER from dialog to
service (not required but may be useful)
- Add roles to your user (if you are not using solman_admin) – same
roles as solman_admin
- Go to http://hostname:5<sys_number>00/useradmin ->
configuration -> ABAP system -> change client number 001 to your
productive client
- Go to configtool, change ume from 001 to 100 (you can use find
then type 001 and change the configuration from 001 to 100).

Skip Step:
- Prepare Outside Discovery – will pursue this configuration on a later
- Configure SAP Gateway – updating..

1. Login to Solution Manager
2. Go to transaction solman_setup
3. Wait for a few seconds/minutes, until your browser will open. You will
see the below screen in your browser. (if you have previously run
this with SP1 you will see the below screens – step 4 onwards)

4. Click System preparation. The window below will be shown.

5. To create user, click edit button.

6. You can now create the user(s) by clicking “CREATE ALL USERS”
- Create the users for SOLMAN.
- Once you have clicked edit, the edit button will be changed to
“read only”.

NOTE: If you have previously run this SP1, SOLMAN_ADMIN and
SOLMAN_BTC will have missing roles, you will need to create/update
the users (go to step 9 to add roles to SOLMAN_ADMIN and
SOLMAN_BTC users).

7. Once you clicked “Create all users”, logs will be shown.
SOLMAN_BTC root@123
SMD_AGT root@123
SM_EXTERN_WS root@123
SM_INTERN_WS root@123

8. After creating the users, click next. (you can also change back to
read only mode)

9. To add roles to users SOLMAN_ADMIN and SOLMAN_BTC:

b. Scroll down to “needed roles” and click execute

Leave it as it is until end of system preparation). (Notice that the “EDIT” button is now “read-only” button. 10. You can also check the SOLMAN_ADMIN/SOLMAN_BTC user has a green status. Once you have clicked “execute”. only means that it is already running. Click next to proceed to “Check Installation”. . You should now be able to see that all users have been created with their recommended roles. g. c. the browser will then provide you with the screen shot below. Repeat steps a to e for SOLMAN_BTC. f. d. After few seconds to few minutes. you can check the logs: e.

You will see the below screen after clicking next (Check installation phase) .11.

You can choose to execute only the selected item or one by one (see below) Or you can choose to execute all. Any of the option you chooses. I used to have red status for “Check Profile Parameter” and “Software Prerequisites”. wait for it to finish. You can also check the logs (click one of the steps from the activities to view the logs.Profile parameters for SAP Solution Manager 7.. Example: System Pre-requisites: Log: Depending on this log. the logs will be shown in at the bottom of the selection (boxed in green) 13.* * . For this one.1) #. When the processing has finished. it will tell you which have failed (by having a “red” status instead of green. you need to edit some profile parameter (note 1582842 . Once you clicked execute.12. you should see the processing circle.

02.* Default profile DEFAULT * #.If you do not have any profile in that Import the profile.02.2017 08:43:03 abap/shared_objects_size_MB = 100 #parameter created by: SAP* 19.2017 08:41:19 rsdb/obj/buffersize = 50000 SAPDBHOST = SAPSOLMAN1 j2ee/dbtype = syb j2ee/dbname = SLM j2ee/dbhost = SAPSOLMAN1 SAPSYSTEMNAME = SLM SAPGLOBALHOST = SAPSOLMAN1 system/type = DS SAPFQDN = etc.2017 08:45:50 icm/keep_alive_timeout = 6000 #parameter created by: SAP* In the next screen if you see your parameter change it.02. . you can add one. .* * #.2016 17:57:35 DIR_PUT = E:\sybase\sap\SUM\abap #parameter created by: SAP* 10. This time pick the one with <sysid>_DVEBMGS<system number>_<hostname> which is an instance profile.* * #.2017 08:44:12 rtbb/buffer_length = 60000 #parameter created by: SAP* 10.2017 . we need to add it to instance profile via tcode rz10 following this guide: .$(SAPFQDN) rdisp/mshost = SAPSOLMAN1 rdisp/msserv = sapmsSLM rdisp/msserv_internal = 3901 enque/process_location = REMOTESA enque/serverhost = SAPSOLMAN1 enque/serverinst = 01 is/HTTP/show_detailed_errors = FALSE icf/user_recheck = 1 icm/HTTP/ASJava/disable_url_session_tracking = TRUE service/protectedwebmethods = SDEFAULT #----------------------------------------------------------------------- # SAP Central Service Instance for J2EE #----------------------------------------------------------------------- j2ee/scs/host = SAPSOLMAN1 j2ee/scs/system = 02 j2ee/ms/port = 3902 ssf/name = SAPSECULIB gw/acl_mode = 1 login/system_client = 001 dbms/type = syb dbs/syb/schema = SAPSR3 dbs/syb/server = SAPSOLMAN1 dbs/syb/dbname = SLM dbs/syb/port = 4901 j2ee/dbport = 4901 rsdb/ssfs_connect = 1 dbs/syb/cache_size = 300 rsec/ssfs_datapath = \SAPSOLMAN1\sapmnt\SLM\SYS\global\security\rsecssfs\data rsec/ssfs_keypath = \SAPSOLMAN1\sapmnt\SLM\SYS\global\security\rsecssfs\key NOTE 01: With adap/buffersize = 800000.****************************************************************************************************************************** #parameter created by: SAP* 10.#.* Version = 000003 * #.02.2017 08:47:10 zcsa/second_language = E #parameter created by: SAP* 10.* Generated by user = SAP* * #.2017 08:46:29 icm/host_name_full = SAPSOLMAN1 #parameter created by: SAP* 10.* Generated on = 08:46:16 login/accept_sso2_ticket = 1 #parameter created by: SAP* 10. 08:50:18 * #.Click on the drop down button for Profile.2017 08:45:05 zcsa/db_max_buftab = 10000 #parameter created by: SAP* 10. .2017 08:46:06 login/create_sso2_ticket = 2 #parameter created by: SAP* Do not forget to save the changes and restart SOLMAN for apply as well. otherwise. Then do the drop down on Profile again.2017 08:45:20 zcsa/presentation_buffer_area = 20000000 #parameter created by: SAP* 10.2017 08:46:51 csi/enable = 0 #parameter created by: SAP* 10. Choose Change.2017 08:47:00 rdisp/max_wprun_time = 3600 #parameter created by: SAP* SAPLOCALHOSTFULL = $(SAPLOCALHOST).2017 08:42:04 rsdb/obj/max_objects = 20000 #parameter created by: SAP* 10.2017 08:46:40 rdisp/elem_per_queue = 4000 #parameter created by: SAP* 10.02.2017 08:44:52 zcsa/table_buffer_area = 100000000 #parameter created by: SAP* 10. RZ10 --> Utilities --> Import Profiles --> Of active server .2017 08:45:34 sap/bufdir_entries = 10000 #parameter created by: SAP* 10.

16. you can face with error SISE_CONF837 and you see an error "The configuration of RFC SAPOSS is not correct" on top of the page. you will see the screen below. Go to the next step: Specify Connectivity Data. the connection test of SAPOSS is passed and the settings of this RFC is aligned with SAP Note 2000132. if you run TCODE .SM59. NOTE 02: Change zcsa/second_language from D to E to complete Check profile parameter. After clicking next. 14. However. . After all activities are green (maybe Check Software Prerequisites is still red). click next to proceed to Implement SAP Note (note 2217486) NOTE: If the error cannot resolve when recheck this step. You need to apply note 2239513 first then apply note 2217486 15.

18. Click on “Start Download” then “Start SAP Note Assistant”. open it and login with SOLMAN_ADMIN. Click to Check Service Connection to change status of RFC Destination Template to green and use S-User from SAP to check User Logon Information. Click Next to Step 4: Implement SAP Note. .sap”.17. You get a file with name “sapshortcut.


go to your solution manager and go to transaction SNOTE. 20. . Type in the SAP Note that you wanted to download (as stated in your browser – 2217486 and 2110259) and click execute/download 22. In SNOTE -> Go to -> Download SAP Note 21.19. SAP will then start to download the SAP Note. As stated in the help section of the screen. Wait for it to finish.

You will know that the note has been downloaded by this message (lower left of your SAP window) .23.

Select the note (click on note 2217486) to recheck Software Prerequisment. 25. Go to menu SAP Note -> Implement SAP Note . Follow guide for check this node. You can check the downloaded note via the screen below.24.

you can implement note 2110259 for SAP SP14. Repeat step 25. . telling you to apply the SAP Notes in the list. After finish note 221486. A pop-up window will appear.26. Click Ok. .


a new pop-up screen will appear. a few more notes are needed to be loaded. if not and want to read. Click yes if you are certain of the side effects. 28.27. 29. Click ok and wait for the download to be completed. You may need to download a few more notes. click on notes. . Once you have clicked ok. Once the download has completed. you will need to wait for the system to download ALL the notes in the list. 30. After all the notes have been downloaded. you may want to click cancel. if you are unsure what to do next.

31. If you click yes, you will then be asked if you want to
implement the notes all at the same time or one by one. Or you may
opt to check the notes and/or cancel.

32. Click on implement all (execute button), you will then see
another pop-up asking you if you have done the manual steps for a
specific note. Confirm that you have read and click ok (check mark).

33. If you haven’t done so, click on display, to display the note
and try to implement the manual steps in the note. (Just perform the
manual steps after the implementation as described in the note).

34. Another pop-up window will ask you to confirm that you have
read the notes. Click yes

35. You will then be informed regarding making repairs in foreign
namespaces. Just click check.

36. You will then be asked to confirm changes for SAP notes. Click

Click ok. . 38.37. You will then be presented with the screen below. Check if the notes have been implemented.

choose status “Performed”. Once all the SAP Notes have been implemented. . and the log are will be updated. go back to the browser. Wait a few seconds.39. 40. In the Implement SAP Note area.

42. Once completed. click next to proceed to Configure Connectivity step. . Click next to proceed to Post-process step. click “execute” button. The error will appears when you recheck this step You need to return previous step and check SAPOSS connection. After clicking execute. wait a few seconds and check the log area. 43.41. In post-process step.

Click on “Configure Web Dispatcher” . 46. Once this step has been completed. 45.44. click next to proceed to Configure Connectivity. You will then see the screen below after click next. you will see the screen below. Once you are in Configure Connectivity step. Click “execute” to perform this step and wait for it to finish.

etc. (http://sapsolman1.47. You can skip this and click next to proceed to “Set Authentication Type for WS”. In this step. Once you have clicked “Configure Web Dispatcher”. Click to “Test Connectivity” to finish this step. you explicitly allow SAP . you will then see the screen below. You can choose to specify web dispatcher for internal communication by ticking “SAP Web Dispatcher used” and imput your Web Dispatcher will be – user j2ee_admin/Ab123456) 49. you will see the log for detail this configuration: 48.

52.509 certificate authentication . X. It will open a new window: SOA Management 53. In Set Authentication Type for WS. Start the configuration by clicking “Start WebDynpro”. You may want to check the documentation first by clicking “Display” 51. Basic authentication . you can start performing by clicking “Start WebDynpro”. Ticket authentication 50. Click on Simplified Web Service Configuration. . The documentation states the specific steps needed to be done. Solution Manager to create Web services using the following authentication types: .

Service Administration Tab -> Simplified Web Service Configuration ..

You will then proceed to the screen below.54. NOTE: Since you don’t have HTTPS configured. Change status from “Not Performed” to “Performed”. you may want to configure it via RZ10 icm server port. You can see the logs have been updated as well. . you can log-out of the SOA Management. Choose API Settings Tab and choose all and click save. Status will be changed to green. 57. 55. 56. Once saved.

.58. Click next to go to next step (Enable Web Services).

59. You can choose to Execute all to create the logical port (in red box) . . In Enable Web Service. You can check the documentation by clicking Display (green box) . You can also check the configuration by clicking the Start WebDynpro link. Automatic Activity. You can manually perform this step by clicking Start WebDynpro (Blue box). . you can see the screen below. Use the documentation to guide you through this Here are the contents of the documentation.

60. Status will be green. Once the job has run and the configuration have been performed. . Once you have clicked the execute all button. the browser will add this part for you to know that the job is running. Logs will appear and with status green as well.

or PDAs). click next to Configure SAPConnect. 63. In this step. In Set Authentication step.  Separate systems: The SAP NetWeaver Gateway Services system and the SAP Solution Manager system are separate. sms). If not. 62. smartphones. In Prepare Landscape step. you need to click to “Generate new certificates” for user certificate.61. In this case. if you use Basic Authentication. In Configure SAPConnect step. you set up the infrastructure that enables SAP Solution Manager to send notifications using e-mail and text messaging (email. Cllick next to go to Configure Gateway step. Once done. 65. you activate SAP NetWeaver Gateway Services for mobile devices (for example. . notebooks. here are the required sub-steps to be done. you have to activate the SAP NetWeaver Gateway Services manually. you only need to wait the system check any policy till this message appears. 64. There are the following possible scenarios:  One system: The SAP NetWeaver Gateway Services and SAP Solution Manager share the same system. NOTE: If you don’t need to use SAP NetWeaver Gateway. click next to continue with Set Authentication Policy for Agents step. You can automatically activate the gateway services displayed in the list below.

(or click next from above current screen of your browser). Click on “Select SLD” to continue. .66.

Optional: .Password: solman_admin password or your password. A pop-up screen will appear.Https: check only if this is working and you want to use https .Port: Normally you would use 5<system number>00 . Either you already have SLD (single or multiple) or none.67.User: solman_admin or your user (optional) . Check the “Help” area. (for this one we’re using no SLD installed). Press the “Setup Local SLD” from the below screen shot. (optional) 69.Host: Input your host (ip address or server name) . . Click Ok. Follow the instructions in the help. 68.

Click change. If the user has only been created. . you will then be asked to change the password of the user. or if password has expired. 72. The process will continue. A new window will appear. You would need to provide passwords for different users . You will also need to provide passwords. I used user j2ee_admin/Ab123456 71. Login to the system.70. 73. Use your credentials or that of SOLMAN_ADMIN or any user with SAP_ALL profile. You need to provide the password for administration user .

it will then proceed. 75. Click next. Wait for it to continue and finish. You may face this error: . you will get the warning window. After you clicked next. click Cancel Process and create a new password for SLDDUSER 76. 74. You can monitor the progress on the top of the screen. If your password is the same with old password.

wait until it finishes or until user interaction is required. Solution: Create user: CTC_NULL with password CTC_NULL 77. 79. You can check the logs and/or the steps. 78. Click Next to proceed to next sub step of prepare landscape. It will then continue to configure. . When the configuration is finished you will be shown this screen. You can now close the window and proceed with your setup.

Click to Save and Refesh to update status of this step .80.

You will face with message un the first time you configure LMDB 82. On this step screen. the window message will appear. click to Configure LMDB Object Server.81. choose your LMDB object server name (default is LMDB_<server name>) . Click Next to LMDB configure.

you need to sync SLD with LMDB. click Save&Activate.83. If no error message is appears. After that. . Input full parameter for this sync connection. click Check to check this configuration. click to Add 84.

you need to upgrade SAP CR Content to version 1. refer to note 669669 Follow Note 669669.85. .vn:50000/sld/admin/index.etc.6. You may face with this error. Administrator => Detail => Data to check current version of SAP CR Content.40. Go to http://sapsolman1.jsp.

Click on Import under header Content (select increment file zip) .NOTE: You need to incrementally update. .x and 9.x to 9.x to 10.x. 8.x. go back to Administration – Import to upload the CRDelta content. Download the newest version of cimsap* and import to SLD Once the import is finished.from version 7.6 to 8.

4). The amount of time needed depends on the size of the update. I measured this update on a development system (not the best sized / fasted environment ) and it took an hour and a quarter to process the update. This import can take a significant amount of time.You can follow the progress of the import (see picture 3. This update was around 30 MB in size. .

back to Solman Management Configuration web abd cick to Active.jsp?view=data to active Activated.etc.86. 87. Click to Advanced to get the name of syncchronization job . You can see the Synchronization connection from http://sapsolman1. After upgrade CRDelta

Use transaction SM37 in Solman Manager to open Simple Job Selection.88. use Job Name in Advanced window to check the status of this job .

If not resolve. NOTE: You can see the warning log with percentage of job. delete the sync link and restart server. OR: use tcode SLG1 to view job log 89. Below is the job log when the synchronization is running well . When the synchronization is completed. kill the background process. click next to Set up SAP Solution Manager System in LMDB (May be you need to wait 2 days to complete this synchronization step)  Very slowlyyy???? See solution below NOTE: If thẻ synchronization stucks on process 0%. deactivate and delete Local SLD sync => recreate sync link.

you maybe seen the warning message allow is your CR Content outdated. After the synchronization is completed. You need to import the lasted version again. .90.

we delete and add new synchronization connections between SLD and LMDB. see SAP Note 1962139 NOTE: 1891566 . but the SAP CR Content version of your SAP Solution Manager LMDB is 12.1. We need to apply a specific SAP CR Content verion in the LMDB.Repair of LMDB CR Content .11.After update CR Content of source SLD to version 12.

implement the attached correction instructions. keep this restriction in mind: Do not change the CIM data model or the CR Content in any of the two namespaces or in any other SLD namespace that is synchronized with the LMDB.1 SP03 . which contains the inconsistent CR Content. o You need to use Tcode SM36 to create program with name “RLMDB_SAP_CR_REPAIR_LMDB”. . If your SAP Solution Manager is on release 7.Perform the CR repair in the LMDB by following the steps described below. During the repair. This repairs the corrupt CR Content data in the LMDB. and the namespace in the SLD that is configured as the source for the CR Content.SP09. During the repair. . However. (maybe 2 days) . you can continue using both LMDB and SLD as usual. you must not update the model or the CR Content as described in SAP Note 669669. Click to Job Wizard and follow the step o Use Tcode SM37 to view Job log and when job finished. In particular. Execute the repair program "RLMDB_SAP_CR_REPAIR_LMDB" as background job due to its long runtime (normally 2 days). two different CIM namespaces are used: The productive namespace in the LMDB ("active").

it writes progress information into the job log and summarizes the results once the repair is finished. . 91. . As the end of the repair. . If the repair fails because the restrictions mentioned previously were not adhered to. Check the job log to ensure that the data repair has been executed completely. . NOTE: Next to this step when the synchronization is completed. While the repair is running. SAP Note 1881516 describes how to identify and create missing associations without running of a full CR Content repair. you must start the repair again. or because the data in the productive namespace are damaged so that not all dependencies could be corrected in one run. associations between CR Content and system landscape (LD) data are repaired as well.

NOTE: After your synchronization is done. (login SAPUSR. client 001 – client use for pre-product not for customer product tcode SNOTE => done ) 92. Now you will be in “Set Up SAP Solution Manager System in LMDB”. You need to implement SNOTE 1849006 to resolve its. your SOLMAN roadmap status maybe change to gray (it’s green before). Choose type of IT Admin Role is Production System and click Save and Execute .

93. waiting 10 minutes for data supplier is synced. . You can face with this warning message.

On SLD window.If it’s not sync completely after 10 minutes => Click on SLD in SAP Solution manager system window to open SLD java stack. click more to open information of Data supllier .


On Manual Activities. 95. In Automatic Activities.94. Click next to go to “Migrate SMSY data into LMDB”. Change the Execution Status to Performed. click to Execute All to complete this step .

. You may face with error when execute Activate SDCCN. click Execute All.96. Click next to Configure Automatic step. go to Solman Manager => tcode SDCCN => Utilities(M) => Activate => done.

You will now be in “Prepare Outside Discovery”. 98. In this step. .97. you will need to do the steps manually. Change all Execution Status to Performed. You can choose to display the documentation to guide you through the manual activities needed.


Run command smdsetup managingconf hostname:"sapms://myhost. (Optional) Click Get Agents.domain. Click Next to go to the next sub step “Connect Diagnostic Agent”. you wil be face with warning Follow this guide to check this message: a. Login to server with Diagnostics Agent admin user (slmadm) <STD>ADM.99. In this server lab is slmadm b.corp" port:"50xx0" user:"SMD_ADMIN" pwd:"xxxxxx" . Stop the Diagnostics Agent c. Go to the directory /usr/sap/<SID_AGT>/J<Instance_Number>/script or /usr/sap/<SID_AGT>/SMDA<Instance_Number>/script d.

1 SP14.domain. the user is SMD_AGT instead of SMD_ADMIN. As of Solution Manager" port:"50000" user:"SLDDSUSER" pwd:"Ab123456" e. smdsetup sldconf hostname:"sap.corp" port:"50xx0" user:"SMD_AGT" pwd:"xxxxxx" where the hostname is the Solution Manager full host name. and xx in the port is the number of the Solution Manager SCS instance number. Start the Diagnotics Agent f. click Connect . or smdsetup managingconf hostname:"sapms://myhost. select agent in list. Back to Solman Management Configuration step 6.etc. click Get Agents. Check if the Agent is shown in the page of Agent Administration in Solution Manager system.7. 100.

Here you will see the summary of the system preparation and your next steps (in the help section). Click finish You have just finished system preparation for Solman 7. 102. you will be in the “Complete” step. You will also see the summary of the system preparation. After clicking next.1 SP14 .101.