When I joined my current role I inherited responsibility for a platform I had never heard of, supporting somewhere in the region of ten thousand users across multiple divisions, with considerable revenue attached to it on both sides. No documentation worth speaking of, no predecessor to ask, and an organisation mature enough to take production environments seriously.

I was given access to the test environment first. No real content, low stakes, hard to do lasting damage. I still didn’t feel comfortable breaking it. That’s not a rational position exactly, but it’s an honest one — I wanted to understand what I was doing before I did it somewhere that mattered, and poking at a test environment I didn’t yet understand felt like the wrong kind of learning.

What I actually wanted was somewhere I could break things properly. Completely. Repeatedly. Without it mattering to anyone.

The OVA file

I started trying to build my own WebCenter environment from scratch. The database layer — which is fairly early in the stack — kept stopping me. I was expecting to find a Docker image somewhere. What I found instead, largely by chance, was an Oracle WebCenter development environment distributed as an OVA file. Sixteen gigabytes. Pre-built. In theory, everything you needed to start developing Oracle WebCenter Portals.

I downloaded it. My Apple Silicon MacBook didn’t want to know. I tried my Linux desktop instead and at least got the file open. Inside was Oracle Linux 6.4, a 12c database, Fusion Middleware, WebCenter Portals, and WebCenter Content — all pre-configured and theoretically ready to go.

There was a readme on the desktop. A single command, it said, should be enough to get started. I ran it, was asked whether I wanted to start the database, middleware, WebCenter Content, WebCenter Portals, OHS, or all of them. I chose all of them.

OHS…

The database came up. Middleware started. Then it hung on OHS.

This was Christmas. I left it running and went downstairs to watch a film with the family. Came back later. Still hanging on OHS. I tried a few more times over the following days, then tried bringing the services up manually one at a time. Everything came up fine that way, with the exception of OHS.

I went looking at what OHS actually was. Found it in the filesystem, recognised it immediately — it was just Apache, acting as a reverse proxy to map ports so the services inside the VM were accessible from the host machine. Useful, but not something I strictly needed to have working through the startup script. I looked at the logs anyway. SSL issue. I commented out the SSL config line from the OHS configuration file, tried again, and everything loaded.

I had a fully working WebCenter environment that I could break as hard and as often as I wanted. If I truly couldn’t recover it, I could delete the VM and start again — and now I knew exactly how to get it running.

I spent a good amount of time in that lab over the following weeks. Breaking things, understanding why, putting them back together. It changed the quality of the questions I was able to ask the DBA team at work — specific questions get specific answers, and I now knew enough to ask specific questions. It helped me describe what I was looking for in the production environment in terms that made sense to people who’d been living in it for years. Nothing beats having somewhere private to be wrong in.

SSL

The SSL issue took a while longer to fully understand. The OVA was built in 2015 and hadn’t been updated since. When it started up and became aware of the current date, the certificates were simply expired — by about a decade. Two fixes: disable SSL entirely, or set the VM clock back to 2015 and disconnect the network card. Both work. For a lab environment that doesn’t need SSL, commenting out the config is the easier default. I’ve spun this OVA up several times since and the fix takes about thirty seconds now.

It’s a small thing. But there’s something quietly satisfying about a ten-year-old virtual machine, abandoned by Oracle, waking up on your Linux desktop over Christmas and becoming genuinely useful again.

Tags: