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, and are migrating to the current release, Siebel CRM version 15.0. You have previously deployed applications using Siebel Open UI, high interactivity, or standard interactivity, or some combination of these. It is strongly recommended to enable Siebel Open UI for the employee applications that support either Siebel Open UI or high interactivity.

Note:

Steps 1 through 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:

Review all of the applicable documentation and requirements.

For more information, see Chapter 2, "Overview of Siebel Open UI," including "Related Information About Deploying Siebel Open UI". See also "About Deploying Siebel Open UI".
Perform a migration installation of the current release, which is Siebel CRM version 15.0 (Siebel Innovation Pack 2015). Use the documented methods for performing migration installations (patch installations) for all applicable installed Siebel modules.

Perform the migration installation for existing instances of Siebel Enterprise Server (such as Siebel Gateway Name Server or Siebel Server), Siebel Web Server Extension (SWSE), Siebel Mobile Web Clients, and Siebel Tools.

Note:
In general, it is not necessary to run the Siebel Configuration Wizards after performing a migration installation, because this task migrates your existing configurations.

For more information about the installation tasks, see the Siebel Installation Guide for the operating system you are using.
Install the latest Siebel Patchset release, where available.

For information about obtaining and installing a Siebel Patchset release, see Siebel Patchset Installation Guides, 1614310.1 (Article ID) on My Oracle Support.
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. For more information about the requirements and steps for running Incremental Repository Merge, see Siebel Database Upgrade Guide. See also the Siebel Installation Guide for the operating system you are using.

Your Siebel database will include all of the repository updates and seed data to support the functionality of Siebel Innovation Pack 2015, including Siebel Open UI.
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.

Depending on your deployment strategy and requirements and on the specific products that you are using, do one or more of the following. Details are provided in subsequent steps.

Keep your applications as they were deployed in your previously installed and configured Siebel CRM release, before you installed the current release as a migration installation. Go to Step 11 .

Note:

For existing installations (migration installation case), applications generally use their existing client user interface, based on your prior deployment choices. However, Siebel Open UI is enabled after a migration from any prior release in which Siebel Open UI was not supported or was not explicitly enabled or disabled, for any of the applications that support both Siebel Open UI and high interactivity. If you want to revert these applications to high interactivity, then set EnableOpenUI to False.

Deploy an employee application using Siebel Open UI (that was previously deployed using high interactivity). In this case (unless Siebel Open UI was already enabled), you are simply changing an existing Application Object Manager component from high interactivity to Siebel Open UI. Go to Step 7.
Deploy an employee application using high interactivity (that was previously deployed using Siebel Open UI). In this case, you are simply changing an existing Application Object Manager component from Siebel Open UI to high interactivity. Go to Step 8 .

Deploy an employee application using both Siebel Open UI and high interactivity, to support a phased migration to Siebel Open UI. In this case, you are creating a copy of an existing Application Object Manager component and disabling Siebel Open UI for the new copy. Go to Steps 9 and 10 .

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, if you have not already done so, perform Step 11 .
To deploy the Siebel Mobile applications, if you have not already done so, perform Step 12 .

As needed, enable Siebel Open UI for an existing employee application (that was previously deployed using high interactivity). Do the following, then go to the next applicable step for your deployment.
- For an Application Object Manager component, such as Call Center Object Manager, set the EnableOpenUI parameter to True. (The HighInteractivity parameter must also be set to True.)
- For all installed Siebel Mobile Web Clients using this application, edit the application configuration file and set the EnableOpenUI parameter to True. For example, for Siebel Call Center, set this parameter in the uagent.cfg file, in the [InfraUIFramework] section. (The HighInteractivity parameter must also be set to True.)
  
  Note:
  If your existing Application Object Manager has existing users, then it is recommended that you instead perform Steps 9 and 10.
For more information, see the Siebel Installation Guide for the operating system you are using and Siebel System Administration Guide.
As needed, disable Siebel Open UI for an existing employee application and enable high interactivity. Do the following, then go to the next applicable step for your deployment.
- For an Application Object Manager component, such as Call Center Object Manager, set the EnableOpenUI parameter to False. (The HighInteractivity parameter must be set to True.)
- For all installed Siebel Mobile Web Clients using this application, edit the application configuration file and set the EnableOpenUI parameter to False. For example, for Siebel Call Center, set this parameter in the uagent.cfg file. (The HighInteractivity parameter must be set to True.)
  
  Note:
  If your existing Application Object Manager has existing users, then it is recommended that you instead perform Steps 9 and 10.
For more information, see the Siebel Installation Guide for the operating system you are using and Siebel System Administration Guide.
As needed, deploy an employee application using both Siebel Open UI and high interactivity. Do the following, then go to Step 10.
- Add a new Application Object Manager component and set the EnableOpenUI parameter to True or False, according to your requirements. For example, you might create a new component for Siebel Open UI that is based on an existing component, such as Call Center Object Manager. (When you copy an Application Object Manager component, make sure that the original application name is copied too.)
- Copy the configuration file for the application corresponding to the Application Object Manager that you created. For all installed Siebel Mobile Web Clients, edit the copied configuration file and set the EnableOpenUI parameter to True or False, according to your requirements.
For more information, see the Siebel Installation Guide for the operating system you are using and Siebel System Administration Guide.
On the Web server computer where you installed the SWSE, manually create virtual directories for any applications for which you created new Application Object Manager components in Step 9. Go to the next applicable step for your deployment.

For more information, see the Siebel Installation Guide for the operating system you are using.
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 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".
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 11, then these 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".
(Optional) As needed, perform configuration (customization) tasks for your Siebel Open UI applications.

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.
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.

Applications that are enabled for both Siebel Open UI and high interactivity would use different URLs. Your deployment process probably will include multiple phases of testing.
For applications that are deployed for both Siebel Open UI and high interactivity, as described in Steps 9 and 10 , roll out the Siebel Open UI client to additional users, as the features of this client meet the acceptance requirements of the test users. Convert applications from high interactivity or 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 the users of any other applications that you have deployed using high interactivity or standard interactivity. For each type of client, 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.