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, lets get to work!Here is the list of prerequisites and tools I have used:
- Good text editor (UltraEdit or Notepad++). If you do not own UltraEdit you can buy one for about $50 (http://www.ultraedit.com) and I am personally consider on the best investment I have ever made
If you are on the budget, then the Notepad++ (http://notepad-plus.sourceforge.net) is the great choice and it is free.
- SAP ESA Discovery Installation Guide (http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b22d4e44-0e01-0010-ffa4-fe9c...)
- SAP Offline Config Tool located in: D:usrsapERPDVEBMGS10j2eeconfigtoolconfigtool.bat
- Make sure you are comfortable with Windows Registry and have admin rights on the server
- Adobe Acrobat Reader, Java SDK v. 1.4.2_08, (http://java.sun.com/products/archive/j2se/1.4.2_08/index.html) , Adobe Flash Player, and Adobe SVG Viewer
- Server Backup!
Now, the list of pre-requisites is complete lets do some real work! We will change servers 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!
- Complete OS install of your server. Login as administrator (admins password can be found on page 6 of Install Guide) and change name of the server to whatever your corporate standard is. Reboot server.
- Follow instructions in ESA Discovery Installation Guide from page 6 through page 15.
- DO NOT REQUEST LICENSE KEY JUST YET!
- Make sure SAP instance is down via SAP Management Console on the Desktop
- Stop SAP Services (SAPERP_00, SAPERP_10, and SAPOsCol)
- Rename J2EE profile files (see image below):
- Open all of the files in Text Editor, then search and replace IWDFVM2160 to SACORT04. Save Files
- Go to Registry Editor and open Hive HKEY_LOCAL_MACHINE -> CurrentControlSet ->Services
- Navigate to Key SAPERP_10
- Choose ImagePath
- Edit pfvalue of ImagePath as follows:
- Click OK
- Go to Key SAPERP_00.
- Repeat Step 10.
- Edit pf value of ImagePath as follows:
- Go to Registry Editor and open Hive HKEY_LOCAL_MACHINE -> ControlSet001 ->Services
- Repeat Steps 9 - 15.
- Go to Registry Editor and open Hive HKEY_LOCAL_MACHINE -> ControlSet002 ->Services
- Repeat Steps 9 15.
- Reboot Server
- Make sure ERP instance is NOT started
- Open Config Tool. When prompted to load default DB Connections settings choose NO.
- Modify Connection Screen as follows (sas password is same as PISUPER):
- Click Load.
- Change reference to IWDFVM2160 to SACORT04:
- Global Dispatcher Configuration:
- ClusterManager ms.host
- LockingManager enq.profile.name; enqu.host
- Global Server Configuration:
- ClusterManager ms.host
- LockingManager enq.profile.name; enqu.host
- Instance_ID1039293
- Message Server Host
- Dispatcher_ID1039293
- ConfigurationManger secstorefs.keyfile; secstorefs.lib; secstorefs.secfile
- Server_ID1039293
- ConfigurationManger secstorefs.keyfile; secstorefs.lib; secstorefs.secfile
- Secure Store
- admin/host/ERP sacort04
- jdbc/pool/ERP/Url - jdbc:nwmss:sqlserver://sacort04:1433;databasename=ERP
- Hit Save.
- Start ERP Instance via SAP Management Console.
- Continue with the ESA Discovery Installation Guide from page 16.
This is it folks!