Pinned topicusing a common tip for TBSM and ITNM-Ip

‏2011-05-05T05:14:09Z
|Tags:

Answered question
This question has been answered.

Unanswered question
This question has not been answered yet.

Hi,
We are using ITNM 3.9. omnibus 7.3.1, TBSM 4.2.1 FP2 and TIP 2.1.0 now is it possible to use a common tip for both ITNM-IP and TBSM . FYI we already using a common tip for ITNM-IP and TBSM but the tip version is 1.3 , TIP version 2.1.0 creates a directory /opt/IBM/tivoli/tipv2 instead of /opt/IBM/tivoli/tip. if any body have any idea please guide.Thanks in advance.

Re: using a common tip for TBSM and ITNM-Ip

‏2011-05-25T07:51:28Z

This is the accepted answer.
This is the accepted answer.

It is not possible to use a common TIP for TBSM 4.2.1 and ITNM 3.9. The reason for this is that the change between 1.1.1 based TIP, which is the version shipped as part of TBSM 4.2.1, and TIP 2.1, which is the version shipped as part of ITNM 3.9, introduced architectural changes which effectively moved products deployed in the TIP application context, from the administration space, as was for TIP 1.1.x, to the default workspace. In addition, TIP was updated from eWAS 6 to eWAS 7 and other updates introduced to address the problems with multi-tenancy environments, as well as enabling support road mapped requirements for future releases, and to ensure that as TIP evolves, products will not meet the same issues as were experienced in previous releases.

Re: using a common tip for TBSM and ITNM-Ip

It is not possible to use a common TIP for TBSM 4.2.1 and ITNM 3.9. The reason for this is that the change between 1.1.1 based TIP, which is the version shipped as part of TBSM 4.2.1, and TIP 2.1, which is the version shipped as part of ITNM 3.9, introduced architectural changes which effectively moved products deployed in the TIP application context, from the administration space, as was for TIP 1.1.x, to the default workspace. In addition, TIP was updated from eWAS 6 to eWAS 7 and other updates introduced to address the problems with multi-tenancy environments, as well as enabling support road mapped requirements for future releases, and to ensure that as TIP evolves, products will not meet the same issues as were experienced in previous releases.