Using configdadb to Configure a Data Area for Database Access

Use configdadb in its GUI mode to configure the database access for a data area.

To configure a data area for database access (GUI mode)

  1. At the Landmark command line, type

    configdadb -g dataarea

  2. On the Infor Interview form for configuring database access, specify the following items:
    Value Description
    The database server configuration to use for the data area.

    Specify a named database access configuration or specify None. If you specify None, you will then need to specify the additional values below.

    For more information about defining a database access configuration, see Creating Named Database Access Configurations.

    Note: 

    This prompt or field only appears if you have already defined at least one database access configuration through the configdatabase utility.

    The database to use for this data area. Choose the number from the list presented by the interview that represents the database you will use, or if in GUI mode, select the database from the drop-down list.
    Are you connecting to an availability group listener of a SQL Server availability group or a SQL Server Failover Cluster Instance? This applies only to SQL Server 2012 and higher. If yes, do not specify an InstanceName, but rather the availability group listener of the availability group as the SQL Server.
    The name of the SQL Server server to use.
    The port number of the remote SQL Server database. If the SQL instance is configured to use dynamic ports, use 0 for the port. Otherwise specify the correct static port.
    The name of the database on the server.
    Do you want to use unicode support?
    The name of the full text index for the database on the server.
    The user ID to use when connecting to SQL Server. A user defined in the SQL Server database.
    The password for the user. The password for the SQL Server user.
    Do you want to specify filegroups for tables and indexes? If you choose to use filegroups, you will need to provide the names of the filegroups to use for tables, indexes, and large objects.
    The prefix to use to build schema names The schema name will be created by concatenating the prefix with an underscore and then the data area name. The resulting schema name cannot exceed 18 characters in length and must start with a letter.
    Value Description
    The database server configuration to use for the data area.

    Specify a named database access configuration or specify None. If you specify None, you will then need to specify the additional values below.

    For more information about defining a database access configuration, see the "configdatabase" topic in the Landmark System Utilities Reference Guide.

    Note: 

    This prompt or field only appears if you have already defined at least one database access configuration through the configdatabase utility.

    The database to use for this data area. Choose the number from the list presented by the interview that represents the database you will use, or if in GUI mode, select the database from the drop-down list.
    The Oracle protocol for the server connection. TCP or TNS. You can select TNS if you have a TNS file configured. Otherwise, you will need to specify the host and port of the database server.
    The full path for the Oracle home directory. If your Oracle protocol is TNS, specify this path.
    The TNS name for the Oracle server. If your Oracle protocol is TNS, specify the TNS name.
    The host name of the remote Oracle database. If your Oracle protocol is TCP, specify the host for the database.
    The port number of the remote Oracle database If your Oracle protocol is TCP, specify the port for the database.
    The SID (Service_Name) for the Oracle database. If your Oracle protocol is TCP, specify the SID for the database. You can find this by looking in the tnsnames.ora file or by running the lsnrctl status command, and then finding the service for the database that the listener is listening for.
    Do you want to use unicode support?
    The name of the table space to use when creating tables. This must already exist and be defined as locally managed.
    The name of the table space to use when creating indexes. This must already exist and be defined as locally managed.
    The name of the table space to use for large objects. This must already exist and be defined as locally managed.
    The Oracle user ID to use when connecting to the database. This existing user will become the owner of the tables created during for the data area. The user name is used to keep the data for this data set separate from any other data stored in the database. All tables will be created with this name as the table owner. You must use a unique user name for each data area.
    The password for the Oracle user ID.
  3. Click Finish when you are ready to configure the database access for the data area.