Chuyển đến nội dung chính

Uninstalling an OIM Connector

Version: Oracle Identity Manager 11.1.2.3.0
Step 1: Modify "ConnectorUninstall.properties" located in the "/home/oracle/Oracle/Middleware/Oracle_IDM1/server/bin" directory.

Step 2: Here is a brief description of each parameter defined in the file:
DatabaseURL: location of the Oracle Database
DbUserName: Name of the OIM schema
Location: Place where you want the log files of this process to be.
ConnectorName: Name of the connector (Same as in the OIM console: Advanced-> Manage Connector -> search. Use the Connector Name field.)

Step 3: Run the" uninstallConnector.sh" script located in "/home/oracle/Oracle/Middleware/Oracle_IDM1/server/bin" directory.
[Enter the DB Password :] <OIM schema password>
[Enter OIM Administrator Name :] xelsysadm
[Enter the OIM Administrator Password :]
[Enter OIM Server t3 URL [Ex. t3://localhost:7001/ ]:] t3://localhost:14000

Step 4: Execute the "DeleteJars.sh" to remove  the jars associated with connector. Refer to the OIMHOME_JARS schema to look for jars associated with the connector you are deleting. Active Directory has no jars. If you ever run this script on a connector with jars files, you will be prompted the following information
Xellerate Admin user: The OIM administrator. e.g. xelsysadm
Admin Password: The OIM administrator password.
Server URL: The OIM server.  e.g. t3://localhost:14000
Context Factory: weblogic.jndi.WLInitialContextFactory
Jar Type: 1. Java Tasks, 2. ScheduleTask, 3. Thrid Party, 4. ICFBundle (Look at OIMHOME_JARS for type)
Name of the jar to be deleted from DB: Look at OIMHOME_JARS  for name.

Step 5: Execute the "DeleteResourceBundle.sh" to remove the resources associated with a connector. This script is located in "<OIM_HOME>/server/bin" directory. Refer to the RESOURCES schema for the name of the resource bundle. Each resource bundle name has a prefix of the connector name to which it is associated with. When running the script, you will be prompted the following information:
Xellerate admin username: The OIM administrator name. e.g. xelsysadm
Admin: The OIM administrator password.
ServerURL: OIM server URL. e.g. t3://localhost:14000
Context Factory: weblogic.jndi.WLInitialContextFactory
Resource bundle type: 2 [Connector Resource]
Name of the resource bundle file: Refer to RESOURCES table for name. e.g. ActiveDirectoryIdC.properties

Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

Approval specific web services in Oracle IDM

Source: https://abhirockzz.wordpress.com Oracle IDM integrates with and leverages the SOA suite for approval related features (SOA is quite rich to be honest and is utilized as the back bone for Web Services connector as well). SOA is not just for namesake – SOA suite does in fact rely on the concept of loosely coupled and independent services. The approval engine makes use of three such web services Request web service : this is deployed on the OIM server Request Callback web service : this is deployed on SOA server Provisioning Callback web service : this too is deployed on OIM and used in context of approvals related to  Disconnected application instances But how/when are these (SOA) services leveraged ? Consider an example of a basic approval process OIM approval engine calls a SOA composite (from within an approval policy) in response to evaluation of a self service request.  The internals of this call are out of scope of this post (maybe some other time!) Operati
1 nhận xét
Đọc thêm

Allow Duplicate Emails

Version: Oracle Identity Manager 11.1.2.3.0 Step 1:  Login to Oracle Identity System Administration Step 2: On the navigation menu, select Configuration Properties under System Configuration. Step 3: Create the following System Property. Step 4: Verify using duplicate emails.
Đăng nhận xét
Đọc thêm

How to OIM cache work

Source: https://abhirockzz.wordpress.com Oracle IDM uses  OSCache  from the OpenSymphony project for  in memory caching  of objects in order to avoid repetitive calls to database and improve performance (of course !). In case you are not familiar with caching in general, I am pretty sure that as someone working on OIM, you would have executed  PurgeCache.sh  at some point in your career – so there it is ! If you have ever purged OIM’s cache, you have indirectly used OSCache.. yay ! How is it implemented ? OIM uses a facade/wrapper over the core OSCache caching APIs XLCacheProvider  is essentially used as the generic interface which is implemented by a class called  OSCacheProvider  (this is OIM specific). You should be able to see an entry of this class in  oim-config.xml  (caching categories config section). It’s FQDN is  oracle.iam.platform.utils.cache.OSCacheProvider This class implements the contract put forth in the XLCacheProvider interface and leverages internal OSCache A
Đăng nhận xét
Đọc thêm