|
|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
$ G& R* } B. x7 k/ s4 l1 N3 g) B
0 y- b1 ^. ]) f- a; _* V( D! Z
/ h) m0 m) {) @$ j
Teamcenter BMIDE热部署原理和步骤
9 G4 ^. M. m, z4 z/ n* q1 ~
Let‘s understand these steps in detail.
1 I2 S& z; ^4 p. l$ g4 j) H4 o( P: ]1) Package & Upload template files to FMS volume
0 h2 R& x" i0 U7 n8 ka. In this step the BMIDE client will generate the new version of the template package and upload this ! V0 B0 o5 J8 Q' Y5 Y) J& s, A) B
package to FMS volume using a SOA.
4 t/ L6 T, g* L0 W6 Y2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
/ v' u( Y# c3 p; j( J8 Ja. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
; t+ b1 o# M; \+ X3 |1 Wfolder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
( ~( G8 d# C F! L* z0 N3) Download template package from FMS volume
4 c4 m0 J, \ p, P4 T7 Pa. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS
, U0 }2 L1 c1 M1 qvolume. $ a6 Q; U0 D& j* p* \
4) Generate delta.xml % ~3 t: I4 y9 P- P& K
a. In this step, the delta.xml is generated using the files in TC_DATA/model
2 d6 ~/ V* c# ]4 ] Gi. Copy model.xml to model_backup.xml 2 I: ~8 r) s3 M5 j* G
ii. Copy model_lang.xml to model_backup_lang.xml
. l# r6 X S% N( f" @, a* Ciii. Consolidate template listed in master.xml to model.xml and model_lang.xml
- @; J& q+ j: {! Y( B; c, ~iv. Load model_backup.xml and model_backup_lang.xml as old model 5 ]# J1 T6 G/ X7 V
v. Load model.xml and model_lang.xml as new model , c" B7 w4 h" c9 R1 K3 ~
vi. Compare and generate delta.xml ; {1 d4 N+ ]/ n% ~7 @" g$ d
2 ?- ?5 V% J4 b0 Q+ N3 @: E0 D) n* x( U( t0 s+ t
b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
|/ g9 ]$ W) i$ N0 V, |from datasets ( except for model.xml and model_backup.xml) ) E+ U! Y0 ?1 z+ X) T+ C
5) Update the database with delta.xml using business_model_updater 8 o$ s! {4 i4 V! J7 N* E% T8 U3 A
a. This is the step where the database is updated with the new data model. The utility - B0 b( Q' B. ?/ e# H
business_model_updater updates the database with the contents delta.xml.
/ ]' t! L2 k. `6 r7 ]b. If the update of the database fails, the contents of database will be extracted into model.xml and
6 ?5 y" A7 i. B1 b0 D+ }; [model_lang.xml 3 n2 z2 U+ ]4 A- u t7 i' i; A
6) Generate CLIPS rules, PLMXML schema file using the extracted file 2 x! M: @) U3 a7 }; Q8 X F1 m
a. The CLIPS rule file is re-generated if any Condition definitions were updated
3 J- Z. }8 O" n( ?# t3 |9 I! Sb. The PLMXML XSD is also re-generated
$ n$ r( c8 O: _/ s7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
& n; ]7 B+ d# ba. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync . b8 \" G! a `' w- U
with the database , D" e3 t( ~) ^3 T3 v
8) Upload log files back to FMS volume & B/ r0 L9 P; A: a- S9 P u
a. All deploy log files are uploaded to the FMS volume
& n0 t- P0 k X) v' ]4 A+ }/ J9) Download log files from FMS volume % a" J/ \) }6 C! i7 K# G
a. BMIDE client downloads log files to the client after deployment completes.
6 B! o/ ]8 S8 o
/ N$ _ m8 ]- D: C% K$ Y3 P- z6 ^ |
|