The Veritas High Availability agent for SAP WebAS supports Enqueue and Enqueue Replication servers running inside Solaris non-global zones.

An example of creating a zone for SAP Enqueue/Enqueue Replication on Solaris is shown as follows.

Step1: Create the zone.

bash-3.00# zonecfg -z enqueue_zone1
enqueue_zone1: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:enqueue_zone1> create

zonecfg:enqueue_zone1> set zonepath=/export/zones/enqueue_zone1

Step2: Add all the required loop back file systems (LOFS) to the zone configuration.

zonecfg:enqueue_zone1> add fs
zonecfg:enqueue_zone1:fs> set dir=/usr/sap/PI1
zonecfg:enqueue_zone1:fs> set special=/usr/sap/PI1
zonecfg:enqueue_zone1:fs> set type=lofs
zonecfg:enqueue_zone1:fs> end
zonecfg:enqueue_zone1> add fs
zonecfg:enqueue_zone1:fs> set dir=/usr/sap/trans
zonecfg:enqueue_zone1:fs> set special=/usr/sap/trans
zonecfg:enqueue_zone1:fs> set type=lofs
zonecfg:enqueue_zone1:fs> end
zonecfg:enqueue_zone1> add fs
zonecfg:enqueue_zone1:fs> set dir=/usr/sap/ccms
zonecfg:enqueue_zone1:fs> set special=/usr/sap/ccms
zonecfg:enqueue_zone1:fs> set type=lofs
zonecfg:enqueue_zone1:fs> end
zonecfg:enqueue_zone1> add fs
zonecfg:enqueue_zone1:fs> set dir=/usr/sap/tmp
zonecfg:enqueue_zone1:fs> set special=/usr/sap/tmp
zonecfg:enqueue_zone1:fs> set type=lofs
zonecfg:enqueue_zone1:fs> end

Step 3: Add the network information to the zone configuration.

zonecfg:enqueue_zone1> add net
zonecfg:enqueue_zone1:net> set address=10.212.98.193
zonecfg:enqueue_zone1:net> set physical=bge0
zonecfg:enqueue_zone1:net> end

Step 4: Add a comment for the zone. This step is optional.

zonecfg:enqueue_zone1> add attr
zonecfg:enqueue_zone1:attr> set name=comment
zonecfg:enqueue_zone1:attr> set type=string
zonecfg:enqueue_zone1:attr> set value="This is 
enqueue_zone1 zone for SAP System PI1." 
zonecfg:enqueue_zone1:attr> end

Step 5: Verify and commit the zone configuration.

zonecfg:enqueue_zone1> verify

zonecfg:enqueue_zone1> commit

zonecfg:enqueue_zone1> exit

bash-3.00# zoneadm list -cv
  ID NAME            STATUS       PATH
   0 global          running      /
   - enqueue_zone1   configured   /export/zones/enqueue_zone1

Step 6: Install the zone.

bash-3.00# zoneadm list -cv
  ID NAME             STATUS       PATH
   0 global           running      /
   - enqueue_zone1    configured   /export/zones/enqueue_zone1

bash-3.00# zoneadm -z enqueue_zone1 install
Preparing to install zone <enqueue_zone1>.
Creating list of files to copy from the global zone.
Copying <6208> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1420> packages on the zone.
Initialized <1420> packages on zone.
Zone <enqueue_zone1> is initialized.
Installation of <113> packages was skipped.
Installation of these packages generated warnings: <VRTSat>
The file </export/zones/enqueue_zone1/root/var/sadm/system/\
logs/install_log> contains a log ofthe zone installation.

bash-3.00# zoneadm list -cv
  ID NAME            STATUS       PATH
   0 global          running      /
   - enqueue_zone1   installed    /export/zones/enqueue_zone1

Step 7: Configure the zone.

To configure the zone for the first time, log in to the zone console from the first terminal using the following command:

bash-3.00# zlogin -C enqueue_zone1
[Connected to zone 'enqueue_zone1' console]

Now, from the second terminal, start the zone.

bash-3.00# zoneadm -z enqueue_zone1 boot

You will see the following message on the first terminal.

[NOTICE: Zone booting up]

SunOS Release 5.10 Version Generic_118833-36 64-bit
Copyright 1983-2006 Sun Microsystems,Inc. All rights reserved.
Use is subject to license terms.
Hostname: enqueue_zone1
Loading smf(5) service descriptions: 25/25

Select a Language

  0. English
  1. Japanese
  2. Korean
  3. Simplified Chinese
  4. Traditional Chinese

Please make a choice (0 - 4), or press h or ? for help:

For more information on setting up zones, refer to the Solaris 10 Administration Guide.

Similarly, configure another zone with name "enqueue_zone2" on the second node, a zone with name "enqueue_zone3" on the third node, and so on, if you have more than three nodes in your cluster configuration and would like to use all the systems for Enqueue and Enqueue Replication server failover targets.

After installing and configuring a zone on each of the cluster nodes where Enqueue and Enqueue Replication Server is running, you must configure Veritas Cluster Server to run under Solaris non-global zones.

Also, ensure that the zone and the Enqueue server have different IPs. This is required because the Enqueue Server (that is, the application running inside the zone) fails over between the zones, but the zone itself does not failover.