|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
5 f z y" H: ^# m1 Z: ]
+ O% E4 O+ t( K p; `
$ ^* e* r9 _, X3 q& s$ c' O: ~
Teamcenter BMIDE热部署原理和步骤
, U& _7 w. _5 d k$ K9 O
Let‘s understand these steps in detail.
8 q) ~( \; F, }1) Package & Upload template files to FMS volume
4 W3 H- Q7 g* H) D" Z2 t% ra. In this step the BMIDE client will generate the new version of the template package and upload this ! K; H% W: @ W* o. J' j/ L: @
package to FMS volume using a SOA. " G! i8 a# S! _
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
4 ~: H, g c4 L' K1 d( Qa. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
; f/ p6 z8 \7 K7 D% \, w8 n% [0 @folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ $ a: S; m( V! y- F
3) Download template package from FMS volume 8 C. `( }0 Y! H% C5 O$ @2 d
a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS , ]5 w ~+ f+ i+ J @
volume.
/ ]* p; J/ a9 Z* i5 z5 @ ^4) Generate delta.xml ! w: N/ \2 O! J) P7 Q; j
a. In this step, the delta.xml is generated using the files in TC_DATA/model
3 j2 \* [+ |- Oi. Copy model.xml to model_backup.xml + l- }* `* t# L: S# j
ii. Copy model_lang.xml to model_backup_lang.xml 5 {+ {' T7 {0 w; P: Q
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml 7 m4 o5 ]* q! g" U4 ~! h
iv. Load model_backup.xml and model_backup_lang.xml as old model : ^/ V* I! o) ]% k, F, R' k r
v. Load model.xml and model_lang.xml as new model
# P$ q0 X4 V2 F5 ]; @vi. Compare and generate delta.xml ( l; |% X; I7 v% I7 S6 {" N
2 A5 P* Q5 u+ C$ c# C/ W# ?
" Y! Z& V& t3 q9 F; b/ }b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model D) \9 x8 z8 c" g ?4 {, Y1 V E
from datasets ( except for model.xml and model_backup.xml) $ A) K4 Z9 D5 ]2 n& C$ T# j
5) Update the database with delta.xml using business_model_updater
- @% f& j; R/ {6 D( \a. This is the step where the database is updated with the new data model. The utility $ l* j2 ?9 u. O. v' M' j1 R. L
business_model_updater updates the database with the contents delta.xml.
: C( R& Y, ]3 Pb. If the update of the database fails, the contents of database will be extracted into model.xml and n& q k/ w0 U" F4 B
model_lang.xml
: m) B" T. G, R! y7 m" B) V6) Generate CLIPS rules, PLMXML schema file using the extracted file $ h, M% h- ^* @9 Y `3 ?& u
a. The CLIPS rule file is re-generated if any Condition definitions were updated $ N3 u6 [( j/ w7 V( [( @: r
b. The PLMXML XSD is also re-generated
2 b4 K/ }0 ^3 Q- R- O* A7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) 5 |6 O. r- _$ H, _ E* u
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
! p7 T6 C3 M& {9 w2 q2 v0 Y7 \with the database
/ V( r6 J( n0 U; y8) Upload log files back to FMS volume
. ~" p% T* o% |: G7 aa. All deploy log files are uploaded to the FMS volume 6 q6 w' B# U" |
9) Download log files from FMS volume ( X# L* K3 n% m- X- j! u; m: J$ v8 v0 O
a. BMIDE client downloads log files to the client after deployment completes.
) ^5 J# }2 Q8 J
3 k }: J8 g' p6 p. ? |
|