Horizontal Scalability - Library server

[pankaj.puranik]

Hi

The IBM documentation says the following about Horizontal Scalability.
I did not really understand how this would work practically in terms of ingestion and retrieval.

"Even though Content Manager OnDemand allows a single library server for each instance,
this library server can be scaled horizontally. The library server is scaled horizontally by using
one or both of the following methods:
 The database tables (both the system and the application group) can be placed in different
databases (z/OS) or different table spaces (Multiplatforms and z/OS) at the table level.
Therefore, each of these tables can scale to the maximum practical size that is supported
by the database within the operational constraints of maintenance and performance.
Content Manager OnDemand does not impose a limitation.
 The application group data table design facilitates the following actions:
– You can create as many application groups as you need to support the required data to
be archived.
– Each application group can be segmented into multiple tables where the table
segmentation is based on size.
– Each of these application group data tables can be placed in a separate database
(z/OS) or table space (Multiplatforms and z/OS)."


Thanks
Pankaj.

[Justin Derrick]

Everything you've pasted in is referring to z/OS -- i.e., mainframes.  It likely doesn't apply to you.

There are very few situations in which a single Library server can't handle the load from regular day-to-day operations.  Even on some of the largest systems I've worked on, library servers are only split for redundancy purposes, not because scalability of a single server is an issue.

-JD.