Teamcenter BMIDE热部署原理和步骤

mildcat

6 v' \! e2 z1 h$ p  Y6 t

1 a! U$ S2 Q4 O! L# x: g

Teamcenter BMIDE热部署原理和步骤

Let‘s understand these steps in detail.
1)   Package & Upload template files to FMS volume
a.   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‖
2 w2 R- A* i9 G7 |! g7 U/ i6 C* X3)   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
! T! a& e! m, m) e5 nvolume.
  @9 L0 }3 i. V. o: b4)   Generate delta.xml
a.   In this step, the delta.xml is generated using the files in TC_DATA/model  
* e: J( h. @) C$ R1 a1 Vi.   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
* T* E+ ^2 @- _. |: A2 ~1 tiv.   Load model_backup.xml and model_backup_lang.xml as old model
- K+ `6 ~$ W2 E2 K  p% i. vv.   Load model.xml and model_lang.xml as new model
; ^1 f* {8 X/ L& vvi.   Compare and generate delta.xml  
, j0 ?  `) N  s0 x% j

! @* y. a7 {0 w! D# lb.   Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
0 Y1 V' S# e4 J$ R1 R* rfrom datasets ( except for model.xml and model_backup.xml)
& H' M, N5 v$ V: D6 y5)   Update the database with delta.xml using business_model_updater
# ?- u& V" z  }- Da.   This is the step where the database is updated with the new data model. The utility
9 w& t! D  |$ ebusiness_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
$ N5 ~- _  Q9 Q( e0 K) {0 vmodel_lang.xml
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
4 ~3 ]6 n. u- @* \' x7 `' q6 sb.   The PLMXML XSD is also re-generated
5 D1 W$ b+ H! `0 r: c7)   Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
9 g7 t0 D/ ]) N9 H& na.   Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
# y: x# D' \. W' b. z) Hwith the database
: p' V5 M5 Y, {" o7 C& F2 @8)   Upload log files back to FMS volume
a.   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.