Accessibility Guide for Siebel eBusiness Applications > Using Siebel Accessibility Features > Enabling Accessibility Features in Standard Interactivity Mode >

Process Flow for Enabling Accessibility Features


Enabling accessibility features requires completion of the following tasks:

  1. Determine which deployment approach to use. This guide assumes that most customer implementations will deploy high and standard interactivity in a mixed environment on the same Siebel Server.
  2. Perform deployment tasks, based on deployment approach selected. Unless a high number of users require accessibility enhancements, most customer sites will want to deploy both high interactivity applications and the standard interactivity accessibility enhancements on the same Siebel Server. If deploying high and standard interactivity on the same Siebel Server, you need to:
    1. Define the second instance of the Application Object Manager.

      See Creating a Second Application Object Manager for Use with Standard Interactivity Mode.

    2. Set up a virtual directory on the Web Server (or SWSE).

      See Adding a Virtual Directory.

      The Application Object Manager can support only one instance of the CFG file. If you are deploying a separate instance of the Application Object Manager to support accessibility, then define it and set up a virtual directory on SWSE.

      NOTE:  It is not necessary to define a second instance of the Application Object Manager for Dedicated or Mobile Web Client deployments or for mixed-environment deployments where high and standard interactivity do not reside on the same Siebel Server.

  3. Modify the application CFG file. The application CFG file must be modified to set accessibility and standard interactivity parameters, regardless of the deployment option chosen.
    • If you are deploying standard interactivity on the same Siebel Server where high interactivity mode is deployed, modify the CFG file associated with the Application Object Manager set up in Task 2.
    • If you are deploying standard interactivity through a Dedicated or Mobile Web Client, perform this task in a client-side file associated with the appropriate application (such as Call Center), and then distribute that CFG file to the Siebel installations on the client machines.

For the procedure that applies to all deployment options, see Configuring an Employee Application CFG File for Accessibility.

Accessibility Guide for Siebel eBusiness Applications