Roadmap for Deploying Siebel Open UI in an Existing Deployment

In an existing Siebel CRM deployment, you have already installed and configured Siebel Business Applications for Siebel CRM version 8.1.1.x, version 8.2.2.x, version 15.x, or version 16.x, and are migrating to Siebel Open UI applications for the current release.

To deploy Siebel Open UI applications for the current release in an existing Siebel CRM deployment of a prior release, you perform the following tasks:

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

2. Perform a migration installation of the current release. Use the documented methods for performing migration installations for all applicable installed Siebel modules.

   Perform the migration installation for Siebel Application Interface (for an existing instance of Siebel Web Server Extension for a prior version), Siebel Gateway, Siebel Server, Siebel Mobile Web Clients, and Siebel Tools.

   For information about requirements for migration installations, see the Siebel Installation Guide for the operating system you are using. For more information about the installation tasks, see the Siebel Installation Guide for the operating system you are using.

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

4. Run Incremental Repository Merge for the Siebel database.

   For more information about the requirements and steps for 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 the current release.

5. Publish and distribute updates to the Siebel runtime repository that include your own custom Siebel Repository content. Update the Siebel runtime repository for the Siebel Servers and Siebel Mobile Web Clients.

   For more information, see Using Siebel Tools.

6. Depending on your deployment strategy and requirements and on the specific products that you are using, determine which applications to deploy.

   For more information, see "Siebel Business Applications That You Can Deploy Using Siebel Open UI".

7. As needed, to deploy newer 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 Siebel Application Interface or install and configure a new instance of Siebel Application Interface. (For the current release, you must do these steps in all cases.)

   For example, you might need to perform these tasks to use Siebel Self Service or Siebel Partner Portal, if these applications did not exist when you initially configured the Siebel applications. For more information, see applicable product-specific documentation and the Siebel Installation Guide for the operating system you are using.

8. As needed to deploy the Siebel Mobile applications, run a script on the Siebel Server to add these applications to the Siebel Server.

   
   

   Note: If you reconfigured both the Siebel Server and Siebel Application Interface in Step 7, then the Siebel Mobile applications are also configured and you do not need to perform this step. After performing Step 8, you must configure the Siebel Application Interface.

   
   

   For more information, see Siebel Mobile Guide: Disconnected or Siebel Mobile Guide: Disconnected.

9. 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 and the Siebel Installation Guide for the operating system you are using.

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

    Your deployment process probably will include multiple phases of testing.

Related Topics

"About Deploying Siebel Open UI"

"Roadmap for Deploying Siebel Open UI in a New Deployment"

"Siebel Open UI Client Requirements"

"Migration Tasks for Siebel Open UI"