VNX: How To Remove a LUN from a Storage Group (User Correctable)

Please follow the steps below

1- Login to Unisphere and select the array serial number

2- Click on the system Tab

3- Click on the Host Tab

4- click on Storage Group

5- Highlight the desired Storage Group, then click on Properties

6- A new pop up window will appear, choose the LUN Tab

7- At the bottom half you will see the LUNs that are in that Storage Group, click on the LUN you wish to remove to highlight it

8-Click on the “Remove” button to remove it. (you may not receive an alert asking if you are sure)

9- Click Apply, or Okay to confirm


Below is a video demonstration of the same

https://www.youtube.com/watch?v=P3xudqZ2bBM

Related:

  • No Related Posts

7022812: Sequencing Reflection Desktop 16 as a Virtual Application with Microsoft Application Virtualization 5.x

Before using the Microsoft Sequencer Package Configuration Wizard to sequence Reflection Desktop 16, document the sequencing requirements and steps by determining which Reflection Desktop 16 components and features are to be installed, the location of installation files, and the location of any configured user data, such as session documents. Some Reflection application components may not be needed and it is recommended to install Reflection on a stand-alone PC to help identify and document the installation steps in advance.

If Reflection has any service packs or updates, ensure that the service pack installer file, *.MSP, is available for installation during the sequencing process. Reflection Desktop Productivity Microsoft Office Tools have not been tested to work with Microsoft Office streamed as a virtual application.

Use the Reflection Installation Customization Tool (ICT) to create Companion install packages and to define permissions files; the basic steps which are listed below. Refer to the Installation and Deployment Guide for Reflection Desktop 16 as a resource, which is available from https://www.attachmate.com/documentation/reflection-desktop-v16-1-sp1/deployment-guide/data/bookinfo.htm

The following steps for using the Installation Customization Tool assume that a Reflection Administrative Installation has been performed per the Installation and Deployment Guide.

If desired, use the Installation Customization Tool to create a Companion.MSI file:

1. Navigate to the Reflection Administrative Installation and run Setup.exe /Admin to launch the Installation Customization Tool.

2. Select “Create a new Companion installer.”

3. Click OK.

4. In the left pane, click “Specify install locations.”

Note: It is important to perform steps a. and b. in order.

a. Under Installation type, select the “Installs to all users of a machine” option.

b. In the Default installation folder drop-down list, type in [CommonDocumentsFolder]Micro FocusReflection.

5. In the left pane, click “Add files to”

6. Select the value of [CommonDocumentsFolder]Micro FocusReflection.

7. Click the “Add button” to add files that need to be included.

These files include pre-configured Reflection session documents (.rd3x, .rd5x, .rdox, .rfw, or .rwsp settings files).

8. Click File / Save As.

Save the Companion.MSI file in the same location as Setup.exe.


If desired, use the Installation Customization Tool to define permissions files:

1. If the Companion file created in the previous section is no longer open, open the Companion.MSI file.

Navigate to the Reflection Administrative Installation and run Setup.exe /Admin.

2. In the left pane, click “Specify install locations”.

Verify that “Installs only for the user who installs it” is selected.

(This option may be dimmed; as long as it is selected, there is no cause for concern)

3. In the left pane, click “Modify user settings” to define *.access permission files.

For example to define an .rd3x.access file to restrict TN3270Basic or TN3270Advanced settings.

a. Select the Application – Settings to modify and click the Define button.

b. Select the Group from the Groups drop-down list.

This allows or restricts accessibility for each item listed.

c. Repeat steps a. and b. until the permissions have been configured appropriately.

d. Click Next.

e. Optional: Select Additional security options for Session file encryption.

f. Click Finish.

4. Click File / Save

Save the Companion.MSI in the same location as Setup.exe.


Use the Application Virtualization Sequencer Wizard to start the sequencing process with Reflection Desktop 16:

1. Launch the Microsoft Application Virtualization Sequencer

2. Select “Create a New Virtual Application Package”

3. For the Packaging Method select “Create Package (default)”

4. Press Next

5. Resolve any issues shown on the Prepare Computer list

6. Press Next

7. For the Type of Application choose “Standard Application (default)”

8. Press Next

9. On the Select Installer dialog choose “Select the installer for the application”

Use the Browse button to find the Reflection Desktop SETUP.EXE program in the Reflection Administrative Installation location

10. Press Next

11. On the Package Name screen enter the Virtual Application Package Name of your choice, like “Reflection Desktop 16”

Enter the Primary Virtual Application Directory (required) name:

For example: C:Program Files (x86)Micro FocusReflection

12. Press Next

13. Wait for the Virtual Environment to load.

14. On the Install Micro Focus Reflection Desktop 16 screen, click Continue.

15. Read and accept the License Agreement; then click Continue.

16. Personalize the installation by completing the Full name, Organization, and VPA number fields on the User Information tab.

17. On the File Location tab, verify the File Location by clicking the Browse button.

Following the example in this article:

File Location is specified as C:Program Files (x86)Micro FocusReflection

Default user data directory should be set to C:UsersPublicDocumentsMicro FocusReflection

18. On the Feature Selection tab, de-select any features not needed so that they will not install.

For example, de-select the following:

UtilitiesKerberos Manager

UtilitiesKey Agent

CompatibilityIBM Personal Communications

CompatibilityNetManageRUMBA

Application Programmer Interface

19. On the Advanced tab verify that “Install to this PC” is enabled.

20. Click the “Install Now” button.

21. When the Installation has completed successfully, click the Close button.

22. If service packs or updates are to be installed to Reflection Desktop:

a. On the Installation dialog of the App-V sequencer, press the “Run” button

b. Select the appropriate *.MSP file(s) to install a service pack, update or patch.

23. When the update or patch is installed or if there is no further .MSP updates to install continue on

24. If a Companion install file is to be installed to Reflection Desktop:

a. On the Installation dialog of the App-V sequencer, press the “Run” button

b. Select the appropriate *.MSI file to install the Companion install file.

25. When the install is complete, check the box that says “I am finished installing”

26. Press Next

27. Wait while App-V collects the system changes and the Configure Software screen displays.

28. From the Configure Software screen, highlight the Reflection Workspace choice and click on “Run Selected” to launch the application.

(Do NOT click Run All.)

29. Verify that the Reflection session documents added by the Companion.MSI file created earlier are available.

To create any additional session documents, use the Create New Document wizard.

Save the session file in the C:UsersPublicDocumentsMicro FocusReflection folder to be available for all end-users.

30. Launch and then close each session document to create the App-V files that will be used for streaming.

If you launch the Reflection Workspace, Reflection FTP client, or any session document, and a Sequencer error displays:

“The Sequencer could not stop the MSIServer service,” click OK and try again.

31. After all the applications and Reflection Workspace have been run and closed, press Next.

32. Verify the data on the Installation Report screen and resolve any issues

33. Press Next.

34. On the Customize screen decide if further customization is needed.

For example: if restrictions are required concerning different operating systems this is the time to do it.

35. If no further customization is needed select “Stop now. Create a basic virtualization package (default).”

36. Press Next.

37. Select “Save the package now” and enter the Save Location for the package contents

38. Press Create.

By default the App-V package will be located on the desktop of App-V Sequencing PC.

39. After the package is created press Close to finish and exit the Application Virtualization Sequencer program.

40. Copy the completed sequenced App-V package files to the Distribution Point or Virtual Application Server.

Related:

  • No Related Posts

How to Convert PFX Certificate to PEM Format for Use with NetScaler

Complete one of the following procedure to convert PFX certificate to PEM format for use with NetScaler:

NetScaler Wizard

Complete the following procedure to convert a PFX certificate to PEM format using NetScaler Wizard:

  1. Navigate to Traffic Management, Select the SSL node.

  2. Click the Import PKCS#12 link.

    User-added image

  3. Specify a file name you want for the PEM certificate in the Output File Name field.

  4. Click Browse and select the PFX certificate that you want to convert to PEM format. Some users prefer to upload the certificate to /ncsonfig/SSL directory and use it from there. If PFX certificate is stored on NetScaler then choose option Appliance and if it stored on your workstation then use Local.

    User-added image

  5. Specify the Import Password.

  6. Click OK.

    User-added image

  7. If the file is encoded, then select DES or 3DES as the Encoding Format:

    User-added image

  8. Specify the PEM Passphrase and the Verify PEM Passphrase.

  9. Click the Manage Certificates / Keys / CSRs link to view the converted PEM certificate files.

    User-added image

  10. You can view the uploaded PFX file with the converted PEM file.

    User-added image

  11. Expand the SSL node.

  12. Select the Certificates node.

  13. Click Install.

  14. Specify a Certificate-Key Pair Name in the Install Certificate wizard.

  15. Browse to the PEM file for both the Certificate File Name and Private Key File Name.

  16. Specify the Password.

  17. Click Install.

    User-added image

  18. Bind the certificate key pair to an SSL load balancing virtual server or NetScaler Gateway virtual server.

OpenSSL Utility

If you have requested and installed a certificate onto a Windows server using the Internet Information Service (IIS) certificate wizard, you can export that certificate with its private key to a Personal Information Exchange (PFX) file. To import this certificate onto the NetScaler Gateway, you must convert the PFX file to unencrypted PEM format.

You can use the open source utility OpenSSL to perform the conversion from PFX to PEM. Download a Win32 distribution of OpenSSL from Win32 OpenSSL.

You might also need C++ redistributable files if you want to use OpenSSL. Download this from Microsoft Visual C++ 2008 Redistributable Package (x86).

To convert a PFX file to a PEM file, complete the following steps on a Windows machine:

  1. Download and install the Win32 OpenSSL package from Win32 OpenSSL.

  2. Create a folder c:certs and copy the file yourcert.pfx into the c:certs folder.

  3. Open command prompt and change into the OpenSSLbin directory:

    cd %homedrive%OpenSSLbin

  4. Run the following command to convert the PFX file to an unencrypted PEM file (all in one line):

    openssl pkcs12 -in c:certsyourcert.pfx -out c:certscag.pem –nodes

    User-added image

  5. When prompted for the import password, enter the password you used when exporting the certificate to a PFX file. You should receive a message that says MAC verified OK.

    User-added image

  6. Point a browser to the NetScaler Gateway administration portal or HTTPS port 9001: https://netscaler-gateway-server:9001.

  7. Log on as root. The default password is rootadmin.

  8. Click the Maintenance link at the top of the page.

  9. Click the Browse button next to the Upload Private Key+Certificate (.pem) field. Browse to the c:certscag.pem file and click Upload.

  10. Restart NetScaler Gateway for the new SSL certificate to be applied.

Related:

  • No Related Posts

7021617: Enabling the Script Menu in Reflection

Enabling the Script Menu in Reflection for HP, UNIX and OpenVMS, and ReGIS Graphics

To enable the Script menu in Reflection for HP, UNIX and OpenVMS, and ReGIS Graphics, follow these steps:

  1. Start Reflection.
  2. On the Setup menu, click Menu to open the Menu Setup dialog box.
  3. In the Defined Menu box, click Macro.

Note: The Macro menu will only appear in the Defined Menu box if Visual Basic for Applications is installed as a component of Reflection.

  1. In the Available Options box, double-click Additional Items.
  2. Double-click Items from Version 6.x, and then click Script.
  3. Click the Add After button to add the Script menu to the Defined Menu list.

Note: You can choose to add the Script menu before or after any existing menu.

  1. Click OK. The Script menu should now appear on Reflection’s main menu.
  2. Click Save on the File menu to save the changes to your settings file. If necessary, create a new settings file.

Enabling the Script Menu in Reflection for IBM

To enable the Script Menu in Reflection for, follow these steps:

  1. Start Reflection.
  2. On the Setup menu, click Menu to open the Menu Setup dialog box.
  3. In the Defined Menu box, click Macro.

Note: The Macro menu will only appear in the Defined Menu box if Visual Basic for Applications is installed as a component of Reflection.

  1. In the Available Options box, double-click Additional Items.
  2. Click Script.
  3. Click the Add After button to add the Script menu to the Defined Menu list.

Note: You can choose to add the Script menu before or after any existing menu.

  1. Click OK. The Script menu should now appear after the Macro menu on Reflection’s main menu.
  2. Click Save on the File menu to save the changes to your settings file. If necessary, create a new settings file.

Related:

  • No Related Posts

NetScaler Native One Time Password Configuration

Configuration using the GUI

LDAP Policies and Actions Configuration

1. Browse to Security >> AAA – Application Traffic >> Polices >> Authentication >> Advanced Policies >> Actions >> LDAP. Click Add.

User-added image

2. Configure your LDAP server. This server/policy will be used for single factor authentication to the /manageotp website for users to add/manage their devices. It will also be used for two factor authentication to the NetScaler Gateway, along with the OTP passcode. This server needs to have authentication enabled.

User-added image

3. Create a second LDAP Action. This server/policy will be used for OTP management. Make sure that you uncheck the Authentication checkbox. Ensure that the Administrator Bind DN that you use has permissions to modify the OTP Secret AD attribute for all applicable users.

User-added image

4. Configure the Server Logon Name Attribute the same as how you configured it for the normal authentication LDAP server in step 3.

User-added image

5. In the OTPSecret field, enter the name of the AD attribute that the NetScaler will use to store the OTP secret. You can use userParameters, as long as that attribute is not already being used for something else. After entering the OTP secret, click Create.

User-added image

6. Create a third LDAP Action. This server/policy will be used for OTP verification (second factor in two factor authentication) when a user authenticates to the NetScaler Gateway using a registered device. This server is to be configured exactly the same as the server in steps 4-6, with the addition of an LDAP Search Filter. In the Search Filter field, enter userParameters>=#@. This will make sure that only users with registered authenticators are allowed to login. Click Create.

User-added image

7. Browse to Security >> AAA – Application Traffic >> Policies >> Authentication >> Advanced Policies >> Policy. Click Add.

User-added image

8. Name your policy, set Action Type to LDAP, in the Action dropdown, select the server that was created in steps 1-2, and enter true as the expression. Click Create.

User-added image

9. Create a second policy. This will be for OTP management (when a user browses to the /manageotp website to enroll/manage their authentication device). Set Action Type to LDAP, in the Action dropdown, and select the LDAP server that you created in steps 3-5. This is the server with Authentication disabled, and the OTP Secret configured. Enter HTTP.REQ.COOKIE.VALUE(“NSC_TASS”).EQ(“manageotp”) in the Expression field, then click Create.

User-added image
10. Create a third LDAP policy. This will be for OTP verification when the user authenticates to the NetScaler Gateway. Set the Action Type to LDAP, and in the Action dropdown, select the LDAP server that you created is step 6. This is the server that we disabled Authentication, and configured the OTP Secret, as well as the SearchFilter. Type true into the Expression field, and click Create.

User-added image

Back to top

Login Schema Configuration

1. Browse to Security >> AAA – Application Traffic >> Login Schema. Click on the Profiles tab, then click Add.

User-added image


2. This is the login schema that will be used when users browse to the /manageotp website. Enter a name, and then click the pencil (Edit) icon in the Authentication Schema field.

User-added image


3. Click LoginSchema to open the folder.

User-added image

4. Scroll down, find SingleAuthManageOTP.xml, and click it to highlight it, then click the Select button, then click Create.

User-added image

5. Click Add to create another Login Schema profile. This login schema will be used for two factor authentication to the NetScaler Gateway. Follow the same steps from step 4, except select the DualAuth.xml file from the Login Schema Files.

User-added image

6. Click More, scroll down, and enter 1 in the Password Credential Index field. This will allow the user’s password to be saved into Attribute#1, which will be used later in a traffic policy to allow single sign-on to StoreFront. Check the checkbox next to Enable Single Sign On Credentials Click Create.

User-added image

7. Switch to the Policies tab. Click Add.

User-added image

8. Enter an appropriate name in the Name field. In the Profile dropdown, select the profile that you created in steps 1-4 above. In the Rule field, enter HTTP.REQ.COOKIE.VALUE(“NSC_TASS”).EQ(“manageotp”), then click Create.

User-added image

9. Add a second login schema policy. Enter an appropriate name into the Name field, and select the profile that you created in steps 5-6 above. In the Rule field, type true, then click Create.

User-added image

Back to top

Configuring Authentication Policy Label

1. Browse to Security >> AAA – Application Traffic >> Policies >> Authentication >> Advanced Policies >> PolicyLabel. Click Add.

User-added image

2. In the Login Schema field, select LSCHEMA_INT. Click Continue. In the Policy Binding section, click the Click to select dropdown box under Select Policy, and then click the radio button next to the LDAP_manage_OTP_pol policy (created in step 9 of the LDAP configuration section of this document), then click Select. Click Bind.

3. Click Add Binding to add another policy. In the Policy Binding section, click the Click to select dropdown box under Select Policy, and then click the radio button next to the LDAP_confirm_OTP_pol that was created in step 10 on the LDAP configuration section of this document. Click Select, then click Bind.

4. Ensure that the LDAP_manage_OTP_pol policy has a higher priority (smaller number), then click Done.

User-added image

Back to top

Configuring AAA vServer

1. Browse to Security >> AAA – Application Traffic >> Virtual Servers. Click Add.

2. Name your vServer, select Non Addressable in the IP Address Type dropdown, click OK.

3. Click No Server Certificate, select an appropriate certificate, then click Bind. Click Continue.

4. Click No Authentication Policy. Select the LDAP policy that you created in steps 7-8 on the LDAP configuration section above, click Select.

5. Click Click to Select in the Select Next Factor dropdown, and select the OTP policy label you previously created, then click Select, and then click Bind. Click Continue.

6. In the right hand portion of the page, under Advanced Settings, click Login Schemas.

7. Scroll down and click No Login Schema in the Login Schema section.

8. Click Click to Select dropdown under Select Policy. Select the Single_manage_OTP_lschema_pol that you created in steps 7-8 in the login schema configuration above. Click Select, then click Bind.

9. Click 1 Login Schema. Click Add Binding, Click to Select, and select the dual factor login schema, click Select, click Bind, then click Close.

10. Verify that the single factor policy has a higher priority (smaller number) than the dual factor policy. Click Close.

User-added image

11. Set the portal theme to RfWebUI. This is the only type of portal theme that is supported with native OTP.

Back to top

Traffic Policy for Single Sign-on Configuration

1. Browse to NetScaler Gateway >> Policies >> Traffic. Click the Traffic Profiles tab, then click Add.

2. Name the profile appropriately, and in the SSO Password Expression field, enter: HTTP.REQ.USER.ATTRIBUTE(1). Click Create.

3. Click the Traffic Policies tab, then click Add.

4. Name the policy appropriately, in the Request Profile dropdown, select the traffic profile you just created, and then click the Switch to Default Syntax link, and create an appropriate expression for the type of traffic to which this policy will be bound in the Expression field. Click Create.

[NOTE: If the expression is configured as ‘true’ or ‘ns_true’, this policy will apply to all traffic and non-http traffic will also be impacted. The ‘true’ expression is for HTTP qualifier; for non http traffic this policy expression would fail, as explained in https://support.citrix.com/article/CTX233260. This behavior is observed in version 12.0 build 57.19]

Back to top

NetScaler Gateway Configuration

1. Browse to NetScaler Gateway >> Virtual Servers. Edit the existing NetScaler Gateway virtual server that you wish to implement OTP on.

2. Scroll down until you see the Policies section, and click the + icon.

User-added image

3. Select Traffic in the Choose Policy dropdown, and then click Continue.

4. In the Select Policy dropdown, click where it says Click to select, and then select the traffic policy that you created in the section above, then click Select, then click Bind.

5. Under Advanced Settings on the right hand side of the page, click Authentication Profile.

6. Scroll down until you see the Authentication Profile section, and then click the + icon to create a new authentication profile.

User-added image

7. In the Name field, enter an appropriate name. In the Authentication Virtual Server dropdown, Click to select. Select the OTP AAA vServer that we created earlier, and then click Select. Click Create.

User-added image

8. Click OK.

User-added image

9. Bind the RfWebUI portal theme to the NetScaler Gateway vServer. This is the only type of portal theme that is supported with native OTP.

10. If your NetScaler Gateway vServer is configured behind a Unified Gateway, you will need to modify the content switching expression. Browse to Configuration >> Traffic Management >> Content Switching >> Policies.

11. Edit the Unified Gateway policy, and add the following to the end of the Expression: || HTTP.REQ.URL.CONTAINS(“/manageotp”). Click OK.

Back to top

Enroll/Manage Mobile Authenticator

1. In your web browser, browse to your NetScaler Gateway FQDN, and add /manageotp to the end. Example: https://gateway.company.com/manageotp

2. This should load the authentication page, and it should be single factor. Login using your LDAP credentials.

User-added image

3. Click Add Device.

User-added image

4. Enter a name for your device, then click Go.

5. Open the Google Authenticator app (you can download this from the Play/App store for free). Scan the barcode that is displayed on your NetScaler Gateway browser page, then click Done. Note that you can also manually enter the string of characters.

User-added image

6. Test by clicking Test, then entering the code that is displayed on your authenticator, and click Go.

User-added image

7. If there are no additional devices to add/manage, you may logoff.

User-added image

Back to top

NetScaler Gateway Login

1. Browse to your NetScaler Gateway authentication page as you normally would, example: https://gateway.company.com

2. You should be prompted for two factor authentication. Enter your LDAP username and password, then enter the passcode from your authenticator.

User-added image

3. You should be successfully authenticated, and SSO to StoreFront should occur.

User-added image

Back to top

Related:

7021516: Keyboard Mapping in Reflection Desktop, Reflection 2014, and Reflection 2011

  1. Connect to your host.
  2. Click the Tools tab. In the Input group, click Keyboard Mapper.
  3. You can select the key to map one of two ways:
    • In the Map Keys section, place your cursor in the field and press the key or key combination that you want to map, and then click the Select Action button. Or,
    • In the Keyboard Mapper section, scroll to and select the Key Combination, and then click Modify.

Figure 1: Select the key to map under Map Keys or Keyboard Mapper.

  1. In the Select Action dialog box, there are several Map To options to choose from in the left pane:
Send Key

Sent Text

Launch Application

Open URL

Run Reflection Workspace Macro

Other Action

Action Sequence

Select an action, such as Open URL, in the left pane and make the selections or provide the information required in the right pane.

View Full Size

2413_1.gif

Figure 2: Select the action and configure it. In this example, the F5 key is being mapped to open a URL.

Mapping Control Characters in Reflection

To map a control character, select Send Text in the Select Action dialog box. Then use one of the following methods to enter the symbolic text for the control character in the “Text to send to host” text box:

  • ALT+nnn — Generate a control character by holding down the ALT key and pressing the three digit ASCII number using the numeric keypad. The symbolic text for the control character is placed into text box (<ESC> for ALT+027, for example). Using this method, Reflection 2011 can generate control characters for ASCII 1 (Start of Header) through ASCII 31 (Unit Separator).
  • CTRL+x — Generate a control character by holding down the CTRL key and pressing the letter corresponding to the control character. The symbolic text for the control character is placed into text box (<ESC> for CTRL+{, for example). Using this method, Reflection can generate control characters for ASCII 1 (Start of Header) through ASCII 29 (Group Separator).
  • Symbolic Text — Directly enter the symbolic text of the control character. All control characters from ASCII 0 (Null) through ASCII 31 (Unit Separator) can be entered using this method.

Note: If you are using Reflection 2014 ot later, you can use the “Select a special character“ list to map commonly used special characters, as shown in Figure 4.

Use the following table to identify the value for each control character for each entry method.

Control Character
ALT+nnn
CTRL+x
Symbolic Text
Null


<NUL>
Start Of Header
ALT+001
CTRL+a
<SOH>
Start Of Text
ALT+002
CTRL+b
<STX>
End Of Text
ALT+003
CTRL+c
<ETX>
End Of Transmission
ALT+004
CTRL+d
<EOT>
Enquiry
ALT+005
CTRL+e
<ENQ>
Acknowledgement
ALT+006
CTRL+f
<ACK>
Bell
ALT+007
CTRL+g
<BEL>
Backspace
ALT+008
CTRL+h
<BS>
Horizontal Tab
ALT+009
CTRL+i
<HT>
Line Feed
ALT+010
CTRL+j
<LF>
Vertical Tab
ALT+011
CTRL+k
<VT>
Form Feed
ALT+012
CTRL+l
<FF>
Carriage Return
ALT+013
CTRL+m
<CR>
Shift Out
ALT+014
CTRL+n
<SO>
Shift In
ALT+015
CTRL+o
<SI>
Data Link Escape
ALT+016
CTRL+p
<DLE>
Device Control 1
ALT+017
CTRL+q
<DC1>
Device Control 2
ALT+018
CTRL+r
<DC2>
Device Control 3
ALT+019
CTRL+s
<DC3>
Device Control 4
ALT+020
CTRL+t
<DC4>
Negative Acknowledgement
ALT+021
CTRL+u
<NAK>
Synchronous Idle
ALT+022
CTRL+v
<SYN>
End of Transmission Block
ALT+023
CTRL+w
<ETB>
Cancel
ALT+024
CTRL+x
<CAN>
End of Medium
ALT+025
CTRL+y
<EM>
Substitute
ALT+026
CTRL+z
<SUB>
Escape
ALT+027
CTRL+{
<ESC>
File Separator
ALT+028
CTRL+|
<FS>
Group Separator
ALT+029
CTRL+}
<GS>
Record Separator
ALT+030

<RS>
Unit Separator
ALT+031

<US>

The following example shows how to map an escape sequence.

Figure 3: Map keystroke F4 to send the text Escape 4 in Reflection 2011.

This example shows how to map to the Backspace, using the “Select a special character” list that is available in Reflection 2014 and later.

Figure 4: Map keystroke F4 to send Backspace in Reflection 2014.

Creating an Action Sequence

Follow these steps to map a series of actions to a keystroke.

  1. In the Select Action dialog box, select Action Sequence in the left pane.
2413_2.gif
  1. In the right pane, click the Add button.
  1. In the right pane, under Action category, select an action, such as Send Key, from the list.
  1. Action parameters vary depending on the action selected. If required, you will be prompted for the needed information for each parameter to the right of the Action. Select or provide the Action parameter.

For example, the Send Key action requires the parameter “Key” to be identified.

  1. Repeat steps 3 and 4 for each action in the sequence until the sequence is complete.
  2. Click OK.

Troubleshooting

If you are using non-VT terminal types such as Linux Console, Wyse, SCO ANSI or BBS-ANSI, and have trouble mapping a key, contact Customer Support (https://support.microfocus.com/contact/attachmate.html) for the latest update,.

Related:

7021516: Keyboard Mapping in Reflection Desktop 16, Reflection 2014, and Reflection 2011

  1. Connect to your host.
  2. Click the Tools tab. In the Input group, click Keyboard Mapper.
  3. You can select the key to map one of two ways:
    • In the Map Keys section, place your cursor in the field and press the key or key combination that you want to map, and then click the Select Action button. Or,
    • In the Keyboard Mapper section, scroll to and select the Key Combination, and then click Modify.

Figure 1: Select the key to map under Map Keys or Keyboard Mapper.

  1. In the Select Action dialog box, there are several Map To options to choose from in the left pane:
Send Key

Sent Text

Launch Application

Open URL

Run Reflection Workspace Macro

Other Action

Action Sequence

Select an action, such as Open URL, in the left pane and make the selections or provide the information required in the right pane.

View Full Size

2413_1.gif

Figure 2: Select the action and configure it. In this example, the F5 key is being mapped to open a URL.

Mapping Control Characters in Reflection

To map a control character, select Send Text in the Select Action dialog box. Then use one of the following methods to enter the symbolic text for the control character in the “Text to send to host” text box:

  • ALT+nnn — Generate a control character by holding down the ALT key and pressing the three digit ASCII number using the numeric keypad. The symbolic text for the control character is placed into text box (<ESC> for ALT+027, for example). Using this method, Reflection 2011 can generate control characters for ASCII 1 (Start of Header) through ASCII 31 (Unit Separator).
  • CTRL+x — Generate a control character by holding down the CTRL key and pressing the letter corresponding to the control character. The symbolic text for the control character is placed into text box (<ESC> for CTRL+{, for example). Using this method, Reflection can generate control characters for ASCII 1 (Start of Header) through ASCII 29 (Group Separator).
  • Symbolic Text — Directly enter the symbolic text of the control character. All control characters from ASCII 0 (Null) through ASCII 31 (Unit Separator) can be entered using this method.

Note: If you are using Reflection 2014 ot later, you can use the “Select a special character“ list to map commonly used special characters, as shown in Figure 4.

Use the following table to identify the value for each control character for each entry method.

Control Character
ALT+nnn
CTRL+x
Symbolic Text
Null


<NUL>
Start Of Header
ALT+001
CTRL+a
<SOH>
Start Of Text
ALT+002
CTRL+b
<STX>
End Of Text
ALT+003
CTRL+c
<ETX>
End Of Transmission
ALT+004
CTRL+d
<EOT>
Enquiry
ALT+005
CTRL+e
<ENQ>
Acknowledgement
ALT+006
CTRL+f
<ACK>
Bell
ALT+007
CTRL+g
<BEL>
Backspace
ALT+008
CTRL+h
<BS>
Horizontal Tab
ALT+009
CTRL+i
<HT>
Line Feed
ALT+010
CTRL+j
<LF>
Vertical Tab
ALT+011
CTRL+k
<VT>
Form Feed
ALT+012
CTRL+l
<FF>
Carriage Return
ALT+013
CTRL+m
<CR>
Shift Out
ALT+014
CTRL+n
<SO>
Shift In
ALT+015
CTRL+o
<SI>
Data Link Escape
ALT+016
CTRL+p
<DLE>
Device Control 1
ALT+017
CTRL+q
<DC1>
Device Control 2
ALT+018
CTRL+r
<DC2>
Device Control 3
ALT+019
CTRL+s
<DC3>
Device Control 4
ALT+020
CTRL+t
<DC4>
Negative Acknowledgement
ALT+021
CTRL+u
<NAK>
Synchronous Idle
ALT+022
CTRL+v
<SYN>
End of Transmission Block
ALT+023
CTRL+w
<ETB>
Cancel
ALT+024
CTRL+x
<CAN>
End of Medium
ALT+025
CTRL+y
<EM>
Substitute
ALT+026
CTRL+z
<SUB>
Escape
ALT+027
CTRL+{
<ESC>
File Separator
ALT+028
CTRL+|
<FS>
Group Separator
ALT+029
CTRL+}
<GS>
Record Separator
ALT+030

<RS>
Unit Separator
ALT+031

<US>

The following example shows how to map an escape sequence.

Figure 3: Map keystroke F4 to send the text Escape 4 in Reflection 2011.

This example shows how to map to the Backspace, using the “Select a special character” list that is available in Reflection 2014 and later.

Figure 4: Map keystroke F4 to send Backspace in Reflection 2014.

Creating an Action Sequence

Follow these steps to map a series of actions to a keystroke.

  1. In the Select Action dialog box, select Action Sequence in the left pane.
2413_2.gif
  1. In the right pane, click the Add button.
  1. In the right pane, under Action category, select an action, such as Send Key, from the list.
  1. Action parameters vary depending on the action selected. If required, you will be prompted for the needed information for each parameter to the right of the Action. Select or provide the Action parameter.

For example, the Send Key action requires the parameter “Key” to be identified.

  1. Repeat steps 3 and 4 for each action in the sequence until the sequence is complete.
  2. Click OK.

Troubleshooting

If you are using non-VT terminal types such as Linux Console, Wyse, SCO ANSI or BBS-ANSI, and have trouble mapping a key, contact Customer Support (https://support.microfocus.com/contact/attachmate.html) for the latest update,.

Related:

7021512: Creating a Hotspot that Opens a Web Page

Using Hotspots

A hotspots file enables you to interact with your terminal session by using the mouse instead of the keyboard. Each new terminal session includes a pointer to a default, built-in hotspots file. You can choose a different hotspots file for each session, and you can create custom hotspots files with the settings you prefer.

Typically, clicking a hotspot transmits a terminal key or command to the host, but you can also configure hotspots to open a web page, launch a macro, or perform a variety of other actions.

Creating a Hotspot to Open a Web Page

You can create a hotspot that opens a particular URL with an exact match or a variable match. An exact match configuration assigns one specific URL to the designated hotspot text. A variable match configuration enables a generic hotspot to open more than one URL, depending on the text that follows the hotspot text. (Examples follow.)

Enable Hotspots

Before setting an exact or variable matching configuration, first enable the hotspot feature and decide how you want to activate the hotspot.

  1. In Reflection, open a terminal session and log on.
  2. On the Appearance tab, click Hotspots (in the ribbon).
  3. On the Set Up Hotspot Display Settings screen:
    1. Click the check box to Enable all defined hotspots, and select a hotspot style (Button, Outline rectangle, or Not visible).
    2. Select how you want the hotspot to be activated. For example, clear the Double-click check box to open the hotspot with a single left-click.
    3. Near the bottom of the left navigation bar, click Manage Hotspots.
  4. On the Manage Hotspots screen, note the Currently selected file. Click Create a new hotspots file from an existing hotspots file.
  5. On the Create a New Hotspots File screen:
    1. Click the Custom option.
    2. Select a file. You can choose one of the defaults.
    3. Check the box to Use the new file in the current session document. (This setting makes the new hotspots file available in the current terminal session.)
    4. Click OK to open the Modify Hotspots screen.

Continue with the steps to Configure an Exact-Match Hotspot or to Configure a Variable-Match Hotspot.

Configure an Exact-Match Hotspot

An exact match configuration assigns one specific URL to the designated hotspot text. Using this feature, you can configure a hotspot to open your company’s intranet Help Desk web page or another helpful web site.

Follow the steps below to create a hotspot that maps the word Main to the Micro Focus Support web site.

  1. On the Modify Hotspots screen, in the Hotspot text field, enter main.
  2. In the Select Action drop-down menu, select Open URL.
  3. In the URL field, enter http://support.microfocus.com
  4. Select how you want the web page to open, such as in a default browser. Click OK.
  5. In the Hotspot Mapper list, select the Hotspot text, main. Click Modify.
  6. On the Hotspot Options screen:
    1. Verify that the hotspot text is entered correctly. Keep the default check boxes selected. Click OK.
    2. Click OK again to exit the Modify Hotspots screen.
  7. When prompted, enter a File name and save the hotspot file.
    1. On the Manage Hotspots screen, note the Currently selected file.
If it is not the file you just saved, click Select another hotspots file. On the Select a Hotspots File screen, click Custom, and then select the file you saved.
    1. Click OK; click OK again to exit the Manage Hotspots screen.
  1. Save the session document to preserve the hotspots file configuration.
  2. In the Reflection workspace, test the hotspot you just created.
    1. Find or type the word Main.
    2. Depending on how you configured the hotspot, click or double-click the highlighted text, Main.
    3. The web site, support.microfocus.com, should open in a new web page.

Note: In IBM terminal 3270 and 5250 sessions, hotspots are matched only in protected fields that the user cannot edit. To test the hotspot, you could send a message that includes the hotspot text (main) in the message. The hotspot text is highlighted in the displayed message. Click the text to open the web page for Micro Focus Support.

Configure a Variable-Match Hotspot

A variable-match hotspot recognizes common text in a string or phrase as an exact match. The remaining (variable) text in the string or phrase defines the exact action that will be performed, such as opening a specific URL.

For example, to create one hotspot that is capable of opening different web pages, configure a hotspot that recognizes http:// as the opening syntax of a URL. The remaining (variable) text of the URL defines which web page will open. After you type in a full URL, and click the http:// hotspot, the specific web page for that URL opens. Type a different URL, click the hotspot, and a different web page opens.

Follow this example to configure a variable-match hotspot:

  1. On the Modify Hotspots screen, in the Hotspot text field, enter http://
  2. In the Select Action drop-down menu, select Open URL.
  3. Select the check box to Use matched hotspot text for the URL. (Note: the URL field becomes unavailable.)
  4. Select how you want the web page to open, such as in a default browser. Click OK.
  5. In the Hotspot Mapper list, select the Hotspot text, http://. Click Modify.
  6. In the Hotspot Options screen, select the check box to Match until a delimiter.
  7. Verify that the Space delimiter is checked. Click OK to exit the Hotspot Options screen and click OK again to exit the Modify Hotspots screen.
  8. When prompted, enter a File name and save the file.
    1. On the Manage Hotspots screen, note the Currently selected file.
If the file is not the one you just saved, click Select another hotspots file. Click Custom, select the file you saved, and click OK.
    1. Click OK to exit the Manage Hotspots screen.
  1. Save the session document to preserve the hotspots file configuration.
  2. Test the hotspot.

In a VT terminal session document, type http:// and look for the highlighted box. Type a full URL, such as http://support.microfocus.com, and press the spacebar or Enter. (In this example, the hotspot will not activate until a space is detected.) Click the hotspot to open the web page.

In IBM 3270 and 5250 terminal session documents, hotspots are matched only in protected fields that the user cannot edit.

3270: As you type in a 3270 session document, the hotspot text will become active. After you type a full URL (followed by a space), click the hotspot to open the web page.

5250: In a 5250 session document, test the hotspot by sending a message that includes a URL. Follow these steps as you progress through the screens.

    1. From the Main Menu, enter 6 for Communications.
    2. Enter 2 for Messages.
    3. Enter 1 to Send a message.
    4. Enter message text such as, “See http://support.microfocus.com for more information.” Note: You must enter a space immediately after the URL; if a period or other character is present, the web page will not open correctly.
Enter a user name or profile to receive the message. Press Enter.
    1. On the Messages screen, enter 3 to Display messages.
    2. On the Display Messages screen, check that the user name or user profile is selected (underlined). Press Enter.
    3. The hotspot should be highlighted on the Work with Message screen. Click the hotspot to open the web page.

Troubleshooting

If the hotspot is not behaving as expected, follow these steps:

  1. Open the Manage Hotspots screen. (Another path: From the Quick Access toolbar, click the Document Settings button. Under Terminal Appearance, click Manage Hotspots.)
  2. Verify that the Currently Selected File is the one in which you saved the hotspot file. If not, click Select another hotspots file, and select the correct one.
  3. Click Modify the currently selected hotspots file.
  4. Select the Hotspot text, for example Main, in the Hotspot Mapper list. Click Modify and check the options you want to save. Click OK until you return to the Reflection workspace.
  5. Save the session document.
  6. Test the hotspot again to see if the web page opens.

Related:

7021472: Setting the Telnet Terminal Type for UNIX Hosts

Background

A UNIX host computer may use a different terminal type for connecting than Reflection uses for emulation. If you are having trouble running a UNIX host application with a Telnet connection, it is possible that the Telnet negotiation between Reflection and the host is incorrect. Since by default the Telnet terminal type is not linked to the emulation terminal type, each needs to be configured independently.

Two Terminal Types in Reflection: Telnet and Emulation

Reflection has two settings for terminal type: the Telnet terminal type, and the emulation terminal type.

Telnet Terminal Type

When Reflection makes a Telnet connection to a host computer, the Telnet protocol negotiates a terminal type with the host. UNIX hosts typically use this value to set the $TERM value of the terminal environment, but a default file such as .profile or .login can override the negotiated $TERM value. The Telnet terminal type can be configured in Reflection Desktop 16, Reflection 2014, or Reflection 2011 from Document Settings > Host Connection > Configure Connection Settings > More Settings > General tab, and in Reflection from the Connection Setup dialog box > More Settings > General tab.

Emulation Terminal Type

Reflection uses this value, configured in Reflection Desktop 16, Reflection 2014, or Reflection 2011 from Document Settings > Terminal Configuration > Select Terminal Type, and in Reflection from the Setup menu, to identify the type of terminal Reflection will emulate. The default is VT500-7. Note: Since VT500 emulation includes VT200, VT300 and VT400, you receive these levels when the emulation terminal type is set to VT500-7 or VT500-8.

Configuring the Correct Telnet Terminal Type

Follow the steps below to configure the Telnet terminal type for your host.

In Reflection Desktop 16, Reflection 2014, or Reflection 2011:

  1. If you are currently connected, disconnect your session.
  2. In the quick access toolbar, click the Document Settings icon.
  3. Under Host Connection, click Configure Connection Settings. Verify that Telnet is the Network Connection Type selected, and then click More Settings.
  4. On the General tab, in the Terminal type field, enter the Telnet terminal type for your host by selecting from the drop-down menu or typing in the correct terminal type for your UNIX or OpenVMS host computer. Click OK twice.
  5. Click Connect to make a Telnet connection to your host.
  6. Verify that the host applications are working correctly. To verify the term setting on a UNIX host, issue the set or echo $TERM command.
    • If the host applications work correctly, continue with step 7.
    • If the host applications still do not function correctly, disconnect the session. Repeat steps 2 through 6 above, using a different Telnet terminal type in step 4.
  1. In the quick access toolbar, click the Save button and save your current session document, entering a unique file name, such as the name of the host computer. Click Save.

In Reflection 14.x:

  1. If you are currently connected, disconnect by clicking the Disconnect icon on the toolbar. (Or click Connection > Disconnect.)
  2. Click Connection > Connection Setup.
  3. Select Network in the Connect Using group box and click TELNET.
  4. Click More Settings.
  5. Your next action depends on the product:
    • For Reflection for UNIX and OpenVMS and Reflection for ReGIS Graphics, in the Terminal Type field (found on the General tab), enter the Telnet terminal type for your host by selecting from the drop-down menu or typing in the correct terminal type for your UNIX or OpenVMS host computer.
    • For Reflection for HP (on the General tab), select the “Use emulation terminal ID” check box. Accept the remaining default values.

Click OK.

  1. Click Connect to make a Telnet connection to your host.
  2. Verify that the host applications are working correctly. To verify the term setting on a UNIX host, issue the set or echo $TERM command.
    • If the host applications work correctly, continue with step 8.
    • If the host applications still do not function correctly, disconnect the session. Repeat steps 2 through 7 above, using a different Telnet terminal type in step 5.
  1. Save the Telnet terminal type to your Reflection settings file:
    1. Click File > Save As to open the Save Settings dialog box.
    2. Enter a name for your settings file. You can give the settings file a unique name, such as the name of the host computer.
    3. Click Save.

Related: