Integrated ITS: installation and activation

The integrated ITS is part of the SAP Web Application Server 6.40. It is automatically installed together with the SAP kernel. To be able to use a service via the integrated ITS, you must first follow the standard procedures for activation and configuration of the Internet Communication Manager (ICM). For more information, see Administration of the Internet Communication Manager.

In addition, you must activate the service you want to execute and the service default_host/sap/public/bc/its/mimes in the Internet Communication Framework (ICF). For further information refer to Activating an SICF Service.

Make sure that besides the Internet service to be used also the two Internet services system and webgui (also known as SAP GUI for HTML) have been published to site INTERNAL, because objects of these services may also be used by other services.

The ICF path for the webgui service is /default_host/sap/bc/gui/sap/its/. You can use this path to search for the service in transaction SICF. HTTP requests with /sap/bc/gui/sap/its/webguispecified as path are forwarded to the request handler of the integrated ITS. The complete URL for access to the SAP system with SAP GUI for HTML is
http(s)://<icman-host>:<icman-port>/sap/bc/gui/sap/its/webgui

When using the integrated ITS, two profile parameters (see also Changing and Switching Profile Parameters) are of special importance:

● itsp/enable

You use this parameter to deactivate (0) or activate (1) the integrated ITS. Even if the integrated ITS is activated, it only accesses system resources when it is actually used. Nevertheless, it can make sense to deactivate it to prevent users from accessing the SAP system with SAP GUI for HTML via special application servers (such as batch or update instances). Since the conversion of SAP screens into HTML pages uses additional CPU time, it makes sense to reserve a number of dedicated application servers to be used with SAP GUI for HTML and to use a special logon group to balance the load between them.

● em/global_area_MB

The “global area“ is a memory shared by all work processes of the SAP kernel. The integrated ITS uses it for the runtime version of the HTML ^Business templates ("preparsed templates"). The memory required depends on the number and size of the templates used to display the services called by the users. The default value is large enough to use SAP GUI for HTML with one browser version in one logon language. If your users access the ITS with different languages or browsers (for example, Microsoft Internet Explorer and Netscape Navigator), or if they need additional services apart from SAP GUI for HTML, then the number of used templates will increase and you will have to adapt em/global_area_MB accordingly. You find information on when and how you should adapt this parameter in note 742048.

upg Ora 817 to 920 WIN

30/04/2008
Restore di A1P su A1S alle WED, APR 30, 2008 01:20:00 AM
utenza produzione: gruppomm / ******
Dopo db copy: pulizia tabelle IACORDES IACORSITE TWPURLSVR - nota 313486 per la pubblicazione su ITS
All services, templates, and mimes have been overwritten by the current version of the component system. Therefore, you have to modify the service files of the bbpstart, bbpvendor, bbpwi services on the ITS server as described in SAP Note 0307782 <-- APPLICATA (A parte il logo, probabilmente modificato direttamente su file system, ITS e' ok)

Aggiornamento kernel alla versione 620 level 674 (nota 580772)

## Oracle Upg 02/05/2008 ##
estensione tablespace SYSTEM da 350 a 650 MB (AUTOEXTEND ON)
backup registry e 817 Ora sw - stop SAP e servizi relativi e servizi antivirus
passaggio US7ASCII --> WE8DEC (nota 102402)

installazione sw 920 nella nuova ORACLE_HOME (A1S920 - k:\oracle\A1S\920)

installazione del current patch set (9.2.0.8, nota 539921 e 578683)
CAUTION - >=9.2.0.7
Make sure that the _OPTIM_PEEK_USER_BINDS Oracle parameter is set to FALSE before you upgrade to Oracle 9.2.0.7 or higher. Otherwise, serious performance problems are very likely. See also the corresponding point in Note 176754.

installazione ultima fix disponibile con Opatch (K:\oracle\A1S\920\OPatch): 6867138
Per l'uso di Opatch e' stato necessario installare ActivePerl-5.10.0 ...
K:\6867138>C:\Perl\bin\perl K:\oracle\A1S\920\OPatch\opatch.pl apply
K:\6867138>C:\Perl\bin\perl K:\oracle\A1S\920\OPatch\opatch.pl lsInventory

passaggio US7ASCII --> UTF8 (nota 669902)

 

avvio servizi Ora (quello di A1S e i 2 listener) cancellazione ORACLE_HOME dal profilo di <sid>adm e lancio DUA
ATTENZIONE: prendere i listener.ora sqlnet.ora tnsnames.ora della 8.1.7 e copiarli sulla 9.20, modificare opportunamente i puntamenti interni per la ORACLE_HOME. La variabile PATH deve presentare entrambe le ORACLE_HOME (prima la 8.1.7 e poi la 9.20) - Prima di lanciare il DUA con <sid>adm modificare il file MEP.CFG situato in %ORACLE_HOME%\assistants\dbma della 920, sostituiendo la stringa <Datafile name ="{ORACLE_BASE}/oradata/{DB_NAME}/odma_rbs.dbf"/> con ad es. <Datafile name ="j:\oracle\DWP\odma_rbs.dbf"/>
ATTENZIONE 2: lanciare il DUA tramite PcAnywhere: con remote desktop si riceve comunque un "TNS protocol adapter error" ...
a fine procedura DUA, post-processing come da manuale, tra cui:
> variabili d'ambiente
> K:\usr\sap\A1S\sys\exe\run>sqlplus /nolog @sapdba_role A1S NT (Nota 134592)
> brtools (fatto girare lo script oradbusr.sql, il comando brconnect -u / -f check va a buon fine)