Client Access


CCS servers support connections from proprietary BMC Software clients (including SmartClient servers) and also third-party TN3270E emulators. The Client Access page allows you to define which client access methods are used and which port number or numbers or used for client connections.

Client Access tab

GUID-BD2E10CA-9A5D-4314-B704-36EF1186572D-low.png

Note

Attempting to connect a TN3270E emulator to a CCS protocol port or a CCS client to a TN3270E protocol port will not work, neither will attempting to make an encrypted connection to an unencrypted port or vice-versa.

You should carefully choose port numbers that do not conflict with port numbers used by other defined CCS servers or any other server processes running on the MVCM unit. We recommend starting client ports at 5000 and incrementing by 10 for each additional port. You may find using a spreadsheet to keep track of CCS server names, client ports and CCS sessions to be helpful in setting up and maintaining your MVCM unit.

Standard protocol clients include the Windows Console Consolidation Client, the CCS Applet and the SmartClient server and Viewer. These clients support both SSL-encrypted and unencrypted connections.

Require client certificates

When checked, the CCS server will require authentication certificates to be sent from the CCS viewer running on the client desktop. This requires setting up a certificate trust store on the computer running MVCM, and all operators must have appropriate certificates set up in their Windows certificate store. For more information, see Establishing-a-PKI-certificate-trust-store.

Enable unencrypted access

If enabled then the CCS server will accept unencrypted connections from a standard protocol client on the specified port.

Enable SSL access

If enabled then the CCS server will accept SSL-encrypted connections from a standard protocol client on the specified port. The server will use the SSL certificate specified on the server SSL tab; clients do not require their own certificate and do not need a copy of the server's certificate.

TN3270E Protocol

TN3270E protocol clients include commercial software such as IBM's Personal Communications (or 'PCOMM') and the open source Linux 'x3270'.

Enable unencrypted access

If enabled then the CCS server will accept unencrypted connections from a TN3270E client on the specified port.

Enable SSL access

If enabled then the CCS server will accept SSL-encrypted connections from a TN3270E client on the specified port. You will probably be required to change the default SSL certificate delivered with the MVCM unit and may also need to install the server's SSL certificate on client desktop computers. Consult with BMC Software support first if you wish to enable TN3270E SSL access.

Enable user ID and password prompt

Enables you to require users of 3270 emulators to enter in a user ID and password before they are allowed access to the 3270 session screen. Prompting is determined on a per-session basis in the configuration for each defined session: if you enable this option in the server configuration then you must also enable it in the desired session configurations(s). Disabling the prompt at the server level will disable the prompt for all sessions whether their configuration requires it or not.

Allow session (LU) selection

Check this option if you wish the CCS server to present a 3270 screen listing available sessions for clients who connect without initially specifying a TN3270E LU name. The user may tab around listing and connect to a specific session by typing X next to it and pressing Enter.

Save

Use the Save button to save any configuration changes you have made to this server. You will be returned to the list of console servers.

Cancel

Use the Cancel button to cancel any configuration changes you have made to this server. You will be returned to the list of console servers.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*