Disabling HTTPS communication between IHS WAS Plugin and WAS servers
Many people believe that you have to have multiple servers to run IBM Connections - this simply isn't true! There's no reason why you cannot run everything of the same server which is what we do here at the office. When you do that, if all servers are inside the firewall - or if you simply doesn't care about the security that it provides - you can disable the IHS WAS Plugin from communicating with the WAS server using SSL. A benefit from this is among other things that you do not have to care about certificates between the IHS WAS Plugin and the WAS server which simplifies installation and management.
Any way... For a while I've doing this configuration change manually directly in plugin-cfg.xml (by commenting the HTTPS transport out) until it bit us the other day. So I finally decided to find a proper, correct, solution. And of course there is a way to do this and it's very well documented in IBM Technote 1452735. So if you want to make that change go ahead and do it - I did and it's working flawlessly.
Re: Disabling HTTPS communication between IHS WAS Plugin and WAS servers
We are thinking about a Core i7-920 quad core, 24 GB RAM, 2x3 TB SATA 6 GB/s HDD, which would also run a Domino 8.5.3, preferably virtualized with VMWare ESXi.
Does this make sense or do you think it would get too slow (maybe the HDD could be a bottleneck)?
Re: Disabling HTTPS communication between IHS WAS Plugin and WAS servers
Re: Disabling HTTPS communication between IHS WAS Plugin and WAS servers
I have just installed Connections 3.0.1 for a testing environment (about 20 - 30 users)... Everthing on 1 VirtualServer:
QuadCore, 8GB RAM, 120GB (just C:\) on a SAN
I'am using a productive Domino for LDAP... The performance is surprisingly really good! But for a productive environment, I would separating at least: Connections (one server), DB2 (one server) and LDAP (one server) --> 3 Servers