|Support provided by||Support may be available from the original author.|
|Origin||Community (AMI Praha)|
Oracle Siebel Connector for midPoint is community developed connector that manages user accounts in Siebel user management.
|Transport||HTTP or HTTPs|
|Licence||Apache License 2.0|
This connector is using native Siebel WS. However, account data model exposed to IdM was configured on Siebel side to match particular deployment.
The following table lists all the configuration properties you can specify when setting up the Siebel connector:
|Maximum page size||X||int||100||Default page size used when explicit setting is not provided (e.g. during reconciliation task)|
|Connection timeout||X||int||60000||Timeout in [ms] to establish HTTP connection|
|Receive timeout||X||int||600000||Timeout in [ms] to retrieve data from single WS call. Should be set high enough for Search All operation to finish.|
|Basedir of SOAP log files|
|Enter path to the file system directory, if detailed SOAP logging is to be enabled. Leavy empty to disable SOAP logging.|
Building the connector
- In Siebel's data model, some values are more important then the other. These are marked as "primary" and connector supports that behaviour via proper attribute naming.
- Related positions (PrimaryPosition, SecondaryPositions) are identified with IDs, not names.
- When creating Siebel roles definition, you may be interested in Radio Button Roles so you can e.g. replace jobtitle value when new role assignment is approved in midPoint.
- When approving role assignment, your Siebel admin may enter some resource attribute values manually (e.g. primary position) using midPoint's forms. (also look for approvalSchema-level-formRef)