Chat now with support
Chat with Support

Identity Manager 8.1.5 - Administration Guide for Connecting to Oracle E-Business Suite

Mapping an Oracle E-Business Suite in One Identity Manager Synchronizing Oracle E-Business Suite
Setting up the initial synchronization Customizing the synchronization configuration Executing synchronization Tasks after a synchronization Troubleshooting
Managing E-Business Suite user accounts and employees Provision of login information Managing entitlement assignments Mapping of E-Business Suite objects in One Identity Manager Handling of E-Business Suite objects in the Web Portal Basic configuration data Users and permissions for synchronizing with Oracle E-Business Suite Default project templates for synchronizing an Oracle E-Business Suite Editing system objects Configuration parameters for managing Oracle E-Business Suite Example of a schema extension file About us

General master data for Job servers

NOTE: All editing options are also available in the Designer under Base Data | Installation | Job server.

NOTE: More properties may be available depending on which modules are installed.
Table 42: Job server properties

Property

Meaning
Server Job server name.
Full server name Full server name in accordance with DNS syntax.

Example:

<Name of server>.<Fully qualified domain name>

Target system Computer account target system.
Language Language of the server.
Server is cluster Specifies whether the server maps a cluster.
Server belongs to cluster

Cluster to which the server belongs.

NOTE: The Server is cluster and Server belongs to cluster properties are mutually exclusive.
IP address (IPv6) Internet protocol version 6 (IPv6) server address.
IP address (IPv4) Internet protocol version 4 (IPv4) server address.
Copy process (source server) Permitted copying methods that can be used when this server is the source of a copy action. At present, only copy methods that support the Robocopy and rsync programs are supported.

If no method is given, the One Identity Manager Service determines the operating system of the server during runtime. Replication is then performed with the Robocopy program between servers with a Windows operating system or with the rsync program between servers with a Linux operating system. If the operating systems of the source and destination servers differ, it is important that the right copy method is applied for successful replication. A copy method is chosen that supports both servers.

Copy process (target server) Permitted copying methods that can be used when this server is the destination of a copy action.
Coding Character set coding that is used to write files to the server.
Parent Job server Name of the parent Job server.
Executing server Name of the executing server. The name of the server that exists physically and where the processes are handled.

This input is evaluated when the One Identity Manager Service is automatically updated. If the server is handling several queues, the process steps are not supplied until all the queues that are being processed on the same server have completed their automatic update.

Queue Name of the queue to handle the process steps. Each One Identity Manager Service within the network must have a unique queue identifier. The process steps are requested by the Job queue using this exact queue name. The queue identifier is entered in the One Identity Manager Service configuration file.
Server operating system Operating system of the server. This input is required to resolve the path name for replicating software profiles. The values Win32, Windows, Linux, and Unix are permitted. If no value is specified, Win32 is used.
Service account data One Identity Manager Service user account information. In order to replicate between non-trusted systems (non-trusted domains, Linux server), the One Identity Manager Service user information has to be declared for the servers in the database. This means that the service account, the service account domain, and the service account password have to be entered for the server.
One Identity Manager Service installed Specifies whether a One Identity Manager Service is installed on this server. This option is enabled by the QBM_PJobQueueLoad procedure the moment the queue is called for the first time.

The option is not automatically removed. If necessary, you can reset this option manually for servers whose queue is no longer enabled.

Stop One Identity Manager Service Specifies whether the One Identity Manager Service has stopped. If this option is set for the Job server, the One Identity Manager Service does not process any more tasks.

You can make the service start and stop with the appropriate administrative permissions in the Job Queue Info program. For more detailed information, see the One Identity Manager Process Monitoring and Troubleshooting Guide.

No automatic software update

Specifies whether to exclude the server from automatic software updating.

NOTE: Servers must be manually updated if this option is set.
Software update running Specifies whether a software update is currently running.

Last fetch time

Last time the process was collected.

Last timeout check

The time of the last check for loaded process steps with a dispatch value that exceeds the one in the Common | Jobservice | LoadedJobsTimeOut configuration parameter.

Server function Server functionality in One Identity Manager. One Identity Manager processes are handled with respect to the server function.
Related topics

Specifying server functions

NOTE: All editing options are also available in the Designer under Base Data | Installation | Job server.

The server function defines the functionality of a server in One Identity Manager. One Identity Manager processes are handled with respect to the server function.

NOTE: More server functions may be available depending on which modules are installed.
Table 43: Permitted server functions

Server function

Remark

Update server

This server automatically updates the software on all the other servers. The server requires a direct connection to the database server that One Identity Manager database is installed on. It can run SQL tasks.

The server with the One Identity Manager database installed on it is labeled with this functionality during initial installation of the schema.

SQL processing server

It can run SQL tasks. The server requires a direct connection to the database server that One Identity Manager database is installed on.

Several SQL processing servers can be set up to spread the load of SQL processes. The system distributes the generated SQL processes throughout all the Job servers with this server function.

CSV script server

This server can process CSV files using the ScriptComponent process component.

One Identity Manager Service installed

Server on which a One Identity Manager Service is installed.

SMTP host

Server from which One Identity Manager Service sends email notifications. Prerequisite for sending mails using One Identity Manager Service is SMTP host configuration.

Default report server

Server on which reports are generated.

Oracle E-Business Suite connector

Server on which the Oracle E-Business Suite connector is installed. This server synchronizes the Oracle E-Business Suite target system.

Related topics

Target system managers

A default application role exists for the target system manager in One Identity Manager. Assign the employees who are authorized to edit all E-Business Suite systems in One Identity Manager to this application role.

Define additional application roles if you want to limit the edit permissions for target system managers to individual systems. The application roles must be added under the default application role.

For detailed information about implementing and editing application roles, see the One Identity Manager Authorization and Authentication Guide.

Implementing application roles for target system managers

  1. The One Identity Manager administrator allocates employees to be target system administrators.

  2. These target system administrators add employees to the default application role for target system managers.

    Target system managers with the default application role are authorized to edit all the E-Business Suite systems in One Identity Manager.

  3. Target system managers can authorize other employees within their area of responsibility as target system managers and if necessary, create additional child application roles and assign these to individual E-Business Suite systems.

Table 44: Default application roles for target system managers
User Tasks

Target system managers

 

Target system managers must be assigned to the Target systems | Oracle E-Business Suite or a child application role.

Users with this application role:

  • Assume administrative tasks for the target system.

  • Create, change, or delete target system objects like user accounts or groups.

  • Edit password policies for the target system.

  • Prepare entitlements to add to the IT Shop.

  • Can add employees who have an other identity than the Primary identity.

  • Configure synchronization in the Synchronization Editor and define the mapping for comparing target systems and One Identity Manager.

  • Edit the synchronization's target system types and outstanding objects.

  • Authorize other employees within their area of responsibility as target system managers and create child application roles if required.

To initially specify employees to be target system administrators

  1. Log in to the Manager as a One Identity Manager administrator (Base role | Administrators application role)
  2. Select the One Identity Manager Administration | Target systems | Administrators category.
  3. Select the Assign employees task.
  4. Assign the employee you want and save the changes.

To add the first employees to the default application as target system managers

  1. Log in to the Manager as a target system administrator (Target systems | Administrators application role).

  2. Select the One Identity Manager Administration | Target systems | Oracle E-Business Suite category.

  3. Select the Assign employees task.

  4. Assign the employees you want and save the changes.

To authorize other employees as target system managers when you are a target system manager

  1. Log in to the Manager as a target system manager.

  2. Select the application role in the Oracle E-Business Suite | Basic configuration data | Target system managers category.

  3. Select the Assign employees task.

  4. Assign the employees you want and save the changes.

To specify target system managers for individual E-Business Suite systems

  1. Log in to the Manager as a target system manager.

  2. Select the Oracle E-Business Suite | Systems category.

  3. Select the system in the result list.

  4. Select the Change master data task.

  5. On the General tab, select the application role in the Target system manager menu.

    - OR -

    Next to the Target system manager menu, click to create a new application role.

    1. Enter the application role name and assign the Target systems | Oracle E-Business Suite parent application role.

    2. Click OK to add the new application role.

  6. Save the changes.

  7. Assign employees to this application role who are permitted to edit the system in One Identity Manager.

Related topics

Users and permissions for synchronizing with Oracle E-Business Suite

The Oracle E-Business Suite requires read access rights to at least the following database objects in the Oracle Database to be connected.

Table 45: Tables and views with select entitlements

Tables

Views

  • ak.ak_attributes_tl

  • ak.ak_excluded_items

  • ak.ak_resp_security_attr_values

  • ak.ak_web_user_sec_attr_values

  • applsys.fnd_application

  • applsys.fnd_application_tl

  • applsys.fnd_data_groups

  • applsys.fnd_data_group_units

  • applsys.fnd_languages

  • applsys.fnd_menus

  • applsys.fnd_menus_tl

  • applsys.fnd_profile_options

  • applsys.fnd_profile_option_values

  • applsys.fnd_request_groups

  • applsys.fnd_resp_functions

  • applsys.fnd_responsibility

  • applsys.fnd_responsibility_tl

  • applsys.fnd_security_groups

  • applsys.fnd_security_groups_tl

  • applsys.fnd_user

  • apps.fnd_user_resp_groups_all

  • apps.fnd_user_resp_groups_direct

  • apps.fnd_user_resp_groups_indirect

  • apps.fnd_usr_roles

  • ak.ak_attributes_tl#

  • ak.ak_excluded_items#

  • ak.ak_resp_security_attr_values#

  • ak.ak_web_user_sec_attr_values#

  • applsys.fnd_application#

  • applsys.fnd_application_tl#

  • applsys.fnd_data_groups#

  • applsys.fnd_data_group_units#

  • applsys.fnd_languages#

  • applsys.fnd_menus#

  • applsys.fnd_menus_tl#

  • applsys.fnd_request_groups#

  • applsys.fnd_responsibility#

  • applsys.fnd_responsibility_tl#

  • applsys.fnd_security_groups#

  • applsys.fnd_security_groups_tl#

  • applsys.fnd_user#

Table 46: Tables with select permissions for synchronizing people data

Tables

Views

  • ap.ap_supplier_contacts

  • ar.hz_parties

  • hr.hr_all_organization_units

  • hr.hr_locations_all

  • hr.per_all_assignments_f

  • hr.per_all_people_f

  • hr.per_job_groups

  • hr.per_jobs

  • hr.per_org_structure_versions

  • hr.per_org_structure_elements

  • hr.per_roles

  • hr.per_sec_profile_assignments

  • hr.per_security_profiles

  • hr.hr_all_organization_units#

  • hr.hr_locations_all#

  • hr.per_all_assignments_f#

  • hr.per_all_people_f#

  • hr.per_job_groups#

  • hr.per_jobs#

  • hr.per_org_structure_versions#

  • hr.per_org_structure_elements#

  • hr.per_sec_profile_assignments#

  • hr.per_security_profiles#

Table 47: Tables with execute permissions for synchronizing employee data

Tables
  • hr.per_sec_profile_asg_api
Table 48: Tables with select entitlements for schema types that are created in the connector schema, but are not contained in the default mapping

Tables

Views

  • applsys.fnd_request_group_units

  • applsys.fnd_request_sets

  • applsys.fnd_request_sets_tl

  • applsys.fnd_user_preferences

  • applsys.fnd_request_group_units#

  • applsys.fnd_request_sets#

  • applsys.fnd_user_preferences#

Table 49: Stored procedures with execute permissions

Stored procedures

  • apps.fnd_user_pkg

    This grants permissions for the following procedures.

    • apps.fnd_user_pkg.AddResp

    • apps.fnd_user_pkg.change_user_name

    • apps.fnd_user_pkg.changepassword

    • apps.fnd_user_pkg.CreateUser

    • apps.fnd_user_pkg.DelResp

    • apps.fnd_user_pkg.DisableUser

    • apps.fnd_user_pkg.UpdateUser

    • apps.fnd_user_pkg.user_synch

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating