Creating or editing a client profile

To use the Session Configuration Manager to create or edit client profiles:

Run the Session Configuration Manager on the server or on your local workstation.
Optional: For general instructions on using the Session Configuration Manager, click the Help tab. This tab also contains links to the Readme file and this Administrator Guide.
Click the Create or Edit Session tab, then do one of the following as needed:
- Create a new session. Click Create a New Session, then select the Type (host emulation session type) and Implementation (Pro or Java client).
- Edit an existing session. Click Open an Existing Session, then specify the full path of the HTML session configuration file to edit. The Browse utility defaults to the location of the last saved configuration file.
Click Go!.
The tabs for the selected host type and technology implementation appear.
Optional: Click each tab, click ? at the bottom of the screen, then print the help pages for each tab.
Configure the settings on each page as needed:
- For details on each field, see the online help. For details on configuring client start options, concurrent sessions, and multiple language support, see Configuring client profiles.
- The Session Configuration Manager displays an exclamation mark next to required settings, and provides many default settings. You need to enter only a few unique settings to make your connections work correctly. However, you should check each page to be sure you select the appropriate options for your needs./choice>
To save the profile, click the check mark icon at the bottom of the Session Configuration Manager.
Web-to-Host generates the HTML file and displays the Save As dialog box.
Specify an appropriate folder in which to save the profile.
In server mode, you must save the profile in a Web-published folder. Otherwise, client sessions do not receive automatic updates from the Web server.

Note: In previous versions of Web-to-Host, updates from the administrator deleted all user configurations. In this version, there are cases when administrator changes do not automatically delete the user’s configuration (.cph) file. For more information, see User Profile Configuration.