≡ Menu

TBSM v6.1: A Quick Walk around the Documentation and Initial Planning Resources

in Best Practices, Business Service Management, E2E Service Management, IBM, Implementation, TBSM, Tivoli, Usability, Value

The main TBSM v6.1 documentation is now online and available here. A documentation landing page is available here for quick access to previous versions of TBSM documentation. PDFs are available for download here.

The TBSM v6.1 Release Notes are available here.

The new TBSM v6.1 wiki is located here. The old TBSM wiki is located here. Content is being migrated to the new wiki.

The TBSM Support homepage is here.

A searchable interface for all TBSM Support content is available here. The RSS feed for all TBSM Support content is available here.

The first place you should start your planning activities is the by closely reviewing the Exploring TBSM : Planning section located here. Read it again and again. Don’t start deployment without carefully considering these high level areas and then performing more detailed research into key topics such as architecture, platform and server requirements, installation types and options, end user browser and JRE support, etc. A more detailed planning overview is available in the Installation Guide available here.

A high level installation overview is available here. The detailed installation procedures are available here.

Migration from a previous version of TBSM 4.2.x requires significant planning and forethought. I do not recommend performing outright migrations or upgrades without significant consideration of key areas such as architecture, platform and system provisioning (32b vrs 64b, CPU/Mem), BSM event management design, key designs for data/template/structure/behavior/navigation/visualization models, etc. with significant focus on how the previous deployment of TBSM v4.2.x can be optimized, improved, and provide increased value for both the administrator and end users by exploiting new capability, feature and function in the new TBSM v6.1 release.

Migration planning information is available here.

As an alternative to an outright migration, I would recommend performing a “selective migration” where the legacy TBSM v4.2.x system is migrated to a temporary TBSM v.6.1 system using the procedures described in the manuals above. Once all of the content has been migrated to the temporary TBSM v6.1 system, you can then use the new and greatly improved export capabilities to “selectively export and migrate” content to a more permanent build (sandbox/dev/test) and fresh installation of TBSM v6.1. These new and greatly improved export/import capabilities offer signficant administrative control at granular levels for what can be moved between TBSM v6.1 systems. I’ll spend more time discussing these features in follow on posts.

That’s all for today.