TECHNICAL OVERVIEW DESKTOP


Home ::  Products ::  Desktop ::  Technical Overview Desktop

Components

The GuiXT Desktop Solution Suite includes three important components that represent different aspects of GuiXT technology. Each component has a major effect on business processes, productivity, and the return on investment of any SAP implementation.

  • 1. Process Engine
    Process engine is the core component of GuiXT comprehensive solutions which streamlines business processes and creates process focused applications by using a scripting technology instead of ABAP. It is the driving engine which is 64-bit compatible of GuiXT technology to create customized user actions in SAP to alter and simplify the flow of business processes.

    • Key Differentiator
      Process engine not only creates simplified, streamlined and customized business processes, but it assists developers in forming these processes. With its recording functionality, it memorizes all user actions taken to complete a process flow which might include several modules in SAP and it transfers this memory to a script file which is called Input Script. The compiled code can either be processed in GuiXT Desktop or in GuiXT WS/64 Desktop Suite depending on the platform it gets executed. Having streamlined and packaged all the user actions needed to be done to complete a process in this particular script file, application runs the compiled code in this file in the background when the process is called. Therefore users gain an experience of simplified UI and fast data entry.

    • How It Works
      Process engine requires a license to perform; therefore it also can be called a "license component". Once this license is obtained, any process flow in SAP can be recorded by recording functionality as described above and redesigned. Process engine is designed to assist developers to create process flows. GuiXT is a technology that works on the front-end of SAP. Therefore, whenever process engine creates a process flow, it uses standard Dynpro screens as event handlers in SAP to manage the flow of user actions. Developers can modify and redesign the Input Scripts formed by the recording process based on the SAP screen design they maintain using Developer Suite (please refer to Developer Suite). All the data entered in screen elements that are created in GuiXT customized SAP screens can be used and accessed in the Input Scripting via global variables assigned to designed screen elements. This is called "the redesign of recorded Process". Input Scripts contain user actions taken in a SAP streamlined process flow. Once streamlined process is formed, it has to be called from screen scripts to initiate the flow of these user actions.

  • 2. Viewer
    Viewer is another license component in Desktop Suite. It lets developers integrate and view external documents, such as web pages and RTF documents, in special windows on GuiXT customized SAP screens.

    • Key Differentiator
      Viewer does not only display web pages or RTF documents in GuIXT customized SAP screens. It also manages the transfer of information between these documents and SAP screens.

    • How It Works
      Viewer component uses a special application programming interface in the SAPGUI client to draw RTF documents and web pages onto SAP screen. This API is called Windows API. Having dependent on this particular API, at the moment GuiXT command (view) is called in the script, a local presence of GuiXT is needed in SAPGUI client for GuiXT to draw the requested component; either web page or RTF document.


  • 3. GuiXT Server
    The GuiXT Server is an individual software component in the GuiXT Desktop Solution Suite. It enhances the management and implementation of GuiXT especially in large enterprises.
Back to Top

GuiXT Server

The GuiXT Server is a central platform that updates and deploys GuiXT runtime. SAPGUI clients receive updates from the GuiXT Server, which runs on a central machine (mimicking the functionality of an SAP router). The Server is configurable and flexible enabling you to connect to multiple back end SAP systems asynchronously.

The Server's powerful configuration sets disaster recovery, logging mechanisms, and load balancing capability—increasing process efficiency and utilizing SAP load balancing. The central deployment mechanism and platform of GuiXT Server is available in 64-bit through GuiXT Desktop Solution Suite.

The GuiXT Server can be configured to work seamlessly for both the desktop and mobile environments. It can also be configured to access and display any standard screen and custom ABAP transaction optimizing the view for a mobile environment.

GuiXT Server: Runs On 64-bit Platform
Running on a 64-bit platform through GuiXT Desktop, this solution provides a highly scalable environment for GuiXT WS applications. Multi-threading capabilities provides GuiXT Server with the best variety of these applications.

Maintaining Development
The Server uses the existing scripts that are developed for local deployment. If an organization decides to transform its structure to GuiXT Server to create a central platform for maintaining GuiXT development, they only need to install GuiXT Server on a central machine and configure it to communicate with client PCs. The existing script development for local GuiXT can be utilized within the server and the user experiences no delay in time to make this transformation. Two ways to initiate:

  • Windows Service: Install GuiXT Server as a service and once it is set to “Automatic”, it will start itself every time the machine reboots.
  • Debug Mode: Used mostly in development stage
Back to Top

Features

  • 1. Scalability
    • Disaster Recovery: GuiXT Server checks the memory usage in every step of the way and depending on the available memory, it informs the user whether there is enough memory to continue or not. Thus it maintains its consistent state.

  • 2. Ease of deployment and development
    • GuiXT Deployment: GuiXT Server initiates GuiXT engine internally to display modified screens. GuiXT is not necessarily turned on in each client PC.
    • Scripts Deployment: GuiXT Server is configured to send the development updates to end user. Development modifications are handled from a single location and end users are able to see it instantly.

  • 3. Debugging and Logging Mechanisms
    • Trace and Log traffics provide a detailed insight to the problem.

  • 4. Efficiency
    • Load Balancing Scenarios
    • GuiXT Server connects to SAP application server.
    • GuiXT Message Server connects to SAP application server.
    • GuiXT Message Server connects to SAP message server.

  • 5. Flexible for New Technological Developments
    • 64-bit Support: Technological developments provide information to be stored in higher bits and create faster execution. GuiXT Server complies with these developments and ensures high efficiency.
Back to Top

Key Differentiator

The GuiXT Server is a scalable standalone product providing a central platform for deployment and management of GuiXT applications, which can be utilized in SAPGUI, as well as other Synactive Solution Suites. For example, GuiXT Mobile and GuiXT Offline. The benefit of utilizing existing architecture for multiple solutions saves time and money by reducing training costs and virtually eliminating errors that often occur when users have to use different platforms to perform similar tasks.

Back to Top

Operation

Acting as an SAP router, the GuiXT Server sends information retrieved from SAPGUI to end users again with the help of Input Scripts.

Architecture and Topology

Load Balancing Scenarios
Load balancing is a technique used to spread work between two or more servers in order to get optimal results. This document contains four connection scenarios (with and without load balancing) using GuiXT Server.

  • Scenario 1: Uses a single GuiXT Server and no SAP message servers.
    • This creates a direct connection to the SAP server with all connections passing through the same GuiXT server.

  • Scenario 2: Uses multiple GuiXT Servers acting as one message server and no SAP message server.
    • When a user tries to log in, the message server will identify the GuiXT server with the least amount of connections and allow a connection directly with the corresponding GuiXT server to the SAP server.

  • Scenario 3: Uses one GuiXT Server and one SAP message server.
    • This creates a direct connection to the SAP message server with all connections passing through the same GuiXT server. SAP Message server decides which application server to go to.

  • Scenario 4: Uses a GuiXT message server, GuiXT server(s), and a SAP message server.
    • When a user tries to log in, the message server will identify the GuiXT server with the least amount of connections, and allow a connection directly with the corresponding GuiXT server to the SAP message server. SAP Message server decides which application server to go to.