Porting an Existing C++ Connector to Java

If you are porting an existing C++ connector to Java consider the following:

Decide if the Java connector is completely deprecating the C++ connector. If so, the Provisioning Manager plug-in does not need to concern itself with backward compatibility. Alternatively, consider whether the connectors Provisioning Manager plug-in detects whether it is communicating with a C++ or Java connector at the back end by testing for the presence of the eTMetaData attribute on the connector’s associated endpoint type.
If there are any non-backward compatible changes (that is, changes rather than simply additions) to an existing schema, parser table, or format of any attribute values, then consider data migration and possible updates to the C++ connector, if it is not being deprecated.