6-70 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager
2.
Create Oracle Identity Manager metadata MDS backup. See MDS Utilities and User Modifiable Metadata Files in the Oracle Fusion Middleware Developers Guide
for Oracle Identity Manager for information about the utilities that you can use to modify Oracle Identity Manager metadata.
3.
Ensure that there are no operations on Oracle Identity Manager until the Uninstall utility is completed. Oracle Identity Manager and SOA servers should be up and
running.
4.
Ensure that all the JMS messages are processed.
6.9.4.3.2 Uninstall To run the ConnectorUninstall script for uninstalling the
connector: 1.
Set values in the properties file used by the script.
The ConnectorUninstall.properties file is a viable in OIM_HOMEserverbin. This file contains information that is used by the script for deleting connector objects.
Open the properties file in a text editor, and then set values for the following properties:
■
DatabaseURL: Enter the JDBC URL for the Oracle Identity Manager database in the following format:
jdbc:oracle:thin:HOST_NAME:DATABASE_PORT:DATABASE_NAMEORACLE_SID For example: jdbc:oracle:thin:localhost:1521:orcl
■
DBUserName: Enter the user name of an Oracle Identity Manager database.
■
DBType: Specifies the type of database.
■
LogLevel: Enter one of the following as the log level: DEBUG, WARN, INFO, or ERROR.
■
Location: Enter the directory location where you want to have all the log files generated by the Uninstall utility.
If the Uninstall utility completes successfully, then the ConnectorUninstall.log file, along with ResourceObject.log files are generated.
If the Uninstall utility fails, then the ConnectorUninstall.log file along with the ConnectorUninstall_Error.log file are generated.
For example, if the Uninstall utility of ActiveDirectory Connector succeeds, then the following logs will be generated:
– ConnectorUninstall.log
– AD User.log
Note: If you provide ConnectorName and Release along with
ObjectType and ObjectValues, then deletion of ObjectValues will be performed by the utility and the Connector information will be
skipped.
Note: If the uninstall utility fails with errors, then check the
ConnectorUninstall.log and ConnectorUninstall_Error.log and take suitable action. Then, run the uninstall utility again.
Managing Connector Lifecycle 6-71
– AD Group.log
– AD Oraganization Unit.log
– AD User Trusted.log
If the Uninstall utility of ActiveDirectory Connector Fails, then the following logs will be generated:
– ConnectorUninstall.log
– ConnectorUninstall_Error.log
■
ConnectorName: The value that you set for this property depends on your requirement. If you want to delete a specific connector, then enter the name of
the connector. The name that you enter must be the same as the name shown in the search results displayed through the Manage Connector feature. For
example, enter Active Directory if you want to delete the Microsoft Active Directory connector.
■
Release: The value that you set for this property depends on your requirement. If you want to delete a specific connector, then enter the release
number of the connector. The release number that you enter must be the same as the release number shown in the search results displayed through the
Manage Connector feature. For example, enter 9.1.0.1 if you want to delete the Microsoft Active Directory 9.1.0.1 connector.
■
ObjectType: The value that you set for this property depends on your requirement:
– If you want to uninstall a connector, then ensure that the ObjectType
property is not assigned a value.
– If you want to delete adapters, lookup definitions, resource objects, or
scheduled task, then enter Adapter, Lookup, ResourceObject, or ScheduledTask respectively.
Example: ResourceObject
■
ObjectValues: Enter a semicolon-separated list of object values. Example: AD User; AD Group
2.
In a command window, change to the OIM_HOMEserverbin directory and then run the script, sh uninstallConnector.sh or bat file.
While the script runs, logs will be generated at the location provided. After you run the utility, you will be prompted to enter following information:
a.
Oracle Identity Manager Database Password
b.
Oracle Identity Manager Administrator Name
c.
Oracle Identity Manager Administrator Password
d.
Oracle Identity Manager Server t3 URL
e.
Confirmation for the deletion of the connectorobjects
6.9.4.3.3 Postuninstall After uninstalling the connector, you must perform the
following steps:
1.
Use DeleteJars utility for deleting the jars associated with the connector from Oracle Identity Manager database.
6-72 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager
2.
Use DeleteResourceBundles utility for deleting all resources that are associated with the connector from Oracle Identity Manager database.
3.
Revisit the log, look for the following information and perform the steps mentioned for each of it:
a.
The list of request templates: Deletemodify these templates as the resource objects, which used these templates are now deleted.
b.
The list of attestation processes: Deletemodify these attestation process as the resource objects, which used these attestation processes are now deleted.
c.
Modify request and approval policies manually to delete the resource object names that are cleaned by the uninstall utility.
d.
As the part of connector uninstall, the approval processes Approval workflowSOA composites are not deleted. If the approval processes are
generic, then you need to modify them if they have association with the deleted resource objects.
4.
Recalculate statistics and re-create indexes and other database objects that are removed by the connector uninstall utility. For more information, see
Performance Tuning and Best Practices.
5.
Restart Oracle Identity Manager, or use PurgeCache utility to purge the Cache. See
Purging the Cache on page 26-3 for information about purging the cache.
Part II
Part II
System Management
This part describes the system management tasks in Oracle Identity Manager. This part contains the following chapters:
■
Chapter 7, Starting and Stopping Servers
■
Chapter 8, Enabling System Logging
■
Chapter 11, Integrating with Other Oracle Components
■
Chapter 12, Handling Lifecycle Management Changes
7
Starting and Stopping Servers 7-1
7
Starting and Stopping Servers
Most Oracle Identity Manager feature configurations, such as password policy create and update, need the restart of the server for the changes to take effect. This chapter
provide procedures to startstop Oracle WebLogic Servers.
You can perform all start and stop operations for managed WebLogic Servers either from command prompt or from Oracle WebLogic Server Administration Console or
Oracle Enterprise Manager Fusion Middleware Control.
The following sections are given only for reference purpose. See Oracle WebLogic Server Administrator Guide for detailed information.
■
Configuring the Node Manager
■
Starting the Node Manager
■
Starting or Stopping WebLogic Administration Server
■
Starting or Stopping WebLogic Managed Servers You can perform all start and stop operations either from command prompt or from
Oracle WebLogic Server Administration Console.
7.1 Configuring the Node Manager
After installing and configuring Oracle Identity Manager and SOA servers, you must configure node manager for using it with WebLogic Administration Console or Oracle
Enterprise Manager Fusion Middleware Control. This configuration is to be done only once.
To configure node manager, you must set StartScriptEnabled=true in the nodemanager.properties file. To do so, run following script:
For UNIX:
Note: Node Manager must be running in order to use the Oracle
WebLogic Server Administration Console or Oracle Enterprise Manager Fusion Middleware Control for controlling startstop
Oracle Identity Manager WebLogic managed servers and SOA WebLogic managed servers.
Note: Node Manager must be running before you can start and stop
administration server, managed server, and SOA server through Oracle WebLogic Server Administration Console.
7-2 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager
MIDDLEWARE_HOMEoracle_commoncommonbinsetNMProps.sh For Microsoft Windows:
MIDDLEWARE_HOME\oracle_common\common\bin\setNMProps.cmd
7.2 Starting the Node Manager
To start the Node Manager:
1.
Navigate to WL_HOMEserverbin.
2.
At the command prompt, enter: .startNodeManager
7.3 Starting or Stopping WebLogic Administration Server
To start or stop the WebLogic Administration Server:
1.
Navigate to DOMAIN_HOMEbin.
2.
To start the server, enter the following: For UNIX:
.startWebLogic.sh For Microsoft Windows:
startWebLogic.cmd To stop the server, enter the following:
For UNIX: .stopWebLogic.sh
For Microsoft Windows: stopWebLogic.cmd
7.4 Starting or Stopping WebLogic Managed Servers
This section contains the following topics:
■
Starting or Stopping the Managed Servers By Using Command Prompt
■
Starting or Stopping the Managed Server By Using Oracle Enterprise Manager Fusion Middleware Control
■
Starting or Stopping Servers By Using Oracle WebLogic Server Administration Console
Note:
■
For Linux Install you have only .startWebLogic.sh and you do not have startWebLogic.cmd in the bin folder.
■
For Microsoft Windows Install we have both .startWebLogic.sh and startWebLogic.cmd in the bin folder.
Starting and Stopping Servers 7-3
7.4.1 Starting or Stopping the Managed Servers By Using Command Prompt
To start or stop the managed servers using command prompt:
1. Navigate to the DOMAIN_HOMEbin directory.
2. To start the server, enter the following at the command prompt:
For UNIX: .startManagedWebLogic.sh MANAGED_SERVER_NAME
ADMIN_SERVER_URL For example:
startManagedWebLogic.sh oim_server1 http:mywlsadminhost.mycompany.com:7001
startManagedWebLogic.sh soa_server1 http:mywlsadminhost.mycompany.com:7001
For Microsoft Windows:
startManagedWebLogic.cmd MANAGED_SERVER_NAME ADMIN_SERVER_URL
To stop the server, enter the following at the command prompt: For UNIX:
.stopManagedWebLogic.sh MANAGED_SERVER_NAME ADMIN_SERVER_URL
For Microsoft Windows:
stopManagedWebLogic.cmd MANAGED_SERVER_NAME ADMIN_SERVER_URL For example:
stopManagedWebLogic.cmd oim_server1 http:mywlsadminhost.mycompany.com:7001
stopManagedWebLogic.cmd soa_server1 http:mywlsadminhost.mycompany.com:7001
7.4.2 Starting or Stopping the Managed Server By Using Oracle Enterprise Manager Fusion Middleware Control
In order to use the Oracle Enterprise Manager Fusion Middleware Control to control managed servers, Node Manager must be running on the computer.
To start or stop the managed server using Oracle Enterprise Manager Fusion Middleware Control:
1.
Log in to the Oracle Enterprise Manager Fusion Middleware Control.
2. Navigate to Weblogic Domain, Domain Name, SERVER_NAME.
3. Right click, and navigate to Control.
4. Click Start Up to start the server.
Click Shutdown to stop the server.
7.4.3 Starting or Stopping Servers By Using Oracle WebLogic Server Administration Console
To start or stop servers by using Oracle WebLogic Administration Console:
