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

Oracle IDM Auditing

Source: https://abhirockzz.wordpress.com Reporting  is a vital functionality in any product which deals with sensitive information. Same applies to Identity & Access Management tools. Oracle IDM’s Auditing module acts as a foundation for its OOTB Reporting capabilities. Let’s take a quick look at  Auditing engine  and how it facilitates the Reporting functionality within OIM The use case presented here is simple –  change to a user record in OIM. What are the sequence of events which get triggered from an Audit perspective? This is best explained by a diagram. I came up with the  figure below  in an attempt to better articulate the process. Although the diagram is self explanatory, a theoretical translation of the same is not going to harm us!  The updated/created user record gets pushed into the  USR  table (stores the user information) – Its a normal process by which the information gets recorded in th...
Đăng nhận xét
Đọc thêm