|
|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
/ D' H9 w I& L6 X* m1 L. G4 @0 c, T/ c" x
8 g6 Y, u( c+ @- `6 }5 a3 x# l
Teamcenter BMIDE热部署原理和步骤
; E8 t- Z+ h# A0 @; m( v; M- T; I3 W
Let‘s understand these steps in detail. + x6 J, q, X; h0 X
1) Package & Upload template files to FMS volume 7 V: x) r+ b9 j: ^- d: M
a. In this step the BMIDE client will generate the new version of the template package and upload this
/ h+ [5 `1 l- i y4 |! p4 t% d9 Rpackage to FMS volume using a SOA.
, f9 Y; G* E& F# ]8 e+ L% R) a2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards) 0 H& N+ L% m% H! R0 a% n4 ^
a. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
- l4 u+ c8 D- K# |3 @3 I* W8 W0 D$ Kfolder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
7 z9 F+ U3 T2 w, ]9 I3) Download template package from FMS volume . U% `8 F! f: x% d# }( W
a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS 4 N( L6 L" p7 Z8 C: x
volume.
3 j1 A7 \$ g: p6 P( {9 b2 S4) Generate delta.xml s9 J. ^6 [+ ]+ s- ~5 I
a. In this step, the delta.xml is generated using the files in TC_DATA/model
8 k' t. N- ?% L1 b8 R. qi. Copy model.xml to model_backup.xml
/ |( z) T k! l( V1 G4 _ii. Copy model_lang.xml to model_backup_lang.xml ) |& _" J3 E/ a3 f2 Y% P, ]3 n
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml / K; d3 }3 U' v- \% T& p
iv. Load model_backup.xml and model_backup_lang.xml as old model
. a( s9 d! y+ u% ~! d$ L5 }v. Load model.xml and model_lang.xml as new model
& K$ O9 B1 g9 w" u, r7 zvi. Compare and generate delta.xml ) E4 N# h* S; u4 q) j0 K9 `
0 W# B0 h6 t% q; P4 g: x/ f
8 @0 F; v0 r( W9 ~' c# p) E, C$ ~b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
: v, R. @( F' T8 j5 tfrom datasets ( except for model.xml and model_backup.xml)
: x0 |: u! q6 o: w1 E" I8 z* M5) Update the database with delta.xml using business_model_updater
+ V2 r" T) g# B; Wa. This is the step where the database is updated with the new data model. The utility
6 X( o$ z. \9 w: C* P5 [business_model_updater updates the database with the contents delta.xml.
6 R; |2 e8 B% Yb. If the update of the database fails, the contents of database will be extracted into model.xml and
0 g& g- q+ |2 d$ l% B4 S& Amodel_lang.xml 6 D T3 d/ a. C) p
6) Generate CLIPS rules, PLMXML schema file using the extracted file
7 O* e7 z* f: F5 n4 A" Ja. The CLIPS rule file is re-generated if any Condition definitions were updated
& U/ i: n h1 t& Nb. The PLMXML XSD is also re-generated $ t3 ^7 Y. q' ^+ J5 b0 b1 K
7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) 4 p, k7 ?+ G1 T* g/ R
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
t8 b7 n6 `2 _7 A3 Kwith the database
+ T0 Y! k" Z9 r7 v8) Upload log files back to FMS volume
; Z+ y# m! i) [' K* ?1 g4 y, Da. All deploy log files are uploaded to the FMS volume
% [5 E8 Q' J" y$ l! f6 ]9) Download log files from FMS volume ! q r" G: D$ v
a. BMIDE client downloads log files to the client after deployment completes. $ N6 |2 `$ H( C: Q; u* f- v. H
4 w: x8 [" ?5 ~6 T
|
|