"ls command not found" in linux

I want to set environment variables in my linux environment and hence I updated .bash_profile with two lines at the end of the file.

export JAVA_HOME=/u01/app/Oracle/Middleware/jrockit_160_29_D1.2.0-10/bin/java
export PATH=/u01/app/Oracle/Middleware/jrockit_160_29_D1.2.0-10/bin

After sometime I had rebooted machine for something else and I am seeing a different screen after logging into linux system, an xclock and xterm stuff which was very unusual.

Later I noticed that ls and other bash commands are also not working as non-root user for which I modified the .bash_profile. See the error message given below.

-bash: ls: command not found

So I logged in as root user and modified the non-root user .bash_profile to include the actual PATH as shown below.

export PATH=$PATH:/u01/app/Oracle/Middleware/jrockit_160_29_D1.2.0-10/bin
Actually the PATH variable was earlier set as shown below.
PATH=$PATH:$HOME/bin

I rebooted machine and it works fine!! A silly mistake killed my time :(

Oracle Identity Management 11gR2 webcast

Next big revolution release from Oracle is Oracle Identity Management 11gR2. WebCast is scheduled today IST 10.30 PM.

Register here.
I'll post the updates tomorrow after attending the webcast. Stay tuned!

Exploring OAM 11g

I am getting free time these days to explore on OAM 11g features more.
Few things I have started with are: Creating OAM 11g administrator users by configuring identity store. Logging and auditing stuff.

I am going to write up posts very soon on the above mentioned stuff. Next exploring topic is Custom Authentication plugins.
Stay tuned!!

Oracle Access Manager 11g is certified with Sharepoint 2010 server

One of the much awaited integrations in OAM 11g queue is Sharepoint 2010 server. Well, there is a good news and it is certified now. Check out the certification matrix.
Please contact me for integration documents.

Configure Node Manager for OAM Server 11g

Hi All,

Today I am going to explain the steps for configuring node manager for OAM Server 11g. In fact these steps can be used to configure node manager for any of the other managed servers too.

Before I get into the actual topic, let me explain you what a Node Manager is. Node Manager is a java utility tool that allows you to perform common operation tasks on Managed Servers. In a typical production environment where managed servers are distributed across geographic locations the Managed Servers can be operated from a single place called Node Manager.

Let's see how we can do this.

1. Create a machine where Managed servers are running. If there are 3 managed servers present in a cluster, then 3 machines with respective hostnames has to be created in WebLogic Admin console. Specify the machine name as you like, but should be meaningful :)
2. Specify the Type of Node Manager and machine hostname and listening port that the node manager has to communicate with.
3. Specify a Managed server to associate with this machine.
4. Execute the setDomainEnv.sh script and connect to WebLogic Admin server using WLST java command.
5. Execute nmEnroll script to enroll the node manager for a specific weblogic domain
6. Edit the nodemanager.properties file and set parameter SecureListener=false. This file is located at $MW_HOME/wlserver_10.3/common/nodemanager
7. Start the node manager using script startNodeManager.sh located at $MW_HOME/wlserver_10.3/server/bin. Wait for the message "Plain socket started listener on port 5556". You will see the port that was specified in step 2.
8. 
9. Goto WLS Admin console and check the status of Node Manager in the machine.
10. Now, its time to start managed server using node manager. Goto WLS Admin console and traverse to Environment -> Servers -> oam_server1 -> Control. Goto the end of the page and select the checkbox and click Start.
11. Wait till the status appears RUNNING.

Planning to install Oracle Identity Management 11.1.1.6?

I have written few posts here on planning the installation of Oracle Identity Management 11.1.1.6 for various scenarios. The post also covers the installation steps with detailed screenshots.

Hope this helps!

Please get back to me in case of any queries/suggestions.

Updates on OES 11g with Java SM in Tomcat Server

Earlier I had written my comments about OES 11g with java SM in Tomcat container in this post. I'd like to redefine this with some changes.

First of all, OES 11.1.1.5.0 is not supported on Tomcat Server 6.x. However if your client have no choice other than using Tomcat and there is an application to be protected against OES 11g, then here is what you can do:

Assuming that OES server and client + Java SM is installed and up and running.

• Goto Tomcat install directory, edit the setclasspath.sh or setclasspath.bat and update the Tomcat Classpath with oes-client.jar as export CLASSPATH=$CLASSPATH:$OES_CLIENT_HOME/modules/oracle.oes.sm_11.1.1/oes-client.jar.
• Specify the Java SM jps-config.xml in the Java OPTIONS (in the same file setclasspath.sh or setclasspath.bat) as export JAVA_OPTS= $JAVA_OPTS -Doracle.security.jps.config=$OES_CLIENT_HOME/oes_sm_instances//config/jps-config.xml.

Test the Tomcat application with some authorization policies and it works!

Exceptions: In my case, our enterprise application was using xml parser jars which was conflicting with xmlparserv2.jar located under $OES_CLIENT_HOME/modules/...