Plan for IBM DB2 for i

When planning to transfer data to IBM DB2 for i, you should consider the databases and user information, such as database names, what data is stored, and the database space needed. Some fix packs require steps prior to the transfer task to complete successfully.

Before you begin:

DB2 is integrated with i, but create the required databases and users and grant the proper privileges to those users. WebSphere Portal can create the databases for you.

The database names and users in this topic are suggested values and provide consistency throughout the documentation. Replace these values with values in environment.

WebSphere Portal uses Apache Derby during installation, and supports configuration of DB2 for an IBM System i5system. The Derby database is ideal for a test environment. For a production environment, you can move from the installed Derby database to IBM DB2 for i, but note that there is no option to transfer back to Derby.

The IBM DB2 for i database enables you to access and manage server data through an application or a user interface. In addition to providing access to and protection for data, IBM DB2 Universal Database™ for i provides advanced functions, such as referential integrity and parallel database processing.

IBM DB2 for i is the relational database manager that is fully integrated on i system. IBM DB2 for i also provides features such as triggers, stored procedures, and dynamic bitmapped indexing that serve a wide variety of application types. These applications range from traditional host-based applications to client/server solutions to business intelligence applications.

As an interface to IBM DB2 for i, the DB2 Query Manager and Structured Query Language (SQL) Development Kit for System i5 add an interactive query and report writing interface, and precompilers and tools to assist in writing SQL application programs in high-level programming languages. The SQL implementation for OS/400 allows you to define, manipulate, query, and control access to i data. It works equally well with i files and SQL tables.

If you choose to use one database to hold all WebSphere Portal, Member Manager, and content publishing information, only one user profile is required. Additional user profiles are necessary only if using multiple i systems or separate databases are required.

When WebSphere Portal creates databases, it uses the database names that are specified in wkplc_dbdomain.properties, located in the UserData directory WP_PROFILE/ConfigEngine/properties. It is possible to create up to six different databases by setting different values in wkplc_dbdomain.properties.

While configuring Portal to use one database is technically possible, use separate databases for scalability and performance tuning reasons. To use a single shared database, replace each database and user variable with the name of database and database user, respectively. The format for database names is *LOCAL/database_name for a Type 2 database connection, or a fully qualified server name such as myserver.mycompany.com/database_name for a Type 4 database connection.

In a local database environment, WebSphere Portal and IBM DB2 for i can be accessed with either a Type 4 or Type 2 connection. Type 4 is the default and recommended connection.

In a remote database environment, WebSphere Portal connects directly to the DB2 server (JDBC Type 4 connection).

  1. Review the different databases shown in the following table and replace these values with the values in environment; schema names must be different when the database is shared.

    Space required for various databases

    Application Database name Space required
    WebSphere Portal

    Used for the portal (at a minimum) or to hold all data. Stores information about user customization, such as pages, and user profile and login information.

      reldb

      commdb

      custdb

    		Depends on the number of users and portal objects, such as pages and portlets.
    Personalization,Web Content Manager

    Contains documents, personalization rules, personalization campaigns, and document library configuration information.

      jcrdb
    		Depends on the number and size of Personalization rules and campaigns, and the number and size of items and elements created in Web Content Manager.
    Feedback

    Contains the information that is logged by Web site for analysis of site activity and generating reports.

      fdbkdb
    		Depends on the amount of traffic to the site. The amount of data that is logged per login-enabled page can vary.
    LikeMinds

    Contains the recommendations to be displayed to users when their interactions with Web site have been analyzed and predictions generated.

      lmdb
    		Depends on the amount of traffic to the site.

  2. Review the tables and types of objects owned by each user.

      The architecture allows each of the following users to exist in the same database. All table spaces are approximately 2.8 GB by default. The size increases with the use of Java™ Content Repository. Table 2. Tables and objects owned by database users


      Application
      Database user placeholder
      Function
      WebSphere Portal

        releaseusr

        communityusr

        customizationusr

      		Core user who owns approximately 230 tables, used for WebSphere Portal core objects, which includes tables that store the user customizations made to pages.
      Java Content Repository

        jcr
      		Java Content Repository user who owns at least 1130 tables. The number could be higher depending on usage.
      Feedback

        feedback
      		Feedback user who owns approximately 50 tables used for logging site and personalization usage.
      LikeMinds

        likeminds
      		LikeMinds user who owns approximately 15 tables used to hold the Web site usage analysis routines and recommendation text.


Parent

Database considerations


Related tasks

http://www.ibm.com/support/docview.wss?rs=688&uid=swg27007791

 


+

Search Tips   |   Advanced Search