“Solution Manager Configuration, EWA, Remote connectivity & SLD

configuration”
Transaction: Solman_setup

Enter the user and pass

User: Ac_salik

Pass: Smartsap@1255

“Fist Part of Configuration System Preparation”

Press continue and proceed to System preparation (1st Part)

Click System Preparation

 Click Edit and select system role as “Development System” and press next

Here the first task is to “Check SLD Configuration on Java”

For this we need to run the web link to check SLD which is given in the display document
Now we will first configure SLD on solution manager for Java system for this we will run the link
to configure SLD

[Link]
As now SLD has been configured. We will proceed back to point number 2 in the system
preparation part

After executing the activity, we will change the status to perform.

After executing the activity, we will change the status to perform

After executing the activity, we will change the status to perform

As we have installed a new solution manager system and not performed an upgrade of Solman,
so we will mark this performed and proceed further.

In this activity we need to first configure the backbone in the system after which we can
proceed further.

SAP BACKBONE CONNECTIVITY

It is on a different document the entire process once completed then marks the entry as “Performed”
 VAR Badi is an optional step so just mark it “performed”

Now below it shows Manual Activities

On clicking the Execute All the list generated error below

 We will click “show” to check what issues are here

Now we need to perform this task manually.

Now, go to transaction STC01 and run Task list “SAP_SUPPORT_HUB_CONFIG”

Select the first check box and click confirm as the activity is performed manually after which
which it will turn green.
 Now select the next log and press Execute it will turn Green.

Now as we already have the Technical S-User, we will click and confirm, it will be green.
Next we have already applied the SSL_Certificates in STRUST so we will click confirm and it will
turn green.

Now edit it and add the details for e.g: Technical S-User, password & Router string

Router String /As this machine of Solman does not have the internet
access:/H/[Link]/S/sapdp99/H/[Link]/S/sapdp99/H/

Technical S-User: S0025542188

Pass: ********
 Check Save and proceed

Check Save and proceed

Now we will run the process in background

 After the task list run is completed we will proceed to the next manual activity.

In this activity these highlighted task are to be performed.

Logon to SAP GUI on Client 000 and run transaction SRT_ADMIN

Kinldy perform this activity of Productive Client of Solution Manager & on 000 Clinet
 Now we need to resolve these issues.

This issue got resolved as per SAP Note# 3304943 - ESI - 'No service destination defined. Further
destination checks not possible' error in SRT_ADMIN technical check

Resolution
Perform the steps below and reconfigure the Web Services Runtime:
 Run Technical Reset in SRT_ADMIN
 Run Technical Setup in SRT_ADMIN
For more information about the Runtime Setup in SRT_ADMIN, please check the SAP Notes
below:
New UI
Classical UI
Now run Solman_ Setup and run Execute all, now it shows missing Abap parameters
Copy all these missing parameter’s and add them in rz10 profile, the value of these parameters
are shows in the details.

All missing parameters are added in the RZ10 profile of ABAP

 Now save the profile so it can be updated and activated, Next restart the application for
permanent changes.

After restarting the application, I have started Solman_setup and will re execute the previous
activity of system preparation.

After execution it has turned green

 Now I will move onto step 3 of system preparation

Now in this step previously we have already done the hub configuration so we will press
execute all to check
Now as the hub connectivity is completed successfully, enter the AISUSER here and save it

The system has showed a warning after which I have created a dialog User same as of the
aisuser in the sap GUI and assigned it SAP_ALL profile
In the next step we will go to transaction AISUSER and make a new entry here.
Now we will go back to the and save the AISUSER over the web interface of Solman_setup
After pressin refresh the system generated the log and gave a warning in the task list
SAP_SUPPORT_HUB, ignore it and we will proceed further on to point 4

Now we will start the step 4.1

Check if the system is non-modifiable make it modifiable and start again.
Now go to S note and implement the S-Note
Make a TR and save it
It requires a tr to be made, make a new and proceed.
Now the Note is completely implemented, we will start post processing
ABAP Correction completed now we will proceed to point 4.3 Java Correction
As this is a new Solution manager system so java has already been updates and it is a manual
activity so change it to Perform and move further
As in Point # 5 Click Create/Update all user.
All points are completed, now click Export to PDF and extract a PDF copy of system preparation
after which click finish.
Now the First part of Solution Manager Configuration is completed, now we will proceed to the
second Part Infrastructure preparation.

“2nd Part Infrastructure Preparation”

 URL: [Link]

User: j2ee_admin

Pass: Saima#54321

In my case at initial it was giving an error message HTTPIO_PLG_CANCELED, which I resolved by

checking SMICM, in there I found out that the port of HTTP was not present,

After which we checked RZ10, and added the ports of http & smtp + icm full host name and
then the issue git reolved.

Now scroll up and press SAVE the check will turn green and proceed next
 Click edit and scroll down

Select the SLD role that is the complete one and press Assign Existing HTTP Destination
As soon as you press Edit it will automatically pick the Object Server Name
Set the Rank of Source Namespace to 1 from -1, then press Check

All Entries checked no errors. Now press Save & Activate

The Job “SAP_LMDB_LDB_0000000001” is running once it will be completed the status will be
green.

You can click Advance and scroll down the pop up to see how much percentage is completed
Our Step is completed and we can see the status is now green
After pressing edit, the system automatically picked the system ID, it is proposed. Click save and
execute to proceed.

Now it shows these errors in the log. Which we have to resolve.

 How we resolved it !!

Run transaction LMDB on the gui

Here it shows warning in the status

Here in the technical System when I select ABAP it does not show me the system ID which is the
issue.

Moving forward to Transport Domain, we are unable to see any transport domain. In this issue
we found a SAP Note 2381495 - LMDB: System missing Extended SID in Transport Domain

Link to the note is attached. [Link]

This SAP Note suggests that, while transport domain info for ABAP system will be automatically
created to SLD/LMDB by the background job

Background Job: “SAP_LMDB_NOTIFY_LDB_0000000001”

 1. Check job log for and look for errors on CL_LMDB_TRANSPORT_MGMT_CONS. Based on
that, there are two possibilities:
A. If errors on CL_LMDB_TRANSPORT_MGMT_CONS:
1. Follow error message instructions.
2. Check for possible solution on 1592461 and 2475429
3. If necessary, create an case/chat for SV-SMG-CM
B. No errors on this consumer:
1. Open the technical system Overview page on LMDB and click on Details
2. Go to Properties tab and make a dummy change on tmsdomain property
3. Save and undo the change.
4. Wait for next execution or start the
job SAP_LMDB_NOTIFY_LDB_0000000001
2. Once job is finished, check Transport Domains on LMDB.
3. Check if there are obsolete systems in the LMDB. Check if there are systems with extended
similar SIDs such as ABC0001. If such systems are no longer needed they may also be part
of the same Transport Domain and can cause conflicts. After removing the system push the
data supplier from RZ70 again.
Now as Checked for the background Job it is already executed with no errors. After which we
open STMS transaction to see that the transport Domain is configured in the system or not,
which we found out that it is not configured, so we will first configure the Transport domain
first to see if it helps in resolving the issue.
Upon pressing save the system asked to define a password for User TMSDM, after saving the
password below message is displayed.
 Now Click Over view and then click SAP SYSTEM

Now Click SAP System and then click update system configuration.
After Saving now select SAP System  Create  Virtual system. If it shows approve option then
kindly press it over wise move back to transport management system screen.

Now press overview  Transport route  press edit  configuration  standard

configuration  development and production  Enter the DEV SID and Virtual SID in
production and press Save.
 Your transport route has been configured.

Now coming back to the error which we were facing in the infrastructure preparation / LMDB
content Check 1.4

Now first step is go transaction RZ70 in your sap gui.

Enter the Gateway / Host & Gateway Services, press save and execute.
 It gave us an error, now we need to open RZ10 and change the value of the parameter
“gw/acl_mode” from 1 to 0 and restart the application server for the changes to take effect
After the system has restarted, go to sm59 and open TCP/IP

Delete previously made two connections SLD_NUC & SLD_UC

Now open the Java SLD page
Now enter the Solution manager host in the Gateway Host & Gateway Service
After entering the values, press save. After which you need to stop and start the SLD.

Click Stop SLD and then Start SLD

Now go to SM59 again and create another RFC by the name of “SLD_DS_CONNECTION”

Open HTTP Connection to External Server.

Press create new

Enter details just as in the below image.

On the next step enter user and password and test connections.
Now go to transaction RZ70 and press execute
Now add the SLD_DS_Connection in rz70
Now go back to the SLD home page and click Technical System

Now it shows that the system is update

 Now again go to solution manager configuration, infrastructure preparation step 1.4 (LMDB
Content Check)

It still gives the message Application Server ABAP <Not Found in LMDB>

In the previous step 1.3 LMDB synchronization it gives a warning message that CR content is out
dated
Now we need to update the CR Content.
 This Error is because the CRM Content is out dated.

Before updating the CR-Content we will check point # 1.3 in solution manager configuration,
infrastructure preparation.
Now as it is showing application server ABAP because we previously resynchronize Technical
system from SLD, So we will press Edit and then save and execute

Which will turn the status green.

Now as you may see point # 1.4 is green and 1.3 still shows warning due to out dated CR
content.

Now we will update the CR Content, for this you need to go to SLD Home page 
administration tab
 Click Import

Here it shows that the current Cr-Content date is of 01/23, but as of now the most latest is
06/23
 Now there are two important files here 1. CIM 2. CR Delta

I already have the downloaded cr content so I will just upload it in the system and press Import
After the Cr Content have been completed, we will move to the Solution manager
configuration, infrastructure preparation

As it is showing the warning here, we will press refresh

Now our LMDB is synchronized and set up correctly.

Now we will move to point #2  2.1
To remove above error, open gui and run transaction LMDB

Go to host, enter host and press display.

 Keep these setting and press save.

Now come back to Solution manager configuration, infrastructure preparation point # 2.1 and
press Edit

Enter FQDN in all three fields.

After entering press Test Connectivity
Now move to next step, press edit and then press execute all.
All steps have been completed, except the last one.

The Job is running keep pressing “Refresh”

Proceed to next step
Move to point # 3 Setting up BW
In the above automatic activity we still got the error, so now we will perform this manually. Go
to t-code RSA1 and perform below activities.
Now go to transaction se37

Set BW Client
Download Interscope Software.
 Un zip these files here.

After Unzipping, open the [Link] file move to bottom and change the last line with “accept”
After changing it to accept save it and now move the complete folder to Linux via winscp or any
other tool

This is a reference Note # 2557578

Now need to download and install the diagnostic agent
Now we need Install the Dignostic Agent for which we will run SWPM  Generic Option  SAP
Diagnostic agent  Install
 As now we have all three files, we will give permission of 777 to the folder

Now we will come back on to the software provisioning manager and give the path where we
have kept the files and press next.
Now all three files are available we will proceed forward by clicking next.
Pass: Saima#54321
Go back to Point No 2 Setup Connectivity

Click Diagnostic Agent Authentication

 Now Click Manage Agents, as of now it shows 0 authenticated agents.

Next it will take you to Agent Administration Portal, here click Non-Authenticated Agent tab
Here check and match the version that you have installed, select the agent and press Trust
Agent

Now on the Connected Agent tab press refresh and it will display your installed agent
Now go back to point # 2 Setup connectivity  2.3 Diagnostic Agent Authentication and press
refresh counter.

Scroll down further and press generate one more time.

Trusted Agent is set perfectly now, now move back to point #4 CA Interscope and press
Discover Interscope EM it will now display the diagnostic agent

Now give the path where apminterscope file is created at the time of installation of willy
Interscope Default in Sues Linux is /usr/sap/ccms
Give the path and press discover Installation.
It will automatically pick the installation, now here the issue is of Connection User Not Set.

Now click User Management and set password for either one Guest or Admin.

In my case pass is Saima#54321 for both, and I have selected Admin and press ok
 Still it shows, error in status

Will delete and reinstall the Interscope

Now will Re-Install Interscope
Interscope is installed successfully, now to check the status
Now after reinstalling CA Interscope we will go to point #4 CA Interscope and press edit.
After deleting the version of willy, we have download a older version. We will move the zip files
to the path on our linux machine and then first we will unzip on OS level the first file that is

WILYISEM00P_6-[Link]
After unzipping this file we move towards, the same path on winscp and there we will first open
the first file [Link] and set accept in the last.
 Next we will open [Link] here we will set 3 things

1. Password (Under Enterprise User Password Setting) (Below image 01)

2. Extension of Eula file. (Under General setting) (Below image 02)

3. Directory where Interscope to be installed (Under General setting) (Below image 03)
Pass: Saima1234 (For Introscope)
 After setting these we will save and go to the path where we have unzipped the file of willy
enterprise manager, we will give full permission via chmod 777 * to all the files and the run the
command as shown in the below image.

As the Introscope has been installed at our defined path that was /usr/sap/ccms.

Now we will move the next file that is WILYISMM00P_11-[Link] to this path by the
command mv WILYISMM00P_11-[Link] /usr/sap/ccms/apmintroscope
After moving the file we will do switch user (su adaadm) and go to the path were introscope is
installed and unzip the mm files
After this we will change user and group and then give full permission

chown sdaadm. sapsys *

chmod 777 *
 After this we will go to /usr/sap/ccms/apmintroscope/bin

And start the Enterprise Manager or Introscope with below command

./[Link] Start

./[Link] Status
Now we will go to the link infrastructure preparation, point no 4 Define CA Interscope

Press Edit and go to Discover Introscope, here give the path of Installation

It will pick the link, after this go to user management enter the password that was saved
previously in the [Link] file,

Check mark the Guest user but enter the same password for both.
 After this press Ok and then SAVE the tab and you willy Interscope has been completely
installed.

Moving to next point that is # 5 Set up email communication User, This is optional step and is
don automatically.
Move to next step Configure CRM Basic

Scroll down and press Execute All

As now all the activities are completed without errors, perform the 2 manual activities
“Technical Upgrade Products” & “Deactivate Creation of BDocs”
Login to GUI and run SA38 and enter the program, then press execute

It will ask to make a transport so make one new.

Now come back and select Performed and press Display of next activity.
 Now again go to gui and run transaction SMW3_00

Now one by one copy and enter the BDoc name, press do not send, press save and press next.
After completing, select performed and proceed next
Now move to next step Enable Gateway Services, select all services one by one and press
Activate

After the services are activated press I confirm and press next
Now as the second Part Infrastructure Preparation is completed press Export to PDF

Press Continue
Now select Include Log’s, select all and press OK
 Now start the Third Part Basic Configuration

Here Press Edit and press Execute ALL (This is a long activity will take 7-10 hours)
As it shows error in SDCCN, go to sap gui and run transaction SDCCN
 Select Early watch Alert, go to Edit and press Start now

Now Select Service Preparation Check, go to Edit and press Start Now
Press YES

Press YES
Now look at the point # 09 Collector and TCOLL (Schedule this job in Cline 000 with DDIC User
as per SAP Note 966309)
As the Job is completed but still Error reside we will select the services that have error and re
execute

After re execution the error is resolved.

One more has warning will do same
Another shows an error, will do same.
After Installing Willy Introscope this error is resolved automatically.
As our company does not create BP from here so we will manually mark it performed.