U2 Datasource Mappings

From Informer 4 Wiki

Jump to: navigation, search

A datasource mapping represents a connection to any database on your network accessible from the web server. The following datasources are available as of the 4.0 release, with more coming in future maintenance releases.


Create a Unidata or Universe Datasource

  1. Click on the “Mappings” section.
  2. Click “Add Datasource”.
  3. In the dialog box, click "U2"
  4. Enter the connection properties:
    1. Name : This is the identifier of your datasource within Informer. It can contain any string of letters or numbers. For example “My Datasource”, “Database1”, and “Backup Account” are all acceptable.
    2. Description : This is the description of the datasource that will be displayed under the datasource name in the mappings section of Informer.
    3. Server Name : This is the host name, or IP Address of the machines that stores your datasource. The web server that runs Informer must be able to see this machine on your network.
    4. Account Path : This is the path on the database computer to the database you wish to connect to
    5. UniRPC Port : This is the port that your database system uses to be accessed from Java. The default port for Unidata and Universe is 31438.
    6. Username : This is the Username Informer uses to connect to your database. It is recommended that you use add a user named "informer" to connect, for diagnostic purposes.
    7. Password : The password associated with the username used to connect to your database.
    8. Pooled and non-pooled connections
      • If you do not have a U2 Connection pooling license. (Informer re-connects to your database on each query.)
        Connection Limit : This is the limit for the amount of database connection Informer may use simultaneously.
      • If you have a U2 Connection pooling license. This is obtained from Entrinsik, upon notice from us that you have purchased such a license from your database vendor. (Informer pools connections to your database for re-use on each query.)
      1. Minimum Pool Size : This is the minimum number of connections Informer should keep in the connection pool at all times. Default is 0. If this number is 1, for example, Informer will take a connection at startup and never let it go, thereby guaranteeing there will always be at least one connection available for Informer users.
      2. Maximum Pool Size : This is the maximum number of connections Informer is allowed to use at any one point in time. This has no direct correlation whatsoever to the number of Informer users logged into the system at one time, but may affect performance in some cases. Informer will not always maintain this number of connections, but is allowed to if necessary.
      3. Timeout : This is the amount of time an unused connection will remain in the connection pool before it is released. Default is 0 minutes. Having a value greater than 0 is particularly useful for enhancing performance, as there is some startup cost associated with creating a connection from scratch.
    9. Initialization Subroutines : If you need to Informer to run database programs to set up an environment, as is the case with SB+ and Datatel customers, you enter these here, in the order they should run.
    10. Database Date Format : This is the format your dates should be input and output when querying the database. This affects how date values are sent to the db query commands.


Preparing your datasource for System Builder (SB+)


You will need to install some subroutines on your database server for SB+ field to work properly. In order to do this, you will need to contact support@entrinsik.com for the referenced source .

  1. You will receive from Entrinsik 3 source files: SBPLUSINIT, SBSETUP, and DISPLAYSB. These will need to be copied or transcribed into a source folder in your database account.
  2. Edit SBPLUSINIT to use any SB+ user you want. Be sure that user has correct access. The ‘SB’ user will have the least risk of something not working. Be sure to add the password.
  3. Compile all 3 subroutines. “BASIC {source file} {subroutinename}”
  4. Catalog all three subroutines:
    • Universe
      “CATALOG {source file} SBSETUP LOCAL”
      “CATALOG {source file} SBPLUSINIT LOCAL”
      “CATALOG {source file} DISPLAYSB LOCAL”
    • Unidata
      “CATALOG {source file} SBSETUP DIRECT”
      “CATALOG {source file} SBPLUSINIT DIRECT”
      “CATALOG {source file} DISPLAYSB DIRECT”
  5. Add SBPLUSINIT to your list of Initialization subroutines in your U2 Datasource edit screen and save.


Preparing your datasource for Datatel


You will need to be able to edit a program inside your database and be able to compile and catalog it. This may require a different set of permissions than you have, so ask your IT department of it is ok. Assume for this example that your source file is "BP"

  1. Log into the informer account to a colon prompt as the informer user.
  2. Note the results of either of the following commands
    :!echo $DASP (Unix)
    :!ECHO %DASP% (Windows)
  3. AE VOC LOGIN in collegue and look for a call to SQLENVINIT. Copy all the parameters. The format will be like this:
    SQLENVINIT DMI:server_here:port_here,account_here
  4. AE BP INFORMERINIT
    0001: VAR = SETENV("DASU","informer_username")
    0002: VAR = SETENV("DASP","encrypted_password_from_step_2}")
    0003: EXECUTE "SQLENVINIT... (from step 3)"
  5. Compile the program using the "BASIC" command: BASIC BP INFORMERINIT
  6. Catalog the program using the "CATALOG" command with the "DIRECT" option: CATALOG BP INFORMERINIT DIRECT
  7. Enter "INFORMERINIT" in the initialization subroutines section of your Unidata datasource
Retrieved from "http://www.entrinsik.com/support/informer/40wiki/index.php/U2_Datasource_Mappings"
Personal tools