1. Implementing Siebel Business Applications on DB2 for z/OS
  2. Preparing to Deploy Siebel CRM on DB2 for z/OS

Preparing to Deploy Siebel CRM on DB2 for z/OS

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

  1. Review the information in the Certifications tab on My Oracle Support 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 the Certifications tab.

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

  2. Review the Siebel architecture of the DB2 for z/OS database server.

  3. 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 Siebel 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. (Unicode is required for new deployments.)

      Note: All environments in the organization (development, test, production, and others) must use the same encoding choice.

    • Decide whether to implement Coordinated Universal Time (UTC). (UTC is required for new deployments.)

    • 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 CRM requires.

    • Specify the appropriate Siebel parameters and environment for your deployment after the installation is completed.

    • Set up development, test, and other environments.

  4. The implementation team must review Siebel Alerts and Siebel CRM Update Guide and Release Notes on My Oracle Support to make sure that they are aware of known anomalies.

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