WebSphere Reverse Investor: Modifying host names and migrating in WebSphere Application server

WebSphere Reverse Investor: Modifying host names and migrating profiles in WebSphere Application server

In each column, "WebSphere contrarian investors" will answer questions, provide guidance and discuss the underlying topics associated with the use of WebSphere products, often giving proven recommendations that contradict popular perceptions.

Is the time for change coming?

The Greek philosopher Heraclitus once said that "the only thing that remains is change itself", and that this statement has been proven correct over the past 2,500 years, and in some cases you will probably need to modify the hostname on the WebSphere application Server system. There are a number of issues associated with this, which is a common practice. Like how I modify the hostname, migrating a WebSphere application Server profile between different machines means migrating your configuration from one test environment to another. Ideally, you would use Wsadmin to script all the configuration processes, so now you just need to rerun the script with the new hostname. What the? The script is missing? I know there are many users who maintain a very comprehensive script library for this purpose (and perhaps you do), but fortunately, WebSphere application Server v6.x and V7 provide some features that can help you accomplish all of these tasks. (And if you are having trouble upgrading the version of WebSphere application Server to a supported release, I will also give suggestions for modifying the v5.x hostname).

Modify Host Name

Let's begin by modifying the host name on the Deployment Manager machine. The initial configuration is shown in Figure 1, where the Deployment Manager node SONOMACellManager01 is located in the host SONOMA.xd61stew.ibm.com.

Figure 1. Initial configuration

After you stop the Deployment Manager, use the WebSphere application Server Backup tool Backupconfig before making any changes. (Sh/bat) It is always a good idea to back up your configuration, as shown in Listing 1. It's not that you want any errors, but it's always nice to be able to get back to the starting point when something goes wrong.

Listing 1

SONOMA:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin　#
　 ./backupConfig.sh　/root/FullSonomaCellBackup.zip
ADMU0116I:　Tool　information　is　being　logged　in　file
　　　　　　 /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/backupConfig.log
ADMU0128I:　Starting　tool　with　the　Dmgr01　profile
ADMU5001I:　Backing　up　config　directory
　　　　　　 /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config　to　file
　　　　　　 /root/FullSonomaCellBackup.zip
ADMU0505I:　Servers　found　in　configuration:
ADMU0506I:　Server　name:　dmgr
ADMU2010I:　Stopping　all　server　processes　for　node　SONOMACellManager01
ADMU0512I:　Server　dmgr　cannot　be　reached.　It　appears　to　be　stopped.
.....................................................................................
ADMU5002I:　939　files　successfully　backed　up
SONOMA:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin　#