Стандартная настройка > Windchill Customization Basics > Managing Customizations > Best Practices for Customizing Files Supplied by PTC > Managing Client JAR Files > Current Foundation JAR Tree Definition
  
Current Foundation JAR Tree Definition
A representative view of the dependency graph of the client JARs is shown below.
* 
The figure and the table following it constitute merely a representative view, not necessarily the complete dependency graph.
Each label refers to a logical JAR (composed of head, customization, DSU, and FCS components) unless otherwise noted. Bolded labels are “root” JARs intended as top-level JARs to directly support applets, whereas the non-bolded labels are intended solely for re-use from other JARs. Each arrow implies a dependency (and essentially inclusion by reference) in the direction of the arrow. It should thus be clear that all JARs currently defined depend on wtApplet and 3rdPartyApplet with the notable exception of wtBootInst. Thus all duplicates are consolidated down the tree except from wtBootInst which is completely independent. The graph shown supports almost all of the Windchill Foundation applets and will certainly grow over time.
These logical JARs are further described in the following table.
Logical JAR
Description
3rdPartyApplet
A head JAR which collects all the commonly required 3rd-party libraries into a single point of reference. As such it does not include any separate resources and thus has no customization, DSU, or FCS components. Rather it is purely an ordered list of references to 3rd-party libraries. This list is similar to that found in 3rdparty.jar but has had all library references which do not make sense for applets (e.g. JSSE) removed.
wtApplet
Common base (non-3rd-party) resources shared amongst most Windchill applets. Like all other shared logical JARs, this JAR serves to collect all resources which would otherwise have been duplicated in JARs above it. Please note that the intermediate JARs wtPolicy, wtQB, and wtWork also serve to consolidate duplicates between themselves and JARs above them.
wtBootInst
The JAR for the Bootstrap loader installation applet. This is currently the only root applet JAR which is not based on wtApplet. This JAR does duplicate a few resources from wtApplet, but this JAR was kept separate as it had so little overlap with wtApplet and without this dependency could be kept extraordinarily small and lightweight.
wtPolicy
The JAR for the Policy Administration and domain browser/selector applets.
wtQB
The JAR for the QueryBuilder and Report Management applets.
wtWork
The JAR for the Workflow, Life Cycle, and Team-related Applets (Workflow Administration, Team Administration, Lifecycle Administration, Initiate Process, Process Manager, and Setup Participants).
wtFVault
The JAR for the External and Remote File Vault Administrator applets.
wtExp
The JAR for the Windchill Explorer applet. Note that this JAR references / depends-on wtPolicy, wtQB, and wtWork as many of the clients supported by these JARs can be launched from within Windchill Explorer.
* 
This JAR is obsolete as of Windchill release 9.0.
wtCal
The Calendar applet JAR.
wtESig
The electronic signature/identity applet JAR.
wtIXB
The JAR to support import/export and bulk-loading applets.
wtSearch
The JAR to support Applet.jsp, AppletQuery.jsp, and ChooserTask.html customization samples. This JAR essentially only contains the top-level applet class and exists primarily to keep wtApplet from containing any applet-specific resources and to provide a simple top-level JAR sample.
wtTypeAdm
The JAR for the Attribute Administrator, Type Manager, CSM, and Re-Use Manager applets
wtLogin
The JAR for the login/reauthentication applet (i.e. that accessed via Login.jsp).
Note that wt.jar and 3rdparty.jar, the JARs used in Windchill applet deployments prior to R7.0 are not used at all by the new applet deployments. Both of these JARs are now the sole province of any applications which use them to maintain and use as they see fit. The new JARs are dramatically smaller than wt.jar.
Parent topic 
Managing Client JAR Files