| Oracle® Fusion Applications Installation Guide for Oracle VM 11g Release 1 (11.1.3) Part Number E26570-05 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Installation Guide for Oracle VM 11g Release 1 (11.1.3) Part Number E26570-05 |
|
|
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 11g Grid Control (Grid 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 Grid 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 Grid 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 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 steps that are related to Oracle VM.
After Oracle VM deployment is complete, follow the manual "Postinstallation Tasks" described in the Oracle Fusion Applications Installation Guide.
After Oracle VM deployment, the Oracle Business Intelligence connection URLs contain invalid entries that cause errors in the setup page of Financials Reports and Analytics. The solution is to manually edit the StaticResourcesLocation property, using the System MBean Browser in Oracle Enterprise Manager, with the correct external load balancer URL for Oracle Business Intelligence. All of the affected applications on the Oracle WebLogic Server managed servers that have a BISoapConnection type must be examined, corrected, and restarted to resolve this issue. Table 3-1 lists the affected applications.
Table 3-1 Affected Applications
| Domain | Server | Application |
|---|---|---|
|
Common |
HomePageServer |
HomePageApp |
|
CRM |
CustomerServer |
CustomerApp |
|
CRM |
MarketingServer |
MarketingApp |
|
CRM |
CRMPerformanceServer |
CRMPerformanceApp |
|
CRM |
SalesServer |
SalesApp |
|
FIN |
GeneralLedgerServer |
LedgerApp |
|
FIN |
PayablesServer |
PayablesApp |
|
FIN |
ReceivablesServer |
ReceivablesApp |
|
HCM |
CompensationServer |
HcmCompensationApp |
|
HCM |
CoreProcessesServer |
HcmCoreApp |
|
HCM |
TalentManagementServer |
HcmTalentApp |
|
IC |
IncentiveCompensationServer |
IncentiveCompensationApp |
|
PRC |
ess_server |
ProcurementEssApp |
|
PRC |
ProcurementServer |
ProcurementApp |
|
PRC |
SupplierPortalServer |
SupplierPortalApp |
|
PRJ |
ProjectFinancialsServer |
ProjectFinancialsApp |
|
SCM |
CostManagementServer |
CostManagementApp |
|
SCM |
LogisticsServer |
LogisticsApp |
|
SCM |
OrderOrchestrationServer |
OrderOrchestrationApp |
|
SCM |
ProductManagement |
ProductManagementApp |
The following steps describe how to edit BISoapConnection objects.
Log in to Oracle Enterprise Manager for each of the product family domains listed in Table 3-1.
Go to System MBean Browser by right clicking the domain target under Farm_Product_FamilyDomain, WebLogicDomain, then Product_FamilyDomain.
Go to Application Defined MBeans, then oracle.adf.share.connections where all servers and applications for the domain are displayed.
Go to each Oracle ADF connection using this navigation path: Server, Application, ADFConnections, ADFConnections. Edit the value of the StaticResourcesLocation property for all connections with type BISoapConnection. Note that the connections are of the type BISoapConnection and can have different names, for example, BIDB_Connection, AtkRPSoapConn, BIPresentationServer, CentralServerConn, MarketingServer, and so on.
Go to the Operations tab and click Save to save the changes to the underlying store and to ensure the values are not lost during server restarts.
Repeat Steps 1 through 5 for all of the affected applications, servers, clusters, and domains. Then restart the affected domains.
Edit the file /oem/app/oracle/product/12c/core/12.1.0.1.0/install/unix/scripts/agentstup inside the Oracle VM. Replace:
sudo > /dev/null 2>&1
With:
/bin/false #sudo > /dev/null 2>&1
Follow these steps to avoid possible failures during Oracle Enterprise Manager 12c Cloud Control discovery for the BI node:
Login to the BI Oracle VM as the applications system user, as specified by the faovm.os.apps.user.name property, and run the following commands.
cd /u01/APPLTOP/ovabext/emcli export JAVA_HOME=/assemblybuilder/jre export EMCLI_STATE_DIR=/u01/APPLTOP/ovabext/emcli/conf
Get the status of the BI Agent.
./emcli get_targets \-noheader \-targets="<BI Oracle VM host name>:<agent port>:oracle_emd" Example: ./emcli get_targets \-noheader \-targets="adc2130498.us.oracle.com:3875:oracle_emd"
Ensure that the status of BI Agent is Up before proceeding to the next step.
Restart the discovery of the BIDomain and the remaining rehydration commands on the BI Oracle VM by logging in to the BI Oracle VM as the root user and then running these commands:
cd /u01/APPLTOP/ovabext/bi.oracleoutsourcing.com
source faovm-host.env
export JAVA_HOME=/assemblybuilder/jre
export PATH=$PATH:$JAVA_HOME/bin
${AB_FAOVM_REHYDRATEFW_HOME}
/bin/rehydrate_assist.sh post-host-rehydrate 93.2
Login to the OIM Oracle VM.
Update -Dtangosol.coherence.clusteraddress=227.7.7.9 in the following files to have a different randomized value (not 7 or 9) for the 3rd and 4th segments of the numbers in the cluster address. In other words, x and y in -Dtangosol.coherence.clusteraddress=227.7.x.y should have a value between 1 to 254. Use the same value that you choose in all of the following files:
/u01/oim/user_projects/domains/oim_domain/bin/setDomainEnv.sh /u01/oim/user_projects/domains/oim_domain/init-info/startscript.xml /u01/oim/user_projects/domains/oim_domain/init-info/startscript-unsub.xml
Restart the OIM domain for these settings to be effective.
Modify the existing idm.conf file to be compatible with your deployment topology. This file is located under the following directory:
ohs_install_directory/ohsauth_inst/config/OHS/ohs1/moduleconf
Comment out all of the context-roots locations in the first virtual host (authohs.mycompany.com) after all of the Load Balancer (LBR) end points (for three virtual hosts) are configured. This prevents access to the context roots through the physical host but only through the LBR. An example follows:
# Admin Server and EM # <Location /console> # SetHandler weblogic-handler # WebLogicHost weblogic-host.mycompany.com # WeblogicPort 17001 # </Location>
Update the administration virtual host to be on https instead of http. For example, update http://admin.mycompany.com:7777 to be https:admin.mycompany.com:443. Oracle recommends that you have the administrative consoles exposed using https (LBR).
Add the RewriteRule to avoid the console logout issues from the Enterprise Manager and the WebLogic Administrator consoles.
RewriteEngine On RewriteRule ^/console/jsp/common/logout.jsp "/oamsso/logout.html?end_url=/console" [R] RewriteRule ^/em/targetauth/emaslogout.jsp "/oamsso/logout.html?end_url=/em" [R] RewriteOptions inherit UseCanonicalName On
Ensure the following ProxySSL entries exist for all the context-root locations, where ever the LBR is configured for the https protocol.
WLProxySSL ON WLProxySSLPassThrough ON
Add a ServerAlias entry under the internal virtual host, for example, idminternal.mycompany.com.
....ServerName http://idminternal.mycompany.com:7777ServerAlias oim.oracleoutsourcing.com authohs-host.mycompany.comRewriteEngine On....
Add a new context-root location entry for the ODSM console. The weblogic host referenced here is the host where ODSM is deployed, which is typically in OID_ORACLE_HOME.
Add this location entry for the default authohs virtual host (http).
<Location /odsm> SetHandler weblogic-handler WebLogicHost weblogic-host-odsm.mycompany.com WebLogicPort 7005 </Location>
Add this location entry for the administration virtual host (https).
<Location /odsm> SetHandler weblogic-handler WLProxySSL ON WLProxySSLPassThrough ON WebLogicHost weblogic-host-odsm.mycompany.com WebLogicPort 7005 </Location>
After you configure the search and start the crawl, enable the Oracle Fusion Applications Search User Interface by setting the value of the FUSION_APPS_SEARCH_ENABLED profile option to Yes. This setting makes the search controls visible in the user interface. The default value is No, which disables the search controls in the user interface.
To set the FUSION_APPS_SEARCH_ENABLED profile option to Yes:
Log in to Oracle Fusion Applications with a user account that is provisioned with the Manage All Application Profile Values role. Contact your security administrator for details.
From the Administration menu in the work area of Oracle Fusion Applications, choose Setup and Maintenance. In the Search: Tasks menu, enter manage administrator, then click the search icon to find the Manage Administrator Profile Values task flow. Click Go to Task to display the Managed Administrator Profile Values page.
Query the profile option 'by entering the profile option code, FUSION_APPS_SEARCH_ENABLED.
Set the value to Yes at the Site Profile Level. This profile option is defined at the site level only.
Select Save from the Action menu to save your work.
Complete the following post-rehydration steps that are related to Oracle Fusion Customer Relationship Management and Oracle Fusion Human Capital Management.
Increase the Memory Settings of the CRMDomain Administration Server
Apply Fix to Support Sales Prediction Engine (SPE) Inline Service Artifacts
For CRM templates only, follow these steps to update the memory settings on the GeneralLedgerServer_1 managed server.
On the Oracle Fusion Applications Oracle VM, go to /u01/APPLTOP/instance/domains/HOST_SECONDARY/FinancialDomain/bin.
Modify the file fusionapps_start_params.properties as follows:
Replace the line:
fusion.FinancialDomain.GeneralLedgerCluster.default.minmaxmemory.main=-Xms50m -Xmx500m
With:
fusion.FinancialDomain.GeneralLedgerCluster.default.minmaxmemory.main=-Xms50m -Xmx750m
Replace the line:
fusion.FinancialDomain.GeneralLedgerCluster.default.minmaxmemory.nonmain=-Xms50m -Xmx500m
With:
fusion.FinancialDomain.GeneralLedgerCluster.default.minmaxmemory.nonmain=-Xms50m -Xmx750m
In the FinancialDomain administration console on the Oracle Fusion Applications Oracle VM, port 7401, restart the GeneralLedgerServer_1 managed server.
For CRM templates only, follow these steps to update the memory setting on the CRMDomain Administration Server.
On the Oracle Fusion Applications Oracle VM, go to /u01/APPLTOP/instance/domains/HOST_SECONDARY/admin-apps.oracleoutsourcing.com/CRMDomain/bin.
Modify the file fusionapps_start_params.properties as follows:
Replace the line:
fusion.CRMDomain.AdminServer.default.minmaxmemory.main=-Xms50m -Xmx1024m
With:
fusion.CRMDomain.AdminServer.default.minmaxmemory.main=-Xms50m -Xmx1536m
Replace the line:
fusion.CRMDomain.AdminServer.default.minmaxmemory.nonmain=-Xms50m -Xmx1024m
With:
fusion.CRMDomain.AdminServer.default.minmaxmemory.nonmain=-Xms50m -Xmx1536m
Restart the CRMDomain Administration Server using Node Manager for these settings to take effect.
For CRM templates only, perform the following steps to update the Oracle Secure Enterprise Search (Oracle SES) configuration.
On the Oracle Fusion Applications Oracle VM, log in to the secondary server. Run the following command:
/u01/APPLTOP/fusionapps/ses/bin/searchadmin -c
http://HOST_SECONDARY:7016/search/api/admin/AdminService
export queryConfig -o /u01/APPLTOP/fusionapps/ses/bin/qConfig.xml -p welcome1
Edit the entry for preserveStaleSecurityFilterOnError in qConfig.xml to be false.
Run the following command to update Oracle SES from the altered file:
/u01/APPLTOP/fusionapps/ses/bin/searchadmin -c http://secondary.oracleoutsourcing.com:7016/search/api/admin/AdminService update queryConfig -i /u01/APPLTOP/fusionapps/ses/bin/qConfig.xml -p welcome1
Stop and start the Oracle SES server in the Common Domain or wait for Oracle SES to include the change during its next cycle.
For CRM templates only, perform the following steps to configure Informatica.
Log in to the CRM_Admin_Server_HOST. Start a VNC session with the command vncserver. An existing VNC session can be used.
Update the Informatica Key file, which needs to updated every year.
Stop the Informatica Identity Resolution (IIR) server.
Edit the file called key in /u01/APPLTOP/InformaticaIR/ssaas/ad5/ad/db. Replace the existing key with the new key provided by Oracle. For 2012, the key value is QARXW7UEAEUK9DRTC79U6HXL1PM8927JP0LA.
Start the IIR server.
Note that the 2012 Key is a limited distribution Key and works only for California addresses. You must request a new Key from the software vendor for production. The Key is valid for one year and you must obtain a new key every year.
Check the database connection using the following commands.
cd /u01/APPLTOP/InformaticaIR/bin
./setfusionEnv.sh
tnsping ORCL (Database connection information can be found in /u01/APPLTOP/InformaticaIR/ids/ssadb.dic)
Start the IIR servers after you confirm the database connection.
/liup
/idsup
Confirm there are eight Informatica processes running plus one for the grep command.
ps -ef | grep Informatica | wc
Initiate indexing.
./idsconc -a
On the launched console, select the Rulebase Type=SSA and Alias=rtunitrb.
Click OK and then click YES to create a new rulebase.
Go to System -> New -> Create a system from SDF and enter the following system information:
System Name: FusionDQRealtime
System Definition File: /u01/APPLTOP/InformaticaIR/ids/FusionDQRealtime.sdf
DB Type: SSA
Alias: fusion_s01
Click OK. When the process is complete, click Close.
Click Select to select FusionDQRealtime, and click OK.
Click Load IDT to start loading the following IDT tables one at a time.
load_location
load_organization
load_org_address
load_person
load_per_address
load_per_phone
Use the IIR web-based search client to sanity test the IIR matching server. The SSA_HTPORT port can be found in /u01/APPLTOP/InformaticaIR/env/isss.
Go to the CRM_Admin_Server_HOST/systems in a browser.
Select FusionDQRealtime from the dropdown list, then dup for the Org, then enter Toyota for the Organization Name and click Search. If the search is successful, then the steps performed so far were successful.
Start the Update Synchronizer.
In the IIR Console, go to the Tools menu, then Synchronizer, and Run Synchronizer. Click OK.
Accept all default values in the Update Synchronizer screen and make sure that the IDT Name=all option is selected. Click OK.
Connect Oracle Fusion Applications to the Data Quality Engine.
Open a browser and login to Oracle Fusion Setup Manager as the faadmin user.
Search for and select the task Manage Server Configuration.
Click Search and confirm that four servers are listed.
For the following servers, update the ServerAddress to Administration_Server, which is the host name of the Administration Server. Update the Server Port to 1666. Note that SSA_SEPORT can be found in /u01/APPLTOP/InformaticaIR/env/isss. Also select the Enable checkbox for the following servers:
Realtime and Batch Basic Server
Realtime Cleanse Server
Batch Cleanse Server
Start the Oracle Fusion Synchronization.
Open a browser and login to Oracle Fusion Setup Manager as the faadmin user.
Search for and select the task Manage Data Synchronization.
Click Actions, then Refresh Identity Table Information. Six tables are listed.
Check Enable for Sync for each Identity Table check box, and click Save.
Click Schedule Synchronization Process to start the synchronization process.
In the Schedule Synchronization Process window, click Advanced button.
Check Using a schedule, set the Frequency to Hourly/Minute using 0 hours and 5 minutes, and set the End Date to be a few days from the current date.
Enable Address Cleansing for a country.
Open a browser and login to Oracle Fusion Setup Manager as the faadmin user.
Search for and select the task Manage Geographies.
Search for the country by name or by country code.
Click Go to task in the Address Cleansing Defined column.
In the popup window, set Real-Time Address Cleansing Level to Optional, then click Save and Close.
For CRM templates only, perform the following steps to disable BI caching.
Go to Oracle Enterprise Manager for the BIDomain.
Expand Farm_BIDomain > WebLogic Domain > BIDomain.
Right click and select System MBean Browser.
Go to Application Defined MBeans > oracle.biee.admin > Domain: BIDomain > BIDomain > BIDomain.
Click the Operations tab, then Lock, then Invoke.
Go to Application Defined MBeans > oracle.biee.admin > BIDomain.BIInstance.PerformanceConfiguration > BIDomain.BIInstance.PerformanceConfiguration.
Change BIServerCacheEnabled to false and click Apply.
Go to Application Defined MBeans > oracle.biee.admin > Domain: BIDomain > BIDomain > BIDomain.
Click the Operations tab, then Commit, then Invoke.
For CRM templates only, perform the following steps to load the roles required by the CRM topology.
Download and open the zip file attached to article 1420426.1 from My Oracle Support (http://support.oracle.com).
Follow the instructions in the patch README file to load both of the LDIF files in the zip file.
Log in to the ATK Homepage as Fusion/Welcome1
Go to Navigator -> Scheduled Processes
Click Scheduled New Process
In the Search New Process window, open the Process Name drop down, and click Search.
In the Search and Select: Process Name window, search for SyncRolesJob, select it, and click OK.
Click OK in the Search New Process window.
Click Submit in the Process Details window.
Take note of the submitted process id, then click Close in the Process Details window.
Monitor the process until completion. If you see errors when running the script, use the command DOS2Unix to fix characters in the LDIF and script files.
For CRM templates only, perform the following steps to prevent errors during usage of SPE artifacts.
Log in to the console for the BI Domain. Lock and edit if necessary.
Go to Service > Data Sources.
Click Fusion_BIDS, then click Connection Pool.
In the URL, remove the extra '/' from around Global Currency 4 so that it ends like this:
NQ_SESSION.PREFERRED_CURRENCY=Global Currency 4;
Repeat steps 3 and 4 in the Connection Pool setting for the BIAnalytics data source.
Activate Changes, if necessary.
Release Configuration
Stop and restart bi_server1.
This section is for CRM templates only. If you want to configure Oracle Fusion Customer Relationship Management with a common email feature, this section provides an example of how to do that.
Start the local sendmail process.
cd /etc/mail/ cp /fsnadmin/saas/crm/b18/mt/sendmail.mc .
Perform the following steps as root.
vi /etc/mail/sendmail.mc
Search for SMART and replace this line:
define(`SMART_HOST',`internal-mail-router.oracle.com')dnl
With this:
define(`SMART_HOST', `auohs-smtp.oracle.com')dnl
Enable sendmail on startup by running the following commands as root.
chmod 777 /var/spool/clientmqueue/ cd /etc/mail make /sbin/service sendmail stop /sbin/service sendmail start /sbin/service sendmail status /sbin/chkconfig sendmail --add /sbin/chkconfig sendmail on /sbin/chkconfig --list sendmail chkconfig --list sendmail sendmail 0:off 1:off 2:on 3:on 4:on 5:on 6:off
Update the SMART_HOST definition in the file sendmail.mc.
cd /etc/mail cp /fsnadmin/saas/crm/b18/sendmail.mc . vi /etc/mail/sendmail.mc
Replace this line:
define(`SMART_HOST',`internal-mail-router.oracle.com')dnl
With this:
define(`SMART_HOST', `adcemodmx.atoracle.com')dnl
Update DAEMON_OPTIONS in the file sendmail.mc.
Replace this line:
DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
With this:
DAEMON_OPTIONS(`Port=submission,Addr=127.0.0.1, Name=MSA, M=E')dnl
As root, edit the submit.mc file.
Replace this line:
FEATURE(`msp', `[127.0.0.1]')dnl
With this:
FEATURE(`msp', `[127.0.0.1]', `MSA')dnl
As root, run the following commands to start or restart the sendmail process.
chmod 777 /var/spool/clientmqueue/ cd /etc/mail make /sbin/service sendmail stop /sbin/service sendmail start /sbin/service sendmail status
Enable sendmail on startup by executing these commands as root.
/sbin/chkconfig sendmail --add /sbin/chkconfig sendmail on /sbin/chkconfig --list sendmail
Update the bhd-onpremise-ctl.sh file.
vi /u01/APPLTOP/fusionbhd/fusionapps/crm/ewm/bhd/bin/bhd-onpremise-ctl.sh
Search for JAVA_HOME and replace this line:
#JAVA=${JAVA_HOME}/bin/java
With this:
JAVA=/u01/APPLTOP/webtier_mwhome/oracle_common/jdk/bin/java
Stop and start BHD as root.
/u01/APPLTOP/fusionbhd/fusionapps/crm/ewm/bhd/bin/bhd-onpremise-ctl.sh stop /u01/APPLTOP/fusionbhd/fusionapps/crm/ewm/bhd/bin/bhd-onpremise-ctl.sh start
As root, edit rc.local so that BHD is started during Oracle VM startup.
vi /etc/rc.d/rc.local
Add these lines to the end of the file.
#Start BHD /u01/APPLTOP/fusionbhd/fusionapps/crm/ewm/bhd/bin/bhd-onpremise-ctl.sh stop /u01/APPLTOP/fusionbhd/fusionapps/crm/ewm/bhd/bin/bhd-onpremise-ctl.sh start
Log in to the CRMDomain Enterprise Manager Console, then select Update Mail Server Properties.
Go to usermessagingdriver-email(soa_server1) -> Email Driver Properties.
Update the following properties:
OutgoingMailServer: auohs-smtp.oracle.com OutgoingMailServerPort: 25 OutgoingDefaultFromAddr: FusionCRMCloudService@AtOracle.com
For CRM templates only, perform the following steps to set up Marketing email.
Verify that the /etc/hosts smtp.oracleoutsouring.com value in the hosts file is equivalent to adcemodmx.atoracle.com. Update this value if it is incorrect.
Log in as faadmin to https://fs-aufsn4x0pod.oracleoutsourcing.com/setup/faces/TaskListManagerTop.
Go to the Manage Marketing Supplier Details and Distribution task.
Click Oracle Fusion Email in the top grid.
Click E-Mail Profile in the bottom grid.
Update the following values for CTD and BHD and save your updates:
CTD Host: crm-aufsn4x0POD.oracleoutsourcing.com CTD port: 443 CTD protocol: https BHD: aufsn4x0POD.atoracle.com
Stop and start EmailMarketingServer_1 in the CRMDomain.
For CRM templates only, perform the following steps to set up IBR.
Log in to the secondary server.
Edit the following file, provider.hda, to change the IntradocServerHostName to the IP address of the secondary server. This only works with an IP address, therefore, do not use host name alias.
/u01/APPLTOP/instance/domains/HOST_SECONDARY/CommonDomain/ucm/cs/data/providers/ibrprovider/provider.hda
An example follows:
IntradocServerHostName=10.240.38.99
Edit the following file to change the fontdirectory to a value that exists, for example:
fontdirectory=/u01/APPLTOP/fusionapps/jdk6/jre/lib/fonts
For Oracle Fusion Human Capital Management Coexistence customers only, perform the following steps to set up Oracle Fusion Human Capital Management Coexistence.
Update roles for FUSION_ODI_STAGE. Connect to the Oracle Fusion Applications database and run the following script.
GRANT SELECT ON FUSION.PER_ROLES_DN TO FUSION_ODI_STAGE; CREATE OR REPLACE SYNONYM FUSION_ODI_STAGE.PER_ROLES_DN FOR FUSION.PER_ROLES_DN;
Set up FTP accounts.
Create two user accounts with read and write access, a generic user account to configure the FTP adapter and a user specific account for Oracle Fusion Applications. For example, create user accounts with the directory structure and permissions as shown in the table Table 3-2. Permissions should be read and write for the current directory and child levels only.
Table 3-2 Directory Structure
| User/Usage | Operating System User Name | Password | User Home Directory | Comments |
|---|---|---|---|---|
|
BPEL/SOA |
<bpel_username> |
<bpel_password> |
/fusion |
User account used with Oracle Fusion SOA FTP Adapter configuration. |
|
Customer 1 |
<customer1_username> |
<customer1-pswd> |
/fusion/E_<ENTERPRISE_ID> |
The <ENTERPRISE_ID> corresponds to the Oracle Fusion Applications ID of Customer 1. The user account is used by the PeopleSoft Enterprise application interaction with the Oracle Fusion SOA/BPEL process. |
Set up the SOA FTP adapter.
Set up the following parameters of the SOA FTP adapter.
Set the FTP server host name in the FTP adapter connections properties file weblogic-ra.xml.
Set the FTP server operating system user name and password.
Set the FTP server host name and set the FTP server operating system user name and password in the FTP adapter connections property file as follows.
Access FtpAdapter.rar available in the Oracle_SOA1 directory structure on the Oracle Weblogic Server (WLS) HcmDomain server file system.
Extract and save the META-INF/weblogic-ra.xml file to a temporary location.
Update the META-INF/weblogic-ra.xml file with appropriate values for the following connection properties.
<wls:jndi-name>eis/Ftp/FtpAdapter</wls:jndi-name>
<wls:name>host</wls:name>
<wls:value>ftpServerHostName</wls:value>
<wls:name>username</wls:name>
<wls:value>ftpUserName</wls:value>
<wls:name>password</wls:name>
<wls:value>ftpUserPswd</wls:value>
<wls:property>
<wls:name>useSftp</wls:name>
<wls:value>false</wls:value>
</wls:property>
Create an additional copy of FtpAdapter.rar.
Update FtpAdapter.rar with the updated META-INF/weblogic-ra.xml file by running the following command.
zip -ur /<path>/Oracle_SOA1/soa/connectors/FtpAdapter.rar META-INF/weblogic-ra.xml
Bounce the WLS HcmDomain.
Set Up Oracle Data Integrator
Download the hcmPythonUtil.jar from this location: http://hcmwiki.us.oracle.com:8880/download/attachments/54561116/hcmPythonUtil.jar?version=1&modificationDate=1328308334000.
Log in to the HcmDomain App Server host.
Create a temporary directory.
mkdir -p $HOME/tmp/hcmOdiConfigDir
FTP the hcmPythonUtil.jar file to the $HOME/tmp/hcmOdiConfigDir.
Unzip hcmPythonUtil.jar.
Update the following settings in $HOME/tmp/hcmOdiConfigDir/hcmConfig.prop.
Modify the updateMode to be false to review the current configuration.
Update ODI Master Repository details, for example: odiMasterJDBCURL=jdbc:oracle:thin:@fusiondb.oracleoutsourcing.com:1616:DPFGR010
Update ODI Supervisor User credentials, for example:
odiWorkUser=FUSION_APPS_HCM_ODI_SUPERVISOR_APPID odiWorkUserPassWord=kza4Qb1grf#etu
Update ODI Work repository details, for example:
odiWorkReposJDBCURL=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=fusiondb.oracleoutsourcing.com)(PORT=1616))(ADDRESS=(PROTOCOL=TCP)(HOST=fusiondb2.oracleoutsourcing.com)(PORT=1616))(LOAD_BALANCE=YES)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=DPFGR010)))
Update ODI Configure Database Connections, for example:
oraFusionSchemaUser=FUSIONoraFusionSchemaUserPswd=welcome1 oraFusionOdiSchemaUser=FUSION_ODI oraFusionOdiSchemaUserPswd=welcome1 oraFusionOdiStageSchemaUser=FUSION_ODI_STAGE oraFusionOdiStageSchemaUserPswd=welcome1
Update the ODI DB link value, for example:
oraOdiInstanceDbLinkFieldValue=fusiondb.oracleoutsourcing.com:1616/DPFGR010
Update ODI JDBC URL value, for example:
oraJdbcThinDriverUrl=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL= TCP)(HOST=fusiondb.oracleoutsourcing.com)(PORT=1616))(ADDRESS=(PROTOCOL =TCP)(HOST=fusiondb2.oracleoutsourcing.com)(PORT=1616))(LOAD_ BALANCE=YES)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=DPFGR010)))
Update ODI File Connections, for example:
#FILE_ROOT_HCM fileRootHcmSchemaLoc=/u01/oracle/ODI_FILE_ROOT_HCM fileRootHcmWSSchemaLoc=/u01/oracle/ODI_FILE_ROOT_HCM #FILE_OUTPUT_HCM fileOutHcmSchemaLoc=/u01/oracle/ODI_FILE_ROOT_HCM/export fileOutHcmWSSchemaLoc=/u01/oracle/ODI_FILE_ROOT_HCM/export
Update and review the following tags in jps-config.xml:
cd $HOME/tmp/hcmOdiConfigDir/config vi $HOME/tmp/hcmOdiConfigDir/config/jps-config.xml <!-- JPS OID LDAP Identity Store Service Instance --> <serviceInstance name="idstore.oid" provider="idstore.ldap.provider"> <property name="subscriber.name" value="dc=us,dc=oracle,dc=com" /> <property name="idstore.type" value="OID" /> <property name="cleartext.ldap.credentials" value="cn=orcladmin:fusionapps1"/> <property name="ldap.url" value="ldap://vmfsnpfgr001.oracleoutsourcing.com:3060" /> <extendedProperty> <name>user.search.bases</name> <values> <value>cn=Users,dc=us,dc=oracle,dc=com</value> </values> </extendedProperty> <extendedProperty> <name>group.search.bases</name> <values> <value>cn=Groups,dc=us,dc=oracle,dc=com</value> </values> </extendedProperty> <property name="username.attr" value="uid" /> <property name="groupname.attr" value="cn" /> </serviceInstance>
Review and update the setDomainEnv.sh location in hcmAdmin.sh, for example:
# Modify the path of the HcmDomain setDomainEnv.sh if needed to match the env. #--------------------------------------------------------------------- /u01/APPLTOP/instance/domains/admin-apps.oracleoutsourcing.com/HCMDomain/bin/setDomainEnv.sh sh $HOME/tmp/hcmOdiConfigDir/hcmAdmin.sh
Capture the output in viewodiconfig.log.
cd $HOME/tmp/hcmOdiConfigDir/ vi $HOME/tmp/hcmOdiConfigDir/hcmConfig.prop
Modify the updateMode to be true, to update the ODI configuration.
Run the shell script, sh $HOME/tmp/hcmOdiConfigDir/hcmAdmin.sh and capture the output in the postUpdateViewOdiConfig.log.
Enable SQL*Loader for Oracle Data Integrator.
Oracle Fusion HCM Coexistence Oracle Data Integrator uses SQL*Loader to import file data. Use the SQL*Loader in Oracle Data Integrator from the Oracle Weblogic Server environment, to perform the following steps.
Determine the directory where the Oracle client software is installed for your deployment. The default name would be DBCLIENT and it will be placed in the parent directory of MW_HOME. You can refer to this directory as DBCLIENT ORACLE_HOME.
Verify the existence of DBCLIENT ORACLE_HOME/bin/sqlldr.
Using the cd command, change the directory to ODI_ORACLE_HOME/bin.
Use a text editor to create a script with the file name sqlldr containing the following text:.
#!/bin/sh ORACLE_HOME=<DBCLIENT ORACLE_HOME> export ORACLE_HOME $ORACLE_HOME/bin/sqlldr $* #
Make the script executable by using the following command.
chmod +x sqlldr
Compile the following information required by the Oracle Fusion HCM Application Administrator for configuring the HR2HR functionality:
Sftp details including user name, password, host name, port and credentials
ODI Context: DEVELOPMENT (default value)
ODI Root Directory
ODI User: FUSION_APPS_HCM_ODI_SUPERVISOR_APPID (default value)
ODI Password
ODI Work Repository: FUSIONAPPS_WREP (default value)
Enable proxies by performing the following steps.
Append the following entries to fusion.default.default.sysprops in DOMAIN_HOME/bin/fusionapps_start_params.properties for primary and secondary hosts. The values for proxyHost, proxyPort and nonProxyHosts need to change for each implementation. The values here are examples used at Oracle.
-Dhttp.proxyHost=www-proxy.oracleoutsourcing.com -Dhttp.proxyPort=80 -Dhttp.proxySet=true -Dhttp.nonProxyHosts=*.oracleoutsourcing.com
Stop and start the entire domain.
Add the appropriate proxy entries in /etc/hosts, as shown in the following example.
133.10.55.130 www-proxy.oracleoutsourcing.com 133.10.55.130 www-proxy.us.oracle.com
Apply the mandatory Oracle Fusion Middleware patches. For more information, see "Oracle Fusion Middleware" in Oracle Fusion Applications release notes.
Apply the following mandatory patches:
13618503 - BACKPORT REFERENCE GRANTS FOR SETIDS
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
get some more background on these use cases (telling customers when they will need to run a particular task).
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.
In order to configure CRM IIR:
Update the Informatica Key File:
Login to the administration sever slc00yqw.us.oracle.com.
If a VNC session is not currently running, begin a VNC session by executing the command vncserver. If a VNC session is currently running, it can be used.
Update the Informatica Key file. It can be found at nfs://adc1006nap.us.oracle.com/vol/fade_adc_txn/cvijayan/current_changes/infa_asm_keys/2012/key. This file must be updated yearly. The 2012 key file md5 value is 2044381d06a9d46d5c4d360cf4b90a60.
Connect to the administrator server slc00yqw.us.oracle.com with FTP and login.
Backup the old key file to key.original in /u01/APPLTOP/InformaticaIR/ssaas/ad5/ad/db.
Update the key file with the new one.
Ensure functional database connection with tnsping ORCL:
Navigate to the proper folder by running the command cd /u01/APPLTOP/InformaticaIR/bin/setfusionEnv.sh.
Execute the command tnsping ORCL. (Database connection information can be found in /u01/APPLTOP/InformaticaIR/ids/ssadb.dic.)
If the database connection is working, start the IIR Servers by executing the following commands:
./liup
./idsup
ps -ef | grep Informatica | wc
Perform the initial indexing:
Execute ./idsconc -a.
On the launched console, select the Rulebase Type=SSA and Alias=rtunitrb.
Click OK
Click YES to create a new rulebase.
Navigate to System/New/Create a system from SDF.
Enter the following system information and then click OK:
System Name: FusionDQRealtime
System Definition File: /u01/APPLTOP/InformaticaIR/ids/FusionDQRealtime.sdf
DB Type: SSA
Alias: fusion_s01
When the process completes, click Close.
Click Select to select FusionDQRealtime, and then click OK.
Click Load IDT to start loading the individual IDT tables until the following IDTs are completed:
load_location
load_organization
load_org_address
load_person
load_per_address
load_per_phone
Start Update Synchronizer:
In IIR Console, open the Tools menu, select Synchronizer, click Run Synchronizer, and then click OK.
On the Update Synchronizer popup screen, Ensure that the option IDT Name=(all)is selected and then click OK.
Connect Oracle Fusion Applications to the Data Quality Engine
Open a web browser and login to FSM as faadmin user.
Search for the task "Manage Server Configuration. Four servers should be listed.
For the servers Realtime and Batch Basic Server, Realtime Cleanse Server, and Batch Cleanse Server, update the value ServerAddress to slc00yqw.us.oracle.com and update the server port to 1666.
Select the Enable checkbox
Start the Oracle Fusion Synchronization
Open a web browser and login to FSM as faadmin user.
Search for the task Manage Data Synchronization and navigate to that page.
Click on Actions and then Refresh Identity Table Information. Six tables will be listed.
Ensure that the Enable for Sync checkbox is selected for each Identity Table.
Click on Save.
Click on the Schedule Synchronization Process button to begin the synchronization process.
On the Schedule Synchronization Process screen, click on the Advanced button.
Select the Using a schedule radio button and set the frequency to Hourly/Minute and 0 hours, 5 minutes. Set the End Date to a few days from the current date.
Enable Address Cleansing for a Country
Open a web browser and login to FSM as faadmin user.
Search for the task Manage Geographies and navigate to that page.
Search for the country by name or by code.
Click on the Go to task button in the Address Cleansing Defined column.
In the popup window, set the value Real-Time Address Cleansing Level to Optional.
Click on Save and Close.
In order to set up Oracle Data Integrator for HCM Coexistence, complete the following steps:
Manually apply DDL for 12701405
GRANT SELECT ON FUSION.PER_ROLES_DN TO FUSION_ODI_STAGE;
CREATE OR REPLACE SYNONYM FUSION_ODI_STAGE.PER_ROLES_DN FOR FUSION.PER_ROLES_DN;
Set up SOA FTP Adapter
Follow the steps listed in https://stbeehive.oracle.com/jsso/SSOLogin?appurl=https%3A%2F%2Fstbeehive.oracle.com%2Fteamcollab%2Fwiki%2FPDIT%2BOracle%2BPublic%2BCloud%2B%2528OPC%2529%3APDIT%2BOPC%2BDocs%2B-%2BMulti-Tenant%2BSFTP%2BOperational%2BDocument&appid=%2Fteamcollab#stbeehive.oracle.com#443
Download the hcmPythonUtil.jar:
Login to HcmDomain App Server host.
Create a temp directory by executing mkdir -p $HOME/tmp/hcmodiConfigDir.
FTP the hcmPythonUtil.jar file from its location at http://hcmwiki.us.oracle.com:8880/download/attachments/54561116/hcmPythonUtil.jar?version=1&modificationDate=1328308334000 to the $HOME/tmp/hcmOdiConfigDir directory.
Unzip the file hcmPythonUtil.jar by executing the command unzip $HOME/tmp/hcmOdiConfigDir/hcmPythonUtil.jar -d $HOME/tomp/hcmOdiConfigDir.
Execute the command vi $HOME/tmp/hcm0diConfigDir/hcmConfig.prop.
Modify the value updateMode to read updateMode=false
Update the ODI Master Repository details to read odiMasterJDBCURL=jdbc:oracle:thin:@fusiondb.oracleoutsourcing.com:1616:DPFGR010
Update the ODI Supervisor User credentials to read:
odiWorkUser=FUSION_APPS_HCM_ODI_SUPERVISOR_APPIDodiWorkUserPassWord=kza4Qb1grf#etuUpdate the ODI Work Repository Details to read odiWorkReposJDBCURL=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=fusiondb.oracleoutsourcing.com)(PORT=1616))(ADDRESS=(PROTOCOL=TCP)(HOST=fusiondb2.oracleoutsourcing.com)(PORT=1616))(LOAD_BALANCE=YES)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=DPFGR010))).
Update ODI Configure Database Connections to read:
oraFusionSchemaUser=FUSIONoraFusionSchemaUserPswd=welcome1oraFusionOdiSchemaUser=FUSION_ODIoraFusionOdiSchemaUserPswd=welcome1oraFusionOdiStageSchemaUser=FUSION_ODI_STAGEoraFusionOdiStageSchemaUserPswd=welcome1Update the ODI Database Link Value. Example: oraOdiInstanceDbLinkFieldValue=fusiondb.oracleoutsourcing.com:1616/DPFGR010
Update ODI JDBC URL value. Example: oraJdbcThinDriverUrl=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=fusiondb.oracleoutsourcing.com)(PORT=1616))(ADDRESS=(PROTOCOL=TCP)(HOST=fusiondb2.oracleoutsourcing.com)(PORT=1616))(LOAD_BALANCE=YES)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=DPFGR010)))
Update ODI File connections. For example:
#FILE_ROOT_HCM
fileRootHcmSchemaLoc=/u01/oracle/ODI_FILE_ROOT_HCM
fileRootHcmWSSchemaLoc=/u01/oracle/ODI_FILE_ROOT_HCM
#FILE_OUTPUT_HCM
fileOutHcmSchemaLoc=/u01/oracle/ODI_FILE_ROOT_HCM/export
fileOutHcmWSSchemaLoc=/u01/oracle/ODI_FILE_ROOT_HCM/export
Navigate tot he config directory by executing the command cd $HOME/tmp/hcmOdiConfigDir/config.
Open jps-config.xml for edit by executing the command vi $HOME/tmp/hcmOdiConfigDir/config/jps-config.xml.
Update and review the following tags in jps-config.xml.
<!-- JPS OID LDAP Identity Store Service Instance --> <serviceInstance name="idstore.oid" provider="idstore.ldap.provider"> <property name="subscriber.name" value="dc=us,dc=oracle,dc=com" /> <property name="idstore.type" value="OID" /> <property name="cleartext.ldap.credentials" value="cn=orcladmin:fusionapps1"/><property name="ldap.url" value="ldap://vmfsnpfgr001.oracleoutsourcing.com:3060" /> <extendedProperty> <name>user.search.bases</name> <values> <value>cn=Users,dc=us,dc=oracle,dc=com</value> </values> </extendedProperty> <extendedProperty> <name>group.search.bases</name> <values> <value>cn=Groups,dc=us,dc=oracle,dc=com</value> </values> </extendedProperty> <property name="username.attr" value="uid" /> <property name="groupname.attr" value="cn" /></serviceInstance>
Navigate back to the hcmOdiConfigDir directory by executing the command cd $HOME/tmp/hcmOdiConfigDir/.
Modify the path of the HcmDomain setDomainEnv.sh if needed to match the env. For Example:
. /u01/APPLTOP/instance/domains/admin-apps.oracleoutsourcing.com/HCMDomain/bin/setDomainEnv.sh
sh $HOME/tmp/hcmOdiConfigDir/hcmAdmin.sh
Capture the output in viewodiconfig.log by executing the commands
cd $HOME/tmp/hcmOdiConfigDir/
vi $HOME/tmp/hcmOdiConfigDir/hcmConfig.prop
Modify updateMode to updateMode=true
Execute the command sh $HOME/tmp/hcmOdiConfigDir/hcmAdmin.sh and capture the output in viewodiconfig.log.
Enable SQL*Loader for Oracle Data Integrator
Oracle Fusion HCM Coexistence Oracle Data Integrator uses SQL*Loader to import file data. Use the SQL*Loader in Oracle Data Integrator from the Oracle Weblogic Server environment to perform the following steps:
Determine the directory where the Oracle client software is installed for your deployment. The default name would be DBCLIENT and it will be placed in the parent directory of <MW_HOME>. You could refer to this directory as DBCLIENT ORACLE_HOME
Verify the existence of DBCLIENT ORACLE_HOME/bin/sqlldr.
Using the cd command, change the directory to <ODI ORACLE_HOME>/bin.
Use a text editor to create a script with the file name sqlldrcontaining the following:
#!/bin/sh
ORACLE_HOME=<DBCLIENT ORACLE_HOME>
export ORACLE_HOME
$ORACLE_HOME/bin/sqlldr $*
#
Make the script executable by using the following command:
chmod +x sqlldr
Update environment information in POD's excel sheet
Provide the following information in the POD's excel sheet:
Sftp details including hostname, port, and credentials
FUSION_APPS_HCM_ODI_SUPERVISOR_APPID password
Add proxy information so calls to elocation.oracle.com do not timeout
Apply proxy changes to ensure the calls to the elocation server do not timeout, as each location/person creation takes five minutes per row if the outsourcing proxy is not set. To apply the proxy changes:
Navigate to the folder $DOMAIN_HOME/bin/fusionapps_start_params.properties.
Alter the fusion.default.default.sysprops entries for primary and secondary by appending them with:
-Dhttp.proxyHost=www-proxy.oracleoutsourcing.com -Dhttp.proxyPort=80-Dhttp.proxySet=true -Dhttp.nonProxyHosts=*.oracleoutsourcing.comPing www-proxy.oracleoutsourcing.com to ensure it is reachable prior to bounce.
Update FusionVirtualHost_hcm.conf on App OHS environment
On the apps ohs update FusionVirtualHost_hcm.conf with the following entry in the "External Virtual Host" section:
<Location /soa-infra >SetHandler weblogic-handlerWebLogicCluster HOST_SECONDARY:9420SetHandler weblogic-handlerWLProxySSL ONWLProxySSLPassThrough ONRewriteEngine OnRewriteOptions inherit</Location>
The following troubleshooting scenarios are included in this section.
Resolve Error About essbase Server When Starting BI Components
Stop and Restart CRMPerformance Server Every Time BI Server Starts
If you scaled out your servers after Oracle VM deployment, you may encounter an error when starting BI components.To resolve this error, edit the /u01/APPLTOP/instance/BIInstance/config/OPMN/opmn/opmn.xml file. In the opmn.xml file, check if the path value of <variable id="ARBORPATH" > exists. If the path does not exist, update it to a path that does exist. Then stop and start all BI components to allow the Essbase server to start up successfully.
You must stop and start the CRMPerformance server every time you start the BI Server. The following example provide the correct order of steps for starting the BI server.
Start the BI Server.
Log in to the HOST_BI/console as the applications system user, as specified by the faovm.os.apps.user.name property.
Click Servers.
Go to the Control tab
Select bi_server1 and click Start.
Stop and start the CRMPerformance Server.
Log in to HOST_CRM /console as the applications system user, as specified by the faovm.os.apps.user.name property.
Click Servers.
Go to the Control tab
Select CRMPerformanceServer_1 and click Shutdown, then Force Shutdown Now.
When the server is shut down, select CRMPerformanceServer_1 and click Start.
|
 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|