Example 27 shows a list of authorized users of this vswitch definition.
Note:
Because access to a vswitch definition can be authorized prior to the
creation of z/VM directory entries, it is recommended that all possible
dynamically provisioned servers be included in the authorization files.
Example 27 CP query vswitch access output
VSWITCH SYSTEM LAN1 Type: VSWITCH Connected: 2 Maxconn: INFINITE
PERSISTENT RESTRICTED NONROUTER Accounting: OFF
VLAN Unaware
State: Ready
IPTimeout: 5 QueueStorage: 8
Portname: UNASSIGNED RDEV: 2E2C Controller: TCPIP VDEV: 2E2C
Authorized userids:
IDADM001 IDADM002 IDADM003 IDADM004 SAPCI SAPCM
SAPDI SYSTEM
SAP master systems setup
A base SAP system implementation is needed prior to running the IBM Dynamic
Infrastructure for mySAP. This would entail the SAP Central Instance and at least
one SAP Dialog Server for each SAP SID in your landscape, along with any
systems required for interfaces to other applications. It is expected that these
systems already exist and are functional.
After the base SAP systems are in place, you can implement the rest of the SAP
configurations to support IBM Dynamic Infrastructure for mySAP.
The Linux on zSeries code was installed by initially booting from VM EXEC
starter files, then continuing the Linux on zSeries code installation over the
network. Service Pack 3 was then installed via YaST2 control center.
Updates to the SAP base systems
The SAP Service Marketplace provides the list of update activities that must be
performed for each specific version of SAP. For our environment, we had to install
the following additional code on each base Linux system:
suse sapinit.rpm
saplocales 2.2.5 2
Java SDK 1.3.1
Dynamic Provisioning of SAP Environments using IBM DI for mySAP and Tivoli Provisioning Manager
43
<
New Page 1
Web Hosting SSH