search cancel

Recommended installation when running CPT and TCPaccess.


Article ID: 53910


Updated On:


SOLVE:Operations Automation SOLVE:Access Session Management SOLVE:FTS TCPaccess SOLVE



TCPaccess 6.0 is currently installed. I am preparing to install Solve:CPT 6.1.

Should Solve:CPT be installed in the same SMP CSI as TCPAccess or, can it be installed in its own CSI?


CPT shares FMIDs with TCPaccess, including the tracing, SAS, and the API translation table components. CA customer support therefore highly recommends installing all TCPaccess family products together.

There are TCPaccess PTFs that, if applied, require that specific CPT PTFs also be applied (and vice versa). If you have the two products in separate CSI's, you will miss some of these dependencies as the IFREQ statement in each PTF will not find the FMID that the other PTF belongs to, and thus not notify you of a potential problem.

It is possible to install the products in separate CSIs.

The danger in doing so is that some of the same components now exist in two separate locations. We strongly recommend against this method as it exposes installations to mixed product levels in production, potentially causing unpredictable results. We have seen unexpected and unpleasant problems with some customers using this method.

Our recommendation is to keep both products in the same CSI.

If you have both products in the same CSI, you can avoid having to maintain some of the same FMIDs in two separate places, and you avoid applying PTFs with IFREQs in one place and not the other. Maintenance for CPT is contained on the TCPaccess Service Pack tapes, so you can update both products at the same time.


Component: SOPMVS