Deploying Siebel Open UI > Deploying Siebel Open UI for Siebel Business Applications >

Roadmap for Deploying Siebel Open UI in an Existing Deployment


In an existing Siebel CRM deployment, you have already installed and configured the Siebel Business Applications for Siebel CRM version 8.1.1.x or version 8.2.2.x. You have previously deployed applications using the high interactivity or standard interactivity clients. (You might have already deployed some applications using Siebel Open UI.)

NOTE:  Step 1 through Step 5 apply for any existing deployment of Siebel CRM.

To deploy applications using Siebel Open UI in an existing Siebel CRM deployment, you perform the following tasks:

  1. Review all of the applicable documentation and requirements.

    For more information, see Overview of Siebel Open UI including Related Information About Deploying Siebel Business Applications and Siebel Open UI. See also About Deploying Siebel Open UI.

  2. Perform a patch installation of the current release of Siebel CRM, which is Siebel CRM version 8.1.1.11 or version 8.2.2.4. Use the documented methods for performing patch installations for all applicable Siebel modules.

    NOTE:  For the Siebel Enterprise Server modules and the Siebel Web Server Extension (SWSE), patch installation is also called migration installation. In general, it is not necessary to run the Siebel Configuration Wizards after performing a migration installation, because the configuration has been migrated.

    Perform the patch installation for all applicable modules, including the Siebel Gateway Name Server, the Siebel Server, and the Siebel Web Server Extension (SWSE). Also install Siebel Mobile Web Clients and Siebel Tools clients, as needed. For more information about the installation tasks, see the Siebel Installation Guide for the operating system you are using. See also the applicable Siebel Maintenance Release Guide on My Oracle Support.

  3. Install the latest Siebel Patchset release.

    For information about obtaining and installing a Siebel Patchset release, see Siebel Patchset Installation Guide for Siebel CRM 8.1.1.11 / 8.2.2.4 IP2013, 1614310.1 (Article ID) on My Oracle Support. See also the readme document for the patchset release.

  4. Run Incremental Repository Merge for the Siebel database.

    Before you run Incremental Repository Merge, you must have installed at least one Siebel Server with Database Configuration Utilities and installed Siebel Tools. In addition, you must update the Siebel Repository files, as described in the Siebel Installation Guide for the operating system you are using. For more information about running Incremental Repository Merge, see Siebel Database Upgrade Guide.

    Your Siebel database will include all of the repository updates and seed data to support the functionality of Siebel CRM version 8.1.1.11 or version 8.2.2.4, including Siebel Open UI.

  5. Compile new Siebel Repository (SRF) files that include your own custom Siebel Repository content. Update the SRF files for the Siebel Servers and Siebel Mobile Web Clients.

    For more information, see Siebel Database Upgrade Guide and Using Siebel Tools. See also the Siebel Installation Guide for the operating system you are using.

  6. Depending on your deployment strategy and requirements for Siebel Open UI and on the products that you are using, do one or more of the following. For example:
    • To deploy a high interactivity application using Siebel Open UI, perform Step 7. In this case, you are simply changing an existing Application Object Manager component from high interactivity to Siebel Open UI.
    • To deploy an application using both high interactivity and Siebel Open UI, to support a phased migration to Siebel Open UI, perform Step 8 and Step 9. In this case, you are creating a copy of an existing Application Object Manager component and enabling Siebel Open UI for the new copy.

      NOTE:  Using Siebel Open UI side by side with high interactivity requires that you use multiple browsers in your overall Siebel CRM deployment. For more information about deploying Siebel Open UI with multiple browsers, see Siebel Open UI Client Requirements and Choosing a User Interface for Siebel CRM.

    • To deploy certain new Siebel Business Applications for Siebel Open UI, perform Step 10.
    • To deploy the Siebel Mobile applications if you have not already done so, perform Step 11.
  7. To enable Siebel Open UI for an existing Application Object Manager component, such as Call Center Object Manager, set the EnableOpenUI and HighInteractivity parameters to True.

    NOTE:  If your existing Application Object Manager has existing users, then it is recommended that you instead perform Step 8 and Step 9.

    For more information, see the Siebel Installation Guide for the operating system you are using and Siebel System Administration Guide.

  8. As needed for your deployment of Siebel Open UI, add new Application Object Manager components and set the EnableOpenUI and HighInteractivity parameters to True. For example, you might create a new component based on an existing component, such as Call Center Object Manager. Then go to Step 9.

    TIP:   When you copy Application Object Manager components, make sure that the original application name is copied too.

    For more information, see the Siebel Installation Guide for the operating system you are using and Siebel System Administration Guide.

  9. On the Web server computer where you installed the SWSE, manually create virtual directories for the applications for which you created new Application Object Manager components in Step 8.

    For more information, see the Siebel Installation Guide for the operating system you are using.

  10. As needed, to deploy certain new Siebel Business Applications for Siebel Open UI that did not exist when you originally configured your Siebel CRM environment, do the following:
    1. Reconfigure the Siebel Server or install and configure a new instance of Siebel Server.
    2. Reconfigure the SWSE logical profile. Also reconfigure the SWSE or install and configure a new instance of SWSE.

      For example, you might need to perform these tasks to use the new Siebel Self Service Portal for Siebel Open UI or the new Siebel Partner Portal for Siebel Open UI. For more information, see the applicable Siebel Maintenance Release Guide on My Oracle Support, applicable product-specific documentation, and the Siebel Installation Guide for the operating system you are using. See also Siebel Business Applications That Require Siebel Open UI.

  11. As needed to deploy the Siebel Mobile applications, run scripts to add these applications to the Siebel Server and the SWSE.

    NOTE:  If you reconfigured the Siebel Server and SWSE in Step 10, then the Siebel Mobile applications are also configured and you do not need to perform this step.

    For more information, see Siebel Mobile Guide: Connected or Siebel Mobile Guide: Disconnected. See also Siebel Business Applications That Require Siebel Open UI.

  12. As needed to enable Siebel Open UI for applications on Siebel Mobile Web Clients, edit the application configuration files to set the EnableOpenUI and HighInteractivity parameters to True. For example, for Siebel Call Center, set these parameters in the uagent.cfg file.

    For more information, see the Siebel Installation Guide for the operating system you are using.

  13. (Optional) As needed, perform configuration (customization) tasks for your Siebel Open UI applications. For example, for customer applications that were originally designed for standard interactivity, you must perform additional configuration steps.

    For example, you might need to perform some of the tasks described in Migration Tasks for Siebel Open UI. See also Configuring Siebel Open UI.

  14. Make the URLs for the Siebel Open UI applications available to test users, who can help you to ensure the readiness for your company's specific functional requirements.

    In most cases, the applications that are enabled for Siebel Open UI use different URLs than the existing high interactivity or standard interactivity applications. Your deployment process probably will include multiple phases of testing.

  15. Roll out the Siebel Open UI client to additional users, as the features of this client meet the acceptance requirements of the test users. Add more Application Object Managers with Siebel Open UI enabled and add the corresponding virtual directories, as needed.

    Your gradual deployment of applications using Siebel Open UI does not have to affect users of other applications that you have deployed using high interactivity or standard interactivity. For each type of application, users must use a browser that meets documented requirements.

    Depending on your requirements and on the features supported for Siebel Open UI in a given Siebel CRM release, you might eventually migrate all of your users to Siebel Open UI.

Related Topics

About Deploying Siebel Open UI

Roadmap for Deploying Siebel Open UI in a New Deployment

Siebel Open UI Client Requirements

Choosing a User Interface for Siebel CRM

Migration Tasks for Siebel Open UI

Deploying Siebel Open UI Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.