DataSplice Releases Mobile Integration Suite 3.0
Beginning a Session
Depending on the steps previously taken, the behavior for working with a session may vary. For example, if the user has not yet been authenticated from a previous session, the initial login dialog box is displayed. The user must then log in using the correct credentials to connect to the DataSplice Server and be authenticated appropriately. In contrast, if the user has previously been authenticated, the list of available views will be displayed upon launching the application, although the user is still not connected at this time. Any action in the application that requires a query of information from the DataSplice Server will attempt to automatically reconnect.
Logging In
If this is the first time accessing the Remote Client, or if the previous session was successfully logged out, the user will be required to log in to obtain a new session.
- Launch the Remote Client.
- In the resulting dialog box, enter the appropriate login information, keeping in mind that all entries are case-sensitive:
Field Name Description User Name The unique login name for this user. Password The password corresponding to the unique user name in the previous field. Domain The domain that this user belongs to. If the desired entry does not show up in the drop-down list, it can be typed directly into the drop-down field. After a successful login attempt, the domain that was entered will remain in the drop-down list for future use. DataSplice Server The computer name or IP address of the machine running the DataSplice Server. If a port other than the default, 4100, is being used, it should be specified with a colon and the port number immediately following the server name or IP address. For example, if the server is named test and the DataSplice Server is configured to listen on port 4101, the value should be entered as test:4101. 
- Click the Connect button to continue. If the Cancel button is clicked, the user will not be authenticated, and the Remote Client application will automatically close.
- The Remote Client will attempt to authenticate and connect with the given information. The behavior to follow depends on the settings of the Offline Behavior attribute, as described in the following sections.
Reconnecting an Existing Session
If the user has previously been authenticated and has not since logged out, the list of available views will be displayed upon launching the application, although the user is still not connected at this time.
- Launch the Remote Client.
- The home screen will be displayed, showing the list of available views. Remember that, at this time, the connection to the DataSplice Server has not yet been re-established.
- Perform any action in the Remote Client application that requires a query of information from the DataSplice Server, such as querying data in a view, attempting to synchronize with the DataSplice Server, etc.
- The Remote Client will attempt to automatically reconnect to the DataSplice Server.
Acquiring Offline Data when Offline Behavior is Defined as Always Online
If the Offline Behavior attribute in the DataSplice Administration Client has been defined as Always Online, it is not possible to cache offline data onto the Remote Client device. For the same reason, it is also not possible to obtain an offline session in this scenario. Please see the explanation of built-in system attributes for more information about this attribute setting.
Acquiring Offline Data when Offline Behavior is Defined as Always Offline
If the Offline Behavior attribute in the DataSplice Administration Client has been defined as Always Offline, the caching of offline data will be automatically performed during any login or synchronization process. In addition, the user always has an offline session, even if the user is still connected to the DataSplice Server. This offline session will remain until it is released by logging out of the Remote Client or it is revoked by an administrator in the Administration Client. Please see the explanation of built-in system attributes for more information about this attribute setting.
- Launch the Remote Client.
- Log in with the credentials of a user who has offline behavior defined as Always Offline.
- Offline data will automatically be cached onto the Remote Client device, during which time a status dialog box will be displayed.
- Click OK to close the dialog box when the offline data has finished loading on the device.
- The home screen will be displayed, showing the list of available views.
- Because of the Always Offline setting, the application will immediately assume the device is disconnected as soon as the synchronization process finishes. Thus, as soon as the offline data is loaded on the device, it is ready to be used in an environment without network connectivity.
Acquiring Offline Data when Offline Behavior is Undefined
If the Offline Behavior attribute in the DataSplice Administration Client has not been defined, the ability to acquire offline data is available to the user but it requires the synchronization process to be explicitly invoked. Once a synchronization has been performed in this scenario, the user will have an offline session, even if the user is still connected to the DataSplice Server. Please see the explanation of built-in system attributes for more information about this attribute setting.
- Launch the Remote Client.
- Log in with the credentials of a user who has undefined offline behavior.
- Upon successful login, click File > Synchronize with Server.
- Offline data will be cached onto the Remote Client device, during which time a status dialog box will be displayed.
- Click OK to close the dialog box when the offline data has finished loading on the device.
- The home screen will be displayed, showing the list of available views.
- Click File > Work Offline to disconnect from the DataSplice Server and begin using the stored offline data.
Last modified 2006-10-18 02:41 PM
