As for the database server, IBM DB2 Server V7 for z/OS is running in an LPAR
with z/OS V1.6 in our zSeries z990. Also, maintenance RSU 0502 and SAP
service marketplace OSS 81737 are installed.
Because the version of SAP used in this scenario is 4.7, a started task (STC)
named ICLIM5D was configured to serve as the Integrated Call Level Interface
(ICLI) for the transfer of SQL statements from the SAP application servers to the
DB2 database server.
Note:
The version of SAP used will determine whether an ICLI or Distributed
Relational Database Architecture (DRDA ) connection via DB2 Connect
is required.
The SAP Agent component needs DDIC user privileges. In order to run, the SAP
Agent needs certain SAP function modules installed on the monitored SAP
systems. These function modules are provided by several SAP base support
packages and are installed as a patch. In our environment as the SAP support
pack 47 is installed, the monitored SAP servers must have the SAPKB62047
package installed.
The SAP Administrator has to make sure that all system collectors are running.
The SAPOSCOL (running on the SAP monitored systems), RFCOSCOL
(running on the database server), and all other collectors must be started
automatically during startup.
IBM Dynamic Infrastructure for mySAP assumes that SAP users log on to a
predefined SAP logon group. Each application server that belongs to the set of
dynamically provisioned SAP application servers must be a member of a unique
SAP logon group.
Management environment overview
The recommended topology used for the management environment is a
two servers architecture as shown in Figure 2 on page 8. The following list
represents the software and hardware configuration on each of the servers:
Server one
Cygwin DLL 1.5.14 1
IBM DB2 UDB Workgroup Server Unlimited Edition V8 with fix pack 3 and
APAR IY57410 for DB2
IBM Tivoli Directory Server V5.2
10
Dynamic Provisioning of SAP Environments using IBM DI for mySAP and Tivoli Provisioning
<
New Page 1
Web Hosting SSH