SAP® AG ??Neurottstr. 16 ??D-69190 Walldorf

Release 6 .40

IGS Internet Graphics Service Installation Guide

W i n 3 2 s t a n d a l o n e

Copyright © Copyright 2002 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One. All other product and service names mentioned are the trademarks of their respective owners.

Documentation in the SAP Service Marketplace You can find this documentation at the following address:

http://service.sap.com/instguidesNW04 -> Installation

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Contents

1 INTERNET GRAPHICS SERVICE INSTALLATION - GENERAL INFORMATION...... 5

2 INTERNET GRAPHICS SERVICE................................................................................ 6

3 INSTALLATION PROCESS ......................................................................................... 7

3.1 Planning ................................................................................................................................................. 8

3.2 Preparations .......................................................................................................................................... 8

3.3 Installation ............................................................................................................................................. 9 3.3.1 Installation Procedure ...................................................................................................................... 9 3.3.2 Starting the IGS.............................................................................................................................. 24 3.3.3 Installation Check........................................................................................................................... 24 3.3.4 SAP System Configuration ............................................................................................................ 25

3.4 Post Installation................................................................................................................................... 27

4 ADDITIONAL INFORMATION.................................................................................... 30

4.1 Uninstalling the IGS ............................................................................................................................ 30

5 FURTHER INFORMATION......................................................................................... 36

5.1 Information on Software Used ........................................................................................................... 36

1 Internet Graphics Service Installation - General Information

Purpose

This guide shows you how to install the Internet Graphics Service (IGS).

Implementation Considerations

The IGS is already used in a wide range of scenarios including the following:

Web Reporting in the Business Warehouse

Displaying graphics in the SAP GUI for HTML

SEM: Balanced scorecard

Early Watch

CRM

Read the following installation notes before beginning the installation. These notes contain the most recent information regarding the installation, as well as corrections to the installation documentation.

Make sure that you have the most recent version of each note. You can find the SAP notes in the SAP Service Marketplace (http://service.sap.com/notes) or by using SAPNet - R/3 Frontend.

List of Related SAP Notes

Internet Graphics Service: Main Note 458731

Graphics Not Displayed in SAP GUI for HTML 422757

Troubleshooting when a problem occurs with the IGS 514841

SAP IGS support strategy 480692

HW/SW requirements for Internet Graphics Service 443430

IGS: Configuring the RFC connection in SM59 454042

Simultaneous installation of SAP IGS, SAP ITS and SAP GUI 518155

2 Internet Graphics Service

The IGS is a server-based engine for generating content (graphical or non-graphical) based on data from an SAP system or an external system.

Key features of the IGS

Independence of the front end

The content is generated on the server and can then be displayed on the front end of your choice, for example in a browser or in a GUI.

Platform independence

The architecture has been designed so that it can be ported to various operating system platforms. Currently Windows and those Unix platforms on which the Web Application Server runs are currently supported. If the Chart OCX is used (for example, in the Business Information Warehouse) parts of the IGS must be installed on a Windows platform (at least one portwatcher including the Chart interpreter files).

Note for BW: BW release 3.0B only runs with the IGS 6.20 and later and is only supported for Windows NT and Windows 2000.

Extensibility:

- Easy integration of new components

- Easy integration of new protocols (listeners) that react to new data streams

Accessibility:

- Using RFC and HTTP (XML)

- Data sent from an SAP System or an external system

Support for a variety of data formats, for example, XML

Improved scalability/monitoring

3 Installation Process

Make sure that you have administrator rights for the machine where the IGS is to be installed. This is a prerequisite for the installation.

Before installing the IGS we recommend obtaining some port numbers, depending on the number of IGS Portwatchers to be configured. These services are needed to guarantee stable tcp/ip communications. The number ports required can be calculated as follows: Add 1 for the IGS Multiplexer, add 1 for each IGS Portwatcher.

The IGS Multiplexer, IGS Portwatcher and the related SAP-Systems have to be accessible through the network. Try to contact the machines by using the system networking tool ‘ping’. Alternatively you can use rfcping to test the rfc access to the SAP System.

The “data” directory and the “conf” directory have to have “write” authorizations for the multiplexer- and portwatcher processes. This is important because of “on demand” configuration changes during the operation of the IGS. These configuration changes may include additional IGS Interpreters for new graphics types or additional data for IGS Interpreters that have already been installed to enhance its capabilities (for example: adding new maps for the GIS-Interpreter).

The graphics components use parts of the system’s graphical capabilities, so please ensure that the graphics card of your server supports at least 256 colors, we recommend 16bit color mode (or 32K colors).

We recommend that you deactivate the "smooth font" setting to avoid pixel artefacts.

To deactivate an interpreter change the extension from .dll to .(something else). To reactivate an interpreter rename it to .dll. For the change to take effect restart the Portwatcher.

3.1 Planning

Requirements

The IGS currently runs on Windows 2000, Windows NT and those Unix platforms on which the Web Application Server runs.

Hardware: We recommend using the IGS on a machine with a graphics card with at least 32K colors. Please adjust your screen color depth accordingly. The resolution does not affect the graphics image generation in the way that the color depth does.

Distribution of elements of the IGS

The elements of the IGS can be distributed across various machines running on various platforms. For example, the multiplexer and one portwatcher could run on a Windows NT machine and another portwatcher could run on UNIX.

Generating one graphic on a Pentium 800 MHz.

Maps 600 ms

Business graphics 300 ms

Memory requirements MUX: roughly 64 MB

Memory requirements per portwatcher roughly 64 MB

Generating one graphic on a Pentium 400 MHz

You should double the times for a "slower" Pentium with 400 MHz.

Example for a Pentium with 400 MHz

Time required for 2000 maps and 5000 business graphics (per hour)

2000 * 1.2 sec + 5000 * 0.6 sec => 2400 sec + 3000 sec = 5400 sec

This means that at least two portwatchers are required. These can be distributed either on two CPUs or on two servers.

The minimum configuration is therefore:

1 PC with two CPUs and 3 * 128 = 384 MB

or

1 PC with one CPU, 2 * 128 = 256 MB

1 PC with one CPU, 128 MB

3.2 Preparations

If you are installing the IGS and the ITS/SAP GUI or all three on one host you should read note 518155.

3.3 Installation

3.3.1 Installation Procedure

You should always install the most up-to-date IGS – the IGS is downwards-compatible. You can find it on the Service Marketplace http://service.sap.com/patches -> SAP IGS.

The file used to start the installation is 'setup.exe'. The IGS documentation on the CD is in the directory 'docu' and is called IGSinst.pdf.

Note: At a number of points default entries are suggested. You are advised to use the default settings if they are appropriate for your requirements. This makes later stages in the test more straightforward.

1. If you have already installed a version of the IGS make sure you uninstall it:

a) Choose Start -> Settings -> Control Panel -> Add/Remove Programs

b) Select the program SAP IGS (scroll down if necessary)

c) Choose Change/Remove.

d) Select a language.

e) Select the radio button Remove and choose Next.

f) Choose Finish.

It this does not work then try the following:

You should delete the Service for the IGS manually otherwise you may have problems when you install a new version of the IGS without rebooting:

a) Call DOS box (Start -> Run -> cdm + Enter)

b) Change to the path C:\Program Files\SAP\Internet Graphics Server\bin

c) To uninstall the service execute the command: igsWdServ –u + Enter

Finally you have to manually delete folders generated during the installation of the IGS:

a) Locate the folder Internet Graphics Server where the IGS was installed. The default path is Program files -> SAP -> Internet Graphics Server.

b) Delete the subfolders, for example conf, log and so on.

2. Install the IGS as follows:

Execute the file setup.exe for the IGS on the Server Components CD. Below are the most important dialog boxes and what entries you should make in them. Note: At a number of points default entries are suggested. You are strongly advised to use the default settings. This makes later stages in the test more straightforward.

Select the language in which the installation is to be carried out, default English. Then choose OK.

Choose Next on the initial screen of the Install Shield.

This specifies where the IGS will be installed on your hard disk. We recommend you accept the default by choosing Next.

Select the appropriate setup type, choose Next and proceed to the next step.

Add additional components, for example, the Loopback and XML Chart interpreters and select the corresponding checkboxes.

Note: You cannot select both the Gfw Chart interpreter and the Chart interpreter at the same time!

Then choose Next.

Specify what type of installation you want. If you want a complete installation on a single host (Multiplexer + Portwatcher) then choose Single-Host.

The other two types of installation are relevant if you need a distributed scenario with a Multiplexer on one machine and a Portwatcher on a different machine.

If you just want to install the Multiplexer on a machine then choose Client-Server: Mux. If you just want to install a Portwatcher then choose Client-Server: Portwatcher.

If an existing configuration is found you must decide whether to:

Backup the old file and write a new configuration file OR

Overwrite the old file with a new file OR

Leave it as it is.

Specify the IP and port for the multiplexer:

Enter the address of your PC in the field IP (that is, the number identifying your PC, for example P12345).

Enter the port for the Multiplexer in the field Port (default: 3290).

Specify the number of portwatchers (default 2).

Specify the port numbers for the portwatchers. You have to specify ports for all the portwatchers so a similar dialog box is displayed for every portwatcher required (default 3291 and 3292).

Specify whether you require an RFC or an HTTP setup or both. Default: Select both checkboxes. Choose Next.

Specify the port for the HTTP listener. Default: 8030

Specify the number of RFC listeners you want to configure (default: 1).

The IGS needs to “know” an R/3 system. The system must be at least 4.6D or later. Specify the program ID, the RFC host and the gateway for the RFC listener.

The program ID:

We suggest an entry in the form: IGS.Pxxxxx where Pxxxxx is the PC where the IGS is being installed.

The RFC-host:

To find this call up the SAP Logon dialog box -> (button) Server… -> <system name> in the field System Id -> (button) Generate list In the section Servers find the enqueue server. The abbreviation ENQ is used as part of the string in the relevant line.

For example, if there is the string hs0344 (b20main_B20_21, DIA UPD ENQ BTC SPO) for one of the servers. The string ENQ shows that this is the enqueue server.

The host in the above case is hs0344.

The gateway service: This is the string sapgw with the system number as a suffix. In the above example that is the number 21. So the complete gateway service is sapgw21 in the above example.

When the installation has finished the following dialog box is displayed.

3.3.2 Starting the IGS

Start the IGS as a service. The preferred method for starting the Windows IGS is by using services. You can start/stop the service for the IGS as follows:

For Windows 2000 and Window NT choose Start -> Settings -> Control Panel -> Services (or Administrative Tools -> Services) -> Scroll down and choose SAP IGS -> Button: Start Service.

3.3.3 Installation Check

Testing the HTTP Listener

Monitoring the installation of the IGS

Call up the initial monitoring page as follows:

Call up a browser

Enter the following in the address line of the browser: http://(host name):(port)/ where (host name) is the name of the machine you have installed the IGS on and (port) is the port number.

How to find out the host name

Start -> Settings -> Control Panel -> Network -> (entry in field "Computer Name")

How to find out the port

Call up the config file igs.xml in an editor of your choice, for example notepad.

Find the entry with the port number of the http listener, for example

<LISTENERHTTP port="1090"/>. The port number in this case is 1090.

If this is successful it means that the IGS is running.

3.3.4 SAP System Configuration

The IGS runs as an additional server in the SAP server network.

A precondition for using the IGS from an SAP System is that the SAP System knows the IGS. To achieve this an RFC destination must be maintained both in the SAP System and also in the IGS so that the SAP System can access the IGS.

To maintain the RFC destination in the SAP System proceed as follows:

1. Call transaction SM59.

2. Select 'Create' to create a new RFC destination. The following screen appears (the exact appearance of this screen can change slightly from one release to the next):

3. Specify 'IGS_RFC_DEST' as 'RFC destination'.

4. Specify 'T' for TCP/IP as the 'Connection type'.

5. Enter a text as documentation (otherwise you can't save your entry).

6. Switch to "Registered server program" (select the appropriate radio button).

7. Specify your destination as program ID: IGS.xxx.xxx.xxx (The program ID is the same as what is specified in IGS.XML - we recommend the IGS abbreviation and then the IGS server's IP address. That is a useful reminder as to where the IGS is running.) Note: DO NOT select 2-byte-destinations in Unicode systems.

8. Gateway host: To find this call up the SAP Logon dialog box -> (button) Server… -> Enter the system name in the field System Id -> (button) Generate list In the section Servers find the enqueue server. That is the server where the main instance is running. The abbreviation ENQ is used as part of the string in the relevant line. For example, in QB6 there is the string PWDF0647 (PWDF0647_QB6_28, DIA VB ENQ BTC SPO VB2 ) for one of the servers. The string ENQ shows that this is the enqueue server.

9. Gateway service: This is the string sapgw with the system number as a suffix. In the above example that is the number 28.

10. Save and test the RFC destination using the button Test Connection.

11. Repeat the steps 2-10, but enter 'GFW_ITS_RFC_DEST' as 'RFC destination'.

12. Leave the transaction.

Testing the RFC Listener

You can use the RFC Listener to test the IGS as follows:

Call up the ABAP Editor (SE38).

Execute the report graphics_igs_chart_test (using your RFC destination on the second screen).

If a chart is displayed then the test was successful.

3.4 Post Installation

Preferences: (.xml files)

Once you have installed the IGS you can change the configuration if you like.

To configure the IGS use the XML document ‘IGS.XML’. It should always be located in the Configuration Directory (‘./conf’).

If this file does not exist, the startup of the IGS Watchdog (igsWd.exe) will create a simple configuration file with minimal configuration attributes. See below for a detailed explanation.

The IGS Multiplexer can also generate a config file based on parameters. See next chapter for how to do this.

All Portwatchers can be activated by adding new entries to this configuration file.

Example: <?xml version = "1.0"?>

<IGSCONFIGURATION version="1.0">

<TRACELEVEL>3</TRACELEVEL>

<MUX ip="190.180.20.10" port="3299">

<LISTENERRFC

programid="IGS.YOURIPHERE"

gwhost="HAL9000" gwservice="sapgw00"

recontime=”hourly”

>

</LISTENERRFC>

<LISTENERHTTP port="8030">

</LISTENEHTTP>

</MUX>

<PORTWATCHER port="3298" loadfactor="3">

</PORTWATCHER>

<PORTWATCHER port="3297" loadfactor="3">

</PORTWATCHER>

</IGSCONFIGURATION>

Detailed explanation of the configuration file:

<IGSCONFIGURATION version="1.0"> This tag contains the version of the configuration file to guarantee backwards compatibility for later release versions.

<TRACELEVEL> Species the level of the developer trace: from 1 = little tracing to 3 = a lot of tracing. If the IGS runs into an error during operation, we recommend setting the error level to 3 to gain maximum information.

<MUX ip="xxx.xxx.xxx.xxx" port="xxx"> The IGS Multiplexer’s IP address and the related port number has to be specified here.

<LISTENERRFC programid="IGS.xxx.xxx.xxx.xxx" gwhost="HAL9000" gwservice="sapgw00" recontime=“hourly”> programid: The RFC destination name for the SAP System and the RFC listener is specified using the ‘programid’. Use a unique identifier as a destination (Program ID), for example, a short abbreviation for the server and the IP address of the server’s machine. recontime and gateway: The reconnection time specifies how often the listener tries to reconnect to a disconnected gateway (possible values are “every minute”, “hourly”, “daily”, “weekly” or at intervals of a given number of seconds (default is 3600 seconds = 1 hour))

<LISTENERHTTP port="xxxx"> port: The HTTP Listener only needs a configured port number.

<PORTWATCHER port="xxxx" loadfactor="x"> This entry is used to configure the individual portwatchers on a computer. The important point is that different ports are specified for each portwatcher and they must not clash with the mux or the listeners. The “loadfactor” entry is not evaluated, but it does have to be specified. The number of portwatcher entries determines how many instances of a portwatcher are started on a computer.

Generating the config file with the IGS Watchdog

You can start the Watchdog with the command ‘-c’ to force the writing of a new configuration file.

The syntax is as follows:

Boldface = parameter name. The parameters ‘portwatcher’, ‘listenerrfc’ can be sent several times, once for each to be added.

Placeholders = ipaddress, hostname, port number, service are placeholders to be replaced by your configuration data.

<> = mandatory parameter (you have to specify this parameter)

[] = optional parameter (you can specify this parameter, but your do not have to.)

From the command line call the IGS Multiplexer with the following parameters:

tracelevel=<0|1|2|3>

mux=<ipaddress|hostname>,<portnumber>

portwatcher=<portnumber>[,<loadfactor>]

listenerrfc=<IGS.ipaddress|hostname>,<gwhost>,<gwservice>[,<reconnectiontime>]

listenerhttp=<portnumber>

Mandatory parameters are at least one mux, one portwatcher and either a listenerrfc or a listenerhttp.

Example:

igsWd -c –tracelevel=0 –mux=igsserver1,3297 –portwatcher=3298 -portwatcher=3299 –listenerrfc=IGS.igsserver1,sapgwhost,sapgw00,3600 –listenerhttp=8030

This will generate the following config file:

<?xml version = "1.0"?> <IGSCONFIGURATION version="1.0"> <TRACELEVEL>0</TRACELEVEL> <MUX ip="igsserver1" port="3297"> <LISTENERRFC programid="IGS.igsserver1" gwhost="sapgwhost" gwservice="sapgw00" recontime=”3600” > </LISTENERRFC> <LISTENERHTTP port="8030" /> </MUX> <PORTWATCHER port="3298" loadfactor="3" /> <PORTWATCHER port="3299" loadfactor="3" /> </IGSCONFIGURATION>

4 Additional Information

4.1 Uninstalling the IGS

(Windows 6.10C2 and later) – Install Shield

Choose Start -> Settings -> Control Panel -> Add/Remove Programs.

Select SAP IGS (scroll down if necessary) and choose Add/Remove.

Select a language

Specify that you want to remove the IGS.

To confirm that you want to uninstall the IGS choose OK.

If a read-only file is detected in your installation the following dialog box will be displayed. Select the checkbox and choose Yes.

The uninstall is now complete.

Although the IGS has now been uninstalled there will still be some IGS-related files on your hard disk which you can remove manually. These files include configuration files and log files. You will find them in their corresponding folders on the hard disk in the location where the IGS was installed.

Uninstalling the IGS (Windows 6.10) - R3SETUP

You can uninstall the IGS as follows:

1. Locate the IGS files on your hard disk. They will probably be in the folders under Program Files -> SAP Internet Graphics Server. If not then search for the files igsPw.exe (portwatcher) and igsMux.exe (multiplexer).

2. Open a DOS box at the folder bin (this contains the files igsPw.exe and igsMux.exe).

3. Stop the portwatcher by executing the command: igsPw -e

4. Stop the multiplexer by executing the command: igsMux -e

5. Uninstall the portwatcher by executing the command: igsPw -u

6. Uninstall the multiplexer by executing the command: igsMux -u

7. => Switch to your Windows Explorer and manually delete the folder Internet Graphics Server with its content and its subfolders.

Note concerning controls

When you uninstall the IGS you also uninstall various controls such as the Chart control. Since you may well need these controls you should only uninstall the IGS if you are going to install a newer version (and so the controls will be available again). To prevent the IGS being started in the background you can disable the IGS instead of uninstalling it

Disabling the IGS

If you do not want the IGS to be started in the background whenever you start the computer then instead of uninstalling the IGS just disable it or change it to manual startup as follows:

Start -> Settings -> Control Panel -> (Administrative Tools) -> Services -> (Select the service for the IGS) -> Button: Startup -> Startup type: Disable / Manual

5 Further Information

5.1 Information on Software Used

We acknowledge use of the software called zlib. See http://www.gzip.org/zlib/zlib_license.html.

We acknowledge use of the software called libjpeg. See http://www.faqs.org.

We acknowledge use of the software called libtiff. See http://www.libtiff.org/misc.html.

We acknowledge use of the software called FreeType. See http://www.freetype.org/freetype2/FTL.txt.

We acknowledge use of the software called libungif. See http://prtr-13.ucsc.edu/~badger/software/libungif/getting.shtml.

We acknowledge use of the software called libpng. See http://www.libpng.org/pub/png/src/libpng-LICENSE.txt.