Solution Manager 7 1 SP14 System Preparation

Solution Manager 7.
1 (SP14) Initial Setup

Assumptions:
- 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
SP14
- 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
date.
- Configure SAP Gateway updating..
Steps:
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_ADMIN root@123
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:

a. Select SOLMAN_ADMIN
b. Scroll down to needed roles and click execute

c. Once you have clicked execute, the browser will then provide
you with the screen shot below, only means that it is already
running.
d. After few seconds to few minutes, you can check the logs:
e. You can also check the SOLMAN_ADMIN/SOLMAN_BTC user has a

green status.
f. Repeat steps a to e for SOLMAN_BTC.
g. You should now be able to see that all users have been created
with their recommended roles.
10. Click next to proceed to Check Installation. (Notice that the

EDIT button is now read-only button. Leave it as it is until end of
system preparation).
11. You will see the below screen after clicking next (Check
installation phase)
12. 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, the logs will be shown in at the
bottom of the selection (boxed in green)
13. Once you clicked execute, you should see the processing
circle, wait for it to finish.
When the processing has finished, it will tell you which have failed
(by having a red status instead of green.
For this one, I used to have red status for Check Profile Parameter
and Software Prerequisites.
You can also check the logs (click one of the steps from the activities
to view the logs.
Example: System Pre-requisites:
Log:
Depending on this log, you need to edit some profile parameter

(note 1582842 - - Profile parameters for SAP Solution Manager 7.1)
#.* *
#.* Default profile DEFAULT *
#.* *
#.* Version = 000003 *
#.* Generated by user = SAP* *
#.* Generated on = 10.02.2017 , 08:50:18 *
#.* *
#.******************************************************************************************************************************
#parameter created by: SAP* 10.02.2017 08:47:10
zcsa/second_language = E
rdisp/max_wprun_time = 3600
csi/enable = 0
rdisp/elem_per_queue = 4000
icm/host_name_full = SAPSOLMAN1
login/accept_sso2_ticket = 1
login/create_sso2_ticket = 2
icm/keep_alive_timeout = 6000
sap/bufdir_entries = 10000
zcsa/presentation_buffer_area = 20000000
zcsa/db_max_buftab = 10000
zcsa/table_buffer_area = 100000000
rtbb/buffer_length = 60000
abap/shared_objects_size_MB = 100
DIR_PUT = E:\sybase\sap\SUM\abap
rsdb/obj/max_objects = 20000
rsdb/obj/buffersize = 50000
SAPDBHOST = SAPSOLMAN1
j2ee/dbtype = syb
j2ee/dbname = SLM
j2ee/dbhost = SAPSOLMAN1
SAPSYSTEMNAME = SLM
SAPGLOBALHOST = SAPSOLMAN1
system/type = DS
SAPFQDN = etc.vn
SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(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, we need to add it

to instance profile via tcode rz10 following this guide:
- Click on the drop down button for Profile.If you do not have any
profile in that Import the profile.
RZ10 --> Utilities --> Import Profiles --> Of active server
- Then do the drop down on Profile again. This time pick the one
with <sysid>_DVEBMGS<system number>_<hostname>
which is an instance profile.
- Choose Change.
- In the next screen if you see your parameter change it,

otherwise, you can add one. Do not forget to save the changes
and restart SOLMAN for apply as well.
NOTE 02: Change zcsa/second_language from D to E to
complete Check profile parameter.
14. 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. Go to the next step: Specify Connectivity Data, 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.
However, if you run TCODE - SM59, the connection test of SAPOSS is

passed and the settings of this RFC is aligned with SAP Note
2000132.
16. After clicking next, you will see the screen below.
17. 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.
18. Click Next to Step 4: Implement SAP Note. Click on Start

Download then Start SAP Note Assistant. You get a file with name
sapshortcut.sap, open it and login with SOLMAN_ADMIN.
19. As stated in the help section of the screen, go to your solution
manager and go to transaction SNOTE.
20. In SNOTE -> Go to -> Download SAP Note
21. Type in the SAP Note that you wanted to download (as stated
in your browser 2217486 and 2110259) and click
execute/download
22. SAP will then start to download the SAP Note. Wait for it to
finish.
23. You will know that the note has been downloaded by this
message (lower left of your SAP window)
24. You can check the downloaded note via the screen below.
25. Select the note (click on note 2217486) to recheck Software

Prerequisment. Follow guide for check this node. Go to menu SAP
Note -> Implement SAP Note
26. After finish note 221486, you can implement note 2110259 for
SAP SP14.
- Repeat step 25, A pop-up window will appear, telling you to apply
the SAP Notes in the list. Click Ok.
27. Once you have clicked ok, you will need to wait for the system
to download ALL the notes in the list.
28. Once the download has completed, a few more notes are
needed to be loaded. Click ok and wait for the download to be
completed.
29. You may need to download a few more notes.
30. After all the notes have been downloaded, a new pop-up
screen will appear. Click yes if you are certain of the side effects, if
not and want to read, click on notes, if you are unsure what to do
next, you may want to click cancel.
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 havent 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
Ok.
37. You will then be presented with the screen below. Click ok.
38. Check if the notes have been implemented.

39. Once all the SAP Notes have been implemented, go back to
the browser. In the Implement SAP Note area, choose status
Performed.
40. Wait a few seconds, and the log are will be updated.
41. Click next to proceed to Post-process step. In post-process
step, click execute button.
42. After clicking execute, wait a few seconds and check the log
area.
The error will appears when you recheck this step
You need to return previous step and check SAPOSS

connection.
43. Once completed, click next to proceed to Configure

Connectivity step.
44. Once you are in Configure Connectivity step, you will see the
screen below. Click execute to perform this step and wait for it to
finish.
45. Once this step has been completed, click next to proceed to
Configure Connectivity.
46. You will then see the screen below after click next. Click on
Configure Web Dispatcher
47. Once you have clicked Configure Web Dispatcher, you will
then see the screen below. Click to Test Connectivity to finish this
step, you will see the log for detail this configuration:
48. You can choose to specify web dispatcher for internal

communication by ticking SAP Web Dispatcher used and imput
your Web Dispatcher will be used. (http://sapsolman1.etc.vn:8000
user j2ee_admin/Ab123456)
49. You can skip this and click next to proceed to Set
Authentication Type for WS. In this step, you explicitly allow SAP
Solution Manager to create Web services using the following
authentication types:
- Basic authentication
- X.509 certificate authentication
- Ticket authentication
50. In Set Authentication Type for WS, you can start performing by
clicking Start WebDynpro. You may want to check the
documentation first by clicking Display
51. The documentation states the specific steps needed to be

done.
52. Start the configuration by clicking Start WebDynpro. It will

open a new window: SOA Management
53. Click on Simplified Web Service Configuration.

- Service Administration Tab -> Simplified Web Service
Configuration
54. You will then proceed to the screen below.
Choose API Settings Tab and choose all and click save.
NOTE: Since you dont have HTTPS configured, you may

want to configure it via RZ10 icm server port.
55. Once saved, you can log-out of the SOA Management.
56. Change status from Not Performed to Performed. Status

will be changed to green.
57. You can see the logs have been updated as well.
58. Click next to go to next step (Enable Web Services).
59. In Enable Web Service, Automatic Activity, you can see the
screen below.
- You can choose to Execute all to create the logical port (in red
box)
- You can check the documentation by clicking Display (green box)
- You can manually perform this step by clicking Start WebDynpro

(Blue box). You can also check the configuration by clicking the
Start WebDynpro link. Use the documentation to guide you
through this
Here are the contents of the documentation.

60. Once you have clicked the execute all button, the browser will
add this part for you to know that the job is running.
Once the job has run and the configuration have been performed.
Status will be green. Logs will appear and with status green as well.
61. Once done, click next to continue with Set Authentication
Policy for Agents step.
62. In Set Authentication step, if you use Basic Authentication,

you only need to wait the system check any policy till this message
appears. If not, you need to click to Generate new certificates for
user certificate.
63. Cllick next to go to Configure Gateway step. In this step, you

activate SAP NetWeaver Gateway Services for mobile devices (for
example, smartphones, notebooks, or PDAs).
There are the following possible scenarios:
One system: The SAP NetWeaver Gateway Services and SAP
Solution Manager share the same system. You can automatically
activate the gateway services displayed in the list below.
Separate systems: The SAP NetWeaver Gateway Services system
and the SAP Solution Manager system are separate. In this case,
you have to activate the SAP NetWeaver Gateway Services
manually.
NOTE: If you dont need to use SAP NetWeaver Gateway, click next
to Configure SAPConnect.
64. In Configure SAPConnect step, you set up the infrastructure
that enables SAP Solution Manager to send notifications using e-mail
and text messaging (email, sms).
65. In Prepare Landscape step, here are the required sub-steps to
be done.
66. Click on Select SLD to continue. (or click next from above
current screen of your browser).
67. Check the Help area. Either you already have SLD (single or
multiple) or none.
68. Follow the instructions in the help. (for this one were using no
SLD installed). Press the Setup Local SLD from the below
screen shot.
Optional:
- Host: Input your host (ip address or server name)
- Port: Normally you would use 5<system number>00
- Https: check only if this is working and you want to use
https
- User: solman_admin or your user (optional)
- Password: solman_admin password or your password.
(optional)
69. A pop-up screen will appear. Click Ok.

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

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

Solution:
Create user: CTC_NULL with password CTC_NULL
77. It will then continue to configure, wait until it finishes or until

user interaction is required.
78. When the configuration is finished you will be shown this

screen.
79. You can check the logs and/or the steps. You can now close
the window and proceed with your setup. Click Next to proceed to
next sub step of prepare landscape.
80. Click to Save and Refesh to update status of this step
81. Click Next to LMDB configure. You will face with message un
the first time you configure LMDB
82. On this step screen, click to Configure LMDB Object Server,

the window message will appear, choose your LMDB object server
name (default is LMDB_<server name>)
83. After that, you need to sync SLD with LMDB, click to Add
84. Input full parameter for this sync connection, click Check to
check this configuration. If no error message is appears, click
Save&Activate.
85. You may face with this error, refer to note 669669
Follow Note 669669, you need to upgrade SAP CR Content to

version 1.6.40.
Go to http://sapsolman1.etc.vn:50000/sld/admin/index.jsp,
Administrator => Detail => Data to check current version of
SAP CR Content.
NOTE: You need to incrementally update. - from version 7.6 to
8.x, 8.x to 9.x and 9.x to 10.x.
Download the newest version of cimsap* and import to SLD
Once the import is finished, go back to Administration Import to

upload the CRDelta content. Click on Import under header
Content (select increment file zip)
You can follow the progress of the import (see picture 3.4). This
import can take a significant amount of time. 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. The
amount of time needed depends on the size of the update. This
update was around 30 MB in size.
86. After upgrade CRDelta packages, back to Solman
Management Configuration web abd cick to Active. You can see the
Synchronization connection from
http://sapsolman1.etc.vn:50000/sld/admin/details.jsp?view=data to
active Activated.
87. Click to Advanced to get the name of syncchronization job

88. Use transaction SM37 in Solman Manager to open Simple Job
Selection, use Job Name in Advanced window to check the status of
this job
NOTE: You can see the warning log with percentage of job.
OR: use tcode SLG1 to view job log
89. When the synchronization is completed, 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%, kill the
background process, deactivate and delete Local SLD sync
=> recreate sync link. If not resolve, delete the sync link
and restart server. Below is the job log when the
synchronization is running well
90. After the synchronization is completed, you maybe seen the
warning message allow is your CR Content outdated. You need to
import the lasted version again.
After update CR Content of source SLD to version 12.11, we
delete and add new synchronization connections between
SLD and LMDB, 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, see SAP Note 1962139
NOTE: 1891566 - Repair of LMDB CR Content

Perform the CR repair in the LMDB by following the steps described
below. During the repair, two different CIM namespaces are used:
The productive namespace in the LMDB ("active"), which contains
the inconsistent CR Content, and the namespace in the SLD that is
configured as the source for the CR Content.
During the repair, you can continue using both LMDB and SLD as
usual. However, 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. In
particular, you must not update the model or the CR Content as
described in SAP Note 669669.
- If your SAP Solution Manager is on release 7.1 SP03 - SP09,

implement the attached correction instructions.
- Execute the repair program "RLMDB_SAP_CR_REPAIR_LMDB" as

background job due to its long runtime (normally 2 days). This
repairs the corrupt CR Content data in the LMDB.
o You need to use Tcode SM36 to create program with name

RLMDB_SAP_CR_REPAIR_LMDB. Click to Job Wizard and
follow the step
o Use Tcode SM37 to view Job log and when job finished.
(maybe 2 days)
- While the repair is running, it writes progress information into the
job log and summarizes the results once the repair is finished.
Check the job log to ensure that the data repair has been
executed completely.
- As the end of the repair, associations between CR Content and

system landscape (LD) data are repaired as well. SAP Note
1881516 describes how to identify and create missing
associations without running of a full CR Content repair.
- If the repair fails because the restrictions mentioned previously

were not adhered to, or because the data in the productive
namespace are damaged so that not all dependencies could be
corrected in one run, you must start the repair again.
91. NOTE: Next to this step when the synchronization is

completed.
NOTE: After your synchronization is done, your SOLMAN
roadmap status maybe change to gray (its green before).
You need to implement SNOTE 1849006 to resolve its. (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. Choose type of IT Admin Role is Production System and click
Save and Execute
93. You can face with this warning message, waiting 10 minutes
for data supplier is synced.
If its not sync completely after 10 minutes => Click on SLD in SAP
Solution manager system window to open SLD java stack. On SLD
window, click more to open information of Data supllier
94. Click next to go to Migrate SMSY data into LMDB. On Manual
Activities, Change the Execution Status to Performed.
95. In Automatic Activities, click to Execute All to complete this

step
96. Click next to Configure Automatic step, click Execute All.
You may face with error when execute Activate SDCCN, go to

Solman Manager => tcode SDCCN => Utilities(M) => Activate =>
done.
97. You will now be in Prepare Outside Discovery. In this step,
you will need to do the steps manually. You can choose to display
the documentation to guide you through the manual activities
needed.
98. Change all Execution Status to Performed.

99. Click Next to go to the next sub step Connect Diagnostic
Agent. (Optional)
Click Get Agents, 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. In this server lab is slmadm
b. 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. Run command
smdsetup managingconf
hostname:"sapms://myhost.domain.corp" port:"50xx0"
user:"SMD_ADMIN" pwd:"xxxxxx"
or
smdsetup managingconf
hostname:"sapms://myhost.domain.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. As of Solution Manager 7.1 SP14, the user is
SMD_AGT instead of SMD_ADMIN.
smdsetup sldconf hostname:"sap.etc.vn" port:"50000"

user:"SLDDSUSER" pwd:"Ab123456"
e. Start the Diagnotics Agent
f. Check if the Agent is shown in the page of Agent Administration

in Solution Manager system.
100. Back to Solman Management Configuration step 6.7, click Get

Agents, select agent in list, click Connect
101. After clicking next, you will be in the Complete step. Here
you will see the summary of the system preparation and your next
steps (in the help section). You will also see the summary of the
system preparation.
102. Click finish
You have just finished system preparation for Solman 7.1 SP14

Solution Manager 7 1 SP14 System Preparation

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Solution Manager 7 1 SP14 System Preparation

Uploaded by

Copyright:

Available Formats

Solution Manager 7.

1 (SP14) Initial Setup

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

NOTE: If you have previously run this SP1, SOLMAN_ADMIN and

7. Once you clicked Create all users, logs will be shown.

9. To add roles to users SOLMAN_ADMIN and SOLMAN_BTC:

b. Scroll down to needed roles and click execute

e. You can also check the SOLMAN_ADMIN/SOLMAN_BTC user has a

f. Repeat steps a to e for SOLMAN_BTC.

10. Click next to proceed to Check Installation. (Notice that the

Or you can choose to execute all.

Depending on this log, you need to edit some profile parameter

NOTE 01: With adap/buffersize = 800000, we need to add it

- In the next screen if you see your parameter change it,

14. After all activities are green (maybe Check Software

However, if you run TCODE - SM59, the connection test of SAPOSS is

18. Click Next to Step 4: Implement SAP Note. Click on Start

20. In SNOTE -> Go to -> Download SAP Note

25. Select the note (click on note 2217486) to recheck Software

29. You may need to download a few more notes.

35. You will then be informed regarding making repairs in foreign

38. Check if the notes have been implemented.

The error will appears when you recheck this step

You need to return previous step and check SAPOSS

43. Once completed, click next to proceed to Configure

48. You can choose to specify web dispatcher for internal

- X.509 certificate authentication

51. The documentation states the specific steps needed to be

52. Start the configuration by clicking Start WebDynpro. It will

53. Click on Simplified Web Service Configuration.

NOTE: Since you dont have HTTPS configured, you may

55. Once saved, you can log-out of the SOA Management.

56. Change status from Not Performed to Performed. Status

- You can check the documentation by clicking Display (green box)

- You can manually perform this step by clicking Start WebDynpro

Here are the contents of the documentation.

62. In Set Authentication step, if you use Basic Authentication,

63. Cllick next to go to Configure Gateway step. In this step, you

69. A pop-up screen will appear. Click Ok.

72. The process will continue.

73. You will also need to provide passwords.

- You need to provide the password for administration user

- You would need to provide passwords for different users

After you clicked next, it will then proceed.

76. You may face this error:

Create user: CTC_NULL with password CTC_NULL

77. It will then continue to configure, wait until it finishes or until

78. When the configuration is finished you will be shown this

82. On this step screen, click to Configure LMDB Object Server,

Follow Note 669669, you need to upgrade SAP CR Content to

Download the newest version of cimsap* and import to SLD

Once the import is finished, go back to Administration Import to

87. Click to Advanced to get the name of syncchronization job

OR: use tcode SLG1 to view job log

89. When the synchronization is completed, click next to Set up

NOTE: 1891566 - Repair of LMDB CR Content

- If your SAP Solution Manager is on release 7.1 SP03 - SP09,

- Execute the repair program "RLMDB_SAP_CR_REPAIR_LMDB" as

o You need to use Tcode SM36 to create program with name

- As the end of the repair, associations between CR Content and

- If the repair fails because the restrictions mentioned previously

91. NOTE: Next to this step when the synchronization is

92. Now you will be in Set Up SAP Solution Manager System in