|
|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
+ x0 ]# X, u( o0 K: V
+ M$ [, L% [: ]5 g5 {; C
0 D- s/ o- b2 ` e( s* y1 m. L
Teamcenter BMIDE热部署原理和步骤
: z. @- J& G& O1 b8 A
Let‘s understand these steps in detail. 1 {9 H3 g; B6 n! I$ p, U% ?
1) Package & Upload template files to FMS volume + R: P9 j$ D/ C/ I, R- T# y# ^
a. In this step the BMIDE client will generate the new version of the template package and upload this 5 ?* o* f) c8 \5 m
package to FMS volume using a SOA. - k3 _' J0 d# F) j! \+ j0 {& }: O
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
, O5 e2 N' R- j) N/ k) ~% Za. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model " K3 G4 ~5 f+ W( B1 `
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
# M; j0 ]) A% b2 P9 u9 s/ X- |0 F# z+ `) K3) Download template package from FMS volume . ^9 T; J9 k. U* H7 R% }% R( s
a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS A/ o' C( W# {" a2 x
volume. % H, j7 O$ x% D' b$ [+ j" y4 H
4) Generate delta.xml ' N+ C; ]- K* u, M- k; k
a. In this step, the delta.xml is generated using the files in TC_DATA/model 9 x, H" | D7 z+ D9 ?
i. Copy model.xml to model_backup.xml
0 l2 A, L! T9 I- ^ii. Copy model_lang.xml to model_backup_lang.xml : q* Z* g$ I2 m
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml
" o% R7 a0 m+ q. H2 Civ. Load model_backup.xml and model_backup_lang.xml as old model
`5 W6 w( S9 P/ Yv. Load model.xml and model_lang.xml as new model
2 B6 G# t+ J G! s' d' w- c- xvi. Compare and generate delta.xml
$ U- J3 J- a; m5 I' g1 o* B8 D
/ N7 Y! T' p* I% @' E* `/ i* M o6 |0 W; C" u) L1 w
b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
. S0 C2 G: I# b+ s2 b3 \* Dfrom datasets ( except for model.xml and model_backup.xml)
/ B* M( H7 d4 i5) Update the database with delta.xml using business_model_updater
& i$ e. ~* V3 T7 z* A6 ta. This is the step where the database is updated with the new data model. The utility # |6 C$ Q& _, R% ^6 B, P3 V& L
business_model_updater updates the database with the contents delta.xml.
2 s$ h8 ?* v. g7 y; Sb. If the update of the database fails, the contents of database will be extracted into model.xml and - i5 \# \5 ]+ z4 \' [7 N! ~
model_lang.xml
6 O% B- P' `" z6 }) T* E2 p8 f6) Generate CLIPS rules, PLMXML schema file using the extracted file
" Y5 f$ ^5 ?4 W- P; m' ?a. The CLIPS rule file is re-generated if any Condition definitions were updated ( A9 f# g2 }6 Q$ ^# ~8 N
b. The PLMXML XSD is also re-generated
( \" K# P: X* I7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) j1 M' N# i9 l4 W9 v5 |! k
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync 2 g6 e% `; Y# H
with the database
! F. R: v+ r$ g: V4 b/ F8) Upload log files back to FMS volume % R! d" J: n8 @& R( o, g
a. All deploy log files are uploaded to the FMS volume
" s K9 G @, u! r; h" | ^2 R: b0 N9) Download log files from FMS volume
, P8 f0 G* W- ea. BMIDE client downloads log files to the client after deployment completes.
6 ~, b, y& j! I* F+ m' ]
+ v% a9 K1 r1 i# x& @ |
|