AdminConsole on TomEE

The shared folder should be created with two folders namely conf and lib where the necessary configuration files required for running the AdminConsole application will be placed.

The conf folder should be placed with config and properties files required for AdminConsole application namely,

  1. ac.properties
  2. ac-oipa-jmxconnection-content.xml

This ac-oipa-jmxconnection-content.xml file will have the ports to listen to cycle web servers. Based on count of cycle web managed servers , those many nodes should be created. port of this node should match with port that given in the cycle web arguments.

The lib folder should be populated with all the necessary database drivers and third party jars like

  1. Download aspectj 1.8.10.jar from http://www.eclipse.org/downloads/download.php?file=/tools/aspectj/aspectj-1.8.10.jar
    1. Open aspectj-1.8.10.jar with an unzipping software and retrieve aspectjrt.jar and aspectjweaver.jar from the lib folder.
    2. Copy aspectjrt.jar and aspectjweaver.jar into libs sub-directory.
  2. 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 libs sub-directory.
  3. Copy the database drivers of your database into this directory.
    1. Oracle – The necessary driver, ojdbc8-12.2.0.1.jar, is included in the libs directory of the OIPA Media Pack.
    2. Microsoft SQL Server – download the sqljdbc4.jar library version 4.0  from  https://mvnrepository.com/artifact/com.microsoft.sqlserver/sqljdbc4/4.0 
    3. IBM DB2 – The necessary .jar files (db2jcc4) are included with the purchase of the DB2 software. These files are not available for download. Contact your IT department if you need assistance locating these files.
  4. Use a text editor to open the ac.properties file that you just copied to the server. The ac.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.
  5. The properties setting must match the type of database being used. Please refer to the OIPA System Properties document in the Oracle Insurance Policy Administration E91417_01 Documentation Library on the OTN for a complete list of all properties and allowed values.
    1. application.databaseType
    2. jpa.databasePlatform

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

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

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

Creating Data Sources

tomee.xml is the file where all the data sources, JMS configurations are done. Any data source, which is needed by an application to run, has to be configured in this file. AdminConsole requires ADMINCONSOLEDS datasource to be created.

Sample configuration of all the data sources which are required for AdminConsole to run:

Deploying AdminConsole

Rename the AdminConsole war, which is generated using AC-tomEE profile, from the distribution to AdminConsole.war.

Deploy AdminConsole war in webapps folder of TomEE application server.

Finally start the server and test the deployment with the following url:

  • http://hostname:port/AdminConsole

Note: If you change the context name, use that name in the URL instead of AdminConsole.