|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
* g$ c! d6 |' E
3 t; `3 S% N9 @0 J! f8 n( Z
% W( l3 I* s; k! M, D+ m7 |
Teamcenter BMIDE热部署原理和步骤
( r8 V; j9 L: d4 p$ x0 _
Let‘s understand these steps in detail.
9 D$ e5 W" w. D! ^; B, x, ~! J& A1) Package & Upload template files to FMS volume 4 j* K T, C9 y
a. In this step the BMIDE client will generate the new version of the template package and upload this
9 q5 D2 \* S" I' |; u" n) r, L) Xpackage to FMS volume using a SOA.
|/ E3 n! T. l; `2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards) * ?& E# z. Z ?: y; c9 b* P
a. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model ! t" s/ Y+ H" z7 [
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
( }, L$ h6 \1 b8 \" D3) Download template package from FMS volume $ `- c2 l9 S' S5 F$ i- a
a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS
W! x! V* C D7 G# c' lvolume.
7 U% S5 ~& E6 u( M. m4) Generate delta.xml
! x/ G8 l! }* `( E, e" }8 Ya. In this step, the delta.xml is generated using the files in TC_DATA/model ' K6 V4 s( G/ ^
i. Copy model.xml to model_backup.xml
) F: N2 h3 C5 K" i0 M3 K; aii. Copy model_lang.xml to model_backup_lang.xml 9 V0 n- T/ O P# { O4 c
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml 3 o" {5 t% K7 j# n. Y
iv. Load model_backup.xml and model_backup_lang.xml as old model
7 { {# u$ z8 f/ I9 av. Load model.xml and model_lang.xml as new model 6 w1 T* e* o& O* U+ V
vi. Compare and generate delta.xml
7 [# Y* c, b4 W: K& y
4 K& M! l6 w& X- @9 r0 ?# C+ D4 {2 d, P) K
b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
- }' R8 H5 `8 H9 W4 F8 ~from datasets ( except for model.xml and model_backup.xml)
, R( ]5 @& f0 w$ L3 h5 e% y( J7 a6 K5) Update the database with delta.xml using business_model_updater & L* K( a" K( J4 j: s+ q) x
a. This is the step where the database is updated with the new data model. The utility
6 k8 R: ?: E( Z4 Obusiness_model_updater updates the database with the contents delta.xml. 9 Y+ E& K9 m, t& S/ ]
b. If the update of the database fails, the contents of database will be extracted into model.xml and
& M. ? E/ z0 o W3 wmodel_lang.xml ! S) }: W8 P1 U3 o4 b$ n* N
6) Generate CLIPS rules, PLMXML schema file using the extracted file & B+ S, u) k; d: w- L% B; R8 t
a. The CLIPS rule file is re-generated if any Condition definitions were updated
- `* s" m( n$ K3 v- y, [ `% V: Db. The PLMXML XSD is also re-generated
( R$ j5 D: v5 d. x; {7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
7 V. B* Q4 G5 O5 f3 Aa. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
- [( x- X3 x; s8 V9 {with the database
+ i* F1 O7 h9 [( K, S! M6 g. I' `8) Upload log files back to FMS volume : m( ^* `/ I% A1 s& J. {+ b
a. All deploy log files are uploaded to the FMS volume
* I& V/ u1 H; G) o" v8 W9) Download log files from FMS volume ) P2 q% H- i1 W$ f: z9 r' N; W5 X% C
a. BMIDE client downloads log files to the client after deployment completes. 0 }4 V& `( {4 |
9 m7 _- p: P5 O- k0 ^: p |
|