When Voyager server IP address is changed, which files must be updated?
Question
When the IP address of a Voyager server is changed, which files need to be updated with the new IP address?
Answer
Files which may require updating if the Voyager Server IP is changed are listed below. Some files may not exist on some systems, and can therefore be ignored.
OS
- /etc/hosts
- /etc/networks
- /etc/defaultrouter
- /etc/netmasks
- /etc/resolv.conf
Apache
- /m1/shared/apache2/conf/httpd.conf
- /m1/shared/apache2/conf/ConfiguredVirtualHosts/*.conf
Oracle
- $ORA_NET/tnsnames.ora
- $ORA_NET/listener.ora
- $ORA_NET/sqlnet.ora
Voyager
- /m1/voyager/XXXdb/ini/voyager.ini
- /m1/voyager/XXXdb/ini/voyager.env
- /m1/voyager/XXXdb/ini/[client]svr.ini
- /m1/voyager/XXXdb/etc/webvoyage/header.htm
- /m1/voyager/XXXdb/etc/webvoyage/voyager.ini
- /m1/voyager/XXXdb/etc/ascopac/opac.ini file
- /m1/voyager/XXXdb/webvoyage/html/webvoy.htm
Tomcat WebVoyage
- /m1/voyager/voydb/tomcat/vwebv/context/vwebv/WEB-INF/web.xml
- /m1/voyager/voydb/tomcat/conf/server.xml
Additional Files
There may be additional files on the system which will need to be updated. Most often these will include:
- Custom WebVoyage skin files, help pages, or landing pages
- Third party software configurations
- Custom scripts
To aid in finding such files the following commands will locate files that contain IP information:
- grep -rl "<ip address>" ./*
- find . -type f -print | xargs grep <ip address>
- find . -type f -print | xargs grep -l <ip address>
DNS
Update the DNS server with the new IP address. A and PTR records should be updated to allow for both lookup and reverse lookup.
Article last edited: 19-Apr-2016