Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390 >

Preparing to Deploy Siebel on DB2 for z/OS and OS/390

Several items should be considered when preparing your implementation of Siebel eBusiness Applications using IBM DB2 UDB for z/OS and OS/390. These considerations are covered in-depth throughout this guide.

To prepare for Siebel deployment on DB2 for z/OS and OS/390

  1. Review the prerequisites in the System Requirements and Supported Platforms on Siebel SupportWeb for your Siebel application version and make sure that all requirements are met. For the DB2 area, that includes:
    • Applying required OS maintenance as listed in the IBM informational APAR ii13487.
    • Installing a supported version of DB2 Connect and IBM Fix Pack.
    • Installing Unicode Conversion Services.
  2. Review Siebel architecture with the DB2 for z/OS database server with Siebel Expert Services.
  3. Decide on DB2-related architecture and other related choices:
    • Separate or shared DB2 subsystem for production.
    • ASCII or EBCDIC encoding scheme, code page selection.
    • Security scheme (native DB2 security or LDAP).
    • Whether you plan to implement UTC.
    • Remember that Siebel requires deployment of user-defined functions (UDFs) and stored procedures.
    • Understand and design the database storage layout for the Siebel schema.
    • Understand the Siebel Schema and review possible table space partitioning.
    • If batch processing through EIM is planned, review partitioning, so it will work for both batch and online activities.
    • Review and set up required and recommended DB2 system parameters (DSNZPARMs).
    • Configure the DB2 Data Distribution Facility and the z/Series Workload Manager (WLM).
    • After the installation is completed, set up Siebel parameters and environment variables as it suits your deployment.
    • Decide on backup and recovery mechanisms.
    • Decide on maintenance procedures, such as RUNSTATS and REORG.
    • Set up development, test, and other environments.
  4. The implementation team should review the Release Notes and Alerts on Siebel SupportWeb to make sure that they are aware of known anomalies.
  5. Have a project staff:
    • Dedicate DBAs to support Siebel deployment.
    • Establish good working relationships with mid-tier administrators, because some operations, such as installation or upgrade, require close cooperation between these groups of people.
    • DB2 DBAs using the Siebel application for the first time should be aware of the following because it contains:
      • Many objects, some of them unused.
      • Data types, mainly VARCHAR, that are used in the Siebel data model.
      • All dynamic SQL.
      • SQL that is generated by the Siebel application versus traditional SQL precisely coded by developers.

Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390