Professional Documents
Culture Documents
March 2007
Oracle Part No. B42516-01 Copyright 2007 Oracle. All rights reserved. Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Siebel Release Media Planning Your System Installation Maintenance Releases Installing Siebel CRM Applications Third-Party Applications Data Model Information Contacting Technical Support
Language Media Language files categorized by product category and product name are available. Language media supports a specific language for all applicable products and platforms. Encryption Media Provides strong encryption support for Siebel products and is installed after base product installation. (Base products are a prerequisite.) Encryption packs contain no language components. License and Configuration Codes Siebel CRM products might require license and configuration codes for installation and use. For information on how to obtain and use these codes if applicable, click the Siebel CRM tab at http://licensecodes.oracle.com
System Requirements and Supported Platforms FAQ 2248: What Are JAR Files and How Do You Use Them? Siebel Release Notes
Siebel Deployment Planning Guide Siebel Installation Guides for Microsoft Windows and UNIX platforms Siebel Database Upgrade Guide Implementing Siebel Business Applications on DB2 UDB for z/OS Going Live with Siebel Business Applications Siebel Anywhere Administration Guide
Maintenance Releases
Oracle provides additional Siebel releases that can be installed on top of your existing base product installation. These releases are collectively known as maintenance releases. Note: For an explanation of release types and numbering for Siebel Business Applications, see Siebel Business Application Version Numbering in the Installation and Upgrade section of Siebel SupportWebs Knowledge Base. If you already have a base product installation, a subsequent three-digit release can be installed as a maintenance release. For example, 8.0.2, if available, could be installed on top of an existing 8.0.1 installation. Releases that can only be installed as maintenance releases include fix pack releases (four-digit releases, such as 8.0.2.1 or 8.0.2.2) and Quick Fix releases. Typically, no configuration tasks are associated with installing a maintenance release. However, requirements for a given maintenance release, or for using particular supported languages or features, may vary. Every Siebel product used within a given Siebel Enterprise must share the same release level, such as 8.0.3 or 8.0.2.1.
For detailed information about installing maintenance releases and about the features or other changes provided in the release, refer to the applicable Siebel Maintenance Release Guide in the Product Documentation area of Siebel SupportWebs Knowledge Base.
A list of fixes included in product maintenance release and fix packs. Installation instructions for the latest fix packs. Fix request identification numbers, associated change request numbers, and the Siebel version in which the issue was first addressed. Resolved change request instructions, where applicable.
Plan your deployment; for example, you might install and configure server clustering software. See the Deployment Planning Guide. Determine your load-balancing strategy. See Configuring Load Balancing for Siebel Applications in the Siebel Installation Guide.
10
Create your database instance. See Configuring the RDBMS in the Siebel Installation Guide. Obtain Siebel media and create a Siebel installation image on the network, from which installs will be performed. See Creating the Siebel Installation Image on the Network in the Siebel Installation Guide. Install required third-party products. See System Requirements and Supported Platforms on Siebel SupportWeb and the Siebel Business Applications Third-Party Bookshelf. (Optional) Install search products. For specific guidelines and requirements, see the Siebel Search Administration Guide. Create directories for Siebel software and the Siebel File System. See General Considerations in Planning Your Siebel Deployment in the Siebel Installation Guide. Create the required Siebel accounts. See Creating the Siebel Service Owner Account in the Siebel Installation Guide.
3.
4. 5.
6.
11
Install Siebel Gateway Name Server, Siebel Server, and Database Configuration Utilities. Run the Siebel Configuration Wizard to configure the Siebel Gateway Name Server, Siebel Enterprise, Siebel Web Server Extension (SWSE) logical profile, and Siebel Server. See the following topics in the Siebel Installation Guide:
Installing Siebel Enterprise Server and Related Components Configuring Siebel Enterprise Server and Related Components Configuring the SWSE (task for configuring SWSE logical profile)
3.
Run the Database Configuration Wizard on the Siebel Server machine where you installed Database Configuration Utilities. This task includes creating the Siebel Database and installing the schema on the RDBMS. See Configuring the Siebel Database in the Siebel Installation Guide. NOTE: This task does not apply if you have an existing Siebel Database, such as in an upgrade scenario.
12
4.
Install your Web server, and install and configure the Siebel Web Server Extension (SWSE)applying the SWSE logical profile. See Installing and Configuring the Siebel Web Server Extension in the Siebel Installation Guide.
(Optional) Install Siebel Mobile or Developer Web Clients. See Installing Siebel Mobile Web Clients in the Siebel Installation Guide. Install Siebel Tools. See Installing Siebel Tools in the Siebel Installation Guide. (Optional) Install additional Siebel Servers, if required. See Installing the Siebel Server in the Siebel Installation Guide. (Optional) Install additional Siebel products such as the Siebel Reports Server, Siebel EAI Connector software, or the NetCharts Server. See related topics in the Siebel Installation Guide. Verify your environment using EVT. See Verifying Your Server Environment in the Siebel Installation Guide.
2. 3. 4.
5.
13
System Requirements and Supported Platforms Siebel Database Upgrade Guide Siebel Database Upgrade Guide for DB2 UDB for z/OS
See the Product Documentation section of Siebel SupportWebs Knowledge Base for other upgrade-related documentation. License and Configuration Codes Siebel CRM products might require license and configuration codes for installation and use. For information on how to obtain and use these codes if applicable, click the Siebel CRM tab at http://licensecodes.oracle.com
14
Third-Party Applications
Your companys license agreement with Oracle sets forth the permitted uses of license keys to applicable third-party products. For more information about third-party applications, see System Requirements and Supported Platforms on Siebel SupportWebs Knowledge Base.
15
Third-Party Documentation
For your convenience, we include third-party product documentation as a downloadable ZIP file from Siebel SupportWeb. See the link in the Installation and Upgrade section of Siebel SupportWebs Knowledge Base.
16
17
Note: If you are unable to access the Service Request part of Siebel SupportWeb for any reason, see the email section following to find out how to submit Service Requests. All users need a username and password to access Siebel SupportWeb. Only Designated Contacts of licensed customers get access to the Service Request section of Siebel SupportWeb. When submitting a Service Request, you should be prepared to provide the following information:
Siebel product and version (for example, V8.0.2.1 instead of V8.0). Database and version. Client and Siebel Server operating system. Severity level. Review the Severity Level Definitions document. Environment where the problem is occurring (for example, development, production, test). As much detail and background information as possible.
18
Email
If you are a Designated Contact and are unable to access the Service Request area in Siebel SupportWeb, log your requests using email. In addition to logging Service Requests by email, send supporting documents (such as log files) for Service Requests logged by other methods using email. Send email to Siebel Technical Support at siebelsupport@oracle.com To log a Service Request, send an email note with a description of the problem and information as outlined in the previous section. For more information, see the Using Technical Services area of Siebel SupportWebs Knowledge Base.
Telephone
Designated Contacts may contact Oracles Siebel Technical Support by telephone regarding critical production Severity 1 and 2 issues. For more information, including telephone numbers, see the Siebel SupportWeb Login page: http://ebusiness.siebel.com/supportweb
19
Provide information about whether this is a new deployment or an upgraded deployment that previously implemented CTI Connect. Specify whether Parallel or USB port is required.
20