|
|
请使用QQ关联注册PLM之家，学习更多关于内容，更多精彩原创视频供你学习！
您需要 登录 才可以下载或查看，没有账号？注册
x
' D4 P4 _! _& u. l+ Z
) Y& ?1 i, L- d- z; K8 y/ S
* T4 O. s5 _9 g2 v6 ~$ x% {
Teamcenter BMIDE热部署原理和步骤
8 h: X: U4 Q( L$ W( YLet‘s understand these steps in detail. $ j3 |8 s: N8 I3 v7 M2 I1 L
1) Package & Upload template files to FMS volume
2 F9 _9 ]1 V3 v8 t5 c" \! Ua. In this step the BMIDE client will generate the new version of the template package and upload this
( `. q- Z2 i$ z8 Y! f6 a( opackage to FMS volume using a SOA. * M$ y2 T9 R+ z) S2 b
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
, p' Z5 q$ u' k+ U; pa. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model 3 O! @( E/ s+ I
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
2 i/ ?4 V; t3 X! X8 j3) Download template package from FMS volume
- ^% w9 i8 Q$ w0 w: {, ca. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS ' u* ] v! q2 j/ z2 W% V g5 [5 o
volume.
' l# w* e8 O; O) I) w. e4) Generate delta.xml " Y: r8 `. i. f6 p3 M
a. In this step, the delta.xml is generated using the files in TC_DATA/model
* z4 s6 ~3 r' K+ K4 _1 q2 b9 `i. Copy model.xml to model_backup.xml
# i4 r: L7 _- S" t2 I9 G, C4 Xii. Copy model_lang.xml to model_backup_lang.xml Q& @6 Q' @8 B
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml + i) y4 Y! L9 v& {6 y: H$ v
iv. Load model_backup.xml and model_backup_lang.xml as old model * y) c- S# k$ {# b
v. Load model.xml and model_lang.xml as new model q. h8 U% {6 `7 k% b
vi. Compare and generate delta.xml
1 L, N6 G9 s. x) j4 g3 H$ \7 Y: {- n( b
& J; d8 \/ h8 W- D! tb. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model 1 b8 m& w, E# a* I& _. f$ ~) ]
from datasets ( except for model.xml and model_backup.xml)
& L% W) b0 P1 Z) O" N9 p5) Update the database with delta.xml using business_model_updater
! }) ?' G4 p4 f3 H. X7 Fa. This is the step where the database is updated with the new data model. The utility # [5 H- y# G% y
business_model_updater updates the database with the contents delta.xml. - K: _ C0 _8 q+ ~5 Y5 d( p
b. If the update of the database fails, the contents of database will be extracted into model.xml and ( e* q) J* g& U) U( b- U
model_lang.xml
( u* s l8 C3 o; w$ U# |; ]6) Generate CLIPS rules, PLMXML schema file using the extracted file
: R7 [7 j) V# @& B: Q" Ha. The CLIPS rule file is re-generated if any Condition definitions were updated
+ M( k. B y( m% _- h- w& rb. The PLMXML XSD is also re-generated
4 j! p7 e4 A( Y7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
2 y. \# {& C; Oa. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync 5 P, O: x( p+ H6 G1 n+ P
with the database
- U% R) S1 i* y8) Upload log files back to FMS volume
7 B5 Y, Y! D7 _5 Wa. All deploy log files are uploaded to the FMS volume % v& X: H- i6 b
9) Download log files from FMS volume & T6 t/ _5 B; ]) V8 A: @* S2 I4 j
a. BMIDE client downloads log files to the client after deployment completes.
, M. r9 L7 s: s2 B9 C/ [6 A1 q3 d# A% A% H |# o6 l8 s8 H1 ]# e- O. E* p
|
|
|小黑屋|PLM之家-专注工业软件生态建设，大模型CAD创新生态
( 沪ICP备2026005248号-1 )
发表于 2013-11-25 18:19:57
