Using the SDK with the e-Vantage ID Manager
If you are using the e-Vantage ID Manager with either Host Access Server (HAS) or the Management and Control Services (MCS), your application can take advantage of the ID Manager's ability to provide multiple terminal or session IDs for UTS or T27 host sessions. This allows your application to open multiple host sessions simultaneously, using only one WebView (and associated connection).
 |
The ID Manager is only used for connecting to 3270, 5250, UTS, or T27 host sessions, which require a unique ID; ALC and VT host sessions do not require a unique ID. |
The following sections outline the steps involved in using the ID Manager with your application.
Creating IDs in the ID Manager
To use the ID Manager with your custom application, you must first complete the following tasks within the ID Manager:
- Add an Address Pool (recommended) or a User as the type of Name you will create for the IDs.
- Assign IDs to the Name (either Address Pool or User) that you added. You must create an equal or greater number of IDs than will be used at any one time by your application.
Once you have created IDs and assigned them to an Address Pool or User in the ID Manager, you must create a configuration in HAS Management, specifying the following:
- On the New Configuration - INT1 Properties page (for UTS) or New Configuration - TCPA Properties page (for T27), select the Use ID Manager option.
- Select either Address Pool or User Name from the Get ID From list box. If you select Address Pool, you must also enter the name of the pool in the Address Pool field.
Configuring ID Usage within the SessionLoader Object
The SDK's SessionLoader object provides two methods that you may need to use if you are obtaining terminal or session IDs for your application from the ID Manager:
This method
|
Does this
|
setResourceManagerOptions |
Allows you to specify the initial number of IDs that are allocated to the application from the ID Manager, as well as the increment in which additional IDs will be obtained when all allocated IDs are already in use. If you do not use this method to specify these values, the default values of 5 (initial reserve) and 5 (reserve increment) are used.
 |
This method also has a third parameter — rsa — which is not currently used, and should be set to an empty string (""). |
|
|
In addition to allowing you to request a larger number of IDs, you can also use this method to limit the number of IDs in use. For example, if your application requires only one ID, you can use this method to specify an initial reserve of 1, with a reserve increment of 1. |
Shutdown |
Ensures that all IDs defined with a Lease Timeout (from e-Vantage ID Manager) are properly retained by the SDK for future use, once your application no longer requires them. (IDs that do not have a Lease Timeout defined are freed automatically when the application closes.) You must call this method when your application terminates if you are using leased IDs.
 |
If the IDs have a Lease Timeout value defined, you must call this method when your application terminates. Failure to do so may cause these IDs to become unusable by your application or by e-Vantage ID Manager. |
|
For more detail about using these SessionLoader methods, see Establishing a Host Connection.