|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
6 h: J9 B, U8 c' ~- X, N+ g/ i
3 k5 s+ t; G# b+ Y; `8 t6 A9 B: j, C, V+ ~0 L& j8 M9 ^# i0 I& a
Teamcenter BMIDE热部署原理和步骤
6 R ^) _6 l; ILet‘s understand these steps in detail.
% c! X* Y$ }6 X7 F8 U# Y. K! g1) Package & Upload template files to FMS volume
3 u! i# r6 F" w6 x" o& n4 ^4 Xa. In this step the BMIDE client will generate the new version of the template package and upload this ! L9 s6 b, E5 z$ \1 k d) n5 W2 q: l
package to FMS volume using a SOA. - ]- U( R! N. E2 w* e) W; f- j
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
; p8 V7 p+ l0 f5 X: g* r8 d0 Ka. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
7 h$ n: h. \0 L" P9 k7 xfolder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ , w9 d' W* }4 D; x9 o0 i6 Z8 k
3) Download template package from FMS volume
" |! v2 O5 Y! G7 L/ Z% }a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS
+ Q3 t$ Z' o4 Evolume.
. _. {% \% L. L" \2 e1 |7 s# |4) Generate delta.xml 7 [; ?6 C3 o' L/ c# p
a. In this step, the delta.xml is generated using the files in TC_DATA/model % s; d$ c/ @& m- t2 |! W
i. Copy model.xml to model_backup.xml
. Q3 l" T& Q4 ~ e4 m1 gii. Copy model_lang.xml to model_backup_lang.xml
' F- L. E% S. r: s% Ciii. Consolidate template listed in master.xml to model.xml and model_lang.xml
! {6 i& K8 e4 H+ E3 C* Z- Niv. Load model_backup.xml and model_backup_lang.xml as old model + N/ ?# l! b3 f( U# \
v. Load model.xml and model_lang.xml as new model
: T0 q3 R) l. d3 k" ]* mvi. Compare and generate delta.xml 2 Q }( t& t5 ^- Z3 T8 \
. V( K1 j h) o2 w1 j& p( @1 }$ A. S2 n) A; U8 }
b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model 5 H8 p# x9 Y1 d9 x* t6 @6 r: J2 l
from datasets ( except for model.xml and model_backup.xml)
" x6 \9 i( C; }1 K9 e& s2 n3 ^5) Update the database with delta.xml using business_model_updater ( @& j8 {& _" C* X
a. This is the step where the database is updated with the new data model. The utility
7 P9 _, _; m3 V4 ~& Qbusiness_model_updater updates the database with the contents delta.xml. k/ w) p* `1 N' t. A3 J4 D
b. If the update of the database fails, the contents of database will be extracted into model.xml and
( Y+ G& F9 i% o4 t1 U. |model_lang.xml
}6 w$ i0 S: M6) Generate CLIPS rules, PLMXML schema file using the extracted file
. o# u6 X" o* I, b- ta. The CLIPS rule file is re-generated if any Condition definitions were updated
1 j6 Z/ t3 D+ N: M/ T; Q/ t+ Kb. The PLMXML XSD is also re-generated
( j0 Z2 N4 T( C/ o7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) - P- e! \: V, P% s7 F1 f" U5 [
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
+ w5 `8 i1 h4 `; ?with the database
$ n0 O0 G+ J8 h' E- b6 b5 v0 Q: H8) Upload log files back to FMS volume
0 `7 J z3 W& F. ja. All deploy log files are uploaded to the FMS volume % M4 Q0 X8 [- T P2 b4 B
9) Download log files from FMS volume 2 w6 s& o2 o! i/ t" R, s) u; R
a. BMIDE client downloads log files to the client after deployment completes. 6 r4 h: M" M: B; I" \- V+ ^
* m' W q+ w/ X: ^6 F) \
|
|