| Oracle® Fusion Applications Installation Guide for Oracle VM 11g Release 1 (11.1.4) Part Number E26570-07 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Installation Guide for Oracle VM 11g Release 1 (11.1.4) Part Number E26570-07 |
|
|
PDF · Mobi · ePub |
This chapter describes the steps for the deployment of Oracle VM templates.
This chapter includes the following sections:
From the FAS/deployfw/deployprops directory created in Section 2.12, "Install the Oracle VM Automation Utility", copy the ovm- crm|fscmh|hcm-deploy.properties file to the ova-ha-deploy.properties file, depending on which topology you are deploying. This file contains the input properties for the deployment instance that are required for creating a topology from the templates. The properties file should be modified as described in the following steps. Each step includes an example of the file properties to be modified.
Update the following properties to specify your Oracle VM Manager connection information and the default pool name.
faovm.ovmm.host=server01.com faovm.ovmm.port=8888 faovm.ovmm.secure.port=8889 faovm.ovmm.use.secure=false faovm.ovmm.username=admin faovm.ovmm.password=Welcome1
Update the following properties to specify the Oracle Enterprise Manager 12c Cloud Control (Cloud Control) information for the wiring for the Oracle Enterprise Manager agents inside the Oracle VMs.
faovm.emagent.oms.host=server01.com faovm.emagent.oms.ports=4889 faovm.emagent.agent.password=Welcome1
Update the following properties to specify your Cloud Control Oracle Management Server (OMS) Repository information.
faovm.oms.url=http://server01.com:4889/em/ faovm.oms.user=sysman faovm.oms.password=Welcome1 faovm.oms.db.host=server01.com faovm.oms.db.port=1521 faovm.oms.db.service.name=emdb.us.oracle.com
Update the following JVM Diagnostics properties to specify your Cloud Control OMS.
faovm.jvmd.host=server01.com faovm.jvmd.port=3600
Update the following properties to point to your storage server. Use faovm.storage.type to indicate the type of storage that you will use, for example, netapp, sun or genericnfs, and specify the properties for that storage type in subsequent sections.
# Storage-related properties, supported types: netapp, sun, genericnfs faovm.storage.type=netapp # location where the shared storage is mounted on the reference system (DO NOT CHANGE) faovm.storage.mount=/u01 # location to mount the deploy shared storage on deployer and VMs (MAY BE CHANGED) faovm.storage.physical.mount=/u1234 # Netapp Storage properties faovm.storage.netapp.host=server01 faovm.storage.netapp.username=fusionst faovm.storage.netapp.password=CHANGEME faovm.storage.netapp.containing-aggregate=emsprod01 # snapshot disable property should be set only in developer's environment faovm.storage.netapp.snapshot.disable=true # NFS options to use when mounting storage faovm.storage.netapp.nfs.export.root=/vol faovm.storage.netapp.nfs.mount.options=rw,tcp,hard,nointr,rsize=32768,wsize=32768,nfsvers=3,timeo=600 # Sun Storage properties faovm.storage.sun.host=server404 faovm.storage.sun.username=fusovm faovm.storage.sun.password=CHANGEME faovm.storage.sun.pool=pool-404 faovm.storage.sun.project=emsprod02 faovm.storage.sun.snapshot.disable=true # NFS options to use when mounting storage faovm.storage.sun.nfs.export.root=/export faovm.storage.sun.nfs.mount.options=rw,tcp,hard,nointr,rsize=131072,wsize=131072,nfsvers=3,timeo=600 # Generic, Predefined NFS faovm.storage.genericnfs.host=server123 faovm.storage.genericnfs.nfs.export.root=/vol faovm.storage.genericnfs.nfs.mount.options=rw,tcp,hard,nointr,rsize=32768,wsize=32768,nfsvers=3,timeo=600
If you plan to use the same template several times, you can use the pre-exported template storage feature. Instead of exporting template contents during deployment, this feature exports the template file system contents, once before you begin, and then each deployment uses clones of this volume to save time and space on the storage appliance.
To use this feature, set the following property to true:
# Controls whether createTopology will attempt to thin-provision storage # using exploded template storage already provisioned using the # createExportedTemplateStorage verb. Note: this can not be used when # the storage.type is genericnfs faovm.storage.use.exported.template=true
The following properties become relevant and should be set based on what storage type is in use:
# Settings used when using flex-cloning
faovm.storage.netapp.exported.template.nfs.export.root=${storage.netapp.nfs.export.root}
faovm.storage.netapp.exported.template.snapshot.name=faovm_exported_template_snapshot
# Settings used when using snapshot-cloning
faovm.storage.sun.exported.template.project=${storage.sun.project}
faovm.storage.sun.exported.template.nfs.export.root=${storage.sun.nfs.export.root}
faovm.storage.sun.exported.template.snapshot.name=faovm_exported_template_snapshot
The following properties are used to construct the names and sizes of the volumes used for the base exported template volume and need to be updated only when using netapp flexclones because the "-" character is not allowed in volume names:
faovm.ha.fa.storage.exported.template.size=80g
faovm.ha.fa.storage.exported.template.name=${faovm.ha.fa.vm.template.name}
faovm.ha.primary.storage.exported.template.name=${faovm.ha.fa.storage.exported.template.name}
faovm.ha.secondary.storage.exported.template.name=${faovm.ha.fa.storage.exported.template.name}
faovm.ha.bi.storage.exported.template.name={faovm.ha.fa.storage.exported.template.name}
faovm.ha.ohs.storage.exported.template.size=8g
faovm.ha.ohs.storage.exported.template.name=${vm.template.name}
faovm.ha.webchat.storage.exported.template.size=10g
faovm.ha.webchat.storage.exported.template.name=${vm.template.name}
(Optional) Update the following properties for your system and VNC console credentials for the Oracle VMs.
faovm.os.vnc.console.password=Welcome1 faovm.os.system.user.name=root faovm.os.system.user.password=Welcome1
(Optional) Update the following properties to specify the operating system (OS) user and group name and IDs for the OS user that owns the Netapp volumes:
faovm.os.apps.user.name=oracle faovm.os.apps.user.password=Welcome1 faovm.os.apps.user.id=1000 faovm.os.apps.user.group.name=dba faovm.os.apps.user.group.id=1001 faovm.os.apps.user.home.dir=/home/oracle
Update the following properties to configure the eth0 network for the Oracle VMs. These settings may be the same as the setting of the Hypervisors where the Oracle VMs will be started.
If you have Oracle VMs spread across different Hypervisors that happen to be located in a different subnet, then you can add additional properties for the specific combination of topology type and Oracle VM host type. The format of the additional properties is faovm.topologyType.hostType.network.X, where topologyType = ha, hostType takes one of the values from ohs|fa|primary|secondary|bi|webchat|idm1|idm3db|idm3mw|idm3ohs, and X is the remainder of the property such as dns.server, eth0.gateway, and so on.
The following properties are the default network properties for all Oracle VM host types:
faovm.os.network.dns.server=144.20.190.70 faovm.os.network.eth0.gateway=10.232.144.1 faovm.os.network.eth0.netmask=255.255.248.0
Update the following properties for your BIG IP end point host and ports. Note that ports are optional.
faovm.ha.bigip.mapping.fs.host.external=fscmhcm-cln-large-fs-ext.us.oracle.com faovm.ha.bigip.mapping.fs.port.external=10614 faovm.ha.bigip.mapping.fs.host.internal=fscmhcm-cln-large-fs-int.us.oracle.com faovm.ha.bigip.mapping.crm.host.external=fscmhcm-cln-large-crm-ext.us.oracle.com faovm.ha.bigip.mapping.crm.port.external=10616 faovm.ha.bigip.mapping.crm.host.internal=fscmhcm-cln-large-crm-int.us.oracle.com faovm.ha.bigip.mapping.fin.host.external=fscmhcm-cln-large-fin-ext.us.oracle.com faovm.ha.bigip.mapping.fin.port.external=10604 faovm.ha.bigip.mapping.fin.host.internal=fscmhcm-cln-large-fin-int.us.oracle.com faovm.ha.bigip.mapping.scm.host.external=fscmhcm-cln-large-scm-ext.us.oracle.com faovm.ha.bigip.mapping.scm.port.external=10618 faovm.ha.bigip.mapping.scm.host.internal=fscmhcm-cln-large-scm-int.us.oracle.com faovm.ha.bigip.mapping.hcm.host.external=fscmhcm-cln-large-hcm-ext.us.oracle.com faovm.ha.bigip.mapping.hcm.port.external=10620 faovm.ha.bigip.mapping.hcm.host.internal=fscmhcm-cln-large-hcm-int.us.oracle.com faovm.ha.bigip.mapping.prj.host.external=fscmhcm-cln-large-prj-ext.us.oracle.com faovm.ha.bigip.mapping.prj.port.external=10606 faovm.ha.bigip.mapping.prj.host.internal=fscmhcm-cln-large-prj-int.us.oracle.com faovm.ha.bigip.mapping.prc.host.external=fscmhcm-cln-large-prc-ext.us.oracle.com faovm.ha.bigip.mapping.prc.port.external=10608 faovm.ha.bigip.mapping.prc.host.internal=fscmhcm-cln-large-prc-int.us.oracle.com faovm.ha.bigip.mapping.prc.supplierportal.host.external=fscmhcm-cln-large-prc-sp-ext.us.oracle.com faovm.ha.bigip.mapping.prc.supplierportal.port.external=10610 faovm.ha.bigip.mapping.prc.supplierportal.host.internal=fscmhcm-cln-large-prc-sp-int.us.oracle.com faovm.ha.bigip.mapping.bi.host.external=fscmhcm-cln-large-bi-ext.us.oracle.com faovm.ha.bigip.mapping.bi.port.external=10622 faovm.ha.bigip.mapping.bi.host.internal=fscmhcm-cln-large-bi-int.us.oracle.com faovm.ha.bigip.mapping.default.port.external=443
If external ports are not specified, they are configured with the default value of 443.
This step includes updating Oracle RAC database properties and database directories.
Update the following properties to specify Oracle RAC database properties. Specify the following values that you collected when setting up the Oracle RAC instance in Section 2.7.2, "Set Up an Oracle Real Application Clusters (RAC) Database":
- Oracle RAC service name
- Physical host names for the two-node Oracle RAC database
- SID values for the two-node Oracle RAC database
- Listener port for the two-node Oracle RAC database, where the ports must be the same on each instance
- Oracle home
- Operating system user credentials that own the Oracle RAC instance, generally for the oracle user
- SYS schema credentials
- Oracle Automatic Storage Management DATA disc and REDO disc names
Examples follow:
faovm.ha.fusiondb.new.service.name=dbm
faovm.ha.fusiondb.rac.new.sid1=dbm1
faovm.ha.fusiondb.rac.new.sid2=dbm2
faovm.ha.fusiondb.clone.enabled=true
faovm.ha.fusiondb.src.backup.dir=db <an absolute path or relative path to $OVABHOME/db, where db backup archive is located >
faovm.ha.fusiondb.src.backup.archive=${fusiondb.src.backup.dir}
/dbbackup.tar.gz <path to the RMAN backup archive
>
faovm.ha.fusiondb.clone.do.backup.push=true <this enables the deploy to untar the DB tar ball directly to target DB, make sure there is enough disk space on target DB.>
faovm.ha.fusiondb.clone.backup.stage.path=<path to where src.backup.archive should be staged on the HOST1 of the target DB. If do.backup.push is enabled, the backup.archive will be exploded to this location during deployment. This is a non-ASM path.>
faovm.ha.fusiondb.clone.host.user.name=oracle
faovm.ha.fusiondb.clone.host.user.password=<CHANGE ME>
faovm.ha.fusiondb.clone.sys.user.name=sys
faovm.ha.fusiondb.clone.sys.user.password=welcome1
faovm.ha.fusiondb.clone.oracle.home=/u01/app/oracle/product/11.2.0/dbhome_1
faovm.ha.fusiondb.clone.datadisc=DATA
faovm.ha.fusiondb.clone.recodisc=RECO
faovm.ha.fusiondb.clone.datafile.path=${fusiondb.clone.datadisc}/${fusiondb.new.service.name}/datafile
faovm.ha.fusiondb.clone.tempfile.path=${fusiondb.clone.datadisc}/${fusiondb.new.service.name}/tempfile
faovm.ha.fusiondb.clone.recolog.path=${fusiondb.clone.recodisc}/${fusiondb.new.service.name}/ONLINELOG
faovm.ha.fusiondb.clone.spfile=+${fusiondb.clone.datadisc}/${fusiondb.new.service.name}/spfile${fusiondb.new.service.name}.ora
# physical host 1 for 2-node RAC
faovm.ha.HOST_DB=adcdba04.us.oracle.com
# physical host 2 for 2-node RAC
faovm.ha.HOST_DB2=adcdba05.us.oracle.com
Note:
The Oracle Automatic Storage Management directory structures defined by the variables below must exist and be writable:
faovm.ha.fusiondb.new.datadisc=DATA
faovm.ha.fusiondb.new.recodisc=RECO
faovm.ha.fusiondb.new.datafile.path=${fusiondb.new.datadisc}/${fusiondb.new.sid}/datafile
faovm.ha.fusiondb.new.tempfile.path=${fusiondb.new.datadisc}/${fusiondb.new.sid}/tempfile
faovm.ha.fusiondb.new.recolog.path=${fusiondb.new.recodisc}/${fusiondb.new.sid}/ONLINELOG
faovm.ha.fusiondb.new.spfile=+${fusiondb.new.datadisc}/${fusiondb.new.sid}/spfile${fusiondb.new.sid}.ora
For each of the above directory structures in Oracle Automatic Storage Management, the following must exist and can be created using asmcmd:
+DATA/hcmtest1/datafile+DATA/hcmtest1/tempfile+RECO/hcmtest1/ONLINELOG
In addition, if specifying a path in the controlfile location, the directory structure *.control_files='+DATA/hcmtest1/controlfile/control01.ctl','+DATA/hcmtest1/controlfile/control02.ctl' must exist before you run the command.
Review and update, if necessary, the following properties that specify the paths for database directory objects in the database:
# dba_directories configuration (can add as many as needed)
faovm.ha.fusiondb.new.oracle.base=/u01/app/oracle/product/11.2.0_CHANGEME
faovm.ha.fusiondb.new.dba.dir.name0=APPLCP_FILE_DIR
faovm.ha.fusiondb.new.dba.dir.path0=${fusiondb.new.oracle.home}/incident_logs
faovm.ha.fusiondb.new.dba.dir.name1=APPLLOG_DIR
faovm.ha.fusiondb.new.dba.dir.path1=${fusiondb.new.oracle.home}/appllog_dir
faovm.ha.fusiondb.new.dba.dir.name2=ADMIN_DIR
faovm.ha.fusiondb.new.dba.dir.path2=${fusiondb.new.oracle.home}/rdbms/admi
faovm.ha.fusiondb.new.dba.dir.name3=EQ_CONFIG_DIR
faovm.ha.fusiondb.new.dba.dir.path3=${fusiondb.new.oracle.home}/search/webapp/config
faovm.ha.fusiondb.new.dba.dir.name4=XMLDIR
faovm.ha.fusiondb.new.dba.dir.path4=${fusiondb.new.oracle.home}/rdbms/xml
faovm.ha.fusiondb.new.dba.dir.name5=EQ_LANG_DIR
faovm.ha.fusiondb.new.dba.dir.path5=${fusiondb.new.oracle.home}/search/data/language
faovm.ha.fusiondb.new.dba.dir.name6=ORACLE_OCM_CONFIG_DIR
faovm.ha.fusiondb.new.dba.dir.path6=${fusiondb.new.oracle.home}/ccr/state
faovm.ha.fusiondb.new.dba.dir.name7=DATA_PUMP_DIR
faovm.ha.fusiondb.new.dba.dir.path7=${fusiondb.new.oracle.base}/admin/${fusiondb.new.service.name}/dpdump
faovm.ha.fusiondb.new.dba.dir.name8=EQ_CACHE_DIR
faovm.ha.fusiondb.new.dba.dir.path8=${fusiondb.new.oracle.base}/oradata/${fusiondb.new.service.name}/cache
For most directories, their paths are relative to fusiondb.new.oracle.home, so the default value should be sufficient. The DATA_PUMP_DIR and EQ_CACHE_DIR directories depend on the value of the fusiondb.new.oracle.base property by default. Specify a value for the fusiondb.new.oracle.base property if you want to use the default values for the DATA_PUMP_DIR and EQ_CACHE_DIR directories.
Update the following properties for the host names of the Oracle VMs for the topologies to be deployed.
faovm.ha.HOST_FA=adc2130516.us.oracle.com_CHANGEME faovm.ha.HOST_PRIMARY=adc2130517.us.oracle.com_CHANGEME faovm.ha.HOST_SECONDARY=adc2130518.us.oracle.com_CHANGEME faovm.ha.HOST_BI=adc2130519.us.oracle.com_CHANGEME faovm.ha.HOST_OHS=adc2130505.us.oracle.com_CHANGEME faovm.ha.HOST_WEBCHAT=adc2130527.us.oracle.com_CHANGEME
Update the following properties for your Oracle VMs for the HA nodes if you plan to create a High Availability Oracle VM.
faovm.ha.HOST_PRIMARY_HA1=adc2130531.us.oracle.com_CHANGEME faovm.ha.HOST_SECONDARY_HA1=adc2130532.us.oracle.com_CHANGEME faovm.ha.HOST_OHS_HA1=adc2130506.us.oracle.com
The creation of HA nodes for Primary, Secondary, and OHS Oracle VMs as part of createTopology is disabled by default with the following settings in ovm-ha-deploy.properties. If you want the HA nodes for primary and secondary Oracle VMs to also be created, set the following properties to true:
faovm.ha.primary.create.ha.node=true faovm.ha.secondary.create.ha.node=true faovm.ha.ohs.create.ha.node=true
Update the following properties to point to your external dependency hosts, for example, LDAP, IDMDB, OAM, OIM, and so on.
# host 1 for 2-node RAC faovm.ha.HOST_DB=adcdba04.us.oracle.com # host 2 for 2-node RAC faovm.ha.HOST_DB2=adcdba05.us.oracle.com faovm.ha.HOST_LDAP=adcgby14.us.oracle.com faovm.ha.HOST_IDMDB=adcgby14.us.oracle.com faovm.ha.HOST_PSTORE=adcgby14.us.oracle.com faovm.ha.HOST_WEBGATE=adcgby14.us.oracle.com faovm.ha.HOST_OAM=adcgby14.us.oracle.com faovm.ha.HOST_OIM=adcgby14.us.oracle.com faovm.ha.HOST_SMTP=adc2170258.us.oracle.com
Note that hosts specified in Steps 12, 13, and 14 are used to identify the IP addresses to update /etc/hosts during rehydration of each Oracle VM.
Specify the template name that you previously registered with Oracle VM Manager, and any VM-specific properties for the FA node.
faovm.ha.fa.ovmm.pool.name=adcgei12-pool faovm.ha.fa.vm.template.name=ha-fscmh-v1-mt_20111013_fa faovm.ha.fa.cpus=6 faovm.ha.fa.memory=13312 faovm.ha.fa.netapp.volume.name=ha_fscmh_v1_fa faovm.ha.fa.netapp.volume.size=120g
Update VM-specific properties for the Primary node. The Primary node uses the same template as the FA node and shares the same volume.
faovm.ha.primary.ovmm.pool.name=adcgei12-pool faovm.ha.primary.cpus=12 faovm.ha.primary.memory=20480
Update VM-specific properties for the Secondary node. The Secondary node uses the same template as the FA node and shares the same volume.
faovm.ha.secondary.ovmm.pool.name=adcgei12-pool faovm.ha.secondary.cpus=24 faovm.ha.secondary.memory=51200
Specify the template name that you previously registered with OVM manager and any VM-specific properties for the BI node. The BI node shares the volume with the FA node.
faovm.ha.bi.ovmm.pool.name=adcgei12-pool faovm.ha.bi.vm.template.name=ha-fscmh-v1-mt_20111013_bi faovm.ha.bi.cpus=4 faovm.ha.bi.memory=6144
Specify the template name that you previously registered with Oracle VM Manager and any VM-specific properties for the OHS node. The OHS node has its own volume.
faovm.ha.ohs.ovmm.pool.name=adcgei12-pool faovm.ha.ohs.vm.template.name=ha-fscmh-v1-mt_20111013_ohs faovm.ha.ohs.cpus=2 faovm.ha.ohs.memory=1024 faovm.ha.ohs.netapp.volume.name=ha_fscmh_v1_ohs faovm.ha.ohs.netapp.volume.size=12g
Specify the template name that you previously registered with Oracle VM manager and any VM-specific properties for the WebChat node. The WebChat node has its own volume so you must replace user_webchat_CHANGEME with the file system that you allocated to the WebChat Node. See Section 2.5, "Provide Access to NetApp or Sun Storage Server" for more information.
faovm.ha.webchat.ovmm.pool.name=adcgei12-pool faovm.ha.webchat.vm.template.name=ha-fscmh-v1_20111013_webchat faovm.ha.webchat.cpus=4 faovm.ha.webchat.memory=5120 faovm.ha.webchat.storage.size=12g faovm.ha.webchat.storage.name=user_webchat_CHANGEME
For deployment of a single-tenant IDM based topology, specify the template name that you previously registered with Oracle VM Manager and any VM-specific properties for the IDM node. The IDM node has its own volume so you must replace user_idm_CHANGEME with the file system that you allocated to the IDM node. See Section 2.5, "Provide Access to NetApp or Sun Storage Server" for more information.
faovm.ha.idm1.ovmm.pool.name=adcgei12-pool faovm.ha.idm1.vm.template.name=ha-fscmh-v1_20111013_idm faovm.ha.idm1.cpus=4 faovm.ha.idm1.memory=16384 faovm.ha.idm1.storage.size=70g faovm.ha.idm1.storage.name=user_idm_CHANGEME
You may find that the ovm-ha-deploy.properties file has more properties defined than the ones listed in this section. You do not need to change the values of these properties.
Save the ovm-ha-deploy.properties file after you complete your updates.
This section lists additional deployment properties added in this release, as well as their default values. You can make changes to these properties to suit your needs and then continue with deployment.
Property for specifying privilege escalation pbrun policy name:
faovm.privilege.escalation.pbrun.policy.name=policy1-root
Properties for enabling/disabling agent for Java VM Diagnostics and specifying its version:
faovm.jvmd.enabled=${emagent.install.enabled}
faovm.jvmd.agent.version=12c
Property for specifying ODI repository identifier:
faovm.odi.repository.id=502
Property for enabling ODI for HR2HR (HCM Coexistence):
faovm.hcm.hr2hr.odi.config.enable=false
Properties for Secure File Transfer Protocol (FTP):
faovm.sftp.config.enabled=false faovm.sftp.username=user faovm.sftp.password=pwd faovm.sftp.server.host=sftp.cloud.oracle.com faovm.sftp.server.port=2021
Property for removing WebGate configuration:
faovm.ha.ohs.remove.webgate.conf=false
Property for specifying sendmail configuration and enabling sendmail feature:
faovm.sendmail.smart.host=smtp.oracleoutsourcing.com faovm.sendmail.daemon.options='Port=submission,Addr=127.0.0.1, Name=MSA, M=E ' faovm.sendmail.submit.feature.msp=' [127.0.0.1] ', 'MSA' faovm.ha.sendmail.enabled=false faovm.ha.primary.sendmail.enabled=true faovm.ha.secondary.sendmail.enabled=true faovm.ha.bi.sendmail.enabled=true faovm.ha.idm1.sendmail.enabled=true faovm.ha.idm1.sendmail.smart.host=auohs-smtp.oracle.com faovm.ha.idm1.sendmail.daemon.options='Port=smtp,Addr=127.0.0.1, Name=MTA ' faovm.ha.idm3mw.sendmail.submit.feature.msp=' [127.0.0.1] '
The default values for these deployment properties have changed from the previous release:
faovm.emagent.install.enabled=true #faovm.mtidm.source.tennant.id=17099669285212912 #faovm.mtidm.source.tenant.name=acme #faovm.mtidm.source.enterprise.id=17099669285215912 #faovm.mtidm.source.jps.root=cn=acme.FAService,cn=OPSS faovm.lstorage.sun.nfs.mount.options=rw,hard,nointr,rsize=131072,wsize=131072,timeo=600,noacl,noatime,nodiratime faovm.storage.genericnfs.nfs.mount.options=rw,hard,nointr,rsize=32768,wsize=32768,timeo=600 #faovm.storage.vm.aux.mount0.nfs.mount.options=rw,tcp,hard,nointr,rsize=32768,wsize=32768,timeo=600 faovm.ha.bigip.mapping.ic.host.external=crm-cln-ha-ic-ext.us.oracle.com faovm.ha.bigip.mapping.ic.port.external=10612 faovm.ha.bigip.mapping.ic.host.internal=crm=cln-ha-ic-int.us.oracle.com faovm.ha.HOST_SMTP=adcemodmx.atoracle.com faovm.ha.fa.memory=20480 faovm.ha.fa.originally.provisioned.memory=26624 faovm.ha.primary.cpus=6 faovm.ha.primary.memory=17408 faovm.ha.primary.originally.provisioned.memory=19456 faovm.ha.idm1.standalone.file.archive0=idm/u01_dboid.tar.gz faovm.ha.idm1.storage.size=90g faovm.ha.idm1.storage.exported.template.size=80g #faovm.ha.idm1.faapsadmin.username=FAAdmin_CHANGEME #faovm.ha.idm1.faapsadmin.password=CHANGEME faovm.ha.idm3db.standalone.file.archive0=idm/u01_dboid.tar.gz faovm.ha.idm3db.storage.size=70g faovm.ha.idm3db.storage.exported.template.size=65g faovm.ha.webchat.lockfile=/dev/shm/ohs_webchat_http_lock faovm.ha.idm1.lockfile=/dev/shm/ohs_auth_http_lock faovm.ha.idm3ohs.lockfile=/dev/shm/ohs_auth_http_lock faovm.ha.ohs.lockfile=/dev/shm/ohs_ohs1_http_lock
This step initiates the creation of the Oracle Fusion Applications topology, including Oracle Identity Management, onto the Oracle VM systems.
Set the following environment variables.
setenv OVAB_HOME path_to_your_ovab_home setenv JAVA_HOME path_to_jre (in OVAB_HOME/jre) or path_to_JDK_1.6 setenv FAOVM path_to_ovm_utility export ABUSERPROPS="-Dassemblybuilder.runtime.nolock=true"
Note that the path_to_ovm_utility refers to the directory you created in Section 2.12, "Install the Oracle VM Automation Utility".
Run the faovmdeploy.sh utility to create exported template storage. This step is optional and should be used only if you followed Step 6 in Section 3.1, "Prepare Deployment Properties".
cd $FAOVM/deployfw/bin ./faovmdeploy.sh createExportedTemplateStorage type=ha
This utility operates on all host types for which storage is created, such as ohs, fa, webchat, and idm hosts. It does not operate on hosts that share storage, such as primary and secondary hosts.
This utility generates a log file for the creation of your topology in the directory, $FAOVM/deployfw/logs.
An example of the output follows:
[13:33:13/ohs] Executing Task: Create Sun Storage Share - ha-crm-v1r1-mt_20111213_ohs ... Done. [0m45s] [13:33:59/ohs] Executing Task: Mount Storage - /u1234 ... Done. [0m1s] [13:34:00/ohs] Executing Task: Change Storage Owner to Deploy User - /u1234 ... Done. [0m11s] [13:34:12/ohs] Executing Task: Read Shared File Sets ... Done. [0m28s] [13:34:41/ohs] Executing Task: Export File Sets ... [13:34:41/ohs] Executing Task: Export File Set - fmwHome ... Done. [8m29s] [13:43:10/ohs] Executing Task: Export File Set - webgate ... Done. [0m49s] [13:44:00/ohs] Executing Task: Export File Set - ora_inventory ... Done. [0m26s] [13:44:26/ohs] Executing Task: Export File Set - ovabext ... Done. [0m26s] [13:44:52/ohs] Executing Task: Export File Set - EMAgent ... Done. [0m44s] ... Done. [10m55s] [13:45:36/ohs] Executing Task: Unmount Storage - /u1234 ... Done. [0m1s] [13:45:44/ohs] Executing Task: Create Sun Storage Snapshot - ha-crm-v1r1-mt_20111213_ohs@faovm_exported_template_snapshot ... Done. [0m8s] [13:45:52/fa] Executing Task: Create Sun Storage Share - ha-crm-v1r1-mt_20111213_fa ... Done. [0m31s]
Run the faovmdeploy.sh utility to create an Oracle VM.
cd $FAOVM/deployfw/bin ./faovmdeploy.sh createTopology type=ha
This utility generates a log file for the creation of your topology in the directory, $FAOVM/deployfw/logs.
An example of the output follows:
[19:40:59] Starting createTopology execution for FSCM+HCM HA Topology [19:40:59/ohs] Executing Task: Create Volume - ilawler_ohs ... Done. [0m9s] [19:41:08/ohs] Executing Task: Change Volume Owner ... Done. [0m5s] [19:41:13/ohs] Executing Task: Read Shared File Sets ... Done. [0m32s] [19:41:46/ohs] Executing Task: Export File Sets ... [19:41:46/ohs] Executing Task: Export File Set - fmwHome ... Done. [3m46s] [19:45:33/ohs] Executing Task: Export File Set - ORACLE_INSTANCE ... Done. [0m40s] [19:46:14/ohs] Executing Task: Export File Set - webgate ... Done. [0m43s] [19:46:57/ohs] Executing Task: Export File Set - ovabext ... Done. [0m31s] [19:47:29/ohs] Executing Task: Export File Set - EMAgent ... Done. [0m38s] ... Done. [6m21s] [19:48:07/ohs] Executing Task: Instantiate Rehydration Templates ... Done. [0m5s] [19:48:12/ohs] Executing Task: Copy Rehydrate Framework Files to Volume ... Done. [0m0s] [19:48:13/ohs] Executing Task: Stage Rehydration Patches ... Done. [0s] [19:48:13/ohs] Executing Task: Fix APPLTOP Permissions ... Done. [0m15s] [19:48:29/ohs] Executing Task: Change Volume Owner ... Done. [0m24s] [19:48:53/ohs] Executing Task: Create OVM - adc2130518.us.oracle.com ... Done. [3m35s] [19:52:29/ohs] Executing Task: Unmount Volume Mount Point - /u01 ... Done. [0m5s] ..... [19:52:35] Completed createTopology execution for CRM Small Topology [11m35s]
The faovmdeploy.sh command completes after the storage volumes are created and populated and the Oracle VMs are powered on. The rehydration of the domains continues within each individual Oracle VM even after the command completes.
Use the status argument to check the status of the createTopology session. You can check the status of the entire topology with this command:
cd $FAOVM/deployfw/bin ./faovmdeploy.sh status type=ha
You can also check the status of a single node type by specifying the hostType argument:
cd $FAOVM/deployfw/bin ./faovmdeploy.sh status type=ha hostType=[ohs|fa|primary|secondary|bi]
To manually check the status of each Oracle VM, log in to each Oracle VM using the root credentials that you specified, and monitor the rehydration progress within that Oracle VM.
For example, to check progress of the FA node, log in to the FA Oracle VM and run this command:
cd /u01/APPLTOP/ovabext/crmapps.oracleoutsourcing.com/CRMDomain ls wls-latebinding-*.out
This command lists the Managed Servers for the CRMDomain, such as the Administration Server and Managed Servers, that have been rehydrated so far. An example of the output follows:
-rw-r-r- 1 root root 33 May 12 03:50 wls-latebinding-CRMDomain-AdminServer.properties.out -rw-r-r- 1 root root 33 May 12 03:53 wls-latebinding-CRMDomain-ODICluster.properties.out -rw-r-r- 1 root root 33 May 12 03:56 wls-latebinding-CRMDomain-EmailMarketingCluster.properties.out -rw-r-r- 1 root root 33 May 12 04:00 wls-latebinding-CRMDomain-ContractManagementCluster.properties.out -rw-r-r- 1 root root 33 May 12 04:05 wls-latebinding-CRMDomain-SalesCluster.properties.out -rw-r-r- 1 root root 33 May 12 04:10 wls-latebinding-CRMDomain-CRM_SOACluster.properties.out -rw-r-r- 1 root root 33 May 12 04:14 wls-latebinding-CRMDomain-CRMAnalyticsCluster.properties.out -rw-r-r- 1 root root 33 May 12 04:18 wls-latebinding-CRMDomain-MarketingCluster.properties.out -rw-r-r- 1 root root 33 May 12 04:22 wls-latebinding-CRMDomain-CustomerCluster.properties.out -rw-r-r- 1 root root 33 May 12 04:27 wls-latebinding-CRMDomain-CRMPerformanceCluster.properties.out -rw-r-r- 1 root root 33 May 12 04:33 wls-latebinding-CRMDomain-CRMCommonCluster.properties.out -rw-r-r- 1 root root 33 May 12 04:38 wls-latebinding-CRMDomain-OrderCaptureCluster.properties.out -rw-r-r- 1 root root 33 May 12 04:41 wls-latebinding-CRMDomain-CRMSearchCluster.properties.out -rw-r-r- 1 root root 33 May 12 04:45 wls-latebinding-CRMDomain-ESSCluster.properties.out
Each file contains the following text if the rehydration of that Managed Server was successful:
/u01/APPLTOP/ovabext/crmapps.oracleoutsourcing.com/CRMDomain/wls-latebinding-CRMDomain-AdminServer.properties.out deployer.rehydration-result = OK
Additional log files related to rehydration are located under the /assemblybuilder/log directory within the Oracle VM.
Perform the following steps after rehydration completes successfully:
Note:
In the following sections, references to hosts, such as HOST_SECONDARY and HOST_BI, represent the host names that you defined in Steps 12 through 14 in Section 3.1, "Prepare Deployment Properties". You must replace them with the host names in your environment to perform the manual steps.
Complete the following post-rehydration step that is related to Oracle VM.
After Oracle VM deployment is complete, follow the manual "Postinstallation Tasks" described in the Oracle Fusion Applications Installation Guide.
Complete the following post-rehydration step.
After Deployment, a user who tries to access some URLs may not see the Single Sign-On page. If this is the case, perform the following manual steps:
Locate the file /u02/instance/CommonDomain_webtier)local/config/OHS/ohs1/httpd.conf
Using a text editor, add the following to the end of the file:
include /u02/instance/CommonDomain_webtier_local/config/OHS/ohs1/webgate.conf
Bounce OHS
Apply the mandatory Oracle Fusion Middleware patches. For more information, see "Oracle Fusion Middleware" in Oracle Fusion Applications release notes.
Refer to Oracle Fusion Applications release notes for information related to any additional patches that must be applied after Oracle VM deployment.
You must now perform the necessary implementation and functional setup tasks.
For complete information about setting up and managing passwords for your new environment, see "Securing Oracle Fusion Applications" and "Provisioning Identities" in Oracle Fusion Applications Administrator's Guide
Before you can start using any of the product offerings you have installed, you must complete some common implementation tasks and enable the functionality of the offerings in your environment.
A large library of product-related documentation is available for use after provisioning. Some of the guides that you will find useful are listed here:
Oracle Fusion Applications Information Technology Management, Implement Applications Guide
Product-specific Oracle Fusion Applications implementation guides
These are other life cycle management tasks that might be useful for your Oracle VM installation.
To scale out the OHS node, first prepare the ovm-ha-deploy.properties file by updating the scale-out Oracle VM information. You must specify your Oracle VM host names. Other properties are determined automatically based on the specifications for the base OHS Oracle VM.
faovm.ha.HOST_OHS_SCALE1=server02.com
You must add the number of scale-out host names based on the number of scale out OHS Oracle VM. Update environment information in POD's excel sheets that you want to create.
To execute the scale out:
cd $FAOVM/deployfw/bin ./faovmdeploy.sh scaleoutOHS type=ha scaleoutInstances=1
To scale out the Primary node, first prepare the ovm-ha-deploy.properties file by updating the scale-out Oracle VM information. You must specify your Oracle VM host names. Other properties are determined automatically based on the specifications for the base Primary Oracle VM.
faovm.ha.HOST_PRIMARY_SCALE1=adc2130529.us.oracle.com
You must add the number of scale-out host names based on the number of scale out Primary Oracle VMs that you want to create.
To execute the scale out:
cd $FAOVM/deployfw/bin ./faovmdeploy.sh scaleoutApps type=ha scaleoutInstances=1
If you want to remove a topology that you previously created, use the cleanupTopology argument with faovmdeploy.sh.
cd $FAOVM/deployfw/bin ./faovmdeploy.sh cleanupTopology type=ha
Additionally, if you want to reset the Oracle RAC database to its original state, you can do this by dropping the data files. You should drop these data files only if you are certain that you want to destroy the topology. An example script follows:
startup nomount pfile='/tmp/workpfile.ora'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/system01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/sysaux01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_undo01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_transaction_table_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_transaction_table_02.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_transaction_table_03.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_transaction_table_04.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_transaction_table_05.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_transaction_table_06.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/SEARCH_INDEX_1.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_ias_sdpmaq_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_archive_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_dq_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_interface_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_nologging_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/otbi_biacmts_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_seed_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_dyn_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_queues_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_aq_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/SEARCH_DATA_1.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_media_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_summary_01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/bee_data.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/bee_index.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/bee_seed.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/bee_interface.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/bee_audit.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/bee_archive.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/bee_queues.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/bee_lobs.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/bee_search_data.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/bee_search_index.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/bee_search_lobs.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/BEE_mds.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/fusion_temp01.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/SEARCH_TEMP_1.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/BEE_iastemp.dbf'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/redo01.log'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/redo02.log'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/redo03.log'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/redo01b.log'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/redo02b.log'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/redo03b.log'; ALTER DISKGROUP DATA_SLCC10 drop file '+DATA_SLCC10/undotbs2.dbf'; shutdown; quit;
If you previously used the pre-exported template storage feature, as described in Step 6 under Section 3.1, "Prepare Deployment Properties", you can remove these templates by using the cleanupExportedTemplateStorage command. Do not use this command if any topologies exist with volumes that are clones of the base exported template storage volumes and shares. If you run this command when these clones exist, the command will fail and it may also remove all of the storage for those clones. The command syntax follows:
cd $FAOVM/deployfw/bin ./faovmdeploy.sh cleanupExportedTemplateStorage type=ha
If you want to rerun a deployment, reset the database and reexecute the restore process because some steps cannot be rerun on a database that has already undergone a deployment and rehydration. To reset the database, create a shell script /tmp/resetdb.xxxx.sh, where xxxx is the source database name, to help stop the database and drop or remove the data files.
The following troubleshooting scenarios are included in this section.
During rehydration, if for some reason, you need to log in to an Oracle VM and manually re-trigger rehydration for that Oracle VM by invoking abinit-host.sh, remember to set the following environment variables first:
export JAVA_HOME=/assemblybuilder/jre export PATH=$PATH:$JAVA_HOME/bin
|
 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|