This document discusses leveraging Oracle E-Business Suite with Endeca extensions. It begins with an overview of Hitachi Consulting's association with Oracle and Endeca concepts. It then covers Endeca installation and configuration best practices, including installing multiple Endeca applications, disaster recovery setup, and AppsDataSource configuration. The document provides guidance on optimizing performance, backups, role-based access control, and reference materials.
"Impact of front-end architecture on development cost", Viktor Turskyi
Leverage your business with ebs extensions with endeca ppt
1. Session ID:
Prepared by:
Leverage your Business with
EBS Extensions with Endeca
- Oracle E-Business Suite
Information Discovery
10477
Venkataramana Muthadi
Manager, Specialized Services
Hitachi Consulting
2. Session Agenda
• Hitachi Consulting and our association with Oracle.
• Overview on Endeca concepts.
• Endeca Installation & Configuration
– Basic Install, Multiple Endeca installs
– Disaster Recovery for Endeca
• Endeca Best Practices
2
5. Endeca Overview
5
• Oracle Endeca Server
• Oracle Endeca Information Discovery
Integrator
• Oracle Endeca Information Discovery Studio
6. How does Endeca benefit EBS?
6
Typical EBS
Not a User
Friendly
Limited Search
No Aggregation
of data
Business
Problems
EBS with Endeca
Hybrid
Search
Information
Driven
In-Memory
Guided
Navigation
Modern UI
Tag Clouds,
Graphs
10. OS Requirements
Oracle E-Business Suite Information Discovery,
Release 12.2 V6 (12.2.5.6)
• Oracle Linux 5/6 64-bit.
• EID Components: Server 7.5.1, Studio 3.0 &
Integrator 3.3.0.35.
• WebLogic Server 10.3.6.
• Oracle XE Database.
• Ports – 7001/2/4/5/6, 7011-8011.
• Minimum of 32GB RAM & 12 CPU’s.
• Sufficient Disk space to hold temporary files
10
14. Post Install Setups
• Create EBS Data source for Clover & Studio.
• Create Data Domain profile.
• Patch EBS Artifacts to Endeca:
– Run createPayload.sh on EBS.
– Copy payload.zip to Endeca Server.
– Run patchEID.sh on Endeca.
• Bounce Endeca Services.
14
15. Integrate Endeca with E-Business
Suite
• Integrate Endeca with E-Business Suite
• Copy endeca.conf to E-Business Suite Server.
• s_endeca_conf_comment in context file.
• Run Autoconfig.
• FND_ENDECA_PORTAL_URL Profile
• Perform Product specific setup on EBS
– RBAC & Grants, etc.,
15
16. Multiple Endeca Applications
Current Limitations:
• Quick Install with prepackaged setup
• All Ports are predefined and no provision of port
modifications.
• XE Database
– Single Database, No advanced features DR,RMAN
– Limted SGA,Size,etc.,
• Separate Endeca Server for each Non-Prod EBS.
16
17. Multiple Endeca Applications
• Use SE/EE Database.
• Perform Endeca Database Setup on new database.
• Install Endeca Software on default ports.
• Modify ports for the below Admin Server & Managed
Servers:
– Endeca Domain Admin Server
– Endeca Managed Server
– Studio Managed Server
– Integrator Domain Admin Server
– Clover Managed Server
Contd..
17
18. Post Install configuration
• Ports in quickInstall WebLogic Scripts.
• Modify ports
– json files (connection between Studio & Server)
– Datadomain backup & restore scripts.
– Workspace files (workspace.prm).
– Administration scripts
• Update the cluster ports for Endeca clustered
configuration.
18
19. Additional Considerations
Nothing is perfect!
• Automate post steps for multiple installations using
Shell scripting.
• Impact on ports getting overwritten as part of
Endeca application patching.
• Perform port modifications as post step after
patching.
• Update temporary directory location to prevent
permissions of files/directories between two endeca
instances.
19
22. AppsDataSource & JAAS - Endeca
• Prevent exposure of Apps
Password.
• Minimal impact of Apps
password change.
• Enhanced control on
access to EBS Database.
• Isolating custom
applications from having
apps schema access.
Leverage AppsDataSource
option with Endeca
application.
22
23. AppsDataSource Setup
• Register Endeca server node in EBS.
• Copy the DBC file to Endeca Server.
• Create FND_USER in E-Business Suite.
• Assign UMX|APPS_SCHEMA_CONNECT to EBS
User
• Update data source connection details in WebLogic
Console for both domains
– Endeca Domain
– Integrator Domain
23
24. Endeca Best Practices
• Increase Dgraph cache size & thread count for better
performance.
– Start with 2GB cache size.
– Ensure to have 50% RAM available for Filesystem
Caching.
• Optimize Memory & Disk sizing by performing full
loads on test environments.
• Schedule regular backups of Endeca Data Domains.
• Perform backups of sandboxes before applying
Endeca patch.
24
25. Endeca Best Practices
• Use E-Business Suite Database for Endeca Studio
& Integrator Database Setup
• Use UMX_ENDECA_RBACAuto.sh script for
assigning Endeca role.
• Schedule purging of load executions & log files.
• Ensure to retain file modes(Dos, Unix) as they were
developed during migrations.
• Configure alerts for incremental & full load failures
from integrator.
25
29. Reference Materials
• Installing Oracle E-Business Suite Information Discovery,
Release 12.2 V6 (ID 1970071.1)
• Oracle E-Business Suite Information Discovery
Clustering Guide, Release 12.2 V6(ID 2021220.1)
• Oracle E-Business Suite Information Discovery
Globalization Guide, Release 12.2 V6(ID 1970072.1)
• DMZ and SSL Configuration Guide for Oracle E-Business
Suite Information Discovery, Release 12.2 V6 (Doc ID
2038186.1)
• Oracle E-Business Suite Information Discovery Integration
and System Administration Guide
29
31. 31
Please complete the session evaluation form in the
COLLABORATE 16 agenda builder and networking
app.
- We appreciate your feedback and insight
Speaker: Venkataramana Muthadi
Contact:
vmuthadi@hitachiconsulting.com
Session ID: 10477
Editor's Notes
1 of 8 Diamond Partner. 800+ Oracle Consultants, 47 Specialize, 13 Advanced,
Accelerators Appgrade, HEMS, Oracle Partner of the Year,
Oracle Endeca Server is hybrid search/analytical database and at the heart of Oracle Endeca Information Discovery, providing unprecedented flexibility in combining diverse and changing data as well as strong performance in analyzing that data.
Oracle EID Integrator is a powerful visual environment for data integration that includes the Information Acquisition System (IAS) for gathering content from file systems, content management systems, and websites; and out-of-the-box ETL purpose-built for incorporating data from a wide array of sources, including Oracle BI Server.
Oracle Endeca Information Discovery (EID) enables you to access a pre-selected data subset of Oracle E-Business Suite information with enhanced navigation.
Information discovery platform
Tag clouds, Filters, and analytics on diverse, changing information Interactive response at scale.
Ports are hardcoded in the Install state and these ports should be free for Endeca install to proceed. Port range 7011-8011 are being used by various data domains of Endeca Server.
Apply Patches – All the patches related to Endeca are applied on EBS and these are migrated to Endeca using createpayload.sh & patchEID.sh utilities provided by Endeca.
QuickInstall – Quickinstall is fully customized installer provided by Oracle which performs all installations & configurations using envSetup.sh script.
Configure Proxy – As part of Endeca setup, Integration creates endeca.conf and this file needs to placed under EBS OHS Location and update Endeca profile on EBS (FND: Endeca Portal URL)
RBAC Setup – As part of RBAC Setup, Admin provides Endeca roles to the responsibilities on which the Endeca page needs to be enabled.
Data Source using createJNDI.sh
Lar files, graphs, json, workspace.prm
envSetup.sh – option 6
endeca.conf – proxy configuration from EBS to Endeca
s_endeca_conf_comment – Enable
Profile to <EBS>/endeca
Configure Standby using Oracle Dataguard, Clone Endeca Primary application to Standby
Open Standby Database in Snapshot mode and Configure Endeca.
Schedule rsync of Endeca Server Data domains files between Primary and Standby
Any customizations on Primary to be migrated to Standby.
Incase of Disaster, perform recovery of data domain and run Incremental load.
The AppsDataSource standard data source enables access to the Oracle E-Business Suite APPS database schema from external Java EE environments without sharing the APPS schema password. Since the APPS database password is typically changed frequently, using these data sources insulates such programs from having to change their authentication information. Using these data sources also helps prevent wide exposure of the APPS password. Oracle E-Business Suite contains a repository of application users (FND users) and their associated roles (authorization for access to certain functional areas of the product). If you are developing a custom or third-party Java EE application to integrate with Oracle E-Business Suite, and you want to use that existing repository of users and roles for authentication and authorization for your Java EE application, you can use the Oracle E-Business Suite implementation of Java Authentication and Authorization Service (JAAS). This feature is intended to secure an HTTP resource or piece of application functionality at the Oracle E-Business Suite user level.
patchEid.sh: <Endeca_Base>/Oracle/quickInstall/logs/patchLog.out
Oracle Endeca Domain Admin server: <Endeca_B ase>/Oracle/Middleware/user_projects/domains/endeca_domain/bin/domain.log
Oracle Endeca Integrator Domain Admin server: <Endeca_Base>/Oracle/Middleware/user_projects/domains/integrator_domain/bin/domain.log
Endeca ETL: You can check the graph logs through the UI. Navigate to the execution history, and click Graph Details. Within the details, click Log.
Studio Managed Server Log: <Endeca_Base>/Oracle/Middleware/user_projects/domains/endeca_domain/bin/studio.log
Studio UI logs: <Endeca_Base>/Oracle/Middleware/user_projects/domains/endeca_domain/eid-studio.log
Clover Managed Server Log: <Endeca_Base>/Oracle/Middleware/user_projects/domains/integrator_domain/bin/clover.log