ELAJOU - Integration Architecture

Technical Architecture Document

Version 1.0

Oracle Consulting Team

Oracle Saudi Arabia
Table of Contents
Introduction .......................................................................................................................................................... 4
Purpose of Document ....................................................................................................................................... 4
Integration Platform ......................................................................................................................................... 5
Oracle Cloud Infrastructure (OCI) ......................................................................................................................... 6
Current/ Future Infrastructure ......................................................................................................................... 6
ELAJOU current OCI Subscription: .................................................................................................................... 7
ELAJOU PROD and Non-PROD environments ............................................................................................... 8
Services Scope per environment: ............................................................................................................. 9
ELAJOU Current OIC Provisioned: ............................................................................................................... 10
ELAJOU Current Database Provisioned:...................................................................................................... 11
Audience ......................................................................................................................................................... 12
Integration Overview .......................................................................................................................................... 13
Assumptions ................................................................................................................................................... 14
Integration Architecture ................................................................................................................................. 15
High-level Integration Architecture Design ................................................................................................ 15
Sample of Integration Cycles ...................................................................................................................... 16
Quote to Cash Cycle: ............................................................................................................................... 16
Procure to Pay Cycle ............................................................................................................................... 17
HCM Integration with Time Attendance:................................................................................................ 18
Service Request Cycle: ............................................................................................................................ 19
Integration Details .............................................................................................................................................. 21
Prerequisites ................................................................................................................................................... 21
Integration Considerations ............................................................................................................................. 22
Integration Security ........................................................................................................................................ 22
Oracle ERP Cloud APIs................................................................................................................................. 22
Oracle Fusion SOAP Web Services Security ................................................................................................ 22
TLS Security ................................................................................................................................................. 23
Oracle Integration On-Premises Connectivity Agent .................................................................................. 23
Integration Monitoring ................................................................................................................................... 24
OIC Monitoring ........................................................................................................................................... 24
REST API .................................................................................................................................................. 25
OIC Error Handling and Alerting ................................................................................................................. 25
Error Classification .................................................................................................................................. 26
Auditing and Traceability ............................................................................................................................ 26
Logging .................................................................................................................................................... 26

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 2 of 32
 Audit........................................................................................................................................................ 27
Notifications............................................................................................................................................ 27
General Features ................................................................................................................................................ 28
Error Handling ............................................................................................................................................. 28
Technical Error Handling............................................................................................................................. 28
Business Error Handling .............................................................................................................................. 28
Glossary .......................................................................................................................................................... 29
Document Control .............................................................................................................................................. 30
Change Record ............................................................................................................................................ 30
Reviewers.................................................................................................................................................... 30
Distribution ................................................................................................................................................. 30
Open & Closed Issues .......................................................................................................................................... 31
Open Questions .............................................................................................................................................. 31

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 3 of 32
Introduction
ELAJOU is currently adopting Oracle Fusion cloud Services to manage functions of Financials and
Supply chain internal activities. Oracle Saudi Arabia is carrying out the design and development
process of the subject solution as a part of ELAJOU Fusion Implementation Project, delivered as
per Oracle True Cloud Method.

This Integration Catalogue lists the integrations that need to be built for ELAJOU to replace and
enhance the Fusion business Process within the new Oracle Fusion Cloud Implementation
project. It also defines the principles and patterns to be used.

Purpose of Document
The objective of this document is to provide ELAJOU with a High-Level Integration Architect
Design to realise the Solution as part of their Oracle Cloud Implementation.

The High-Level Design supports the delivery of a successful business transformation by:

• Providing High-Level Integration Architect Design for Implementation.

• Capturing operational considerations for this Implementation.

The main goal of this integration architecture is to deliver of a successful integration for
Automatic generation of ELAJOU ERP transactions and business process via managing proper
data transfers from and to ELAJOU Fusion ERP and 3rd party systems, while maintaining the best
business practices for ELAJOU. Moreover, to ensure smooth process while keeping the
integration process fully automated with minimal user intervention as well as achieving the
maximum ease of use and user-friendly process steps.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 4 of 32
Integration Platform
Oracle Integration Cloud (OIC) has been elected as the platform to build and operate the solution
integrations. OIC-Oracle Cloud Integration is a cloud-based Integration tool. With Oracle
Integration allows designing integrations to monitor and manage connections between different
applications, selecting from a portfolio of hundreds of prebuilt adapters and recipes to connect
with Oracle and third-party applications.

It seamlessly integrates on-

premises applications with Oracle
Cloud (SaaS) or other Cloud Apps to
other Cloud Apps. OIC brings
together all the capabilities of both
Application Integration and
Integration Analytics into a single
unified cloud service. Oracle
Integration Cloud brings real-time

and batch-based integration,

structured and unstructured
processes, case management, stream analytics and integration insight allowing customers to
service all their end-to-end integration needs in one cohesive platform so that all users can now
build and deliver capabilities needed to realize true Digital Business Transformations.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 5 of 32
Oracle Cloud Infrastructure (OCI)
Current/ Future Infrastructure
Oracle Cloud Infrastructure (OCI) is a set of complementary cloud services that enable you to build and run a
wide range of applications and services in a highly available hosted environment. OCI offers high-
performance compute capabilities (as physical hardware instances) and storage capacity in a flexible overlay
virtual network that is securely accessible from your on-premises network

Infrastructure
In this section we are trying to define major concepts and terminology of OCI and will try to capture
any relevant Customer
information in that perspective.
Tenancy
When you sign up for OCI, Oracle creates a tenancy for you in one of the available regions. This is
your home region.
Region
An OCI region is a localized geographic area that contains one or more data centers, called
availability domains. Regions are
independent of other regions, and vast distances can separate them (across countries or even
continents).
All the resources in this architecture are deployed in a single region. OC has chosen the following
region: JEDDAH DC
(Saudi Arabia) for their tenancy and all the resources in this architecture are deployed in a single
region.
Availability Domain (AD)
AD is a standalone, independent data centers within a region. The physical resources in each
availability domain are isolated from the resources in the other availability domains, which provides
fault tolerance. Availability domains don’t share infrastructure such as power or cooling, or the
internal availability domain network. So, a failure at one availability domain is unlikely to affect the
other availability domains in the region.
A Fault Domain is a logical grouping of hardware and infrastructure within an availability domain to
provide isolation of
resources in case of hardware failure or unexpected software changes. Fault domains enable you to
distribute your compute instances so that they are not on the same physical hardware within a
single Availability Domain, thereby introducing another layer of fault tolerance. In addition to host
anti-affinity, you get a level of power anti-affinity since the physical hardware has independent and
redundant power supplies preventing power faults within a Fault Domain from affecting other Fault
Domains.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 6 of 32
Fault domains can protect your application against unexpected hardware failures or outages caused
by maintenance on the underlying computer hardware. Additionally, you can launch instances of all
shapes within a fault domain.

ELAJOU current OCI Subscription:

• Name: 20084294 – Universal Credits

• Type: Infrastructure

• Status: Active

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 7 of 32
ELAJOU PROD and Non-PROD environments

ELAJOU tenancy is: elajouholding, please check below screen-shot

ELAJOU OCI will be consisted of 2 waves, one environment/ Service at a time.

First one will DEV environment then PROD environment.
All applications and databases are interdependent, and it seems relevant to migrate all together to
avoid synchronization issues.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 8 of 32
Services Scope per environment:

➢ Non Production:
o Database Cloud Service
o Integration Cloud Service
o WebLogic Content Service (Optional)
➢ Production:
o Database Cloud Service
o Integration Cloud Service
o WebLogic Content Service (Optional)

Some Assumptions about the Services:

❖ A freeze will also be required for moving to PROD environment during deployment operations.
❖ Database environments are with type Autonomous Transaction Processing (ATP).
❖ Integration environments are Enterprise Edition.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 9 of 32
ELAJOU Current OIC Provisioned:
❖ Dev/ Test Service:
• Name: AjouTestOIC

• Type: Enterprise

• URL: https://ajoutestoic-axxez98sximq-je.integration.me-jeddah-1.ocp.oraclecloud.com/

• Status: Active

• Message packs: 1 (You can transmit up to 5,000 messages per hour)

• Compartment: elajouholding (root) >> AjouTestPaaS >> OIC_Test

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 10 of 32
ELAJOU Current Database Provisioned:
❖ Dev/ Test Service:
o Name: ELAJOUTESTDB

o DB System Version: 19.18.0.0.0

o Oracle Database software edition: Standard Edition

o URL: https://cloud.oracle.com/dbaas/dbsystems/ocid1.dbsystem.oc1.me-jeddah-

1.anvgkljrfoxgq7ial5iyqsjosbahqeiaj7k5c6k2ki2ntdcooqkknhdviu4q?region=me-jeddah-1

o Status: Active

o Port: 1521

o Public IP: 144.24.211.189

o Compartment: elajouholding (root) >> AjouTestPaaS >> DB_TEST

o Availability domain: imSZ:ME-JEDDAH-1-AD-1

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 11 of 32
Audience
This document is primarily aimed at the following staff:

• ELAJOU Technical Architecture team.

• ELAJOU integration team.
• ELAJOU ERP Support Engineers.
• Oracle Integration Designers.
• Oracle Functional consultants

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 12 of 32
Integration Overview
The integration is aimed to perform business integration activities between 3rd Party Systems and Oracle
Fusion SaaS Modules (Inventory – Sales Orders – Procurement – Sales CX – General Ledger. . .etc):

JD Edward

Time Attendance Machine

ZATAC (e-Invoicing)

MS Azure AD

This integration solution under implementation shall manage data transfer of these business objects between
Oracle Fusion Cloud (SaaS) and these 3rd party systems.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 13 of 32
Assumptions
1. Oracle Integration Cloud (OIC) will be used as the integration platform.
2. If the interfacing requirements identified during the analysis phase exceeds the interfaces
in this scope, then the additional interfaces will be subject to CR.
3. Outbound and inbound interface from/ to Oracle ERP Cloud will be limited to the delivered
and configured data items (modules) included in scope of the project.
4. In case of file-based integrations, all data files generated by the outbound interface from
the Oracle ERP Cloud or to be read by inbound interfaces to Oracle ERP Cloud will be
placed in Universal Content Management (UCM) server of ERP Cloud.
5. Integrations using File Based Data Import (FBDI), ERP Data Load (HDL) or Extracts will be
in batch mode.
6. Outbound interfaces flat file will be delivered by extracting the relevant data from Oracle
Cloud application using BI Publisher (BIP) reports and will be delivered to UCM.OIC will be
used to transfer the files to the customer's common SFTP file system. It will be
responsibility of the 3rd party applications or customer to pull the files from the SFTP
server for consumption.
7. Coexistence integrations will be implemented using the integration prebuilt packages ex:
CPQ to Order management Integration.
8. You will need to allow the connection required to link between the Fusion Cloud with Your
on-premises.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 14 of 32
Integration Architecture
High-level Integration Architecture Design

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 15 of 32
Sample of Integration Cycles

Quote to Cash Cycle:

One of the important Cycle for ELAJOU project is the Quote to Cash Cycle, below design flow for
the proposed integration:

A ransac on that will be

ayables
A nvoice in for nter
ompany low

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 16 of 32
Procure to Pay Cycle

rocure to a ce
A nvoice

udget ontrol
Account ayables urchasing
Accoun ng
ournals

A nvoice for
nter company
low i ed Asset
upply lanning
Accoun ng Accoun ng
i ed Assets ournals eneral edger ournals
upply emand etails tems
roduct ub

nventory anagement

Accoun ng ournals

urchase e uisi on

ro ect etails
eceivables elf ervice rocurement

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 17 of 32
HCM Integration with Time Attendance:

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 18 of 32
Service Request Cycle:

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 19 of 32
Lead to Quote Cycle:

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 20 of 32
Integration Details
Prerequisites
• Provide Login credentials and URL of ELAJOU SaaS Cloud environment.
• Provide Login credentials and URL of ELAJOU PaaS Cloud environment.
• Enable Oracle Integration Server Port (443).
• Assign Required Business Roles to an Integration User.
• Provide Connection Security Certificate to access 3rd Party Web services.
• Create OIC REST Connection to access Oracle Cloud REST webservices.
• Create OIC Soap Connection to access Oracle Cloud SOAP webservices.
• Complete the Setup configuration of Oracle related Modules.
• Get the IP of Oracle Integration Cloud instance dedicated to ELAJOU so that is
added to the IP whitelist in any Network.
• Points Related to JD-Edward system, ELAJOU team will be taken care of any
development or API’s consuming inside JD-Edward system, it will be on ELAJOU
team shoulders.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 21 of 32
Integration Considerations
During the integration development the following points shall be taken inro consideration:

• Business Unit for Each Integration.

• Sync the consolidation for Business Groups implemented in Fusion SaaS.
• Integrations with Systems which are Up and Running.
• Freezing the Design and ELAJOU team to approve the Design from their side.
• The Availability of the 3rd Party systems teams in case required during the development/
Testing and Deployment phases.
• The Availability of the 3rd Party systems teams to share samples from the 3rd Party systems.
• The Availability of the 3rd Party systems teams During the SIT/ Testing sessions.

Integration Security
Oracle ERP Cloud APIs

To invoke an Oracle ERP Cloud service catalogue or event catalogue service from Oracle
Integration, you create a separate user in Oracle ERP Cloud. This user is then configured
in the connection in OIC. Only the Username Password Token policy is supported by the
Oracle Engagement Cloud adapter. The password is not visible in the Connection UI and
the underlying database cannot be accessed.

Oracle Fusion SOAP Web Services Security

To run SOAP web service processes, a user needs to be granted specific roles.
Furthermore, these web services are secured by the
oracle/wss11_saml_or_username_token_with_message_protection_service_policy policy.

This policy enforces message protection (integrity and confidentiality) and one of the
following authentication policies, based on whether the client uses a SAML or username
token, respectively:

• SAML-based authentication for inbound SOAP requests in accordance with the

WS-Security 1.1 standard.

• Username token authentication for inbound SOAP requests in accordance with

the WS-Security 1.1 standard.

In addition, the integration user running the integration needs to have been granted the
appropriate application roles and privileges for the data being processed.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 22 of 32
TLS Security

Certificates validate outbound SSL connections from OIC. If you make an SSL connection
in which the root certificate does not exist in Oracle Integration, an exception is thrown.
In that case, you must upload the appropriate certificate. A certificate enables Oracle
Integration to connect with external services.

Oracle Integration On-Premises Connectivity Agent

The security features for the Oracle Integration On-Premises Connectivity Agent are:

• No ports are opened on the on-premises system for communication.

• All communication is secured using SSL.

• The on-premises connectivity agent registers with Oracle Integration over SSL
using the provided Oracle Integration credentials.

• The on-premises connectivity agent checks for work by making outbound

requests through the firewall.

• The on-premises connectivity agent can use a proxy to access the internet (the
same proxy as other internal applications and browsers use). Authentication
support for outbound proxy access is provided.

• The on-premises connectivity agent connections are configured by the agent

retrieving the configuration details from Oracle Integration.

• The on-premises connectivity agent processes requests by pulling messages

from Oracle Integration across SSL.

• The on-premises connectivity agent posts responses by pushing messages

to Oracle Integration across SSL.

• All communication is initiated by the on-premises connectivity agent.

• No private SOAP-based web services are exposed.

• No data is persisted in the on-premises agent

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 23 of 32
Integration Monitoring
OIC Monitoring

You can monitor integrations by (1) integration (2) connections or by (3) integration
instance. Messages can be resubmitted from the OIC console. You can use the OIC
Dashboard below to manage and view integrations:

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 24 of 32
REST API
OIC provides the following REST APIs for monitoring purposes if a 3 rd party wishes to
integrate with OIC for this purpose. The available APIs encompass:

• Discard an Error Integration Instance

• Discard Error Integration Instances

• Download a Log File

• Download an Incident

• Resubmit an Error Integration Instance

• Resubmit Error Integration Instances

• Retrieve Activated Integrations

• Retrieve an Activated Integration

• Retrieve an Error Integration Instance

• Retrieve an Integration Instance

• Retrieve Audit Records

• Retrieve Error Integration Instances

• Retrieve Integration Instances

• Retrieve the Activity Stream

OIC Error Handling and Alerting

The errors pages in OIC display information about individual integration instances and
group the errors by integrations and connections over a specified time period.

The following can be performed from the errors page and its subpages:

• Search for and display errors by integration name or the total error count over a
specific time period.

• Resubmit errors.

• Discard (remove) errors by integration name.

• Display errors by connection name over a specific time period.

• Discard errors by connection name.

• Display errors by integration instance identifier, error location, or time of

occurrence over a specific time period.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 25 of 32
 • View the instance in which errors occurred.

• View the error message.

• View and discard errors by instance ID.

• View the audit trail and message payload of a failed integration instance.

• View the business identifiers of a failed integration instance.

OIC can alert failures by sending email notifications to an appropriate person or group as
part of an error handling flow.

OIC can also notify users by email with hourly or daily reports about total messages
received, total messages processed, successful messages, failed messages, and
successful message rate; with service failure alerts (for example, when a runtime or
storage service is down or an agent becomes unavailable); or with a detailed report every
five minutes when an integration failure occurs.

The following can be downloaded directly from the Integration Health dashboard:

• Activity Stream – audit trail

• Download Diagnostic Logs – server logs

• Download Incident – logs for a specific incident

Error Classification
Errors can be classified in a number of different ways.

One of them is the distinction between Business or Technical errors:

Business errors are related to data itself and could be raised by validations or
transformations. Their handling should include notification to business users.

Technical errors are related to infrastructure and implementation of integrations. They

can be handled automatically or by administrative staff.

Auditing and Traceability

OIC has a number of capabilities to support audit and traceability.

Logging
Log messages can be added to the activity stream and diagnostic logs by adding the log
activity at any point in the integration. The log message can either be a static message or
variable-populated message.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 26 of 32
During runtime, the messages in the log activities are written to the activity stream and
diagnostic logs. The messages can be viewed by accessing the Activity Stream from the
Monitoring console.

When adding the log activity in an integration flow, it allows logging to occur either always
or only when trace is enabled, the latter being the default. For the purposes of the
implementation at ELAJOU, logging, when used, will be set as only when trace is enabled.

Audit
When an integration is activated, there are options to enable tracing. This allows an audit
trail to be viewed in the Activity Stream. The payload can optionally be included in the
logs and Activity Stream. However, due to performance and data security concerns,
enabling payload tracing is not recommended for production environments.
Consequently, for the ELAJOU implementation, payload trace will not be enabled for the
production environment.

If you do not enable tracing, minimal logging details are created in ics-flow.log to indicate
when the activated integration begins and completes execution (regardless of execution
success or failure). You can download the logs on the Dashboard page.

Notifications
Notification emails can be sent to relevant users at specific points in the execution of an integration.
Notifications are typically used as part of an error handling flow.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 27 of 32
General Features
Error Handling

Errors could occur in a number of situations. The following tables shows these and their
handling:

Technical Error Handling

Error Scenario Error Handling

Execution of an expression results Error Monitoring

in an unhandled fault in an
expression language or query
language

Explicit Fault in a process Error process

Errors not specifically handled Error Monitoring

No response from target process Error Monitoring

within configured timeout period

Business Error Handling

Error Scenario Description Example

Invalid Data The value is not valid Value is not part of a defined list
of values, or it is a non-existing
technical id

Invalid Format The value is malformed A date is malformed

Mandatory field The value is empty, but the field

is mandatory

Duplicate Data Duplicate data is found based

on the specified keys

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 28 of 32
Glossary
Abbreviation Definition

API Application Program Interface

SaaS Software as a Service, i.e., Oracle Fusion Applications
OIC Oracle Integration Cloud
PaaS Platform as a Service
REST Representational State Transfer - an architectural API style for
developing web services. Leverages HTTP rather than proprietary
standards, frameworks and technologies
SOAP Simple Object Access Protocol
TCM True Cloud Method – implementation method solely available from
Oracle Consulting
UCM Universal Content Management. A document management system
based on Oracle Web Centre Content embedded in Oracle Fusion
Applications
WS Web Service
WSDL Web Services Definition Language
DFF Descriptive Flex Field: an extensible set of definable columns that
can be configured as per users needs.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 29 of 32
Document Control
Change Record

Date Author Version Change Reference

15 -Mar-2023 Oracle OCS 1.0 Initial Draft

Reviewers

Name Position

Distribution

Copy No. Name Location

1 Library Master Project Library

Note to Holders:

If you receive an electronic copy of this document and print it out, please write your name
on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover,
for document control purposes.

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 30 of 32
Open & Closed Issues
This section is used to summarise any issues relating to the document and responses to
these questions when known.

Target
ID Issue Resolution Responsibility Status
Date

Open Questions
This section is used to summarise any open questions relating to this integration design and
responses to these questions when known.

ID Topic Question Status Response

001

002

003

004

005

006

007

008

ELAJOU Integration Architecture Document | 12th of March 2023| Version 1.0| Page 31 of 32
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. This
document is provided for information purposes only and the contents
hereof are subject to change without notice. This document is not
warranted to be error-free, nor subject to any other warranties or
conditions, whether expressed orally or implied in law, including implied
warranties and conditions of merchantability or fitness for a particular
purpose. We specifically disclaim any liability with respect to this
document and no contractual obligations are formed either directly or
indirectly by this document. This document may not be reproduced or
transmitted in any form or by any means, electronic or mechanical, for any
purpose, without our prior written permission.

Oracle, True Cloud Method and Java are registered trademarks of Oracle
and/or its affiliates. Other names may be trademarks of their respective
owners.

AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks
or registered trademarks of Advanced Micro Devices. Intel and Intel Xeon
are trademarks or registered trademarks of Intel Corporation. All SPARC
trademarks are used under license and are trademarks or registered
trademarks of SPARC International, Inc. UNIX is a registered trademark
licensed through X/Open Company, Ltd. 1212

Connect with us

blogs.oracle.com

facebook.com/oracle

twitter.com/oracle

oracle.com