|
请使用QQ关联注册PLM之家,学习更多关于内容,更多精彩原创视频供你学习!
您需要 登录 才可以下载或查看,没有账号?注册
x
# l& v2 R/ _2 x5 V8 F, u- k! N9 g- A
! V) w1 C b, x1 O
Teamcenter BMIDE热部署原理和步骤
0 o( _/ K: e1 b- {! Q* G N
Let‘s understand these steps in detail.
4 y r6 P& ]2 d' G4 p: o: `, X/ a1) Package & Upload template files to FMS volume / j1 Q/ ^4 v' M, y9 y) C% k: f
a. In this step the BMIDE client will generate the new version of the template package and upload this 5 D) m* N- q, |- O' R
package to FMS volume using a SOA. # Z0 S, A, }. u
2) Download files to TC_DATA/model from dataset (Applicable from Teamcenter 8.3 onwards)
/ L& P9 I9 e0 J1 Q( ~4 ?0 sa. In this step, we download files from the dataset instead of relying on files residing in TC_DATA/model
* w2 c# N/ E* j8 s1 O4 V5 a9 Cfolder. For details see section titled ―Storage of TC_DATA/model files in dataset‖ % {, n$ l2 h1 o, L: o/ T
3) Download template package from FMS volume # B2 m' _ |+ ]- B! q- `1 x" U" O
a. In this step, we download the latest version of the template that the BMIDE client uploaded to FMS $ Z ~! i: ]! t; S: q. E% `
volume.
$ T7 u- M! P1 I8 c6 B* p* d' C4) Generate delta.xml
3 O ?; q$ z, ], [$ Q6 N( O" [a. In this step, the delta.xml is generated using the files in TC_DATA/model , \/ \* q+ J) }" w) i
i. Copy model.xml to model_backup.xml
1 ]! W6 O: _" Mii. Copy model_lang.xml to model_backup_lang.xml
5 U* m7 f' n: q& T$ Kiii. Consolidate template listed in master.xml to model.xml and model_lang.xml
4 o/ i% v! n$ e5 |iv. Load model_backup.xml and model_backup_lang.xml as old model
' w+ K) w, ]$ lv. Load model.xml and model_lang.xml as new model " S5 M" @( ` e3 {0 C; n |9 W. D
vi. Compare and generate delta.xml : e% i4 Q4 s Z
8 R, `: b) F1 ]# e8 y5 i0 f
3 c, d/ y" V% H$ |: s
b. Teamcenter 8.3 onwards, if any errors occur during this step, we restore all files in TC_DATA/model
" ^3 W" k0 O+ g5 [. a' Zfrom datasets ( except for model.xml and model_backup.xml) 5 `# @: H/ G/ t% P( Y
5) Update the database with delta.xml using business_model_updater ( h3 @) A* J! U8 v
a. This is the step where the database is updated with the new data model. The utility $ W7 Y8 K/ L4 B2 X
business_model_updater updates the database with the contents delta.xml.
) O/ u: D+ y' |b. If the update of the database fails, the contents of database will be extracted into model.xml and + @7 o1 ?! i3 c' ]
model_lang.xml ) K! y' ]% D1 J, n; ~" @3 w T
6) Generate CLIPS rules, PLMXML schema file using the extracted file 2 M7 d6 F% ]5 W1 D
a. The CLIPS rule file is re-generated if any Condition definitions were updated
% c' r" v* X z3 p: K& _3 }b. The PLMXML XSD is also re-generated
+ s* M* I0 R$ Y; Q7) Upload files from TC_DATA/model to datasets (Applicable from Teamcenter 8.3 onwards)
( ?$ w" h6 a, Y/ T e" Wa. Finally the contents of TC_DATA/model folder are uploaded back to datasets to ensure it is in sync
' Q- A3 `1 r; f: ` i7 i0 c9 Hwith the database 9 m6 Y" I s- E$ X1 G; N$ o! x
8) Upload log files back to FMS volume & Z) ^# ] n! B
a. All deploy log files are uploaded to the FMS volume 3 y" d6 Q% G0 R" ]
9) Download log files from FMS volume
9 i6 ]$ k; J( b' ~4 u. Ua. BMIDE client downloads log files to the client after deployment completes.
( n- C5 S0 x6 f% ~5 ^
8 k7 f9 N: a' a- k& Q7 }/ k# M |
|