SAP: setting up a new Virtual System & Transport Layer in STMS

In this post I would like to tackle the subject of setting up a new Virtual System in an NetWeaver SAP instance.  For the purpose of this discussion I will be using a standard SAP EHP 2 for SAP NetWeaver 7.0 demo system.

System Access

The first thing we need to do is gain access to the configuration client 000.  I am using SAP* master user account to make all the system changes in client 000.  Also note that to make things simple I am using a NSP system in my examples below – you might have a different system so please adjust your configurations accordingly.

Setting up the RFC destination

When going through the steps for setting up a new Virtual System I ran in to a few issues that resulted in a bit of a detour – below I will describe the issues that I’ve faced and how I went about solving those problems.

Changing the password of TMSADM user for TMSADM@NSP.DOMAIN_NSP RFC destination

When examining the TMSADM@NSP.DOMAIN_NSP RFC destination I’ve noticed that the PW Status was set to incorrect.  The fix is not as trivial as changing the SU01 information for the designated user:

    1. Transaction SE38
    2. Execute program TMS_UPDATE_PWD_OF_TMSADM
    3. Populate a new password and execute the command

Error Details RFC error when sending logon data.

I’ve only noticed that the password for the TMSADM user was incorrect because of this error.  When I executed the program TMS_UPDATE_PWD_OF_TMSADM I noticed a few error messages related to the inability to connect to the system.

An attempt to manually re-create TMSADM@NSP.DOMAIN_NSP RFC destination did not work.

An attempt to delete and re-generate the TMSADM@NSP.DOMAIN_NSP RFC destination via Transaction STMS did not work.  But here are the steps:

    1. Transaction SM59
    2. Highlight the TMSADM@NSP.DOMAIN_NSP RFC destination and click the Garbage Can button
    3. Transaction STMS
    4. Select: Overview – Systems
    5. Highlight the NSP system
    6. Select: Extras – Generate RFC Destination

An attempt to manually create Z<SID> RFC destination pointing to the current system and using a different user/password did not work.

An attempt to remove errored SECSTORE records did the trick. And here are the steps:

    1. Transaction SECSTORE
    2. Click Execute button
    3. Expand [if not already] the following tree: Secure Storage – ___ Client-Independent – Others
    4. I had two entries here both of which were flagged in red
      1. /HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM
      2. /HMAC_INDEP/RFC_INTERNAL_TICKET_4_TRUSTED_SYSTEM
    5. Call transaction SM37
    6. Run function module RFC_PING with a target
    7. The forums on-line suggest that this action [if not successful the first time] should be executed twice
    8. Transaction SECSTORE
    9. Note that the two deleted nodes in step 4 are now recreated and are in Green status
    10. Transaction SM59
    11. Test the TMSADM@NSP.DOMAIN_NSP destination
    12. Done

 

Creating a new Virtual System

Steps taken above resulted as a troubleshooting effort to the actions described below.

  1. Transaction STMS
  2. Select: Overview – Systems
  3. Select: SAP System – Create – Virtual System
  4. Specify the name and short description
  5. Click Save
  6. Go back to Transaction STMS
  7. Select: Overview – Transport Routes
  8. Select Edit Mode
  9. Drag both systems in to the window and double click on the development system to activate the generation of the Transport Layer
  10. I’ve crated a basic DEV – PRD system on my development box

That’s about it.  Hope this was helpful.

Leave a Reply

*

captcha *