Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
patelyogesh
Active Contributor
57,469

Hello Friend,

You have your SAP Solution Manager ready for next step. You successfully upgraded your system following document

Now its time to make system ready for New Client, Profile Parameters & UME

Solution Manager Client

Note: As per SAP you do not require to create new client in SAP Solution Manager unless you have special requirements. You can continue configuring your system with SAP default client 001. I have show you below for an example. You can skip if you working with default clinet 001 to step : ABAP Profile Parameters

In my example I have SAP Solution Manager client 300

Make sure you set profile parameter login/no_automatic_user_sapstar = 0 in order to login new client

Perform client copy SAP_CUST

And SAP_USER

Your client is ready for next step.

ABAP Profile Parameters

Before making any changes to profile parameters make sure you have configured PHYS_MEMSIZE parameters for your ABAP system

You need to consider following for memory allocation

  • - SQL server memory allocation
  • - JAVA system memory allocation
  • - Wily Introscope memory allocation
  • - Operating System memory allocation
  • - ABAP system memory allocation

2048519 - Profile parameters for SAP Solution Manager 7.2

abap/buffersize

500000

abap/shared_objects_size_MB

350

csi/enable

0

icm/host_name_full

icm/server_port_<X>

***

login/accept_sso2_ticket

1

login/create_sso2_ticket

2

rdisp/elem_per_queue

4000

rdisp/max_wprun_time

3600

rsdb/cua/buffersize

10000

rsdb/ntab/entrycount

30000

rsdb/ntab/ftabsize

60000

rsdb/ntab/irbdsize

15000

rsdb/obj/buffersize

50000

rsdb/obj/max_objects

20000

rtbb/buffer_length

60000

sap/bufdir_entries

10000

system/type

zcsa/db_max_buftab

10000

zcsa/presentation_buffer_area

20000000

zcsa/second_language

E

zcsa/table_buffer_area

100000000

Add following parameters to ABAP instance profile

ABAP Instance

icm/server_port_0 = PROT=HTTPS,PORT=5$(SAPSYSTEM)01,TIMEOUT=60,PROCTIMEOUT=3600

icm/server_port_1 = PROT=SMTP,PORT=25,TIMEOUT=120,PROCTIMEOUT=120

icm/server_port_2 = PROT=HTTP,PORT=5$(SAPSYSTEM)00,TIMEOUT=60,PROCTIMEOUT=3600

ssl/client_ciphersuites = 902:HIGH

JAVA SSL and Profile Parameter


Add profile parameter to java SCS profile


ms/server_port_1 = PROT=HTTPS,PORT=444$$

Navigate to \usr\sap\<SID>\J<XX>\sec. Create an empty text file and save it as ticket (no extension). That's it. Without this, SSL will not function.

For more information follow link

Copy SAPSSLS.pse and ticket file from java instance and paste in to SCS instance sec directory

SAP Help links

https://help.sap.com/saphelp_nw74/helpdata/en/a2/f9d7fed2adc340ab462ae159d19509/frameset.htm

https://help.sap.com/saphelp_nw74/helpdata/en/09/392712944fc6478c9f1ff198b6b0a7/content.htm?frameset...

Open SSL login to to NWA

You will be seen as below

Configure pors as below

UME

Login to NWA and open Configuration >> Infrastructure >> Destinations

Change RFC Destination UMEBackendConnection to SAP ABAP client 300 from 001

UME configuration completed.


SAP Roles

Create Java role

1776467 - Step 'Maintain Users' shows error 'User <user_name> is not allowed to perform this request. Check SAP Note 1647157'

1647157 - How to Set up Access to the SPML Service on AS Java

Assign this role to J2EE_ADMIN user

Restart SAP systems (ABAP + JAVA)

You will see access points as below for your system

Now you have system ready for  SAP Support Pack correction Notes 03 SPS

Thank you for reading

Yogesh

29 Comments
Labels in this area