4.7s Sr2 kernel upgrade 111 to 274 patch level.

IGS watchdog will not start. So troubleshoot this by updating the latest IGS
which we need to download from SMP

Installing and Updating the IGS

The Internet Graphics Service (IGS) needs to be installed before it can be used. You
should always install the most recent version of the IGS. It is also recommended to install
the latest IGS patch directly after the primal installation of an SAP Web Application
Server. Also note that an IGS patch always contains the complete IGS.
Until SAP Web Application Server 6.20 the IGS has been available only as standalone
engine. The standalone IGS is a windows application that runs standalone on a machine
and which is connected against several systems.
With SAP Web AS 6.40, IGS is additionally available as integral part of the SAP Web AS
and will be installed with every SAP Web AS installation. Thus, with SAP Web AS 6.40
you had the choice to use either the standalone or the integrated IGS. With SAP
NetWeaver 7.0 only the integrated version should be used.
The integrated IGS exists on every SAP Web AS machine and is started and stopped with
SAP WebAS. However, IGS is not part of the kernel which means it has to be patched
separately.

Procedures
The installation/upgrade procedures for the integrated IGS are as follows:

Integrated Version Installation

The integrated IGS is automatically installed with the SAP Web Application Server.

Integrated Version Upgrade

You find the upgrade files for the integrated IGS version on the SAP Service
Marketplace:

http://service.sap.com/swdc Download Support Packages and Patches Entry

by ApplicationGroup SAP Frontend Components SAP IGS SAP IGS
<version> SAP IGS <version> <operating system>.
There, you find the IGS executables and libraries (igsexe_*.sar) as well as the IGS folder
structure (igshelper_*.sar) containing among others font files.
With the upgrade files of the executables and libraries, proceed exactly like you would
with kernel patches (for example, extract the Archive to the same location). More
information about kernel patches can be found in the related note 19466 in the section
Copying and Installing a Patch.
The upgrade files for the IGS folder structure must be extracted to the instance directory
(DIR_INSTANCE). More information can be found in note 1028690.
After a restart of the Web AS the new IGS is up and running.
Information about finding out your IGS patch level is provided in note
931900.

For an upgrade of an integrated IGS please also check note 896400.

The Note no is Note 454042 - IGS: Installing and Configuring the

IGS
The IGS needs to be installed before it can be used.
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.
Other terms
Internet Graphics Server, Remote Function Call
Solution
Installing the IGS
==================
you should always install the most recent version of the IGS. We do also recommend installing the latest
IGS patch directly after the primal installation of an SAP Application Server.
You can find it:

On the Service Marketplace: on www.service.sap.com/patches -> SAP IGS (for the IGS 6.40
standalone Windows version). For the location of the integrated installation archive please refer to
note 718267 for IGS 6.40 or note 896400 for IGS 7.00.

On the most recent Server Components CD (for the standalone Windows version)

Or on the IGS CD of your installation disks (for the integrated installation).

In case of an upgrade of your standalone IGS please deinstall (remove) your IGS, as described in the
documentation, and install the new IGS. The configuration of the IGS (igs.xml) will not be deleted and can
be used with the new installation. You will be asked during the new installation if you want to use the old
configuration file or create a new one.
Configuring 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.
3. Specify GFW_ITS_RFC_DEST (and IGS_RFC_DEST if you are using a SAP Release 610 and
above) as the RFC destinations.
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 the program ID:
For the Win32 standalone IGS 6.40 and 7.10:
The program ID (IGS.xxx.xxx.xxx) is the same as what is specified in IGS.XML (for IGS
6.40) or in IGSProfile.pf (for IGS 7.10) - 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.
For the intergrated IGS:
The program ID must be IGS.<SAPSYSTEMNAME> where SAPSYSTEMNAME is the
name of your system.
Note: The program ID is case sensitive!
Note: Do NOT select 2-byte destinations in Unicode systems.
The following two steps are only relevant for a standalone IGS. If you use an integrated IGS leave these
parameters empty.
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.wdf.sap-ag (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. Test the RFC destination using the button "Test Connection".

Note 946153 - Parameters of the IGS configuration file igs.xml

You installed an IGS. This IGS defined an RFC listener or HTTP listener.
Solution
There are two ways in which you can call the IGS monitoring page:

Using the RFC listener: Start the relevant system and open transaction SA38 (or
SE38). Start the GRAPHICS_IGS_ADMIN report and select the corresponding
RFC destination. See also Note 995471.

Using the HTTP listener: Call the http://<IGS Host>:<IGS Port> page in the
browser, for example: http://localhost:40080. See also Notes 965201 and 959358.

The version number is displayed on the initial page. The penultimate character is the
patch level of the IGS. Click the status to go to the status page and check whether the
patch level of REGISTERED_PORTWATCHER and REGISTERED_INTERPRETER
matches the patch level on the initial page.
With older versions, the version information is not contained on the initial page. Only
carry out the check on the status page here.