System configuration

Here are the assumptions about the system:
  • Two groups of users: the customer service department and users at Customer XYZ.
    Note: This example assumes that customers access the system by using the Content Manager OnDemand Web Enablement Kit (ODWEK) feature. However, for purposes of demonstrating how the system works and how to use the administrative client to implement the requirements, these users could easily represent another department within the organization.
  • Add the telephone bill report to the system. The telephone report is generated by an application program running on a z/OS® system. Download is used to transmit the report data to the Content Manager OnDemand server. The report is indexed on the server.
  • Content Manager OnDemand servers. The library server and the object server reside on the same workstation.
  • Database. Use table spaces and create incremental backups each time that a report is loaded into the system. The database resides on RAID storage devices. Use Tivoli® Storage Manager to maintain the database log files and backup image files. Tivoli Storage Manager maintains the files in an automated tape library.
  • Cache storage. When a report is loaded into the system, Content Manager OnDemand stores a copy in cache storage and maintains the report for 60 days. Reports are cached on RAID storage devices attached to the object server.
  • Archive storage. When a report is loaded into the system, Content Manager OnDemand stores a copy of the report in archive storage. Tivoli Storage Manager maintains the report in an optical storage library for five years.
  • System parameters. Users must log on to the system with a password. Set the minimum password length to six characters. Accept the defaults for the other system parameters.