A Start-Up is Born

We get hundreds of press releases like this every month at Network Computing, so we couldn't resist announcing our new lab in Green Bay using the same kind of hyperbole. In our case, the company, NWC Inc., is fictional (its products sound great, though, right?). But the IT infrastructure we've been building for this unique application-testing environment is very real. We think our hard work will pay off in helping you and your company make smart application-purchasing decisions.

Network Computing has always tried to make its testing as real-world as possible. With five distributed labs, some collocated on business and university sites, we can build cross-lab tests and do testing on live networks. For example, executive editor Bruce Boardman has performed extensive network-management testing at Syracuse University. However, with the ugly things we do to our test beds, using someone else's network isn't always feasible. In those cases, we set aside equipment for a particular review, configure switches, provision servers with operating systems and applications software, design test beds that include multiple "client" machines or dedicated test equipment, and develop test protocols that we test and deploy. Then that equipment is wiped clean and we start all over again with the next review. This process usually works very well. Over the years we've learned the tricks of the trade when it comes to provisioning equipment with minimal muss or fuss-- critical when deadlines are tight.

But what if we want to test employee portals? Say we're especially interested in seeing how well they work with a company's legacy data, HR and CRM (customer relationship management) applications and accounting software. That would mean that in addition to the installation and configuration work required for the portal applications, the reviewer would need to generate legacy data, install and configure HR, CRM and accounting software, and tie all the systems together for the review. That would make for a great review, but it would also be prohibitively time-consuming and expensive.

But what if the legacy data were already online and available, gathered as part of the ongoing operation of NWC Inc.? What if the HR, CRM and accounting applications were already installed and running simulated transactions 24x7? Furthermore, what if these systems weren't subject to the normal rip-and-replace process inherent in testing labs? Then we'd be able to do the portal review and much more--testing the vital interoperability features that are critical to your business. The switches, routers, servers, storage, operating systems and applications software installed at NWC Inc. are dedicated to the IT needs of the fictitious company. We'll treat NWC Inc.'s networks and servers as if they are production systems to ensure they're there when we need them. The applications and data will also be available to do the kind of in-depth, comprehensive reviews we need to do.

The core application infrastructure will maintain databases with financial, inventory, customer and order data. Our Microsoft Active Directory Server and Exchange implementations maintain a list of employees and access rights. The applications and data served by our infrastructure won't go away: They'll expand and change over time. When we bring in a product to review, we'll pit it against the real-world data and applications residing in the existing environment. Business-intelligence tools will need to analyze existing, real-time data. CRM applications will need to integrate with our customer and order data. HR applications will have to interoperate with our existing authentication mechanism, and Web-based products will have to play nice with our Apache/IBM WebSphere/DB2-based Web infrastructure. (For more infrastructure particulars see "Building Blocks" and "Software Focus".)

We'll use NWC Inc. to test business applications from a unique angle, looking hard at integration capabilities as well as feature sets and product life-cycle issues, such as those involved when performing critical system upgrades. How does the new software affect and interact with not only our current data but other integrated applications? If the pieces don't fit together, we'll tell you. If there are particular pitfalls to avoid, we'll let you know.