|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
- F Z8 W9 B$ O x& g! d# o9 m9 D) Z5 N2 K E0 G* n/ I
& _) i) V+ m9 Q' M0 m; Q* q- L# r
Teamcenter BMIDE热部署原理和步骤
6 D) u6 }4 h/ {& B2 @+ ILet‘s understand these steps in detail. / [' v6 \/ H, ]1 y
1) Package & Upload template files to FMS volume 6 i6 T) i: F" g0 q7 ]( N8 ?$ D
a. In this step the BMIDE client will generate the new version of the template package and upload this - O! p e/ R5 L3 c1 Y' V9 v
package to FMS volume using a SOA. 4 [" c# h% V6 y
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
- n9 f7 [- U6 k# U ?a. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model 2 ^3 [9 I9 b: y) j+ J9 |6 G
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
: z/ o6 k% _, E# U: k3) Download template package from FMS volume
+ Z" P0 D* s2 h' Y$ _4 ]a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS $ G1 B8 _6 V% m# a5 B {% a( ^8 S
volume. ) |, T+ |2 t& k/ `4 f
4) Generate delta.xml
5 R2 }5 I) k0 a4 o1 Wa. In this step, the delta.xml is generated using the files in TC_DATA/model - Y" c( d% F/ G0 q% v9 x/ _
i. Copy model.xml to model_backup.xml
. K6 S. Q |( |9 D- r! y5 Nii. Copy model_lang.xml to model_backup_lang.xml
3 H4 b7 C! {8 \$ ziii. Consolidate template listed in master.xml to model.xml and model_lang.xml $ d6 j9 w9 T' K
iv. Load model_backup.xml and model_backup_lang.xml as old model / C+ ], h+ [! e( ~4 g# l2 ?* u
v. Load model.xml and model_lang.xml as new model
) `! A2 v7 d' F" J* W X% Nvi. Compare and generate delta.xml 4 v+ Q0 x* m* J& w
6 [8 m6 \0 ~( O5 K5 d1 ?
* T4 x% R2 k: c! E
b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
. l2 `/ A( y0 B, ?* Hfrom datasets ( except for model.xml and model_backup.xml)
+ N6 G# Z& ~9 g! k5) Update the database with delta.xml using business_model_updater 5 b6 y: b3 n. d: B
a. This is the step where the database is updated with the new data model. The utility
) r3 c5 j8 {9 [) v4 D4 pbusiness_model_updater updates the database with the contents delta.xml.
5 z4 G0 |$ \+ f$ V5 pb. If the update of the database fails, the contents of database will be extracted into model.xml and
1 U2 q0 Y4 Y1 u1 I0 c( gmodel_lang.xml
/ e( f# m: x) d7 b+ ~6) Generate CLIPS rules, PLMXML schema file using the extracted file
$ C& U) I& y s: za. The CLIPS rule file is re-generated if any Condition definitions were updated
, a0 v& d( H8 `8 D! e+ F, {$ `b. The PLMXML XSD is also re-generated
) g9 b/ i" D& c* p1 h1 h2 m( |7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) % p, I5 Y1 p6 H3 r! b
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync 9 t9 d+ u1 [/ f; @7 p" ]% K
with the database & G- M( Q3 ~8 f8 z6 c
8) Upload log files back to FMS volume
7 Z& U1 b2 p- e' ^# ta. All deploy log files are uploaded to the FMS volume 4 r% p4 ]% ~2 J c6 O0 B" \
9) Download log files from FMS volume
0 i6 d6 y2 O" J+ p: ^9 wa. BMIDE client downloads log files to the client after deployment completes. : C- |8 b. B/ W/ h
/ s; d7 d( V- U+ J* r2 _( ] |
|