|
|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
×
, @ x$ g9 ?7 C: M9 V3 I
, ?; e. c5 U7 I' j5 |% r/ v4 B
0 K3 Y9 [4 E4 R2 V- m; W" Q
Teamcenter BMIDE热部署原理和步骤
! b, f) g- o' }; D- y
Let‘s understand these steps in detail.
; N& q% N7 p& i1 w1) Package & Upload template files to FMS volume ) F* V9 _# Y! v4 u; Q9 X
a. In this step the BMIDE client will generate the new version of the template package and upload this 7 ]- P' A6 M7 z' r/ t& A+ W: D
package to FMS volume using a SOA.
( F1 ]% t) g3 A/ s c) X! Z1 I2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards) & r4 Q" L8 Z: m+ U1 k
a. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model " m) ]/ h- U h# N5 ~7 ~' V
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ 1 M( m! D5 K( q; l! K- Y7 Z
3) Download template package from FMS volume
, M& h7 u9 {% w& n! L" q3 ^a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS
: |9 v1 ^0 E) I- s! ]volume. # k, V" X- S5 e+ C' J
4) Generate delta.xml ; I9 n( @" `6 ~# i
a. In this step, the delta.xml is generated using the files in TC_DATA/model
8 ^; R+ B& \2 |" l3 n }+ y* Xi. Copy model.xml to model_backup.xml . B" h5 h5 C$ _2 Y
ii. Copy model_lang.xml to model_backup_lang.xml
- T; J2 w: G, _7 a) { kiii. Consolidate template listed in master.xml to model.xml and model_lang.xml . R" z2 p) S" p8 Q$ o+ |- R3 C
iv. Load model_backup.xml and model_backup_lang.xml as old model 7 w1 y% y3 {% S
v. Load model.xml and model_lang.xml as new model
" J( w4 y( |1 D. [. vvi. Compare and generate delta.xml
$ r( d: d- ], _/ I- {- z
) e S8 t! S- y1 u
% E" [+ U @" `8 F3 J2 {b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model ' Z) U1 p. D9 t' d
from datasets ( except for model.xml and model_backup.xml)
' s# `5 e7 h3 _, V. |" }5 q5) Update the database with delta.xml using business_model_updater 1 v d( z6 w; Y
a. This is the step where the database is updated with the new data model. The utility
9 f" X* A. ^9 Kbusiness_model_updater updates the database with the contents delta.xml. * _7 m+ K! v, h6 `. ?
b. If the update of the database fails, the contents of database will be extracted into model.xml and 8 s" J$ z4 ~* V1 _8 L3 C6 x% D
model_lang.xml . c+ N$ q+ m' J+ r
6) Generate CLIPS rules, PLMXML schema file using the extracted file
1 g! c$ _9 Q2 J- v' y. |/ ^' ma. The CLIPS rule file is re-generated if any Condition definitions were updated
# t2 F2 l/ x& H! F+ u" H; fb. The PLMXML XSD is also re-generated ' @6 } n1 i+ p9 Y. P& Y o( X' q
7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
2 a. L# f0 l/ Z2 E4 @5 \a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync 0 P: Q9 Z* m8 x: x. @# o; y% |+ s
with the database
9 `% E* A3 p' X T8 s7 F5 e8) Upload log files back to FMS volume 5 g! [7 d' l/ I( v L' i8 N( A1 ~# v
a. All deploy log files are uploaded to the FMS volume
, e2 y. _. z. R0 B+ ~9) Download log files from FMS volume 6 q S8 j) K5 D0 b! r7 |0 m
a. BMIDE client downloads log files to the client after deployment completes.
. |3 [; r( P" p" L' @
) c1 f0 t/ }* M" k' n! T |
|