http://kecheng.baidu.com/view/61dc23a1360cba1aa911da27.html
1.如何在系统中查找对象对应的类
打开站点中的"类型和属性管理器",选择部件,这个部件就对应了系统中的一个对象,wt.part.WTPart就是系统中部件对应的类,wt.part是包名,WTPart就是类的名称
2.系统类的设计
系统中的服务类设计为xxHelper.java文件和xxService.java是组合关系,系统中的所有业务对象对应的方法在对应的service中,通过xxHelper.serivce.方法 .
部件操作:WTPartHelper.service.方法
文档操作:WTDocumentHelper.service.方法
EC操作:ChangeHelper2.service.方法
文件夹的操作:FolderHelper.service.方法
生命周期的操作:LifeCycleHelper.manager.方法
推进流程对象的操作:MaturityHelper.service.方法
通知机制对象的操作:NotificationHelper.service.方法
位号的操作:OccurrenceHelper.service.方法
参与者的操作:OrganizationServicesHelper.manager.方法
版本的操作:VersionControlHelper.service.方法
3.如何通过类在数据库中查找相关的表
在类型管理器中定义的那些对象在数据库中都有对应的表存在.如部件对象的类名是WTPart.
如要获取一个部件的生命周期状态,数据库中对应字段是statestate这个字段,那么在代码中通过part.getLifeCycleState().getDisplay()这个函数来获取.
4.类型
类型的值被定义在 wt.doc.DocumentTypeRB中
Department
在Windchill中允许用户选择区域,负责文件的管理,值都被定义在 wt.doc.DepartmentListRB中
文件与文件之间的关系:
文件结构 : 一个文件可以使用很多其它子文件,其下层子文件也可以被其它文件使用。(使用与被使用的关系)
文件参考 :一个文件涉及的信息存在于其他文件中。(参考与被参考的关系)
部件wt.part.WTPart
部件参考wt.part.WTPartReferenceLink
部件主数据wt.part.WTPartMaster
文档wt.doc.WTDocument
文档使用wt.doc.WTDocumentUsageLink
文档主数据wt.doc.WTDocumentMaster
项目wt.projmgmt.admin.Project2
项目活动 (典型)wt.projmgmt.execution.ProjectActivity
用户wt.org.WTUser
产品wt.pdmlink.PDMLinkProduct
存储库wt.inf.library.WTLibrary
活动com.ptc.projectmanagement.plan.PlanActivity
计划com.ptc.projectmanagement.plan.Plan
交付com.ptc.windchill.wp.delivery.DeliveryRecord
角色承担者wt.org.WTRolePrincipal
进程com.ptc.windchill.dpimpl.core.WTMasterProcess
可交付结果com.ptc.projectmanagement.deliverable.PlanDeliverable
组wt.org.WTGroup
流程活动节点对象WfAssignedActivity
流程对象wfProcess
5.Windchill各个包的介绍
Package | Functionality |
access | Functionality for access control; used to define access policies and object ownership (that is, define rules for what users or groups have access to what information). |
admin | Functionality to create administrative domains and policies. |
change2 | Functionality to manipulate change items (change issue, request, investigation, proposal, order, and change activity). |
container.batch | Functionality for a client application to gather a group of create, modify, and delete assertions, and submit them to a service method for processing in one transaction. |
content | Functionality for handling content data (attaching files and URLs to content holders, such as documents and change objects) and associating business information metadata (such as the author) with content. |
doc | Functionality for document management. |
effectivity | Functionality to assert that a PDM object is effective under certain conditions. |
enterprise | Functionality for the basic business objects used in the Windchill system. |
events | Functionality for registration, subscription and notification of processing events. The events package provides a hierarchical subscription mechanism that makes it possible to subscribe directly to events of interest. Event dispatching is based on simple synchronous in-thread/transaction calls. |
fc | Basic foundation classes (WTObject, Item, and Link) and basic services for those classes (persistence, object mappable, and identify service). |
federation | The federation service provides functionality to create and manage proxy objects of remote systems and perform utility functions supporting the federation system. |
folder | Functionality to put information into folders and cabinets for navigational purposes. |
fv | Functionality to define and execute the vaulting algorithm for content items. |
identity | Functionality to display the identity of business objects; that is, their type and identifier (for example, a type of part and an identifier of part number). |
index | Functionality to index metadata and content data, controlling how information is put into search indexes. |
introspection | Functionality to make model information available to a run time system. This includes class hierarchy, association, attribute, and database mapping information. |
lifecycle | Functionality to define and use life cycles. |
locks | Functionality to lock and unlock objects. |
notify | Functionality to define rules such that when certain events occur to certain objects, E-mail notification is sent. |
org | Organization services; functionality to create users and groups (generically called principals). |
ownership | Functionality to define ownership of an objects. |
part | Functionality to manipulate parts. |
project | Functionality to create projects, associate projects to business objects, and resolve roles to principals. |
query | Functionality to create queries for retrieving persistent objects. |
queue | Functionality to define and manage queues. Queues are used to persistently record deferred processes. Because queued processes are persistently stored, they are guaranteed to execute at a later time. |
router | Functionality to distribute execution of tasks to multiple Windchill method servers. |
scheduler | Functionality to schedule execution of resource intensive method invocations and keep a history of their outcomes. |
services | Functionality to define and manage application services. Service management includes service start up and shutdown along with service event registration, subscription and notification. |
session | Functionality to define and manage user sessions. |
util | The util package groups together simple low level utilities that do not belong in other packages. |
vc | Version control; functionality to handle versions of objects. Version control services described in this chapter include baselines, configuration specifications, version structuring, version viewing, and work in progress. |
workflow | Functionality to create and manage workflow definitions, initiate and manage process instances, and distribute work items to users and groups. |
6.
7.