Installing a domain server using the installation wizard

Follow these steps to install a domain server using the installation wizard. You can use a domain server in a stand-alone domain server deployment, or as part of a synchronization server deployment.

Note: The synchronization server deployment type is obsolete. In a new TADDM deployment where more than one server is needed, use the streaming server deployment.

You must be logged in to an account with administrator privileges to install the TADDM server. Complete all prerequisite steps, including any required database configuration, before starting the installation process.

If you are installing the TADDM server on a supported Microsoft Windows Server, you must temporarily turn off User Account Control (UAC) before starting the installation process. You must restart the system each time you modify this option. For more information on Windows Server 2012 see http://social.technet.microsoft.com/wiki/contents/articles/13953.windows-server-2012-deactivating-uac.aspx.

There are two basic types of domain server installation:
  • Simple installation installs the domain server with default options, using a local DB2® database (which you can optionally install during the server installation). This type of installation is suitable for testing but is not intended for production environments.
  • Advanced installation installs the domain server using a remote DB2, DB2 for z/OS®, or Oracle database, and with installation options that you can customize for your environment. Use advanced installation for production environments.
The installation wizard prompts you to select either simple or advanced installation. If you select simple installation, some steps in the installation procedure do not apply.
Notes
  • If you are installing on a dual-stack system that supports both the IPv4 and IPv6 protocols, make sure any numeric IP addresses you specify during the installation process are IPv4 addresses.
  • For Oracle RAC database, you can only select Advanced installation. TADDM installer does not support RAC configuration directly. You can only install TADDM with one RAC node configuration, and then update JDBC connection string in the collation.properties file after the installation. See Configuring Oracle RAC after installation.

To install the domain server using the installation wizard:

  1. Insert the TADDM Disc 1 installation DVD for your supported operating system into the DVD drive. If you downloaded TADDM in the zip format, the zip files number 1 and 2 are the equivalent of Disc 1.
  2. At a command prompt, go to the DVD drive, or to the directory where you saved the zip files, and run the appropriate command for your operating system:
    • For AIX® operating systems, setupAix.bin
    • For Linux® operating systems, setupLinux.bin
    • For Linux on System z® operating systems, setupZLinux.bin
    • For Windows operating systems, setupWin.bat
    Restriction: When you run the TADDM installation wizard setupWin.bat on Windows operating systems, select the Run as administrator option. Otherwise, the installation will fail.
    Note: If an error message is displayed that there is insufficient disk space in the temp directory, run the installation again and specify a different temp directory. Use the option -t temp (for example, setupLinux.bin -t /mytempdir).
  3. Select the language to use for your installation. Click OK.
  4. On the Introduction page, click Next.
  5. Read and accept the terms of the software license agreement and click Next.
  6. Specify the location where you want to install the server.
    Make sure that the path you specify contains only ASCII characters, and does not contain any spaces. Non-ASCII characters or spaces in the path can cause installation problems and problems starting the server.

    After you specify the server location, click Next.

  7. Specify the user ID you want to use to run the server.
    • On Windows operating systems, the user must belong to the Administrators group. If the user does not exist or is not part of the Administrators group, select the check box to create the user or add the user to the Administrators group. The user ID must be a local user account.
    • On Linux and UNIX operating systems, the user ID you specify must be non-root.

    After you have specified the user ID, click Next.

    Note: If the user ID you are using to run the installer is not an administrator or root, this page is not displayed.
  8. On the IBM® Tivoli Application Dependency Discovery Manager Deployment Option page, select Domain server deployment.
    Click Next.
  9. Select the installation type (Simple or Advanced):
    • To install the server with default options and a local DB2 database, select Simple. This type of installation is suitable for testing but is not intended for production environments.
      If the DB2 database software is not already installed on your system, you can optionally select Install DB2 database on the system to include the DB2 software as part of a simple installation.
      Note: Make sure that the password that you choose for the DB2 user complies with the DB2 and operating system requirements. TADDM installer does not verify the password and if the password does not comply with the requirements, DB2 installation fails.

      On Linux and UNIX operating systems, DB2 is installed in /opt/ibm/db2/10.1 and the DB2 instance is installed in /home/db2inst1.

      On Windows operating systems, DB2 and the DB2 instance are installed in Program_files\IBM\SQLLIB

      Ensure that there is enough disk space available at these locations. The disk space used by the instance will increase with use. For more information about the amount of disk space required for a typical installation, see Database server hardware requirements.

      The default installation locations cannot be changed when installing DB2 as part of a simple installation. If sufficient disk space is not available, you must either install DB2 manually on the local sever, or use a remote DB2 instance installed on another computer.

    • To install the server for a production environment with a remote DB2, DB2 for z/OS, or Oracle database, select Advanced. With advanced installation, you can customize the installation options.
    After you select the installation type, click Next.
    Note: If you chose a simple installation, configure Registry Services connection as described in 10. e. and skip to step 11.
  10. Specify advanced server options and the database type:
    1. On the General network connection settings page, specify the required settings. Click Next.
    2. On the Public ports on server page, specify the required port information. Click Next.
    3. On the Inter-server communication ports page, specify the required port information. Click Next.
    4. On the Additional Server Information page, specify the following options:
      • The platform binaries to install. If you configure the binaries later, the binaries are pushed to the remote gateway or anchor. If you are not sure which platform binaries you want to install, select All.
      • Server startup options.
      Click Next.
    5. On the Registry Services connection information page, specify the Registry Services Connection URL and the user information. You can also choose data providers. Click Next. If you do not want to configure Registry Services connection, clear the Configure Registry Services connection check box.
    6. Select the database type (DB2, DB2 z/OS, or Oracle). Click Next.
    7. If you are using an Oracle database, specify the path to a directory that contains the Oracle JDBC driver and two other Oracle jars that support XML operations, ojdbc6.jar, xdb6.jar, and xmlparserv2.jar. Click Next.
      Verify that the version of all the files that you are using is the same as the version of the Oracle server.
      Important: If you use Oracle 11.2.0.3, or 11.2.0.4, the jars must be in version 11.2.0.4. If you use Oracle 12, the jars must be in version 12. You must place the jar files in the dist/lib/jdbc directory on your TADDM server. You can download them from the Oracle website, or copy them from the Oracle server, not Oracle client, from the following locations:
      • ../app/oracle/product/Oracle_version/dbhome/jdbc/lib/ojdbc6.jar
      • ../app/oracle/product/Oracle_version/dbhome/rdbms/jlib/xdb6.jar
      • ../app/oracle/product/Oracle_version/dbhome/xdk/lib/xmlparserv2.jar on Oracle 11g, or ../app/oracle/product/Oracle_version/dbhome/lib/xmlparserv2.jar on Oracle 12c
      Oracle provides various copies of the xmlparserv2.jar file, therefore, you must copy it from the preceding location, not from another one. For more information, contact your database administrator.
      Note: Fix Pack
4If you use Oracle 12 (version 12.2.0.1), after completion of TADDM installation, the jars- ojdbc6.jar, xdb6.jar and xmlparserv2.jar at the path dist/lib/jdbc must be replaced with jars ojdbc7.jar, xdb6.jar and xmlparserv2.jar. These jars can be copied from the path : ../app/oracle/product/Oracle_version/dbhome/sqldeveloper/sqlcl/lib.
  11. On the Database Information page, specify the TCP/IP host name or numeric IP address, listening port, database name, and user information for the database.
    If you are using the simple installation process with an existing local installation of DB2, select Create the database during install unless the required TADDM database and tables already exist.

    Click Next.

    Note: If you are using the simple installation process, skip to step 17 after you complete this step.

    See Configuring the remote database server for information about user account requirements.

  12. Optional: If you want to configure the Context Menu Service and Data Integration Service during the installation process, select the Configure Context Menu Service (CMS) / Data Integration Service (DIS) check box.
    (If you do not select this option during the installation process, you can manually configure the Context Menu Service and Data Integration Service after installing. For more information, see Configuring for the Context Menu Service and Data Integration Service.)

    If you are not configuring the Context Menu Service and Data Integration Service, skip to 14.

  13. Optional: If you are configuring the Context Menu Service and Data Integration Service, specify the required database information.
    Note: To avoid delays in registering configuration items in the database, install the CMS/DIS database on a server that is geographically close to the TADDM database server.
    If you are using a DB2 database, follow these steps:
    1. Specify the database server, port, database name, and user information for the database.
      The database name must be different from the TADDM database name.
    2. Select Create the database during install unless the required database and tables already exist.
      (If you select Create the database during install and the database already exists, the installer deletes the existing database and creates the new one.)
      Note: The Create the database during install check box is available only if the DB2 database is on the local system and the user ID running the installation process has root or administrator privileges.

      Click Next.

    If you are using an Oracle database, follow these steps:
    1. Specify the database server, port, system ID, and Oracle user information for the database.
      The Oracle user for the Context Menu Service and Data Integration Service must be different from the Oracle user for the domain server.
    2. Select Create the user during install unless the required user already exists.
      (If you select Create the user during install and the user already exists, the installer deletes the existing user and creates the new one.)
      Note: The Create the user during install check box is available only if the user ID running the installation process has root or administrator privileges.
      Click Next.
    3. If you selected the Create the user check box, specify the Oracle database administrator information and the Oracle home directory.
      This information is used to create the Context Menu Service and Data Integration Service Oracle user during the installation process.

      Click Next.

  14. Select the user registry option:
    • To use a file-based registry, select File-based user registry. No additional configuration information is required for this option.
    • To use a Lightweight Directory Access Protocol (LDAP) user registry, select LDAP user registry.
    • To use a WebSphere® Federated Repositories registry, select WebSphere Federated Repositories.
    Click Next.
  15. If you selected an LDAP user registry, additional pages prompt you for LDAP server and configuration information:
    1. Specify the LDAP server and user information. Click Next.
    2. Specify the LDAP configuration parameters (or accept the defaults values). Click Next.
  16. If you selected a WebSphere Federated Repositories registry, specify the WebSphere Federated Repositories server and user information.
    Note: User IDs and passwords are case sensitive. Make sure you use the correct case.
    Click Next.
  17. Review the pre-installation summary. After you verify that the information is correct, click Next to start the installation process.
  18. If you are installing the DB2 software as part of a simple installation, follow the instructions to install DB2:
    Important: If you are installing a Linux, or AIX system, make sure you navigate to the root directory and unmount the optical drive before changing disks.
    1. Insert TADDM Disc 2, or specify the DB2 installation image directory. If you downloaded TADDM in the zip format, the zip files number 3 and 4 are the equivalent of Disc 2. Click Next.
    2. Insert TADDM Disc 1 (zip files number 1 and 2), or specify image directory. Click Next.
  19. When prompted, insert TADDM Disc 3 into the DVD drive. Specify the image directory. If you downloaded the zip files, specify the path to the zip file number 5. Click Next.
    Fix Pack
6Note: TADDM Disc 3 is the unzipped path to TADDM 7.3.0.1 which is available on fix central, see https://www-945.ibm.com/support/fixcentral.
  20. After the installation finishes, click Done to close the installation wizard.
This installation can be a lengthy process, depending on the number and type of components you are installing. While the installation process is running, you can monitor progress by viewing changes to the installation log. The log also contains information that can help you troubleshoot problems that occur during installation. Log files can be found in the installLogs subdirectory of the installation directory.

On a supported Microsoft Windows Server, remember to turn User Account Control (UAC) on after you have finished the installation, and to restart your system. For more information on Windows Server 2012 see http://social.technet.microsoft.com/wiki/contents/articles/13953.windows-server-2012-deactivating-uac.aspx.