During a recent ASUG Webcast I gave on the basic components of BusinessObjects Enterprise, I was showing the Windows version of the Central Configuration Manager (CCM). I had a question as to whether the CCM was available in UNIX or Linux. I was able to answer that yes it did exist, but did not have sufficient time to explain it in detail. It’s the perfect topic for a blog!
It isn’t Very Pretty
Windows won its huge market share in the late 1980’s and early 1990’s because, let’s face it, it was a whole lot prettier than DOS. Being arguably easier to use probably had something to do with it, too. But UNIX and Linux didn’t fall prey to that nonsense (well Linux has started to, but that’s another topic). For the most part, the non-Windows operating systems are big, bad and ugly. They stay up for years without needing a reboot, can handle massive workloads, but you’d better know your way around a command line and a little bit about shell scripting if you’re to survive the encounter. The BusinessObjects CCM for UNIX or Linux are no exception.
The Shell is the Thing
The CCM in a non-Windows install is a shell script better known as ccm.sh. It is in the /bobje directory under your default install path where most of the other main product files and folders live. Of course, like any self-respecting shell script, ccm.sh requires different parameters and authorization so it knows 1.) what you want it to do, 2.) to which CMS you want to do this, and 3.) who you are to request such a thing
From the Admin Guide (with a little of my own color commentary added), here are the parameters you can pass.
For question 1, What you want ccm.sh to do:
For answers to question 2 and 3, the following options are used:
Practice, Practice, Practice!
So putting all of that together might be a little confusing for the first couple of tries, but once you get the hang of it, it really does become second nature.
For playing around with such things, I have a Red Hat Linux VM installed on my laptop with BusinessObjects Enterprise XI 3.1 installed on it. It’s slower than molasses in January in Vancouver, but it functions and allows me to experiment with impunity.
For my example, I’ll show the -display command since that’s quite useful to an administrator.
The command, when properly strung together looks like this:
./ccm.sh -display -cms GMYERS01L -username administrator -password
Here’s the output of that:
As you can see, this is very useful for an admin. You can see if the server is running and/or enabled, and what the PID is.
The other commands I use frequently are -stop, -start, and -restart although much less of these are needed in XI 3.1. We still have most of our installs on XI r2, so I have to do the stopping and starting and restarting this way. 3.1 makes it way easier with the SIA (which will be the topic of another blog I’m working on). Overall, BOXI 3.1 on Linux and UNIX is way easier to administer than XIr2 is.
While ccm.sh isn’t anywhere near as pretty as the Windows equivalent, it has all of the functionality. I especially like the “terminate with extreme prejudice” option for those times when I have to kill stuff in a hurry. I’d like to see you try that on a Windows box! 🙂