|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
! v7 u$ U& n% f, o
# y6 r& N7 x! @7 q+ t$ i9 Z
" E& _, r3 h* [) ^
Teamcenter BMIDE热部署原理和步骤
N6 F3 _9 U+ A u T
Let‘s understand these steps in detail.
$ `. ~: b8 i0 O4 ]2 }" p# f1) Package & Upload template files to FMS volume 8 S3 {' v; ~. D5 V' M
a. In this step the BMIDE client will generate the new version of the template package and upload this
0 Z8 @3 Y/ ~" K5 V- {package to FMS volume using a SOA.
1 M$ W/ L: Z/ d; J8 Y. J% i& X+ ~2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
! p& }$ j' ~, _( Q& Ca. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model & O0 \; i2 \- {2 W
folder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ # o4 |6 ~/ I( I, n# c* |, j
3) Download template package from FMS volume 7 x9 j# B& r% H) ?' ?* v6 s' M6 S
a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS 4 c0 N" Y" g" {0 ]: @
volume.
0 C/ P5 b7 D3 N: O4) Generate delta.xml
6 e, y7 K1 y- P- @1 Qa. In this step, the delta.xml is generated using the files in TC_DATA/model 9 ?/ a' U$ y e9 N. O0 q) @% A
i. Copy model.xml to model_backup.xml
1 Z2 u9 A# ?/ @& z2 m- G" Cii. Copy model_lang.xml to model_backup_lang.xml
, ^+ |/ T: J1 x; ^/ @* m9 a% [$ Eiii. Consolidate template listed in master.xml to model.xml and model_lang.xml 2 G# ?+ V9 g7 U) u
iv. Load model_backup.xml and model_backup_lang.xml as old model
0 v4 Q7 e! B5 i; f& Pv. Load model.xml and model_lang.xml as new model " A j+ ~# t& `: w" R- @+ [; j
vi. Compare and generate delta.xml
0 J# z6 u+ K$ |, i& S
7 j6 t' e% } j) O: e8 D3 I7 M% p \3 w$ N* H- d
b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
0 b8 t8 }& S) g$ ifrom datasets ( except for model.xml and model_backup.xml) B% a& X% I/ W
5) Update the database with delta.xml using business_model_updater
, y, i, T! b) e @+ r5 p- F* ua. This is the step where the database is updated with the new data model. The utility
5 F+ R% x" T' m$ y" Bbusiness_model_updater updates the database with the contents delta.xml.
/ u2 @$ E4 D- I7 ~- P8 Ab. If the update of the database fails, the contents of database will be extracted into model.xml and
1 F! n1 G" }; N$ Hmodel_lang.xml 3 _; s' T9 ]: D+ ]) O" I
6) Generate CLIPS rules, PLMXML schema file using the extracted file # [$ H6 M. ^2 d
a. The CLIPS rule file is re-generated if any Condition definitions were updated
0 X, P& H& b/ v: ~" F* A X/ Y! i0 fb. The PLMXML XSD is also re-generated
. d) ^. d$ B8 {/ M7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
* W7 Z0 R7 \! W0 i9 y5 h+ o) x$ Ka. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
( M) k& ]6 ]; b& L9 z* Bwith the database
9 U9 V! I0 q! h2 g* c6 f9 O. [8) Upload log files back to FMS volume
4 |9 t& g+ N/ G) G. V0 B+ M) |a. All deploy log files are uploaded to the FMS volume
* q; |7 a. Z0 E8 _" J% s% ]9) Download log files from FMS volume 1 R/ R6 D D) B. V- p, y
a. BMIDE client downloads log files to the client after deployment completes.
( z" \/ ~7 Z3 j, ~
3 F1 R6 u1 S' B) h. R |
|