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 the new and up-to-date version of the Install FileNet P8 series, replacing the old one (5.2). What is mainly new, compare to CPIT 5.2:
- Tivoli Directory Server 6.3 FP24
- GSKit 18.104.22.168
- FileNet Content Platform Engine 5.2.1
- WebSphere Application Server 8.5.5
- IBM Content Navigator 2.0.3
- Installation Manager 1.6.2
- There are now two WAS nodes, one for FileNet and one for ICN
- IBM DB2 9.7 Fix Pack 8/li>
Last version was Install FileNet P8. This post is intended to help you to use the CPIT installer to install a fully functional FileNet P8 on a single server. We will see what you need to run and how to proceed. As nice as it sounds, errors are frequent so we will try to isolate all errors and see how to fix them.
This is weird, but most of the errors from the CPIT 5.1 are still present in the version 5.2.1… The only one actually fixed is the creation of the setDB2port which is not needed anymore.
Here is a quick summary of how to upgrade to FileNet 5.2.1. As usual, before starting, snapshot/backup your server. Here are the main steps for a single server platform installed with the CPIT installer and where the application server has not been upgraded. If it has been or you platform is different, check the knowledge center but procedure should be mostly the same and you can use this to help you.
When programming with P8, one recurrent task is counting how many results a query has.
There are a few options to do this, none of them being
count(*) and I’ll explain why. The purpose of this post is to expose them and compare their execution time and limitations with benchmarks. We will also see how to optimize each of them separately. Hopefully, after reading this post, you will be able to choose which one best fits your needs. Before introducing all options IBM made available to us, a little introduction important to understand this post and its benchmarks.
When counting, it may be strange, but it is a lot better to expect something. Or if you can’t, at least have a limit over which the result doesn’t really matter, you are happy enough knowing it is more than this limit. Actually in most case that’s enough. For UI you would say over something, to forbid an operation you usually have a limit over which you will forbid it anyway, and so on. Of course, if you want the exact number of item, it can be done but it will be a lot slower.
Benchmarks will be counting the number of documents in a 5/4/10 folder hierarchy, meaning 5 level of sub-folders, each level with 4 sub-folders and 10 documents. This is about 55,000 documents in 5,500 folders. And we don’t always want to count exactly, in the benchmarks we will ask if there is more than 5, 10, 15,50 … until 40,000 documents. Because sometimes knowing than there is more than 50 documents is enough to forbid an operation.
Now let’s introduce the few options we have to count.
After a CPIT installation, you will have a few more steps to do before your platform is fully operational. If you don’t, you will mainly have two errors:
A user authenticated as anonymous has attempted to access a session owned by user... in the WebSphere logs, resulting to be always disconnected in TDS console, and a really unstable platform (a lot of errors in the ACCE)
Failed to get configuration file WcmApiConfig.properties when trying to configure the Workflow system (along with a login window you shouldn’t get)
Here are the steps to follow. Since the new CPIT installer now has two WAS profiles (one for FileNet and the other for ICN, I will add for each step if they should be executed on server A (FileNet), B (Icn), or both (AB). In the IBM WebSphere administration console:
Update: This post is now super-seeded by the last version, installing FileNet P8. I will still be answering any question you might have though.
IBM came up with something that sounds really nice: The Composite Platform Installation Tools or also called CPIT. And it is true, being able to have a running platform (for test and development only) in less than one hour sounds like a dream, especially when you know how installing P8 is a nightmare. Except it never works…
And from the one hour expected, we fall back to a few days like before. It is actually impressive how many errors this thing can produce. That’s why I write this post, trying to summarize all errors that can occur.