Preparing to Deploy Siebel Business Applications on DB2 for z/OS

This chapter provides information to help you plan your implementation of Oracle’s Siebel Business Applications using IBM DB2 Version 11.1 for z/OS (hereafter referred to as DB2 for z/OS). It contains the following topics:

About Deploying Siebel Business Applications on DB2 for z/OS

Many of the tasks involved in installing and configuring Siebel Business Applications are the same for all database platforms. However, there are several considerations you need to keep in mind when implementing Oracle’s Siebel Business Applications using DB2 for z/OS, and several implementation tasks that are specific to the DB2 for z/OS platform. These considerations and tasks are described in depth throughout this guide.

For general information on installing the Siebel Enterprise Server components, including the Siebel Gateway, Siebel Server, and Database Configuration Utilities, see Siebel Installation Guide for the operating system you are using. This guide describes how to install and configure the Siebel Schema on DB2 for z/OS.

Preparing for a Siebel Business Applications Deployment on DB2 for z/OS

Preparing to deploy Siebel Business Applications on DB2 for z/OS involves the following steps:

Review Siebel System Requirements and Supported Platforms on Oracle Technology Network for your Siebel application version and make sure that all requirements are met.
For DB2 databases, the requirements include:
- Installing a supported version of DB2 Connect and the appropriate IBM Fix Pack, as specified in Siebel System Requirements and Supported Platforms on Oracle Technology Network.
- Ensuring that the z/OS Unicode Conversion Services have the conversions required by the code pages for your DB2 subsystem.
  
  Note: The Siebel Bookshelf is available on Oracle Technology Network (http://www.oracle.com/technetwork/indexes/documentation/index.html) and Oracle Software Delivery Cloud. It might also be installed locally on your intranet or on a network location.
Review the Siebel architecture of the DB2 for z/OS database server.
Decide on the DB2-related architecture and other related choices:
- Understand and design the database storage layout for the Siebel Schema.
- Review possible table space partitioning.
  If you plan on using batch processing through EIM, ensure the partitioning scheme is appropriate for both batch and online activities.
- Decide whether to use a separate or shared DB2 subsystem for production.
- Configure the DB2 Data Distribution Facility and the z/OS Workload Manager (WLM).
- Review and set up the required and recommended DB2 system parameters (DSNZPARMs).
- Decide whether to select an ASCII, EBCDIC, or Unicode encoding scheme code page.
- Decide whether to implement Coordinated Universal Time (UTC).
- Decide which security scheme to use, either native DB2 security or Lightweight Directory Access Protocol (LDAP).
- Decide on backup and recovery mechanisms.
- Decide on maintenance procedures, such as RUNSTATS and REORG.
- Ensure you know how to deploy the user-defined functions (UDFs) and stored procedures that Siebel Business Applications require.
- Specify the appropriate Siebel parameters and environment for your deployment after the installation is completed.
- Set up development, test, and other environments.
The implementation team must review Siebel Alerts and Siebel Release Notes on My Oracle Support to make sure that they are aware of known anomalies.
Establish a project staff:
- Dedicate database administrators (DBAs) to support the Siebel application deployment.
- Establish good working relationships with midtier administrators because some operations, such as installation or upgrade, require close cooperation with these groups of people.
- DB2 DBAs using the Siebel application for the first time need to be aware that in the Siebel application:
  - There are many database objects, some of them unused.
  - The Siebel data model uses different data types, mainly VARCHAR.
  - Dynamic SQL is generated versus traditional SQL precisely coded by developers.

About the Deployment Planning Worksheet

Before starting your DB2 for z/OS implementation, make a copy of the worksheet in Deployment Planning Worksheet. Use this copy to record information about your deployment team and your deployment environment.

Distribute a copy of the completed worksheet to each member of the deployment team. You will need the information you have recorded on the worksheet at various stages during the implementation process. Record changes to your deployment environment on the worksheet for future reference.

About File Path and Directory Naming Conventions

This guide uses the following file path and directory naming conventions to specify file locations:

SIEBEL_ROOT. This location is the main Siebel release installation directory. Enterprise Server components, such as the Siebel Gateway and the Siebel Servers, are installed into this directory. The default top-level installation directory is C:\siebel\8.1.1.0.0\ses (Windows) or /siebel/8.1.1.0.0/ses (UNIX).

Note: $SIEBEL_ROOT (no italics) represents the value of the SIEBEL_ROOT environment variable, which usually corresponds to a module-specific installation directory, for example, siebel/siebsrvr for the Siebel Server.
SIEBSRVR_ROOT. This location is the Siebel Server installation directory. By default, the Siebel Server is installed in C:\siebel\8.1.1.0.0\ses\siebsrvr (Windows) or /siebel/8.1.1.0.0/ses/siebsrvr (UNIX).
DBSRVR_ROOT. This location is the directory in which the Siebel Database Configuration Utilities are installed on the Siebel Server. By default, the Database Configuration Utilities are installed in C:\siebel\8.1.1.0.0\ses\dbsrvr (Windows) or /siebel/8.1.1.0.0/ses/dbsrvr (UNIX).

Use lowercase for all file names, directory names, path names, parameters, flags, and command-line commands, unless you are instructed otherwise.