In this post we will learn about how to create OIM Disconnected Resource and test provisioning user to disconnected resource up on user request
Steps:
- Login to http://pokuri.demo.com:14000/sysadmin/ console with XELSYSADM account
- Click on Sandboxes
- Click on Create Sandbox
- Name Sandbox and click on "Save and Close"
- Click on "OK"
-- Check Sandbox status as "Active"
- Double Click on "Application Instances" in the left panel
- Click on "Create"
- Enter Disconnected Resource Name and select Disconnected Check Box and click on "Save"
- Click "OK"
- Notice message "Application Instance AdminApp created successfully" on top.
- Search if the Application instance created or not.
- As we are dealing with "Disconnected Resource" below change in "Process Definition" needed.
- Login to OIM Design Console with "XELSYSADM" account and double click on "Process Definition"
- Click on "Search" icon as shown in the below screen shot.
- Click on "Process Definition Table" tab at the bottom.
- Select the Disconnected application entry and double click on sequence number associated to it.
- Double click on "ManualProvisioningStart" Task.
- Click on "Yes"
- Click on "Task to Object Status Mapping" tab as shown in the below screen shot.
- Select status "C" row and double click in "Object Status" column which opens another pop up window.
- Select "Provisioned" and click on "OK"
- Click on "Save" button as shown in the below screen shot.
- Click on "Close" symbol as shown in the below screen shot.
- Click "Save" button again at the "Process Definition"
- Click "Publish Sandbox" to activate the changes.
- Click "Yes" to complete publishing sandbox.
- Disconnected resource configuration is completed.
Now, Lets test it by provisioning user to that disconnected resource.
- Login as an end user in to http://<<hostname>>:14000/identity
- Double Click on "Catalog"
- Click on the Search button as shown in the below screen shot.
- Make sure new disconnected resource just created appears here then click on "Add to Cart" button next to it
- Resource is added to cart
- Click on "Checkout"
- Add the details as needed and click on "Ready to submit"
- Click on "Submit"
- Check the request id and the request sent to administrator for approval
- Login as "xelsysadm" into identity console
- Double Click on "Home"
- In the dashboard, check "Pending Approvals" section and notice that there is a request for approval. Click on that request
- Click on "Approve" (if appropriate access)
- As it is disconnected resource, request will be sent to the concerned resource Inbox for fulfillment. In this case i just have "XELSYSADM" and so request comes to "XELSSYADM" Inbox. Click on "Inbox"
- Click on the "My Tasks" and see new task is waiting for "Complete" status. Once the Manual work is completed click on "Complete" button.
Now, Lets go and check the User Accounts and it's status
-- As shown in the below screen shot "AdminApp" is "Provisioned" successfully.
Hope this helps some one out there.
-- Siva Pokuri.
5) Change the default installation if required
6) Click Install
7) Installation is completed
Now, Lets deploy web gate instance with the command as shown in the screen shot below.
A new web gate instance folder will be created and copies required files.
Now, Configure the web gate instance with IIS Web Site as shown in the below screen shot.
Check "webgate.ini" file for registered web gate instance.
Check "web.config" file as shown in the below screen shots
Now, Restart the IIS web server
Create New 11g WebGate Profile from OAM Admin Console and copy the "cwallet.sso" & "ObAccessClient.xml" from output folder to webgate instance "config" folder as shown in the below screen shot.
Hope this helps some one out there!!-- Siva Pokuri
