OIM UDFs: Data Components associated

Entity	Page	Data Component	View Object
User	Create User	Data Component - Catalog	userVO
	Modify User	Data Component - Catalog	userVO
	Search Users	Data Component - Manage Users	UserVO1
	View User Details	Data Component - Manage Users	UserVO1
	My Information	Data Component - My Information	UserVO1
	New User Registration	Data Component - User Registration	UserVO1
Role	Create Role	Data Component - Role	RoleDetailsVO
	Modify Role	Data Component - Role	RoleDetailsVO
	Search Roles	Data Component - Role	RoleVO1
Organization	Create Organization	Data Component - Organization	EditOrgVO
	Modify Organization	Data Component - Organization	EditOrgVO
	Search Organizations	Data Component - Organization	OrganizationVO

OIM query to find entitlements associated with application instance

SELECT ent.ent_code AS "Entitlement Name", ent.ent_display_name AS "Entitlement Display Name" from ent_list ent

INNER JOIN app_instance app_instance ON
app_instance.object_key = ent.obj_key AND
app_instance.itresource_key = ent.svr_key AND
app_instance.app_instance_name = 'ActiveDirectory';

Java Embedding Activity: Use collection object like HashMap

Ensure that you have the following line in the .bpel file before the java embedding activity:

<bpelx:exec import="java.util.HashMap"/>

AccountNotFoundException: When manual provisioning is customized to auto-complete

<Error> <oracle.iam.provisioning.ws> <BEA-000000> <Exception occured during manual provisioning of accountID = 1972 operation = Provision

oracle.iam.provisioning.exception.AccountNotFoundException: An error occurred in oracle.iam.provisioning.util.ProvisioningUtil/getUserIdFromAccountId(String accountId) as account with key 1972 does not exist. 

Solution:

Add a wait activity in BPEL process (composite) before the response is returned from SOA. Set the wait time to 5 seconds.

Create wlfullclient.jar

wlfullclient.jar is required for multiple operations in OIM. The following are the steps to create the same in your OIM environment:

1. Login into OIM box.

2. Navigate to the following location: <MW_HOME>/wlserver_10.3/server/lib

       /app/Middleware/wlserver_10.3/server/lib

3. Execute the following command:

       java -jar /app/Middleware/modules/com.bea.core.jarbuilder_1.7.0.0.jar

    Depending on your environment, you might have a different version of com.bea.core.jarbuilder jar

4. You will receive the following confirmation message post the jar creation:

       Created new jar file: /app/Middleware/wlserver_10.3/server/lib/wlfullclient.jar

ORABPEL-02183: JTA transaction is not in active state.

Set the following two values. The values must be in accordance with your environment, given here are just sample values.

1. syncMaxWaitTime

• Login into EM console.
• Expand SOA and right click on "soa-infra" and select: SOA Administration -> BPEL Properties
• Click on "More BPEL Configuration Properties" link
• Locate syncMaxWaitTime and change it.

2. JTA transaction time out

• Log into Oracle WebLogic Administration Console.
• Click Services -> JTA.
• Change the value of Timeout Seconds (the default is 30) to 1200.
• Click Save.
• Restart WebLogic Server.

Start node manager

1. Navigate to <WL_HOME>/server/bin e.g.: /app/oracle/Middleware/wlserver_10_3/server/bin
2. ./startNodeManager.sh