How to Change the Enterprise Name

Let’s say you don’t like the way a consultant named the Siebel Enterprise. Well, fortunately, he was kind enough to leave you instructions on how to rename it. These instructions are not for the faint of heart. You should really know what your doing or you can seriously foul things up. Follow these steps.

1. Backup the ADMIN directory on the gateway.

2. Leave all Siebel Application and Gateway Services running everywhere.

3. Stop the Web Server

4. Log into one of the application servers

5. Start a command window

6. Move to the BIN directory in siebsrvr

7. Remove ALL servers from the Enterprise by repeating the following command for each server:

a. srvredit –g HOSTNAME_OF_GATEWAY –e NAME_OF_THE_SIEBEL_ENTERPRISE –s NAME_OF_SERVER_TO_REMOVE –x $server

i. –x $server tells the srvredit program to remove the server

ii. example: this was run in dev to remove the Siebel Application Server named “vccssdev”:

srvredit –g sw75dgccsw03 –e vccssdev –s vccssdev –x $server

8. Remove the Enterprise with srvredit

a. srvredit –g sw75dgccsw03 –e vccssdev –x $Enterprise

i. notice how no server name is passed in

ii. notice how “x” is literally “$Enterprise”

9. Restart the Gateway Server

10. Look at siebns.dat and notice how it is empty

11. Stop all Siebel Servers

12. Remove the DSN (ODBC) on each Application Server.

13. Remove the Service entry for the “dead” server service in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SiebSrvr_siebel_SiebSrvrname

14. Reboot each Siebel Server

15. Now run StartàProgramsàSiebel Enterprise Server ConfigurationàSiebel Server Configuration.

16. Use the Wizard to configure all your Siebel Servers and name a new Enterprise in the process.

17. Be sure to update any Siebel Dedicated Client .cfg files. Search and replace the Enterprise Name but do not replace any ODBC names (which have the old enterprise name in it) without also updating the ODBC entry for your Client, too.

18. Log in with the thick client and validate things. If you got some errors during Server Confg you can see with the thick client what needs to be fixed. A lot of time you need to grab the ODBC that is in Administration-Server ConfigurationàServersàServer Parameters for the ODBC Data Source and make it on each Server since this is usually the one piece that bombs.

19. Bounce the enterprise.

20. Run the Web Server Config on web servers or just search replace the enterprise name in the eapps.cfg files.

21. Restart Web Servers