Teamcenter BMIDE热部署原理和步骤

mildcat

Teamcenter BMIDE热部署原理和步骤

2 P" x+ l+ J0 F) a8 m- m# MLet‘s understand these steps in detail.
1)   Package & Upload template files to FMS volume
- q# i1 b% O  _0 ia.   In this step the BMIDE client will generate the new version of the template package and upload this
package to FMS volume using a SOA.
2)   Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
a.   In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
" M: _% i% D4 X; Z7 @2 v' E3)   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
* j% K* H+ j; I$ A; ^6 E; C1 i1 kvolume.
( F% k7 Y. q( u7 F$ j2 v( Z4 Z5 v1 x4)   Generate delta.xml
) u. y1 a1 Y7 y8 g% T3 ha.   In this step, the delta.xml is generated using the files in TC_DATA/model  
i.   Copy model.xml to model_backup.xml
ii.   Copy model_lang.xml to model_backup_lang.xml
iii.   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
3 i* U: Q  I: c8 c2 B' d7 \v.   Load model.xml and model_lang.xml as new model
  J$ N* Q3 y5 cvi.   Compare and generate delta.xml  

1 {$ w9 i( D" D, }+ G8 O3 t
' L% z( g+ S. Z/ H& _b.   Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
from datasets ( except for model.xml and model_backup.xml)
: H( F9 I1 g" o, l3 \4 `1 W' l5)   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
0 Z" v( R' Q$ t6 @business_model_updater updates the database with the contents delta.xml.
( q' E8 ^8 l% k" U" V  sb.   If the update of the database fails, the contents of database will be extracted into model.xml and
model_lang.xml
" `9 |# t, b% O& [( F' `6)   Generate CLIPS rules, PLMXML schema file using the extracted file
a.   The CLIPS rule file is re-generated if any Condition definitions were updated
9 p4 L9 e5 ]3 x$ t/ u' L5 ^b.   The PLMXML XSD is also re-generated
6 E0 }) {. w/ e- l7)   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
: t# W- h1 N" ewith the database
% P/ u4 y9 J% G1 p5 _# g& @; j- T$ M8)   Upload log files back to FMS volume
# h( K" O( A9 |  z5 O9 a6 i+ g( La.   All deploy log files are uploaded to the FMS volume
9)   Download log files from FMS volume      
a.   BMIDE client downloads log files to the client after deployment completes.