The more I write on this blog, the more difficult it gets to find information. So here is a kind of map of the most useful articles by topic. That should help you navigate within the content.
I’m really excited to announce a new area for ICN!
Ok, maybe I’m overreacting but this is really, I hope, the beginning of something great.
My colleague Kerry Langford and I, have been working for months internally on the idea of building a global, centralized, IBM managed, open source repository for ICN Plug-ins and get me approved to commit code there. The idea is a public repository of Plug-ins, a bit like Jenkins does, where people can choose what they need and just download production-ready releases, but also give feedback, open issues, enhancement requests or even contribute.
I really wanted to thank Kerry in this post because he has been doing an amazing job internally to push open source and build a better FileNet/ICN community, which is IMHO one of the weak spot of FileNet and ICN, but probably because I’m used to open source, community driven projects 🙂 Nothing would have been possible without him so Thank you Kerry for making this possible!
So, after a lot of discussion with the ICN Team (they own the GitHub repository), we finally did it. It’s live here. Hosted by IBM, one unique repository to rule them all!
I’m pleased to announce that the Jenkins Plug-in to reload ICN plug-in is now available as an official Jenkins plugin. You can now install it from the Jenkins Update center within your Jenkins web client.
I hope we can all work together to make it support more authentication methods and improve it.
There are situations where you can get stuck out of the ICN Admin desktop. For instance because you change the uid mapping for the LDAP and the ID you used is not valid anymore, you should now use the email address or another field. If you forgot to add the new ID before you made the change, you’ll have to rollback and restart ICN which is not always possible. There is one way to add/remove admins without restarting.
You can update directly the database, and wait 10 minutes (the default refresh time) to get your changes pick up. The entry we are interested in is settings.navigator.default in the table NEXUS.CONFIGURATION.
This field contains a json object with plenty of information. You can check it by doing:
select ATTRIBUTES from NEXUS.CONFIGURATION where ID='settings.navigator.default'
Then when you are ready, you can add a new admin by using the following command:
UPDATE NEXUS.CONFIGURATION SET ATTRIBUTES = REPLACE(ATTRIBUTES, 'adminUsers=', 'adminUsers=NewAdmin,') WHERE ID='settings.navigator.default'
Wait for at top 10 minutes and you should be able to log in again. Then you should clean up old admins which are not needed anymore.
Here is how to set aliases for the Windows command window and Clink if you’re using Clink.
First, create a cmd file somewhere to create your aliases using the doskey command. Mine looks like this:
doskey np=notepad++.exe $*
doskey ls=dir $*
doskey ns=nslookup $*
doskey ip=ipconfig $*
doskey hosts=notepad++.exe C:\Windows\System32\drivers\etc\hosts
doskey aliases=notepad++.exe C:\Applis\clink\aliases.cmd
You can also use all available cmd commands and variables to customize your shell, like title, color, set PROMPT, …
Then, open your registry and go to the following key:
and add add a string value named AutoRun and valued with the absolute path of your aliases file.
That’s it, from now on, all your aliases will be loaded every time you start cmd or clink.
I’ve been focusing a lot lately on how to install P8 with CPIT. Mostly because this is easier, faster, and usually more convenient, but it has inconveniences as well. Installing all components separatly has a few benefits and I thought it was time to write how to do that:
- Install different versions of the components
- Install Fix Packs during install
- Use different technologies
- Split components on different servers
- Use pre-installed components (LDAP, DB, …)
- Optimize install size by deleting binaries after each install
- And for curious people, understand better what’s going on 🙂
This will be a long post, but I’ll try to split this step by step and explain precisely what is going on. At the end of this post, I will give the full script you can run to install a full platform. Unlike the CPIT installer, I’ve tried to keep everything in one script to ease distribution, installation and customization. That’s why you will see a lot of HERE-doc commands to create files on-the-go. At this moment I’m using only one dependency, which is a file from the CPIT installer: cpt-actions.jar. This is the java tool allowing us to create the default domain and object store. This is quite basic to implement using the Java API so I hope to write soon how to rewrite this tool so we can get rid of all dependency on CPIT.
Here is how to upgrade P8 FileNet Platform 5.2.1 to 5.2.1 FP5 silently. This upgrades both the server and the client.
You need FileNet 5.2.1 to upgrade to 5.2.1 FP 5. Here is a way to install FileNet 5.2.1.
You can execute this in the same directory you copied 126.96.36.199-P8CPE-LINUX-FP005.tar.gz and 188.8.131.52-P8CPE-CLIENT-LINUX-FP005.tar.gz.
Here is a way to silently upgrade from IBM Content Navigator 2.0.3.x to 2.0.3 FP8. You can use this right after using the CPIT installer to be up-to-date with your ICN version. You need at least ICN 184.108.40.206 to upgrade to ICN 2.0.3 FP8.
In the same folder you copied 2.0.3-ICN-FP008-LINUX.tar, execute these commands: