docmain.css" />
As an example, let’s configure the Application Configuration section of a MDM Tool app assignment to:
Only support IBM sessions (disable SSH and Telnet)
Block the user from creating, editing, or managing sessions
Hide the host name/IP and port from the user
Configure two sessions
Figure 1-1 The MDM Tool administrative console would look as follows:
Here’s a table of the key-value pairs for this example and what each does.
Table 1-1
Configuration Key |
Value Type |
Configuration Value |
Description |
---|---|---|---|
EnableSSH |
Boolean |
false |
Disables support for SSH sessions. |
EnableTelnet |
Boolean |
false |
Disables support for Telnet sessions. |
AllowNewSession |
Boolean |
false |
Locks down users ability to create a new session. |
AllowEditSession |
Boolean |
false |
Locks down users ability to edit a session. |
AllowManageSessions |
Boolean |
false |
Locks down user from managing sessions. |
ShowIPAddressAndPort |
Boolean |
false |
Remove host name/IP or port in user interface. |
Sessions.deleteall |
String |
* |
Delete all existing sessions. |
Session1.Name |
String |
Sales |
Name of session1 |
Session1.HostURL |
String |
tn3270e://serverx.acme.com:23 |
Host URL for session1 |
Session2.Name |
String |
Accounting |
Name of session2 |
Session2.HostORL |
String |
tn5250://servery.acme.com:23 |
Host URL for session2 |
Notes for Deploying Reflection Mobile with an MDM Tool
The Sessions.deleteall entry deletes all session configurations on the device. This guarantees that the only sessions on the device will be the ones configured via MDM. This is optional.
All sessions must be named (i.e. the Name property must be set to a unique string). If not named the session will not be created.
Add session configuration using Session1, Session2, Session3, and etc. syntax.
If the session type has been restricted, the session will not be created. For example if the EnableSSH property has been set to false and an SSH session configuration is present, the session will not be created.