Go to servers, oim_server1. You can see that SSL Listen Port is enabled.

27-18 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager 3. In addition to the SoD check being triggered by default before any level of approval, it can be triggered by attaching the predefined DefaultSODApproval workflow. The workflow can be attached to the operational level of approval by creating an approval policy. For using the default workflow, see Appying the Workflow By Using Approval Policy on page 27-30. This workflow contains an approval task that is assigned to the system administrator. After this approval task, a call is made to the asynchronous SoDCheck Web service to start SoD check. To complete and callback the SoDCheck Web service, you must run the Get SOD Check Results Approval scheduled job. The workflow with SoDCheck Web service call is shown in Figure 27–6 . Note: In Oracle Identity Manager 11g, patches were required on SOA and WebLogic Server to allow the SoD workflow to work. No patch is required with the release of Oracle Identity Manager 11g PS1. Note: There are three levels of approval for any request: template-level approval, request-level approval, and operational-level approval. DefaultSODApproval workflow must only be attached at the operational level. For bulk requests, the request-level approval is common for all resources and users. After this level of approval, separate requests are created for each combination of resource and user. The workflow performs SoD check separately for each resource and user at a time. The workflow is useful when SoD Check is required after request-level approval. One such instance is when the connector IT resource information is entered by the approver. Here, the IT Resource field in the request dataset is made approver-only, as shown below: AttributeReference name=EBS Server attr-ref=EBS Server type=String length=50 widget=itresource-lookup available-in-bulk=true itresource-type=eBusiness Suite UM required=true approver-only=true In this example, the IT resource information is not available when the request is raised. It is available only after the approver enters it. If it is entered during request-level approval, then the DefaultSODApproval workflow can be used at operational level.