Now that's a big question. The architectures currently are very different, although they are mo
ving closer. At this stage I would recommend using BMC professional services or a BMC partner for this kind of work.
I know that sounds like a cop out, but particularly in terms of managing DMZ environments and inventory, there are some significant differences. The CMDB integration (if you have one) also needs to be reviewed. Reporting is also very different, with additional hardware probably required for BSARA.
You also need to bear in mind that Bladelogic offers a lot of features that Marimba does not, so you need to asses which of these you want to use and what impact that will have.
"if so what would you need to take into consideration in terms of architectural changes besides the obvious physical hardware differences?" Could you be more detail on your question? Are talking about server groups or workspace or roles? Or are you asking about logical or physical Architectural differences? I can try to answer most of those question.
I actually work for a solution partner but am new to Bladelogic, I was initially looking for an answer for the logical and physical architectural differences, but if you could also answer the question with regards to the groups, roles and workspaces as well that would be great, the more detailed the answer the better.
Here is short version of the logical model.
BladeLogic is 3 tier Model. Client | Middle | Server. On the marimba side the client is component is runchannel.exe is like blcli.exe for BladeLogic. On the Bladelogic has CM Console which is fat java client which is like DM. Your middle tier is the Application Server, PXE, and TFTP. Your RSCD agents are at the server tier.
Marimba is muti-tier Model with Web (no client to install) | Middle | Server/Workstation (Agents) | Plug-in (Transmitter) | LDAP hooks etc. If i need to explain the logical Model for the DM. Please ask.
Here is the short version of the physical model for blade.
BladeLogic has different ports. Please review my post: http://communities.bmc.com/communities/message/96299#96299
The only port you'll need is 4750 for blade where has BCAS needs 7717 and 5282. BCAS does RPC with 7717 and get channels via 5282. But, Blade does RPC calls with one port. If you using provisioning, then you'll need more ports. BCAS didn't support provisioning of servers but, it did have provisioning part for workstation. Here are equivalent phyical/software components comparision:
BladeLogic BCAS Application Server Transmitters Repeaters Repeaters CM Console (Fat Client) DM (Web Based) BASRA CMS (Report Center) Provisioning N/A
Hope that helps. Oh, There is no bandwitdh and policy contorl in BladeLogic.
Yes it would be much appreciated if you could explain the logical model for the DM.