OIPA Setup - TomEE

1. Create a directory on the TomEE server to store various configuration files for OIPA (i.e., /%Tomee_Home%/shared or D:\tomee\shared).
2. Create subdirectories inside the directory from Step 1 called conf and lib.
3. Copy PASJava-tomEE.war file from the OIPA distribution zip file into the webapps subdirectory of TomEE server (Ex : /%Tomee_Home%/webapps or D:\tomee\webapps).
4. Rename the war to PASJava.war.
5. Copy the following configuration files from OIPA distribution zip/conf directory into the \shared\conf directory under TomEE server:
   • coherence-cache-config.xml
   • coherence-config.xml
   • PAS.properties
   • EDKeyValue.dat
   • logging.properties
6. Copy the following files from the OIPA distribution zip/lib directory into the shared\lib directory:

   • commons-collections4-4.4-83acfd3.jar

   • commons-logging-1.2-1e55e8f.jar

   • el-api-2.2.jar

   • jakarta.persistence-2.2.3.jar

   • eclipselink-2.7.10.jar

   • spring-instrument-5.3.30.jar

   • jaxws-rt-2.3.0.jar

   • streambuffer-1.5.4.jar

   • policy-2.7.2.jar

   • management-api-3.2.1-b002.jar

   • gmbal-api-only-3.2.0-b003.jar

   • ha-api-3.1.9.jar

   • stax-ex-1.7.8.jar

   • saaj-api-1.3.4.jar

   • Aspect Jars

     • Download aspectjrt 1.9.1 from https://mvnrepository.com/artifact/org.aspectj/aspectjrt/1.9.1

     • Download aspectjweaver 1.9.1 from https://mvnrepository.com/artifact/org.aspectj/aspectjweaver/1.9.1

     • Copy aspectjrt-1.9.1.jar and aspectjweaver-1.9.1.jar into lib sub-directory.

   • Download log4j-1.2.17.jar from https://archive.apache.org/dist/logging/log4j/1.2.17/log4j-1.2.17.jar and copy it to lib sub-directory.

   • Copy the database drivers for your database into lib directory of TomEE (%Tomee_Home%/lib folder).

     • Oracle - The necessary driver, ojdbc11-21.3.0.0.jar, is included in the lib directory of the OIPA Media Pack.

     • Microsoft SQL Server – download the mssql-jdbc.jar library version 9.2.1.jre11 from https://mvnrepository.com/artifact/com.microsoft.sqlserver/mssql-jdbc/9.2.1.jre11

     • IBM DB2 – The two necessary .jar files (db2jcc4 and db2jcc4_license_cu) are included with the purchase of the DB2 software (DB2 Version 11.5). These files are not available for download. Contact your IT department if you need assistance locating these files.

7. Use a text editor to open the PAS.properties file that you just copied to the server. The PAS.properties file contains properties for Oracle, SQL Server and DB2 database types, with the Oracle settings active by default. The inactive settings are commented out with a '#' character at the start of each line. To change a setting, remove the '#' from the required property setting, and insert it at the beginning of the setting you want to de-activate.

8. The properties setting must match the type of database being used.

   • application.databaseType
   • jpa.databasePlatform

   Note: Refer to the latest System Properties document in the Oracle Insurance Policy Administration Documentation Library published on the OHC for a complete list of all properties and allowed values.

9. Identify the default locale in the PAS.properties file. The locale selected will determine the translation that is loaded in the database for OIPA when it launches.

   • application.defaultLocale

10. The property application.encryptDecryptFilePath should point to the EDKeyValue.dat in the shared/conf

11. If using an Oracle or Microsoft SQL Server database, please skip this step. If using a DB2 database, you will need to modify the PAS.properties file to include configuration for case-insensitive searching. Modify the PAS.properties file to include the following line:

    • search.field.text.caseInsensitive=true

12. Use a text editor to open the logging.properties file that you just copied to the server.

    • Edit the path mention for property "java.util.logging.FileHandler.pattern" with new application log location i.e. if application log location is /home/OIPA/logs then set this value as java.util.logging.FileHandler.pattern = %h/OIPA/logs/oipa%u.log. Also same time make sure that directory is created and has r/w permission.

13. Extension classes/jars developed using OIPA extension interfaces should be copied to PASJava-.war/WEB-INF/lib before copying PASJava.war to the war subdirectory. This is required for the extensions to work that an application like OIPA need to run.

Set Environment Variables - TomEE

For Windows deployment we need to create setenv.bat file in the bin folder of extracted TomEE directory.

For Linux deployment we need to create setenv.sh file in the bin folder of extracted TomEE directory.

The following configuration needs to be placed in the setenv.bat file for Windows environment.

Windows Arguments

set CATALINA_OPTS=-Xms128m -Xmx1024m -XX:+UseG1GC
-Dtangosol.coherence.cacheconfig=C:/Servers/TomEE/OIPAInstance/shared/conf/coherence-cache-config.xml
-Dtangosol.pof.config=com-adminserver-pas-web-pof-config.xml
-Dtangosol.coherence.override=C:/Servers/TomEE/OIPAInstance/shared/conf/coherence-config.xml
-Dtangosol.coherence.distributed.localstorage=true
-Djava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.autodiscovery=true
-Dcom.sun.management.jmxremote.port=5588

 

Note: Each argument should be separated by space and not the next line (Enter)               

For Linux Env in setenv.sh

Linux Arguments

export CATALINA_OPTS="-Xms128m -Xmx1024m -XX:+UseG1GC
-Dtangosol.coherence.cacheconfig=/Servers/TomEE/OIPAInstance/shared/conf/coherence-cache-config.xml
-Dtangosol.pof.config=com-adminserver-pas-web-pof-config.xml
-Dtangosol.coherence.override=/Servers/TomEE/OIPAInstance/shared/conf/coherence-config.xml
-Dtangosol.coherence.distributed.localstorage=true
-Djava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.autodiscovery=true
-Dcom.sun.management.jmxremote.port=5588"

Note: To run the application in debug mode, add the following in the setenv file:

Debug Argument
-agentlib:jdwp=transport=dt_socket,address=1043,server=y,suspend=n