cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Ensure Windchill functions and Windchill start when one LDAP Adapter is offline

Ensure Windchill functions and Windchill start when one LDAP Adapter is offline

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
Windchill administrators and general users


2. What version of Windchill are you currently running?
11.1 , 11.2, 12.0, 12.1


3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
Windchill does not start when at least one LDAP adapter is offline or wrong configured, but other LDAP adapters are online.


4. What is the use case for your organization?
Windchill is offline, no one can work


5. What business value would your suggestion represent for your organization?
Windchill should start when at least one LDAP adapter is online. Users from offline adapters cannot login.

3 Comments
olivierlp
Community Manager

Hello, 

Thank you for your idea and the information provided.

olivierlp
Community Manager
Status changed to: Acknowledged
 
BrianSullivan
7-Bedrock

Hello.

Very Valid Point to have this enhancement as so many smaller customers run into this issue.  Windchill should stay up for Users that can access the System - And Just Report a Notification to All Users that an Adapter is Offline - so it can be reported to Windchill Administrators.  Even if its just a local site admin account.


We Still configure customers that have multiple Active Directory Integrations and the Systems will go down if one is not available.

 

Currently the Best Solution is to make a Primary and a Secondary Entry  for a LDAP/JNDI Adapter.. so if the Primary Server is offline Windchill does not go down.

https://www.ptc.com/en/support/article/cs158333

 

Additionally - Workaround for some customers has been to make the Secondary LDAP Entry be on the same Virtual Server Architecture as the Windchill Server so as not to be impacted by any Network connectivity issues outside principal facility.

For Example:

Windchill in Michigan

US AD Integration is in Michigan

Europe AD Integration is pointing at Primary in Belgium,  but they make a Secondary AD in Michigan.  If Belgium goes off Line - Windchill is not effected as it sees the Secondary local to it. (Though if Link Broken or Primary DNS down -users in Belgium likely can not access anyway).  All North American users are not effected.