|
|
请使用QQ关联注册PLM之家，学习更多关于内容，更多精彩原创视频供你学习！
您需要 登录 才可以下载或查看，没有账号？注册
x
* f' C8 f& F7 e
- z$ t/ x9 r6 l" E, K- L) O7 r0 S$ y8 r9 e
Teamcenter BMIDE热部署原理和步骤
# {4 Z: c* g9 DLet‘s understand these steps in detail.
/ f" e; J$ [2 z* t! m7 f/ E% W5 Z1) Package & Upload template files to FMS volume - ]. e/ a) b4 O( ?, B8 `
a. In this step the BMIDE client will generate the new version of the template package and upload this
5 f% c# P$ d4 `, g6 Ppackage to FMS volume using a SOA. # d& t5 e6 | P- O% x) N( w
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
" s7 w: r8 X8 n8 j7 C" ya. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
5 V, V/ S; Q5 N A. I; O- Efolder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ 3 Q3 o8 l4 K2 |$ j
3) Download template package from FMS volume ) Z7 [% q* m" B! O! Q% q5 \, Y
a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS + Q3 [2 D1 s3 A/ d \+ h8 B# J9 t8 s
volume.
5 N- }) y$ `* u' _; d4) Generate delta.xml ' F2 G& l0 ~' V4 @
a. In this step, the delta.xml is generated using the files in TC_DATA/model w! a7 J$ g' y' n+ z( P
i. Copy model.xml to model_backup.xml
2 P2 H: V- c$ |5 J$ |4 W* `$ N; X) Gii. Copy model_lang.xml to model_backup_lang.xml 5 {2 ?" L. U6 x7 u+ ]: o/ Q) O
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml 4 ]- o0 p. p/ z) x, s) u
iv. Load model_backup.xml and model_backup_lang.xml as old model
5 y. Y6 C6 r0 T9 Y: J4 Zv. Load model.xml and model_lang.xml as new model 8 d- F- O/ c ]% w
vi. Compare and generate delta.xml
7 V6 O3 G; {& q* S( q: f5 ]$ B# E ^/ Z2 a7 z0 A, q
. p4 u* a1 q, e/ S/ p2 W" Jb. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model 6 l( B {: f6 l7 \
from datasets ( except for model.xml and model_backup.xml) 5 @. J6 p* A# e: \0 F( d
5) Update the database with delta.xml using business_model_updater - I" d/ S& L+ v. C7 h2 z( p$ n
a. This is the step where the database is updated with the new data model. The utility
8 l: i3 v0 B+ S9 gbusiness_model_updater updates the database with the contents delta.xml.
0 F- _/ |- z& R* Yb. If the update of the database fails, the contents of database will be extracted into model.xml and
9 P" q; m1 J P9 n0 A/ P4 g3 Zmodel_lang.xml 5 Z) d' h1 e7 f) m4 u
6) Generate CLIPS rules, PLMXML schema file using the extracted file / h* }7 ^7 s5 k% i( R2 X
a. The CLIPS rule file is re-generated if any Condition definitions were updated
: A: \7 a% }) Q: J6 qb. The PLMXML XSD is also re-generated : Z" P/ N% [7 P% m) w5 J4 z
7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) 8 Q; \2 N5 l4 k0 f1 r
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
4 s9 J( }' f# x( n- ]with the database $ L X+ r y$ K1 ~7 W* Y
8) Upload log files back to FMS volume
1 n' n4 F3 G1 p: r' da. All deploy log files are uploaded to the FMS volume
' T2 i! x/ w; Q# |( n: V! H2 W1 K9) Download log files from FMS volume
; x G) n" B( g2 N. C' ha. BMIDE client downloads log files to the client after deployment completes.
' J8 ^+ a2 L3 n0 j# C1 h" a3 {* d, z; J% x
|
|
|小黑屋|手机版|PLM之家-企业数智化转型工业软件学习平台
