Abstract: Methods, systems, and techniques for automatically allocating and dynamically determining icons for placement on legacy task output as part of modernizing such tasks are provided. These enhanced modernization techniques may be used for many different applications to automatically provide graphical enhancement to legacy applications in ways heretofore not pragmatically possible because of the sheer volume of menus in typical enterprise scenarios running legacy applications. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for configuring customizations to legacy tasks as part of modernizing such tasks are provided. Example embodiments of an RBMS provide tiered configuration so that end users can be provided with tools with which they can further modernize legacy tasks in ways that do not tamper with the integrity of the system. For example, in one embodiment at least two configuration levels are available: (1) an administrator level that can control and configure aspects of the RBMS such as the legacy and non-legacy tasks associated with a particular role and defining what tools will be provided to the end user level and (2) an end user level. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for role-based modernization of legacy applications are provided. Example embodiments provide a Role-Based Modernization System (“RBMS”), which enables the reorganization of (menu-based) legacy applications by role as a method of modernization and enables user access to such modernized applications through roles. In addition the RBMS supports the ability to enhance such legacy applications by blending them with non-legacy tasks and functions in a user-transparent fashion. In one embodiment, the RBMS comprises a client-side javascript display and control module and a java applet host interface and a server-side emulation control services module. These components cooperate to uniformly present legacy and non-legacy tasks that have been reorganized according to role modernization techniques.

Abstract: Methods, systems, and techniques for adding extensions to legacy tasks as part of modernizing such tasks are provided. A user can add dynamically add task extensions to an individual legacy task by configuring them, even while a task is running. Role extensions can be added to a home desktop of a role through configuration parameters. Task extensions can be made accessible to users through UI controls added as part of the modernization procedure when a legacy task data stream is received from a host computing system. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for supporting access to multiple copies of a legacy task are provided. When there are multiple copies of a task present, then instead of showing the output from a single task, the task workspace area displays task representation pictograms that represent the state and inform the user regarding each particular instance of that legacy task running on the host. The user can use the interface to perform various operations, including to start a new copy of the task, to end a copy of the task, and to select one of the copies for viewing. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for assigning hotkeys to legacy tasks as part of modernizing such tasks are provided. A user can assign a hotkey to an individual task so that the user can have instant access to a legacy or a non-legacy task without needing to navigate to “sub-” tasks of the legacy task. Hotkey access may be used with role-based modernization of legacy tasks to provide navigation to and from legacy tasks without starting and stopping sessions. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for supporting access to multiple copies of a legacy task are provided. When there are multiple copies of a task present, then instead of showing the output from a single task, the task workspace area displays task representation pictograms that represent the state and inform the user regarding each particular instance of that legacy task running on the host. The user can use the interface to perform various operations, including to start a new copy of the task, to end a copy of the task, and to select one of the copies for viewing. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for role-based modernization of legacy applications are provided. Example embodiments provide a Role-Based Modernization System (“RBMS”), which enables the reorganization of (menu-based) legacy applications by role as a method of modernization and enables user access to such modernized applications through roles. In addition the RBMS supports the ability to enhance such legacy applications by blending them with non-legacy tasks and functions in a user-transparent fashion. In one embodiment, the RBMS comprises a client-side javascript display and control module and a java applet host interface and a server-side emulation control services module. These components cooperate to uniformly present legacy and non-legacy tasks that have been reorganized according to role modernization techniques.

Abstract: Methods, systems, and techniques for automatically allocating and dynamically determining icons for placement on legacy task output as part of modernizing such tasks are provided. These enhanced modernization techniques may be used for many different applications to automatically provide graphical enhancement to legacy applications in ways heretofore not pragmatically possible because of the sheer volume of menus in typical enterprise scenarios running legacy applications. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for handling session emulation for running legacy applications/tasks in host environments using session pools are provided. These enhanced session emulation techniques may be used for many applications, including modernizing legacy applications, particularly in mid-range or mainframe host computing. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses the enhanced emulation techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for configuring customizations to legacy tasks as part of modernizing such tasks are provided. Example embodiments of a Role-Based Modernization System (“RBMS”) provide tiered configuration so that end users can be provided with tools with which they can further modernize legacy tasks in ways that do not tamper with the integrity of the system. For example, in one embodiment at least two configuration levels are available: (1) an administrator level that can control and configure aspects of the RBMS such as the legacy and non-legacy tasks associated with a particular role and defining what tools will be provided to the end user level and (2) an end user level. Example embodiments provide an RBMS, which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for adding extensions to legacy tasks as part of modernizing such tasks are provided. A user can add dynamically add task extensions to an individual legacy task by configuring them, even while a task is running. Role extensions can be added to a home desktop of a role through configuration parameters. Task extensions can be made accessible to users through UI controls added as part of the modernization procedure when a legacy task data stream is received from a host computing system. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for role-based modernization of legacy applications are provided. Example embodiments provide a Role-Based Modernization System (“RBMS”), which enables the reorganization of (menu-based) legacy applications by role as a method of modernization and enables user access to such modernized applications through roles. In addition the RBMS supports the ability to enhance such legacy applications by blending them with non-legacy tasks and functions in a user-transparent fashion. In one embodiment, the RBMS comprises a client-side javascript display and control module and a java applet host interface and a server-side emulation control services module. These components cooperate to uniformly present legacy and non-legacy tasks that have been reorganized according to role modernization techniques.

Abstract: Methods, systems, and techniques for assigning hotkeys to legacy tasks as part of modernizing such tasks are provided. A user can assign a hotkey to an individual task so that the user can have instant access to a legacy or a non-legacy task without needing to navigate to “sub-” tasks of the legacy task. Hotkey access may be used with role-based modernization of legacy tasks to provide navigation to and from legacy tasks without starting and stopping sessions. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for handling session emulation for running legacy applications/tasks in host environments using session pools are provided. These enhanced session emulation techniques may be used for many applications, including modernizing legacy applications, particularly in mid-range or mainframe host computing. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses the enhanced emulation techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for supporting access to multiple copies of a legacy task are provided. When there are multiple copies of a task present, then instead of showing the output from a single task, the task workspace area displays task representation pictograms that represent the state and inform the user regarding each particular instance of that legacy task running on the host. The user can use the interface to perform various operations, including to start a new copy of the task, to end a copy of the task, and to select one of the copies for viewing. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses these enhanced modernization techniques to provide role-based modernization of menu-based legacy applications.

Abstract: Methods, systems, and techniques for handling session emulation for running legacy applications/tasks in host environments using session pools are provided. These enhanced session emulation techniques may be used for many applications, including modernizing legacy applications, particularly in mid-range or mainframe host computing. Example embodiments provide a Role-Based Modernization System (“RBMS”), which uses the enhanced emulation techniques to provide role-based modernization of menu-based legacy applications.