|
|
请使用QQ关联注册PLM之家，学习更多关于内容，更多精彩原创视频供你学习！
您需要 登录 才可以下载或查看，没有账号？注册
x
4 `8 |0 v3 N1 X" R- e
1 w! R8 Q1 H* k1 p$ R5 O( W; m
Teamcenter BMIDE热部署原理和步骤
+ B+ {! H4 v6 p2 Q! y
Let‘s understand these steps in detail.
7 n% J0 f8 {1 T: q7 t' l" L1) Package & Upload template files to FMS volume
. Z! P, o, `" a& Wa. In this step the BMIDE client will generate the new version of the template package and upload this $ a% s7 I, Z1 K A
package to FMS volume using a SOA.
; N$ s' U/ J; v2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards) 6 ?+ j$ `. X% |( \& A
a. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
* d0 L' |" R# q0 R7 q& \folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ ( R/ Z# I' |3 ^. H3 a
3) Download template package from FMS volume
( X. s- c" _2 `, k8 L8 L4 Ma. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS % P$ l( A1 a6 F2 g3 E* S ?0 [
volume. L" W7 Y) Z4 i& C6 ]
4) Generate delta.xml 3 O3 I; R8 g; i& P, h
a. In this step, the delta.xml is generated using the files in TC_DATA/model / O* X6 _# Y7 D0 ], X- v2 s2 g! d
i. Copy model.xml to model_backup.xml
; h" O! \/ o Gii. Copy model_lang.xml to model_backup_lang.xml
/ ? n& V1 q$ I. ?) xiii. Consolidate template listed in master.xml to model.xml and model_lang.xml . y3 m @9 @4 Z) }
iv. Load model_backup.xml and model_backup_lang.xml as old model : D$ O0 a* _+ V2 v% t$ l6 _# w
v. Load model.xml and model_lang.xml as new model
( U8 o* s/ q. a. ^) V6 s1 e0 Uvi. Compare and generate delta.xml * S& N( s% a- \# w2 [6 m1 A3 j, [" U
, _7 `; o8 k; V8 n/ h% m8 [4 s% F6 L% U7 d' [3 q# X- I
b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
1 s9 Z: b$ h( ^. }from datasets ( except for model.xml and model_backup.xml)
* K( J' [- R2 M) ? K7 \# b' j- j5) Update the database with delta.xml using business_model_updater 2 }' k& e' N# p/ s+ H" l7 u
a. This is the step where the database is updated with the new data model. The utility
s- ^) N' D& X) n- gbusiness_model_updater updates the database with the contents delta.xml. & `0 T3 j+ T* M
b. If the update of the database fails, the contents of database will be extracted into model.xml and
8 M. H8 z3 T) i2 N: J8 \model_lang.xml
( K* A+ d# Y4 K: C/ I; I" C2 M6) Generate CLIPS rules, PLMXML schema file using the extracted file 8 ~ x. h C c1 {9 I7 y
a. The CLIPS rule file is re-generated if any Condition definitions were updated
0 z! v5 Y* H$ Q6 Q$ V3 P% lb. The PLMXML XSD is also re-generated
# D. D. ~9 ^0 _+ U& u) ^7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) 9 ~) D' ~1 _8 N, o7 U/ b x, C
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
- I1 |3 C9 [$ o( O# Kwith the database ( g# r& s) U# D! V% w
8) Upload log files back to FMS volume
, _7 R4 c# c: }5 Pa. All deploy log files are uploaded to the FMS volume
1 ?# F' f1 C* B: v0 K" s5 K& l9) Download log files from FMS volume % ~) `7 @4 \; Z+ w( Q1 z; D( X5 [
a. BMIDE client downloads log files to the client after deployment completes.
' ~9 m1 e+ `7 v: ~! d
* P* a; G% P" G0 {( a7 G/ K |
|
|小黑屋|手机版|PLM之家-企业数字化转型工业软件学习平台
