User has a 4-tier connection working OK on http (TC RAC 4-tier, TC web client, SEEC 4-tier).
Customer created a self-signed certificate in IIS and deployed to IIS.
Customer updated the TC website within IIS to bind via https, rather than http.
Customer updated via TEM the 4-tier configuration to use https.
Both Teamcenter 4-tier RAC and Teamcenter web client work as expected - they can create new datasets and download data.
From web browser, customer accessed the self-signed certificate and copied to file.
Then customer imported to local machine and imported to Java cacert file.
SEEC does not connect/login to Teamcenter - gives an error with the SSL certificate.
Does Solid Edge need another SSL certificate installing somewhere?
Solution
In this example the customer did not use the TcCS connection with SEEC.
With TEM they deployed the features/config for TcCS.
Within SEEC define databases, using the TcCS button then populated the form with the TcCS URL.
Solid Edge can now log in without any further errors and can access the user's TC Home.
Notes and References
Hardware/Software Configuration
Platform: INTL64
OS: window
OS Version: 764SP1
Product: SOLID_EDGE
Application: DOC_MANAGEMENT
Version: V109MP5
Function: SEEC
Ref: 001-8883921