|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
; `; Y r& h2 u7 ^) C
. |2 T6 z! x; o) N4 k3 x. H" j
1 @1 t; J- v6 z( m6 x, F0 s
Teamcenter BMIDE热部署原理和步骤
9 @ C5 }% M% U$ n2 P: S( L
Let‘s understand these steps in detail.
( a. ~4 a2 h) |' G% y5 y1) Package & Upload template files to FMS volume
% M: `5 N, Y7 Ha. In this step the BMIDE client will generate the new version of the template package and upload this % }# `9 e1 M1 h$ K& h. }* i
package to FMS volume using a SOA.
1 `+ Q9 E W8 T& n2 H! Y& t2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
3 Y+ _& k. c( K+ s$ F% z2 y/ ?a. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model 4 r- g3 ?/ p* s A* Q& U
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ 6 g: C6 `, p, Q5 [5 r, v
3) Download template package from FMS volume
( U, K5 w$ M, V2 `8 ta. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS
, _/ `/ J' R- T$ D" J! P: X4 d* rvolume.
+ y( b3 R. h4 P4) Generate delta.xml 5 p( D2 u# p) s
a. In this step, the delta.xml is generated using the files in TC_DATA/model
5 f, V. h5 S4 |% j* Ji. Copy model.xml to model_backup.xml
' o) k4 j9 t7 a) z$ f! }! `ii. Copy model_lang.xml to model_backup_lang.xml 7 Q. C! F, A5 z5 j$ ]& q& y4 j
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml ; `* J% a' P8 E, K
iv. Load model_backup.xml and model_backup_lang.xml as old model
$ _( T) d& K! M4 L- F- Ev. Load model.xml and model_lang.xml as new model , L- L! G1 n3 v) H* s
vi. Compare and generate delta.xml
- R. M& `& p2 i/ q/ w$ L7 g; G9 Z1 ]8 n' e6 B W5 {& S! u
8 F! ?4 P( \ r! b @, L6 @+ \( e
b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
) d. j- Y( j6 b7 tfrom datasets ( except for model.xml and model_backup.xml) M+ c3 J8 E6 W+ ~
5) Update the database with delta.xml using business_model_updater
) T( C L( F* q, I/ T e6 `a. This is the step where the database is updated with the new data model. The utility 4 T4 ^, ?$ B3 E/ a/ i# i( `( ^
business_model_updater updates the database with the contents delta.xml. " R) Q' X2 v" P2 u; T
b. If the update of the database fails, the contents of database will be extracted into model.xml and ( N) e9 M- v r% E
model_lang.xml
7 @$ m9 F9 H8 b& P* W% o6) Generate CLIPS rules, PLMXML schema file using the extracted file
* m, J# K; h- {1 }' v9 i, @3 e" i5 xa. The CLIPS rule file is re-generated if any Condition definitions were updated
2 T8 Q: i4 u* b; z- [ v. E5 w& m9 ab. The PLMXML XSD is also re-generated
; Z$ D5 A& G! ^5 h, {) p1 d7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
9 E+ e1 [" ~; B3 t( `a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync 8 r1 `9 ?8 z* Y$ L
with the database - d$ l. X4 R8 p& T# ]6 ^7 ]
8) Upload log files back to FMS volume ! V$ ^, Y6 ?, Y, i
a. All deploy log files are uploaded to the FMS volume
" \" ~4 t% C7 h9) Download log files from FMS volume
8 z$ ]) e2 l9 ?. e- S9 \2 q; Sa. BMIDE client downloads log files to the client after deployment completes. 3 ]( f: t; \0 @% `- B
1 d9 G! N) O; c! F- U; d
|
|