IAM

Thursday, 27 July 2017

Steps to repair oraInventory of Oracle installation

Identify Oracle Inventory central location
Run the installer as below

${ORACLE_HOME}/oui/bin/runInstaller -attachHome -invPtrLoc /prj/oracleim/oim/Oracle_IDM1/oraInst.loc ORACLE_HOME="<ORACLE_HOME>" ORACLE_HOME_NAME="<ORACLE_HOME_NAME>" CLUSTER_NODES="{}"

e.g.,

./runInstaller -attachHome -invPtrLoc /prj/oracleim/oim/Oracle_IDM1/oraInst.loc ORACLE_HOME="/prj/oracleim/oim/Oracle_IDM1" ORACLE_HOME_NAME="Oracle_Home_Name" CLUSTER_NODES="{}"

An alternative to fix orainventory is to run attachhome command from below location

$ORACLE_HOME/oui/bin/attachHome.sh

OIM Server does not start when first node of DB RAC is down

JPS configuration by default points to first node of the DB and hence OIM does not start when first node is down. Update following files with RAC JDBC url and restart servers -

<WLS_DOMAIN>/config/fmwconfig

./jps-config-jse.xml
./jps-config.xml
./jps-config-migration.xml

How to enable signature login in OIM 11g

Signature login in OIM 11g does not work because of the conflict of certificates (OIM and Remote Manager) in default-keystore. Follow steps below to re-generate remote manager certificate and update default-keystore. Post these updates, signature login will work as expected.

Re-generate the remote manager certificate

------------------------------------------

NOTE: Please use the passwords for keystore and key entry that you entered during Remote manager installation.

1. Backup the existing default-keystore.jks, xlserver.cert and xell.csr in $REMOTE_MANAGER/config directory

2. Using a shell, navigate to the $REMOTE_MANAGER/config directory

3. Generate a new keystore with a private key entry $JAVA_HOME/bin/keytool -genkey -alias xell -keyalg RSA -keysize 1024 -dname "CN=<COMMON_NAME>, OU=<OU>, O=<Org>, L=City, ST=NY, C=US" -validity 3650 -keypass <keypass> -keystore default-keystore.jks -storepass <storepass> -storetype jks -provider sun.security.provider.Sun

4. Generate a certificate request

"C:\Program Files\Java\jdk1.6.0_43\bin\keytool.exe" -certreq -alias xell -file xell.csr -keypass <keypass> -keystore default-keystore.jks -storepass <storepass> -storetype jks -provider sun.security.provider.Sun

5. Export and import the certificate as a trusted entry "C:\Program Files\Java\jdk1.6.0_43\bin\keytool.exe" -export -alias xell -file xlremote.cert -keypass <keypass> -keystore default-keystore.jks -storepass <storepass> -storetype jks -provider sun.security.provider.Sun

"C:\Program Files\Java\jdk1.6.0_43\bin\keytool.exe" -import -trustcacerts -alias xeltrusted -noprompt -keystore default-keystore.jks -file xlremote.cert -storepass <storepass>

Re-establish the trust relation between OIM server and Remote Manager

---------------------------------------------------------------------

1. In the OIM server default-keystore.jks, located at $DOMAIN_HOME/config/fmwconfig/default-keystore.jks, remove the existing key entry for the remote manager. In your case, you need to remove the "rm_trusted_cert" alias from the OIM server's default-keystore.jks

$JAVA_HOME/bin/keytool -delete alias rm_trusted_cert -keystore default-keystore.jks -storepass <SERVER-KEYSTORE-PASSWORD>

2. Re-import the remote manager certificate, exported earlier in the file xlremote.cert in the server keystore

keytool -import -trustcacerts -alias rm_trusted_cert -noprompt -keystore default-keystore.jks -file <ABSOLUTE_PATH_OF_CERT> -storepass <storepass>

Validation

----------

1. Test OIM server signature login works properly

2. Test that OIM server <-> Remote manager communication and functionality works properly

Monday, 31 October 2011

How to start DB, OID and ODSM

This post describes the procedure to start DB, OID and ODSM.

To start DB, follow the steps in the order given below:

1. Set the environment variables (if they are not already set) by executing the below commands:
a. export ORACLE_HOME = /app/oracle/product/11.2.0/dbhome_1. Path of the base directory of database
b. export PATH = /app/oracle/product/11.2.0/dbhome_1/bin: $PATH. The bin directory of ORACLE_HOME
c. export LD_LIBRARY_PATH=/app/oracle/product/11.2.0/dbhome_1/lib. The lib folder of ORACLE_HOME
d. export ORACLE_SID=orcl. Database SID
PS: All these variables can be permanently set in the session by writing these commands to ".profile" file of the unix user.
2. Start the database listener by executing the below command:
a. lsnrctl start

3. After starting the listener, login to idle instance of database by executing:

a. sqlplus / as sysdba

4. Start the database instance by executing
a. startup

You have successfully started the database now.

The next step is to start OID. In 11g, OID has ODSM which is GUI similar to "Oracle Directory Manager" in 10g version. You can just start OID process using OPMN and start working with out ODSM as ODSM is only a GUI interface provided by Oracle.

Steps to Start OID using OPMN

1. Set the environment variables required to start OID by executing the below commands:

a. export ORACLE_HOME=/home/oracle/Oracle/Middleware/Oracle_IDM1. Path of the base directory of Oracle Internet Directory

b. export ORACLE_INSTANCE=/home/oracle/Oracle/Middleware/asinst_1. Path of the instance directory created while installation
c. export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$ORACLE_INSTANCE/bin:$PATH.
d. export TNS_ADMIN=$ORACLE_INSTANCE/config
PS: Make sure the first directory of PATH variable is always bin directory of ORACLE_HOME as defined above. You might get errors while executing ldap commands if this is not maintained.
2. Start OID by executing
a. opmnctl startall
You can check the status of OID by executing opmnctl status to verify if the status is Alive i.e., if OID is started.

You have started OID successfully. You can start working with OID now.

(Optional) The next step is to start ODSM i.e., Weblogic Managed Server. To start with you have to start Weblogic Admin Server.

Steps to start Web logic Admin and Managed Server

1. To start Weblogic Admin Server, Navigate to <WLS_DOMAIN>/bin directory and execute:

a. ./startWeblogic

2. To start Managed Server, Navigate to <WLS_DOMAIN>/bin directory and execute:

a. ./startManagedWeblogic <Managed_Server_Name> <Admin_Server_URL>

PS: If you get an error "Unable to get lock on "WLS_<>.DAT" file while starting Admin or Managed Server, Delete the ".DAT" files from the "<WLS_DOMAIN>/servers/<Admin or Managed>/data/store/default" and "<WLS_DOMAIN>/servers/<Admin or Managed>/data/store/diagnostics" directories and try restarting the server.

Sunday, 30 October 2011

Configuration of OID

After installation you should configure OID. Follow the steps given below:
1. Browse to <Oracle_Home>/bin directory and execute config.sh

2. Select “Create New Domain” and enter the credentials and name of the domain to be created. Click Next to continue

3. Specify Weblogic sever directory, Oracle Instance location and Instance Name. Click Next to continue

4. Select the components to be configured

5. Select appropriate option to configure ports of OID

6. Select Create Schema and provide the connection details of Database.

PS: If you have already created schema using RCU, select "Use Existing Schema"

7. Enter the password of the schema owner. Click Next to continue

8. Specify OID realm, OID admin password and click Next to continue

9. Verify the installation summary. Click configure

10. Configuration progress

11. Installation complete. Click Finish to exit.

You have successfully installed and configured OID. Click here to see how to start DB, OID and ODSM

OID 11.1.1.5.0 Patch Installation

1. Download the patch from the metalink site.
2. Browse to Disk1 of patch installer directory, execute runInstaller. Click Next to continue

3. Specify the Middleware home and Oracle home directory of previous installation. Click Next to continue

4. Verify the details and click on Install

5. Installation Complete. Click finish to exit.

OID 11.1.1.3.0 Installation

In OID installation, you can create the database schema either by using RCU or by opting for create schema while installation. We are going to install OID without using RCU here.We will install 11.1.1.3.0 version first, then update the software to 11.1.1.5.0 and configure OID.

1. Download the software from the link provided in the first post.
2. Browse to Disk1 of the installer directory and execute "runInstaller". Click next to continue the installation