The eServers' interoperability capabilities are particularly valuable since most of the museum's applications are Windows-based. In addition, because the museum's applications are based on different databases (Sybase and SQL Server) and operating systems, as well as different versions of those platforms, each application needs its own server. Dedicating each blade server to a separate application is much more efficient and economical than devoting a Wintel system to each one, says Horio.
The i820 provides file and print services, and an x250 system the museum already had on hand hosts a Citrix application. The x250 is connected to the i820 via the Integrated xSeries Adapter.
The i820 and its integrated blade servers also host a number of specialized applications, such as the TM VISTA online ticketing system, Blackbaud's Raisers Edge fundraising and membership management software, MIP accounting software, a Retail Pro point-of-sale application, Argus asset management software, and Meridian Project Systems's (MPS) building management and maintenance database.
Separate xSeries servers host Cisco CallManager, Cisco Unity, IBM Content Manager, IBM Video Charger, Websense filtering software, and Esker Software's Notes Fax Server.
While IBM won the contract in the end, it wasn't the only server vendor in contention. Horio initially considered going with updated Dell systems, but past problems with the company took it out of the running. "You call Dell up and you can't get any real support," says Horio. "Getting Dell to come out and fix a piece of equipment was also a little slow compared to IBM." In addition, the museum was interested in blade servers, which weren't available from Dell at the time. Finally, since the museum's applications required varying amounts of disk space, underutilization was a problem with some of the old Dell systems. The IBM servers let Horio allocate disk space to applications much more effectively than in the past, he notes.
Despite its sprawling scope, the rollout of the new network was accomplished by only a handful of folks, including the museum's IT staff, three independent contractors, and a team of three KIS employees. Although parts of the implementation process occurred as planned, some unanticipated events resulted in scheduling snafus. The building contractor kept pushing the completion date out, which caused a host of problems. In 2002, the IT staff had moved to the new location, with the expectation that the museum's other employees would soon follow. But due to the construction delays, things didn't go exactly as planned.