|
|
请使用QQ关联注册PLM之家，学习更多关于内容，更多精彩原创视频供你学习！
您需要 登录 才可以下载或查看，没有账号？注册
x
3 `/ }) f. Y6 U( F+ X4 ~
* R! w+ v7 b: F) k
, T. L4 _2 d/ O5 T% O, C
Teamcenter BMIDE热部署原理和步骤
# G& e7 P8 R+ [% f, xLet‘s understand these steps in detail.
' S6 [ O# h( f' B; [; X9 a0 v1) Package & Upload template files to FMS volume
1 S8 n1 N! J9 b, U0 m- n ba. In this step the BMIDE client will generate the new version of the template package and upload this & a9 Q) ~8 E/ r' x: Q; p m
package to FMS volume using a SOA.
2 }# ] b' A$ g+ p2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
) T5 o4 n$ l$ K. U7 |% j# Aa. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model 3 T! h+ P0 f; A* A# b' O" m+ v9 x# E0 v
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
# w% Z4 J6 ~" t5 J& x0 t* s* Z' G3) Download template package from FMS volume
3 L1 a! X6 \! N5 r+ l: R# m1 ia. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS ; ]3 c, m# u5 `! u4 z! Q( _
volume.
5 _5 h# @- g8 M6 ?6 a9 Y4) Generate delta.xml
( ]1 ~) G% B; |7 D( R( G- X# aa. In this step, the delta.xml is generated using the files in TC_DATA/model & o! p2 m% a2 m1 g$ z
i. Copy model.xml to model_backup.xml
+ D% x- u" A8 t8 J$ Tii. Copy model_lang.xml to model_backup_lang.xml , y6 [ L6 Q2 V" U$ H; c
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml ' R' [) V% P0 u1 @8 Z( F4 g, B( p
iv. Load model_backup.xml and model_backup_lang.xml as old model 3 D* Z3 u, ~8 Q1 Y4 ^, L
v. Load model.xml and model_lang.xml as new model 4 L/ J( ?0 u4 E9 P0 a5 ]# p2 J
vi. Compare and generate delta.xml 3 ~4 W& _/ h2 e$ j- b7 O: r
( ^" R' w4 Y- ^
N, g" n* i$ ]6 F* G% O* d
b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
* y) I h/ e4 M! H. ]/ m( y8 N1 kfrom datasets ( except for model.xml and model_backup.xml)
' D$ A0 o! z: h5) Update the database with delta.xml using business_model_updater
/ a4 I1 i2 S5 B: v6 v& c2 Oa. This is the step where the database is updated with the new data model. The utility " W1 s3 M' ]; j/ x; c4 ]5 ?0 K% ]
business_model_updater updates the database with the contents delta.xml.
/ M, v8 j8 Q9 Z7 @9 c8 M9 Ob. If the update of the database fails, the contents of database will be extracted into model.xml and 0 F$ K ^. I5 `; V6 L
model_lang.xml v# i5 Q# c& S4 l
6) Generate CLIPS rules, PLMXML schema file using the extracted file - B$ A2 v4 a- @ s$ w/ Q5 S" S# D
a. The CLIPS rule file is re-generated if any Condition definitions were updated / n+ Y2 `% a9 i- m$ T
b. The PLMXML XSD is also re-generated
* X/ ]$ m) W0 s# f7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) 9 F# p4 r7 H8 t
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync + h$ W+ n) K4 x- w( N+ U
with the database + ~0 [, f+ M! ]5 e1 z x- ?
8) Upload log files back to FMS volume ' Z! @$ s0 n& m$ L7 i1 H
a. All deploy log files are uploaded to the FMS volume
1 k8 f& ^6 I! s7 h9) Download log files from FMS volume 0 @; J' X/ o1 ~+ j Q/ `2 d6 f: s# l* p
a. BMIDE client downloads log files to the client after deployment completes. / h! M$ t+ D- h
; D L k6 Q2 [+ l% `* c' h |
|
|小黑屋|PLM之家-专注工业软件生态建设，大模型CAD创新生态
( 沪ICP备2026005248号-1 )
发表于 2013-11-25 18:19:57
