Installation note for WebLogic 14c

Overview

Requirements

• Certified Oracle Java SE 8 or 11

• WebLogic Server 14c

• Database and JDBC driver

• EBX® CD

WebLogic Application Server installation

1. Download WebLogic 14c latest version from:

   https://www.oracle.com/middleware/technologies/fusionmiddleware-downloads.html

2. Run the Oracle Fusion Middleware Weblogic installation wizard using a certified Oracle JDK and the java -jar command line

3. Perform a standard installation with default options and choose the appropriate installation directory

4. Leave the 'Automatically launch the Configuration Wizard' option activated to perform the next steps:

   1. Create Domain: choose 'Create a new domain' and specify the domain home directory, then click 'Next'

   2. Templates: keep as default and click 'Next'

   3. Administrator Account: enter a domain administrator username and password and click 'Next'

   4. Domain Mode and JDK: choose the production mode and your JDK installation home and click 'Next'

   5. Advanced configuration: check 'Administration server' and 'Topology'. That way, we create two independent domain nodes: an administration one and an application one.

      Click 'Next'

   6. Administration Server: enter your administration node name (for example 'AdminServer') and listen port (by default 7001), then click 'Next'

   7. Managed Servers: add the application node name (for example 'EbxServer') and listen port (for example 7003), then click 'Next'

   8. Clusters: keep as default and click 'Next'

   9. Server Templates: keep as default and click 'Next'

   10. Machines: keep as default and click 'Next'

   11. Configuration Summary: click 'Create'

   12. Configuration Process: click 'Next'

   13. End Of Configuration: click 'Finish'

EBX® home directory configuration

1. Create EBX_HOME directory, for example C:\EBX\home, or /home/ebx

2. Copy from EBX® CD the ebx.software/files/ebx.properties file to EBX_HOME. In our example, we will have the following file:

   C:\EBX\home\ebx.properties, or /home/ebx/ebx.properties

3. If needed, edit the ebx.properties file to override the default database. By default the standalone H2 database is defined. The property key ebx.persistence.factory must be uncommented for other supported databases and the h2.standalone one must be commented.

WebLogic Application Server and Java Virtual Machine configuration

1. Configure the launch properties for the Managed Server (for example 'EbxServer')

   Edit the <DOMAIN_HOME>/bin/startManagedWebLogic.sh script file by adding the following lines:

   EBX_HOME="<path_to_the_directory_ebx_home>"
   EBX_OPTIONS="-Debx.home=${EBX_HOME} -Debx.properties=${EBX_HOME}/ebx.properties"
   export JAVA_OPTIONS="${EBX_OPTIONS} ${JAVA_OPTIONS}"

2. Edit the <DOMAIN_HOME>/bin/setDomainEnv.sh script file by adding the following line:

   PRE_CLASSPATH="<path_to_the_data_compression_library>"
   
   # For our example
   # PRE_CLASSPATH="${DOMAIN_HOME}/compress/ebx-lz4.jar"

EBX® and third-party libraries deployment

1. Copy third-party libraries from the EBX® CD to the <DOMAIN_HOME>/lib directory except for the Data compression library. In our example, for an H2 standalone data base, we will have:

   <DOMAIN_HOME>/lib/h2-2.1.212.jar (default persistence factory) coming from ebx.software/lib/lib-h2 directory.

   The complete description of the components needed by EBX® is given in chapter Java EE deployment. Obviously, if those components are already deployed on the class-loading system, they do not have to be duplicated (ex: javax.mail-1.5.6.jar and xml-apis-1.4.01.jar are already present in the WebLogic Server).

2. Create a directory dedicated to the Data compression library (for example <DOMAIN_HOME>/compress) and copy it there.

   Note

   Ensure that the library is copied in the directory pointed out by the previously updated PRE_CLASSPATH environment variable.

Data source and JDBC provider configuration

1. Start the 'Administration server' (for example 'AdminServer'), using:

   <DOMAIN_HOME>/bin/startWebLogic.sh

2. Launch the 'WebLogic Server Administration Console' by entering the following URL in the browser:

   http://localhost:7001/console.

   Log in with the domain administrator username and password

3. Click on 'Services > Data sources' in the 'Domain Structure' panel, then click on 'New > Generic Data Source':

   1. Set: Type Name: EBX_REPOSITORY, JNDI Name: EBX_REPOSITORY, Database Type: Your database type

      Click 'Next'

   2. Choose your database driver type, and click 'Next'

   3. Uncheck 'Supports Global Transactions', and click 'Next'

   4. Setup your database 'Connection Properties' and click 'Next'

   5. Click 'Test Configuration' and then 'Finish'

   6. Switch on the 'Targets' tab and select all Servers, then click 'Save'

   7. Restart the Administration server (for example 'AdminServer'), using:

      <DOMAIN_HOME>/bin/stopWebLogic.sh

      <DOMAIN_HOME>/bin/startWebLogic.sh

EBX® application deployment

1. Copy from the EBX® CD the ebx.software/webapps/ear-packaging/EBXForWebLogic.ear to the EBX_HOME directory. In our example, we will have:

   C:\EBX\home\EBXForWebLogic.ear, or /home/ebx/EBXForWebLogic.ear

2. Launch the 'WebLogic Server Administration Console' by entering the following URL in the browser:

   http://localhost:7001/console

3. Click on 'Lock and Edit' in the 'Change Center' panel

4. Click on 'Deployments' in the 'Domain Structure' panel, and click 'Install':

   1. Install Application Assistant: Enter in 'Path' the application full path to EBXForWebLogic.ear file, located in C:\EBX\home\, or /home/ebx/ directory and click 'Next'

   2. Choose the installation type and scope: Click on 'Install this deployment as an application', 'Global' default scope and click 'Next'

   3. Select the deployment targets: Select a node (for example 'EbxServer') from the 'Servers' list and click 'Next'

   4. Optional Settings: keep as default and click 'Finish'

5. Click on 'Activate Changes', on the top left corner. The deployment status will change to 'prepared'

6. Switch to 'Control' tab, select the 'EBXForWebLogic' enterprise application, then click 'Start' > 'Servicing all requests'

7. Start the application node (for example 'EbxServer'), using:

   <DOMAIN_HOME>/bin/startManagedWebLogic.sh EbxServer http://localhost:7001

EBX® application start

1. After WebLogic Application Server launch, run the EBX® web application by entering the following URL in the browser:

   http://localhost:7003/ebx/

2. At first launch, EBX® Wizard helps to configure the default properties of the initial repository.