mixing manual edits and CLI's with web server 7
With Web Server 7, if you manually edit the configuration files like magnus.conf, obj.conf or server.xml for common server administration tasks, then you will need to pull your manual edit's into administration server's internal repository. Here is a brief snippet on how to get this done.
For e.g, let us assume that you have installed your Web Server 7 under 'opt/ws7' directory. Now, if you had to manually edit the Sun Java System Web Server's configuration file (like magnus.conf or obj.conf) to configure a 3rd party plugin like Web Logic, Web Sphere or SiteMinder , then you will need to do the following to start using our CLI
- First, let us fire the Web Server 7 Administration Server by doing something like
/opt/ws7/admin-server/bin/startserv
- Now, let us inform our Web Server 7 Administration Server that we have manually made some changes to our configuration files and he needs to update his internal repository.
/opt/ws7/bin/wadm pull-config --user admin --port 8989 (or whatever the administration port that you have configured) --config=CONFIGNAME HOSTNAME.DOMAINAME
where CONFIGNAME will usually be the hostname of your machine.
HOSTNAME - hostname of your machine
DOMAINNAME - your current domainname.
for eg, I would do something like
/opt/ws7/bin/wadm pull-config --user admin --port 8989 --config=mcfly.sun.com mcfly.sun.com
Without running this above command, you won't be able to make any web server administration via CLI . This is because , Web Server 7 Administration Server internally computes the difference between its internal repository and the server instance's (https-CONFIGNAME) configuration files. If these two are different, we expect users to manually run the above command.
Hope this helps
For e.g, let us assume that you have installed your Web Server 7 under 'opt/ws7' directory. Now, if you had to manually edit the Sun Java System Web Server's configuration file (like magnus.conf or obj.conf) to configure a 3rd party plugin like Web Logic, Web Sphere or SiteMinder , then you will need to do the following to start using our CLI
- First, let us fire the Web Server 7 Administration Server by doing something like
/opt/ws7/admin-server/bin/startserv
- Now, let us inform our Web Server 7 Administration Server that we have manually made some changes to our configuration files and he needs to update his internal repository.
/opt/ws7/bin/wadm pull-config --user admin --port 8989 (or whatever the administration port that you have configured) --config=CONFIGNAME HOSTNAME.DOMAINAME
where CONFIGNAME will usually be the hostname of your machine.
HOSTNAME - hostname of your machine
DOMAINNAME - your current domainname.
for eg, I would do something like
/opt/ws7/bin/wadm pull-config --user admin --port 8989 --config=mcfly.sun.com mcfly.sun.com
Without running this above command, you won't be able to make any web server administration via CLI . This is because , Web Server 7 Administration Server internally computes the difference between its internal repository and the server instance's (https-CONFIGNAME) configuration files. If these two are different, we expect users to manually run the above command.
Hope this helps
