Skip to Content
Technical Articles

Solution Manager 7.2 SP 08 Upgrade and Migration Using SUM DMO Approach – IV – Post Steps – ABAP Stack

Solution Manager 7.2 SP 08 Upgrade and Migration Using SUM DMO Approach – IV – Post Steps – ABAP Stack

 

In this blog I will go through the post steps performed after the completion of Solution Manager 7.2 upgrade for ABAP stack.

Post Steps

->1.Make sure SPAU changes are completed within 14days

To ease the configuration process, common configuration steps are provided as an automated task list for the ABAP task manager. This task list provides the automated creation of the necessary connections to the support backbone. To leverage the automation, please implement SAP Note 2738426

->2.Automated Configuration Of New Support Backbone Communication

SAP Note 2738426 – Automated Configuration of new Support Backbone Communication

For every affected area, various activities have to be performed (as listed on this page).

To ease the configuration process, common configuration steps are provided as an automated task list for the ABAP task manager. This task list provides the automated creation of the necessary connections to the support backbone. To leverage the automation, please implement SAP Note 2738426.

  • As per the note 2738426,Implement TCI with transaction SNOTE
  • Check with transaction SPAM that version is minimum level 70
  • Download the TCI Note and the corresponding TCI SAR archive for the software component version that is appropriate for your system (Scroll to Correction Instructions and click on SAP_BASIS, select the release and use download link)

click on SAP_BASIS, select the release and use download link

Click Download, it downloads file K74000VCPSAPBASIS.SAR

Upload the TCI SAR archive on the system. (Transaction SNOTE > Goto > Upload TCI)

Upload/Download the TCI Note on the system. (Transaction SNOTE > Goto > Upload SAP Note or Download SAP Note)

  • Implement the TCI Note. (Transaction SNOTE > select the TCI Note > Implement SAP Note- 2738426)
  • (For details check KBA 2543372 – How to implement a Transport-based Correction Instruction and SAP Note 2187425 – Information about SAP Note Transport based Correction Instructions (TCI) ).

3.Now execute the task list SAP_BASIS_CONFIG_OSS_COMM

Here, if you click on change parameter, we can select whether it want to check SSL Client(Standard) or to check SSL Client(Anonymous)

Download Baltimore CyberTrust Root certificate from below link

https://www.digicert.com/digicert-root-certificates.htm

Click Fill parameters button for task Certificate For SSL Client(STRUST)

For next step Create HTTPS Connections for SAP Services (SM59)’, fill parameters

Make sure you have technical communication user in place, please follow below note

2174416 – Creation and activation of users in the Technical Communication User application

After filling parameters, click SAVE and come back

Now run the task list SAP_BASIS_CONFIG_OSS_COMM

Make sure below RFC destinations are working properly.

  • SAP-SUPPORT_NOTE_DOWNLOAD

 

  • SAP-SUPPORT_PARCELBOX

2716729 – SAP backbone connectivity – SAP Parcel Box configuration

  • Perform a connection test
    • In tab “Test Result”
      • In field “Status HTTP Response” the value “200” must be shown

  • SAP-SUPPORT_PORTAL

  • Click on the documentation icon of each task for additional infos and troubleshooting help
  • Connection test returns http code 0: make sure that https port for system is configured
  • The task list performs an connection test for the connections SAP-SUPPORT_PORTAL (ping) and SAP-SUPPORT_PARCELBOX (ping & authorization). If both are ok, also the connection SAP-SUPPORT_NOTE_DOWNLOAD is ok.

4. Next Configure task list – SAP_SUPPORT_HUB_CONFIG

Confirm the first task

In my case Solman system is already on version 7.2 SPS 04, hence I skipped the step – Request&Activate Support Hub User, if you want to create please follow below note

2174416 – Creation and activation of users in the Technical Communication User application

Confirm

Go to Transaction STRUST and make sure that PSE “SSL client SSL Client (Anonymous)” exists and contains “VeriSign Class 3 Public Primary Certification Authority – G5” Certificate. If not, you may download it as described in KBA 2631190 , as per note 2631190 , need to have below certificates in solman system-SMD

  • Please populate the profile parameter ssl/client_ciphersuites accordingly, including the activation of TLSv1.1 and TLSv1.2 which will be used for outgoing https connections.  Our recommendation for this parameter on Solution Manager 7.2 only is: 918:PFS:HIGH::EC_P256:EC_HIGH(this activates protocol version TLS1.0, TLS1.1, TLS1.2 and is functionally equivalent to the recommended value  150:PFS:HIGH::EC_P256:EC_HIGH  in section 7 of note 510007  for CommonCryptoLib 8.4.31 and newer ).
  • After the setting of this parameter, restart the SAP Solution Manager system. For more information, such as how to deactivate or activate certain protocol versions and cipher suits, please look for SAP Note 510007 – setting up SSL on Application Server ABAP parameter.

  • When you click save button it gives error, so I manually  created service user BGRFC_SUSR with role SAP_BC_BGRFC_SUPERVISOR in  the solman system and also the RFC destination BGRFC_SUPERVISOR with user BGRFC_SUSR

Tcode – SRT_ADMIN

Always productive client is the existing client

Click Schedule, both the jobs will get scheduled in the system.

To resolve above error for Task Watcher and Supervisor destination

For Task Watcher, again Run the steps again in SLM client 000

  1. Open transaction srt_admin
  2. Select radio button “Check Technical Settings”
  3. Execute
  4. Select client 000
  5. Execute

For above error Supervisor Destination, make sure RFC destination – bgRFC is working

After that once again execute the above steps on the solman system , it resolves

Confirm tasks manually and run the task list

5.The last step of support hub connectivity is to perform the step 3.2 of System preparation

Click Execute All

 

->6.Execute t-code – SGEN, depending upon the components in the system, it will generate all objects and the background job RSPARAGENER8M will be executed in background.

->7.Please cross check whether all jobs are in Released status or not from t-code SM37

  • If you find multiple jobs in suspended status, in that case execute the report BTCTRNS2

->8.Check t-code SMICM , all services should be active as shown below

If you find services inactive, please perform below checks

  • Check the permission of file icmbnd (it should be like -rwsr-x—)
  • If you find issues with permission of file icmbnd , rerun  script saproot.sh

->9.T-code- SLICENSE-After completion of upgrade, Initial temporary license is added by default.
Make sure permanent license is updated.

->10.If you have CUA configured on the system, make sure all child systems are properly connected to Parent system.

->11. DBACOCKPIT -Maintain database connections

  • Create user for database backups with privileges-System admin,catalog read and database admin which will used to schedule backups in tcode- DB13

->12.Go to tcode- DB13 and you can schedule backups for SystemDB  and tenant DB

SYSTEMDB

Tenant DB

->13.After upgrade when you run t-code /nsolman_setup , it will ask to activate webdynpro services

It will take  several seconds to activate and then it will get opened.

->14.After upgrading SAP Solution Manager 720 SP08

  • In SOLMAN_SETUP -> Infrastructure Preparation scenario -> Step2.2 ‘Enable Connectivity’ -> Activity ‘Check Java Software Prerequisites’, this note corrects check for ISAGENT_MIN_J5 component.
  • There is a program error , to resolve it implement note 2739682 – Activity ‘Check Java Software Prerequisites’

-> 15.After upgrading to Solution Manager 7.2 SP 07 or SP 08,you cannot access on any application using the Scope Selection functionality because of the following error message:

->16.If suppose table logging was enabled in the system, again after upgrade we need to disable table logging by following note

2341818 – Disable Logging for several objects as of SAP_BASIS 740 and following releases

  • Implement the steps 1 to 3 as per the note 2341818 then proceed with step4
  • Run report ZSLA_CREATE_DATAFILE_LOGGING_1 in transaction SE38
    If you want to process all rows at once, do not change the default value 60.000.
    In case you want to split the processing into several parts, enter PACKSIZE 10.000 or 5.000 for example.
    Reducing the PACKSIZE can be necessary, if time frame for batch input processing is too small. Batch Input Processing of all rows at once, takes about 3 hours.
  • F8
  • 1. Run report ZSLA_SE13_06_AS_OF_740 in transaction SE38
    Tick radio-button Generate Session
    Enter any session name in field Session name
    Enter TABLES_WITH_PROTOKOL_x in field DATASET (x represents the sequential number of the file: 1,2,n)
  • Execute the report with icon Execute ,If the list of transactions is displayed proceed with point 2.

 

  • 2. Start transaction SM35
    Select the session with the Session name you entered above.
  • Press button Process
  • In screen Process Session choose radio-button Background in frame Processing Mode
    Press button Process
  • Now you can monitor the process in transaction SM37,Once the job has status Finished, this task is done.
  • Repeat step 1 and 2 one after the other for all files TABLES_WITH_PROTOKOL_1, TABLES_WITH_PROTOKOL_2, TABLES_WITH_PROTOKOL_n,

Se38 , execute report – ZSLA_SE13_06_AS_OF_740 with session name .

For example I gave session name as DISABLELOG

Execute, the list of transactions is displayed as shown below

Now start transaction SM35
Select the session with the Session name you entered above.
Press button Process
In screen Process Session choose radio-button Background in frame Processing Mode
Press button Process

Select session and click Process,now you can monitor the process in transaction SM37

once the job is finished,again go to tcode-sm35

From above screenshot,out of 1137, 153 tables went into error,

In order to find the list of these 153 tables, go to SE38 and give program name – RSTBHIST and click List Of Logged Tables button,  it will list out table names for which log data changes didn’t took place.

You can manually check tables using t code se13

  1. Start transaction SE13
  2. Enter the object within field Table/view name

When I try to change table manually , it gave me a popup saying that the objects are locked in the respective transports.

I released the respective transport and again Repeat the step 1 and 2 one after the other for the remaining 153 tables

->17.After Solution Manager 7.2  SPS 08 upgrade,again need to perform end to end Mandatory Configurations in t-code SOLMAN_SETUP

  • System Preparation
  • Infrastructure Preparation
  • Basic Configuration

->18.If you are using TREX Embedded Search with the option type = ESH, after migrating to Hana database, you can stop the Trex instance and perform the new Embedded Search Configuration for Hana database.

Troubleshooting Information for Additional Post-Upgrade Activities

In the next blog,I have explained in detail How to configure Enterprise Search Configuration from TREX to Hana database.please find the below link for the same.

Solution Manager 7.2 SP 08 Upgrade – Enterprise Search Configuration from TREX to SAP HANA – V – ABAP Stack

Be the first to leave a comment
You must be Logged on to comment or reply to a post.