Complete Guide to Oracle Enterprise Command Center (ECC) Framework Implementation
Introduction
This comprehensive guide walks through the complete implementation of Oracle Enterprise Command Center (ECC) Framework, based on a successful deployment on EBS 12.2.13 with Oracle Database 19c. The implementation covers everything from initial server preparation through final user access configuration.
1. Network Configuration and Prerequisites
Hostname Configuration
Verify the hostname is properly set and resolved:
[oracle@ebstest 19c]$ hostname ebstest.finsys.co.ke
Ensure the hostname resolves to an IP address via DNS or by adding it to /etc/hosts:
127.0.0.1 localhost localhost.localdomain ::1 localhost localhost.localdomain 192.168.0.100 ebstest.finsys.co.ke ebstest
Create OS Users and Groups
Create the oinstall group and oracle user for the ECC installation:
groupadd oinstall useradd -g oinstall oracle
Install Required OS Packages
# psmisc provides fuser command yum install psmisc # bind-utils provides host command yum install bind-utils yum install jq
2. ECC Installation
Download and Prepare Installation Files
Create the ECC installation root directory (referred to as
$ECC_BASE):
mkdir -p /u01/app/ecc
Download the latest ECC patch from MOS (at the time of writing: ECC v14 patch 36962225)
Extract the patch to a staging directory:
unzip p36962225_R12_GENERIC.zipCopy the
.bsxfile to$ECC_BASEand set executable permissions:
cp *.bsx /u01/app/ecc/ chmod +x /u01/app/ecc/*.bsx
Execute the installer:
cd /u01/app/ecc for f in *.bsx; do sh $f; done
This creates two directories:
insta_client: SQL*Plus client directoryOracle: ECC Framework quick install scripts and software
3. EBS Prerequisite Patches
Before configuring ECC, apply the required EBS patches in the exact order shown below.
Determine Framework Code Stack Level
Run this query to check your current Framework stack:
SELECT codelevel, decode((codelevel), 'C.13', '12.2.14 Framework Code Stack', 'C.12', '12.2.13 Framework Code Stack', 'C.11', '12.2.12 Framework Code Stack', 'C.10', '12.2.11 Framework Code Stack', 'C.9', '12.2.10 Framework Code Stack', 'C.8', '12.2.9 Framework Code Stack', 'C.7', '12.2.7/12.2.8 Framework Code Stack', 'C.6', '12.2.6 Framework Code Stack', 'C.5', '12.2.5 Framework Code Stack', 'C.4', '12.2.4 Framework Code Stack', 'B.5', '12.1.3 Framework Code Stack', 'B.4', '11.5.10 Framework Code Stack' ) stack FROM AD_TRACKABLE_ENTITIES WHERE abbreviation='fwk';
Apply Patches in Sequential Order
Important: Apply patches in steps 2, 3, and 4 in the sequence shown. Do not merge these patches together.
# 1. ATG Consolidated Patch [applmgr@ebstest ~]$ adop phase=apply patches=36962204 # 2. Adapter Patch [applmgr@ebstest ~]$ adop phase=apply patches=36962214 # 3. Product Family Consolidated Patches [applmgr@ebstest ~]$ adop phase=apply patches=36962149,36962130,36962147,36962150,36962148,36962151 # 4. Additional Required Patches for Enterprise Command Centers [applmgr@ebstest ~]$ adop phase=apply patches=37764404,37656362,35045912,30994020,32379321,33282888,32394548,33828966,36245474,35059202,35680702,35625136,37477799,35573606,36440950,36480192,35211868,31604775,36214549,35088899,37495742,35135853 # 5. Product Family Online Help Patches [applmgr@ebstest ~]$ adop phase=apply patches=36968391,36968376,36968399,36968363,36968383,36968278 # 6. Complete the ADOP Cycle [applmgr@ebstest ~]$ adop phase=finalize [applmgr@ebstest ~]$ adop phase=cutover [applmgr@ebstest ~]$ adop phase=cleanup [applmgr@ebstest ~]$ adop phase=fs_clone
4. ECC Configuration
Database Setup
Create the ECC configuration file with the following parameters:
# Path of the ECC directory ECC_BASE=/u01/app/ecc # Directory location of ecc-config.properties ECC_CONFIG_LOC=$ECC_BASE/Oracle/quickInstall/env/ecc # Log directories for ECC and SOLR ECC_LOG_DIR=$ECC_BASE/Oracle/quickInstall/logs/ecc # EBS Middletier Properties EBS_MIDDLETIER_HOST_FQDN=ebstest.finsys.co.ke EBS_MIDDLETIER_PORT=8010 EBS_MIDDLETIER_PROTOCOL=http # EBS Middletier DB Details EBS_DB_URL=jdbc:oracle:thin:@ebstest.finsys.co.ke:1531:uat EBS_DB_USERNAME=apps EBS_ECC_USER=ECC_USER TIMEZONE=EAT # ECC DB Details ECC_DB_URL=jdbc:oracle:thin:@ebstest.finsys.co.ke:1531:uat ECC_DB_USERNAME=ECC SCHEMA_CREATION=NO ECC_HOST_NAME=ebstest.finsys.co.ke ECC_HOST_PROTOCOL=http # Zookeeper host url zkHost=localhost:2181/solr # Clustering mode CLUSTER_MODE=standalone ECC_DATA_CACHE_SIZE=2000 # Ports ECC_ADMIN_PORT=7775 ECC_MANAGED_PORT=7776 ECC_ADMIN_SSL_PORT=7777 ECC_MANAGED_SSL_PORT=7778 # Heap Memory settings ADMIN_HEAP_USER_MEM=1024M MANAGED_HEAP_USER_MEM=4096M # Languages ECC_DEFAULT_LANGUAGE=en ECC_LANGUAGES=en # Analyzer DATASET_ANALYZER_DEFAULT=solr CLUSTER_JPA_MANAGER=zookeeper # Push configuration PUSH_STAGING_DIR=$ECC_BASE/Oracle/quickInstall/staging # Export details MAX_EXPORT_COUNT=1000 ENABLE_EXPORT=true MAX_ACTION_RECORD_COUNT=1000 # Online full load ONLINE_FULLLOAD_ENABLED=false ONLINE_FULLLOAD_STAGING_LOCATION=$ECC_BASE/Oracle/quickInstall/staging # Activity Audit ACTIVITY_AUDIT_ISENABLED=true ACTIVITY_AUDIT_INGEST_LIMIT=100 # Export configuration EXPORT_PDF_MAX_COUNT=100 EXPORT_PDF_ENABLED=true RELATIVE_DATE_WEEK_STARTDAY=1 # Purge configuration ECC_PURGE_DATA_LOAD_ENABLED=true ECC_PURGE_DATA_LOAD_RETENTION_TIME_DAYS=30 ECC_PURGE_DATA_LOAD_SCHEDULER_FREQUENCY_HRS=24 ECC_PURGE_ACTIVITY_AUDIT_ENABLED=true ECC_PURGE_ACTIVITY_AUDIT_RETENTION_TIME_DAYS=365 ECC_PURGE_LOG_FILES_ENABLED=true ECC_PURGE_LOG_FILES_RETENTION_TIME_DAYS=30 # ETL configuration ECC_INGEST_ETL_ENABLED=true ECC_ETL_SCHEDULER_FREQUENCY=6 # Dataset Statistics ECC_DATASET_STATISTICS_ENABLED=true
Update Environment File
[oracle@ebstest ecc]$ /u01/app/ecc/Oracle/quickInstall/createEnvFile.sh Enter the absolute full path of EccConfig.properties file: /u01/app/ecc/Oracle/quickInstall/EccConfig.properties
Run Database Setup
Source the environment and run the setup script:
[oracle@ebstest quickInstall]$ cd Oracle/quickInstall [oracle@ebstest quickInstall]$ source ./env/ecc.env [oracle@ebstest quickInstall]$ unset which [oracle@ebstest quickInstall]$ ./envSetup.sh
Choose option 1. Database Setup and follow the prompts to create the ECC schema.
Verify ECC Schema Connection
[applmgr@ebstest ~]$ sqlplus ecc/K0Junga# SQL> show user USER is "ECC"
5. Set Up ECC Framework
Install WebLogic Server
From the envSetup.sh script, choose option 2. Install Weblogic Server:
Select which option you want to proceed with 1. Database Setup 2. Install Weblogic Server 3. Create ECC Domain 4. Create EBS JNDI 5. Integrate ECC with EBS 6. Exit: 2
Password Requirements: Ensure the ECC admin user password is at least 8 characters with a special character and number.
Create ECC Domain
Choose option 3. Create ECC Domain and follow the prompts to:
Configure the wallet
Create the ECC domain
Apply necessary patches
Create EBS JNDI
Choose option 4. Create EBS JNDI:
Enter the password for apps Database: Enter the ECC Domain weblogic password:
This creates JNDI connections for:
eccdb: ECC database connectionebsdb: EBS database connectionsrcDB: Source system connection
Integrate ECC with EBS
Choose option 5. Integrate ECC with EBS:
Enter the password for apps Database: Enter the password for EBS FND user DEVELOPER used by ECC:
This step:
Updates the ECC Security Manager
Restarts the ECC managed server
Configures connection filters
Sets up the Source System
6. EBS Integration Configuration
Edit EBS Context Variables
Log in to Oracle E-Business Suite as a system administrator and navigate to System Administration > Oracle Applications Manager > AutoConfig.
Select the application tier context file and choose Edit Parameters
Search for the following variables and set appropriate values:
| Variable | Value Example |
|---|---|
s_ecc_conf_comment | (Remove # to uncomment) |
s_ecc_protocol | http |
s_ecc_web_host | ebstest.finsys.co.ke |
s_ecc_managed_server_port | 7776 |
Save changes and run AutoConfig:
[applmgr@ebstest secure]$ adautocfg.sh
Configure OHS
Check that the OHS configuration file includes the following settings:
RewriteEngine on RewriteRule ^/ecc(.*)$ http://ebstest.finsys.co.ke:7776/ecc/?system=EBS [CO=ORA_ECC_GUEST_LANG:en:ebstest.finsys.co.ke,NE,P,QSA,L]
Clear Cache and Restart Services
# Stop all services $ADMIN_SCRIPTS_HOME/adstpall.sh # Clear cache cd $OA_HTML/cabo/images cp -r cache cache_bkp rm -rf cache/* cd $OA_HTML/cabo/styles cp -r cache cache_bkp rm -rf cache/* # Restart services $ADMIN_SCRIPTS_HOME/adstrtal.sh
7. Import ECC Applications
Run patchEccFiles.pl
From the EBS server, run the import script:
cd $FND_TOP/bin perl ./patchEccFiles.pl
Follow the prompts:
Enter temporary directory for ECC Files
Enter EBS DB apps user password
Select language(s) to process (e.g.,
enfor English)Choose
Yto add all products
The script imports all available ECC applications and provides a summary report.
8. Configure User Access
Assign ECC Responsibilities
Manually assign the ECC Developer responsibility to desired users, or use the automated script:
source EBSapps.env run $FND_TOP/bin/UMX_ENDECA_RBACAuto.sh
Prepare a CSV file UMX_ENDECA_RBAC.csv with the format:
PERMISSION_SET_CODE,RESPONSIBILITY_CODE,ENDECA_ROLE_CODE AP_ECC_ACCESS_PS,FND_RESP|SQLAP|PAYABLES_MANAGER|STANDARD,UMX|AP_ECC_ACCESS_ROLE AR_ECC_ACCESS_PS,FND_RESP|AR|RECEIVABLES_MANAGER|STANDARD,UMX|AR_ECC_ACCESS_ROLE
Clear Cache
After role assignment, clear the EBS cache using the Functional Administrator responsibility.
9. Data Loading
Run ECC Data Loader Programs
Switch to the appropriate product responsibility (e.g., Payables Manager for AP, Receivables Manager for AR)
Run the Command Center Data Load concurrent program
For subsequent updates, run in INCREMENTAL_LOAD mode
Troubleshooting Data Load Issues
If you encounter connection filter errors:
Connection rejected, filter blocked Socket
Remove the following rule from the WebLogic admin console:
* * 7776 deny
10. TLS Configuration (Optional)
If your EBS instance is TLS-enabled, perform these additional steps:
Import Certificate
For both 64-bit and 32-bit JDK:
cd [s_fmw_jdktop]/jre/lib/security keytool -import -alias r122SelfSigned -file /tmp/r122.localdomain.crt -v -keystore cacerts cd $OA_JRE_TOP/lib/security keytool -import -alias r122SelfSigned -file /tmp/r122.localdomain.crt -v -keystore cacerts
11. Verification
Verify Admin and Managed Servers
Check the domain log files:
vi /u01/app/ecc/Oracle/Middleware/user_projects/domains/ecc_domain/bin/domain.log vi /u01/app/ecc/Oracle/Middleware/user_projects/domains/ecc_domain/bin/ecc.log
Search for the message: "The server started in RUNNING mode"
Access ECC
ECC Admin Console:
http://ebstest.finsys.co.ke:7775/consoleECC Application:
http://ebstest.finsys.co.ke:7776/eccCore Solr Application:
http://ebstest.finsys.co.ke:7776/core_ecc/#/
Test Data Source Connection
Log in to the ECC admin console
Go to Services > Data Sources
Select
ebsdbJNDI configurationNavigate to Monitoring > Testing
Select the managed server and click Test Data Source
Expected result: Success Test of ebsdb on server was successful
References
Installing Oracle Enterprise Command Center Framework, Release 12.2 V13 (Doc ID 3059038.1)
Enabling TLS for Oracle Enterprise Command Center Framework, Release 12.2 (Latest Version) (Doc ID 2496445.1)
Enabling TLS in Oracle E-Business Suite Release 12.2 (Doc ID 1367293.1)
This guide is based on a successful implementation on EBS 12.2.13 with Oracle Database 19c. Individual environments may require adjustments to patch numbers and configuration parameters.
No comments:
Post a Comment