Beruflich Dokumente
Kultur Dokumente
| Contents | 2
Contents
1.0 Overview.............................................................................................................. 3
Architecture........................................................................................................................................................... 3
Implementations.................................................................................................................................................... 4
Features................................................................................................................................................................. 5
2.0 Installation...........................................................................................................6
System Requirements............................................................................................................................................6
Server Install Process........................................................................................................................................... 7
Modification and Removal................................................................................................................................. 18
Licensing............................................................................................................................................................. 19
Obtaining Licenses..................................................................................................................................19
Adding, Importing, and Removing Licenses......................................................................................... 22
Validating Licenses................................................................................................................................. 23
3.0 Deployment........................................................................................................25
Sizing Requirements........................................................................................................................................... 25
Connection Strings..............................................................................................................................................26
Load Balancing................................................................................................................................................... 27
Scenario 1: Standalone GuiXT Server................................................................................................... 27
Scenario 2: GuiXT Message Server.......................................................................................................29
Scenario 3: SAP Message Server...........................................................................................................34
Scenario 4: GuiXT Message Server.......................................................................................................37
Client PC Configuration..................................................................................................................................... 40
Using GuiXT Server as a SAP Router.............................................................................................................. 41
Configuring GuiXT Server as a Message Server.............................................................................................. 43
Server Configuration...........................................................................................................................................50
sapproxy.ini............................................................................................................................................. 50
SynWatchdog...........................................................................................................................................58
5.0 Troubleshooting.................................................................................................63
Disaster Recovery............................................................................................................................................... 63
32-bit Server Recovery...........................................................................................................................63
64-bit Server Recovery...........................................................................................................................67
6.0 Appendices.........................................................................................................72
Revision History................................................................................................................................................. 72
Upgrading GuiXT Server................................................................................................................................... 73
Using SAPConsole with GuiXT Server.............................................................................................................74
SAPConsole System Requirements........................................................................................................75
Installing Server for SAPConsole.......................................................................................................... 76
Configuring GuiXT Server for SAPConsole......................................................................................... 76
Comparing SAPConsole with GuiXT Mobile....................................................................................... 76
| 1.0 Overview | 3
1.0 Overview
GuiXT Server provides a centralized mechanism to deploy GuiXT and to send updates without the necessity of
managing individual clients. Server also serves as a central repository for a customers GuiXT scripts and mimics
an SAP router in terms of deployment. Using GuiXT Server also enables you to use custom SAP solutions ona wide
variety of touch points, including iPad, iPhone, and Windows CE-based handheld devices.
The benefits provided by GuiXT Server include a zero-footprint deployment and simplified software management.
GuiXT Server also provides central deployment and maintenance for tasks such as upgrading GuiXT, updating
current implementation or changing GuiXT parameters. GuiXT Server can be used in conjunction with the Liquid UI,
Desktop, Mobile and Offline solution suites. This section includes the following topics:
Architecture
Implementations
Features
This version of the technical documentation is based on the 3.4.450.0 release of GuiXT WS Server.
Architecture
Description and explanation of how GuiXT Server is architected in relation to the other components of the WS
platform.
GuiXT Server resides on a dedicated server machine and provides a centralized home for the GuiXT WS engine and
the requisite scripts. This means that the GuiXT WS components do not need to be individually installed on local
systems - everything resides on the server. The GuiXT Server also serves as a SAProuter between the SAP ERP and
the various clients. GuiXT Server communicates with the SAP database and parses the data to and from the SAP
database so that the client can manipulate it. There are three major components:
GuiXT Server
SAP GUI (or other supported touch points, such as Liquid UI for iOS)
SAP Application Server
| 1.0 Overview | 4
GuiXT communicates with SAP through a dispatcher port. The GuiXT Server contains the scripts that provide the
customized screens and processes, which are then propagated to the various clients. The process is as follows:
1.
2.
3.
4.
All screen modifications are removed prior to any client request being forwarded to SAP. Once SAP responds to a
client request, the screen modifications are re-applied.
Implementations
Available implementations using GuiXT Server.
Currently, GuiXT Server can be deployed with the following GuiXT solutions:
| 1.0 Overview | 5
Note: Server is available only with the Professional and Enterprise editions.
GuiXT Desktop
GuiXT Mobile
GuiXT Offline
Features
Major features available with GuiXT Server.
GuiXT Server offers the following features:
Administraor Console
SynWatchdog
| 2.0 Installation | 6
2.0 Installation
Installing GuiXT Server.
This section will describe the requirements to install GuiXT Server and the process by which it will be installed on a
single system. This section covers the following topics:
System Requirements
Installing GuiXT Server
Modifying and Removing GuiXT Server
Licensing GuiXT Server
System Requirements
System requiremednts for GuiXT Server.
Before you install GuiXT Server, you must first ensure that the target system can support GuiXT Server. For
production requirements, SYjnactive recommends that you install GuiXT Server on either Windows 2003 Server or
Windows Server 2008.
Note: As GuiXT Server is a Windows-based application, it can be run on a wide variety of Windows-based
operating systems.
For all systems, Synactive recommends the following above and beyond Microsoft's system requirements:
The above requirements are for a typical implementation. However, it is also possible to use GuiXT Server in
conjunction with a Telnet server and the character-based SAPConsole UI to communicate with non-Windows based
RF handheld devices. For the system requirements for this implementation, please see the Using SAPConsole with
GuiXT Server section.
| 2.0 Installation | 7
32-bit systems
64-bit systems
32-bit Installations
The process to install the GuiXT WS Server on a 32-bit system is as follows:
1. Download the Installer package from a location specified by a Synactive Support or Sales representative. The
install package is named GuiXTServerSetup.exe.
2. Double-click the Setup.exe package. The InstallShield Wizard will start and the Welcome screen will appear. Click
Next.
3. The End User License Agreement (EULA) screen will appear. Click the I accept... checkbox and then click Next.
| 2.0 Installation | 8
| 2.0 Installation | 9
| 2.0 Installation | 10
6. The install status screen will display duing the install. When GuiXT Server has been installed, the Finish window
will display as shown below. Click Finish.
| 2.0 Installation | 11
7. The 32-bit GuiXT Server has now been successfully installed on your target system.
64-bit Installations
The process to install the GuiXT WS Server on a 64-bit system is as follows:
1. Download the Installer package from a location specified by a Synactive Support or Sales representative. The
install package is named GuiXTServerSetup_64.exe.
2. Double-click the Setup.exe package. The InstallShield Wizard will start and the Welcome screen will appear. Click
Next.
| 2.0 Installation | 12
3. The End User License Agreement (EULA) screen will appear. Click the I accept... checkbox and then click Next.
| 2.0 Installation | 13
| 2.0 Installation | 14
| 2.0 Installation | 15
6. The install status screen will display duing the install. When GuiXT Server has been installed, the Finish window
will display as shown below. Click Finish.
| 2.0 Installation | 16
7. The 64-bit GuiXT Server has now been successfully installed on your target system.
Note:
If you are using GuiXT WS, you may need to do some additional steps, as follows:
1. Go to the C:\\Program Files\Synactive Inc\GuiXTServer folder and create a new file
named guixt.sjs.
2. Consult the Configuration section of this document for directions on how to configure the GuiXT Server.
Installing as Administrator
For certain Windows systems, you must install GuiXT Server using an account that has Administrator privileges.
Affected systems are as follows:
Windows Vista
Windows Server 2008
| 2.0 Installation | 17
4. After the installation completes, navigate to the GuiXT Servwer folder. The paths are as follows:
32-bit systems: C:\Program Files\Synactive Inc\GuiXTServer
64-bit systems: C:\Program Files (x86)\Synactive Inc\GuiXTServer
5. Right-click on 'SynSerial Manager.exe' and select 'Run as Administrator' as shown below:
| 2.0 Installation | 18
| 2.0 Installation | 19
Choose an option as shown above and follow the on-screen instructions to modify or remove GuiXT Server from your
system.
Licensing
Adding, importing and validating GuiXT Server licenses.
All Synactive GuiXT WS products require a license in order to operate. This section will explain how to do the
following operations on GuiXT Server:
Note: GuiXT WS licenses do not work on GuiXT environments and vice-versa. GuiXT WS users must have
a WS-specific license.
The following topics will be covered:
Obtaining Licenses
Using and obtaining GuiXT Server licenses.
New customers will receive a valid license when you purchase GuiXT Server. This section will not cover that
process. Instead, we will focus on the process for requesting and installing new GuiXT Server licenses for an existing
implementation of GuiXT Server. The following topics will be covered:
| 2.0 Installation | 20
Obtaining licenses
Requesting Licenses
To request an additional GuiXT Server license, or to request a replacement for a soon-to-expire license, please do the
following:
1. Launch License Manager and click the Copy Host ID button on the right side of the Manager window.
2. Paste the Host ID into a text file. You will need this later on in the process.
Note: Synactive host IDs are unique - they are not the same as Microsoft host IDs and cannot be obtained
using any tool other than License Manager.
3. Click the Request New button located immediately above the Copy Host ID button.
4. You will be re-directed to the Synactive web site(http://www.guixt.com). Click the Customers link as shown
below:
| 2.0 Installation | 21
| 2.0 Installation | 22
7. Enter the number of licenses and then input the Host ID that you saved earlier.
8. Scroll down to the bottom of the page and click submit.
9. You will typically receive your new GuiXT Server license(s) in one to two business days.
10. To add the license to License Manager, please proceed to the Adding and Removing Licenses section of this
document.
Importing a license
Adding a license
Removing a license
| 2.0 Installation | 23
3. Type in the serial number that you received from Synactive and click OK. You can also launch the import process
described above by clicking the Import License File button in the bottom left corner.
4. The license will be added to the License Manager.
5. To remove a license from License Manager, highlight a license and click the Remove button.
6. The license serial number will be removed from License Manager.
Removing Licenses
To reomve a license from the License Manager, please do the following:
1. Open License Manager and highlight the license you wish to remove.
2. Click the Remove button.
3. The license serial number will be removed from License Manager.
Validating Licenses
Validating GuiXT Server licenses.
Once a license has been added to the License Manager, you can validate it to obtain the following information:
License Manager will contain the licenses for all installed Synactive products. Therefore you can view not just GuiXT
Server, but also GuiXT Designer, GuiXT WS, and GuiXT Web Server. To validate a license, please do the following:
1. Launch License Manager.
2. Click Validate.
3. The following window will display.
| 2.0 Installation | 24
4. In this window you can verify the time remaining and the actual date a license will expire.
| 3.0 Deployment | 25
3.0 Deployment
The GuiXT Server can be deployed in a number of differing configurations. The main deployments are as follows:
Liquid UI for SAP GUI
Liquid UI
Mobile
Offline
In addition to serving as a standalone server, GuiXT Server can also be configured in a load-balancing format. Load
balancing allows the load to be spread between multiple GuiXT Servers. This section covers the deployment and
load-balancing for GuiXT Server. Topics covered are as follows:
Sizing Requirements
Connection Strings
Load-balancing Scenarios
Sizing Requirements
Server sizing requirements.
The sizing requirements for the various deployment scenarios are as follows:
Number of Users
OS
100
64-bit Windows
2003 Server
64-bit Windows
2008 Server
CPU
RAM
HD Free Space
Intel quad-core or
equivalent
2 gigabytes
40 gigabytes
| 3.0 Deployment | 26
Number of Users
200
OS
64-bit Windows
2010 Server
64-bit Windows
2003 Server
64-bit Windows
2008 Server
64-bit Windows
2010 Server
CPU
RAM
HD Free Space
Intel quad-core or
equivalent
4 gigabytes
40 gigabytes
Calculating Memory
GuiXT Server typically requires 12 MB per logged on session or connection. This can be used to calculate memory
requirements for additional users. For installations where there are more than 200 users, we recommend implementing
a load-balancing solution. Please see the Load Balancing section for more information on implementing loadbalancing with GuiXT Server.
Connection Strings
Using SAP connection strings with GuiXT Server.
A connection string is the string that defines the target SAP ERP system to which GuiXT Server will connect.
The connection can either be via a message server or directly. Connection strings are found in the sapproxy.ini
configuration file and look something like the following examples:
/M/SAPMC1/S/SAPMSPRD/G/GRP_HR
/H/SAPMSPRD:3600
/H/SAPMSPRD
Connection strings are typically used when there are either multiple GuiXT servers connecting to a single or multiple
SAP ERP systems or when there are multiple SAP ERP systems involved. The following connection string types are
supported:
Connection String
Description
/H/server_name
This format is used for a single SAP application server. If a single GuiXT
Server is deployed, this format also can be used for that case as well.
/H/server_name/G/
group_name
This format is used with a single application server when user groups must
be specified.
server_name:port_number
This format is used when a single application server and the connection port
both must be specified.
/H/server_name/S/
server_name
This format is used when there is an application server (or a GuiXT server)
connecting to multiple application servers.
/M/server_name/S/
server_name/G/group_name
| 3.0 Deployment | 27
Load Balancing
Implementing load-balancing with GuiXT Server.
For scenarios in which there are more than two hundred users, Synactive recommends implementing load-balancing.
Load-balancing enables you top spread the work among two or more servers, thus reducing the load and optimizing
your results. There are four possible scenarios for deploying GuiXT Server and of these, two incorporate loadbalancing. These scenarios are as follows.
Scenario I
Scenario II
Scenario III
Scenario IV
The two GuiXT Server scenarios that incorporate load-balancing are those that include either a GuiXT Message
Server or a SAP Message Server. It is important to remember that connecting to one SAP ERP system is not
necessarily the same thing as connecting to one SAP ERP message server. Multiple application servers can be defined
to distribute the load of a single SAP system (eg. PRD) via a SAP message server. Each of the scenarios is more fully
described in the following sections.
Important: When using a load-balancing deployment such as Scenario II or Scenario IV, the same
sapproxy.ini file must reside on each individual GuiXT Server. In addition, GuiXT Message Server will
run only on a Windows Server operating system such as Windows Server 2008 - end-user systems such as
Windows 7 are not supported.
| 3.0 Deployment | 28
| 3.0 Deployment | 29
Note: Your settings may be different from the examples shown below. Please verify your settings with your
your system administrator.
SAP Logon Pad Settings
In this scenario, you will create an entry for the GuiXT Server in the SAP Logon Pad. The Logon Pad connection
settings would be as shown in the following example:
in our example, we are using the following settings for the SAP Logon Pad.
sapproxy.ini Settings
The sapproxy.ini settings in the GuiXT Server would be as follows for this deployment.
Note: Your settings may be different from the examples shown below. Please verify your settings with your
your system administrator.
[Control]
proxycount=1
[Proxy]
Listenport=xxxx (The four-digit port number that the server will use to listen for traffic from the Logon Pad.
TargetServer=your_server_name (The name of the SAP application server)
TargetServerPort=xxxx (The four-digit port nuimber that is used to connect the GuiXT Server to the SAP application
server.
GuiXT=10 (This indicates that the WS engine is being used.)
Since there is only a single GuiXT Server, there will only be one proxy, for a count of one. Our example has the
following settings.
[Control]
proxycount=1
[Proxy]
Listenport=3290
TargetServer=your_server_name
TargetServerPort=3200
GuiXT=10
| 3.0 Deployment | 30
| 3.0 Deployment | 31
Note: Your settings may be different from the examples shown below. Please verify your settings with your
your system administrator.
SAP Logon Pad Settings
In this scenario, you must create a new Groups entry in the SAP Logon Pad. To create the group entry, please do the
following:
1. Open the SAP Logon Pad and click the New Item... button.
2. The initial screen will display as shown below. Click Next.
3. From the Connection Type dropdown list, select the Group/Server Selection entry as shown below.
| 3.0 Deployment | 32
| 3.0 Deployment | 33
sapproxy.ini Settings
The sapproxy.ini settings in the GuiXT Server would be as follows.
| 3.0 Deployment | 34
Note: Your settings may be different from the examples shown below. Please verify your settings with your
your system administrator.
[Control]
Messageserver=/M/serverName/T/10
proxycount=1
[Proxy]
Listenport=3290
TargetServer=your_server_name
TargetServerPort=3200
GuiXT=10
The settings are defined as follows.
Messageserver=/M/serverName/T/10
proxycount
| 3.0 Deployment | 35
Note: Your settings may be different from the examples shown below. Please verify your settings with your
your system administrator.
| 3.0 Deployment | 36
Description: Can be any unique descriptor for the GuiXT server. In our example, we used 'My GuiXT Server'.
Application Server: The name of the GuiXT Server. In our example, we used the name 'GUIXTSVR'.
System Number: Your two-digit system number.
System ID: Your three-digit system ID.
The System Entry window in SAP is shown below with some example settings.
sapproxy.ini Settings
The sapproxy.ini settings in the GuiXT Server would be as follows. The user in our example is a member of the group
'SPACE'.
Note: Your settings may be different from the examples shown below. Please verify your settings with your
your system administrator.
[Control]
proxycount=1
[Proxy]
Listenport=3290
| 3.0 Deployment | 37
TargetServer=/M/SAPMC1/S/SAPMSPRD/G/SPACE
TargetServerPort=3600
GuiXT=10
| 3.0 Deployment | 38
| 3.0 Deployment | 39
Note: Your settings may be different from the examples shown below. Please verify your settings with
your your system administrator. In addition, keep in mind that there may be multiple groups with different
permissions, such as GRP_HR and GRP_SD. For example, the GRP_HR may only have access to applicaton
server 1, while GRP_SD may have access to application server 2.
SAP Logon Pad Settings
In this scenario, you will create a group entry for the GuiXT Server in the SAP Logon Pad. THe Logon Pad
connection settings would be as shown in the following example:
Description: Can be any unique descriptor for the GuiXT message server. In our example, we used 'My GuiXT
Server'.
Message Server: The name of the GuiXT Message Server. In our example, we used the name 'GUIXTMSSVR'.
Group: Your group name. In this example, we will use 'SPACE'.
System ID: Your three-digit system ID.
sapproxy.ini Settings
The sapproxy.ini settings in the GuiXT Server would be as follows. The user in our example is a member of the group
'SPACE'.
Note: Your settings may be different from the examples shown below. Please verify your settings with your
your system administrator. You must also remember that the same sapproxy.ini settings must be on every
GuiXT Server that connects to your message server for the load balancing to work correctly.
[Control]
proxycount=1
[Proxy]
Listenport=3290
TargetServer=/M/SAPMC1/S/SAPMSPRD/G/GRP_HR
TargetServerPort=3600
GuiXT=10
Client PC Configuration
SAPGUI for Java
Server Configuration
SynWatchdog Configuration
Client PC Configuration
Configuring SAPGUI on the client PC.
The client computer is configured via the SAP GUI system properties wizard. The system properties box for SAP
7.10 looks as shown below:
Server that the user will connect to. In our example, the
description is GuiXT Server.
Application Server
System Number
System ID
Application Server
System Number
System ID
Sapproxy.ini Entries
When GuiXT Server is being used as a SAP Router, you must also create a corresponding entry in the sapproxy.ini
file. Using the settings in our screenshot as an example, the entry in the sapproxy.ini file would look as follows.
[Control]
proxycount=1
[Proxy]
Listenport=3299
TargetServer=saprouter
TargetServerPort=saprouter
GuiXT=10
Important: When you configure GuiXT Server as a SAP Router, you must specify both the TargetServer and
TargetServerPort settings in the sapproxy.ini as 'saprouter' or the connection will fail.
You must also ensure that GuiXT is not active on any clients that you will be using in this deployment. When GuiXT
Server is deployed, all GuiXT customization is handled centrally, so you do not need to have GuiXT enabled on the
individual client systems.
You must also ensure that GuiXT is not active on any clients that you will be using in this deployment. When GuiXT
Server is deployed, all GuiXT customization is handled centrally, so you do not need to have GuiXT enabled on the
individual client systems.
SAP System Properties
The system properties box for SAP 7.10 looks as shown below:
System ID
System Number
5. Copy the sapproxy.ini file and place the exact same file on each of the GuiXT Servers that will be connecting
through the message server.
Important: If the same sapproxy.ini file does not exist on each of the GuiXT Servers, the load-balancing
configuration will not succeed.
6. Open the Windows services file with a text editor such as Notepad. This file is usually found in the following
location.
C:\Windows\System32\drivers\etc
7. At the end of the services file, type in the following entry.
sapmsGXT 3600/tcp
This entry specifies the port number and type (TCP) that the message server will use to communicate with the
SAP GUI Logon Pad. The other ports used by the GuiXT Servers to communicate are specified in the sapproxy.ini
file.
8. Open the SAP Logon Pad and click the New Item... button.
9. Select the 'Group/Server Selection' from the Connection Type drop-down list as shown below.
11. In the 'Description' field, enter a description of the connection. We will call our example 'GuiXT Message Server'.
12. In the System ID field, enter the system ID. In our example, we will use the value 'GXT'.
13. In the 'Message Server' field', enter the name of the message server. In our example, it is 'GuiXTMSSRVR', but
you should use the hostname of the system hosting the message server.
14. Now click the 'Group/Server' field. If no groups are specified, the entry will be the default 'Space' as shown below.
15. Click the Finish button. The new connection entry is now in the connection list as shown below.
16. You are now ready to start the GuiXT Servers. The message server will distribute the load amongst them as
needed.
Server Configuration
Configuring GuiXT Server.
GuiXT Server is configured by means of the sapproxy.ini file. The companion SynWatchDog service is
configured via the synwatchdog.ini file. For GuiXT configuration, please see the appropriate documentation.
The sapproxy.ini and synwatchdog.ini files will be more fully explained in the following sections.
sapproxy.ini
Explaining the sapproxy.ini configuration file.
The SAPProxy.ini file is where the you will define the server configuration parameters. It is housed in the same
directory as the GuiXT Server files. A typical sapproxy.ini file will appear as shown in the following example:
Parameters
The sapproxy.ini file contains two sections and a number of parameters, which are defined below. The two sections
are:
control
Proxy
Control
The [control] section of the sapproxy.ini file is where you will define how many servers you will be connecting to. A
sample [control] section of the sapproxy.ini file appears as follows:
The parameter contained in the [control] section of the sapproxy.ini file is explained as follows:
proxycount
Proxy
The [ProxyX] section of the sapproxy.ini file is where you will inputy the actual connection parameters of the server.
The [X] is a number indicating the proxy number for each connection. There must be a [ProxyX] section for each
server specified in the [control] section. In other words, if you set proxycount=4 in the [control] section, you must
have four [Proxy] section. These will be numbered as follows:
[Proxy1]
[Proxy2]
[Proxy3]
[Proxy4]
A sample [ProxyX] section of the sapproxy.ini file is displayed in the example below.
[control]
proxycount=1
[Proxy1]
ListenPort=3200
TargetServer=test
TargetServerPort=3200
ReservedPhysMem=25
GuiXT = 10
Options= -logtraffic:on -tracetraffic:on
The parameters contained in the [Proxy] section of the sapproxy.ini file are as follows:
ListenPort
This is the port that the GuiXT Server will listen to for
information from SAP. This should be the same as the
TargetServerPort described below.
TargetServer
TargetServerPort
ReservedPhysMem
GuiXT
Other Options
In addition to the parameters introduced above, the sapproxy.ini file can contain other parameters as well. These are as
follows:
Important:
All options can only be used separately - you cannot combine options. In other words, you can only use one
of the below options at a time.
Trace options
ITS On/Off
SAPConsole On/Off
SecureConnectPasskey=XXXX
Trace Connections
Limit Trigger
Log Traffic
Trace Traffic
Progress Indicator
Async RFC
_INTR_
When you have multiple SAP systems in the sapproxy, the [Proxy] data is as follows:
ListenPort
TargetServer
TargetServerPort
GuiXT
options
Note that the sapproxy.ini file now contains two entries - one for each SAP instance. Note that the port information
and the server name information is unique. This is important - there cannot be two identically-named instances in the
sapproxy.ini file. It is important to note that the proxy count in the [Control] section must equal the number of SAP
instances as well. For multiple instances of SAP, it is necessary to create a unique connection for each in the SAP
Logon Pad as well. Each connection instance will point to the same server, but will have a unique system number. In
the following screenshot, the server GUIXTSVR points to the local system, using the system number '10':
In the following example, the server is the same, but the system number has changed to '15'. This denotes a separate
instance of the SAP server.
SynWatchdog
SynWatchdog is a bundled utility for GuiXT Server.
The SynWatchdog is a utility that will stop and restart GuiXT Server, regardless of what state the Server might
be in. SynWatchdog can also record events and send warning emails to a system administrator. SynWatchdog is
automatically installed by the InstallShield wizard. However, SynWatchdog is not set to start automatically - it must
be manually started by a user.
Note: For information on upgrading SynWatchdog, please see the Upgrading SynWatchdog section.
SynWatchdog Actions
SynWatchdog can be configured to execute different actions for different failures. In the Services pane, SynWatchdog
can be configured to perform actions based on whether a failure is the first, second or some other failure. The
available options are as follows:
Take no action
Run a program
5. Click on the drop-down menu for each failure type and select the desired action to occur.
SynWatchdog.ini
The SynWatchdog utility configured through the SynWatchdog.ini file located in the GuiXTServer folder. A typical
SynWatchdog configuration file looks like the following example.
The SynWatchdog.ini file contains a number of parameters, which are explained as follows:
AppName
KillTimeOut
MonitorInterval
GuiXT
AdminRestart
AdminSMTPServer
AdminEmailAddress
MaxMemoryPerConnect
MaxMemoryUsage
VerboseLog
SendEmailCrash
SendEmailLowMemory
SendEmailNoResponse
NotifyInterval
Starting SynWatchdog
To start SynWatchdog, users double-click on the 'Synwatchdog-Service.bat' file located in the GuiXTServer folder. To
set SynWatchdog to start automatically, please do the following:
1. Go to Start > Run and type services.msc.
2. The Services window will appear. Scroll down to the entry for Synactive Watchdog Service.
3. In the Startup Type column, right-click and select Properties.
4. The Properties window will display. In the General tab, find the Startup drop-down menu and select 'Automatic'
and then click OK.
5. SynWatchdog will now start automatically when Windows starts.
Upgrading SynWatchdog
Upgrading the SynWatchdog component of GuiXT Server.
SynWatchdog is integrated into the latest versions of GuiXT Server. To upgrade, please do the following:
1.
2.
3.
4.
5.
6.
7.
8.
| 5.0 Troubleshooting | 63
5.0 Troubleshooting
Various techniques for resolving issues with GuiXT Server.
There will be times when it is necessary to perform troubleshooting and recovery operations on GuiXT Server. This
section will cover the following topics:
Disaster Recovery
Disaster Recovery
Recovering from a GuiXT Server failure.
All customers should have a disaster recovery plan in the event that the GuiXT Server goes down and is not
recoverable. This section will cover the process to set a disaster recovery plan in place and what files are necessary.
We assume a backup process is already in place where files are regularly backed up and can quickly be recovered to a
different server machine.
For GuiXT Server there are two possible recovery scenarios, which are as follows:
Backup
Recovery
Backup
The backup part of the recovery operation must be done before you attempt to recover GuiXT Server. To perform an
effective backup following a failure, please do the following:
1. Back up the entire GuiXT Server folder. This folder typically resides at the following location: C:\Program
Files\Synactive Inc\GuiXTServer. An example folder is shown below.
| 5.0 Troubleshooting | 64
2. Ensure that the original configuration files are included in this backup. These files are as follows:
admin.ini
sapproxy.ini
synwatchdog.ini
3. Ensure that all files are stored safely and regularly updated to be the most recent versions. This is especially
important in the case of the configuration files, as any changes that are not backed up will be lost in the event of an
un-recoverable crash.
Recovery
Once you have backed up your configuration files, you can start the recovery portion of the process. This is described
as follows:
1. Set up a backup GuiXT Server with the same server name and IP address as the main server. This is important the IP address, the name and the domain for this backup server MUST be identical to the main GuiXT Server.
2. Copy the files backed up from the main server to the replacement server.
| 5.0 Troubleshooting | 65
3. Call Synactive Support or send an email to rfi@synactive.net to request a replacement license. Synactive licenses
are based on the system's host ID, which can be obtained by clicking the 'Copy HostID' button in the Synactive
License Manager as shown below:
4. Send the HostID in the email requesting a new license and the replacement should arrive in about two business
days.
5. When the replacement license arrives go to Start > Programs > Synactive Inc > GuiXTServer
> LicenseManager and launch the License Manager (SynSerialManager.exe).
6. Then click the 'Import License File' button as shown below:
| 5.0 Troubleshooting | 66
7. Navigate to the directory where the new license is stored as shown in the following example and select the license
file, then click Open.
| 5.0 Troubleshooting | 67
Backup
Recovery
Backup
The backup part of the recovery operation must be done before you attempt to recover GuiXT Server. To perform an
effective backup following a failure, please do the following:
1. Back up the entire GuiXT Server folder. This folder typically resides at the following location: C:\Program
Files\Synactive Inc\GuiXTServer. An example folder is shown below.
| 5.0 Troubleshooting | 68
2. Ensure that the original configuration files are included in this backup. These files are as follows:
admin.ini
guixt.ini
guixt.sjs
sapproxy.ini
synwatchdog.ini
3. Ensure that all files are stored safely and regularly updated to be the most recent versions. This is especially
important in the case of the configuration files, as any changes that are not backed up will be lost in the event of an
un-recoverable crash.
Recovery
Once you have backed up your configuration files, you can start the recovery portion of the process. This is described
as follows:
| 5.0 Troubleshooting | 69
1. Set up a backup GuiXT Server with the same server name and IP address as the main server. This is important the IP address, the name and the domain for this backup server MUST be identical to the main GuiXT Server.
2. Copy the files backed up from the main server to the replacement server.
3. Call Synactive Support or send an email to rfi@synactive.net to request a replacement license. Synactive licenses
are based on the system's host ID, which can be obtained by clicking the 'Copy HostID' button in the Synactive
License Manager as shown below:
4. Send the HostID in the email requesting a new license and the replacement should arrive in about two business
days.
5. When the replacement license arrives go to Start > Programs > Synactive Inc > GuiXTServer
> LicenseManager and launch the License Manager (SynSerialManager.exe).
6. Then click the 'Import License File' button as shown below:
| 5.0 Troubleshooting | 70
7. Navigate to the directory where the new license is stored as shown in the following example and select the license
file, then click Open.
| 5.0 Troubleshooting | 71
| 6.0 Appendices | 72
6.0 Appendices
In addition to the main concepts previously introduced, there is some additional information contained in the
Appendices. The following topics are covered:
Revision History
This section of the document contains the changes made to this document since the baseline 3.4.417.0 release. Please
note that not all changes will be noted. Synactive uses the following methodology to track document revisions.
New Features
Content Corrections
Content Additions
Content Deletions
Screen captures
Change Type
Change Details
Document Version
Configuration
Content Addition
3.4.444.0
| 6.0 Appendices | 73
Document Section
Change Type
Change Details
Document Version
Configuration
Content Addition
Configuration
Content Addition
Added section on
Administration Console.
3.4.444.0
Appendices
Content Addition
3.4.436.0
Load-Balancing
Content Addition
3.4.436.0
| 6.0 Appendices | 74
6. Download the latest version of the GuiXT Server from Synactive and save it to an easily accessible location. You
will need to obtain the download link from a Synactive Sales or Support representative.
7. Launch the InstallSheild wizard and follow the on-screen instructions to install the update.
8. Open the new GuiXT Server folder and locate the sapproxy.exe file.
9. Right-click the sapproxy.exe file and select the Properties option.
10. Choose the Version tab and select the File Version option.
11. Verify that you have the correct version number.
12. Open the sapproxy.ini file and verify that the following information matches the previous sapproxy.ini
file in the GuiXTServer folder that we saved in Step 3 above.
ListenPort
TargetServer
TargetServerPort
13. Close the sapproxy.ini file and go to the Services control panel we used in Step 4.
14. Re-start the Synactive R/3 Proxy Service.
15. THe GUiXT Server is now updated to the latest version and you can begin using it.
| 6.0 Appendices | 75
Most Synactive customers use the GuiXT Mobile client for Windows-based handhelds together with GuiXT Server
to connect to Windows-based handheld devices. However, it is also possible to use GuiXT Server with non-Windows
based handheld devices such as those using SAPConsole.
Although Windows-based handheld devices are more common these days, we are aware that some customer s
may still have a need to deploy character-based devices and we will explain how to install, deploy and configure a
SAPConsole deployment in this appendix. The following topics will be covered:
System Requirements
Installation
Configuration
Telnet Server
SAPConsole
GuiXT Server
Operating System
The following Microsocft operating systems are supported for GuiXT Server.
Telnet Server
Telnet servers are not Synactive products. There are many such solutions that can be used and Synactive does not
recommend any particular solution. It is only necessary to choose a solution that can be used on the same machine as
SAPs SAPConsole UI. The Telnet server must support VT220 emulation. The Telnet servers used in this document
are as follows:
The following system requirements are based on the SLNet 2.6 Telnet server.
Server
SLNet 2.6
RAM
SAPConsole
The SAPConsole can be installed on the same machine as the Telnet server and the current system requirements are as
follows:
Operating System
| 6.0 Appendices | 76
CPU
RAM
Storage (HDD)
Supported Versions
Screen Resolution
Install SAPConsole, the Telnet server of your choice, and GuiXT Server.
On the device, open SAPLOGON and create a new connection.
Enter a name for the connection in the Description field. We recommend something like 'GuiXT Server'.
Enter the name or IP address of the GuiXT Server in the Application Server field.
Select the type of system - R/3 or R/2. Most of the time it should be R/3.
Enter the system number in the System number field.
Note: The system number is actually the listen port number as defined in the sapproxy.ini file.
| 6.0 Appendices | 77
Features
GuiXT Mobile
SAPConsole
Yes
No
Yes
Yes
Supports buttons
Yes
No
Allows disconnection
Yes
No
Yes
No
Data validation
Yes
Yes
Middleware required
No
No
Telnet required
No
Yes
Yes
No
Touchscreen support
Yes
No
Platform
GuiXT Mobile
SAPConsole
Windows CE
Yes
No
Pocket PC
Yes
No
Character-based OS
Yes
No
Tablet PC
No
No
Windows Mobile
Yes
No
Development
GuiXT Mobile
SAPConsole
No
Yes
Infrastructure
GuiXT Mobile
SAPConsole
Wi-Fi Required
Yes
Yes
Yes
Yes
Yes
No