4.0.0 cannot upgrade an installation older than 3.3.0 directly.
Up to 3.2.x, OAuth consumers, friends and configuration were stored in XML files under
sodius/data in the Windchill Home folder. Versions 3.3.0 to
3.17.x provide a migration that moves them to the Windchill database;
4.0.0 no longer does.
From such an installation, first upgrade to 3.17.6, launch the pending migrations from the OSLC Connect administration page, check that your friends and consumers are listed there, then upgrade to 4.0.0.
Uninstall the previous version with the 4.0.0 uninstaller, before installing 4.0.0.
Extract the 4.0.0 delivery, then run its extensionUninstall.xml against the
version currently in place. Do not reuse the uninstaller that came with the older delivery.
Up to 3.17.x, the Extension configured Windchill by writing
its properties into site.xconf. From 4.0.0 it declares them in a file of its own
and adds a single reference to declarations.xconf, leaving
site.xconf untouched.
The two do not simply coexist: site.xconf is applied last, so an entry left
there by an older version overrides the new declaration. Skipping this step, or running the
older uninstaller, leaves an Extension that installs without error, reports no problem in the
logs, and never starts.
The 4.0.0 uninstaller removes those entries. Before changing anything, it writes a copy of
each file it is about to modify, and the list of the entries it removes, into a
sodius-xconf-backup folder inside the folder you extracted the delivery to.
Keep them until you are satisfied with the upgrade: they are what lets you check exactly what
was taken out, and put back anything you need. See
Check the deployment of the OSLC Connect for Windchill Extension.
From 4.0.0, OSLC HTTP clients validate the SSL certificate chain as a default. A friend whose server uses a self-signed certificate, or a certificate not signed by a trusted certificate authority, is no longer reachable after the upgrade. If this is expected in a staging or test environment, you may temporarily turn off the "Validating SSL Certificate Chain" setting in the Security configuration.