06c_-_V6R2013x_-_R20xxx-to-R2013x_Upgrade_v1
3D S .C O M ? D a s s a u l t S y s t èm e s | C o n f i d e n t i a l I n f o r m a t i o n | 4/16/2013| r e f.: 3D S _D o c u m e n t _2012
ENOVIA V6 Upgrade
From V6R20xxx GA to V6R2013x
3
D S .
C
O
M
?
D
a
s
s
a
u
l
t
S
y s
t è
m
e s
|
C o
n
f
i d
e
n
t
i a
l
I
n f
o r
m
a t
i o
n
|
4/
16
/
20
1
3
|
r e
f.:
3
D
S
_D o
c
u
m
e n
t
_2012Purpose of this document This document describes the steps followed to upgrade an ENOVIA V6
environment from V6R20xxx GA to V6R2013x We will expose the case where a Data Model Customization of Product modeler has been deployed on the V6R20xxx GA level and therefore must be migrated
3D S .C O M ? D a s s a u l t S y s t èm e s | C o n f i d e n t i a l I n f o r m a t i o n | 4/16/2013| r e f.: 3D S _D o c u m e n t _2012Definitions DMC –Data Modeler Customization is an interactive tool for customizing the ENOVIA VPM V6 data model STORE –repository for content inside of ENOVIA V6The following example shows an upgrade process using WebSphere and DB2. The steps are analogous when upgrading Oracle or Tomcat or SQL Server or WebLogic
3
D S .
C
O
M
?
D
a
s
s
a
u
l
t
S
y s
t è
m
e s
|
C o
n
f
i d
e
n
t
i a
l
I
n f
o r
m
a t
i o
n
|
4/
16
/
20
1
3
|
r e
f.:
3
D
S
_D o
c
u
m
e n
t
_2012Procedure Overview Export Database from old environment Install new DB environment Create new server instance in new database Check tablespace sizes Import old database into new one DMC Tools backup on R20xxx system Install V6R2013x Live Collaboration Platform Upgrade MQL command on V6R2013x system Install other centrals DMC Tools on V6R2013x to Migrate each prefix in customization DMC Tools on V6R2013x to Migrate each environment Save and publish changes Mask migration Deploy and compile Rebuild 3D Indexes (incremental if <= V6R2012)
3
D S .
C
O
M
?
D
a
s
s
a
u
l
t
S
y s
t è
m
e s
|
C o
n
f
i d
e
n
t
i a
l
I
n f
o r
m
a t
i o
n
|
4/
16
/
20
1
3
|
r e
f.:
3
D
S
_D o
c
u
m
e n
t
_2012
Database stuff
DB2-specific but same procedure applies for Oracle Export DB2 v9.x R20xxx database via db2 backup command db2 backup db $DATABASE_NAME Install DB2 v9.7 software and license Create new server instance in DB2 v9.7Check tablespace sizes to ensure 2 GB of overhead for migration tool Catalog new database db2 "catalog tcpip node $DB2_NODE_NAME remote $BASE_HOST_NAME server $DB2_SVCE_NAME"db2 "catalog database $DB2_NODE_NAME as $DB2_NODE_NAME at node $DB2_NODE_NAME authentication server"Import DB2 v9.x database into DB2 v9.7 via db2 restore command db2 drop db $DATABASE_NAME db2 restore db $DATABASE_NAME NOTE:
3D S .C O M ? D a s s a u l t S y s t èm e s | C o n f i d e n t i a l I n f o r m a t i o n | 4/16/2013| r e f.: 3D S _D o c u m e n t _2012Backup of R20xxx DMC Customization We make the assumption that a backup of the DMC has been done on the V6R20xxx level via the DMC tool:
3D S .C O M ? D a s s a u l t S y s t èm e s | C o n f i d e n t i a l I n f o r m a t i o n | 4/16/2013| r e f.: 3D S _D o c u m e n t _2012Migration procedure (1/7)
DB upgrade + ENOVIA Centrals install
1.Create following folders: /home/data/V6R2013x
2.Old MATRIX-R bootstrap file to new directory
3.In this new path, install V6R2013x ENOVIALiveCollaborationPlatorm
4.From /home/data/V6R2013x/server/[binary]/code/bin, ?MQL>upgrade ;
5.Install the other centrals you had in the original installation ?NOTE: If upgrading from a CBP-only installation to V6R2013 or higher, the MXIDENT table must be created via mql>transition –see the
ProgramDirectory for details and be warned that this will take a LONG time
3
D S .
C
O
M
?
D
a
s
s
a
u
l
t
S
y s
t è
m
e s
|
C o
n
f
i d e
n
t
i a
l
I
n f
o r
m
a t
i o
n
|
4/
16
/
20
1
3
|
r e
f.:
3
D
S
_D o
c
u
m
e n
t
_2012Schema Migration Steps
?The database schema must be upgraded next ?Note that there are several manual steps depending on which version of ENOVIA V6 you are moving from and too ?
Please refer to the Official Documentation in the Installation and Administration Section -> ENOVIA -> Live Collaboration Server -> Installing the Server -> Upgrading the Database after Installing a New Version of Software
3
D S .
C
O
M
?
D
a
s
s
a
u
l
t
S
y s
t è
m
e s
|
C o
n
f
i d
e
n
t
i a
l
I
n f
o r
m
a t
i o
n
|
4/
16
/
20
1
3
|
r e
f.:
3
D
S
_D o
c
u
m
e n
t
_2012
Migration procedure (2/7)
DMC migration (if previous install had VPLM customizatio Updating the runtime view : the idea is to migrate the PRODUCT customization with the help of the DMC tool Start the DMC tool (DMCTool.sh) from /home/data/V6R2013x/server/Apps/VPMMultiDiscipline/V6R2013x/scripts:In Tools / Options of DMC tool, make sure that the "working folder" matches with the V6R20xxx backup folder Run the DMC migration step :
3D S .C O M ? D a s s a u l t S y s t èm e s | C o n f i d e n t i a l I n f o r m a t i o n | 4/16/2013| r e f.: 3D S _D o c u m e n t _2012Migration procedure (3/7)
DMC migration Move manually the customizations before saving your environment (from left to right)Save your environment ("VPM" here)
3
D S .
C
O
M
?
D
a
s
s
a
u
l
t
S
y s
t è
m
e s
|
C o
n
f
i d
e
n
t
i a
l
I
n f
o r
m
a t
i o
n
|
4/
16
/
20
1
3
|
r e
f.:
3
D
S
_D o
c
u
m
e n
t
_2012Migration procedure (4/7)
DMC migration Publish your modifications
3
D S .
C
O
M
?
D
a
s
s
a
u
l
t
S
y s
t è
m
e s
|
C o
n
f
i d
e
n
t
i a
l
I
n f
o r
m
a t
i o
n
|
4/
16
/
20
1
3
|
r e
f.:
3
D
S
_D o
c
u
m
e n
t
_2012Migration procedure (5/7)compile and verify Last step: JPO compilation from MQL window:
MQL> compile prog * force ; This done by checking following points:each.err file must be empty each.log should not contain any "ERROR" pattern Semantic Relation migration must have been completed w/o errors JPO compilation errors must not show any errors Applicative tests from Wintop :create & save new data with contextual design (to check new SR infra)Re-use V6R20xxx data and update them (ex: assembly update)Applicative tests from Webtop (ex: Engineering Central):create new data (ex: create part & Publish to Enterprise)reuse/update existing V6R20xxx data (ex: transfer control)
3D S .C O M ? D a s s a u l t S y s t èm e s | C o n f i d e n t i a l I n f o r m a t i o n | 4/16/2013| r e f.: 3D S _D o c u m e n t _2012Mask Migration
1.
mkdir –p /tmp/previous/vplm/mask/DEFAULT and copy the R20xxx default mask into /tmp/previous/vplm/mask/DEFAULT 2.
mkdir –p /tmp/custo/vplm/mask/DEFAULT and copy the R20xxx customized mask into /tmp/custo/vplm/mask/DEFAULT 3.
generate the V6R2013x default mask for each custo (DAVCAIRFPRODUCT, …) with VPLMPosMaskGenerator.sh :mkdir –p /tmp/current/vplm/mask/DEFAULT cd /home/data/B82GA7/V6R2013x/matrix/Apps/VPMMultiDiscipline/V6R2013x/scripts VPLMPosMaskGenerator.sh –d /tmp/current/vplm/mask/DEFAULT DAVCAIRFPRODUCT …4.run VPLMPosMaskMerger.sh tool from V6R2013x code mkdir –p /tmp/merged/vplm/mask/DEFAULT cd /home/data/B82GA7/V6R2013x/matrix/Apps/VPMMultiDiscipline/V6R2013x/scripts VPLMPosMaskMerger.sh –m DEFAULT –p /tmp/previous/ /tmp/current/ /tmp/custo/ -d /tmp/merged/This step will merge all the masks into /tmp/merged/vplm/mask/DEFAULT 5. Copy the merged masks in STAGING area /home/data/B82GA7/V6R2013x/matrixRMI/STAGING/ematrix/WEB-INF/classes/vplm/mask/DEFAULT 6.Generate the DEFAULT.SecurityMask (containing your custo)cd /home/data/B82GA7/V6R2013x/matrix/Apps/VPMMultiDiscipline/V6R2013x/scripts VPLMPosMaskCompiler.sh –m DEFAULT –d /tmp/merged This step will generate DEFAULT.SecurityMask file into /tmp/merged
This operation generates some 235 errors; don’t take care of these errors.
7.Copy the generated DEFAULT.SecurityMask file in STAGING area
/home/data/B82GA7/V6R2013x/matrixRMI/STAGING/ematrix/WEB-INF/classes/vplm/mask
3D S .C O M ? D a s s a u l t S y s t èm e s | C o n f i d e n t i a l I n f o r m a t i o n | 4/16/2013| r e f.: 3D S _D o c u m e n t _2012Deploy Now, rebuild the war/ear file and redeploy into the Application Server Be careful to then recompile all programs using the server version of mql:set context user creator;compile program force *;Note: the compile might have error messages:Other types of errors need to be reported to Technical Support
3D S .C O M ? D a s s a u l t S y s t èm e s | C o n f i d e n t i a l I n f o r m a t i o n | 4/16/2013| r e f.: 3D S _D o c u m e n t _2012Indexes and STOREs Exalead Full-Text Search Just ensure that the new installation points to the old index directories or rebuild all STOREs (plmx, STORE, Image Store, etc)Use system to ensure that the metadata points to the original R20xxx location of the content 3D Indexes Incremental build only if previous version was V6R2012 or above Full build required if previous version was 3D S .C O M ? D a s s a u l t S y s t èm e s | C o n f i d e n t i a l I n f o r m a t i o n | 4/16/2013| r e f.: 3D S _D o c u m e n t _2012