Skip to main content
K
KV_104072467-Bedrock
7-Bedrock
May 20, 2025
Question

Windchill not working after setting Windchill DNS alias for URL

  • May 20, 2025
  • 3 replies
  • 549 views

These are the steps I followed to set DNS alias name for URL.

 

1. Disabled the SSO configuration

2. Set the DNS alias name in wt.server.codebase property by 

xconfmanager -s "wt.server.codebase=$(wt.webserver.protocol)://myalias.domain.com/$(wt.webapp.name)" -t codebase/wt.properties -p

 

Property defined in site.xconf file

KV_10407246_0-1747756323323.png

 

3. CERT file has DNS alias name and imported to keystore.

4. Enabled sso.

5. After this unable access new DNS alias name site URL (https://newDNSaliasName.com).

It is not showing It Works.... and unable to generate metadata.

 

Windchill page Shows

KV_10407246_1-1747757154601.png

 

 

Please let me know if I'm missing something.

FYI: followed Article CS387851

 

Thanks.

 

3 replies

M
mmeadows-316-Pearl
16-Pearl
May 20, 2025

That may work, but it is not correct according to PTC's documentation.

https://support.ptc.com/help/windchill/r13.1.0.0/en/index.html#page/Windchill_Help_Center/WCSysAdminWCConsiderSecureInfrastructure/WCConsiderSecureInfrastructure_ServerHostnameProp.html

"The host name used to connect to the Windchill instance is stored in the wt.rmi.server.hostname property (which is initially set during installation as the value provided for the web server DNS host name). This host name is used by all clients that are not JMX clients."

 

wt.server.codebase should not have been touched.  Just change wt.rmi.server.hostname.

xconfmanager --reset wt.server.codebase

xconfmanager -t codebase/wt.properties -s wt.rmi.server.hostname={FQDN} -p

    J
    Jimwang16-Pearl
    16-Pearl
    May 26, 2025

    Do you update the ServerName to the new DNS in httpd.conf under <HTTPServer>/conf?

    M
    mmeadows-316-Pearl
    16-Pearl
    May 27, 2025

    If you are switching all of Windchill to an alias name, at a minimum you have to...

    • Modify the Repository table in the database
    • Change the ServerName in Apache
    • Update the wt.rmi.server.hostname in Windchill
    • Rehost your LDAP JNDI Adapter(s).

    That last one is particularly painful when done manually.

     

    The way you should do all of this is with PTC's rehosting script.  It is tedious to configure but will handle all of these issues and more.

     

    If you are sure that Apache is your only issue, just update it from a Windchill shell.

    ant -f %wt_home%\..\httpserver\config.xml reconfigure -DServerName=server.company.com

    V
    vnamboodheriCommunity Manager
    Community Moderator
    May 28, 2025

    Hello @KV_10407246, 

     

    It looks like you have some responses from some community members. If any of these replies helped you solve your question please mark the appropriate reply as the Accepted Solution. 
    Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.

    Thanks,
    Vivek N.
    Community Moderation Team.

    Terms & ConditionsCookie settingsAccessibility statement