Find ConfigEngine tasks in WebSphere Portal 6.1

Sometimes when a ConfigEngine task fails, it can be handy to be able to look up in the code to see more information about which task failed. And since all the tasks are written in plain old xml files it’s quite easy to just go in there and look at them. In Portal 6.0 (and before) this was really easy to do, since all the configuration scripts were located in the same place (or two places – WebSphere/PortalServer/config/actions and WebSphere/PortalServer/config/includes) . You could simply grep over all the xml files in these two directories for the task name that was failing and it would return the xml file the task was in.

From 6.1 and on this is more difficult because the configuration scripts are located with each component of Portal, in form like this: /config/includes/.xml . Here’s a oneliner than you can use to search for task names in just these directories. Run it from the PortalServer directory.


#!/bin/bash
find . -wholename */config/includes/*.xml -print0 -type f | xargs -0 grep -l "task-name"

Here’s the same thing in a script.
config-engine-search

If you make any changes to the ConfigEngine scripts, make sure you take a backup first!