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

Process of Preparing for a Siebel Application Deployment on DB2 for
z/OS

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

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 DB2 databases, the requirements include:
   • Applying required DB2 maintenance as listed in the IBM informational APAR ii13487.
   • Installing a supported version of DB2 Connect and the appropriate IBM Fix Pack as specified in the System Requirements and Supported Platforms on Siebel SupportWeb.
   • Installing Unicode Conversion Services.
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 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 or EBCDIC encoding scheme code page.
   • Decide whether to implement Coordinated Universal Time (UTC).
   • Decide which security scheme to use (native DB2 security or Lightweight Data 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 applications require.
   • 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 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 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 between these groups of people.
   • DB2 DBAs using the Siebel application for the first time should be aware that in the Siebel application:
     • There are many 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.