Shared Library Reference, where is my OK button?

Studying is fun not only because it is an excellent time-killing tool but also it gives us an exploration-like experience. Often, its payback can be very rewarding as well.
In contrast to most believes, struggling while studying can be fun as well when we manage to conquer its challenges.

Today, I study WJ402 - WebSphere Extreme Scale v7 which is a self-paced e-learning course.
I am struggling in a lab where I get exceptions. I tried to debug the application myself to see what went wrong.

Unfortunately, I have to port the application to a standalone WebSphere Application Server profile in order to easily use it with Rational Application Developer (RAD) as a local WebSphere Test Environment instance. Things works fine until I plan to associate a set of jar files to the enterprise application using shared library.

Hey, how can I commit my shared library reference association?
It should be like this.

A normal shared-library page in the admin console

 Unfortunately, it is not. The OK button disappears. Just like this.

A strange behavior of a shared library page in WTE/RAD

I struggled for too long. Going back and forth comparing it with existing WAS ND shared library definition.  Checked upper-case, smaller-case drive letter. Things are identical. I tried many things on WebSphere-side. Use wsadmin instead of admin console. Result is not very satisfactory.

I then realized it may not be a WebSphere problem. Rather it can be related to how RAD treats WebSphere as a development environment. I then searched the support web site and found this interesting link.
http://www-01.ibm.com/support/docview.wss?uid=swg21383952

In conclusion, we just need to allow RAD to publish the whole application configuration artifacts to WebSphere by unchecking "Minimize application files copied to the server" check box (highlighted in yellow) as shown below.

Solution to the problem

Use "add and remove projects" function to uninstall and reinstall the application.
Then, the OK button reappears again to allow us to associate an application with the shared libary.

I can continue to struggle debugging now.