Teamcenter BMIDE热部署原理和步骤

mildcat

7 H0 q. T: S2 W6 z" N( K

. `$ l, H! p, f" J: _$ m

Teamcenter BMIDE热部署原理和步骤

- P; W+ o4 ~0 y+ u- K1 q5 lLet‘s understand these steps in detail.
/ `" L( e9 Q% d' `1)   Package & Upload template files to FMS volume
  s" l0 x8 ^& `! a6 Q* Wa.   In this step the BMIDE client will generate the new version of the template package and upload this
: v1 \# G1 z3 r# t* O+ Wpackage to FMS volume using a SOA.
5 @9 S% K/ ^. G  f! u" |2)   Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
- K5 D/ I9 V7 U- r. [- Xa.   In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
. D- l& X# u  v3 I2 f! {& R$ Qfolder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
9 v6 R& H. K' }: m; v& a3)   Download template package from FMS volume
a.   In this step, we download the latest version of the template that the BMIDE client uploaded to FMS
4 {$ ~! x3 {' F# b& @volume.
3 C( G9 e, a8 ~5 q7 Y4)   Generate delta.xml
a.   In this step, the delta.xml is generated using the files in TC_DATA/model  
4 ~& A& k' ?1 E8 k# D0 E# Vi.   Copy model.xml to model_backup.xml
ii.   Copy model_lang.xml to model_backup_lang.xml
* ]* H, P6 G& A! A, X8 ]) p( w% liii.   Consolidate template listed in master.xml to model.xml and model_lang.xml
iv.   Load model_backup.xml and model_backup_lang.xml as old model
v.   Load model.xml and model_lang.xml as new model
& ?. _; n; _% r4 t. q+ r  tvi.   Compare and generate delta.xml  
/ F% E: [& y% x1 Y) |
' T0 Y9 U* h( M! t: W- m8 m
% M2 @3 ^$ l6 Sb.   Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
* E) d4 T) m0 X- bfrom datasets ( except for model.xml and model_backup.xml)
5)   Update the database with delta.xml using business_model_updater
a.   This is the step where the database is updated with the new data model. The utility
business_model_updater updates the database with the contents delta.xml.
b.   If the update of the database fails, the contents of database will be extracted into model.xml and
" [+ b, f3 j$ T: D' mmodel_lang.xml
6)   Generate CLIPS rules, PLMXML schema file using the extracted file
( `- {& p( N; o/ i( j& ua.   The CLIPS rule file is re-generated if any Condition definitions were updated
- \0 k% D: _0 K" wb.   The PLMXML XSD is also re-generated
7)   Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
a.   Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
1 ^' z1 C8 P$ F  Bwith the database
8)   Upload log files back to FMS volume
& T! P% o6 V/ T1 ]* Y# a' i$ Da.   All deploy log files are uploaded to the FMS volume
2 v6 U$ h# Y/ A1 }2 p( X) @# r9)   Download log files from FMS volume      
0 f5 v  O* w) n$ V5 H2 J2 ma.   BMIDE client downloads log files to the client after deployment completes.
$ J5 H) j) x4 l& h2 [/ H
$ q% h* J$ j# h6 U