ECE Non-Cloud Native Prerequisites

7 ECE Non-Cloud Native Prerequisites

Learn about the software compatible with Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE) 15.2.

Topics in this document:

Additional ECE Software Requirements

See "ECE System Requirements" in ECE Installation Guide for hardware and information requirements.

Note:

This section applies to non-cloud native deployments only. For cloud native deployments, the BRM container images include all required prerequisites.

Additional ECE Software Requirements

Table 7-1 lists the required third-party software for ECE 15.2.

Note:

Oracle does not provide any third-party software mentioned in the table below. You must obtain and install the required third-party software before using the product.

Table 7-1 Required Third-Party Software for ECE 15.2

Software	BRM 15.2	Notes
Apache Kafka Clients	4.0.0	None.
Groovy	4.0.28	The ECE software package does not include Groovy. Installing Groovy is a prerequisite for running ECE monitoring tools.
Oracle Coherence for Java Libraries	14.1.2	The ECE software package does not include Oracle Coherence libraries.

Table 7-2 lists the JAR files that are required during ECE installation.

Table 7-2 Required JAR Files

File	Description
coherence-login.jar	This file is available in the Oracle Coherence package.
coherence-work.jar	This file is available in the Oracle Coherence package.
coherence.jar	This file is available in the Oracle Coherence package.
com.oracle.weblogic.bean gen.general.api.jar	This file is available in the Oracle WebLogic Server client package.
kvclient-25.1.14.jar	You must rename the file to kvclient.jar for the ECE installer to find it.
ojdbc11.jar	Download version compatible with DB26ai and jdk21 from https://www.oracle.com/nl/database/technologies/appdev/jdbc-downloads.html Note: Ensure you download the version 23.9.0.0.0 or later of the ojdbc11.jar file for the correct version of your database.
wlthint3client.jar	This file is available in the Oracle WebLogic Server client package. Note: If you choose to use two JMS providers, both WebLogic Server and another provider, ensure that you do the following after installation on the driver machine: Copy the other JMS provider’s client JARs to the ECE_home/oceceserver/lib directory. Rename the other JMS provider JAR file to wlthint3client.jar. (When using the other JMS provider to publish ECE notification events) Update the ECE_home/oceceserver/JMSQueueConfiguration.xml file to specify the InitialContextFactory and protocol information of the other JMS provider.
xdb6.jar	Download this file from the following page: https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html