That's nice to see how others do it!
How I do it, is a bit different. And I think this could be an enhancement for the ICN product in order to have after the deployment of ICN in WAS a working CMOD connection... not like today.
Every time I need to tweak WAS in order to make it work. Every single time... with or without having CMOD installed in the default directory.
What I do is the following:
After deployment of ICN in WAS, I add the following settings:
- From WAS Admin Console: Servers -> Server Type -> WebSphere application servers
- Then click on your server (eg: server1)
- Then Server Infrastructure -> Java and Process Management -> Process Definition
- Then Additional Properties -> Java Virtual Environment
- Finally in the "Generic JVM arguments" I add the following line:
- Djava.library.path=/<custom Path or original path>/ibm/ondemand/V10.1/www
Now, the next part is ONLY if you install CMOD as a user OR in a non standard path.
- From WAS Admin Console: Servers -> Server Type -> WebSphere application servers
- Then click on your server (eg: server1)
- Then Server Infrastructure -> Java and Process Management -> Process Definition
- Then Additional Properties -> Environment Entries
- Now you need to add 2 new entries
Name=ARS_INSTALL_SERVER_Vxxx_DIR
Value=<CMOD Install Path> (ie: /home/archive/ibm/ondemand/V10.1)
and
Name=ARS_INSTALL_ODWEK_Vxxx_DIR
Value=<CMOD Install Path> (ie: /home/archive/ibm/ondemand/V10.1)
Where Vxxx is
V101 for CMOD V10.1
V95 for CMOD V9.5
V90 for CMOD V9.0
So if I have CMOD V10.1 it should look something like:
Name=ARS_INSTALL_SERVER_V101_DIR
Value=/home/archive/ibm/ondemand/V10.1
Name=ARS_INSTALL_ODWEK_V101_DIR
Value=/home/archive/ibm/ondemand/V10.1
Save everything is the Admin WAS Console.
Then finally restart WAS.
But now I see thanks to you nishen, that I can replace the last step with the ARS_INSTALL_*_V*_DIR with your explanation:
we had to add the odwek_install_dir parameter in the ICN Ondemand Configuration page as a custom property
Thank you !!! :-D