Oracle Enterprise Command Center (ECC) V13 Installation and Integration with Oracle E-Business Suite 12.2.5

Overview

Oracle Enterprise Command Center (ECC) provides a modern, search-driven user experience that enables business users to analyze transactional data through interactive dashboards. Integrating ECC with Oracle E-Business Suite (EBS) enhances visibility into business processes and improves operational decision-making.

This article walks through the deployment and integration of Oracle Enterprise Command Center Framework (ECC) V13 with Oracle E-Business Suite 12.2.5 running on Oracle Database 19c. The implementation includes infrastructure preparation, ECC installation, WebLogic domain creation, EBS integration, SSL configuration, validation activities, and post-installation troubleshooting.

Environment Details

Oracle E-Business Suite Environment

Component Details
EBS Host JAYTSTPRIM.eclipse.int
EBS Version Oracle EBS 12.2.5
Database Version Oracle Database 19c
Web Protocol HTTPS
Web Port 443

Oracle ECC Environment

Component Details
ECC Host JAYTSTECC.eclipse.int
ECC Version V13
WebLogic Version 14.1.1
ZooKeeper Port 2181
Admin Server Port 7775
ECC Managed Server Port 7776
ECC HTTPS Port 7778

Architecture Design

To ensure optimal performance and scalability, ECC was deployed on a dedicated server rather than sharing resources with the EBS application tier. This architecture minimizes resource contention and allows ECC indexing and dashboard operations to run independently.

The communication flow consists of:

  1. Oracle EBS Application Tier
  2. Oracle Database 19c
  3. Dedicated ECC Server
  4. WebLogic Domain Hosting ECC Services
  5. Secure HTTPS Communication Between EBS and ECC

Operating System and Network Readiness

Before beginning the installation, several infrastructure checks were completed to validate connectivity and server readiness.

Host Resolution Verification

hostname
nslookup JAYTSTECC
ping JAYTSTPRIM.eclipse.int

Connectivity Validation

telnet JAYTSTPRIM.eclipse.int 443
telnet JAYTSTPRIM.eclipse.int 1531

Firewall Verification

The following ports were confirmed to be open and reachable:

  • 2181 (ZooKeeper)
  • 7775 (WebLogic Administration)
  • 7776 (ECC Managed Server)
  • 7778 (ECC HTTPS Access)
  • 1531 (Database Listener)
  • 443 (Oracle EBS HTTPS)

Successful completion of these checks ensured smooth communication between EBS and ECC components.

Installing Oracle ECC V13

The ECC V13 Quick Install package was deployed using Oracle’s installation framework.

Installation Package

The following patch bundle was used:

ECC Framework V13 – Patch 36527725

Installation Steps

unzip p36527725_R12_GENERIC.zip

chmod +x *.bsx

for f in *.bsx
do
   sh $f
done

Installation target directory:

/u01/ECC

Components Installed

The quick installation successfully deployed:

  • Oracle Middleware Infrastructure
  • Oracle WebLogic Server
  • ECC Framework Components
  • ECC Quick Install Utilities
  • Deployment and Configuration Scripts

ECC Configuration

After software installation, ECC properties were configured to establish connectivity with Oracle EBS and the backend database.

Configuration File

$ECC_BASE/Oracle/quickInstall/EccConfig.properties

Key parameters updated included:

EBS_MIDDLETIER_HOST_FQDN=JAYTSTPRIM.eclipse.int

EBS_DB_URL=jdbc:oracle:thin:@JAYTSTPRIM.eclipse.int:1531:ebs_FLRDEVL

ECC_DB_URL=jdbc:oracle:thin:@JAYTSTPRIM.eclipse.int:1531:ebs_FLRDEVL

EBS_ECC_USER=ECC

Environment Generation

cd $ECC_BASE/Oracle/quickInstall

./createEnvFile.sh

This process generated the environment configuration required for subsequent installation steps.

ECC Database Setup

The ECC repository schema was created using Oracle-provided setup utilities.

Database Initialization

source ./env/ecc.env

./envSetup.sh

Select:

Database Setup

Validation

SELECT username
FROM dba_users
WHERE username='ECC';

The ECC schema was successfully created and validated within the database.

WebLogic Installation and Domain Creation

ECC services are hosted within a dedicated WebLogic domain.

WebLogic Installation

./envSetup.sh

Select:

Install WebLogic Server

ECC Domain Creation

Execute the domain creation option from the installation menu.

After completion, verify the startup status:

grep RUNNING \
$ECC_BASE/Oracle/Middleware/user_projects/domains/ecc_domain/bin/domain.log

Successful validation confirms that the domain and managed servers are operational.

Creating the EBS JNDI Connection

ECC requires a JNDI datasource to communicate with Oracle EBS.

DBC File Configuration

Copy the EBS DBC file:

scp *.dbc \
$ECC_BASE/Oracle/quickInstall/connection.dbc

Run:

./envSetup.sh

Select:

Create EBS JNDI

The utility establishes the connection required for ECC authentication and data synchronization.

Integrating ECC Security with Oracle EBS

Security integration enables ECC to leverage EBS authentication and authorization mechanisms.

Integration Command

./integrateEBSSecurity.sh

Validation Query

SELECT source_system_name,
       security_manager
FROM ecc_source_system;

Expected output:

oracle.ecc.security.extensions.EbsEccSecurityManager

This confirms that ECC security has been successfully linked with Oracle EBS.

Oracle EBS Profile Configuration

Two important profile options must be configured within EBS.

ECC Framework Agent

ECC_FRAMEWORK_AGENT

Value:

https://JAYTSTPRIM.eclipse.int:443

ECC Portal URL

FND_ENDECA_PORTAL_URL

Value:

https://JAYTSTECC.eclipse.int:7778/ecc

These settings allow EBS responsibilities to redirect users into ECC dashboards.

Enabling HTTPS for ECC

To provide secure communication between ECC and Oracle EBS, HTTPS was enabled.

Certificate Verification

openssl s_client \
-connect JAYTSTECC.eclipse.int:7778

Importing the ECC Certificate

orapki wallet add \
-wallet <wallet_path> \
-trusted_cert \
-cert ecc_ca.pem

Validation

orapki wallet display \
-wallet <wallet_path>

The ECC certificate was successfully added to the Oracle wallet, enabling secure SSL communication.

Configuring OHS Rewrite Rules

Oracle HTTP Server was configured to redirect ECC requests through HTTPS.

RewriteEngine On

RewriteRule ^/ecc$ \
https://JAYTSTECC.eclipse.int:7778/ecc/?system=EBS \
[CO=ORA_ECC_GUEST_LANG:en:JAYTSTPRIM.eclipse.int,NE,P,QSA,L]

After updating the configuration, restart EBS services:

adstpall.sh

adstrtal.sh

Post-Installation Validation

Several functional tests were performed to verify ECC integration.

ECC Developer Responsibility

Result:

✅ ECC launched successfully.

Users were able to access dashboards and navigate the ECC interface without issues.

Payables Manager Responsibility

Result:

⚠ Dashboard content did not load successfully.

Validation using:

curl -vk \
https://JAYTSTECC.eclipse.int:7778/ecc/web/ap/balance

Returned:

HTTP 401 Unauthorized
Current user is not authenticated

This indicates that ECC access was established, but dashboard-level authorization was failing.

Troubleshooting Findings

The integration was largely successful, with ECC services, SSL communication, and EBS redirection functioning as expected. However, the Payables Supplier Balance dashboard remained inaccessible.

Potential causes identified during analysis included:

  • Missing ECC role assignments
  • Incomplete UMX role synchronization
  • Dashboard-level authorization restrictions
  • Responsibility-to-role mapping inconsistencies
  • Security context propagation issues

Because the ECC landing page opens successfully, the issue appears to be authorization-related rather than connectivity-related.

Recommended Follow-Up Activities

To resolve dashboard access issues, the following checks are recommended:

Verify ECC Security Configuration

SELECT *
FROM ecc_source_system;

Synchronize User Roles

Confirm that ECC roles are properly assigned and synchronized from EBS.

Clear EBS Cache

Navigate to:

Functional Administrator
→ Caching Framework
→ Clear All Cache

Validate Responsibility Mapping

Ensure that the affected responsibility has access to the required ECC datasets and dashboards.

Review ECC Logs

Inspect:

ECC Managed Server Logs
ECC Security Logs
WebLogic Logs

for authorization or authentication errors.

Conclusion

Implementing Oracle Enterprise Command Center V13 with Oracle E-Business Suite 12.2.5 significantly enhances the analytical capabilities of EBS by providing intuitive, role-based dashboards and real-time business insights. The deployment described in this article successfully established ECC infrastructure, integrated EBS authentication, enabled SSL communication, and validated end-to-end connectivity.

While the core installation was completed successfully, further investigation into dashboard authorization and role synchronization is required to achieve full functionality for all business responsibilities. Once resolved, ECC can serve as a powerful analytics layer that improves user productivity and decision-making across the enterprise.

Recent Posts