The transmit configuration defines how the Agentry client communicates with the server. It can define which application-level data definitions to synchronize, whether to log out a user from the server when a transmit has completed, or to keep the connection to provide real-time communication functionality.
- The actions to take, if any, in the event of a communications error.
- Whether data tables and complex tables are synchronized.
- Whether the client remains logged in for real-time communication.
- How the application behaves if using a modem, what to do if not currently connected, and when to close the connection.
Define a transmit configuration for all available communications methods on the client device. For example, if a wireless LAN connection is available to client devices in the deployment, define a transmit configuration for this connection. If a wireless WAN connection is also available, also define a transmit configuration for this connection.
- In the application project, create a text file called TransmitConfigurations.ini.
- Modify the file to include a section for each transmit configuration to override called [<TransmitConfigurationName>], and any override attributes. Include the file when you publish the project for production. See Publishing to Production in Developer > Agentry App Development.
- In Management Cockpit, import the project ZIP file on the server.
- In Management Cockpit, select the application and navigate to App Specific Settings. Under Configuration, make sure the Transmit Configuration File setting points to this file location.
- Restart the application on each server to initiate the changes.
For a production workflow, coordinate Management Cockpit activities with the Administrator.
- Make changes to the TransmitConfigurations.ini file in the development environment, not on SAP Mobile Platform Server, and publish a new ZIP file in Management Cockpit. Do not modify the file on the server, or it is overwritten when you upgrade the server.
- Restart each server in a cluster to distribute the changes.
Within the TransmitConfigurations.ini file, there is one section for each transmit configuration defined within the application, denoted as [<TransmitConfigurationName>], where <TransmitConfigurationName> is the name of the definition within the application project. Each section can contain override values for any and all attributes within a given transmit configuration definition.
[<TransmitConfigurationName>] stayLoggedIn=true retryPeriod=30 retryAttempts=5 onlineRetryAttempts=5 serverInactiveTimeoutOverride=300
All other attributes within the transmit configuration definition can be overridden using the proper key and value pair. Any attributes not overridden within this file are sent to Agentry Clients as defined in the application project.
When using this override file for multiple Agentry applications, each server should have its own version of this file that includes the required configuration settings that are unique to that server instance.
Transmit Configuration Attributes
For additional information about the definition attributes, see Configuring the Transmit Configuration File for Agentry Applications in Administrator > Application Administration .
|Name||The unique name of the transmit configuration. This value must be unique for all transmit configurations defined for the application.|
|Display Name||Each transmit configuration defined in the application is listed in the Transmit Dialog on the Agentry application, so choose an appropriate Display Name that is clear to the application end user.|
|Connect Type||WebSockets over HTTPS, which is the communications protocol used when synchronizing with SAP Mobile Platform Server.|
|Group||The group into which the transmit configuration is organized within the application. The default options are Fast and Slow, or you can create a new group by entering a name in this field. It is then available to select for all transmit configurations within the same application project.|
|Failover to||If the Agentry application cannot connect to the server using the first transmit configuration, you can select a failover transmit configuration. You can set this attribute to any other transmit configuration within the application.|
|Check Data Tables||Specifies whether the data tables within the application are synchronized when the transmit configuration is used. .|
|Check Complex Tables||Specifies whether complex tables within the application are synchronized when the transmit configuration is used.|
|Address||Disabled for WebSockets.|
|Port||Disabled for WebSockets.|
Transmit Configuration ‒ Session Attributes
Track Transmit Events
Whether to track transmit events.
|Stay Logged In||Select to indicate that the client user remains logged in and the application remains connected to the server to support real-time communication within the mobile application, which includes background sending and push behaviors. Set this attribute when an Agentry application requires a constant network connection to the back-end data. The serverInactiveTimeoutOverride setting is used during stay connected, and during an actual transmit.|
|Prompt on Log In||Select to display a prompt when the connection between the application and the server is lost, and the application attempts to reconnect.|
|Prompt on Log Out||Select to display a prompt when the Agentry application is logged out of the server.|
|Inactive Timeout||Specifies the time limit, in seconds, to keep the application connected to the server, both when there is no data transmission activity between the client and server, and during an actual transmit. If you experience frequent disconnects, increase this number.|
|When Off-line||If the connection to the server is lost, indicates whether to stay offline or attempt to reconnect at the specified interval.|
|Attempts||If you select to reconnect when offline, indicate the number attempts. If you exceed the number of attempts, the manner in which the application responds depends on the Transmit Configuration attributes. For example, the application can display a prompt or switch to the failover transmit configuration.|
Reconnect Attempt Period
If online, the period of time, in seconds, the client should try to reconnect.
If the connection to the server is lost, the time period that must elapse before attempting to reconnect.
|keepAlivePeriod||Disabled for WebSockets.|
|Allow background sending from client||Enables background sending of pending transactions from the application to the server as soon as they are applied.|
|Retry Period||If background sending is enabled, specifies the amount of time, in hours, minutes, and seconds, to wait between failed attempts to send a transaction.|
|Retry Attempts||If background sending is enabled, specifies the number of attempts at sending a transaction over background sending.|
|Allow server to push data to client||Select to allow the server to push data to the application. A module definition for pushes must exist for the application. Users connecting to the server are logged in as Push Users.|
|Retry Period||If "Allow Server to Push Data to Client" is selected, specifies how long the server waits before attempting to resend data for a push when a failure occurs.|
|Attempts||If "Allow Server to Push Data to Client" is selected, specifies how many attempts to push data to the application when a failure occurs.|
|Client Port||Disabled for WebSockets.|
Transmit Configuration ‒ Modem Connection Attributes
|Check for Modem Connection||Specify whether the Agentry application checks for a modem connection when using the transmit configuration prior to beginning the transmit.|
|Connection Name||Options include:
|If Not Connected||Specifies that the application attempts to create a connection using the specified Windows network connection when there is no current connection. If this option is not selected, the remaining modem connection attributes are disabled.|
|Connect Prompt||Provides a message or instructions to the user on the client prior to attempting to create a modem connection. Leave blank if no message is required.|
|Prompt User for Dial-up Username||If selected, prompts the user to enter a user name for the network connection, which is used as the login name for the network connection once the modem’s handshaking processes are successful. If this option is not selected, the Agentry application login is used.|
|Prompt User for Dial-up Password||If selected, prompts the user to enter a password for the network connection. If this option is not selected, the Agentry application password is used.|
|Modem Init Wait||Specifies the amount of time, in milliseconds, to wait for the client device’s modem to initialize before beginning the dial-up process.|
|Post-connect Wait||Specifies the amount of time, in milliseconds, to wait after the network connection is made before beginning the transmit process between the client and server.|
|Close Connection||Specifies when to close the modem connection once no more
data is being transmitted between client and server:
Remind to Turn On Modem
Whether to remind user to turn on modem.
Remind to Turn Off Modem
Whether to remind user to turn off modem.