Configuring JBoss EAP / WildFly for EcoSys - EcoSys - Version 8.6 - Installation - Hexagon PPM

EcoSys Installation

PPMProduct
EcoSys
PPMCategory_custom
Installation & Upgrade
Version_EcoSys
8.6

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

Java Configuration for JBoss EAP / WildFly

  1. Navigate to the application server bin folder and open the standalone.conf.bat file.

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

Installing the ESFM Overlay

  1. Navigate to the C:\EcoSys\alt\deploy folder 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

Configuring ESFM_HOME

  1. Navigate to the standalone\configuration folder in the application server installation and edit the standalone.xml file.

  2. Paste the following setting right below the closing </extensions> tag.

    <system-properties>
    <property name="ESFM_HOME" value="C:\EcoSys\ESFM_HOME"/>
    </system-properties>

  3. If ESFM_HOME is not “C:\EcoSys\ESFM_HOME”, edit the property in the standalone.xml to reflect its correct location on the local file system.

Configuring the DataSource

  1. Navigate to the standalone\configuration folder in the application server installation and edit the standalone.xml file.

  2. Depending on the database platform being used, paste the appropriate database driver text below 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>
    </driver>

  3. Choose Data Source setting from below for the database type that being used and paste it above the opening <drivers> tag. Modify the bold string to match the 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>

    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.

Copying Library Files

  1. 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

    If Primavera API is being used please refer to EcoSys P6 Adapter Installation document.

Deploying EcoSys

  1. Copy the ecosys.war file from the C:\EcoSys\deploy folder into the \standalone\deployments folder of the application server.

  2. Start the application server.