Bladelogic has this concept of "Custom Objects" which are a bit similar to "Plugins".
For instance, "Hardware Information" that you see in live browse is obtained using the "hardware information" CO running on your targets.
At times, when the COs are heavy or java based, they can be used via. a special process, which is blcoserver (and hence the name bl-co-server, make sense?)
So when this process comes into picture, you'll get its logs.
Note that "hardware information" is not a CO that gets loaded under blcoserver, so you'll see no logs with it.
The blcoserver.log file generally referred during the provisioning process. Say you are provisioning through the CLM and the customization is failing at some point of time these logs from the target machine will help you to understand in details.
This logs you can find at Target<RSCD/VmWare> folder.
You will find that on the vCenter server where the agent is installed. It is the log of the activity performed by the BladeLogic (bl) Configuration Object (co). In the case of the vCenter, it has the VMWare CO pushed to it.
Thank you for the reply.
I try on the vCenter.