GuiXTServer_WS_3.4.450.0

GuiXT Server 3.4.450.0

| Contents | 2

Contents

1.0 Overview.............................................................................................................. 3Architecture........................................................................................................................................................... 3Implementations.................................................................................................................................................... 4Features................................................................................................................................................................. 5

2.0 Installation...........................................................................................................6System Requirements............................................................................................................................................6Server Install Process........................................................................................................................................... 7Modification and Removal................................................................................................................................. 18Licensing............................................................................................................................................................. 19

Obtaining Licenses..................................................................................................................................19Adding, Importing, and Removing Licenses......................................................................................... 22Validating Licenses................................................................................................................................. 23

3.0 Deployment........................................................................................................25Sizing Requirements........................................................................................................................................... 25Connection Strings..............................................................................................................................................26Load Balancing................................................................................................................................................... 27

Scenario 1: Standalone GuiXT Server................................................................................................... 27Scenario 2: GuiXT Message Server.......................................................................................................29Scenario 3: SAP Message Server...........................................................................................................34Scenario 4: GuiXT Message Server.......................................................................................................37

4.0 Server Configuration........................................................................................40Client PC Configuration..................................................................................................................................... 40Using GuiXT Server as a SAP Router.............................................................................................................. 41Configuring GuiXT Server as a Message Server.............................................................................................. 43Server Configuration...........................................................................................................................................50

sapproxy.ini............................................................................................................................................. 50SynWatchdog...........................................................................................................................................58

5.0 Troubleshooting.................................................................................................63Disaster Recovery............................................................................................................................................... 63

32-bit Server Recovery...........................................................................................................................6364-bit Server Recovery...........................................................................................................................67

6.0 Appendices.........................................................................................................72Revision History................................................................................................................................................. 72Upgrading GuiXT Server................................................................................................................................... 73Using SAPConsole with GuiXT Server.............................................................................................................74

SAPConsole System Requirements........................................................................................................75Installing Server for SAPConsole.......................................................................................................... 76Configuring GuiXT Server for SAPConsole......................................................................................... 76Comparing 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 ofmanaging individual clients. Server also serves as a central repository for a customer’s GuiXT scripts and mimicsan SAP router in terms of deployment. Using GuiXT Server also enables you to use custom SAP solutions ona widevariety 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, updatingcurrent 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.

ArchitectureDescription and explanation of how GuiXT Server is architected in relation to the other components of the WSplatform.

GuiXT Server resides on a dedicated server machine and provides a centralized home for the GuiXT WS engine andthe requisite scripts. This means that the GuiXT WS components do not need to be individually installed on localsystems - everything resides on the server. The GuiXT Server also serves as a SAProuter between the SAP ERP andthe various clients. GuiXT Server communicates with the SAP database and parses the data to and from the SAPdatabase 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

The architecture is depicted as follows:

| 1.0 Overview | 4

GuiXT communicates with SAP through a dispatcher port. The GuiXT Server contains the scripts that provide thecustomized screens and processes, which are then propagated to the various clients. The process is as follows:

1. Client makes a request to SAP.2. GuiXT Server parses the request, removes any screen modifications and forwards it to SAP.3. SAP will respond to the request, usually via Port 00.4. Web Server receives data from SAP, re-applies any screen modifications and forwards the SAP response to client

through the dispatcher port.

All screen modifications are removed prior to any client request being forwarded to SAP. Once SAP responds to aclient request, the screen modifications are re-applied.

ImplementationsAvailable implementations using GuiXT Server.

Currently, GuiXT Server can be deployed with the following GuiXT solutions:

• Liquid UI for iOS

| 1.0 Overview | 5

Note: Server is available only with the Professional and Enterprise editions.

• Liquid UI for Android

Note: Server is available only with the Professional and Enterprise editions.

• GuiXT Desktop• GuiXT Mobile• GuiXT Offline

FeaturesMajor features available with GuiXT Server.

GuiXT Server offers the following features:

• Administraor Console• SynWatchdog

These features will be more fully explained later in this document.

| 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 asingle system. This section covers the following topics:

• System Requirements• Installing GuiXT Server• Modifying and Removing GuiXT Server• Licensing GuiXT Server

System RequirementsSystem requiremednts for GuiXT Server.

Before you install GuiXT Server, you must first ensure that the target system can support GuiXT Server. Forproduction requirements, SYjnactive recommends that you install GuiXT Server on either Windows 2003 Server orWindows Server 2008.

Note: As GuiXT Server is a Windows-based application, it can be run on a wide variety of Windows-basedoperating systems.

For all systems, Synactive recommends the following above and beyond Microsoft's system requirements:

• RAM: 1GB (3GB or above recommended)

Server System Requirements

To install the host server OS, the following requirements must be satisfied:

Windows 2003 Server • CPU: Intel Pentium/AMD K6 133MHz or above(550MHz recommended)

• RAM:128MB or above (256MB recommended)• HDD:3GB free space or above• Browser: Internet Explorer 7 or above; Firefox 3.0 or

above• SAP GUI: 3.0 or above

Windows Server 2008 R2 • CPU: 1.4GHz (x64) single-core or 1.3GHz dual-coreprocessor

• RAM: 512MB (8GB recommended)• HDD: 32GB• Browser: Internet Explorer 7 or above; Firefox 3.0 or

above• SAP GUI: 3.0 or above

The above requirements are for a typical implementation. However, it is also possible to use GuiXT Server inconjunction with a Telnet server and the character-based SAPConsole UI to communicate with non-Windows basedRF handheld devices. For the system requirements for this implementation, please see the Using SAPConsole withGuiXT Server section.


Server Install ProcessInstalling GuiXT Server with the InstallShield Wizard.

There are two processes for installation, as follows:

• 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. Theinstall package is named ‘GuiXTServerSetup.exe’.

2. Double-click the Setup.exe package. The InstallShield Wizard will start and the Welcome screen will appear. ClickNext.

3. The End User License Agreement (EULA) screen will appear. Click the I accept... checkbox and then click Next.


4. The Destination Folder screen will appear. Click Next.


5. The Ready To Install screen will appear. Click Install.


6. The install status screen will display duing the install. When GuiXT Server has been installed, the Finish windowwill display as shown below. Click Finish.


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. Theinstall package is named ‘GuiXTServerSetup_64.exe’.

2. Double-click the Setup.exe package. The InstallShield Wizard will start and the Welcome screen will appear. ClickNext.


3. The End User License Agreement (EULA) screen will appear. Click the I accept... checkbox and then click Next.


4. The Destination Folder screen will appear. Click Next.


5. The Ready To Install screen will appear. Click Install.


6. The install status screen will display duing the install. When GuiXT Server has been installed, the Finish windowwill display as shown below. Click Finish.


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 filenamed 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

To install GuiXT Server as an Administrator, please do the following:

1. Log out of SAP and close all SAP windows including the Logon Pad.2. Log into the target machine as Administrator. GuiXT Server requires full Administrator rights in order to install

correctly.3. 3. Right-click on the setup file and select 'Run as Administrator' as shown below:


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:


6. The License Manager will launch. Click Add.7. The license will be added to the License Manager. Click Apply and close the License Manager.8. The license is now installed and GuiXT Server is ready to use.

Modification and RemovalModifying and removing GuiXT Server.

The InstallShield Wizard can also be used to repair or remove the GuiXT Server once it is installed to repair orremove, simply launch the Installer. The following screen will appear, from which users can choose to repair, modifyor remove GuiXT Server:


Choose an option as shown above and follow the on-screen instructions to modify or remove GuiXT Server from yoursystem.

LicensingAdding, 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 thefollowing operations on GuiXT Server:

Note: GuiXT WS licenses do not work on GuiXT environments and vice-versa. GuiXT WS users must havea WS-specific license.

The following topics will be covered:

• Obtaining Licenses on page 19• Adding, Importing, and Removing Licenses on page 22• Validating Licenses on page 23

Obtaining LicensesUsing and obtaining GuiXT Server licenses.

New customers will receive a valid license when you purchase GuiXT Server. This section will not cover thatprocess. Instead, we will focus on the process for requesting and installing new GuiXT Server licenses for an existingimplementation of GuiXT Server. The following topics will be covered:

• Using License Manager


• Obtaining licenses

Using License Manager

As previously noted, you must have a valid license for GuiXT Server to function. GuiXT Server licenses are managedwith a tool called License Manager, which is included with GuiXT Server. To launch License Manager, please do thefollowing:

1. Go to Start > Programs > Synactive Inc > GuiXTServer > License Installation.2. The License Manager will launch and display as shown below:

Requesting Licenses

To request an additional GuiXT Server license, or to request a replacement for a soon-to-expire license, please do thefollowing:

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 obtainedusing 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:

http://www.guixt.com


5. Choose the Production License link.6. The license request form will display as shown below. Enter your personal or corporate information and then

scroll down to the Server section.


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.

Adding, Importing, and Removing LicensesAdding, importing and removing GuiXT Server licenses.

This section will explain how to do the following actions in License Manager:

• Importing a license• Adding a license• Removing a license

Importing GuiXT Server Licenses

Once you receive your GuiXT Server license from Synactive, you must import it into License Manager. To import alicense, please do the following:

1. Locate the license file you received from Synactive. It will be in a .SY3 format.2. Launch License Manager (Start > Programs > Synactive Inc > GuiXTServer >License

Installation).3. Click the Import License FIle at the bottom of the column of buttons on the right side of the License Manager

window.4. Use the WIndows browse utility to browse to the license file you received from Synactive.5. Select the license file you wish to use and then click the Open button in the Windows file open utility.6. The file will be imported into the License Manager


7. Click Apply to apply the license to your GuiXT Server.8. Proceed to the Validate section below.

Manually Adding Licenses

In addition to importing licenses as described above, you can also manually add licenses into License Manager bydoing the following.

1. Open the License Manager and click Add.2. A window will display as shown below:

3. Type in the serial number that you received from Synactive and click OK. You can also launch the import processdescribed 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 LicensesValidating GuiXT Server licenses.

Once a license has been added to the License Manager, you can validate it to obtain the following information:

• See how much time is remaining on a license• See the exact date when the license will expire

License Manager will contain the licenses for all installed Synactive products. Therefore you can view not just GuiXTServer, 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.


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 The GuiXT Server provides a centralized deploymentand maintenance for a GuiXT environment as well asmimicking a SAProuter. The scripts themselves canreside anywhere - some common storages are localdirectories, SAP web repositories or network shares. TheSAP GUI client resides on a desktop system within thelocal network.

Liquid UI The GuiXT Server provides the same role as in theLiquid UI for SAP GUI deployment, but also servesas a communications router between the iOS-baseddevice and the SAP ERP system. In this implementation,the GuiXT Server will deliver customized screens andtransactions via the Liquid UI for iOS or the Liquid UIfor Android client.

Mobile The GuiXT Server provides the same role as in theLiquid UI deployment.

Offline The GuiXT Server provides the same role as in theLiquid UI for SAP GUI deployment, but also servesas a communications router between the iOS-baseddevice and the SAP ERP system. In this implementation,the GuiXT Server will serve as the middleman insynchronizing data between the OFfline client on alaptop or a handheld device (e.g. a scangun) and the SAPERP system.

In addition to serving as a standalone server, GuiXT Server can also be configured in a load-balancing format. Loadbalancing allows the load to be spread between multiple GuiXT Servers. This section covers the deployment andload-balancing for GuiXT Server. Topics covered are as follows:

• Sizing Requirements• Connection Strings• Load-balancing Scenarios

Sizing RequirementsServer sizing requirements.

The sizing requirements for the various deployment scenarios are as follows:

Number of Users OS CPU RAM HD Free Space

100 • 64-bit Windows2003 Server

• 64-bit Windows2008 Server

Intel quad-core orequivalent

2 gigabytes 40 gigabytes


Number of Users OS CPU RAM HD Free Space• 64-bit Windows

2010 Server

200 • 64-bit Windows2003 Server



Intel quad-core orequivalent

4 gigabytes 40 gigabytes

Calculating Memory

GuiXT Server typically requires 12 MB per logged on session or connection. This can be used to calculate memoryrequirements for additional users. For installations where there are more than 200 users, we recommend implementinga load-balancing solution. Please see the Load Balancing section for more information on implementing load-balancing with GuiXT Server.

Connection StringsUsing 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.iniconfiguration file and look something like the following examples:

• /M/SAPMC1/S/SAPMSPRD/G/GRP_HR• /H/SAPMSPRD:3600• /H/SAPMSPRD

The components of the connection string are defined as follows:

• H: Defines the actual SAP system if no message server is used.• M: Defines the SAP message server if one is present. In this case, the message server would be 'SAPMC1'.• S: Defines the actual SAP ERP system to be targeted if a message server is deployed. In the example, the SAP

system would be 'SAPMSPRD'.• G: DEfines the group that will have access. In our example, the group is 'GRP_HR'.

Connection strings are typically used when there are either multiple GuiXT servers connecting to a single or multipleSAP ERP systems or when there are multiple SAP ERP systems involved. The following connection string types aresupported:

Connection String Description

/H/server_name This format is used for a single SAP application server. If a single GuiXTServer 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 mustbe specified.

server_name:port_number This format is used when a single application server and the connection portboth 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

This format is used when a SAP message server is connecting to multipleSAP application servers and the user's group must be defined.


Load BalancingImplementing 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 optimizingyour results. There are four possible scenarios for deploying GuiXT Server and of these, two incorporate load-balancing. These scenarios are as follows.

Scenario I This scenario incorporates a single, standalone GuiXTServer and a single SAP Application server.

Scenario II This scenario involves a GuiXT Message Server and asingle SAP Application Server.

Scenario III This scenario includes a single, standalone GuiXT Serverand a SAP Message Server comunicating with multipleSAP Application Servers.

Scenario IV This scenario incorporates a GuiXT Message Serverand a SAP Message Server. The GuiXT Message Servercommunicates with multiple GuiXT Servers and the SAPMessage Server similarly communicates with multipleSAP Application Servers.

The two GuiXT Server scenarios that incorporate load-balancing are those that include either a GuiXT MessageServer or a SAP Message Server. It is important to remember that connecting to one SAP ERP system is notnecessarily the same thing as connecting to one SAP ERP message server. Multiple application servers can be definedto distribute the load of a single SAP system (eg. PRD) via a SAP message server. Each of the scenarios is more fullydescribed in the following sections.

Important: When using a load-balancing deployment such as Scenario II or Scenario IV, the samesapproxy.ini file must reside on each individual GuiXT Server. In addition, GuiXT Message Server willrun only on a Windows Server operating system such as Windows Server 2008 - end-user systems such asWindows 7 are not supported.

Scenario 1: Standalone GuiXT ServerUsing a single GuiXT Server with a single SAP application server.

In this scenario, there will be a single SAP application server and a single GuiXT Server. No load-balancing isinvolved and the architecture is as depicted in the diagram below:



Note: Your settings may be different from the examples shown below. Please verify your settings with youryour 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 connectionsettings would be as shown in the following example:

• Application Server: serverName• System ID: XXX (Your three-digit system ID)• System Number: XX (Your two-digit system number)

in our example, we are using the following settings for the SAP Logon Pad.

• Application Server: MyServer• System ID: XXX• System Number: 90

sapproxy.ini Settings

The sapproxy.ini settings in the GuiXT Server would be as follows for this deployment.


[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 applicationserver.

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 thefollowing settings.

[Control]

proxycount=1

[Proxy]

Listenport=3290

TargetServer=your_server_name

TargetServerPort=3200

GuiXT=10

Scenario 2: GuiXT Message ServerUsing a GuiXT Message Server and multiple GUiXT Servers.

The second scenario would feature a single message server in conjunction with multiple GuiXT Servers. A GuiXTServer can also function as a message server. This configuration will identify the GuiXT Server with the fewestconnections or lightest load and will connect directly to that server. The architecture would appear as depicted in thediagram below:





In this scenario, you must create a new Groups entry in the SAP Logon Pad. To create the group entry, please do thefollowing:

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.


4. The following screen will display.


Enter the connection setting parameters as follows:

• Description: A description of the server.• System ID: XXX (Your three-digit system ID)• Message Server: The name of the GuiXT Server. In our example, we used the name 'GuiXT_msgSvr_Name'.• SAPRouter: The name you entered in the previous field. in our example, this is 'GuiXT_msgSvr_Name'.• Group/Server: The group name• System Number: XX (Your two-digit system number)

5. Click the Next button.6. Click the Finish button to create the new connection.7. Once you have created the Logon Pad connection, go to C:\WINDOWS\system32\drivers\etc

\services and add the following line to the bottom of the services file:

sapmsGXT 3600/tcp

This line instructs the server to use port 3600 and the TCP protocol.

Note: Your entry may be different - check with your system administrator.


The sapproxy.ini settings in the GuiXT Server would be as follows.



[Control]

Messageserver=/M/serverName/T/10

proxycount=1

[Proxy]

Listenport=3290

TargetServer=your_server_name


GuiXT=10

The settings are defined as follows.

Messageserver=/M/serverName/T/10 The messageserver string contains several components,which are as follows.

• /M/: This specifies the server where the GuiXTmessage server is actually running. In our example,the server name is 'your_server_name'.

• /T/: This specifies the time intervals in seconds forthe individual GuiXT Servers to contact the messageserver. in our example, the GuiXT Servers willcontact the message server every ten seconds.

• /G/: This specifies the group name. Our example isnot using groups.

proxycount This exntry defines the individual GuiXT Servers. Thereshould be one entry for each individual GuiXT Server. Inour example, there is only a single server, so there will beonly one proxy. The proxy settings are defined in moredetail in the sapproxy.ini section of this document, butwe will briefly list them here as well.

• Listenport: This specifies the port on which yourclient is communicating with the messsage server.

• TargetServer: This specifies the name of the GuiXTServer for this proxy.

• TargetServerPort: This specifies the port thatthe GuiXT Server is using to connect to the SAPapplication server

• GuiXT: This specifies if you are using the WSengine. GuiXT=10 means you are using the GuiXTengine; GuiXT=1 means you are not using the WSengine.

Scenario 3: SAP Message ServerUsing a GuiXT Server with a SAP Message Server.

In this scenario, there is a single GuiXT Server and a single SAP message server. The message server may beconnected to multiple SAP databases and will distribute the connections as required based on the group identities ofthe users. A single GuiXT server can also act as a message server, as shown in the previous scenario. The architectureis as follows:





In this scenario, you will crate an entry for the GuiXT Server in the SAP Logon Pad. THe Logon Pad connectionsettings would be as shown in the following example:

• 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.


The sapproxy.ini settings in the GuiXT Server would be as follows. The user in our example is a member of the group'SPACE'.


[Control]

proxycount=1

[Proxy]

Listenport=3290


TargetServer=/M/SAPMC1/S/SAPMSPRD/G/SPACE


GuiXT=10

Scenario 4: GuiXT Message ServerUsing a GuiXT Message Server and multiple GUiXT Servers with a SAP Message Server.

In this scenario, there is a single GuiXT message server communicating with multiple GuiXT servers and a singleSAP message server. In this configuration, the GuiXT Message Server balances multiple GuiXT Servers, but canconnect only to a single SAP ERP system - the SAP message server. The message server takes care of connecting tothe various SAP application servers. This architecture would appear as shown below: The architecture is as follows:



Note: Your settings may be different from the examples shown below. Please verify your settings withyour your system administrator. In addition, keep in mind that there may be multiple groups with differentpermissions, such as GRP_HR and GRP_SD. For example, the GRP_HR may only have access to applicatonserver 1, while GRP_SD may have access to application server 2.


In this scenario, you will create a group entry for the GuiXT Server in the SAP Logon Pad. THe Logon Padconnection 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 GuiXTServer'.

• 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.•

Once you have created the Logon Pad connection, go to C:\WINDOWS\system32\drivers\etc\servicesand add the following line to the bottom of the services file:

sapmsGXT 3600/tcp

This line instructs the server to use port 3600 and the TCP protocol.

Note: Your entry may be different - check with your system administrator.


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 youryour system administrator. You must also remember that the same sapproxy.ini settings must be on everyGuiXT 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


GuiXT=10

| 4.0 Server Configuration | 40

4.0 Server Configuration

This section covers the configuration of a GuiXT Server. It consists of the following elements:

• Client PC Configuration• SAPGUI for Java• Server Configuration• SynWatchdog Configuration

Client PC ConfigurationConfiguring SAPGUI on the client PC.

The client computer is configured via the SAP GUI system properties wizard. The system properties box for SAP7.10 looks as shown below:

This system properties dialog box contains the following information:

Description The description can be literally anything. Typically,this is either the name of the SAP server or the GuiXT


Server that the user will connect to. In our example, thedescription is ‘GuiXT Server’.

Application Server The application server is the name of the applicationserver the user will connect to. In our example, theapplication server is named ‘TEST’.

System Number The system number is the system number of theapplication server. In most real-world cases, this will be‘00’ as in our example.

System ID The System ID is the SAP box to which the Server willbe connecting. The System ID can be different dependingon your corporate environment. Some examples mightbe ‘DEV’ for development, ‘QAS’ for regressiontesting or ‘PRD’ for production. Each of these can havespecific data and restrictions associated. For example,development might be prohibited in PRD so as not to riskdamaging the production system or data.

SAP Router String The SAP Router string contains the actual IP address ofthe application server. However, you will only enter aSAP Router string if the GuiXT Server will be used asa SAP Router. Using GuiXT Server as a SAP Router isexplained below. Leave this blank for a standard GuiXTServer connection.

Using GuiXT Server as a SAP RouterGuiXT Server can also be used as a SAP Router. To designate the GuiXT Server as a SAPRouter, you must enter aSAP Router string into the SAP System Properties when you create your connection on the client system. The systemproperties box for SAP 7.10 looks as shown below:



Description The description can be literally anything. Typically,this is either the name of the SAP server or the GuiXTServer that the user will connect to. In our example, thedescription is ‘GuiXT Server’.

Application Server The application server is the name of the applicationserver the user will connect to. In our example, theapplication server is named ‘TEST’.


System ID The System ID is the SAP box to which the Serverwill be connecting. The System ID can be differentdepending on the corporate environment. Some examplesmight be ‘DEV’ for development, ‘QAS’ for regressiontesting or ‘PRD’ for production. Each of these can havespecific data and restrictions associated. For example,development might be prohibited in PRD so as not to riskdamaging the production system or data.


SAP Router String The SAP Router string contains the actual IP addressof the application server. In our example, the address is’10.0.0.42’. Connection strings are explained in moredetail above.

Sapproxy.ini Entries

When GuiXT Server is being used as a SAP Router, you must also create a corresponding entry in the sapproxy.inifile. 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 andTargetServerPort 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 GuiXTServer is deployed, all GuiXT customization is handled centrally, so you do not need to have GuiXT enabled on theindividual client systems.

Configuring GuiXT Server as a Message ServerAs previously introduced in the Load Balancing section, you can configure GuiXT Server as a message server. Thisenables you to deploy multiple GuiXT Servers and spread the load evenly amongst them. To configure GuiXT Serveras a message server, you must first comnfigure your sderver via the sapproxy.ini file and then enter the appropriatesettings into the SAP System Properties when you create your connection on the client system.

Important: GuiXT Server must run on a Windows-based Server OS in order for it to run as a messageserver. Only Windows Server operating systems are currently supported.

Sapproxy.ini Entries

When GuiXT Server is being used as a message server, you must create an entry in the sapproxy.ini file. Our exampleentry in the sapproxy.ini file would look as follows.

[Control]

Messageserver=/M/GuiXTMSSRVR/T/10

proxycount=1

[Proxy]

Listenport=3290

TargetServer=[servername]


GuiXT=10


You must also ensure that GuiXT is not active on any clients that you will be using in this deployment. When GuiXTServer is deployed, all GuiXT customization is handled centrally, so you do not need to have GuiXT enabled on theindividual client systems.

SAP System Properties

The system properties box for SAP 7.10 looks as shown below:


Description The description can be literally anything. Typically,this is either the name of the SAP server or the GuiXTServer that the user will connect to. In our example, thedescription is ‘GuiXT Message Server’.

System ID The System ID is the SAP box to which the Server willbe connecting. The System ID is typically a three-digitcode and can be different depending on the corporateenvironment. Some examples might be ‘DEV’ fordevelopment, ‘QAS’ for regression testing or ‘PRD’for production. Each of these can have specific data andrestrictions associated. For example, development mightbe prohibited in PRD so as not to risk damaging the


production system or data. In our example, we will usethe ID 'GXT'.

Message Server The message server is the name of the GuiXT messageserver that you will connect to. In our example, themessage server is named ‘GuiXTMSSRVR’, but youshould use the hostname of the machine hosting theMessage Server.


Setting Up a GuiXT Message Server

To configure a GuiXT message server, please do the following.

Note: You must configure your server's sapproxy.ini file before you configure the connection in the SAPLogon pad, otherwise you will not be able to successfullty create the group connection in the SAP Logon Pad.

1. First, open the sapproxy.ini file on the message server. This file will typically be located in the following directory.

C:\Program Files\Synactive Inc\GuiXTServer2. Enter the following information.

[control] Messageserver=/M/GXT/T/10 proxycount=1

This information is defined as follows. The proxycount specifies how many servers are being defined. Since this isa message server, only a single entry will be defined in the sapproxy.ini file. The messageserver entry specifies themessage server itself. The '/M/' parameter defines the name of the message server. In our example it is 'GXT'. The'/T/' parameter defines the interval for comunications between the message server and the other GuiXT Servers.In this case we are connecting directly to a single SAP system, so we will not define any group parameters in theconnection string.

3. In the sapproxy.ini file, enter the following information.

[Proxy 1] ListenPort=3210 TargetServer=GXT TargetServerPort=3200 GuiXT=10

The above information is defined as follows. The ListenPort is the port used by the GuiXT Servers to listen fordata from the message server. The TargetServer value is the name of the SAP Application Server that the GuiXTServers will connect to. The TargetServerPort is the port used by the GuiXT Servers and the SAP ApplicationServer to communicate with each other.

4. Save your changes and close the file. You will need the hostname of the system where the message server resides.To find this information, open a command promnpt and type the following.

ipconfig /all

The command prompt should display the system name as shown in the example below.


5. Copy the sapproxy.ini file and place the exact same file on each of the GuiXT Servers that will be connectingthrough the message server.

Important: If the same sapproxy.ini file does not exist on each of the GuiXT Servers, the load-balancingconfiguration will not succeed.

6. Open the Windows services file with a text editor such as Notepad. This file is usually found in the followinglocation.

C:\Windows\System32\drivers\etc7. 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 theSAP GUI Logon Pad. The other ports used by the GuiXT Servers to communicate are specified in the sapproxy.inifile.

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.


10. The following screen will display.


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 asneeded.

Server ConfigurationConfiguring GuiXT Server.

GuiXT Server is configured by means of the sapproxy.ini file. The companion SynWatchDog service isconfigured 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.iniExplaining the sapproxy.ini configuration file.

The SAPProxy.ini file is where the you will define the server configuration parameters. It is housed in the samedirectory 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 sectionsare:

• control• Proxy

Control

The [control] section of the sapproxy.ini file is where you will define how many servers you will be connecting to. Asample [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 This parameter defines how many SAP ERP systems theGuiXT Server will connect to. In our example, there isonly a single SAP system involved. Client sites may haveup to four proxies.


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 eachserver specified in the [control] section. In other words, if you set proxycount=4 in the [control] section, you musthave 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=3200TargetServer=testTargetServerPort=3200ReservedPhysMem=25GuiXT = 10Options= -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 forinformation from SAP. This should be the same as theTargetServerPort described below.

TargetServer This is where the SAP ERP system is specified. Userscan either use a name, as in the preceding example (eg.‘juneau’) or a connection string. For more informationabout connection strings, please see the ConnectionStrings section.

TargetServerPort This is the system ID of the SAP ERP system to whichthe GuiXT Server will connect. The system ID ispreceded by the number ‘32’. So if the SAP ERP systemID is ‘00’, the TargetServer number will be ‘3200’. Asample entry is shown below.

ReservedPhysMem This entry designates the amount of actual physicalmemory that will be verified for any subsequent launchesof the sapproxy.exe. Sapproxy always checks thememory before launching and norm,ally requires a largeamount of free memory to launch. This is a useful optionfor users with smaller or more limited systems, as it tellsSapproxy that only the specified amount of memoryneeds to be checked in order to luanch sapproxy. Asample entry specifying 25M of memory is shown below.

ReservedPhysMem=25

GuiXT This is where you will specify whether or not the GuiXTinstance is or is not WS. If the implementation is not WS,the number will be ‘1’. If it is WS, the number will be‘10’.


Other Options

In addition to the parameters introduced above, the sapproxy.ini file can contain other parameters as well. These are asfollows:

Important:

All options can only be used separately - you cannot combine options. In other words, you can only use oneof the below options at a time.

Trace options You can add trace options to the sapproxy.ini file. Traceoptions assist in debugging GuiXT Server. The syntax isas follows:

options=-logtraffic

This option is a Boolean that can be set to either 'on' or'off'. Logtraffic will trace each and every network packet,writing the results as a log file. Logs will use the namingconvention 'TL_*'. The 'logtraffic' option is added to theSapproxy.ini under the keyword 'Options=logtraffic:on/off'. The default setting for logtraffic is 'off'.

To add trace options, please do the following:

1. Open the Sapproxy.ini in a supported text editor. Weusually use Notepad.

2. Add the following keyword to the Sapproxy.ini file:options=-logtraffic:on. This keyword will trace eachand every network packet, writing the results as logfiles. The logs will use the naming convention: TL_*

3. Once the log files are generated, send them toSynactive for review by a Support specialist.

Easy Access On/Off This flag turns off the automatic addition of theNO_EASYACCESS flag. The NO_AEASYACCESSflag is used to eliminate the easy access bit in the DIAG.The default setting is 'on'. The option is written as shownbelow

-add_no_easyaccess:off

ITS On/Off This is used to disable the removal of the ITS flag. ITSwas the predecessor to NetWeaver. GuiXT was able torun in ITS and this flag was used to prevent the flag frombeing removed. Since ITS is no longer common, thisflag is unlikely to be used in most scenarios. The defaultsetting is 'on' and it is written as follows:

-remove_its:off

SAPConsole On/Off This flag is used to turn the sapconsole detection onor off, causing the appropriate handling of sapconsolepackets to occur. When the flag is set to 'on' thensapconsole mode is turned on. The default setting is'auto'. It is written as follows:

-sapconsole:off/on

SecureConnectPasskey=XXXX This setting is used to turn on the Secure Connect featurefor Liquid UI. The passphrase may be anywhere from


X to XX characters long and may contain alphabeticcharacters, numbers, and symbols. The syntax is asshown below.

SecureConnectPasskey=<passphrase>

To use this setting, please do the following.

1. On the GuiXT Server, open thesapproxy.ini file and type in the following:SecureConnectPasskey=test.

2. Savwe your changes and close the sappro0xy.ini file.3. On your iOS device, open the Connection List and

select the connection you wish to use.4. In the 'Secure Connect' filed, type the same

passphrase you entered on the GuiXT Server.5. Click the Save button to save your changes.6. In the COnnection List, click Done.7. The connection will launch securely. YOu can tell

that the connection is secure because the SAP systemID will be green.

Swap Easy Access On/Off This option is used to turn off the automatic swapping of'Easy Access'. The default setting is 'on'. THe option iswritten as shown below:

-swap_easyaccessoff

Send Direct Return On/Off This option turns on the process of sending screens fromserver to client during ‘Input Script’ processing. Thedefault state is 'off' but please note that this flag cannotbe turned on if a given connection is determined to befrom sapconsole. THis option is written as follows:

-senddirectreturn:on

Trace Connections This option is used to trace and display information abouteach connection. The default setting is 'off'. THe optionis written as shown below:

-traceconnections:on

Limit Trigger This option is used to turn off the limit trigger. This isexplained in more detail in the Server Debugging section.The option is written as follows:

-limit_trigger:off

Log Traffic This option is used to log each packet sent and receivedby the server. The default setting is 'off'. The option iswritten as in the example below:

-logtraffic:on

Trace Traffic This option is used to trace and log each network packet.The log can then be used to replay back the R/3 networkflows. The default setting is 'off'. The option is written asfollows:

-tracetraffic:on


Progress Indicator This option turns off the progress indicator during InputScript processing. The default setting is 'on', and it iwwritten as shown below:

-progress_indicator:off

Async RFC This option is used to suppress addition of this flag tothe SAP application server. If active, the SAP serverwill send all RFCs and wait for response. It is written asfollows:

-async_rfc:off

Remove Menu Entries This option will remove menu entries sent to client whenit is turned on. It is used only for sapconsole mode andthe default setting is 'off'. It iw written as in the examplebelow:

-removemenuentries:off

_INTR_ When this entry is included in the sapproxy.ini file, theGuiXT Server will send a blank screen to the SAP GUIclient. The syntax is as follows:

TargetServer=_INTR_

This setting means that you will not have a liveconnection to a SAP server, similar to how the Offlineproduct works. Also as in Offline, you can run scripts tocreate controls and other functions on this screen. Thissetting is useful for creating custom controls or functionswithout sending data to SAP. Click the X in the upperright corner of this screen to turn it off.

The _INTR_ entry takes a single optin, as follows.

• app: This option designates the dynpro. In theexample, it is the ZGUIXT custom dynpro.

Beginning with the 3.4.xxx.0 release of GuiXT WSServer, the _INTR_ syntax has changed. The originalsyntax is shown below.

TargetServer=__INTR__ , app=ZGUIXT

From the 3.4.xx.0 release, the syntax will be as follows.Any new options will be included in the list of options.

TargetServer=__INTR__ , options=-app:ZGUIXT -n:1001 -sid:PRD

Note: The two syntaxes cannot be mixed - youmust use one or the other. If both are used, the'options' syntax will always take precedence.

The options for the _INTR_ entry are as follows.

• -app: This designates the dynpro name.• -n: THis designates the dynpro number.• -sid: This designates the database name.


Multiple SAP InstancesEntering multiple SAP instances in the sapproxy.ini file.

In the case of multiple SAP instances, the sapproxy.ini file must contain an entry for each instance. Each entry mustcontain the relevant information for that particular SAP instance. An example of a sapproxy.ini file where there aremultiple SAP instances is shown below:

When you have multiple SAP systems in the sapproxy, the [Proxy] data is as follows:

ListenPort The port on which the GuiXT Server will listen fortraffic.

TargetServer The SAP server IP address or name

TargetServerPort The port on which the specified SAP application serverwill listen for incoming traffic.

GuiXT The SAP server IP address or name

options The SAP server IP address or name

Note that the sapproxy.ini file now contains two entries - one for each SAP instance. Note that the port informationand the server name information is unique. This is important - there cannot be two identically-named instances in thesapproxy.ini file. It is important to note that the proxy count in the [Control] section must equal the number of SAPinstances as well. For multiple instances of SAP, it is necessary to create a unique connection for each in the SAPLogon Pad as well. Each connection instance will point to the same server, but will have a unique system number. Inthe 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 separateinstance of the SAP server.


SynWatchdogSynWatchdog 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 mightbe in. SynWatchdog can also record events and send warning emails to a system administrator. SynWatchdog isautomatically installed by the InstallShield wizard. However, SynWatchdog is not set to start automatically - it mustbe 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, SynWatchdogcan be configured to perform actions based on whether a failure is the first, second or some other failure. Theavailable options are as follows:

Take no action Nothing will happen when the failure occurs.

Restart the service SynWatchdog will restart the service after the failureoccurs.

Run a program Choose an application to run. This might be a diagnosticapplication or some other program.


Restart the computer Restart the computer after the failure occurs.

To set these actions, 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 Recovery tab will be listings for ‘First Failure’, ‘Second Failure’ and

‘Subsequent failures’ as shown below:

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 typicalSynWatchdog configuration file looks like the following example.


The SynWatchdog.ini file contains a number of parameters, which are explained as follows:

AppName Path to the location of the GuiXT Server application.This parameter must include the -debug flag in order tofunction correctly.

KillTimeOut Time in seconds before killing SynWatchdog if there isno response from SAPProxy.exe.

MonitorInterval Time between SynWatchdog monitoring sessions inminutes. the minimum value is 1.

GuiXT Specify whether GuiXT is using the WS engine. If theimplementation is not WS, the number will be 1. If it isWS, the number will be 10.

AdminRestart Value dictating if an immediate restart is to be performed.Value 1 is to send an email to the administrator but notrestart; value 0 is to restart immediately and send emailto the administrator in addition.

AdminSMTPServer The customer's email SMTP server.

AdminEmailAddress The email address of the administrator. Multiple emailaddresses can be entered, using a comma as delimiter.

MaxMemoryPerConnect This is the total amount of memory that can be allocatedper each connection in megabytes. Normally this shouldnot be set above 50 MB - average usage normally runsbetween 30 and 35 MB per connection.

MaxMemoryUsage Unlike the previous parameter, this value is a percentageof the total available memory. Users can determine thisvalue by using the following formula:

• X = Maximum concurrent connections (eg. 50)• Y = Total virtual memory (eg. 2000 MB)• 20 = Average virtual memory used per connection• MaxMemoryUsage = 100 * ((x * 20) / Y(MB))• 100 * ((20 * 50) / 2000) = 50


• When the specified low memory value is reached,SynWatchdog will send out an email.

VerboseLog This is a Boolean value - it can be set to either 0 or 1.If at zero, no verbose logging is provided. If set to 1,verbose logs like the following example are created inthe GuiXTServer folder.

SendEmailCrash A Boolean value, this is set either to 0 or 1. If set to 1,it will send an email to the system administrator emailspecified in the INI file in the event of a GuiXT Servercrash.

SendEmailLowMemory Like the crash parameter, this is a Boolean. If set to 1, itwill send an email to the administrator email address inthe event that the memory limits specified in the INI fileare approached.

SendEmailNoResponse If set to 1, sends email to the administrator in the eventof there being no response from the GuiXT Server.

NotifyInterval Defined in minutes, this is the interval between the initialemail being sent and the subsequent email. Please notethat multiple emails are only sent if the server is in alow memory situation. If the server actually crashes,only a single email will be sent as SynWatchdog restartsthe server and that action clears all error conditions.However, in a low memory situation, multiple emailsmay be sent as in the following scenario:

• GuiXT Server reaches a low memory situation at 11PM and the interval is set to 720 minutes (12 hours),if the state is the same at 11 AM, a second email willbe sent to the administrator. Each parameter has aseparate interval. If a low memory situation occurs at10 PM, there will not be another low memory emailuntil 10 AM. But if another parameter is triggeredat 1 AM, an email will be sent at that time; the nextemail would be sent at 1 PM.

Starting SynWatchdog

To start SynWatchdog, users double-click on the 'Synwatchdog-Service.bat' file located in the GuiXTServer folder. Toset 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 SynWatchdogUpgrading the SynWatchdog component of GuiXT Server.

SynWatchdog is integrated into the latest versions of GuiXT Server. To upgrade, please do the following:

1. Obtain the latest version of GuiXT Server from Synactive.2. Obtain the latest version of Liquid UI from the Apple App Store.3. Stop the existing Syanctive Proxy Service on the server.4. Remove the Synactive Proxy Service by opening a command prompt and typing the following:

sapproxy.exe -remove5. Copy the new SynWatchdog and configuration file to the same location as the previous version. This is usually C:

\Program Files\Synactive Inc\GuiXTServer

6. Open the SynWatchdog.ini file in a text editor and add the following lines://Email SMTP Server AdminSMTPServer=your SMTP server name // Administrator Email Address. Usesemicolon to add more than one address [email protected]

7. Install the SynWatchdog service by typing the following in the command prompt:synwatchdog.exe -install

8. Start SynWatchdog. This will usually start the GuiXT Server as well.

| 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. Thissection will cover the following topics:

• Disaster Recovery

Disaster RecoveryRecovering from a GuiXT Server failure.

All customers should have a disaster recovery plan in the event that the GuiXT Server goes down and is notrecoverable. 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 adifferent server machine.

For GuiXT Server there are two possible recovery scenarios, which are as follows:

• 32-bit Server Recovery• 64-bit Server Recovery

32-bit Server RecoveryPerforming recovery on a 32-bit GuiXT Server.

To recover a 32-bit server, there are two separate sets of actions that must be done. These actions 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 aneffective 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:\ProgramFiles\Synactive Inc\GuiXTServer. An example folder is shown below.


2. Ensure that the original configuration files are included in this backup. These files are as follows:

admin.ini This is the configuration file for the ServerAdministration Console tool.

sapproxy.ini This is the configuration file for the GuiXT Serveritself.

synwatchdog.ini This is the configuration file for the SynWatchdogutility.

3. Ensure that all files are stored safely and regularly updated to be the most recent versions. This is especiallyimportant in the case of the configuration files, as any changes that are not backed up will be lost in the event of anun-recoverable crash.

Recovery

Once you have backed up your configuration files, you can start the recovery portion of the process. This is describedas 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.


3. Call Synactive Support or send an email to [email protected] to request a replacement license. Synactive licensesare based on the system's host ID, which can be obtained by clicking the 'Copy HostID' button in the SynactiveLicense Manager as shown below:

4. Send the HostID in the email requesting a new license and the replacement should arrive in about two businessdays.

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:

mailto:[email protected]


7. Navigate to the directory where the new license is stored as shown in the following example and select the licensefile, then click Open.


8. The license file will be automatically installed by the License Manager.9. Click the Apply button to apply the license. The Server is now licensed and ready to use.10. In the GuiXTServer directory, double-click the ConsoleMode.bat file to start the server, or double-click the

Start_GuiXTServer_Service.bat file to run GuiXT Server as a service.11. The recovery should now be complete and the Server will be ready to use.

64-bit Server RecoveryPerforming recovery on a 32-bit GuiXT Server.

To recover a 64-bit server, the process is very similar to that used for a 32-bit server. The main differences are that thefile paths may not be exactly the same. As in the case of the 23-bit server, there are two separate sets of actions thatmust be done. These actions 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 aneffective 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:\ProgramFiles\Synactive Inc\GuiXTServer. An example folder is shown below.


2. Ensure that the original configuration files are included in this backup. These files are as follows:

admin.ini This is the configuration file for the ServerAdministration Console tool.

guixt.ini This is the GuiXT configuration file. If you are usingGuiXT WS, this file is not necessary.

guixt.sjs This is the GuiXT WS configuration file. If you are notusing GuiXT WS, this file is not necessary.

sapproxy.ini This is the configuration file for the GuiXT Serveritself.

synwatchdog.ini This is the configuration file for the SynWatchdogutility.

3. Ensure that all files are stored safely and regularly updated to be the most recent versions. This is especiallyimportant in the case of the configuration files, as any changes that are not backed up will be lost in the event of anun-recoverable crash.

Recovery

Once you have backed up your configuration files, you can start the recovery portion of the process. This is describedas 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.3. Call Synactive Support or send an email to [email protected] 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 SynactiveLicense Manager as shown below:

4. Send the HostID in the email requesting a new license and the replacement should arrive in about two businessdays.

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:

mailto:[email protected]


7. Navigate to the directory where the new license is stored as shown in the following example and select the licensefile, then click Open.


8. The license file will be automatically installed by the License Manager.9. Click the Apply button to apply the license. The Server is now licensed and ready to use.10. In the GuiXTServer directory, double-click the ConsoleMode.bat file to start the server, or double-click the

Start_GuiXTServer_Service.bat file to run GuiXT Server as a service.11. The recovery should now be complete and the Server will be ready to use.

| 6.0 Appendices | 72

6.0 Appendices

In addition to the main concepts previously introduced, there is some additional information contained in theAppendices. The following topics are covered:

• Upgrading GuiXT Server• Using GuiXT Server with SAPConsole

Revision HistoryThis section of the document contains the changes made to this document since the baseline 3.4.417.0 release. Pleasenote that not all changes will be noted. Synactive uses the following methodology to track document revisions.

New Features Any new features added to the WS engine will be notedand the release version in which they first appear willbe included. You can also check feature additions in theversion history matrix in the Appendices.

Content Corrections Any content that is subsequently found to be inaccuratewill be corrected and the correction will be noted here,together with the relerase version in which the correctionwas made.

Content Additions Any content that is added to a particular section of thedocument will be noted in this section, together witb theversion in which the addition was made.

Content Deletions Content is never deleted. It may be corrected or additionsmay be made, but we do not delete content.

Typographical and Grammatical Corrections Typographical errors and grammatical errors will becorrected silently and will not be documented. Thesetypes of errors will only be noted if the correctionchanges the actual meaning of the content. Screencapsthat are mis-sized will also not be noted when they arecorrected.

Screen captures Screen capture updates will not be noted unless thechange affects the actual content. Changing screenshotstaken in SAP 7.10 to screenshots taken in SAP 7.20, forexample, will be a silent update.

Document Change History

The following table contains the specific changes made to this document since the last release.

Document Section Change Type Change Details Document Version

Configuration Content Addition Added new syntax andoptions to '_INTR_' entryin sapproxy.ini section.

3.4.444.0


Document Section Change Type Change Details Document Version

Configuration Content Addition Added 'ReservedPhysMem'option to sapproxy.inisection.

3.4.444.0

Configuration Content Addition Added section onAdministration Console.

3.4.444.0

Appendices Content Addition Added new appendixfor tracking documentchanges.

3.4.436.0

Load-Balancing Content Addition Revised and expandedsection on configuringGuiXT Server as aMessage Server for load-balancing. Also revisedarchitectural diagramsand sections on load-balancing for additionaldetail and easier customerimplementation.

3.4.436.0

Upgrading GuiXT ServerUpgrading an existing installation of GuiXT Server.

Synactive releases regular updates to GuiXT Server. If you are a paid customer, you will receive these updates andwill need to upgrade your server. To up[grade your server, please do the following.

Note: You must have administrative rights to upgrade GuiXT Server.

1. Close all SAP windows, including the Logon Pad2. Go to the directory containing the GuiXT Server files. On most machines, this directory can be found at C:

\Program FIles\Synactive Inc\GuiXTServer.3. Make a backup of the current GuiXTServer folder. Synactive recommends saving it as

MMDDYYYY_GuiXTServer.4. Open the Services tool. This tool can usually be found at Start > Control Panels >

Administrative Tools > Services..5. Find the Synactive R/3 Proxy Service as shown below and click the Stop button to stop the service.


6. Download the latest version of the GuiXT Server from Synactive and save it to an easily accessible location. Youwill 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.

Using SAPConsole with GuiXT ServerUsing SAPConsole and Telnet with GuiXT Server.

SAPConsole is an character-based UI solution for RF-based handhelds and was originally shipped with the 46B / 46CSAPGui installation CD. SAPConsole is designed to translate the SAP GUI screens to character-based devices suchas scanguns.


Most Synactive customers use the GuiXT Mobile client for Windows-based handhelds together with GuiXT Serverto connect to Windows-based handheld devices. However, it is also possible to use GuiXT Server with non-Windowsbased handheld devices such as those using SAPConsole.

Although Windows-based handheld devices are more common these days, we are aware that some customer smay still have a need to deploy character-based devices and we will explain how to install, deploy and configure aSAPConsole deployment in this appendix. The following topics will be covered:

• System Requirements• Installation• Configuration

SAPConsole System RequirementsThe system requirements for implementing SAPConsoel with GuiXT Server.

Important: A Telnet server is required in order to use SAPConsole with GuiXT Server.

The basic requirements for using GuiXT Server with SAPConsole are as follows:

• Telnet Server• SAPConsole• GuiXT Server

Operating System

The following Microsocft operating systems are supported for GuiXT Server.

• Windows 2000 Server• Windows 2003 Server• Windows Server 2008

Telnet Server

Telnet servers are not Synactive products. There are many such solutions that can be used and Synactive does notrecommend any particular solution. It is only necessary to choose a solution that can be used on the same machine asSAP’s SAPConsole UI. The Telnet server must support VT220 emulation. The Telnet servers used in this documentare as follows:

• Seattle Labs SLNet 2.6• Georgia SoftWorks GS_Tnet

The following system requirements are based on the SLNet 2.6 Telnet server.

Server SLNet 2.6

RAM 1MB of system memory per logged-in user.

Required Memory Formula The formula to calculate the amount of memory requiredfor your deployment is as follows:

OS Memory Requriements + 2MB SLNet + (1MB x number of users)

SAPConsole

The SAPConsole can be installed on the same machine as the Telnet server and the current system requirements are asfollows:

Operating System Windows 2003 Server (32-bit only)

http://seattlelab.com

http://www.georgiasoftworks.com


CPU 600MHz Pentium III processor. Minimum cache size of512K.

RAM 512 or dedicated RAM or above. We recommend addinga minimum of 1 GB to the server's system requirements.

OS Memory Requriements + 2MB SLNet + (1MB x number of users)

Required Memory Per User You should typically calculate about 2MB of memory perlogged-on RF session.

Storage (HDD) Dual 10GB Raid 1 (mirrored). Only 1.5 GB is actuallyused by the OS, SAPCONSOLE, and telnet software.

Supported Versions SAPConsole 4.6B and above

Screen Resolution Currently supports screen sizes of 8x40 and 16x20. Otherscreen sizes may be supported via screen exits or customtransactions.

Installing Server for SAPConsoleUsing SAPConsole and Telnet with GuiXT Server.

To install the GuiXT Server for SAPConsole, first install SAPConsole on the relevant handheld devices and theninstall GuiXT Server on a supported operating system as described in the Install Process section of this document.

SAPConsole UI can be installed on the same machine as the Telnet server. Please see the System Requirements sectionfor more SAPConsole detailed requirements. We will not cover the installation and configuration processes eitherfor SAPConsole or for Telnet servers in this document. Please consult SAP's SAPConsole documentation for moredetailed information on installing SAPConsole. In addition, the SAPConsole documentation is also available fromSAP.

Note: A valid OSS account number and password will be required to download the SAPConsoledocumentation.

Configuring GuiXT Server for SAPConsole

To configure the GuiXT Server for a SAPConsole deployment, please do the following:

1. Install SAPConsole, the Telnet server of your choice, and GuiXT Server.2. On the device, open SAPLOGON and create a new connection.3. Enter a name for the connection in the Description field. We recommend something like 'GuiXT Server'.4. Enter the name or IP address of the GuiXT Server in the Application Server field.5. Select the type of system - R/3 or R/2. Most of the time it should be R/3.6. 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.

7. Click OK to create the new connection.

Comparing SAPConsole with GuiXT MobileComparisong of the SAPConsole and GuiXT Mobile solutions.

Synactive offers a Mobile solution for handhelds. In the following table we will compare Synactive Mobile toSAPConsole.

http://www.sdn.sap.com/irj/sdn/sap-gui?rid=/library/uuid/e0602bdd-84f2-2a10-d982-b0dd2f2cd8f4


Features GuiXT Mobile SAPConsole

Hand-held version of desktop SAPGUI

Yes No

Works on existing SAP transactions Yes Yes

Supports buttons Yes No

Allows disconnection Yes No

Built in auto-tab and auto-enter Yes No

Data validation Yes Yes

Middleware required No No

Telnet required No Yes

Supports SAP GUI 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

ABAP programming required No Yes

Infrastructure GuiXT Mobile SAPConsole

Wi-Fi Required Yes Yes

WAN Integration (GPRS / GSM) Yes Yes

Retains back-end connection toServer

Yes No

Date post:	10-Dec-2015
Category:	Documents
Upload:	satya-bharat-kumar-naidu
View:	55 times
Download:	11 times

GuiXTServer_WS_3.4.450.0

Documents