Application Server Setup
To modify the connection settings for the IndySoft Application Server, goto your 'IndySoft Application Server' program group, and launch the 'Application Server Setup' icon. The following screen will appear.
Application Server Setup Dialog
If the IndyIOAppServer service has not been installed on your workstation, then you will see the button in the upper left with a caption of 'Install Service'. Otherwise, the button will display 'Uninstall Service'. This button will simply register/de-register the IndyIOAppServer in Windows Service Manager. Note: the IndyIOAppServer service is typically installed into Service Manager automatically by the IndySoft Application Server install.
To the right of this button you will see a drop down showing any past connection settings that you have saved for quick recall:
Once you have configured your database connection (settings below), you can press the 'Save Configuration' button to give your configuration a name. This name will become available in the drop down for future recall. Press the 'Delete Configuration' button to remove a previously saved configuration from the drop down. This drop down is handy for installations where you have a test database and a production database - both connections could be listed for fast switching.
2 options are available: 'TCP/IP' or 'UDP'. The 'TCP/IP' option is the default, and it is highly recommended. 'UDP' is a very fast protocol, but since it omits any error checking, it is not practical for most network implementations.
•# Initial Sessions - This option will allow you to specify how many sessions the server should make upon startup.
•Max # of Session - This options allows you to specify a "ceiling" of how many connections will be made to the database. As connections are needed the application server will continue to make more and more connections -- sharing the connections in a "pool" on an as needed basis. If this ceiling is reached, users will have to wait for an available pooled connections -- as opposed to the application server spawning a new database connection. We recommend setting this # to twice the amount of user using the system on a normal basis.
•Use Compression - This option will allow you to specify if your clients will be using compressed data. Under normal circumstances, this should be left unchecked. If checked, you will need to make sure each IndySoft Client application also has the appropriate compression box checked in workstation setup.
•Persistent Sessions - This option will keep a connection per user, until the user logs out. Use this feature only when asked to by IndySoft tech support.
•Shrink Back To...Sessions Every...Minutes - These 3 settings work together to create a clean-up interval that occurs when the application server is running. When the interval triggers there are 3 actions that will occur.
1.The list of active applications in the AppServerLog.exe utility will be validated. Any applications that are not still connected to the application server will be removed. It is uncommon that applications would be 'stuck' in this listing - but this validation should clean-up any applications that remain in the listing from abnormal conditions.
2.Each application server session will be tested to insure it still has a connection to the database and sql can be successfully executed. Any session that fails this test will be automatically removed. This check is to help proactively close any sessions that have become invalid - in the hope that this temporary condition (maybe a network issue between database and server) is fixed shortly. If so, the next time the application server needs to open a fresh connection to replace this one it will be able to do so successfully.
3.Finally, the application server will make an attempt to reduce the # of active sessions back down to the # specified here. Typically this # will be the same as the '# Initial Sessions'. Note that only inactive sessions can be freed - so reducing the # of sessions during peak activity might not be possible. This scheduled shrink operation is meant to keep the # of database connections at a reasonable amount - so peak usage times do not leave a permanent effect on resource usage on the application server evidenced by a large # of database sessions. The default value is to perform the shrink and other clean-up operations every 60 minutes, shrinking down to the # of initial database sessions.
•Port Used - This option specifies the TCP/IP port used when clients connect to the server. IndySoft client applications must use this same port when connecting to the Application Server.
•Authentication - Select either 'Windows Authentication' or 'Server Authentication'. If Windows Authentication is used then the User Name and Password below will not be relevant.
•User Name - This option specifies the user name to use when logging into the database. (For Firebird DB's - the default is an uppercase "SYSDBA" -- leave this default under almost all circumstances)
•Password - This option specifies the password for the user name specified above. (For Firebird DB's - the default is a lower case "masterkey" -- leave this default under almost all circumstances)
MSSQL Database Info (only visible if 'MSSQL' is selected for 'Database Type')
This option is used to specify database parameters.
•Server - This option specifies the Server to connect to.
•Database - This field is required in order to connect and is used to specify the MSSQL Identifier for your database.
Oracle Database Info (only visible if 'Oracle' is selected for 'Database Type')
This option is used to specify database parameters.
•Date Format SQL - This option specifies the Oracle Connection string for formatting dates. Leave this option as-is unless directed to change by IndySoft tech support.
•Database - This field is required in order to connect and is used to specify the Oracle Identifier for your database.
•Host IP - the IP Address of the host computer. If the oracle database is installed on the same computer as the applicaton server, this address would be '127.0.0.1'.
•Oracle Port - port for Oracle communications, default is 1521.
•Home Name - Use this setting to select which Oracle client will be used in your application. Use this property only in cases when there is a number of Oracle clients on the machine. When 'OCI' is selected for 'Connection Type', IndySoft searches all available homes in HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE registry folder. If HomeName property is set to '', IndySoft uses the first directory from the list of homes encountered in environment PATH variable as default Oracle home.
•Connection Type - a 'Native' connection connects the application server directly to the Oracle database, without requiring an installation of Oracle client on the application server workstation. An 'OCI' connection type connects through oci.dll, which is installed with the Oracle client. 'Native' connection is the default.
To test the database connection based on the settings input use the 'Test Connect' button available from the 'Database Type' panel. If the IndyIOAppServer is currently started in Windows, you will see:
The stop button can be used to quickly stop the service (without having to launch Windows Service Manager). If the IndyIOAppServer is currently NOT started, you will see: Please wait at least a couple seconds after stopping the service before restarting - to insure that all database connections have been closed and the application is loaded out of memory.
Press the start button to quickly launch the service (without having to launch Windows Service Manager). If a connection fails to the database, a dialog will appear showing the connection error message.
Press 'OK' after reviewing all settings.
Right mouse click the URL below for copy and bookmark options available with your browser.