OIC Embedded File Server: Complete Guide to SFTP Integration
Use Embedded File Server in Oracle Integration Cloud (OIC): Complete Guide
Introduction
File-based integration is still widely used in enterprise environments. Applications such as Oracle Fusion Cloud Applications, ERP systems, HR platforms, banking systems, payroll applications, and legacy systems often exchange data through files such as CSV, XML, JSON, TXT, and ZIP files.
Traditionally, organizations deploy a separate SFTP server to receive and distribute these files. This approach introduces additional infrastructure, security configuration, maintenance, monitoring, and operational overhead.
Oracle Integration Cloud (OIC) provides an alternative through its File Server, an embedded SFTP server that is available within Oracle Integration. It allows organizations to securely store and exchange files without having to host and maintain a separate SFTP server. Oracle’s current documentation describes File Server as an embedded SFTP-compliant repository within Oracle Integration.
This article explains the concept, architecture, configuration, integration flow, security, practical use cases, and best practices for using the Embedded File Server in OIC.
What Is the Embedded File Server in OIC?
The Embedded File Server is a managed SFTP-based file repository integrated into Oracle Integration.
It provides a location where external applications, vendors, partners, and internal integrations can securely upload and download files.
Instead of building an architecture like:
External System → External SFTP Server → OIC
you can simplify it to:
External System → OIC File Server → OIC Integration
The File Server can therefore act as the central file exchange point for integration workflows.
Oracle states that File Server allows organizations to focus on integrations without hosting and maintaining a separate SFTP server.
Why Do We Need a File Server in OIC?
Many enterprise applications do not exchange information through REST or SOAP APIs alone.
For example:
- Payroll systems may generate employee files.
- Banks may provide transaction statements as files.
- Suppliers may send invoice files.
- HR applications may generate employee extracts.
- ERP systems may consume bulk data files.
- Legacy applications may only support SFTP.
- Third-party vendors may require SFTP for data exchange.
Without an embedded file server, organizations may need to maintain a separate SFTP server.
That creates additional responsibilities:
- Server provisioning
- OS maintenance
- Security configuration
- User management
- SSH key management
- Storage management
- Monitoring
- Patching
- Backup
- Network configuration
With OIC File Server, much of this infrastructure is managed as part of Oracle Integration.
High-Level Architecture
A typical architecture can look like this:
External System
|
| SFTP
v
+-----------------------+
| OIC File Server |
| Embedded SFTP |
+-----------------------+
|
| File Server Action
| or FTP Adapter
v
+-----------------------+
| Oracle Integration |
| Integration Flow |
+-----------------------+
|
+----------+----------+
| |
v v
Oracle Fusion REST/SOAP/API
Applications Applications
The external system uploads a file to the OIC File Server.
OIC then processes the file and sends the required information to the target application.
Oracle Integration currently provides two ways for an integration to interact with File Server:
- File Server action
- FTP Adapter
Oracle recommends the File Server action for easier setup and improved performance, while the FTP Adapter provides additional capabilities.
Key Features of OIC File Server
1. Embedded SFTP Server
The primary feature is the built-in SFTP capability.
External systems can use standard SFTP clients to transfer files securely.
For example:
External Application
|
| SFTP
v
OIC File Server
This eliminates the need to deploy another SFTP server for many integration scenarios.
2. Secure File Transfer
SFTP provides encrypted communication between the external client and File Server.
This makes it appropriate for enterprise file-transfer scenarios where sensitive business data is exchanged.
Examples include:
- Payroll files
- Employee information
- Financial reports
- Supplier information
- Banking files
- Invoice data
3. User Management
Administrators can configure File Server users and control their access.
For example:
PAYROLL_USER
HR_USER
FINANCE_USER
SUPPLIER_USER
Each user can be configured according to the requirements of the integration.
4. Directory-Based Access
Directories allow files to be organized according to business functions.
For example:
/inbound
/hr
/finance
/payroll
/outbound
/reports
/payroll
/archive
This makes file management easier and helps separate data belonging to different integrations.
5. External SFTP Access
Partners and external applications can connect to File Server using SFTP client software.
Typical clients include:
- WinSCP
- FileZilla
- Command-line SFTP clients
- Enterprise file-transfer applications
The external application can upload or download files according to its assigned permissions.
Prerequisites
Before using File Server, there are several things to consider.
1. Oracle Integration Instance
You need an Oracle Integration instance.
2. File Server Must Be Enabled
An administrator must enable File Server for the OIC instance through the Oracle Cloud Infrastructure Console. Oracle’s current documentation specifically identifies this as a prerequisite.
3. Required Permissions
The administrator needs appropriate OCI permissions to manage the Integration instance.
4. SSH Authentication
For external SFTP access, configure the appropriate authentication mechanism and SSH keys as required by the environment.
5. Network Connectivity
External clients must be able to reach the OIC File Server endpoint.
Step 1: Enable File Server
In the current Oracle Integration 3 experience, File Server is enabled from the OCI Console.
Navigate to the Integration instance details.
Look for the File Server option under the Integration Instance Information section.
If File Server is disabled, select:
Enable
Oracle notes that enabling File Server can take several minutes while the instance is updated.
Conceptually:
OCI Console
|
v
Integration Instance
|
v
Integration Instance Information
|
v
File Server
|
v
Enable
After enablement, File Server can be configured and used for file-transfer scenarios.
Step 2: Configure File Server Users
The next step is to configure users who will access the File Server.
For example:
User: PAYROLL_USER
Purpose: Payroll file exchange
Authentication: SSH-based
A dedicated user for each business function is generally preferable to sharing one account across multiple integrations.
For example:
HR_USER → HR files
FIN_USER → Financial files
PAYROLL_USER → Payroll files
SUPPLIER_USER → Supplier files
This improves security and simplifies auditing.
Step 3: Configure SSH Authentication
SFTP connections require secure authentication.
A common enterprise approach is to use SSH public/private key authentication.
Conceptually:
External System
|
| Private Key
|
v
SFTP Authentication
|
| Public Key registered
v
OIC File Server
The private key should remain securely stored on the client side.
The public key is configured according to the File Server user configuration.
Best practice: Never share private SSH keys between unrelated applications or teams.
Step 4: Create and Organize Directories
Create a directory structure that reflects the integration architecture.
For example:
/inbound
/employee
/supplier
/payroll
/outbound
/employee
/supplier
/payroll
/archive
/employee
/supplier
/payroll
/error
A good folder structure makes it easier to:
- Identify incoming files
- Separate integrations
- Archive processed files
- Troubleshoot failures
- Apply appropriate access controls
Step 5: Assign Permissions
Users should only receive the access they require.
For example:
PAYROLL_USER
|
+-- /inbound/payroll
| Read + Write
|
+-- /outbound/payroll
Read
Avoid giving every user access to every directory.
This follows the principle of least privilege.
Step 6: Obtain the File Server Connection Details
After File Server is enabled and configured, obtain the connection information required by the external SFTP client.
The connection typically requires information such as:
Host
Port
Username
Authentication method
Directory
The exact endpoint and connection information should be taken from the OIC environment rather than hard-coded from examples.
Step 7: Connect From an External SFTP Client
An external application or SFTP client can connect to the OIC File Server.
For example, conceptually:
sftp <username>@<file-server-host>
After authentication, the user can navigate to the permitted directory.
Example:
cd /inbound/payroll
put payroll_2026_08_22.csv
The file is then available in OIC for processing.
Step 8: Use File Server From an OIC Integration
Once the external system uploads the file, an OIC integration can process it.
Oracle Integration provides the File Server action for interacting with files stored in File Server. The FTP Adapter can also be used when its additional capabilities are required.
A typical flow is:
File Server
|
v
Read File
|
v
Validate File
|
v
Parse Data
|
v
Transform Data
|
v
Invoke Target Application
|
v
Archive File
Example: Employee Data Integration
Consider an HR system that generates an employee CSV file every night.
Example:
EMPLOYEE_20260822.csv
The file contains:
Employee_ID,Name,Department,Salary
1001,John,IT,75000
1002,Smith,Finance,68000
1003,David,HR,62000
The external HR system uploads the file to:
/inbound/employee
OIC then processes the file.
Integration flow
HR System
|
| SFTP Upload
v
/inbound/employee
|
v
OIC Integration
|
+--> Validate CSV
|
+--> Transform Data
|
+--> Invoke REST API
|
v
Target Application
|
v
/archive/employee
After successful processing, the file can be moved to an archive location according to the integration design.
Example: Payroll Integration
Payroll is another excellent use case.
Suppose a payroll application generates:
PAYROLL_20260822.csv
The payroll provider uploads the file to:
/inbound/payroll
OIC processes the file and sends the information to the appropriate Oracle Cloud application or third-party system.
The flow becomes:
Payroll Provider
|
| SFTP
v
OIC File Server
|
v
OIC Integration
|
+--> Validate
|
+--> Transform
|
+--> Enrich
|
v
Oracle/Third-Party Application
|
v
Archive
This architecture avoids maintaining a separate SFTP infrastructure solely for the integration.
File Server Action vs FTP Adapter
This is an important distinction for OIC developers.
File Server Action
The File Server action is designed specifically for interacting with files in OIC File Server.
It provides:
- Easier configuration
- Direct interaction with File Server
- Improved performance in supported scenarios
Oracle recommends considering the File Server action when working directly with the embedded File Server.
FTP Adapter
The FTP Adapter is a broader integration adapter.
It can be used to interact with FTP/SFTP endpoints, including OIC File Server.
It can be useful when your integration requires capabilities that aren’t available through the File Server action.
Therefore:
Need direct File Server interaction?
|
v
File Server Action
Whereas:
Need FTP/SFTP adapter capabilities?
|
v
FTP Adapter
Polling vs Event-Driven File Processing
Historically, file-based integrations often used scheduled polling.
For example:
Every 15 minutes
|
v
Check /inbound
|
v
Is there a file?
|
+--+--+
| |
Yes No
| |
Process End
Oracle introduced File Server Events in the 25.04 release of Oracle Integration.
These events can automatically trigger integrations when files or folders are created or deleted through an SFTP connection. The supported event types include:
- File created
- File deleted
- Folder created
- Folder deleted
This enables an event-driven architecture such as:
Partner Uploads File
|
v
File Server
|
File Created Event
|
v
OIC Integration
|
v
Process File
This can eliminate unnecessary polling for supported event-driven scenarios.
Oracle’s initial File Server Events implementation has specific limitations; for example, the documented events are triggered by file/folder operations through the FTP Adapter/SFTP connection and not by all native File Server actions.
File Processing Lifecycle
A well-designed file integration should have a defined lifecycle.
For example:
+-------------+
| External |
| System |
+------+------+
|
| Upload
v
+-------------+
| Inbound |
+------+------+
|
v
+-------------+
| Processing |
+------+------+
|
+-----------+-----------+
| |
Success Error
| |
v v
Archive Error
Folder Folder
This makes troubleshooting easier.
For example:
/inbound
/archive
/error
can provide a simple operational model.
Security Best Practices
Security should be a major consideration when implementing File Server.
1. Use Dedicated Users
Do not use one generic account for every external system.
Instead:
BANK_USER
PAYROLL_USER
HR_USER
SUPPLIER_USER
2. Follow Least Privilege
Give users access only to the directories they require.
For example:
SUPPLIER_USER
↓
/inbound/supplier
There is no reason for this user to access:
/payroll
/finance
/hr
3. Protect Private Keys
Private SSH keys should never be:
- Uploaded to public repositories
- Sent through email
- Shared through chat
- Stored in plain-text configuration files
Use an appropriate enterprise secret-management approach.
4. Use PGP for Sensitive Data Where Required
SFTP encrypts data during transport, but organizations may also require file-level encryption.
For highly sensitive information, consider PGP encryption according to organizational security requirements.
For example:
Plain File
|
v
PGP Encryption
|
v
Encrypted File
|
v
SFTP Transfer
5. Archive Processed Files
Do not leave processed files indefinitely in the inbound directory.
A common approach is:
/inbound
|
| successful processing
v
/archive
For failures:
/inbound
|
| processing failure
v
/error
File Naming Best Practices
A predictable naming convention makes automation easier.
Instead of:
data.csv
consider:
EMPLOYEE_20260822.csv
or:
PAYROLL_20260822_001.csv
For larger environments:
<SYSTEM>_<FUNCTION>_<DATE>_<SEQUENCE>.<EXT>
Example:
HCM_EMPLOYEE_20260822_001.csv
This helps with:
- Identification
- Troubleshooting
- Duplicate detection
- Automation
- Auditing
Error Handling
File-based integrations should include proper error handling.
Possible errors include:
- Invalid file format
- Missing mandatory fields
- Duplicate file
- Incorrect file name
- Authentication failure
- Connection failure
- Target application failure
- Transformation error
- Insufficient permissions
A simple design could be:
File
|
v
Validate File
|
+------+------+
| |
Valid Invalid
| |
v v
Process /error
|
+---+---+
| |
Success Failure
| |
v v
/archive /error
Monitoring
Monitoring is an important part of production implementation.
Use OIC monitoring capabilities to check:
- Integration instances
- Successful executions
- Failed executions
- Processing times
- Error messages
- File-processing status
Oracle’s File Server capabilities also include management APIs, and Oracle notes that management API access requires the ServiceAdministrator role.
A production support team should define monitoring and alerting procedures before moving the integration to production.
Common Real-World Use Cases
1. Payroll Processing
Payroll Provider
↓
SFTP
↓
OIC File Server
↓
OIC Integration
↓
Oracle Fusion
2. Supplier Invoice Processing
Supplier
↓
Invoice File
↓
OIC File Server
↓
OIC Integration
↓
ERP
3. Bank Statement Processing
Bank
↓
Statement File
↓
OIC File Server
↓
Transformation
↓
Finance Application
4. Employee Data Integration
HR System
↓
Employee CSV
↓
File Server
↓
OIC
↓
Target HR Application
5. Legacy Application Integration
Legacy applications often support file transfer rather than modern APIs.
OIC File Server can act as the bridge:
Legacy System
|
| SFTP
v
OIC File Server
|
v
OIC Integration
|
| REST/SOAP
v
Modern Cloud Application
This is one of the strongest use cases for OIC.
Advantages of Embedded File Server
Reduced Infrastructure
There is no need to maintain a separate SFTP server for supported scenarios.
Simplified Architecture
The file-transfer capability is integrated with the integration platform.
Secure File Exchange
SFTP provides encrypted transport.
Better Integration With OIC
Files can directly participate in OIC integration workflows.
Reduced Operational Overhead
Organizations can reduce responsibilities associated with maintaining standalone SFTP infrastructure.
Suitable for B2B Integrations
External partners can exchange files through SFTP.
Limitations and Considerations
Although File Server is powerful, it should not automatically replace every enterprise file-transfer platform.
Consider:
Storage Requirements
Evaluate file size, volume, retention, and storage requirements before implementation.
File Retention
Define how long files should remain in inbound, outbound, archive, and error directories.
Security
Use appropriate authentication, authorization, encryption, and key-management practices.
High-Volume Transfers
Analyze throughput and processing requirements for very large or high-frequency file workloads.
External Partner Requirements
Check whether partners require specific SFTP capabilities that may influence whether OIC File Server is appropriate.
Best-Practice Architecture
A production-ready architecture could look like this:
External Partners
|
Secure SFTP
|
v
+-------------------+
| OIC File Server |
+---------+---------+
|
+------------+------------+
| |
File Event Integration
| |
+------------+------------+
|
v
+-------------------+
| Validate / Parse |
+---------+---------+
|
v
+-------------------+
| Transform / Map |
+---------+---------+
|
v
+-------------------+
| Target Application |
+---------+---------+
|
+------+------+
| |
Success Error
| |
v v
/archive /error
This architecture provides clear separation between:
- File reception
- Processing
- Transformation
- Target delivery
- Archival
- Error handling
Troubleshooting Checklist
If an external system cannot upload a file, check:
Connection
- Is File Server enabled?
- Is the correct endpoint being used?
- Is the correct port configured?
- Is network connectivity available?
Authentication
- Is the username correct?
- Is the SSH public key configured correctly?
- Is the private key being used correctly?
Authorization
- Does the user have access to the target directory?
- Are read/write permissions correctly configured?
File
- Is the file name correct?
- Is the file format supported by the integration?
- Is the file located in the expected directory?
Integration
- Is the integration active?
- Is the trigger/event configuration correct?
- Is the integration failing during mapping or target invocation?
Monitoring
Check OIC monitoring and error details to identify the exact processing failure.
File Server vs Traditional SFTP Server
| Feature | OIC File Server | Traditional SFTP Server |
|---|---|---|
| SFTP support | Yes | Yes |
| Managed within OIC | Yes | No |
| Separate server required | No | Usually |
| OIC integration integration | Native | Requires connection |
| Infrastructure maintenance | Lower | Higher |
| User management | Integrated | Separate |
| Suitable for OIC workflows | Excellent | Requires additional integration |
| External SFTP access | Yes | Yes |
The main advantage is not that SFTP itself is new; rather, the capability is integrated into the Oracle Integration platform.
Important Interview Questions
1. What is the Embedded File Server in OIC?
It is a managed SFTP server integrated into Oracle Integration that allows external systems and integrations to securely exchange files without requiring a separate SFTP server.
2. Why would you use File Server instead of an external SFTP server?
It can simplify architecture and reduce the infrastructure and operational overhead of maintaining a separate SFTP environment.
3. How can an external system access OIC File Server?
Through SFTP using the configured File Server endpoint, user credentials/authentication, and appropriate directory permissions.
4. How does an OIC integration interact with File Server?
It can use the File Server action or the FTP Adapter, depending on the integration requirements.
5. What are File Server Events?
They are OIC system events that can trigger integrations when supported file or folder creation/deletion operations occur on File Server.
6. Why are archive and error folders useful?
They separate successfully processed files from failed files and make operational troubleshooting easier.
Conclusion
The Embedded File Server in Oracle Integration is a valuable capability for organizations that depend on secure file-based integrations.
Instead of deploying and maintaining a separate SFTP infrastructure, organizations can use the managed File Server capability within Oracle Integration for supported file-exchange scenarios.
A typical implementation looks like:
External System
↓
SFTP
↓
OIC File Server
↓
OIC Integration
↓
Transform / Validate
↓
Target Application
↓
Archive / Error
For modern OIC implementations, File Server can be combined with the File Server action, FTP Adapter, and File Server Events to create efficient file-processing architectures. Oracle’s newer event-driven capability can also reduce the need for scheduled polling when the documented event conditions are met.
The key takeaway is:
OIC File Server turns file transfer from a separate infrastructure problem into an integrated part of the enterprise integration platform.
For current Oracle Integration 3 implementations, always verify the exact configuration steps, permissions, limits, and supported features against Oracle’s current documentation because the File Server capabilities have evolved over time.
Official Oracle Resources
Oracle Integration – File Server Documentation
Using File Server in Oracle Integration 3 – Oracle Documentation
