|
|
请使用QQ关联注册PLM之家，学习更多关于内容，更多精彩原创视频供你学习！
您需要 登录 才可以下载或查看，没有账号？注册
x
+ A% J& b0 G" X. o* h1 q
! o7 a4 G1 M7 j; ]
6 c t) u1 g0 P( `7 P
Teamcenter BMIDE热部署原理和步骤
- p4 Q9 y: A$ h; Z. KLet‘s understand these steps in detail.
% N% A G" ]0 T9 I1) Package & Upload template files to FMS volume
3 ^ r! v' i: |1 O: c8 \+ ia. In this step the BMIDE client will generate the new version of the template package and upload this 6 Z. e# }* K% w! r
package to FMS volume using a SOA.
/ F3 N$ k. Y6 h6 J3 |2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
* R$ G# b" D0 {- Ra. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model j& ]: v" H( c, F
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ , a) V0 L9 L, C# C c/ w
3) Download template package from FMS volume 0 v. v0 s/ s2 F, z0 a$ c
a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS 5 m$ P {9 ]5 f) @5 O) o; `
volume. : Z2 D9 J( `; t l$ B
4) Generate delta.xml Y, ?5 ?5 N+ ?6 P3 |. D
a. In this step, the delta.xml is generated using the files in TC_DATA/model
* S! y0 g3 _5 b }. ri. Copy model.xml to model_backup.xml 4 H: B1 N! I& I/ a1 _5 Z: M
ii. Copy model_lang.xml to model_backup_lang.xml
0 J: y* B5 `/ @3 \" Niii. Consolidate template listed in master.xml to model.xml and model_lang.xml
) U& ~* l& }5 `7 S# Z2 i* siv. Load model_backup.xml and model_backup_lang.xml as old model 7 p( n" i; k% d1 A6 r! R3 G. Z
v. Load model.xml and model_lang.xml as new model
; Y/ r d; a' ~$ _# Ovi. Compare and generate delta.xml : [4 ]/ W8 l/ ?4 r- V3 l
7 C6 B+ w7 N9 z/ q( Q: A
/ J$ S7 V3 ~# m( yb. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model + _2 _: X) A6 P1 s, A0 q* u% H Z
from datasets ( except for model.xml and model_backup.xml)
0 H7 R' }5 M' l e0 g G- k1 F5) Update the database with delta.xml using business_model_updater 9 A! a8 N) N# A; W% o0 {
a. This is the step where the database is updated with the new data model. The utility & u- v# l/ M. ]' W: a4 r
business_model_updater updates the database with the contents delta.xml. - U3 L9 \6 W, [, W1 `4 \1 L
b. If the update of the database fails, the contents of database will be extracted into model.xml and
/ @# w* t" J# S, {3 tmodel_lang.xml
1 z7 w' ?; r) L6) Generate CLIPS rules, PLMXML schema file using the extracted file # Y9 |! V2 Z* l+ n3 Y4 L3 Z/ D0 d) P
a. The CLIPS rule file is re-generated if any Condition definitions were updated
* d, \" l- N; E) z) z/ c. db. The PLMXML XSD is also re-generated * o' o$ U# u9 j1 c3 `. q7 T! h
7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
+ s/ N7 r2 a2 \$ m& ha. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync $ q5 D8 a( [: O4 r6 Q
with the database / n( p2 a2 H1 {& o
8) Upload log files back to FMS volume ' r7 L3 j$ Z9 K) X
a. All deploy log files are uploaded to the FMS volume ) b8 c& R5 I! }' m) ~1 |- X! j
9) Download log files from FMS volume
' G' ^9 H( r5 j# \( `- Ma. BMIDE client downloads log files to the client after deployment completes.
- ]6 o* r f5 U3 H* B( O% _
5 a6 Y* K0 B/ [8 o* j! S |
|
|小黑屋|手机版|PLM之家-企业数智化转型工业软件学习平台
