|
Deployment Links 3270 Display Administrator Website |
Deployment StrategiesThere are a number of ways that PASSPORT WEB TO HOST can be launched from client PCs. These include the following:
Advanced Deployment Issues
The Standard PASSPORT WEB TO HOST websiteThe easiest way to deploy PASSPORT is to send an email to each user with the following information: their user name or the session profile name the user must use and the URL for the standard PASSPORT website. This website consists of a series of HTML files that provide an easy method to launch a PASSPORT session. The following sections are included in the PASSPORT website:
For a Windows Server installation of PASSPORT, the default PASSPORT website can be accessed at the following URL: http://www.YourWebSite.com/pec/ For a Java Application Server (IBM WebSphere, BEA WebLogic, and so on) installation of PASSPORT, start Internet Explorer from any PC with access to the web server and type in the URL: http://YourWebSite/passweb/Eclient/Index.htm Prompting for a User NameIf you do not want to give users access to the standard PASSPORT home page, you may create your own Web page that prompts for the user name and then displays the list of sessions for that user. The list of sessions assigned to a user is stored in the ...\Eclient\Users\Xxxxxxxx.htm file, where Xxxxxxxx is the user name. To do this, you can modify the Launchmain.htm, Launch3270dsp.htm, Launch3270prt, Launch5250dsp, Launch5250prt, Launchvtdsp and Launchwysedsp.htm files. Then you can link them to your own Web page. Prompting a User for a Session Profile NameIf you do not want to give your users access to the standard PASSPORT home page, you may create your own Web page that prompts the user for a session profile name and then launches the PASSPORT ActiveX component. To do this, you can make a copy of the Launchmain.htm, Launch3270dsp.htm, Launch3270prt, Launch5250dsp, Launch5250prt, Launchvtdsp and Launchwysedsp.htm files and edit them accordingly. Then you can link it to your own Web page. Listing the Session Profiles in a Web PageYou can also create a Web page that lists various links to each mainframe session that a user or group of users may access. This can be done in a fashion similar to List of Configured Profiles. To do this, you can make a copy of the Eclientsessionlist.htm file and edit it accordingly. This deployment method is somewhat more involved and will require more time and effort. There is an Eclientsessionlist.htm file in the 3270dsp, 3270prt, 5250dsp, 5250prt, Vtdsp, and Wysedsp folders. Giving a User a Specific URL to Access the HostYou can give each user or group of users a unique URL name and they can then add it to their list of favorites in their browser. For example, on Windows Servers, the URL for the session profile name vmhost would be: http://yourwebsite/Pec/Ecomes.htm?sessionprofile=3270dsp/sessions/vmhost On Java Application Servers, the URL for the session profile name vmhost would be: http://YourWebSite/passweb/Eclient/Ecomes.htm?sessionprofile=3270dsp/sessions/vmhost Advanced Deployment IssuesUsers and Groups vs. Session ProfilesIt is not necessary to use the user and group features of the PASSPORT administration configuration program. If you wish, you can just define session profiles and then distribute these accordingly. The user and group feature provides a higher level of administration that may not be necessary in all situations. Pooled SessionsIf you have pooled LUs (logical units) configured on your TN3270E or TN5250E server, you may also want to configure pooled session profiles. This method allows multiple users to launch the PASSPORT software with the same exact configuration information and access the same pool of LUs. For example, if you have a pool on your TN3270E or TN5250E server called POOLMOD2 which is a pool of model 2 screen size LUs, you can create a session profile called POOLMOD2 which has the resource name POOLMOD2 and the screen size set to model 2. One disadvantage of using pooled LUs is that if all LUs in that pool are in use and another user tries to connect to that pool, that user will receive an error message and not be able to connect to the host. The advantage of pooled LUs is that it is very easy to setup and configure and can be done very quickly. Basic TN3270 and TN5250 always connect to a generic pool of LUs. The generic pool that is connected to is determined by the screen size (model 2, 3, 4 or 5) and the extended attributes setting. Dedicated SessionsIf you have configured dedicated LUs (also called specific LUs) on your TN3270E or TN5250E server, you probably want to configure a dedicated unique session profile for each dedicated user. For example, if you have dedicated LUs on your TN3270E server called USER001, USER002, USER003, etc., you may want to create session profiles called USER001, USER002, USER003, etc. as well. The advantage of dedicated session profiles is that each time a user connects to a mainframe, the user is guaranteed that an LU will be available for them. Each session profile can also have other unique session profile settings as well. This can be time consuming for a large number of dedicated sessions. However, this process can be automated by generating your own session profiles described in the following section. Automated generation of session profilesFor advanced system administrators that are familiar with Visual Basic or some other programming or scripting language, you may wish to generate your own session profiles. The session profiles are text based configuration files that are described in a human readable format reminiscent of Windows INI files. |