Preparing the database wizard

Before you can use the wizard to create databases for your IBM® Connections deployment, prepare the database server.

Before you begin

Ensure that you have given the necessary permissions to the user IDs that need to log in to the database system and access the IBM Connections Wizards directory.

Notes:
  • If you are planning to create multiple database instances, prepare and run the database wizard once for each instance.
  • (DB2® only) Create a dedicated IBM DB2 database user named lcuser. For more information, see the Creating a dedicated DB2 user topic.

  • (Oracle only) Ensure that the Statement cache size for the data sources on WebSphere Application Server is no larger than 50. A higher value could lead to Out Of Memory errors on the application server instance.

  • (AIX® only) If you are downloading the wizard, the TAR program available by default with AIX does not handle path lengths longer than 100 characters. To overcome this restriction, use the GNU file archiving program instead. This program is an open source package that IBM distributes through the AIX Toolbox for Linux™ Applications at the IBM AIX Toolbox web site. Download and install the GNU-compatible TAR package. You do not need to install the RPM Package Manager because it is provided with AIX.

    After you have installed the GNU-compatible TAR program, change to the directory where you downloaded the IBM Connections TAR file, and enter the following command to extract the files from it:

    gtar -xvf IBM_Connections_5.5_wizards_lin_aix.tar

    This command creates a directory named after the wizard.

  • (AIX only) Download and install the following packages from the AIX Toolbox for Linux Applications webpage:

    gtk2-2.10.6, pango-1.14.5, fontconfig-2.4.2, pkg-config-0.19, libjpeg-6b, freetype2-2.3.9, expat-2.0.1, zlib-1.2.3, xft-2.1.6, xcursor-1.1.7, glib-1.2.10, glib2-2.12.4, atk-1.12.3, gettext-0.10.40, libpng-1.2.32, and libtiff-3.8.2

    Note: Some of these packages have dependencies on other packages. The AIX package installer alerts you to any additional packages that might be required.

About this task

To prepare the database wizard, complete the following steps:

Procedure

  1. Log in to your database server as the root user or system administrator.
  2. (AIX and Linux only) Grant display authority to all users by running the following commands under the root user or system administrator:
    xhost + // Grant display authority to other users
    Note: If granting display authority to all users is a security concern for you, change the command to grant display authority to a specific user or users. For more information about this command, consult your AIX or Linux administrator guide.

    echo $DISPLAY // Echo the value of DISPLAY under the root user

  3. (AIX and Linux only) Ensure that the current user is qualified or else switch to a qualified user by running the following commands:
    • DB2

      su – db2inst1 // db2inst1 is the default DB2 administrator

      export DISPLAY=hostname:displaynumber.screennumber

      where hostname:displaynumber.screennumber represents the client system, monitor number, and window number. For example: localhost:0.0

      xclock // Display the clock, confirming that the current user has display authority and can run the wizard

      // Press Ctrl + C to close the clock and return to the command prompt

    • Oracle
      Note: Before running the database wizard, you must create an Oracle database instance.

      su – oracle // oracle is the Oracle database administrator

      export DISPLAY=hostname:displaynumber.screennumber

      xclock //Display the clock, confirming that the current user has display authority and can run the wizard

      // Press Ctrl + C to close the clock and return to the command prompt

      where hostname:displaynumber.screennumber represents the client system, monitor number, and window number. For example: localhost:0.0

    Note: If you can see the xclock application running after issuing the xclock command, then you have permission to run the database wizard. If you cannot see the xclock application, run the xhost + command as root user and then run the su command.
  4. Start the database instance:
    Note: Run the database commands under the user account that has administrative access to the database.
    • AIX or Linux:
      • DB2

        db2start // Start the current DB2 instance

        Note: For more information about starting a DB2 instance, go to the Setting the current instance environment variables web page in the DB2 information center.
      • Oracle (login as oracle or use the su oracle command to change to oracle)

        export ORACLE_SID=orcl // Specify the current Oracle database

        export ORACLE_HOME=/home/oracle/oracle/product/10.2.0/db_1 // Specify the Oracle home directory

        cd $ORACLE_HOME/bin

        ./sqlplus "/ as sysdba"

        startup // Start the current Oracle database

    • Microsoft™ Windows™:
      Note: Windows registers most database instances as a service. You can start or stop a database service manually if necessary.
      • DB2
        1. Log in to the Control Center.
        2. In Object View, right-click the database instance.
        3. In the menu, click Start to start the database manager.
      • Oracle
        1. Open the Windows Services panel: Click Start > All Programs > Administrative Tools > Services.
        2. Right-click the Oracle service.
        3. From the menu, click Start to start the database service.
      • SQL Server
        1. Open SQL Server Management Studio.
        2. Connect the database instance.
        3. Start the database instance from the studio.
  5. Copy the Wizards directory in the IBM Connections installation media to the system that hosts the database server.
    Notes:
    • If you have more instances, exit from the current instance and repeat this step for each instance.
    • (AIX and Linux only) Ensure that users other than root have permission to access the IBM Connections Wizards directory.
    • (DB2 only) For more information about working with multiple instances, see the Setting the current instance environment variables topic in the DB2 information center.