Setting up application servers to run investigation, SQA, or Match Statistics reports

The investigation, Standardization Quality Assessment (SQA), and Match Statistics reports can read data from a sequential file or a database table. You must set up the application server to find the applicable data source.

Procedure

  1. If the stage writes the report data to a sequential file, perform the action that corresponds to the topology of your installation.
    Topology Action
    IBM® InfoSphere® Information Server engine and the services tier are on the same computer.

    No additional steps are necessary.

    InfoSphere Information Server engine and the services tier are on different computers.
    The sequential file exists only on the engine. Because the reports run on the application server, perform one of the following steps:
    • Create a network shared directory that both the engine and application server can access.
    • Copy the sequential file from the engine tier computer to the local file system of the services tier. Ensure that the file paths are identical on both the engine tier computer and the services tier computer.
  2. If the stage writes the report data to a database table, perform the action that corresponds to the topology and operating system of your installation.
    Topology and operating system Action
    • All operating systems
    • InfoSphere Information Server engine and the services tier are on different computers
    Because the necessary ODBC drivers are not installed on the application server, perform the following steps:
    1. Set up the JDBC data source on the application server.
    2. Ensure that the JNDI name is the same as the ODBC DSN on the engine.
    • AIX® Solaris
    • InfoSphere Information Server engine and the services tier are on the same computer
    Because the ODBC DSN is not visible to the engine as the system DSN, perform the following steps:
    1. Set up the Java™ Database Connectivity (JDBC) data source on the application server.
    2. Ensure that the Java Naming and Directory Interface (JNDI) name is the same as the ODBC DSN on the engine.
    • Linux®
    • InfoSphere Information Server engine and the services tier are on the same computer
    Because the ODBC DSN is not visible to the engine as the system DSN, perform the following steps:
    1. Set up the Java Database Connectivity (JDBC) data source on the application server.
    2. Ensure that the Java Naming and Directory Interface (JNDI) name is the same as the ODBC DSN on the engine.
    • Microsoft Windows
    • InfoSphere Information Server engine and the services tier are on the same computer

    No additional steps are necessary.

    The reports run on the application server. They can find the database table by using the Open Database Connectivity (ODBC) data source name (DSN) that was set up on the engine.