Skip to main content

Upgrades & integrating vendor software

The last month we seem to have spent a lot of time dealing with projects to upgrade various  systems.  We run a large number of such systems, covering everything from virtual learning environments and wikis to student record systems and timetabling, and also encompassing underlying middleware software.  I say "vendor systems" but some of these are open-source projects maintained by a global community.  Others are traditional vendors, ranging from large multi-national corporations to niche vendors of HE products.

We have encountered problems with a number of systems, from various sources.    Some of these have been bugs in the third-party software.  I won't name the systems, nor even say what functions they perform, as I don't want to bring any particular vendor into disrepute.  Other issues have turned out to be caused by mistakes in our own systems.  In one failed upgrade, we kept the existing system running on one site while we upgraded the system on the backup site, only for the tests to fail; it turned out that the problem was a setting in the load balancer that we were using to separate traffic between the two sites.

Upgrade failures are very frustrating for everyone involved.  We have responded quickly in all cases.  Usually we have brought an external consultant on site for a couple of days, as a new pair of eyes can help to diagnose problems.  The consultants don't always find the underlying problem but sometimes they do, and at least they can confirm that we aren't missing anything obvious.

In most cases we have resolved the issues and the upgrades have either proceeded or are due to proceed shortly. One or two do remain and we are working with the vendors to find a way forward.




Comments

Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…