|
|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
9 p _. w- I& O( `
2 T; N8 |- z6 }! X! V2 Z8 G' z3 d; k+ a% Y( d/ c5 @
Teamcenter BMIDE热部署原理和步骤
0 i# l7 k2 n- m K
Let‘s understand these steps in detail.
7 l2 _% R% G0 l1 y! {& H5 y1) Package & Upload template files to FMS volume 6 }) M t1 F1 V* z! q, G$ e% d+ q
a. In this step the BMIDE client will generate the new version of the template package and upload this
$ ?# c( P2 k2 w: U' C- Fpackage to FMS volume using a SOA. 1 i# a# P+ p$ {9 a5 m" m$ D
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards) $ G& B7 ~% X! s$ T- J- C% N
a. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model - n4 R& v# I, b5 L- J6 I) w! o
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ " P3 t8 I$ S( U8 \: K! s2 e
3) Download template package from FMS volume % R/ S L5 B% C6 o! w/ G! `2 s! Q6 R
a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS + [! K) ~7 _; O" L: C. }7 s
volume. ( S% S( ~7 Y! q$ [' {
4) Generate delta.xml
, S) s2 v% r( W8 R: }' Ma. In this step, the delta.xml is generated using the files in TC_DATA/model
+ y+ j& u0 Z3 X/ R' }( g% Qi. Copy model.xml to model_backup.xml $ U! p1 U' R, ^3 B* z$ ]
ii. Copy model_lang.xml to model_backup_lang.xml
1 O* B. }8 u. f, O% D( N. I6 r aiii. Consolidate template listed in master.xml to model.xml and model_lang.xml + O: m. A* G3 }2 E+ n2 H
iv. Load model_backup.xml and model_backup_lang.xml as old model * l* n& m6 g& H/ R0 F
v. Load model.xml and model_lang.xml as new model
9 m1 T- h& N! ovi. Compare and generate delta.xml
( f, u( u6 R" }1 h8 U8 z* H7 @0 v; C' g
+ w' Z2 W5 H' ?* Q; k1 u8 ^9 d% Eb. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
% k( Y, f7 P! k4 m( F% lfrom datasets ( except for model.xml and model_backup.xml) 1 d' j" ~4 h% l' z3 y
5) Update the database with delta.xml using business_model_updater " b- h8 a" j7 E; E$ Z# m
a. This is the step where the database is updated with the new data model. The utility
1 k, O; i8 e4 ^' E' Sbusiness_model_updater updates the database with the contents delta.xml. 0 c- f9 P4 a( y2 [
b. If the update of the database fails, the contents of database will be extracted into model.xml and
% @, C, ^0 N- l4 H0 @% p% smodel_lang.xml
6 @# j- p" |. Y8 M6) Generate CLIPS rules, PLMXML schema file using the extracted file
# u' y; j7 U0 La. The CLIPS rule file is re-generated if any Condition definitions were updated 8 {$ h# P. ]$ Z/ r8 ]
b. The PLMXML XSD is also re-generated
n3 P6 B! X3 u7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
0 X8 e) h( F8 {3 n8 }' |a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
+ s5 @( v. N3 {8 d5 @. H, _with the database
# j2 _; `+ b) B G8) Upload log files back to FMS volume ( [4 m8 b+ E* N1 K0 G2 ^3 r
a. All deploy log files are uploaded to the FMS volume
, i1 s/ s+ p9 P W7 g" r9) Download log files from FMS volume 8 e( Y( y9 `% I( _$ b* L5 k9 H( {
a. BMIDE client downloads log files to the client after deployment completes.
9 {- z$ k# T: L# M: {5 D
5 v6 d/ X/ l0 e, f/ [. }6 O. v5 g |
|