Production Technical Architecture for Costpoint 7.0.1
Yesterday, I did a post about the technical changes introduced in Costpoint 7.0.1. This sets the stage for today’s discussion – the technical architecture for a production deployment of Costpoint 7.0.1.
IIS Servers for SSL Encrypt/Decrypt for Traffic to/from the Internet
If you are going to allow access from the Internet, deploy two IIS Servers in a DMZ Network behind a load balancer. The two servers and load balancing provide you higher availability. The DMZ helps protect your backend infrastructure from the evils of the Internet by isolating how far into the network an intruder can traverse.
Middleware and Reporting Servers
For the Weblogic middleware and BIRT reporting servers, in smaller deployments, deploy two small virtual machines in a load balanced cluster. For larger deployments, deploy only three servers in the load balanced cluster, then add CPUs and Memory to the three machine cluster to support greater workloads (more users, more reports). The secret here is that Weblogic is good at using memory to cache what it needs. Scaling is accomplished with larger machines, not more of them. In either case, you’ll need one additional virtual machine to be the administrative server for your cluster.
Database on the Backend
The database is the real workhorse in a Costpoint deployment. Not only does it store the transactional data but much of the business logic is still executed inside the database. The key to a well performing Costpoint environment is having a professional that can size, run, and manage your database environment. In general, the burden on the database for CP 7.0.1 is roughly the same as CP 6 except that CP 7 now requires a 64-bit environment.
Process Server is now Job Server
In the days of CP 6, the batch processing server was called the process server. For some, it was a dedicated workstation where users sent or scheduled jobs to run. In CP 7 and CP 7.0.1, there’s no need for a dedicated server or workstation. Define the new job server to run on the two or three machine Weblogic cluster. Let Weblogic figure out where to run each job especially since most of the work falls back onto the database in the end.
In production, a dedicated Weblogic server is a good idea when you are running Deltek Connector or Pervasive. The Weblogic server can run on the same server on which you run the Integration Engine. When you start deploying packages you’ll understand why. Every time you deploy or update an interface, it restarts the Weblogic server. That’s why you don’t want to use your main Weblogic cluster.
Costpoint 7 is a very different animal than it’s predecessor. If you need some help, we’re here. NeoSystems has a wide range of analysis, conversion, support, training, project plans, and best practices that will enable you to successfully navigate through upgrade and beyond.
If your company is running Costpoint on three, five, or ten year old hardware, then our Hosting solution might be an interesting alternative to rebuilding your infrastructure. Our secure, private cloud hosting solutions are an affordable alternative to deploying your test and/or production workloads internally.
Oh, did you know that Cognos (Costpoint Enterprise Reporting) and Deltek Time & Expense are now in major release cycles too? Luckily, these products don’t require upgrading at the very same time you do your Costpoint 7 upgrade. You have some flexibility, but ultimately, you have three products to upgrade sometime in 2013.
The Costpoint 7 upgrade process is no easy task. We’re here to help you along the way.