CA SCM Tuesday Tip by Dave Carmack, Sr. Support Engineer for June 28, 2011
Support for PowerBuilder was dropped begining with the r12 GA release.
Following is a workaround tip on how to install and setup the client SCM to use the Legacy plugin which supports Microsoft's SCC 1.1 protocol:
1) what is scc 1.1 ? From wikipedia: SCC is a Microsoft Source Code Control (MSSCCI) compliant implementation. This is a Microsoft standard protocol that was developed by them to provide a library of api’s (function calls) to custom plugins that would allow an interface to software change management. The “Legacy” plugin conforms to this protocol (scc 1.1). To my knowledge there has been scc 1.1 and scc 1.2 versions published.
2) what SCM / Harvest version provided the scc 1.1 legacy plugin ? SCM release R12 FP2 and below provides the legacy scc 1.1 plugin in the client release media.
3) How could it help me with PB ? We have had PB customers install r12.0 on their workstations that can work with a r12 or r12.1 server. They can do check-ins/check-outs, but no refactoring (scc 1.1 does not support refactoring). The client workstations can install and upgrade to r12 FP2 to continue to have scc 1.1 support with PowerBuilder. There is a procedure for installing the scc legacy plugin and switching to the legacy plugin after the install.
Install Procedure for R12 Legacy plugin:
a) Install the r12 client using custom mode, set scc support to be installed with the client, reboot after install.
b) Use %CA_SCM_HOME%\SwitchSCCProviders.exe to select "CA SCM" in the Installed SCC Providers dropdown list, then check the "Legacy VCI" plugin checkbox, the click the "Set Active" button.
This will set the right registry settings for use of the Legacy VCI plugin as the interface to SCM repository via PowerBuilder application.
A reminder that this scenario is not tested nor supported by CA, it has simply been reported to CA Support as a customer workaround by the customers that use PowerBuilder and SCM.
Dave Carmack SCM CA Support