Skip to Content

In the midst of MDM work and NW upgrade I finally have time to work on my lab. My lab consists of four Enterprise SOA Discovery servers. Once I started setting up my lab I notice that all DS are sharing same hostname. Most of you seem to have similar problem and this is an attempt to correct this oversights. In the nutshell, same hostname on multiple servers’ means, that only one server can exist at any given time on the LAN segment. So without further due I will begin this whitepaper with a word of caution and some prerequisites. Also, this whitepaper will only show how to change computer hostname, and does not go in the details of changing SAP system ID (SID). In order not to turn this whitepaper into full blown install guide I will make assumption that reader is intermediate to advance level and I will omit some obvious steps such as hit OK or SET…

CAUTION: “These instructions are not for the faint-hearted and full backup is highly recommended!”

Anyway, let’s get to work!Here is the list of prerequisites and tools I have used:

  1. Good text editor (UltraEdit or Notepad++). If you do not own UltraEdit you can buy one for about $50 ( and I am personally consider on the best investment I have ever made… If you are on the budget, then the Notepad++ ( is the great choice and it is free.
  2. SAP ESA Discovery Installation Guide (
  3. SAP Offline Config Tool – located in: D:usrsapERPDVEBMGS10j2eeconfigtoolconfigtool.bat
  4. Make sure you are comfortable with Windows Registry and have admin rights on the server
  5. Adobe Acrobat Reader, Java SDK v. 1.4.2_08, ( , Adobe Flash Player, and Adobe SVG Viewer
  6. Server Backup!

Now, the list of pre-requisites is complete lets do some real work! We will change server’s host name from iwdfvm2160 to sacort04. Please make appropriate substitutions for your host name. I would highly recommend reading Installation Guide before hands on work!

  1. Complete OS install of your server. Login as administrator (admin’s password can be found on page 6 of Install Guide) and change name of the server to whatever your corporate standard is. Reboot server.
  2. Follow instructions in ESA Discovery Installation Guide from page 6 through page 15.
  4. Make sure SAP instance is down via “SAP Management Console” on the Desktop
  5. Stop SAP Services (SAPERP_00, SAPERP_10, and SAPOsCol)
  6. Rename J2EE profile files (see image below):
  1. Open all of the files in Text Editor, then search and replace IWDFVM2160 to SACORT04. Save Files
  2. Go to Registry Editor and open Hive HKEY_LOCAL_MACHINE -> CurrentControlSet ->Services
  3. Navigate to Key “SAPERP_10”
  4. Choose “ImagePath”
  5. Edit “pf”value of “ImagePath” as follows:
  6. Click OK
  7. Go to Key “SAPERP_00”.
  8. Repeat Step 10.
  9. Edit “pf” value of “ImagePath” as follows:
  10. Go to Registry Editor and open Hive HKEY_LOCAL_MACHINE -> ControlSet001 ->Services
  11. Repeat Steps 9 – 15.
  12. Go to Registry Editor and open Hive HKEY_LOCAL_MACHINE -> ControlSet002 ->Services
  13. Repeat Steps 9 – 15.
  14. Reboot Server
  15. Make sure ERP instance is NOT started
  16. Open Config Tool. When prompted to load default DB Connections settings choose “NO”.
  1. Modify Connection Screen as follows (sa’s password is same as PISUPER):
  2. Click Load.
  3. Change reference to IWDFVM2160 to SACORT04:
    1. Global Dispatcher Configuration:
      1. ClusterManager –
      2. LockingManager –;
  1. Global Server Configuration:
    1. ClusterManager –
    2. LockingManager –;
  1. Instance_ID1039293
    1. Message Server Host
  1. Dispatcher_ID1039293
    1. ConfigurationManger – secstorefs.keyfile; secstorefs.lib; secstorefs.secfile
  1. Server_ID1039293
    1. ConfigurationManger – secstorefs.keyfile; secstorefs.lib; secstorefs.secfile
  1. Secure Store
    1. admin/host/ERP – sacort04
    2. jdbc/pool/ERP/Url – jdbc:nwmss:sqlserver://sacort04:1433;databasename=ERP
  1. Hit Save.
  2. Start ERP Instance via “SAP Management Console”.
  3. Continue with the ESA Discovery Installation Guide from page 16.

This is it folks!

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member

    we changed the host name of our discovery system, but there is an issue when testing following scenario

    When i log in the portal with EBPP_Admin/sap123 the page in the main part doesn´t appear. I get an error:

    Unable to determine IP address from host name for

    This is not our host name, where does the portal get this host name from? I checked and changed all rfc connections, any ideas?

    – How can i solve this problem ? –

    Best regards,


    1. Former Member Post author
      Here are few suggestions, main portal login page does appear and you can login to a portal for any other scenario. If that is the case then, you need to check your service alias via EP Admin Console. Now, if you do not even get EP login screen then you have a problem with JAVA engine config… Let me know if this solved your problem…

      Sincerely, Max Efimov


Leave a Reply