|
|
请使用QQ关联注册PLM之家，学习更多关于内容，更多精彩原创视频供你学习！
您需要 登录 才可以下载或查看，没有账号？注册
x
( q2 R; N7 e5 [. L2 L5 f. ?. p0 Z5 }
2 B5 s" N, {; G& z
) y$ j( e/ Q' y( ?
Teamcenter BMIDE热部署原理和步骤
7 h( W) G2 l. M+ Z
Let‘s understand these steps in detail. & Z" d* q Z8 J4 V" d
1) Package & Upload template files to FMS volume ; j: X/ T2 M9 [" C
a. In this step the BMIDE client will generate the new version of the template package and upload this
" [6 C6 \& Z0 o+ c5 Y8 ~package to FMS volume using a SOA.
! w/ ]0 h1 b5 u6 w! f2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards) # ~! z( S! }, b- ]7 y5 q
a. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model ! {4 G, C6 X$ t' @+ R/ @9 c' p" M
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ 9 u8 z# t1 H9 q9 u. @, ~
3) Download template package from FMS volume
2 g4 ]7 |/ X) l: ^( E5 Qa. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS
% h& @+ a0 a9 zvolume. & A0 g! Q0 T7 g1 v9 G( w% ~
4) Generate delta.xml
1 b; D' d4 D( n3 h& Q8 e# D9 R5 Ca. In this step, the delta.xml is generated using the files in TC_DATA/model
# M" D* F! S0 m; P. ji. Copy model.xml to model_backup.xml
o2 e( J) w( [2 Vii. Copy model_lang.xml to model_backup_lang.xml ; A* w) A0 k) @0 V! k3 r
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml
- o9 O9 b8 X, \( eiv. Load model_backup.xml and model_backup_lang.xml as old model
* \$ g( C4 I- j" }/ X, U4 ]4 J- J+ ~8 X8 Uv. Load model.xml and model_lang.xml as new model
/ _6 |6 j) U( \4 [+ r4 V3 Qvi. Compare and generate delta.xml
! J; l: j0 K6 f
5 C" g } W; Z: L+ L7 Y
3 R3 O2 ~% Q1 ~b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model ) B) L# u4 d7 t# W) x# V3 R8 d! N8 M( Y6 g
from datasets ( except for model.xml and model_backup.xml)
. e% D X" m/ J7 b6 J5) Update the database with delta.xml using business_model_updater
9 |9 [6 j6 y( Z2 f3 f0 T) h3 F6 Ha. This is the step where the database is updated with the new data model. The utility - ]7 k/ [* y% T7 v3 q9 \
business_model_updater updates the database with the contents delta.xml.
4 i$ a3 ^$ L; H2 C/ S+ F }1 ^b. If the update of the database fails, the contents of database will be extracted into model.xml and " b/ }# H4 E, u7 ]9 C/ {) e. b
model_lang.xml 1 y) N' g+ N% p" A3 l$ R
6) Generate CLIPS rules, PLMXML schema file using the extracted file
6 C# _7 e$ L, F* s4 f6 O$ La. The CLIPS rule file is re-generated if any Condition definitions were updated $ J% D; @1 F: L g% L
b. The PLMXML XSD is also re-generated
7 m) ~3 v8 ^3 ~: o' c( J7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) ; H8 S* V' S% c8 F0 X
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync , @# t5 L0 P2 @7 E; h5 d
with the database
8 }6 |5 C3 [4 j: D8) Upload log files back to FMS volume 7 @: f* e; d8 g- N- P7 B; v
a. All deploy log files are uploaded to the FMS volume - J% R5 F& {& f' V
9) Download log files from FMS volume % B# Z$ Z! g0 ]
a. BMIDE client downloads log files to the client after deployment completes.
7 q1 B% C0 }4 L5 p7 t9 c: f1 M6 k# ^5 f
|
|
|小黑屋|手机版|PLM之家-企业数智化转型工业软件学习平台
