​ 
Introduction
Embedded servers are quite scalable and can host applications that support millions of users. From HACP EE version 1.10, an embedded server (which is a part of Host On-Demand) is included along with the deployable application, to support all the functionalities of HACP EE including a standalone server.
The main advantage of having an embedded server (One Server) is that, it is not necessary to pre-install a web server in the deployment environment to work with the application.

​Introduction
The Quick-connect feature in HACP EE (Host Access Client Package Extended Edition) enables Users to connect to the host sessions and use the product as a trial version, even without Login credentials and configured page.

Introduction
The Search on Canvas feature allows Users to search for specific keywords/text in the green screen and will appear at the top of the presentation screen on the client side. The search results for a successful search is highlighted with a rectangular box.
​

This document contains a brief description of the new and updated features in the IBM HACP Extended Edition v1.10 release.
To enhance the user experience HACP Extended Edition (HACP EE) v1.10 was made with some additional features for a terminal screen. The new features are listed below:
​

1​. In the HATS admin console, select the setting ‘Enable Host Simulation Recording’.
The host simulation file that is required later to get the error screen for customization, can be obtained by enabling this option.

e)       Open the Host terminal and keep pressing Enter.
f)        When the strpccmd command gets executed (I gave the command as “Strpco” then                      “strpccmd pccmd('notepad c:\test.txt')”) below is how the screen looks:

4. Create a custom widget as follows:
         --> Right-click on Project --> New HATS --> Widget --> give the name --> Select ‘Input                     field’ (on next screen) and then click Finish.
         --> Write the below code in the class:
       (Note: This is a sample code, and can be customized as required.)
​

5. Steps to run a customized project:
a)       Click on the Host terminal and select ‘Customization’.

1. Select the radio button ‘Use a previously captured screen’ and then select the error screen for which you had already taken a screenshot.
2. Select the ‘Screen Recognition Criteria’ as below:
3. Click on ‘Show Advanced’ and select only a section of the string.
4. Enable the attribute ‘Case sensitive’.

    5.   Select a section as shown above, and then click on Next.
    6.    In the subsequent Next Screen, select the input field and then click on Finish.

b) Open  ‘Screen Customization’.
                       i.            Insert the Input field component from Palette.
                       ii.            Select the screen (as shown below) and click on Next.

                                 iii.            Select the custom widget and then click on Finish.

c)       Uncheck Host simulation from the Connections file.
d)       Make sure your customization is selected in the events. Click on Save and then Run the                application.
 
The customized screen appears as below when the application is Run:

Introduction
​Host On-Demand sessions are defined by the administrator and retrieved by the Host On-Demand client when a user accesses a Host On-Demand HTML file.
​

Introduction
​Single sign-on (SSO) is a property of access control to multiple related, yet independent, software systems. With this property, a user logs in with a network credential to gain access to any of several- related systems.
​

​Introduction
Combined-based model pages work with a combination of HTML model pages and Config-based model pages, where the host session information is defined in the configuration server and user updates are saved in the browser cache as in a HTML-based model.

When the macro runtime has selected a new current macro screen, the macro runtime immediately begins to perform the actions in the <actions> element of that macro screen. After the macro run-time has performed all the actions, the next step is to determine the next macro screen to be processed. Within a single macro screen, the macro runtime performs the actions in the order in which they occur in the <actions> element. This is the same order in which you have ordered the actions under the Action list. You are not required to create any actions for a macro screen. If there is no <actions> element specified or the <actions> element is empty, then the macro runtime goes directly to the next section of macro screen processing, which is selecting the next macro screen to be processed.
​