2.2 Product- or Session-specific settings

If you are using one of these products, follow the steps to configure a session or session type.

2.2.1 Configure a Host Access for the Cloud session

Note the session properties and the Session Server URL. Click Launch.
A browser opens to the web client Settings > Connections panel. Configure the settings for this session, and click Save.
When finished configuring, click Exit to save the session to the Management and Security Server.
As a next step, you can
- Use Assign Access to make the session available to end users.
- Return to Manage Sessions to add or edit a session.

2.2.2 Configure a Reflection/InfoConnect Desktop - Workspace Automated Sign-on session

Use this session type to enable automated logons to a mainframe from unmanaged desktop sessions running Reflection or InfoConnect Workspace.

In addition to adding the session, you must Configure Settings for Automated Sign-On to secure the server connections and manage user access. And the mainframe needs to be configured to support PassTickets. See the Automated Sign-on for Mainframe Administrator Guide for details.

Prerequisites

To add a Workspace Automated Sign-on (ASM) session, these preliminary tasks must be completed outside of Management and Security Server.

In Reflection/InfoConnect Workspace, create a 3270 session that includes an ASM login macro. Detailed steps are included in your Reflection/InfoConnect documentation.
Save the session in a location that can be accessed by Management and Security Server.

Proceed with the Workspace Automated Sign-on (ASM) Settings File configuration in Management and Security Server.

Workspace Automated Sign-on (ASM) Settings File

Continue on the Manage Sessions - Add New Session panel in Management and Security Server (where you selected the Product name and Session type).

Session name requirements. The Workspace ASM session name must exactly match the host name to which the client is connecting.

NOTE:Host name variations. If clients connect to different variations of the host name, or if they connect to the host by its IP address, each of those variations needs its own Workspace ASM session with a matching name.

For example, if this session is being configured to automatically log on to blue.mycompany.com, then the session name must be blue.mycompany.com, not blue or another variation.

If you want to enable sessions to automatically log on to blue.mycompany.com, blue, or 123.456.78.90 (blue.mycompany.com's IP address), you must create separate sessions with all of these names.
```
Proper naming of the Workspace ASM session is critical. 
```
If necessary, edit the session name or create additional sessions.
Click Browse. Select the Reflection/InfoConnect session that contains the Workspace ASM login macro.
Click Save to upload the settings file and save the session.

The session is added to the Manage Sessions list and is available to be assigned.

Assigning Access to a Workspace Automated Sign-on session

When you are ready to assign users to be able to log on automatically to the mainframe session, refer to Search & Assign.

In particular, note the required Edit option used to select a method to obtain the mainframe user name.

2.2.3 Configure a Rumba+ Desktop session

You are able to add a Rumba+ session to be managed by Management and Security Server because you already

configured a session in your Rumba+ application.
saved the session profile.

Now, you must upload and attach your Rumba+ session profile to the session you are adding to Management and Security Server.

Rumba+ Session Profile

After you enter a Session name, click Browse. Select the Rumba+ session profile (saved by your Rumba+ application). The profile name displays on this panel.
By default, Overwrite settings files is not selected, and users can set local preferences in their launched sessions.

Check this option if you want Management and Security Server to compare the local and web server versions of the settings file and overwrite the user's file if there are differences.

NOTE:After a Rumba+ session is created in the Administrative Console, users can open their Rumba+ sessions from the Windows Start menu, as usual. The settings file is downloaded from Management and Security Server to the client computer the first time the session is launched.

Users can then launch the session using the local settings file. Sessions launched from the local settings file are not updated from the Management and Security Server settings file.

Overwrite settings files allows you to easily distribute updates to existing settings files; however, changes that users made to their settings will be lost.
If entitled to the Security Proxy Add-On, you can configure the Rumba+ session to connect through a Security Proxy server that has client authorization enabled.

The Security Proxy Settings require one setting in the Rumba+ session (configured separately using the Rumba+ client), and one setting on this Configure Session panel.
1. In the Rumba+ session, set the host name and port to the address of the Security Proxy server.
2. On this Configure Session panel, check the Use security proxy server box.
  
  Enter the host name and port to which the Security Proxy will forward the connection.
Click Save. The profile is then uploaded and attached to the session.

To edit a configured Rumba+ session

Using your Rumba+ application, open the appropriate session profile, and make the changes. Save the profile.
In Management and Security Server, open Manage Sessions, and click the session name.
Click Browse and select the Rumba+ session profile that you just edited and saved.
Click Save to upload and attach the updated profile.

2.2.4 Configure a Reflection for the Web session

You can use additional settings to customize the display and behavior of your Reflection for the Web session.

Options on this panel: Appearance | FTP | Advanced Settings | Applet Parameters

Appearance

Window title. You can change the title bar for the session with special characters.

Table 2-1 The title can include these special characters:

Character	Value
&&	a single ampersand
&c	Connection Status (whether you are connected and over what transport)
&d	Date
&h	Host name
&s	Session type
&t	Transport
&v	Terminal session identifier that uniquely identifies this terminal session from others. See specific types:
&v for IBM 3270 and IMB 3270 Printer sessions	LU name
&v for IBM 5250 and IBM 5250 Printer sessions	Device name
&v for ALC. UTS Terminal, T27, T27 Printer, and Airlines Printer sessions	Terminal ID

Display session in its own window. Select to launch a session in a frame outside of the browser page.
Display session embedded in a web browser window. Select to launch the session in a new browser window.

Use this option to specify a custom page template, which allows you to format the HTML to add custom text, graphics, or JavaScript for the session. The template jsp must be stored in the /mss/server/web/webapps/mss/templates folder on the MSS server. You can copy one of the sample templates as a starting point for your own template.

Templates must be stored in the templates folder directly or in a subfolder. If you leave the page template field empty, the embedded session will appear in a new browser window with a simple heading that shows the name of the session. When the specified template is not present, the default embedded page is used. For more information, see the Knowledgebase article: Using Templates in Reflection for the Web.

FTP

Select Enable FTP within this session when you want to include FTP as an option on the File menu for IBM 3270, IBM 5250, HP, VT, or UTS terminal emulation sessions. When enabled, users can open a window that allows them to easily transfer files using FTP.

FTP Window

When you configure a standalone FTP session, use these options to specify the appearance of the FTP window. When Local/remote lists and console is selected, lists of local and server files and directories are displayed in the top portion of the FTP window, and an FTP console with a command line is displayed in the bottom portion.

Users can change this appearance after the session is started using buttons on the FTP button bar. When either Lists only or Console only is selected, users cannot change the FTP window appearance.

Advanced Settings

Click Advanced, and use these settings to customize how the session is displayed, launched, and delivered.

Window Size and Status Bar

Use best dimensions for each user

Based upon the client machine's screen resolution, Management and Security Server is able to determine the best width and height for each user's session window. This setting applies only when the session is displayed in its own window.
Use maximized dimensions

The session will be in a full screen display. This setting applies only when the session is displayed in its own window.
Use these window dimensions

The Width and Height options determine the dimensions of the applet (in pixels).
Display status bar

This option controls whether the status bar appears in the terminal window. The status bar appears at the bottom of the window and includes information such as the cursor position, whether the connection is encrypted, and the type and status of the connection.

Session Auto Launch

Check Auto Launch to automatically launch the session when the session list is displayed. Users cannot override this Auto Launch mechanism.

When this setting is not enabled, users can choose to open a session automatically by configuring Session Attributes, available from the Action button on the session list.

Applet Parameters

You can customize the properties of a Reflection for the Web session by adding applet parameters.

Applet parameters modify the behavior of the basic session. When you launch a session and change its settings, the new settings are saved in a configuration file. Applet parameters allow you to extend functionality beyond the configuration file.

Refer to Applet Attributes and Parameters in the Reflection for the Web Reference Guide for descriptions and valid values of the standard applet parameters

To add a parameter

Click +Add.
From the Parameter drop-down list, select a standard parameter, or click <Custom> to add a new one.
Enter a Value, if required.
Click Add. The parameter is added to the table.

NOTE:Not all parameters are valid for all session types. To be sure a parameter applies to your session, refer to the Applet Attributes and Parameters.

List of current parameters

The applet parameters that are currently assigned to this session are listed in the table. To remove a parameter, check it, and click -Remove.

Launch

Click Launch, and then configure the session. When you Save/Exit the session, the settings are sent to the Management and Security Server.

Next steps

As a next step, you can

Use Assign Access to make the session available to end users.
Configure Authentication and LDAP authorization.
Return to Manage Sessions to add or edit a session.
Export a Reflection for the Web session

Export a Reflection for the Web session

Use the Export option to save a Reflection for the Web session as a Host Access for the Cloud session type. After the Host Access for the Cloud session is created, the original session remains unchanged in the Manage Sessions list.

On the Manage Sessions panel:

Locate the Reflection for the Web session you want to save as a Host Access for the Cloud session type.

HINT:Reflection for the Web session types are identified by a globe icon (denoting a web-based session), followed by the terminal type, such as 3270: .
Right-click the session (or check the box) and click Export.
On the Export session panel, enter the name for the new Host Access for the Cloud session, and the address of the Session Server that will host the session.
Click Create. The new session is added to the Manage Sessions list and can be assigned to users or groups. Note that the icon changed to the Host Access for the Cloud session type: .

The original Reflection for the Web session is unchanged and remains available in the session list.