WebLogic 14c supports JDK 11, but not JDK 17 LTS. Until a WebLogic release supports JDK 17 LTS, EBX® will continue to support WebLogic 14c with JDK 11. Please be aware that, according to Oracle's Statement of Direction, future versions of supported software might not be compatible with EBX®.
This chapter describes a quick installation example of TIBCO EBX® on WebLogic Application Server.
It does not replace the documentation of this application server.
They are not general installation recommendations, as the installation process is determined by architectural decisions, such as the technical environment, application mutualization, delivery process, and organizational decisions.
The complete description of the components needed by EBX® is given in chapter Java EE deployment.
To avoid unpredictable behavior, the guideline to follow is to avoid any duplicates of ebx.jar
, or other libraries in the class-loading system.
Refer to the Security Best Practices for information on navigating secure deployments.
Certified Oracle Java SE 11 (update 6 and above)
WebLogic Server 14c
Database and JDBC driver
EBX® CD
Download WebLogic 14c latest version from:
https://www.oracle.com/middleware/technologies/fusionmiddleware-downloads.html
Run the Oracle Fusion Middleware Weblogic installation
wizard using a certified Oracle JDK and the java -jar command line
Perform a standard installation with default options and choose the appropriate installation directory
Leave the 'Automatically launch the Configuration Wizard' option activated to perform the next steps:
Create Domain: choose 'Create a new domain' and specify the domain home directory, then click 'Next'
Templates: keep as default and click 'Next'
Administrator Account: enter a domain administrator username and password and click 'Next'
Domain Mode and JDK: choose the production mode and your JDK installation home and click 'Next'
Advanced configuration: check 'Administration server' and 'Topology'. That way, we create two independent domain nodes: an administration one and an application one.
Click 'Next'
Administration Server: enter your administration node name (for example 'AdminServer') and listen port (by default 7001
), then click 'Next'
Managed Servers: add the application node name (for example 'EbxServer') and listen port (for example 7003
), then click 'Next'
Clusters: keep as default and click 'Next'
Server Templates: keep as default and click 'Next'
Machines: keep as default and click 'Next'
Configuration Summary: click 'Create'
Configuration Process: click 'Next'
End Of Configuration: click 'Finish'
Create EBX_HOME directory, for example C:\EBX\home
, or /home/ebx
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
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.
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}" |
Copy third-party libraries from the EBX® CD to the <DOMAIN_HOME>/lib
directory. In our example, for an H2 standalone data base, we will have:
<DOMAIN_HOME>/lib/h2-2.2.224.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 is already present in the WebLogic Server).
Start the 'Administration server' (for example 'AdminServer'), using:
<DOMAIN_HOME>/bin/startWebLogic.sh
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
Click on 'Services > Data sources' in the 'Domain Structure' panel, then click on 'New > Generic Data Source':
Set: Type Name: EBX_REPOSITORY
, JNDI Name: EBX_REPOSITORY
, Database Type: Your database type
Click 'Next'
Choose your database driver type, and click 'Next'
Uncheck 'Supports Global Transactions', and click 'Next'
Setup your database 'Connection Properties' and click 'Next'
Click 'Test Configuration' and then 'Finish'
Switch on the 'Targets' tab and select all Servers, then click 'Save'
Restart the Administration server (for example 'AdminServer'), using:
<DOMAIN_HOME>/bin/stopWebLogic.sh
<DOMAIN_HOME>/bin/startWebLogic.sh
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
Launch the 'WebLogic Server Administration Console' by entering the following URL in the browser:
Click on 'Lock and Edit' in the 'Change Center' panel
Click on 'Deployments' in the 'Domain Structure' panel, and click 'Install':
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'
Choose the installation type and scope: Click on 'Install this deployment as an application', 'Global' default scope and click 'Next'
Select the deployment targets: Select a node (for example 'EbxServer') from the 'Servers' list and click 'Next'
Optional Settings: keep as default and click 'Finish'
Click on 'Activate Changes', on the top left corner. The deployment status will change to 'prepared'
Switch to 'Control' tab, select the 'EBXForWebLogic' enterprise application, then click 'Start' > 'Servicing all requests'
Start the application node (for example 'EbxServer'), using:
<DOMAIN_HOME>/bin/startManagedWebLogic.sh EbxServer http://localhost:7001
After WebLogic Application Server launch, run the EBX® web application by entering the following URL in the browser:
At first launch, EBX® Wizard helps to configure the default properties of the initial repository.