V6R2012 PLM Express Installation - SQL 2008

August 5, 2018 | Author: Alin Cristian | Category: Microsoft Sql Server, Web Application, Installation (Computer Programs), Databases, Backup
Share Embed Donate


Short Description

Download V6R2012 PLM Express Installation - SQL 2008...

Description

V6R2012 PLM Express for Windows Server 2008 Prerequisites: 

JDK 6 x64 (update 24 minimum) m inimum)



Microsoft .NET Framework 3.5.1 (use Administrative Tools > Server Manager > Features to enable, and be sure to update to SP1 using Windows Update )



Apache Tomcat 6.x (x64)



SQL Server 2008 Workgroup, Standard or Enterprise (also need SP1)



SQL Native Client 10.0 April 2009 Update (required if SQL Server 2008 is installed on a different system)

SQL Server 2008

Select “New SQL Server stand-alone installation or add features to an existing installation”

Install:

Change the Named Instance (in this case, MSSQL):

Select “Use the same account for all SQL Server services” and select the “Network Service” account.

Change the Named Instance (in this case, MSSQL):

Select “Use the same account for all SQL Server services” and select the “Network Service” account.

Select the Collation tab and change the collation for the Database Engine and Analysis Services:

Select Mixed Mode under Account Provisioning and specify password for the “sa” login (e.g. Sa123456).

Add Current User to list of SQL Server administrators:

After installation, install SQL Server 2008 SP1. For x64, use SQLServer2008SP1-KB968369-x64-ENU.exe (minimum).

After installing, from a command prompt, run odbcad32.exe. Under System DSN, confirm SQL Server Native Client 10.0 is available. If the Enovia PLM Express Server will be installed on a different system than the SQL Server, you will need to download and install this separately on the Enovia PLM Express Server. Ensure that it is the same version as that on the SQL Server .

Confirm you can connect to SQL Server using the command line:

sqlcmd –S \MSSQL –U sa –P

SQL Server 2008 Tuning

Memory Configuration Ideally, SQL server memory should be limited to 50-70% of system RAM . From a command prompt: sqlcmd –S \MSSQL –U sa –P 1> use master  2> go Changed database context to 'master'. 1> exec sys.sp_configure N'show advanced options', N'1'  2> reconfigure with override 3> go Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 1> exec sys.sp_configure N'max server memory (MB)', N'8192'  2> go Configuration option 'max server memory (MB)' changed from 2147483647 to 8192. Run the RECONFIGURE statement to install. 1> reconfigure with override 2> go 1> exec sys.sp_configure N'show advanced options', N'0'  2> reconfigure with override 3> go Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 1> quit 

Max degree of parallelism for SQL Server Skip this step if you wish SQL Server to use all available processors. For more info, see: http://msdn.microsoft.com/en-us/library/ms181007.aspx To reduce the degree of parallelism to 2 (recommended for vmware images): sqlcmd –S \MSSQL –U sa –P 1> use master  2> go Changed database context to 'master'.

1> exec sys.sp_configure N'show advanced options', N'1'  2> reconfigure with override 3> go Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 1> exec sys.sp_configure N'max degree of parallelism', N'2'  2> go Configuration option 'max degree of parallelism' changed from 0 to 2. Run the RECONFIGURE statement to install. 1> exec sys.sp_configure N'show advanced options', N'0'  2> reconfigure with override 3> go Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 1> quit 

Set “Auto create statistics” and “Auto update statistics” on Tempdb to false: sqlcmd -S \MSSQL –U sa –P 1> use master  2> go Changed database context to 'master'. 1> alter database tempdb set auto_create_statistics off with no_wait  2> go 1> alter database tempdb set auto_update_statistics off with no_wait  2> go

Run odbcad32.exe. Under System DSN, select SQL Server Native Client 10.0 and click Finish. NOTE: This must be configured on the Enovia V6 Server.

Define the data source and select Finish.

Test the data source:

Install JDK (x64) – minimum update 24 required. Install the JDK (x64) to the default installation and set the JAVA_HOME environment variable to the proper version used by Tomcat:

Creation of DSLicSrv.txt file The DSLicSrv.txt file must exist on t he Enovia PLM Express server and client systems and must be located in: Windows 7/2008 Server: C:\ProgramData\DassaultSystemes\Licenses Windows XP: C:\Documents and Settings\All Users\Application Data\DassaultSystemes\Licenses

The contents of this file contains the path and por t number to the license servers(s): Twix:4085

Install ENOVIA PLM Express Server

Provide the settings for SQL Server 2008 (specify the password for sa and the SQL Server Name):

Select the option to Set up the Team Startup Projects:

Select Install:

Verify the enovia login screen is accessible:

Install ENOVIA 3DIndexing

Select Install:

Once installed, run the Index S ecurity Administration tool shortcut on the desktop:

Select Run > Run Now:

When completed, Select Start > Quit and select “Yes” to Save the file.

Run the Data reindexation batch shortcut on the desktop (this will start the 3DI ndexing processes in the background):

Verify the results of the 3DIndexing batch using the IndexationReport.html shortcut:

The Data reindexation batch should be run reg ularly, ideally after new data has been added to VPM. This can also be scheduled on a reg ular basis via the Task Scheduler on the Enovia Server .

Run the Warutil.bat  The warutil.bat needs to be run whenever a new central is installed, or when there is a configuration change that needs to be applied to the Tomcat web server.

Installing ENOVIAIntegrationExchangeFramework  Before installation, enable the Guest account. This is required for Enovia Collaboration for Microsoft Server.

Extract the ENOVIAIntegrationExchangeFramework-V6R2012.Windows64.zip and run the setup.

Run the setupV6.exe. For the ENOVIA Installer folder, select the InstallLauncher folder.

The ENOVIA server install directory for PLM Express is installed at C:\enoviaV6R2012\code. Change the directory:

Install ENOVIACollaborationforMicrosoftServer

Extract the ENOVIACollaborationforMicrosoftServer-V6R2012.Windows64.zip and run the setup.

The ENOVIA server install directory for PLM Express is installed at C:\enoviaV6R2012\code. Change the directory:

Select the vplm vault:

After installation:

Under C:\enoviaV6R2012\code\STAGING\ematrix\properties, modify the ief.properties file in a text editor:

Change line that reads: #webservice properties mcadIntegration.Server.McsUrl = to: #webservice properties mcadIntegration.Server.McsUrl =http://veesixx64:8070/enovia

Save the changes. Run the WARUTIL from \code\win_b64\code\command:

After running the WARUTIL, you w ill need to run the following MQL commands to configure the users for MSF: set context user creator; modify product MSF add person ; modify product CPF add person ; modify role ‘MicrosoftOffice User’ assign person ;

quit; Alternatively, you can assign the licenses and assign the role in the Enovia web interface.

Enabling Preview tab with the ENOVIAWindowsExplorerIntegration – see Client Installs below Add the following lines to the enovia.ini in the C:\ enoviaV6r2012\server\win_b64\code\bin and the C:\enoviaV6R2012\studio\win_b64\code\bin: MX_SERVICE_PATH=C:\tomcat\webapps\enovia\WEB-INF\classes MX_SERVICE_ADMIN=http://veesixx64:8070/enovia

AFTER running the WAR Utility and deploying it to C:\Tomcat\Webapps, copy the x86 and x64 folders of  the ENOVIA3DLiveExamine directories (x64 and x86) to the C:\Tomcat\webapps\enovia\components folder.

Run the following statements in MQL (ensure Tomcat is r unning): set context user creator; compile program *plmprovider* force; compile program *framework* force; quit;

Check that the following files are created in the C:\Tomcat\webapps\enovia\WEB-INF\classes directory:

Client Installs NOTE – The client installations for Catia and 3DLive are similar to previous versions and are not covered in this document. Also, unlike previous versions of V6, you cannot install Express and Full/High-End versions of the client software to the same directories. They must be installed in different directories.

Client Installation for Microsoft Office Integration and Desktop Search

Requires MSF (DSLS) and CPF (DSLS) licenses.

The ENOVIAMicrosoftOfficeIntegrationandDesktopSearch-V6R2012.Windows64.zip will need to be installed on the clients. Ensure that you have no other applications running during the install and that any work is saved as you will need to reboot to complete the installation. Extract the ENOVIAMicrosoftOfficeIntegrationandDesktopSearch-V6R2012.Windows64.zip and run the setup.

After the installation and reboot, you will need to configure the appropriate users.

Assign the MSF and CPF licenses and assign the ‘MicrosoftOffice User’ role to the user(s) from the Enovia

web interface. Alternatively, run the following MQL commands on the Enovia server: set context user creator; modify product MSF add person ; modify product CPF add person ; modify role ‘MicrosoftOffice User’ assign person ;

quit; Once configured, users should be able to log in from the ENOVIA V6 shortcut on t heir desktop, or from the ENOVIA V6 ribbon/toolbar from their Office applications.

Client Installation – ENOVIA Windows Explorer Integration If the ENOVIAMicrosoftOfficeIntegrationandDesktopSearch is installed, you do not need to install this. Extract the ENOVIAWindowsExplorerIntegration-V6R2012.Windows64.zip and run the setup.

Backup and Restore A minimum backup consists of the SQL database (metadata) and the cor responding Enovia store (which contains the documents). Both must be synchronized and backed up at the same time. If custom changes have been made to the Enovia installation loadpoint, this should be backed up as well. Enovia V6 should not be in use while the backup is in progress (ie the Tomcat se rvice should be stopped prior to a backup). In the event that the Enovia server fails and need to replaced, the components detailed in the installation procedure must be reinstalled completely – this also includes any custom changes made to the Enovia installation after the initial Enovia install. Once completed, a restore of the SQL and associated Stores can be performed.

Backing up the SQL Database:

Select Start > Microsoft SQL Server 2008 > SQL Server Management Studio. Login:

Expand Databases, select the Enovia Database, right-click and select Tasks > Backup

Specify a backup destination and file and select OK.

Backing up the store:

Determine the location of the store. From the C:\enoviaV6R2012\code\win_b64\coe\bin, run system.exe. Login as creator.

Select Find. Search for Store. Select Find.

Double-click on “Store plmx” and note the path.

The path contains the physical files associated with the metadata and needs to be backed up. You can use winrar, or winzip to backup this directo ry.

Restoring the SQL Database:

Select Start > Microsoft SQL Server 2008 > SQL Server Management Studio. Login:

Expand Databases, right-click and select Restore Database. Provide the name of the database and be sure to specify the location of the backup file.

Restoring the store:

Simply extract the contents of the backed up store to the original location.

If the Enovia server hostname and/or SQL Server has changed: Update the System DSN, SQL Server Native Client 10.0 connection (only necessary if SQL Server has changed). Be sure to test the connection. Run the WARUTIL.bat to redeploy the Enovia PLM Express Server to Tomcat as documented earlier. Either update or create the necessary connection string in the V6R2012 clients.

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF