3 d! b: T) h. o! Y- i& {) F / J2 \8 k6 F$ A9 O6 ^6 {) M9 SHot deployment (or ―hot deploy‖) 热部署特点: % p4 _- {& a# P; h4 I Deploys directly from the BMIDE to a running test server for verification of custom extensions. ; z' q( u% r& _ Extensions created within the BMIDE can be deployed to a server and visualized with the RAC or thin client . f* C+ Q& Q1 B" v: y
immediately. 0 b* L: k% R% ], F0 e! w/ }' G
Hot deploy requires a user with DBA access. 2 [0 U3 u% N, p% Q$ Y% X% V Supports two-tier and four-tier server configurations. 2 q0 M! C# B/ x' }4 F$ _
Very useful for deploying extensions to a test database. # D4 V4 e0 I7 h: t. z- K4 P9 F Other logged-in users have to log out and back in to see the changes. 6 Y5 Y! p2 B, x7 ~
" j* L/ t G: w, W, X& x
* @# v. o ]% h
Package with BMIDE and deploy with TEM 冷部署特点& K6 s. ^$ k& x! k$ Y+ h
BMIDE wizard packages the template into a feature so that it can be installed to production databases throUGh , p) q2 f m2 T8 s/ T4 R' O3 rTEM. " s" c0 ]. @. z, {: | TEM requires a user with DBA access to install the template. 5 D& Y0 e0 J' L
Requires that the Teamcenter server be stopped, users logged out. * ] T1 H: w Z6 E7 f& v% { Practical for production systems where downtime must be scheduled. ! L7 r/ U+ K: ^5 Q! }$ k Useful when the database update must be coordinated among many sites. + N9 ~6 X; ]- G' R2 _! w. ]( s Used for distributing your template to a partner or customer. * n K/ |; `, c. d 6 d$ T3 N V6 m: v8 `# u$ P4 F% P6 ` [& W; D