In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • Adding a Connection Pool
    You add new connection pools in the Connection Pool Manager by the type of user the pool is going to support. The options are UI API, JITSAPI, SIAPI, or FinAPI. You name each pool with the receiver name of the target QAD Enterprise Applications instance and identify the pool by host machine and port. You then create a startup script for the pool telnet session, and enter the pool parameters.
    When you create or modify a connection pool, it is created or modified in your connectionManagerConfig.xml file. The default version of this file is located in:
    TOMCAT_HOME/webapps/<QXI webapp>/WEB-INF/conf/defaults
    The server-specific version is stored one level up in the /conf directory.
    Warning The connectionManagerConfig.xml file should not be modified manually. Make changes only through the interface.
    Adding a UI API Pool
    1
    In the Connection Pool Manager, choose Add Connection Pool. The available user types display.

    Connection Pool Manager
    2
    Choose Add UIAPI Pool. The Configuration Settings Update form displays. Use the following field descriptions to create a connection pool configuration.

    Add a UI API Connection
    Pool Name
    The pool name must match the receiver name for QXI API pools. The pool name displays in the view and delete connection pool menus.
    Host
    Enter the machine name or IP address of the telnet server.
    Port
    Enter the port number for the telnet server.
    Server Startup Script
    Enter the startup script for the telnet session. Specify the telnet server log-in prompts and the responses to these prompts separated with the pipe symbol (|). The standard order is: loginPrompt|userid|passwordPrompt|$PASSWD|osPrompt| startScript. For example:
    login:|QXtend|Password:|password|$|exec ./qma.QXprod
    For Oracle implementations, the qma script must be modified.
    Server Startup Password
    Specify the password for the telnet session startup script (maximum 20 characters). The password is encrypted on entry. The startup script substitutes the encrypted password for the $PASSWD reference.
    Minimum Connections
    Enter the minimum number of open connections that the Connection Pool Manager should maintain. During startup, the Connection Pool Manager opens this number of connections. As connections are used, it continues to open more so that this number of open connections is maintained, until it reaches the value specified for Maximum Connections.
    In general, keep this number as low as effectively possible; for example, 3 on faster systems. On slower systems, increase the number to reduce startup time on new requests.
    Maximum Connections
    Enter the maximum number of open connections that the system should allow. The Connection Pool Manager will not open any more connections than this.
    Important: On Windows systems, this field must be set to 2 or more to ensure successful connections.
    Maximum Failures
    Enter how many times the Connection Pool Manager should attempt to restart an unsuccessful connection. This number is reset when a successful connection is made. You can also reset it by using the Reset Failed Init Count command on the Connection Pool Functions menu.
    Connections Monitor Frequency
    Enter, in milliseconds, the interval for checking all connections. The default value is 180000 (3 minutes). This monitors all connections in all states and closes those that have timed out.
    Wait Time for Idle Connection
    When a connection is requested from the Connection Pool Manager, this timeout specifies the maximum wait for the connection. The maximum number of connections may have been reached, or new connections may be in the initializing state. The default value is 20000 (20 seconds).
    Max Licensed Agent Retry
    Specify the number of times the system will attempt to reserve a licensed agent before returning an exception.
    Wait Time for Licensed Agent
    Specify the number of milliseconds that the system will wait for a licensed agent.
    See QAD QXtend Licensing for details on licensing.
    Connection Timeout
    Enter, in milliseconds, how long an HTML session can remain inactive before the Connection Pool Manager closes it. The default value is 1800000 (30 minutes).
    Processing Timeout
    Enter, in milliseconds, how long a connection can be in processing mode. Processing mode indicates a locked or busy screen. The default value is 3600000 (60 minutes). Connection Pool Manager closes locked or busy connections that exceed this.
    Message Timeout
    Enter the interval, in milliseconds, for Connection Pool Manager to wait for a general messaging reply from the telnet server. The default value is 10000 (10 seconds).
    Processing Message Timeout
    Enter the interval, in milliseconds, for Connection Pool Manager to wait for reply from the telnet server when a connection is in processing mode. The default value is 6666 (6.6 seconds).
    Initializing Timeout
    Enter the interval, in milliseconds, for Connection Pool Manager to wait for a telnet session to successfully initialize. The default value is 180000 (3 minutes).
    Stop on Pause
    For QXI, this should always be set to false. This prevents a transaction from failing when a “Press Spacebar” message is displayed in the target QAD Enterprise Applications session.
    Operating System Win32/NT
    Set this to true if the Progress telnet sessions are executing on a computer with a Windows operating system. Otherwise, set this to false.
    Progress Controller Program
    Enter mfww01b.p for UI API pools.
    NT Delay
    This can safely be ignored for QXI connection pools.
    Connection Setup User ID
    This and the next two entries are the parameters required to connect to the target QAD Enterprise Applications instance. Enter the valid QAD Enterprise Applications user ID, such as qxtend.
    Connection Setup Password
    Enter the password for the QAD Enterprise Applications user ID (maximum 20 characters). The password is encrypted on entry.
    Domain
    Enter the valid QAD Enterprise Applications domain if the target instance has domains implemented. Domains were introduced in QAD Enterprise Applications version 2.1.
    3
    On completion, choose Save. The new connection pool is started automatically and is added to the list of connection pools in the Connection Pool Manager interface.
    Adding a JITSAPI, SIAPI, or FinAPI Pool
    The JITSAPI, SIAPI, and FinAPI pools are slightly different than the XML-based pools for the UI API. You identify the Progress AppServer and the user ID and password for the AppServer. Several values covered for the UI API pools are not required for SIAPI pools. You must also enter a session type for Progress Dynamics for JITSAPI pools.
    1
    In the Connection Pool Manager, choose Add Connection Pool. The available connection pool types display beneath the Add Connection Pool selection.
    2
    Choose Add JITSAPI Pool or Add SIAPI Pool as needed. The Configuration Settings Update form displays. Use the following field descriptions to create a connection pool configuration.

    Add a SIAPI Pool
    Pool Name
    The pool name must match the receiver name for QXI API pools. The pool name displays in the view and delete connection pool menus.
    Debug
    If debug is set to Yes, debug information is written to the AppServer log file. If set to No, no AppServer logging occurs.
    App Server Name
    Enter the name given to the AppServer in the ubroker.properties file. This is configurable and is done by the user when creating the AppServer settings. See Configuring the Progress AppServer.
    Host
    Enter the machine name or IP address of the machine where the Progress AppServer is installed and running.
    App Server Direct Connect
    Specify whether you want QXtend Inbound to directly connect to the AppServer.
    Yes: QXtend directly connects to the App Server using the port number you provide in the Port field for the AppServer.
    No: QXtend first uses the port number you supply in the Port field to connect to the NameServer, which then assigns the AppServer to the connection.
    Port
    Enter the port number for the AppServer or the NameServer, depending on your App Server Direct Connect setting. If you selected the App Server Direct Connect option, enter the port number for the AppServer; otherwise, enter the port number for the NameServer that is controlling the AppServer instance. In that case, the connection is requested from the NameServer and it assigns the AppServer to the connection.
    State Free
    Specify in which operating mode the connection pool can connect to AppServer.
    Yes: The connection pool can only connect to AppServer when operatingMode is State-free.
    No: The connection pool can only connect to AppServer when operatingMode is Stateless.
    User
    Enter the QAD Enterprise Applications user name.
    Password
    This is the QAD Enterprise Applications user’s password, encrypted on entry.
    Domain
    For a SIAPI pool, enter the valid QAD Enterprise Applications domain if the target instance has domains implemented. This field does not apply to JITSAPI pools.
    Session Type
    This value displays only in the QAD JIT Sequencing API connection pool configuration. See Installation Guide: QAD JIT Sequencing for details. Set it to dynamics session type to enable a Progress Dynamics session.
    Minimum Connections
    Enter the minimum number of open connections that the Connection Pool Manager should maintain. During startup, the Connection Pool Manager opens this number of connections. As connections are used, it continues to open more so that this number of open connections is maintained, until it reaches the value specified for Maximum Connections.
    In general, keep this number as low as effectively possible; for example, 3 on faster systems. On slower systems, increase the number to reduce startup time on new requests.
    Maximum Connections
    Enter the maximum number of open connections that the system should allow. The Connection Pool Manager will not open any more connections than this.
    Maximum Failures
    Enter how many times the Connection Pool Manager should attempt to start a connection. This number is reset when a successful connection is made. You can also reset it by using the Reset Failed Init Count command on the Connection Pool Function menu.
    Connections Monitor Frequency
    Enter, in milliseconds, the interval for checking all connections. The default value is 180000 (3 minutes). This monitors all connections in all states and closes those that have timed out.
    Maximum Connection Idle Time
    Enter, in milliseconds, the maximum time a 4GL connection can remain idle.
    Maximum Connection Init Time
    Enter, in milliseconds, the maximum time a 4GL connection can be initializing.
    Wait Time for Idle Connection
    Enter, in milliseconds, how long the Connection Pool Manager should wait for an initializing connection to become idle before an error is generated. The default value is 20000 (20 seconds).
    3
    On completion, choose Save. The new connection pool is started automatically and is added to the list of connection pools in the Connection Pool Manager interface.