|
|
请使用QQ关联注册PLM之家，学习更多关于内容，更多精彩原创视频供你学习！
您需要 登录 才可以下载或查看，没有账号？注册
x
! A1 E& H2 ~" y" k, l& N) J/ b
3 W7 S, ]- c+ D: n
0 ^& L; W3 r; {5 Y
Teamcenter BMIDE热部署原理和步骤
1 P. O' G( ^. _1 u9 ]' @$ V! V
Let‘s understand these steps in detail. . i0 C' k) h9 o$ o' p# R% {
1) Package & Upload template files to FMS volume
9 h5 F- I! `3 f0 k2 J, Ra. In this step the BMIDE client will generate the new version of the template package and upload this
* q% g4 F4 {0 B7 a* Ipackage to FMS volume using a SOA. : t) {1 _1 s* F% d+ `4 V5 Q
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
1 C9 ?1 b2 g* w+ k! Ha. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
! U# P" [9 c7 m+ m# qfolder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ $ |/ r1 h, l: Z% j0 e2 e
3) Download template package from FMS volume
8 o; [ Z V; T2 a5 f0 {# |* @$ h! ^a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS 6 Y7 b: u _6 \8 x& J0 q
volume.
# Z0 A( {, w3 A' d4) Generate delta.xml 3 ~0 V) v) m% K2 ^' @
a. In this step, the delta.xml is generated using the files in TC_DATA/model / e0 [5 Z* ?; u Q8 E3 j4 b! n
i. Copy model.xml to model_backup.xml
: |* `" |. k" d& @$ fii. Copy model_lang.xml to model_backup_lang.xml 1 @5 J7 O0 P9 E& E# h7 u
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml - q2 Y0 W& N1 b' d% }) N. P
iv. Load model_backup.xml and model_backup_lang.xml as old model
$ F' J W' X( P' ^+ mv. Load model.xml and model_lang.xml as new model
0 Y9 q2 |" [& Y: a2 I; \vi. Compare and generate delta.xml 2 B; H5 H) `; X5 ]
' ?. p: T+ H% ?: k9 {8 d y
4 v8 ^* Y$ {$ A- f' T6 X# a7 G2 Cb. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
8 @+ x6 E R2 u, A& efrom datasets ( except for model.xml and model_backup.xml) 0 x( e8 w8 `1 P3 t
5) Update the database with delta.xml using business_model_updater + N% @ w3 q4 [7 x- W2 K& c
a. This is the step where the database is updated with the new data model. The utility
1 d; S$ V( I- y; U7 G4 R1 Ebusiness_model_updater updates the database with the contents delta.xml. 3 b7 F2 Q7 a O6 I7 F1 H1 H1 s
b. If the update of the database fails, the contents of database will be extracted into model.xml and
9 f/ W* B! {+ d Jmodel_lang.xml 9 G/ e. b! C& a+ t6 N# o# S
6) Generate CLIPS rules, PLMXML schema file using the extracted file % j) K3 b* g) ~, y
a. The CLIPS rule file is re-generated if any Condition definitions were updated
2 B! |: k& P* lb. The PLMXML XSD is also re-generated . H" Z1 X& c2 z/ B }1 T1 I. B
7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) - U* a4 g1 {' M$ p8 }& h. ^0 f- J: [
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
' R" w7 u! Q9 u- nwith the database
8 B3 P' J/ z4 @% p9 X: F8) Upload log files back to FMS volume 7 S0 O+ U1 L. g x6 G
a. All deploy log files are uploaded to the FMS volume ' p$ S$ T' I, P2 ` W
9) Download log files from FMS volume 5 d+ ]9 X2 O7 P0 x( N
a. BMIDE client downloads log files to the client after deployment completes.
) z9 A5 K! T2 E' C, B" P6 l
8 f5 f& `6 z$ j }4 U |
|
|小黑屋|手机版|PLM之家-专注工业软件生态建设，大模型CAD创新生态
( 沪ICP备2026005248号 )
