This worksheet includes all of the installation panel settings. Use this worksheet to keep a record of your settings.
Setting | Description | My setting |
---|---|---|
Pipeline | Installs the component that performs name standardization, data quality management, address hygiene, and entity resolution. The pipeline also generates alerts, based on the system configurations. | (Default setting) |
Configuration Console | Installs the graphical user interface that you use to configure the system, monitor data and route messages, and view reports. | (Default setting) |
Visualizer | Installs the graphical user interface that analysts use to research alerts, view relationships, search for entities, load data, and run reports. | (Default setting) |
Documentation | Installs the IBM® InfoSphere™ Identity Insight information center displays product documentation in a Web browser. | (Default setting) |
Setting | Version supported | My setting |
---|---|---|
IBM DB2® Universal Database™ | Version 9.1 + FIX PACK 2, Version 9.5, or Version 9.7 | (Default setting) |
Microsoft® SQL Server - Version 2005 | Version 2005 (Microsoft Windows® installer only) | |
Microsoft SQL Server - Version 2008 or higher | Version 2008 or higher (Microsoft Windows installer only) | |
Oracle Standard Edition - Version 10g | Version 10.2.0.3 or higher patch level of 10.2.x.x | |
Oracle Standard Edition - Version 11g or higher | Version 11.1.0.7.0 or higher |
Setting | Description | My setting |
---|---|---|
Enable | Use system users for authentication. If selected, you must also refer to your database product documentation for instructions and enable trusted authentication for your database. | |
Disable | Do not use trusted authentication for the database type selected. | (Default setting) |
Setting | Description | JDBC location |
---|---|---|
IBM DB2 Universal Database | The location for the IBM DB2® client JDBC driver. | |
Microsoft SQL Server | The location for the Microsoft SQL Server JDBC driver. | |
Oracle Standard Edition | The location for the Oracle client jar file. |
Setting | Description | My setting |
---|---|---|
Database server hostname | The fully qualified hostname of the server or the IP address of the server hosting the entity database. | |
Database name (IBM DB2 UDB and Microsoft SQL Server) | The name of the entity database. | |
Database SID (Oracle databases only) | The Oracle system ID of the entity database. | |
Database schema (IBM DB2 databases only) | The name of the DB2 database schema. | |
Username | Administrator user name for this database. You
must provide a valid user name. Note: If using Oracle trusted/client
authentication, the OPS$ prefix is required
when entering the username. For example: OPS$johndoe.
Note: If
using Microsoft SQL Server trusted/client authentication, use the
database user (non-operating system) you created.
|
|
Password | Administrator database password for the user name provided for this database | |
Database port | The TCP/IP database port number. |
|
Setting | Description | My setting |
---|---|---|
Update tables automatically | Generates the SQL necessary to create the database schemas and tables necessary for your installation and executes it. | (Default setting) |
Generate SQL only. | Generates the SQL necessary to create the database schemas and tables necessary for your installation and writes it to .txt files (one per database) in the <installation_directory>/installer/logs/ directory. On Microsoft Windows: The ISQL Utility is not supported since it cannot handle large scripts. If manually populating a schema using the provided SQL scripts in a Microsoft SQL Server database, you must use the OSQL utility or the SQL Query Analyzer to execute the script. Using the ISQL utility results in a failure with an error message that reads "Insufficient memory to continue". Allowing the installer to generate and execute the SQL scripts will avoid this problem altogether. |
|
Skip database population |
Setting | Description | My setting |
---|---|---|
Number of errors which will cause the pipeline to shutdown | The number of errors which will cause the pipeline to shutdown | (Default setting is 10) |
Seconds to wait before resetting the pipelines error threshold limit | The seconds to wait before resetting the pipelines error threshold limit | (Default setting is 1440) |
Log all UMF exceptions | This setting logs all UMF exceptions. | |
Stop the pipeline on all UMF exceptions | This setting stops the pipeline on all UMF exceptions. |
Setting | Description | My setting |
---|---|---|
Enable Address Correction | Specifies that you have installed address correction software, and allows you to choose the supported address correction software product and server setting. | |
Pitney Bowes Universal Addressing Module | This radio button specifies that you are using Pitney Bowes Universal Addressing Module as your address correction software. | |
Address Correction hostname and port number | The fully qualified hostname of the server or the IP address of the server hosting the entity database and the port number of the address correction server. | |
Do you wish to override the state? | This setting allows the state to be replaced by the state code. | (Default setting if address correction is enabled) |
Setting | Description | My setting |
---|---|---|
Create pipeline input transports? | This checkbox signifies that you want to create pipeline transports. | (Default and un-deselectable checkbox if Visualizer is installed) |
http:// | The name of the server or the IP address of the server and the port number of the HTTP transport. HTTP transports transport the incoming records into a system node – typically, a pipeline and return a response back to the sending host.host:port | (Required if the Visualizer is installed) |
Create file transport? | This checkbox creates a file transport. File transports allow you to move data from a specific UMF formatted file into a system node – typically, a pipeline. | |
file:/ | absolutepath/to/filename.xml | |
Create database transport? | This checkbox creates a database transport. Database transports allow you to move data from a database to a system node – typically, a pipeline. | |
db2:// (DB2) |
username:password @database '?table=tablename ℴ=table &schema;=schema_name &timeout;=seconds' The schema value is for DB2 only. |
|
Create message queue transport? | This checkbox creates a message queue transport. Message queue transports allow you to send data from system queues to pipelines for processing. | |
Microsoft Message Queuing (MSMQ) transport | This radio button specifies that you are using Microsoft Message Queuing (MSMQ) as your message queuing software. This radio button will only appear during a Microsoft Windows installation, all other platforms only support IBM WebSphere® MQ transport. | |
IBM WebSphere MQ transport | This radio button specifies that you are using IBM WebSphere MQ as your message queuing software. This radio button will only appear during a Microsoft Windows installation, all other platforms only support IBM WebSphere MQ transport. | |
mq:/ |
The IBM WebSphere MQ transport URI. qname?manager=manager_name ?concurrency=n |
|
msmq:/ |
Microsoft Message Queuing (MSMQ) transport URI. This radio button will only appear during a Microsoft Windows installation, all other platforms only support IBM WebSphere MQ transport. qame?concurrency=n |
Setting | Description | My setting |
---|---|---|
SNMP Agent port | The port number of the SNMP agent. The SNMP agent is used to report statistics from the pipeline(s) back to the Configuration Console. | (Default 13516) |
File Authentication | This checkbox uses file authentication as the Configuration Console authentication method. This setting is mutually exclusive from SQL authentication. | (Default setting) |
SQL Authentication | This checkbox uses SQL authentication as the Configuration Console authentication method. This setting is mutually exclusive from file authentication. |
Setting | Description | My setting |
---|---|---|
Enable Application monitoring | This checkbox creates an application monitor that routes information to pipelines. |
Setting | Description | My setting |
---|---|---|
Fully Qualified Host Name | The fully qualified hostname of the server or the IP address of the server hosting the WebSphere Application Server. | (Default to server running installation program) |
Memory used during deployment (MB) | (Default 1024) | |
Web server port number (http) | (Default 13510) | |
Secure web server port number (https) | (Default 13511) | |
Administration port number | (Default 13512) | |
Secure administration port number | (Default 13513) | |
SOAP port number | (Default 13514) | |
Application server port number | (Default 13515) |
Setting | Description | My setting |
---|---|---|
Local Clients | Only local webservices clients' requests are accepted. | |
No webservices client restrictions | Any local or remote webservices clients requests are accepted. | (Default setting) |
Setting | Description | My Setting |
---|---|---|
Documentation port | The TCP port number to install the documentation information center on. | (Default 13517) |