|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
* P% e( o# R8 D2 e( J \3 |1 o# Q+ I5 Y4 q9 f, L4 K
0 a7 e8 O( c7 {0 I" `7 }
Teamcenter BMIDE热部署原理和步骤
7 k$ j4 U: C& I* h' H& LLet‘s understand these steps in detail. 9 E" K! Z# k: K. L
1) Package & Upload template files to FMS volume
8 j( j- u+ |, `a. In this step the BMIDE client will generate the new version of the template package and upload this
1 a2 ^3 F( O# T$ Dpackage to FMS volume using a SOA. ( `% j) C1 W `. h5 y* H0 f+ _
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
! x' h" |9 L! O# g" ?( U( p! l+ J3 l0 _a. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
8 S6 Q$ F: T4 @$ q- a4 x7 Vfolder. For details see section titled ―Storage of TC_DATA/model files in dataset‖
8 W: z9 C# d% ?; Y3 A3) Download template package from FMS volume
& ]3 E, t3 a4 ]) n, z5 M4 l7 r5 R5 la. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS
/ [2 F8 x' o6 }& y# gvolume. - \. p) M9 |5 ?' x2 x
4) Generate delta.xml
7 S+ g1 H! ^: o# _( x6 p% p1 l% oa. In this step, the delta.xml is generated using the files in TC_DATA/model
7 e' L$ e* p+ }9 ` |& H0 li. Copy model.xml to model_backup.xml 1 l- y/ f) C7 O* J4 y1 M4 T
ii. Copy model_lang.xml to model_backup_lang.xml
1 S" o# a W* [8 u! niii. Consolidate template listed in master.xml to model.xml and model_lang.xml
2 s+ M3 \1 V6 V: b7 N- Div. Load model_backup.xml and model_backup_lang.xml as old model + D& {5 M% Q' k1 i# V
v. Load model.xml and model_lang.xml as new model
$ `* J8 e0 v% I0 ^2 evi. Compare and generate delta.xml : J) A+ }. {6 z
! ~' E$ F) \) ^( L; k+ i6 n, m" V9 R. \: H9 M' |2 W4 G* s/ \+ g
b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
: v( F2 X1 Y& Q, N/ yfrom datasets ( except for model.xml and model_backup.xml)
* p. i; p! ?2 q5) Update the database with delta.xml using business_model_updater
5 U% C/ H& }& d4 u/ N, V! ta. This is the step where the database is updated with the new data model. The utility 3 R5 H# i) R+ r* R& j! e
business_model_updater updates the database with the contents delta.xml.
' r, q( C* j' d1 u' T$ \b. If the update of the database fails, the contents of database will be extracted into model.xml and
2 C: F7 a+ i+ X# q+ Kmodel_lang.xml 7 `5 l2 T& t' L, D, e
6) Generate CLIPS rules, PLMXML schema file using the extracted file
" U8 {" u! c" w5 t s: X7 Y" Aa. The CLIPS rule file is re-generated if any Condition definitions were updated # u! n! h* I* F; a; Z/ k
b. The PLMXML XSD is also re-generated
0 y8 w1 m# O$ G, T7 G8 ~0 Q7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards) 2 X+ h9 ^ }$ w2 h4 Z2 {: z/ b
a. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
+ h7 [7 b+ K- @& Ewith the database
2 r) c; H0 M" O# l! u5 b7 C8) Upload log files back to FMS volume
$ D. \8 j4 H$ J6 za. All deploy log files are uploaded to the FMS volume
2 i" L2 k2 U+ o" z) C. o9) Download log files from FMS volume
% G; m6 ^: I, X0 D" Q9 Ya. BMIDE client downloads log files to the client after deployment completes.
+ K! g) \( R8 U) v
& c. _" b1 J7 C0 V( X+ i; @ |
|