|
|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
×
Component details1 m; }6 F( }; @8 W* T
There are several components to the Active Workspace Client.
9 s2 H4 Q F# [+ B7 I• Active Workspace Client data model( R) k8 V+ o m y2 l2 T
The data model is the client-specifi c model required for the Active Workspace
" w3 `# [& y5 E/ X- C2 Q( oClient feature. It is installed as the Active Workspace extension to the% |( k5 [5 A9 S2 o
Corporate Server using Teamcenter Environment Manager (TEM).
. N# n) K$ C- Q. \' W% h, F• awc.war file. L0 u7 Z7 i0 W0 F; S
The awc.war file is an additional deployment. This fil e is generated and
0 n6 h* X6 O ]0 V7 n) [& dconfigured by selecting the Active Workspace Client solution in TEM, with all M- h' C1 F* ?8 \1 W
features that contribute to the Active Workspace Client.
0 F# Z. y" I' r: }; m% {This .war file can be deployed on the same application server that hosts the
0 G. \; G1 Y7 [2 hTC.ear file and the Teamcenter J2EE middle tier. This is the user facing web
9 H7 x* l7 {: m! C4 Gapplication and serves as the host to web proxies that connect to the existing9 {% J3 o! m% M
Teamcenter SOA and File Services. You must deploy the awc.war fil e on an6 t* k: y9 k# ~# c
existing server, much like the traditional Teamcenter web client (J2EE middle# r( Z- W% x( C/ t$ p
tier).
3 k& Z' X# m8 l* P• Visualization Server Manager
1 G/ j6 E, P/ e6 D1 p0 B b2 LThe Active Workspace Client delivers 3D visualization throUGh a pool of
0 v6 X) V$ B N, W; j, mrendering servers. Each server runs a single Visualization Server Manager0 ~, ]9 P, G+ `5 m T
component, which manages as many VisServer rendering processes as required.3 T. h- \; ]- v& V1 l1 |: k
For Active Workspace Client 2.0, only a single rendering server is supported.( U7 m, }% _/ a
Note You cannot run the Visualization Server Manager on a virtual machine [& ^: B' z% v- _7 x
as it requires hardware graphics support.
# g" u& [8 g' E6 f; a6 x. j& [5 c, }. y9 K) X& A
• TcFTSIndexer client& m% M' |+ q- S8 p4 E! [
This is a 4-tier client used to export Teamcenter data for importing into the
6 [) C# H! O! a1 \Solr database. It uses Dispatcher to execute Query, TieExport, Transform
7 Q D& }4 T: i0 P ], Zand load operations. This is installed and configured by selecting the Full
# Z1 d. u( F1 U+ E+ zText Search Indexer feature in TEM, and by installing Dispatcher with
6 k( c$ s( m1 g4 a0 Ttcftsindexer_queryuids, tcftsindexer_tieexport, tcftsindexer_transform,
# V, y6 F- I. L: D, B4 Q3 jand tcftsindexer_load services. The TcFTSIndexer is run directly for the
' Z# \% v- Z. n4 W" I4 ?initial indexing and run periodically (scheduled) for subsequent updates." t5 D1 F0 `% j3 g9 m7 a
• Solr database7 D4 U; Y, |$ K" J! C8 ], E) v
A Solr database is required for storing Teamcenter data for full-text search. This
6 E5 ~# m; M. M- scan be an existing deployment or installed specifically for use by the Active
/ Y: L/ |- d. \, V; kWorkspace Client. If an existing installation is used, there are configuratio n and
' }) C. L: A3 s {, W. F$ G6 mschema changes required to accommodate the Teamcenter data.
( v( c T& |6 a9 o7 q( u2 v: c2 U
- L% v% t9 i% S- p; V w. J; y0 p; a z5 H2 @
|
|