|
|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
4 a7 M' M8 a2 h0 t: b) z
, ~# ]* ?& J: N+ e: c4 q
5 S+ H+ ^2 V4 W: B; K8 O
Teamcenter BMIDE热部署原理和步骤
: ~! |9 r! s1 C
Let‘s understand these steps in detail.
, P" D2 ^/ h, S. N+ g+ Y/ V; B1) Package & Upload template files to FMS volume
6 v6 c3 K; m8 n# Z8 [6 A+ F) Pa. In this step the BMIDE client will generate the new version of the template package and upload this
) T! j( V& V& z, i4 ypackage to FMS volume using a SOA.
4 h! u1 s( v4 I& o2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
7 x! m0 u6 K! v. q7 `2 ~a. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model # `- w( i& ^: c: O/ o0 \
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
$ J( i2 D' y, l# v' l* W7 [3) Download template package from FMS volume
n1 G$ `/ W: @& R, N$ p! Ta. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS # R$ t; y0 y: X. s* T. \
volume. : k1 C+ m8 H& N& L" }5 Q! e( ]
4) Generate delta.xml
/ O) o/ C- ?) h5 c6 w* _a. In this step, the delta.xml is generated using the files in TC_DATA/model
8 F' ?4 d: P+ q. q [i. Copy model.xml to model_backup.xml
1 O1 k: r9 q7 Z X: V5 Z7 j& }ii. Copy model_lang.xml to model_backup_lang.xml ! |& n" a8 ~9 o$ J; @
iii. Consolidate template listed in master.xml to model.xml and model_lang.xml 4 O" I" @ b D
iv. Load model_backup.xml and model_backup_lang.xml as old model
9 Y. i. ~3 \. P& h; Sv. Load model.xml and model_lang.xml as new model
* j2 ~: o5 q# j+ c A. jvi. Compare and generate delta.xml
$ [* K/ e4 Q0 n M1 N7 n1 ]% O) A0 m/ m! N$ ^
8 G: i$ V% Q1 [9 lb. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model ; b$ N5 s; N' L
from datasets ( except for model.xml and model_backup.xml)
) X: J4 O0 Z& B P0 f" X5 r" X5) Update the database with delta.xml using business_model_updater % M- y) L/ @/ p; E* F* _/ B
a. This is the step where the database is updated with the new data model. The utility ' F; b" ]1 v/ S: O9 B3 A
business_model_updater updates the database with the contents delta.xml.
0 ~7 ?+ {; i1 R4 l# N4 ^- S* ?7 g/ Ib. If the update of the database fails, the contents of database will be extracted into model.xml and + b7 n0 Z1 \; G/ j9 P. ~6 Z
model_lang.xml
& `7 e8 [+ P |# e! Q/ o1 x N6) Generate CLIPS rules, PLMXML schema file using the extracted file # D2 W' x a8 P4 H9 S% }) A
a. The CLIPS rule file is re-generated if any Condition definitions were updated
4 ~% ^3 N: ^: f5 l* w# \* }+ Lb. The PLMXML XSD is also re-generated 5 [. k. w' O3 z8 ^* \9 G4 \
7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
4 ^# a n, N& ]" }a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync r1 \& r8 t5 W# @, d0 r
with the database
9 T& N$ A+ ]4 _8 G8) Upload log files back to FMS volume
0 {8 q" ^6 X& l; }1 @6 ~6 \$ ca. All deploy log files are uploaded to the FMS volume
, |0 P1 b3 f* w# m8 h/ z; i9) Download log files from FMS volume 2 a, i7 p" N! h8 S4 P @
a. BMIDE client downloads log files to the client after deployment completes. 3 w3 N. o. }. r( Y' z' M
h% ^( c5 f. h- B+ b& [. V# M |
|