FileNet Content Manager 5.2.1: build the repository (F281G)

• A new development or staging environment has to be stood up.
• Content keeps growing in a single area and it has to be spread out before it fills up.
• You have never created an object store and the first one is going to be in production.
• Somebody has to decide whether content goes to the database, to disk, or to an external device.

• Build an object store: create the JDBC data sources, create the object store and add it as a repository to an IBM Content Navigator desktop
• Work with storage areas: types of storage area, storage options and architectures, storage policies, creating a file storage area, creating a file storage policy and creating an advanced file storage area
• Appendix: starting and stopping system components

• Labs where you build the repository: the JDBC sources, the object store, registering it on a Content Navigator desktop, and the storage areas including the advanced one.
• Taught directly by IBM Champion instructors from the SIXE team.
• Credly badges on completion: credly.com/organizations/sixe/badges
• Flexible format — online, classroom or onsite — in closed groups, priced per attendee, in the language of your choice (ES / EN / FR).

What is the difference between a storage area and a storage policy?
The area defines where the content is stored — database, file system, external device or a replicated advanced area; the policy decides which area, or which farm of areas, is used for which content. With no policy everything lands in the default area, which is behind most space problems.

Is advanced storage covered?
Yes: you create a normal file storage area and then an advanced one, which connects several devices — S3, OpenStack, file system — as replicas of the same content, and that is how repository high availability is handled. For retention on an external system, what you want is a fixed area with its fixed content device.

Do we leave with a repository built?
One gets built in class, start to finish, and that is the exercise. If you are going to build yours afterwards, bring the decisions you have already made — database, storage, growth policy — and we go over them as we go.

Group size and language?
Closed groups of four to ten people, in Spanish, English or French. We run it with fewer than four as well, though it usually pays to wait and fill the group.

• F2800G — the P8 platform
• F282G — object metadata
• F283G — security