Sean's Musings as a Service

Sean's Musings as a Service

Upgrading from UrbanCode version 4 to version 6

  • Published:
  • categories: urbancode
  • tags: ibm, urbancode, urbancode-deploy, urbancode-build

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. Regardless of what tool you are using the upgrade follows some standard procedures, but for the 4 to 6 migration there are some special considerations for both Build and Deploy.

The biggest and most important piece of advice here is to make sure you can perform a complete upgrade of your installation. What I mean here is that you test 3 key areas of the process:

  1. Take complete backups of production, this includes your configuration directories, Code Station directories, keystores, and the database.

  2. Installing the software on a system that has your version installed, go ahead and running this on a test system with a small sub set of data first just to try it out and you can avoid any hairy issues out of the box by keeping it simple as you are learning. i.e. Figure out how you will do this mechanically, what files need to be saved, copied, backed up. How the process works, ensure it does work with what your target production system is running OS, CPU, Memory, Disk Space, Service Users, Firewall ports, Database version, JDBC drivers, also gives you a chance to figure out how Rational licensing works as that is new here. Failing to take this step is asking for trouble.

  3. During the previous step, you should learn a bit more about how this process works and we can take the next progression to working on upgrading and migrating a production-like system.

On my side, I was able to get your backups installed, I got uBuild 4.3.1 with and agent setup and running, uDeploy 4.8.1 up and running. Worked through the uBuild upgrade to 6.1.0.2 after having a chance to talk to uBuild support and other than the services not being auto-removed and re-installed I was able to complete the upgrade pretty easy. If you have not already completed this, we need to get your staging environment setup to match production so you can do the verification on your side.

UrbanCode Build:

The overall process here is more straight forward, the latest version was uploaded earlier this week and the upgrade process does not include any interim version increments, so that means we really just need to prep our current installed version and install the desired target version.

Prepare staging environment, with latest clone from production 0. Confirm you have Java 1.6 installed (I tried both Sun JDK and the IBM JRE) and configured in PATH and JAVA_HOME

  1. Install the starting version of uBuild 4.3.1, into blank db (I couldn’t find an obvious way to install without it setting up the db table contents, so I just installed into an empty UBuild db)
  2. Restore UBuild db
  3. Restore file system build server dir <ubuild-install>/var
  4. Start server
  5. Update System > Server Settings > * URLs to the staging server to avoid agents being directed to the production server

High-level upgrade process

  1. Replace the agentupgrader on the existing server: https://developer.ibm.com/urbancode/docs/upgrading-ibm-ubuild-5-0-1-3-earlier/
  2. Upgrade agents first.
  3. Stop the server services
  4. Backup Database with full backups
  5. Backup FileSystem /var directory
  6. Run Upgrade
  7. Remove old service <build-server-install>\bin\service\service remove ubuild-server
  8. Install new service <build-server-install>\bin\service\service install ibm-ucb

UrbanCode Deploy

Working on the uDeploy upgrade process now, have the new setup running and configured, it is high-level process that will likely require some iteration and feedback from the user community to get it right mainly around configuring the new security model.

Reference:

Prepare staging environment, with latest clone from production 0. Confirm you have Java 1.6 installed (I tried both Sun JDK and the IBM JRE) and configured in PATH and JAVA_HOME

  1. Install the starting version of uDeploy 4.8.1, into blank db (I couldn’t find an obvious way to install without it setting up the db table contents, so I just installed into an empty UDeploy db)
  2. Restore UDeploy db
  3. Restore file system uDeploy server dir <udeploy-install> /var
  4. Start server
  5. Update System > Server Settings > * URLs to the staging server to avoid agents being directed to the production server

High-level upgrade process

  1. Stop the server services
  2. Backup Database with full backups ( Restore point 4.8.1 )
  3. Backup FileSystem <build-server>/var directory
  4. Run Upgrade to 5.0.0.2
  5. Remove old service <deploy-server-install>\bin\service\service remove udeploy-server
  6. Start the server at 5.0.0.2 6.1. Verify basic function 6.2 Backup 5.0.0.2 (Restore point 5.0.0.2 ) 6.3 Configure security model 7 Upgrade 5.0.0.2 to 6.1.1.2 7.1 Verify Security model is working as expected 7.1-a: If security model is good, continue 7.1-b: If security model is not good, restore to 6.2 and try and configure 6.3 again 8 Continue setup at 6.1 level
Reference: