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.

      • application.defaultLocale

   2. ac-oipa-jmxconnection-content.xml

      Note: This 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. Under the lib folder of externallibs/ac_shared directory,

   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

• jakarta.persistence-2.2.3.jar

• eclipselink-2.7.10.jar

  Note: Rename all the jars without version names.

• Example:

  • commons-logging.jar

  • el-api.jar

  • aspectjrt.jar

  • aspectjweaver.jar

  • eclipselink.jar

  • jakarta.persistence.jar

    Note: Make sure you have copied the required libraries to the externallibs/ac_shared/lib directory before building the base image.

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	AC_PORT
   Server Port	SERVER_PORT
   Application Redirect Port	REDIRECT_PORT
   Database Jar Used	DBJar
   DataSource Configuration URL	JDBCURL
   Database Username	DSACUSERNAME
   Database Password	DSACPASSWORD
   External Library Path	EXT_LIB_PATH
   ATP Compatibility	ATP_COMPLIANT

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

• AC_PORT : Mention the AdminConsole Application port

  Example: AC_PORT=6060

• SERVER_PORT : Mention the Server Port

  Example: SERVER_PORT=8001

• REDIRECT_PORT : Mention the Application Redirect Port

  Example: REDIRECT_PORT=7441

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

• Example:

  Oracle: DBJar=ojdbc.jar

  MSSQL: DBJar=mssql-jdbc.jar

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

  ORACLE: JDBCURL=jdbc:oracle:thin:@<host>:<port>:<sid>

  MSSQL: JDBCURL=jdbc:sqlserver://<host>:<port>;DatabaseName=<databasename>

• DSACUSERNAME: Mention the username for the AdminConsole Data Source

• DSACPASSWORD: Mention the password for the AdminConsole Data Source.

• 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=/usr/local/tomee/externallibs

• ATP_COMPLIANT: This variable denotes whether the application is in compliance with ATP or not. Choose the appropriate option before provisioning the environment.

  Example: ATP_COMPLIANT=Yes

• If the ADMIN CONSOLE application is ATP compliant, then copy the required ATP (Autonomous Transaction Processing) database files under the externallibs/ac_shared/atp directory.

  The following parameters need to be updated in the ac_env.dat file and the below jars need to be downloaded and copied to ojdbc folder.

Add Following dependent JARs for ATP

Following JDBC JAR files (JDBC Release 18.3 and above): are required to have a successful database connection:

The jars must be placed under /usr/local/tomee/externallibs/ac_shared/atp/ojdbc directory

Note: Download the JAR files using this link

JAR Files

JAR	Required?	Description
ojdbc.jar	Required	JDBC Thin Driver, please follow OIPA installation documentation for supported JDBC driver version
ons.jar	Optional	Only needed in case FAN (Fast Application Notification) is configured for Oracle RAC cluster
oraclepki.jar	Required	Oracle PKI (public key infrastructure) provider for Oracle Wallets
osdt_cert.jar	Required	Oracle Security Developer Tool Certificates
osdt_core.jar	Required	Oracle Security Developer Tool Core
ucp.jar	Required	Universal Connection Pool

Autonomous Transaction Processing Database (ATP) Variables

ATP Configuration Parameters	Variables
Wallet Location	WALLET
TNS DB name	WALLETDB
ATP Wallet Username	WALLETUSERNAME
ATP Wallet Password	WALLETPASSWORD
ATP Proxy	ATP_PROXY
ATP Proxy Port	ATP_PROXY_PORT

• WALLET: Update the WALLET directory location ( which is preconfigured based on the container structure)

  Example: WALLET=/usr/local/tomee/externallibs/ac_shared/atp/wallet/

• WALLETDB: Open tnsnames.ora file (present in the wallet) and note the TNS name that is suffixed with _tp for transaction processing.

  Example: WALLETDB=oipadb_tp

• WALLETUSERNAME: Mention the username for the ATP connection

• WALLETPASSWORD: Mention the password for the ATP connection

• ATP_PROXY: The ATP instance is on Public IP, if connecting over VPN, then you need to use an HTTP: PROXY

  Example: ATP_PROXY=www-proxy-hqdc.us.oracle.com

• ATP_PROXY_PORT: Mention the HTTP: PROXY PORT

  Example: ATP_PROXY_PORT=80

The sample folder structure is as follows:

Under ojdbc folder copy all the libs downloaded

Under wallet folder