|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
# y* Q- S6 @( D' r7 k8 J+ D }
. ]6 Y5 r" |6 }' ]+ G% v7 J
6 R! j+ {( g" v m6 U8 p
Teamcenter BMIDE热部署原理和步骤
. w! {. U2 K3 W( a" [Let‘s understand these steps in detail.
# h3 M. B, z: B& j1) Package & Upload template files to FMS volume
- [% {9 B, \8 n# W3 t: |a. In this step the BMIDE client will generate the new version of the template package and upload this
, ^+ }, H: W" l _% A# `& q+ Tpackage to FMS volume using a SOA. ; M4 s5 ~2 j9 u$ d! E" ]
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards) ! [! M4 h) Q; u
a. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model / D6 w' c7 m7 [! g3 Z* @9 b, ^
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
% ?& ], T" p% E" h/ w# V: z3) Download template package from FMS volume
# c( J! e5 J3 L$ J) Ga. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS
/ n0 b! P5 h* n! _+ R3 m) D) Wvolume.
/ v/ S0 C* s7 m7 V4) Generate delta.xml
1 O# L5 D! R8 x9 z0 {5 b$ C) L3 }a. In this step, the delta.xml is generated using the files in TC_DATA/model ( s& T: N Q: [
i. Copy model.xml to model_backup.xml + \- E) j! ]1 T* y7 _
ii. Copy model_lang.xml to model_backup_lang.xml
3 _5 x* a% Z N+ xiii. Consolidate template listed in master.xml to model.xml and model_lang.xml " A) J4 ^+ o7 D" b
iv. Load model_backup.xml and model_backup_lang.xml as old model
9 I- F5 ~( `- D1 s: L+ _$ K% Ov. Load model.xml and model_lang.xml as new model
; c) M3 F" a/ ]8 J/ qvi. Compare and generate delta.xml 5 E% ]& a/ b( A9 {
0 ~1 h9 }. y" p1 _
8 r; y* }5 p1 j* D* Yb. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
0 T1 p) f' x bfrom datasets ( except for model.xml and model_backup.xml)
7 W6 k' X, {" c4 _% A5) Update the database with delta.xml using business_model_updater ( \+ p: d2 Y. c7 q
a. This is the step where the database is updated with the new data model. The utility $ t# U0 G' F; B! s" ~
business_model_updater updates the database with the contents delta.xml.
* V$ O Z; \- n1 B8 m0 S* Pb. If the update of the database fails, the contents of database will be extracted into model.xml and 3 h* C, O6 _# E0 V8 x
model_lang.xml * N7 m: z0 G4 K8 T: P7 T) q
6) Generate CLIPS rules, PLMXML schema file using the extracted file
7 ^) F8 X5 \9 X6 sa. The CLIPS rule file is re-generated if any Condition definitions were updated 6 u3 y/ P% W0 v. r& u/ o# _
b. The PLMXML XSD is also re-generated
* v# m) C5 k; G" X4 b7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
% H+ w7 g. R. u) ]4 S' ~a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
, Q+ ?' a0 o* Y" Wwith the database
6 U" c* X! ]2 b- ^8 e7 F6 M* E; N8) Upload log files back to FMS volume ( k' i L8 o' S/ ?
a. All deploy log files are uploaded to the FMS volume ( {* [! `3 X2 r) q( U i
9) Download log files from FMS volume Y" }/ M4 m. ^5 H1 E% y+ B0 R
a. BMIDE client downloads log files to the client after deployment completes. 9 V2 U8 B0 q! ?- U1 E, ~4 o6 |" [
& ?: n' ^( R/ d9 b1 I3 E) O9 L |
|