Vous êtes sur la page 1sur 19

EcoSys Install Guide Release 8.0.

01

Instructions for EcoSys Installation on Supported Platforms

Document Purpose
This document describes steps for performing the installation of EcoSys software. The contents below are
appropriate for:

• New Installations
• Troubleshooting, existing configurations

The intended audience for this guide is: systems administrators, database administrators, application
administrators, and advanced application users responsible for functional configuration.

Contents
Installation Overview .................................................................................................................................................. 1

Installation Prerequisites and Checklist ....................................................................................................................... 2

Oracle Database Setup ................................................................................................................................................ 4

Microsoft SQL Server Setup ......................................................................................................................................... 5

EcoSys Application Installation .................................................................................................................................... 6

EcoSys Application Requirements for Unix/Linux ........................................................................................................ 6

Configuring Tomcat for EcoSys .................................................................................................................................... 7

Configuring JBoss EAP / WildFly for EcoSys................................................................................................................ 10

Configuring Oracle WebLogic for EcoSys .................................................................................................................... 12

Configuring IBM WebSphere for EcoSys .................................................................................................................... 15

Validate the EcoSys installation ................................................................................................................................. 19

Installation Overview

Overview: This section describes the high level steps for installing EcoSys. You can use this as a
high-level checklist during the installation process.

EcoSys Install Guide, Release 8.0.01 Page 1 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
 Step References in This Document

Validate that you have met all the prerequisites for installing
 Validate Prerequisites
EcoSys in the section Installation Prerequisites and Checklist.

 Create Database Create the EcoSys (“ESFM”) database instance for Oracle or
MS SQL Server.
Install Java and
 Application Server
Install the Java JDK and the preferred application server
platform

 Install EcoSys Files Install the EcoSys application files.

Deploy EcoSys Web Deploy the EcoSys web application on your application server
 Application platform: Tomcat, JBoss EAP / WildFly, WebLogic,
WebSphere
Validate EcoSys Validate the EcoSys installation and that all the features are
 Installation functioning.

Installation Prerequisites and Checklist

EcoSys Install Guide, Release 8.0.01 Page 2 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
Overview: This section describes the prerequisites for installing EcoSys. You can use this as a
pre-install checklist before initiating the installation process. These steps should be completed and
confirmed before the scheduled installation.

# Prerequisite Steps

The EcoSys Environmental Configuration Questionnaire provided by the EcoSys


1 Project Manager should be completed and an EcoSys Server Sizing
Recommendations should be on-hand.
Server Hardware and Operating Systems Installation
2 Refer to the document “EcoSys Supported Platforms” to validate that your server
hardware and operating system versions are supported.
Application Server and Platforms Installation
3 Refer to the document “EcoSys Supported Platforms” to validate that your application
server and version is supported.
Database Server Installation
4 Refer to the document “EcoSys Supported Platforms” to validate that your database server
and version is supported.
Java JDK Installation
5 Refer to the document “EcoSys Supported Platforms” to validate that your Java JDK
version is supported.
Software Media on Server
6 The EcoSys installation package (.zip file) should be downloaded and copied to the
application and database server(s) where the software will be installed.
Software Licenses
7 The EcoSys application license key (FMLicense.properties) should be copied to the
application server.
Passwords and Accounts
Before the installation, the following accounts and passwords will be required:
a. Application server administrator account and password, with either console or
8 remote access available.
b. Database accounts and passwords. If you are pre-creating the database, provide
credentials for the EcoSys database (typically “ESFM”). In lieu of this account, the
database server administrator account and password can be used.
Schedule Staff Availability
During the installation, the following people and roles will need to be available. It is
recommended that the installation consultant be provided with the contact information for
each of these roles at the client:
9 a. System Administrator, with admin-level access to application server(s)
b. Database Administrator, with DBA access to the database servers, and knowledge
of database policies and storage parameters.
c. Project Manager, with authority to make decisions about installation preferences
and the deployment priorities for EcoSys.

EcoSys Install Guide, Release 8.0.01 Page 3 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
Optional: Integration Component - Primavera API and/or SAP Requirements
10  If you are integrating with one of our supported platforms please refer to the appropriate
guide(s) in the Integration folder of Documentation after completing the Installation.

Oracle Database Setup

Overview: Oracle database software installation, creating and initializing the Oracle database for
EcoSys. If using Oracle version 11.2.0.1 please refer to the EcoSys System Admin Topics for
environmental considerations.

1. Installing Oracle Server Software

a) Create a general purpose Oracle database called ESFM that will be used for the EcoSys
(“ESFM”) database installation script below.

b) Supported character sets: WE8MSWIN1252 / AL32UTF8

2. Configuring the Database Scripts and Datasets


a) Locate the database script folder in the EcoSys Release Package
(C:\EcoSys\database\oracle\create)

b) Edit the fm_or_create_db.sql file:

• The top of the script indicates which version the database schema will be after it is run
(ie: 0600_0005_0004_0001). Remember this as it will be needed later.

• The default script is set to drop existing EcoSys tablespaces and delete any existing
EcoSys data files. Ignore if installing for the first time.

• The default schema is fmadmin, if this is changed the following line must be added to
the FMServerSettings.properties file.

oracle.schema=<schema-name>
For example, if your schema name is ‘ecpadmin’

oracle.schema=epcadmin

• By default, the script uses Windows commands to delete the datafiles and create the
tablespaces. If you are running this in a Unix environment comment out the Windows
datafile deletion and tablespace creation blocks and uncomment the Unix ones.

• Change the datafile directory locations of the four “create tablespace” strings to match
your environment.
EcoSys Install Guide, Release 8.0.01 Page 4 of 19
Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
• There is a “connect” command in the script below schema user creation for the
“fmadmin”. If the password or database alias (i.e., @ESFM) is different please make
the appropriate changes.

3. Running Database Scripts

a) Connect to the Oracle instance as SYSTEM or a DBA privileged user and execute the
fm_or_create_db.sql script.

b) Review the log file fm_or_create_db.lst. Ignore errors regarding tablespaces or users that
do not exist. If any other errors occur, please contact EcoSys Technical Support.

c) Refer to the EcoSys Upgrade Guide to determine if you require additional scripts to
upgrade the schema to the proper version.

Microsoft SQL Server Setup

Overview: Microsoft SQL Server database software installation, creating and initializing the SQL
Server database for EcoSys (“ESFM”).

1. Installing Microsoft SQL Server Software


a) Follow the setup steps for installing SQL Server.

b) Required collation: SQL_Latin1_General_CP1_CI_AS

c) Allow remote connections to server: enabled (default)

2. Configuring the Database Scripts

a) Locate the database script folder in the EcoSys Release Package


(C:\EcoSys\database\sqlserver\create)

b) Edit fm_ss_create_db.sql

• Change the two “FILENAME” parameters to match the location of the database data
and log files. Do not change the name of the files (esfm_dat.mdf and esfm_log.ldf).

• The user and login password for “fmuser” is also “fmuser”. If you need to change the
password for “fmuser”, you can do so below the user portion. (ie. CREATE LOGIN
fmuser WITH PASSWORD = 'fmuser',)

3. Running Database Scripts

EcoSys Install Guide, Release 8.0.01 Page 5 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
a) Connect to the MS SQL instance as SA or a privileged user and execute the
fm_or_create_db.sql script.

b) Review messages tab below for errors. Ignore the three module ‘depends on missing
object’ warnings. If any other errors occur, please contact EcoSys Technical Support.

c) Refer to the EcoSys Upgrade Guide to determine if you require additional scripts to
upgrade the schema to the proper version.

EcoSys Application Installation

Overview: Installation of EcoSys application files and configuration

1. Copying Application Files


a) From the extracted EcoSys release package, copy the “EcoSys” folder onto the application
server. This is referred to as “C:\EcoSys” for the rest of this document.

2. Customizing the ‘FMServerSettings.properties’ File


a) Edit the FMServerSettings.properties located in C:\EcoSys\ESFM_HOME\ using a text
editor.

b) Customize the value for the datasource.type and make sure it reflects the database
selected for installation (ST_SQLServer or ST_Oracle)

3. Configuring EcoSys Logging

a) Locate the log4j.properties file in the C:\EcoSys\ESFM_HOME folder and edit the log4j
appender directories below to match your environment and save the file.

log4j.appender.FILE.File=c:/EcoSys/log/ESFM-Application.log

log4j.appender.FILE_PLUGIN_TEST.File=c:/EcoSys/log/ESFM-PluginTest.log

log4j.appender.FILE_PLUGIN_SAP.File=c:/EcoSys/log/ESFM-PluginSAP.log

4. Configuring the Java Max Heap Memory Size

Consult with the EcoSys Server Sizing Recommendations provided after the EcoSys
Environmental Configuration Questionnaire for accurate java heap sizing.

EcoSys Application Requirements for Unix/Linux

EcoSys Install Guide, Release 8.0.01 Page 6 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
Overview: Special considerations related to installing EcoSys on a Unix or Linux platform.

1. Java VM Parameters

a) In order to support some graphics and reporting features the following parameter
is required for the JVM.

-Djava.awt.headless=true

2. WebLogic on Linux/Unix ulimit increase

There are two options for setting the ulimit parameter. Choose one.

a) Add the following lines to /etc/security/limits.conf and reboot the server.

* soft nofile 8192


* hard nofile 8192

b) Add ulimit –n 8192 to the start script of WebLogic.

This setting will increase the number of file descriptors a user can open. Default is 1024 which
may cause “too many open files” error depending on usage.

Configuring Tomcat for EcoSys

Overview: Installing and deploying EcoSys on the Tomcat application server. This install was
done using the Tomcat Windows Service Installer.

Note: When using the instructions below replace any Tomcat versions numbers with the version of
Tomcat that you are using.

1. Java Configuration for Tomcat

a) Navigate \Program FilesApache Software Foundation\Tomcat 8.5\bin and run


Tomcat8w.exe

b) The Java Virtual Machine listed should be the one selected at Java_JDK_Installation.

EcoSys Install Guide, Release 8.0.01 Page 7 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
Tomcat Windows Service Settings

c) Add the two java options in the image above and enter the C:\EcoSys\ESFM_HOME
directory path.

• -DESFM_HOME=C:\EcoSys\ESFM_HOME

d) Set the initial memory pool and the maximum memory pool to the size recommended in the
EcoSys Server Sizing Recommendations document.

2. Adding a JDBC Connection Pool

a) Navigate to \Program Files\Apache Software Foundation\Tomcat 8.5\conf and open the


server.xml with a text editor.

b) Choose the database connection string below that matches the database environment and
copy and paste it above the closing </host> tag.

Note: If using Tomcat 8.5 or above change maxActive setting to maxTotal and maxWait
setting to maxWaitMillis.

For ORACLE:
EcoSys Install Guide, Release 8.0.01 Page 8 of 19
Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
<!-- ESFM webapp Context -->
<Context path="/ecosys" docBase="ecosys" debug="0" reloadable="true"
crossContext="true">
<Resource name="jdbc/esfm" auth="Container" type="javax.sql.DataSource"
maxActive="20" maxIdle="10" maxWait="10000" removeAbandoned="true"
removeAbandonedTimeout="600" logAbandoned="true" username="fmuser"
password="fmuser" driverClassName="oracle.jdbc.OracleDriver"
url="jdbc:oracle:thin:@localhost:1521:global"
accessToUnderlyingConnectionAllowed="true"/>
</Context>

For MSSQL:

<!-- ESFM webapp Context -->


<Context path="/ecosys" docBase="ecosys" debug="0" reloadable="true"
crossContext="true">
<Resource name="jdbc/esfm" auth="Container" type="javax.sql.DataSource"
maxActive="20" maxIdle="10" maxWait="10000" removeAbandoned="true"
removeAbandonedTimeout="600" logAbandoned="true" username="fmuser"
password="fmuser"
driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
url="jdbc:sqlserver://localhost:1433;database=esfm"
accessToUnderlyingConnectionAllowed="true"/>
</Context>

Note: It is important to configure removeAbandonedTimeout to be greater than the maximum of


datasource.read.timeout and datasource.update.timeout located in the
FMServerSettings.properties file.

3. Copying Library Files

a) Copy the intgserver-wrapper.jar and the log4j-1.2.17.jar from the C:\EcoSys\alt\lib folder to
the \Program Files\Apache Software Foundation\Tomcat 8.5\lib folder.

b) Copy the correct database JDBC driver into \Program Files\Apache Software
Foundation\Tomcat 8.5\lib folder.

Customers utilizing the Primavera API please refer to EcoSys P6 Adaptor document in the in the
Integration folder of the EcoSys Release Package Documentation

4. Deploying EcoSys

a) Copy the ecosys.war file from the C:\EcoSys\deploy folder into the \Program Files\Apache
Software Foundation\Tomcat 8.5\webapps folder.

b) Start Tomcat and the ecosys.war file will deploy.

EcoSys Install Guide, Release 8.0.01 Page 9 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
Configuring JBoss EAP / WildFly for EcoSys

Overview: Installing and deploying EcoSys on the JBoss EAP or WildFly application server on
Windows.

1.Java Configuration for JBoss EAP / WildFly

a) Navigate to the application server bin directory and open the standalone.conf.bat file.

b) Set the initial memory pool (Xms) and the maximum memory pool (Xmx) to the size
recommended in the EcoSys Server Sizing Recommendations.

2. Installing the ESFM Overlay

a) Navigate to the C:\EcoSys\alt\deploy\ directory and extract and merge the overlay zip file to
the root folder of the application server.

For Oracle: Use the esfm-jboss-wildfly-overlay-ora.zip


For MSSQL: Use esfm-jboss-wildfly-overlay-sql.zip

3. Configuring ESFM_HOME

a) Navigate to the standalone\configuration folder in the application server installation and


edit the standalone.xml file.

b) Paste the following setting just below the closing </extensions> tag.

<system-properties>
<property name="ESFM_HOME" value="C:\EcoSys\ESFM_HOME"/>
</system-properties>
c) If your ESFM_HOME is not “C:\EcoSys\ESFM_HOME”, edit the property in the
standalone.xml to reflect its correct location on the local filesystem.

4. Configuring the DataSource

a) Navigate to the standalone\configuration folder in the application server installation and


edit the standalone.xml file.

b) Choose DB driver setting from below for the database type that you wish to use and paste
it above the closing </drivers> tag.

For Oracle:
<driver name="ojdbc6" module="com.ecosys.jdbc"/>

For MSSQL:
<driver name="sqljdbc" module="com.ecosys.jdbc">
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>

EcoSys Install Guide, Release 8.0.01 Page 10 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
</driver>

c) Choose Data Source setting from below for the database type that you wish to use and
paste it above the opening <drivers> tag. Modify the bold string to match your
environment hostname, port, database name/instance, user name and password.

For Oracle:

<datasource jndi-name="java:/jdbc/esfm" pool-name="EsfmDS" enabled="true"


use-java-context="true">
<connection-url>jdbc:oracle:thin:@localhost:1521:global</connection-url>
<driver>ojdbc6</driver>
<security>
<user-name>fmuser</user-name>
<password>fmuser</password>
</security>
<timeout>
<idle-timeout-minutes>15</idle-timeout-minutes>
</timeout>
</datasource>

For MSSQL:

<datasource jndi-name="java:/jdbc/esfm" pool-name="EsfmDS" enabled="true"


use-java-context="true">
<connection-url>jdbc:sqlserver://localhost:1433;database=esfm</connection-url>
<driver>sqljdbc</driver>
<security>
<user-name>fmuser</user-name>
<password>fmuser</password>
</security>
<timeout>
<idle-timeout-minutes>15</idle-timeout-minutes>
</timeout>
</datasource>

Note: It is important to configure idle-timeout-minutes to be greater than the maximum of


datasource.read.timeout and datasource.update.timeout located in the
FMServerSettings.properties file.

3. Copying Library Files

a) Copy the correct database JDBC driver into the correct directory in the application server

For Oracle: copy the ojdbc6.jar file to com\ecosys\jdbc\main

For MSSQL: copy the sqljdbc4.jar file to com\ecosys\jdbc\main

Customers utilizing the Primavera API please refer to EcoSys P6 Adaptor document in the in the
Integration folder of the EcoSys Release Package Documentation

EcoSys Install Guide, Release 8.0.01 Page 11 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
4. Deploying EcoSys
a) Copy the ecosys.war file from the C:\EcoSys\deploy folder into the \standalone\deployments
folder of the application server.

b) Start the application server.

Configuring Oracle WebLogic for EcoSys

Overview: Installing and deploying EcoSys on Oracle WebLogic application server on Windows.

A WebLogic domain should be created and it is recommended to have a managed server with
corresponding machine set up for EcoSys within WebLogic. Ensure Nodemanager is installed and
running as this is required for a managed server.

Pre-requisite for SQL Server: (skip if connecting to Oracle database)

If you are connecting to an MS SQL database make sure to download Microsoft’s SQL Server
Driver from MSDN. The driver used is sqljdbc4.jar.

Copy the sqljdbc4.jar to the WebLogic installation directory, under the ${WL_HOME}/server/lib
folder

Navigate to C:\Oracle\Middleware\Oracle_home\oracle_common\common\bin and open the


commEnv.bat with a text editor.

Note: In later versions of WebLogic the file to use is commExtEnv.cmd

Find the following lines below and add the bold text:

@rem set up WebLogic Server's class path and config tools classpath
Set
WEBLOGIC_CLASSPATH=%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar
;%WL_HOME%\server\lib\weblogic.jar;%WL_HOME%\server\lib\sqljdbc4.jar;

Restart the Weblogic AdminServer.

EcoSys Install Guide, Release 8.0.01 Page 12 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
1. Configuring the WebLogic Managed EcoSys Server

a) Log in to the WebLogic console and navigate to Environment > Servers and select the
Managed Server you created to run EcoSys. Click on the Server Start tab. Select Lock
and Edit.

b) Modify the Java Home of the server to a supported JDK.

c) Set the class path as follows. Change C:\EcoSys\ to the location where the extracted
EcoSys release package resides.

WL_HOME/server/lib/weblogic.jar;C:\EcoSys\alt\lib\intgserver-
wrapper.jar;C:\EcoSys\alt\lib\log4j-1.2.17.jar

Note: The classpath delimiter is a semi-colon for Windows and a colon for Linux.

c) Set the initial memory pool (Xms) and the maximum memory pool (Xmx) to the size
recommended in the EcoSys Server Sizing Recommendations.

-DESFM_HOME=C:\EcoSys\ESFM_HOME -Xms2048m -Xmx2048m

d) Click Save and then Activate Changes.

WebLogic Server Start Tab

EcoSys Install Guide, Release 8.0.01 Page 13 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
2. Configuring the DataSource

a) From the WebLogic console navigate to Services > Data Sources and click Lock and
Edit. Select New and Generic Data Source.

b) Name the DataSource esfm and set the JNDI Name to ‘jdbc/esfm’

Select Oracle or MS SQL Server depending on your database type and click Next.

• For ORACLE
Select the “Oracle Driver (Thin) for Service Connections, Versions: 9.0.1 or later
Leave the defaults on the next page and hit Next.

• For MSSQL
Select the Microsoft’s MS SQL Server Driver (Type 4) Versions: 2005 and later
Leave the defaults on the next page and hit Next.

c) Enter the database name, host name, user and password (default is fmuser/fmuser) for
the database connection and select Next.

d) Click the Test the connection button and if successful, click Next.
Select the EcoSys server as the target for the data source. Click Finish and Activate
Changes.

e) Modify the Inactive Connection Timeout to 600 seconds from WebLogic admin console.
This setting can be found at the following location.

Services > Data Sources > esfm > Connection Pool > Inactive Connection Timeout
(Under Advanced Settings)

Note: It is important to configure Inactive Connection Timeout to be greater than the


maximum of datasource.read.timeout and datasource.update.timeout located in the
FMServerSettings.properties file.

f) Go to Servers > Control Tab and start the EcoSys server. If node manager is not installed
and running you will receive an error. Contact your WebLogic Administrator to make sure it
is set up properly.

3. Deploy the EcoSys Application

a) From the WebLogic console, click on Deployments and then select Lock and Edit.

b) Click on Install and navigate to the ecosys.ear file in the extracted EcoSys release
package and select Next. Leave the defaults and click Next.

c) Select the EcoSys server as a target for the application and click Next. Click Finish
and Activate Changes. Start the EcoSys deployment.

EcoSys Install Guide, Release 8.0.01 Page 14 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
Configuring IBM WebSphere for EcoSys

Overview: Installing and deploying EcoSys on IBM WebSphere Application Server

1. Setting the Java Heap Size and JVM Arguments

a) From the WebSphere Application Server Administration Console expand Servers >
Server Types and select WebSphere Application Servers. Select the server that will
run EcoSys and under Server Infrastructure expand Java and Process Management
and select Process Definition. Under Additional Properties select Java Virtual
Machine.

b) Set the initial heap size and max heap size according to your EcoSys Server Sizing
Recommendations.

c) Add the following to the Generic JVM Arguments


-DESFM_HOME=C:\EcoSys\ESFM_HOME

2. Create user/password for the database java connection

a) Expand Security and select Global Security then expand Java Authentication
and Authorization Service and select click on J2C authentication data.
Click on New.

EcoSys Install Guide, Release 8.0.01 Page 15 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
b) Enter the fmuser credentials created during database creation. Default is
fmuser/fmuser.

3. Adding EcoSys as a Shared Library on WebSphere

a) Expand Environment and select Shared Libraries.

b) Select the shared library scope and select New.

c) Enter a name ecosys for the shared library name.

In the Classpath text box add the required library files as following:

C:\EcoSys\alt\lib\intgserver-wrapper.jar
C:\EcoSys\alt\lib\log4j-1.2.17.jar

Then click OK and Save.

4. Adding JDBC Provider in WebSphere – Microsoft SQL Database

a) Expand Resources and JDBC, then select JDBC Providers.

b) Select the Scope of the JDBC provider and select New

c) Select SQL Server as the database type, Provider type as Microsoft SQL Server JDBC
Driver and implementation type as Connection pool data source and click Next.

EcoSys Install Guide, Release 8.0.01 Page 16 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
d) Enter the directory location of the sqljdbc4.jar file which is saved as WebSphere variable
${MICROSOFT_JDNC_DRIVER_PATH}. Click Next, and Finish.

5. Adding the Data Source in WebSphere – Microsoft SQL Database

a) Expand Resources > JDBC > Data Sources and select New.
Enter the information below and click Next.

Datasource Name: ecosys


JNDI Name: jdbc/esfm

b) Select an existing JDBC provider and select the JDBC provider created in the previous
step. Click Next.

c) Enter the database specific details for the data source and select Next.

d) Enter the security aliases information as shown below.

Component-Managed authentication alias, choose: fmuser


Mapping-configuration alias: leave as ‘none’
Container-managed authentication alias, choose: fmuser
Click Next, click Finish, and click Save.

e) Check the box next to the datasource and click on the Test Connection button.

6. Setting Default Isolation Level (Microsoft SQL Database)

a) Make sure the default isolation level of the data source is set to 2 as per this article:

http://www-
01.ibm.com/support/knowledgecenter/SS7JFU_7.0.0/com.ibm.websphere.express.iseries.doc/i
nfo/iseriesexp/ae/cdat_isolevel.html?cp=SS7JFU_7.0.0%2F2-8-7-2-2

Skip to the section on Deploying the EcoSys Application on WebSphere below.

7. Adding JDBC Data Source in WebSphere – Oracle Database

a) Expand Resources and JDBC, then select JDBC Providers.

EcoSys Install Guide, Release 8.0.01 Page 17 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
b) Select the Scope of the JDBC provider and select New.

c) Select Oracle as the database type, provider type as Oracle JDBC Driver and
implementation type as Connection pool data source and click Next.

d) Enter the directory location of the ojdbc6.jar file. Click Next, and Finish.

8. Adding the Data Source in WebSphere – Oracle Database

a) Expand Resources > JDBC > Data Sources and select New.
Enter the information below and click Next.

Datasource Name: ecosys


JNDI Name: jdbc/esfm

b) Select an existing JDBC provider and select the JDBC provider created in the previous
step. Click Next.

c) Type the URL for your database, replace the server name, port number and SID to match
your database settings. jdbc:oracle:thin:@servername:port:databaseName and hit Next.

d) Enter the security aliases information as shown below.

Component-Managed authentication alias, choose: fmuser


Mapping-configuration alias: leave as ‘none’
Container-managed authentication alias, choose: fmuser
Click Next, click Finish, and click Save.

e) Check the box next to the datasource and click on the Test Connection button.

9. Deploying the EcoSys Application on WebSphere

a) Expand Applications > Application > WebSphere Enterprise Applications and select
Install. Select Browse and choose the ecosys.ear (from C:\EcoSys\deploy), and hit Next.

b) Leave the default Fast Path selected and hit Next.

c) Check the box for Precompile JavaServer Pages files and select Next. Check the box to
map the module to the server and hit Next, and Finish.

EcoSys Install Guide, Release 8.0.01 Page 18 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.
d) Once the application has finished deploying, click Save at the bottom.

10. Map Resource References to Resources.

a) Finally, select the ecosys enterprise application and select shared library references
under references.

b) Check the ecosys application and click the Reference Shared Libraries button.

c) Highlight the available ecosys library and click the arrow so it moves to the selected box.
Click OK.

d) Check the EcoSys Application module and click the Reference Shared Libraries
button.

e) Highlight the available ecosys library and click the arrow so it moves to the selected box.
Click OK.

f) Click OK and Save.

11. Start the EcoSys Application

a) Expand Applications > WebSphere enterprise applications.

b) Check the box next to ecosys and click on the Start button.

Validate the EcoSys installation

After the application service has been started navigate to the EcoSys Application using the URL -
http://<host>:<port>/ecosys . Contact EcoSys Support if any errors are encountered after the
upgrade and include the upgrade script log files as well as the ESFM-Application.log file.

EcoSys Install Guide, Release 8.0.01 Page 19 of 19


Copyright © 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.
Confidential and Proprietary Information.