Download and Configure Admin Console

  1. Download the domain binaries as mentioned in the Pre-Requisites section of this document.

  2. Copy the following configuration files from AdminConsole distribution zip/conf directory into externallibs/ac_shared/conf directory:

    1. ac.properties

      Identify the default locale in the ac.properties file. The locale selected will determine the translation that is loaded in the database for Admin Console when it launches. The default setting is English.

      1. application.defaultLocale

      2. If using an Oracle database, please skip this step. If using a DB2 database, you will need to modify the ac.properties file to include configuration for case-insensitive searching:

        • Modify the ac.properties file to change the following line from the default setting of "false" to "true": search.field.text.caseInsensitive=true

    2. ac-oipa-jmxconnection-content.xml

      Note: The ac-oipa-jmxconnection-content.xml file will have the ports to listen to cycle web servers. Based on the count of cycle web-managed servers, those many nodes should be created.

      Port of this node should match with the port given in the cycle web arguments.

    3. Update the oipa.url with the PAS application URL

      Example: oipa.url=http://localhost:9090/PASJava

    4. Update the cycle.baseURI with the cycle application URL

      Example: cycle.baseURI=http://localhost:8085/CycleService

    5. Update the service.url with the Service layer Application URL

      Example: service.url=http://localhost:5050/PASService

  3. Copy the following files from the ADMINCONSOLE distribution zip/libs directory into the externallibs/ac_shared/lib directory.

    • commons-logging-1.2-1e55e8f.jar

    • el-api-2.2.jar

    • log4j-api-2.18.0.jar

    • jakarta.persistence-2.2.3.jar

    • eclipselink-2.7.10.jar

      Note: Rename all the jars without version names.

    • Example:

      • commons-collections4.jar

      • commons-logging.jar

      • log4j.jar

      • eclipselink.jar

      • jakarta.persistence.jar

  4. To define the following environment variables at docker run time using the -e option in the command line or define them in the ac_env.dat file.

  5. The environment configuration variables, that need to be set for the TomEE server, and application configuration are defined below:

    Environment Configuration Variables

    Configuration Parameters

    Variable

    Admin Console Application Port (http)

    AC_PORT1

    Admin Console Application Port (https)

    AC_PORT2

    Database Jar Used

    DBJar

    DataSource Properties

    DS_Properties

    External Library Path

    EXT_LIB_PATH

Note: Refer to the ac_env.dat file for more information regarding these variables.

  • AC_PORT1: Mention the AdminConsole Application port (http)

    Example: AC_PORT1= 9087

  • AC_PORT2 - Mention the AdminConsole Application Port (https)

    Example: AC_PORT2= 9050

  • DBJar : Based on the Database used for the application, mention the relevant jar

    Example:

    Oracle: DBJar=ojdbc.jar

    DB2: DBJar=db2jcc4.jar

    MSSQL: DBJar=mssql-jdbc.jar

  • DS_Properties: Mention the DataSource Configuration URL based on the database selected.

    Example

    Oracle: DS_Properties=oracledriverType="thin" serverName="DBHOSTNAME" portNumber="DBPORT" databaseName="DBNAME" password="DBPASSWORD" user="DBUSERNAME"

    DB2: DS_Properties=properties.db2.jcc driverType="4" serverName="DBHOSTNAME" portNumber="DBPORT" user="DBUSERNAME" password="DBPASSWORD" databaseName="DBNAME" currentSchema="SCHEMANAME"

    MSSQL: DS_Properties=properties.microsoft.sqlserver databaseName="DBNAME" serverName="DBHOSTNAME" portNumber="DBPORT" user="DBUSERNAME" password="DBPASSWORD"

  • EXT_LIB_PATH: Define the Package Location inside the container (it is configured based on the base image used. No need to change the value of it).

    Example: EXT_LIB_PATH=/opt/ol/adminconsole/externallibs/