Oracle EBS Connector
Introduction
Description
Oracle Connector could manage an Oracle E-Business Suite.
Managed System
This connector is specific for integration with an Oracle E-Business Suite, if you want to connect a generic SQL database, please visit the following page: SQL Connector.
For more information about the Oracle E-Business Suite, please visit the following page: Oracle E-Business Suite
For more information to check if your system may be synchronized with this connector you do not hesitate to contact us through our Contact form
Prerequisites
It is needed a user with access and permissions to the database.
Download and Install
This addon is located in the Connectors section and its name is Oracle EBS Connector.
For more information about the installation process you can visit the Addons Getting started page.
Agent Configuration
This connector could manage only User objects.
Users created on Soffid will be created on EBS, in the same way disabled users on Soffid will be disabled on EBS.
The responsibilities that exist in EBS can be assigned to the users. They must be created like roles on Soffid System previously, with the same name that the responsibility has on EBS.
For instance: FND_RESP | CSF | CSF_FS_PDA_REP | STANDARD.
Basic
Generic parameters
After the installation of the addon, you may create and configure agent instances.
To configure this Oracle EBS Connector you must select "OracleEBudsinessAgent" in the attribute "Type" of the generic parameters section in the agents' page configuration.
For more information about how you may configure the generic parameters of the agent, see the following link: Agents configuration
Custom parameters
Below there are the specific parameters for this agent implementation:
|
Parameter |
Description |
|---|---|
|
User |
User name to authenticate |
|
Oracle password |
Password of the user to authenticate |
|
Connection string to database |
Database URL. Use something like jdbc:oracle:thin:@host:port:sid |
Load triggers
You can define BeanShell scripts that will be triggered when data is loaded into Soffid (incoming triggers). The trigger result will be a boolean value, true to continue or false to stop.
Triggers can be used to validate or perform a specific action just before performing an operation or just after performing an operation into Soffid objects.
To view some examples, visit the Incoming triggers examples page.
Account metadata
Agents allow you to create additional data, on the "Account metadata" tab, to customize the accounts created for that agent. This additional information will be loaded with the agent's information, or calculated as defined in the mappings.
The additional data can be used in both mappings and triggers.
The attributes which you define here will be shown when you click on the proper account, on the Accounts Tabs at user page.
Operational
Monitoring
After the agent configuration you could check on the monitoring page if the service is running in the Synchronization Server, please go to:
Tasks
Authoritative
If you are checked "Authorized identity source", an automatic task to load identities from the managed system to Soffid is available, please go to:
And you will something like "Import authoritative data from <AGENT_NAME>".
Reconcile
To manage an automatic task to synchronize user objects from the managed system to Soffid is available, please go to:
And you will do something like "Reconcile all accounts from <AGENT_NAME>".
Synchronization
Regarding the synchronization of the objects, there are two possible options:
- If you are checked the generic attribute "Read Only" in the "Basics" tab, only the changes in the managed systems will be updated in Soffid. We recommend these options until the global configuration of Soffid will be tested.
- If you are not checked the generic attribute "Read Only" in the "Basics" tab, all the changes in Soffid or the managed system will be updated in the other. Note that this synchronization must be configured in the "Attribute mapping" tab correctly.
For more information about how you may configure the generic parameters of the agent, see the following link: Agents configuration