OIG 11G R2 PS1 Field Enablement Training - Oracle Software...

OIG 11G R2 PS1 Training

Disconnected Resources Additional Implementations Oracle Proprietary - Restricted to Personal Use in an Oracle partner training class

1 | P a g e

OIG 11G R2 PS1 Field Enablement Training

Lab16_A-Disconnected Resources Additional Implementations

Disclaimer: The Virtual Machine Image and other software are provided for use

only during the workshop. Please note that you are responsible for deleting

them from your computers before you leave. If you would like to try out any of

the Oracle products, you may download them from the Oracle Technology Net-

work (http://www.oracle.com/technology/index.html) or the Oracle E-Delivery

WebSite (http://edelivery.oracle.com)

http://www.oracle.com/technology/index.html

http://edelivery.oracle.com/



2 | P a g e

Table of Contents

OIG 11G R2 PS1 Field Enablement Training .................................................................................................. 1

Disconnected Resources Additional Implementations ............................................................................. 1

1. Introduction .......................................................................................................................................... 3

2. Deploy Test WebService ....................................................................................................................... 4

3. Understanding and Modifying the composite ...................................................................................... 5

4. Deploy the Composite ........................................................................................................................... 9

5. Testing and Understanding the functionality ..................................................................................... 12



3 | P a g e

1. Introduction

The default DisconnectedProvisioning composite has been modified to call a webservice and launch a

service request with a new ID. For ease of implementation the WSDL is just dragged into the project and

the composite is made aware of its existence. Also you will observe that the server/host/port values for

the webservice is being provided from a configuration file rather than being hard-coded.

Understand and review the composite to create similar composites for different requirements.

We shall complete the following in this lab.

1. Deploy a test Remedy webservice on Weblogic server

2. Understand and Modify a default disconnected composite; then deploy

3. Change OIM configurations for the new workflow to be picked.

4. Test the workflow for the functionality.



4 | P a g e

2. Deploy Test WebService

We shall deploy the webservice on OIM server for convenience.

1. Start the ADMIN server.

2. Login to the console of ADMIN server as WEBLOGIC.

3. Click on Deployments.

4. Click on Install.

5. Navigate to the following location.

a. /app/dummydata/disconnected_additional

6. Click Next.

7. Browse for and select the RemedyServiceImpl.war.

8. Click Next.

9. Select oim_server1 for deployment.

10. Proceed with the defaults for all the next steps.

11. Once deployment is successful, start OIM Managed Server.

12. Hit the following URL in the browser.

http://identity.oracleads.com:14000/RemedyServiceImpl/RemedyServiceImplService

13. This should show a success message.

14. You may now shutdown the ADMIN server.

http://identity.oracleads.com:14000/RemedyServiceImpl/RemedyServiceImplService



5 | P a g e

3. Understanding and Modifying the composite

1. Launch JDeveloper using the start script in the Startup Scripts folder on desktop.

2. Open the composite from the following location.

a. /app/dummydata/disconnected_additional/DisconnectedProvisioning.zip

Note: You would have to unzip the above zip file. It will create DisconnectedProvisioing

Directory. The JDeveloper application name is DefaultProvisioningComposite.jws. You

would have to open this file in JDeveloper which will open the application.

3. Notice that the flow now has a step to call the Remedy webservice.

4. Double Click to open the InvokeAssignRemedyTicket step.

5. Notice the code makes a call to the remedy webservice.

6. Open the DisconnectedProvisioning_cfgplan.xml.



6 | P a g e

7. Modify the server and port to the following.

a. Host: Identity.oracleads.com

b. Port: 14000

8. Save the file. Did you understand why we modified this file? This composite can take parameters

from any server in future. Rather than hard-coding the server name etc, we have ensure that

those values are read from a file.

9. Compile the composite and deploy to a file.

To deploy the composite, RIght Click on the DisconnectedProvisioing Project In JDeveloper.



7 | P a g e

In the Menu click Deploy->DisconnectedProvisioing

Chose Deploy to SAR Option

Make sure to specify new version as 2.0



8 | P a g e

Once you deploy. It will create sca_DisconnectedProvisioning_rev2.0.jar file. The file will be

created in the deploy directory inside the unzipped DisconnectedProvisioing Directory.



9 | P a g e

4. Deploy the Composite

Follow the steps below to deploy the composite. Also please ensure to start just the below services.

Admin server

SOA server.

Ensure that any other services like OIM are down.

1. In the VM navigate to the folder where you have saved the composite created in the above

chapter.

2. Locate the sca_DisconnectedProvisioning_rev2.0.jar file you created.

3. Ensure that Admin and SOA are up.

4. Hit the Enterprise Manager console in a new browser window.

5. Login as weblogic.

6. Expand the SOA soa-infra default folders.

7. Right click on default and choose SOA Deployment Deploy to this Partition.



10 | P a g e

8. In the Select Archive screen, choose the second option.

a. Archive on the server where Enterprise Manager is running.

9. Provide the path of the jar file. sca_DisconnectedProvisioning_rev2.0.jar you have created in

the previous step. It will be in the deploy directory inside the unzipped DisconnectedProvisioing

Directory.



11 | P a g e

10. Click Next at the top.

When you deploy the file make sure you deploy this version as the Default version.

11. In the confirmation page, just click on Deploy. EM deploys the composite and this activity might

take a while to complete.

12. You will see the new composite now in the default partition.

Tip: Ensure that you preserve the default composite by versioning the new one and acti-

vating it.



12 | P a g e

5. Testing and Understanding the functionality

Let us quickly try to check how this works. Ensure that the below servers are up and running.

1. ADMIN

2. SOA

3. OIM

Follow the below steps for a quick check.

1. Login as ENESS into the OIM Identity Self Service Console.

2. Click on the Catalog link under the Requests menu.

3. Enter the value AppWorx in the free text search box.

4. Click on the Search button.

5. Deselect Entitlements in the Categories leaving just Application Instances checked.

6. Select the AppWorx item from the Catalog Items list and then Click on the Add to Cart button.

7. Click on the Check Out button.

8. Enter the following details in the request form in the frame below.

a. Account Login: ENESS

b. Password: <default password>



13 | P a g e

9. Click on the Ready to Submit button.

10. Then click on the Submit Button.

11. Review Request Summary information in the Request Details and Approval Details tab. Click on

Refresh button to see the approval flow details if not already shown.

12. In the Approval Details tab observe that the request has been assigned to his manager/admin.

13. Open a different browser and log in as the manager/admin and approve the request.

14. At this state, the workflow is designed to call the webservice and lodge a service ticket. Let us

see that using EM.

15. In a different browser window, hit the EM.

16. Login as WEBLOGIC.

17. Expand as shown and click on DisconnectedProvisioing[2.0]



14 | P a g e

18. Click on the highest valued instance number under Instance ID column on the right side

19. In the popup window, expand the following structure under Trace.



15 | P a g e

20. Click on the ManualProvisioningProcess link. You shall be able to see the Audit trail for this in-

stance of the composite.

21. After the InvokeAssignRemedyTicket step, click on Payload.

22. You should be able to see that the requested resource is Appworx, the requestor is ENESS and

the ticket number is also generated by concatenating the OIM request id and the resource

name.



16 | P a g e

This way if there were an original remedy service or a similar one available in the organization, we may

use the disconnected resources to create service requests in the end system by simply calling in the

webservice in the composite.

This is a huge value add as all the required approvals stay in OIM and the provisioning is handled in the

manual fashion without the requirement of connector handling. Having all the approval data helps in

access reviews.

OIG 11G R2 PS1 Field Enablement Training - Oracle Software...

Documents

Transcript of OIG 11G R2 PS1 Field Enablement Training - Oracle Software...