• How to pick your UrbanCode Deploy licensing type Fri, May 13, 2016 UrbanCode Deploy licensing is not an overly complex set of options, but it is useful to understand what the options are to see what works best for you and your organization.
  toot-toot!
• Getting some UrbanCode Infrastructure monitoring baselines Mon, May 2, 2016 The primary focus of this post is to focus on the operational concerns of running a healthy UrbanCode Deploy infrastructure, the concepts are mostly generic but I will try and add my thoughts on some relevant points of interest as we step through an example setup and analysis for a server in a future post.
  toot-toot!
• Backing up UrbanCode Deploy Sat, Apr 23, 2016 A standard practice that we all should be putting in place even before we go to production to ensure that we actually understand what needs to be backed up and how to put a process in place. There are two types here, the first being a full offline backup, offline here means the UCD server is not running, the second is an incremental backup. One key to how to design your backup plan is understanding your Service Level Agreement(SLA) and time to recover, what amount of data loss can you accept.
  toot-toot!
• Monitoring an UrbanCode linux server Sat, Apr 23, 2016 Monitoring here consists of three stock standard linux tools dstat, iostat, and pidstat I won’t even pretend that I know how to do this on Windows, but I imagine they have some equivalent, feel free to comment and educate me, but I don’t have the cycles to do the play around with Windows as well. The dstat tool is a consolidated replacement for a few previous tools that did each task, so to simplify it is a good starting point to help us cover our system level monitoring, and pidstat.
  toot-toot!
• Understanding CodeStation Cleanup in UrbanCode Deploy Thu, Feb 4, 2016 Part of keeping your UrbanCode Deploy infrastructure healthy is to ensure that you have appropriate cleanup policies in place. One challenge here is identifying what your corporations actual retention policies are, and establishing the ultimate source of truth for deployable artifact information. A key to understanding and persisting data is to first understand what makes up your meaningful data.
  toot-toot!
• Sourcing UrbanCode Deploy artifacts and general cleanup strategies Tue, Dec 8, 2015 Understanding best practices for sourcing, retaining, and clean-up or artifacts is key to running a healthy UrbanCode Deploy server.
  toot-toot!
• Upgrading from UrbanCode version 4 to version 6 Sun, Jul 19, 2015 Upgrading from UrbanCode 4.x to the most recent versions in the 6.1.x versions can be involved and will undoubtably affect your user community. Below are some steps for getting your test environment setup to actually perform the test upgrades and any migrations needed to help facilitate the process when you have to repeat it with production
  toot-toot!
• Scaling IBM UrbanCode Deploy Mon, May 18, 2015 Using IBM UrbanCode Deploy(UCD) to grow your organization’s delivery capabilities is a great start, but we have a follow on problem to our own success. As the deployment process is managed through UCD we now have to account for and support production application requirements as they are now dependent on the UCD server’s availability and ability to perform. The topic of this article is to discuss the primary means of designing and architecting a scalable deployment with fail-over disaster recovery capabilities.
  toot-toot!