In addition to the common configuration settings, 3270 and 5250 host types require these specific settings.
Device name
If you selected TN3270, TN3270E, or TN5250 as the protocol, specify the device name to use when the session connects to the host. The device name is also known as the host LU or pool. If you do not specify a device name for the session, the host dynamically assigns one to the session. A device name that is set within a macro will override this setting.
If you selected Terminal ID Manager you can use it to provide IDs to client applications at runtime. You can use the Terminal ID Manager to manage pooled IDs for different host types. An ID is connection data that is unique for an individual host session. To use Terminal ID Manager, you must have a Terminal ID Manager server configured. See Terminal ID Manager in the Management and Security Server Installation Guide.
If you decide to use Terminal ID Manager and have configured the Terminal ID Manager server, then you can select from the options below to configure the criteria for acquiring an ID. All criteria must be met in order for an ID to be returned.
NOTE:Keep in mind that by specifying a criterion, you are indicating that the ID should be allocated only when an ID that has that specific value is found. The set of criteria selected here must be an exact match of the set of criteria specified on at least one Pool of IDs in Terminal ID Manager before the ID request can succeed.
Table 5-2 Terminal ID Manager Criteria
|
Criterion |
Description |
|---|---|
|
Pool name |
Include this attribute and enter the name of the pool to limit the ID search to a specified pool. |
|
Client IP address |
The IP address of the client machine will be included as part of the request for an ID. |
|
Host address |
The address of the host configured for this session will be included as part of the request for an ID. |
|
Host port |
The port for the host configured for this session will be included as part of the request for an ID. |
|
Session name |
When selected, requires that the ID is configured to be used by this session exclusively. |
|
Session type |
The session type (for example, IBM 3270, IBM 5250, or UTS) is always included as part of any request for an ID. |
|
User name |
Use this criterion to ensure that only IDs created for exclusive use by specific users will be allocated. The current user’s name, which must be found on an ID before it can be allocated, is the name of the user that the session is allocated to at runtime. To configure a session based on user names, a default place holder user name is available: tidm-setup. For the administrator to configure sessions using tidm-setup, the Terminal ID Manager needs to have IDs provisioned for tidm-setup. You can override the default name with one of your own by modifying the Micro Focus/ReflectionZFE/sessionserver/conf/container.properties file as follows: id.manager.user.name=custom-username Where custom-username is replaced by the name you want to use. |
|
Application name (UTS) |
The name of the host application will be used as part of the request for an ID. |
To determine the connection attempt behavior if Terminal ID Manager does not successfully allocate an ID to this session, use If ID is not allocated:
Fail connection attempt -If selected, the session will not attempt to connect when an ID is not allocated.
Allow connection attempt -If selected, the session will attempt to connect when an ID is not allocated. The attempt may be rejected by the host. There are some host types that permit a user to connect without an ID.
To confirm that Terminal ID Manager can provide an ID using the criterion and value selections you have made, click Test.
Terminal model
Choose the terminal model you are connecting to. (3270 host type only)
If you choose Custom Model, you can set the number of columns and rows to customize the terminal model.
Host character set
Select the 3270 or 5250 host character set you want to use. This setting chooses a conversion table to convert host characters (EBCDIC) into PC characters (ANSI). This setting should match the national character set used by your host system. If it doesn't match, then some characters, such as accents, may not display correctly. See your host documentation for definitions of the characters in each set. The default value is US English (037).
TLS/SSL Security
SSL and TLS protocols allow a client and server to establish a secure, encrypted connection over a public network. When you connect using SSL/TLS, ZFE authenticates the server before opening a session, and all data passed between and the host is encrypted using the selected encryption level. The following options are available:
Table 5-3 TLS/SSL Descriptions
|
Security options |
Description |
|---|---|
|
TLS 1.2, 1.1, 1.0, and SSL 3.0 |
Allow connection through TLS 1.2, TLS 1.1, TLS 1.0, or SSL 3.0, depending on the capabilities of the host or server to which you are connecting. |
|
TLS 1.2, 1.1, 1.0 |
Select this value to connect using TLS, but not SSL. As part of the TLS protocol, the client checks the server or host name against the name on the server certificate. Therefore, TLS connections require the common name on the server certificate to match the host or proxy server name. |
|
SSL 3.0 |
Select this value to connect using SSL, but not TLS. This is not recommended, but some hosts do not support TLS. If you plan on using this option, there is an additional configuration step to follow:
|
NOTE:See the section on Making Secure Connections for information on adding trusted certificates, key stores, using SSH, and other advanced security information.