http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/cins_webserver.html
Note that you cannot add a webserver with the admin web interface, you need to use the command line.
Essentially this task is performed from the plugins install dir. There is a facilitating script there called configurewebserver1.bat.
The webserver might not have been installed properly because of pathing. If you install WAS and then reboot and then do HTTP server and plugins it might work.
This script calls a couple of files that might need to have a path modified. Please see my edits below:
D:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\wsadmin.bat -f D:\IBM\WebSphere\AppServer\bin\configureWebserverDefinition.jacl webserver1 IHS "D:\\IBM\\IBMHTTPServer" "D:\\IBM\\IBMHTTPServer\\conf\\httpd.conf" 80 MAP_ALL "D:\\IBM\\WebSphere\\Plugins" unmanaged nsgshsjdnsp02u.XXXX.local nsgshsjdnsp02u.XXXX.local windows
From above, I had to path the wsadmin.bat file and the configureWebServerDefinition.jacl file.
Note that this is a 25K file, you don't wanna create one of these yourself!!
Output of the script looks like the following:
Start computing the cell Type.
StandAlone profile found.
Input parameters:
Web server name - webserver1
Web server type - IHS
Web server install location - D:\IBM\IBMHTTPServer
Web server config location - D:\IBM\IBMHTTPServer\conf\httpd.conf
Web server port - 80
Map Applications - MAP_ALL
Plugin install location - D:\IBM\WebSphere\Plugins
Web server node type - unmanaged
Web server node name - webserver1_node
Web server host name - nsgshsjdnsp02u.XXX.local
Web server operating system - windows
Creating the unmanaged node webserver1_node .
Unmanged node webserver1_node is created.
Creating the web server definition for webserver1.
Parameters for administering IHS web server should be updated using wsadmin scri
pt or admin console.
Web server definition for webserver1 is created.
Start computing the plugin properties ID.
Plugin properties ID is computed.
Start updating the plugin install location.
Plugin install location is updated.
Start updating the plugin log file location.
Plugin log file location is updated.
Start saving the configuration.
Configuration save is complete.
Computed the list of installed applications.
Processing the application DefaultApplication.
Get the current target mapping for the applictaion DefaultApplication.
Computed the current target mapping for the application DefaultApplication.
Start updating the target mappings for the application DefaultApplication.
Target mapping is updated for the application DefaultApplication.
Processing the application ivtApp.
Get the current target mapping for the applictaion ivtApp.
Computed the current target mapping for the application ivtApp.
Start updating the target mappings for the application ivtApp.
Target mapping is updated for the application ivtApp.
Processing the application query.
Get the current target mapping for the applictaion query.
Computed the current target mapping for the application query.
Start updating the target mappings for the application query.
Target mapping is updated for the application query.
Start saving the configuration.
Configuration save is complete.
D:\IBM\WebSphere\Plugins\bin>
I love blogging about new technology appropriate for the enterprise. I want to change the face of innovation to embrace change, agility and promote an innovation culture.
Subscribe to:
Post Comments (Atom)
-
There are a heap of instructions of what you need to change if you change the IP address of your weblogic server, but I find they are not co...
-
They have been around for quite some time, but it's nice to have a refresher on these types of things. 8.12 and 9.0 have have started...
-
I’m running windows 7 virtual on OVM with office 2010. Have E1 fat boy and oracle 11G client. I’m using this machine for some BIP prototyp...
No comments:
Post a Comment