This set of tasks includes:

• Installation of specific applications and services: It is difficult to characterize this task in general as it varies greatly from vendor to vendor. Open Text has a formidable array of applications and solutions that is growing larger on a quarterly basis. That means that while the more mature (in terms of being part of Open Text) applications like Content Server and Archive Server follow a similar and unified installation pattern, but newer acquisitions like the very recent StreamServe have their own unique installation that will vary from the single install.
  • Open Text has moved to an almost exclusive download method for most if not all products and solutions, though physical media can and is still produced and shipped ...
  • The point isn't the method of delivery but the method of installation, is it GUI and/or Wizard-based? is it unzipping a distribution?
• Configuration of base system will include some but probably not all of the following:
  
  • connection to external services:
    • databases
    • ldap / authentication servers
    • authorization servers
    • email servers (for delivery of application-generated email)
    • storage servers
  • assignment of IP addresses and ports for local services
  • creation of administration services
    • notifications
    • process managers (workflow, email delivery)
    • user synchronization
  • integration with search / indexing solution (full-text or database keys)
  • enterprise taxonomy template:
    • top-level folder/container "hierarchy" (the enterprise landing page for the application)
    • groups/role setup
    • access control (mapping the groups to the hierarchy)
  • creation of project / folder / container templates (theming or skinning)
  • integration with trusted clients (scanning stations, email servers, financial systems, backup managers)
  • integration with untrusted clients (web browsers, desktop clients, ftp, unmanaged email)
  • auditing and logging subsystem
  • application reporting
    • Errors and alerts
    • System Usage
• Configure the Application/Solution specific settings
  • creation of workflows
  • creation of project spaces
  • creation of access rules
  • creation of indexing rules
  • creation of classifications
    
    • automatic classification

Typically everything should be working and configured ready for business use. If, for instance, a specific workflow must exist to meet the solution design, then said workflow would be created (however if "workflow capability" is in the design then only the ability to create and use workflows is implemented).