Installing WAS at one IP then changing to another.

[misercord]

When we installed WAS 3.5.5 the machine was at a given ip address. Everything was configured and tested fine. Then the IP of the machine was changed. Apache error log now report not able to find the directory where the servlets are found. It doesn't use the virtual host path but instead uses the document path. We were told by IBM to regenerate the plugins. This has not solved the problem. Has anyone had this problem and solved it with out re-installing WAS?

 

[Einstein47]

I remember something about Websphere uses the IP address for registering information in the WAS repository. The article (in the WebSphere InfoCenter on the IBM web site) gave the SQL that you need to run to update the repository to know what the new IP is.

Sorry I don't have it right at hand. If I come across it, I'll re-post. Einstein47
(Love is like PI - natural, irrational, endless, and very important.)

 

[misercord]

Searched the IBM site didn't find anything. Do you have anything more specfic?

 

[Einstein47]

I found the article - it was an email that I received. The email was originally sent Jan 2001, but the business rules should be the same.

ADVISOR TIP: WEBSPHERE
How to Change the IP Address of WebSphere Application Server
- IBM WebSphere Application Server 3.5.5+
- IBM AIX 4.3.3+
- IBM DB2 Universal Database 6.1+
============================================================

You might think that the IP address of a computer is not related to the software it runs, but that's not always the case with WebSphere.

If you change the IP address of the machine WebSphere Application Server (WAS) resides on, you have to make the following configuration changes to the admin repository and the WebSphere properties files to make the new IP address work.

1. Connect to the admin repository database, and issue the following SQL statements:

update ejsadmin.bindingbeantbl set name='newIP' where name='oldIP' 
update ejsadmin.bindingbeantbl set name='newHostname' where name='oldHostname' 
update ejsadmin.node_table set name='newHostname' where name='oldHostname'

2. Edit the file sas.server.props, and replace all occurrences of the old hostname with the new hostname. If the file sas.server.props.future isn't empty, you must make the same changes to it.

3. Restart WebSphere Application Server.


Amit Jnagal
IBM
Gaithersburg, Maryland


I hope this helps, Einstein47
(Love is like PI - natural, irrational, endless, and very important.)