- Publishing data into inmydata from a Progress / Openedge / PAS relies on setting up a Connection from the System Screen when configuring a data source.
The Connection Details screen (pictured below) allows you to define the connection details for a single Progress AppServer connection.
Select the General tab to enter General Progress Connection Details.
Select the Advanced tab to enter Advanced Progress Connection Details.
Select the Tuning tab to enter Tuning Progress Connection Details.
Enter the connection details, then press OK to save your changes.
Progress Connection Details - General
There are three types of Progress connection you can configure. The connection types are listed below with their description. See below for more details on how to configure each connection type. Connection Type | Description | OpenEdge AppServer | A direct connection to an OpenEdge AppServer, either through a NameServer or direct to the AppServer broker. Ideal where the AppServer is located on the same local area network (LAN) as the client. | Pacific AppServer | A remote connection to a Pacific AppServer. Ideal where the database or databases are located on a public wide area network (WAN) such as the Internet |
OpenEdge AppServer Connections To configure an OpenEdge AppServer connection, enter the name by which this connection will appear in the Data Definition Query Select Subject screen, for the connection you are creating or editing, then select OpenEdge AppServer from the connection type, then enter the appropriate connection Details (detailed below). 
Connection Property | Description | Host | Enter the network name or the IP Address of the machine hosting the Appserver. | Service | Enter the Service Name or Port Number of the Name Sever. If you leave this blank, the default Port umber (5162) will be assumed. If you opt to connect directly to the Appserver rather than through the Name Server, by clicking in the 'Connect Directly To Appserver' check box, you must specify either the Service Name or the Port Number of the Appserver. | Application Service | Enter the Name of the Application Service to connect to. | State free AppServer | Select if you are configuring a connection to an OpenEdge 10 state free appserver (see Progress AppServer Internet Adaptor). | Connect directly to AppServer | Select if you want to connect directly to the AppServer rather than via a NameServer. |
If the Test Server Connection On Finish caption is checked when you exit the screen, the connection will be checked before the screen exits. | Pacific AppServer
If you wish to connect to an OpenEdge database over the internet, you may wish to connect via a Pacific AppServer. To configure a Pacific AppServer connection, enter the name by which this connection will appear in the Data Definition Query Subject Screen screen for the connection you are creating or editing, then select Pacific AppServer from the connection type, then enter the appropriate connection Details (detailed below).
Connection Property | Description | AppServer URL | Enter the string which identifies the location of the Pacific AppServer. The URL should not include usernames, passwords or http protocol identifiers or session model variables | Session Model | Select whether you require a session free or session managed connection. Unless you have a specific reason to require session managed, we would always recommend session free as it will make best uses of the resources on your server. | Use SSL | Select if you wish DataPA to connect to the web server hosting the AIA using SSL encryption |
If the Test Server Connection On Finish caption is checked when you exit the screen, the connection will be checked before the screen exits. |
|
Progress Connection Details - Advanced
As well as passing the Connection Parameters which locate the Appserver, when connecting you can also pass userid, password and appserver-info arguments to the Appserver. These are then passed to the Connect procedure (if defined). If there is no Connect procedure the arguments are discarded. 
If you wish to pass appserver-info on connection, type the information that needs to be passed in the 'Appserver Information' text box. If you wish to pass userid and password arguments to the Appserver, click on the 'Prompt User For Password' check box and a Username and Password dialogue box will prompt you whenever DataPA makes a connection to the Appserver. If you wish this particular connection to always be used for administration tasks (for example importing/building links, lookups, subjects etc) select the Always use this connection for administration checkbox. If you wish to Enable tracing of the OpenClient connection, click on the 'Enable Tracing' checkbox, select the 'Logging Level' that you require and enter a 'Log File Name' or use the browse button to choose the location for your Log File. |
Progress Connection Details - Tuning
To configure the tuning options available for the connection you can edit the properties available on the Tuning tab. 
TCP Settings By default the connection between DataPA and the AppServer will timeout after 41 minutes. This can sometimes be a problem if you want to run a query that takes longer than 41 minutes. If you do then you can change the TCP settings on the connection and control how long it takes for the connection to time out. This timeout is controlled by two settings which you can set on the Tuning tab. Property | Description | TCP Client Retry | This property sets the number of times that DataPA should check with the AppServer to see if the request is complete before giving up and terminating the connection to the AppServer. | TCP Client Retry Interval | The amount of time in hundredths of a second that DataPA should wait between checks with the AppServer to see if the request is complete. |
By default the TCP Client Retry is set to 1000 and the TCP Client Retry Interval is set to 250. This calculates as 1000 x 250 = 250,000 hundredths of a second = 2,500 seconds = 41 minutes and 40 seconds. Compression Settings By default the connection between DataPA and the AppServer will pass data in an uncompressed form. If you are running over a slow network then it may be worth using the compression options available on the Tuning tab to enable compression. Enabling compression will reduce the amount of data being sent between the AppServer and DataPA but the compressing and decompressing process on either end will take a little time. Therefore therefore is a trade off to be considered when deciding whether or not to use compression. There are 3 settings available on the Tuning tab which will enable you to set the optimal compression options for your connection. Property | Description | Enable Compression | This property allows you to choose whether to use compression between DataPA and the AppServer for this connection. | Compression Threshold | This property allows you to control the dataset size threshold at that you want to start using compression at. This allows you to not use it for smaller datasets that may not benefit much from compression. The Use Compression for All Datasets end of the slider means that almost all messages will be compressed from messages of size 256 bytes and above. The Use Compression for Only Big Datasets is at the other end of the scale and allows you to specify that compression should only be used for datasets of 32K and above. You can also use the slider to choose a range of values in between these two extremes. | Compression Level | This property allows you to control the level of compression used. The higher the level selected on the slider the more compressed the datasets will be, meaning that they are smaller. The more compression you use the longer it will take to compress and decompress the messages. In general the slower your network connection is, the more you will benefit from higher compression. |
By default compression is not enabled and when it is the Compression Threshold default to 256 bytes and the Compression Level default to Low Compression. |
AppServer Details
The AppServer Detail screen gathers data from the Connection's Appserver. The screen show the DataPA Server Version and two Tabs, one containing general information, the other more detailed. |
|
The 'DataPA Server Version' is the version of the DataPA Server that is running. The 'Appserver PL Version' is the version of the Procedure Library running on the Appserver. This should match the 'DataPA Server Version'. If there is a mismatch DataPA may experience errors when requesting data from the AppServer. On the General Tab the following pieces of information are displayed:- - The 'Hostname of the connection
- The Filename and location of the Procedure Library
- The Filename and location of the Appserver Logfiles
These pieces of information can be useful when diagnosing AppServer related issues. |
|
The Advanced Tab lists the Appserver Properties for more advanced users. |
