|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
* E, A, D8 m- @/ [' j! }7 W0 X% T* x* T
- {$ k3 w6 ?0 _5 K6 e
Teamcenter BMIDE热部署原理和步骤
; I5 A1 M2 ^( mLet‘s understand these steps in detail. ( z3 g3 t3 {: q- @. {4 y
1) Package & Upload template files to FMS volume ) J# J# p: p. t# S7 N' {
a. In this step the BMIDE client will generate the new version of the template package and upload this
7 e+ ]: J& q8 Q+ `2 Z9 B& g: ]package to FMS volume using a SOA. ( R8 d5 Z: t! o; e- |
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
4 X7 ]! e/ k' G0 Z* o! N3 g$ Pa. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
: w; }& N$ m* E% wfolder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ $ Y: t( X# k2 h' T1 c2 ^
3) Download template package from FMS volume g' H$ l+ y) c$ Q; g
a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS
- [6 v! K4 K: J* T; W$ |" `7 P* E, Hvolume.
/ N( }4 L: w& |% C4) Generate delta.xml
$ P5 W3 i- Y; X+ pa. In this step, the delta.xml is generated using the files in TC_DATA/model 4 M& Q# ?% n" }7 z; u+ S
i. Copy model.xml to model_backup.xml 3 w) \6 m8 O W6 N- K6 R
ii. Copy model_lang.xml to model_backup_lang.xml 5 M1 L* q( G+ s. V" N% `, c4 A
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml
+ t9 R/ _" T, D4 [: d7 ]9 @% e2 Aiv. Load model_backup.xml and model_backup_lang.xml as old model
; ]; s# B1 H4 e( V* ?' m4 x8 gv. Load model.xml and model_lang.xml as new model ) L# ^& y z& b o0 K
vi. Compare and generate delta.xml 3 l2 k4 W& J5 p% z$ p" c
9 Y0 D) Y/ b5 M3 a; u
. o: Y4 U5 [2 v8 Db. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
/ \7 b; B, i( |1 ?, xfrom datasets ( except for model.xml and model_backup.xml)
, ~$ e$ Q; x: D( o5) Update the database with delta.xml using business_model_updater
7 Y* _ d' b8 b- m$ Va. This is the step where the database is updated with the new data model. The utility
& q5 v* \( `9 Hbusiness_model_updater updates the database with the contents delta.xml. 6 p7 d. Q9 Q% g9 g' E4 Y2 i0 T1 Q
b. If the update of the database fails, the contents of database will be extracted into model.xml and ) ?! R5 ?! K, q. Y |' P
model_lang.xml 7 ]) V9 R @/ M$ a+ G3 O; p
6) Generate CLIPS rules, PLMXML schema file using the extracted file . a& D/ v# {" q0 ^7 ?7 N4 S
a. The CLIPS rule file is re-generated if any Condition definitions were updated 9 H. M; A, S+ _# ~! N6 D
b. The PLMXML XSD is also re-generated
0 A+ G3 M$ z* B" x7 e F$ {% n7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) . m$ @3 @9 a7 p8 x' M" x: M: z. o
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync " K" t% r1 H8 J9 m/ N, d0 Y
with the database 5 b3 U" Q' R1 ]' N, |. ]& U
8) Upload log files back to FMS volume - {- b5 f. L2 C: J; i/ i
a. All deploy log files are uploaded to the FMS volume
+ c9 t& |: u/ }# E4 H7 N9) Download log files from FMS volume # A' u7 ^+ m2 [2 |' c U, i2 g) H
a. BMIDE client downloads log files to the client after deployment completes. ; h. R+ M- r6 ~$ s+ Q, v0 L
+ o M, N9 [1 \% d6 w% X3 J7 d6 Z a
|
|