WebSphere Install
I did a silent install of IHS 2.0.42 this morning. A few tweaks to the config and newton’s back on line. I’m trying the base silent install then will do the ND silent install. Scripting global security is the next big thing.
Base install took 24 minutes and installed the 1.3.26 admin service. It added plug-in lines tot he conf but left it the same otherwise.. IHS wouldn’t start:
The Apache service named reported the following error:
>>> API module structure `ibm_app_server_http_module’ in file C:/WebSphere/AppServer/bin/mod_ibm_app_server_http.dll is garbled - perhaps this is not an Apache module DSO?
With Kali’s input, I changed the LoadModule line to:
LoadModule was_ap20_module “C:\WebSphere\AppServer/bin/mod_was_ap20_http.dll”which worked nicely. The last configuration error was in the port directive inserted by the WAS install:
The Apache service named reported the following error:
>>> Port was replaced with Listen in Apache 2.0
I removed the Port directive installed by WebSphere and the server started up fine (except the drive’s going nuts). On service stop apache GP faulted whe a memory write error. Interesting. It turns out that the http_plugin.log is full of these:
[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError
[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError
[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError
[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError
[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError
[Tue Oct 07 13:46:57 2003] [error] AfpaSockAcceptError
So maybe I need to turn the AFPA back on? Yes, that got it going. Here are the lines I uncommented:
#AfpaEnable
#AfpaCache on
AfpaPort 80
#AfpaLogFile “c:/WebSphere/IBMHTTPServer/logs/afpalog” V-ECLF
ND install took just over 28 minutes. netstat shows these ports:
TCP newton:8100 newton:0 LISTENING - cell ORB bootstrap
TCP newton:8101 newton:0 LISTENING - cell SOAP
TCP newton:8109 newton:0 LISTENING - cell discovery
TCP newton:8112 newton:0 LISTENING - cell http 2 (admin)
TCP newton:8113 newton:0 LISTENING - cell https 2
TCP newton:8114 newton:0 LISTENING - cell ORB listener
TCP newton:8120 newton:0 LISTENING - app bootstrap
TCP newton:8121 newton:0 LISTENING - app SOAP
TCP newton:8130 newton:0 LISTENING - app http 1
TCP newton:8131 newton:0 LISTENING - app https 1
TCP newton:8132 newton:0 LISTENING - app https 2 (admin)
TCP newton:8133 newton:0 LISTENING - app https 2
which seems to indicate that the customization worked. So, it’s time to federate. addNode dumps this out:
Usage: addNode cell_host [cell_port] [-conntype] [-includeapps]
[-startingport] [-noagent] [-quiet] [-nowait] [-logfile
] [-replacelog] [-trace] [-username ] [-password
] [-help]
So it’s off to the infocenter: http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp where we find this writeup:
http://publib.boulder.ibm.com/infocenter/wasinfo/topic/com.ibm.websphere.base.doc/info/aes/ae/rxml_addnode.html?resultof=%22%61%64%64%4e%6f%64%65%22%20%22%61%64%64%6e%6f%64%22%20