Windchill System Administrator's Guide

Overview
Protocols
Client Example
Browser with pure
HTML user interface
Java clients, in the
form of Java applets
in HTML pages
Stand-alone Java
applications
As a Web-based application, Windchill must be compatible with security
infrastructures of intranets, extranets, and the Internet.
This appendix provides some basic information for dealing with firewalls, proxy
servers, reverse proxy servers, Network Address Translation (NAT), and so on.
Note: This information is provided only to assist you with security infrastructure
management. PTC does not provide support for any third-party products
mentioned here, nor is PTC responsible for your security infrastructures.
To understand how network security infrastructures affect Windchill, you need to
understand the communication protocols within a Windchill system. To
understand the affect of network security products on this connectivity, you
should understand how clients connect to servers. See the following table:
Local search page;
properties page
Windchill Explorer;
Product Information
Explorer
Workgroup Manager
for Pro/E;Workgroup
Manager for CADDS
Communicate
Protocols Comments
HTTP or HTTPS
Java RMI and HTTP
or HTTPS
Java RMI and HTTP
or HTTPS
Java applet or application
HTTP requests are
performed via the
java.net.URLConnection
class.
Java RMI attempts to
establish direct socket
connections from client to
server (never the reverse)
on well-known server port
numbers (configurable).
But it may also fail to be
tunneled over HTTP or
HTTPS.
B-2 Windchill System Administrator’s Guide