22 Complete Oracle Fusion Human Capital Management Post-Installation Tasks

This section describes the Oracle Fusion Human Capital Management (Oracle Fusion HCM) post-installation tasks that should be reviewed and completed before starting working with an Oracle Fusion HCM implementation.

This section contains the following topics:

22.1 Set Up Oracle Fusion Human Capital Management Coexistence

Oracle Fusion HCM Coexistence functionality enables the integration of the existing Oracle Human Resource applications with a hosted Oracle Fusion HCM implementation. As a result of the integration, use Oracle Fusion Workforce Compensation and Talent Management functionality alongside the existing setup.

Using Oracle Fusion HCM Coexistence, extract, transform, and transport files from PeopleSoft Enterprise or Oracle E-Business Suite and intelligently synchronize selected business object data between the source application and Oracle Fusion HCM applications. Refer to HCM Coexistence: Explained.

Setting up an implementation of Oracle Fusion HCM for Coexistence with an existing application involves the following procedures.

Ensuring that tokens are correctly replaced during Oracle Enterprise Scheduler Service deployment.
Setting up an FTP Server.
Setting up FTP Accounts.
Setting up SOA FTP Adapter.
Setting up Oracle Data Integrator.
Configuring the Oracle Web Services Manager for Interaction with the Source Application Web Services.
Setting up the HCM Configuration for Coexistence Parameters.

These procedures set up the connections in the Oracle Fusion environment to work with the source application. Therefore, set up the connections in the source application as well. The instructions for configuring the source application are in the following documents, which are available on My Oracle Support (MOS):

Integrating PeopleSoft HRMS 8.9 with Fusion Talent Management and Fusion Workforce Compensation (Document ID 1480967.1)
Integrating PeopleSoft HRMS 9.0 with Fusion Talent Management and Fusion Workforce Compensation (Document ID 1480995.1)
Integrating PeopleSoft HRMS 9.1 with Fusion Talent Management and Fusion Workforce Compensation (Document ID 1480996.1)
HCM Coexistence - Integrating EBS HCM 11i and Fusion Talent Management and Workforce Compensation (Document ID 1460869.1)
HCM Coexistence - Integrating EBS HCM R12.1 and Fusion Talent Management and Workforce Compensation (Document ID 1460868.1)

22.1.1 Prerequisites

Use Oracle Fusion Applications Provisioning to provision a new Oracle Fusion Applications environment.

In addition to the components installed using Oracle Fusion Applications Provisioning, Oracle Fusion HCM Coexistence requires the following products to be installed.

Adobe Reader
Oracle Application Development Framework Desktop Integration (ADFDi)
Microsoft Office 2007

22.1.2 Ensure Correct Token Replacement During Oracle Enterprise Scheduler Service Deployment

Ensure that Oracle Fusion HCM invokes the following services defined in the Oracle Enterprise Scheduler Service connections.xml file for HcmEssApp:

BulkLoadOdiInvoke - ODI Agent
OdiAgentURLForHCM - ODI Agent via ODI-ESS bridge
All entries with the prefix BulkLoad* - HCM product services

Ensure that the service URLs of the entries above are replaced correctly during deployment. Ensure that the Protocol, Host and Port tokens are assigned valid values for the application domain.

22.1.3 Set Up an FTP Server

Oracle Fusion Applications Provisioning creates an FTP server and installs Oracle WebCenter. Ensure that the server is configured on port 20 and 21 and start the server.

22.1.4 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 directory structure and permissions as shown in the following table.

User/Usage	User Name (OS User)	Password	User Home Directory	Permissions	Comments
BPEL/SOA	`<bpel_username>`	`<bpel_password>`	/fusion	Read and write for current directory and child levels only	User account used with Oracle Fusion SOA FTP Adapter configuration.
Customer 1	`<customer1_username>`	`<customer1-pswd>`	/fusion/E_<ENTERPRISE_ID>	Read and write for current directory and child levels only	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.

22.1.5 Set Up SOA FTP Adapter

Set up the following parameters of the SOA FTP adapter.

Set the FTP server hostname in the FTP adapter connections properties file weblogic-ra.xml
Set the FTP server operating system user name and password

To set the FTP server hostname and set the FTP server operating system user name and password in the FTP adapter connections property file, do the following:

Access FtpAdapter.rar which is available in the Oracle_SOA1 directory structure on 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>
Create an additional copy of FtpAdapter.rar.
Update FtpAdapter.rar with the updated META-INF/weblogic-ra.xml file. Run the following command:
```
zip -ur  /<path>/Oracle_SOA1/soa/connectors/FtpAdapter.rar META-INF/weblogic-ra.xml
```
Bounce the WLS HcmDomain.

22.1.6 Set Up Oracle Data Integrator

This section describes the prerequisites and steps required for setting up Oracle Data Integrator.

22.1.6.1 Prerequisites

Before setting up Oracle Data Integrator, ensure to complete the following:

Oracle Data Integrator code is loaded using XML Import into a copy of the central template repository (id:500) using the FUSION_ODI schema.
Topology entries are coming from the central template repository.
Work repository (jdbc) is configured automatically to match the installation.
Topology Java DataBase Connectivity (JDBC) entries for the database are configured automatically to match the installation.
Installation uses the default FUSION and FUSION_ODI_STAGE schemas.
Schemas FUSION and FUSION_ODI_STAGE are installed in the same database.
The Oracle Data Integrator repository is in the same database as FUSION (schema: FUSION_ODI).
Default context Development is used.
Oracle Data Integrator console is available for configuration of the topology.

22.1.6.2 Set Up Oracle Data Integrator for Oracle Fusion Human Capital Management Coexistence

To set up Oracle Data Integrator for Oracle Fusion HCM Coexistence, complete the following procedures.

Create Oracle Data Integrator directories.
Validate Oracle Data Integrator topology settings.
Verify the configuration of the work repository.
Verify database connections.
Configure file technology connections.

22.1.7 Create Oracle Data Integrator Directories

Create manually and specify the directories and files to which Oracle Data Integrator has read and write access.

For each enterprise, create an enterprise folder in the work directory.
For the operating system user of the Oracle Data Integrator agent, create or specify directories for the items listed in the following table for Oracle Data Integrator use. The users must have full read and write access to the directories.

Oracle Data Integrator Directory Name	Item Description	Example Values
FILE_ROOT_HCM	Oracle Data Integrator base work directory	/home/ODI_ROOT_DIRECTORY
FILE_OUTPUT_HCM	Oracle Data Integrator export work directory	/home/ODI_ROOT_DIRECTORY/export
N/A	Enterprise directory name, where `<eid>` is the numeric enterprise id	/home/ODI_ROOT_DIRECTORY/E_<eid>

While creating the directory, ensure that the owner of the directory and the operating user of the Oracle Data Integrator agent are the same. The directory should be accessible from the Oracle WebLogic Server domain that runs the Oracle Data Integrator agent and the SOA process.

22.1.8 Validate the Topology Settings

After the directories have been created, use either Oracle Data Integrator Studio or Oracle Data Integrator Repository Explorer to validate the Oracle Data Integrator topology settings.

Configure or validate the following:

Work repository connection
Oracle technology (database) connections
File technology connections

Use JDBC connection and credentials to validate and ensure that the connections refer to the correct database.

22.1.9 Verify the Configuration of the Work Repository

Use Oracle Data Integrator Studio to verify the work directories and repository configuration.

Navigate to Topology, then Repositories, and then Work Repositories.
Double-click FUSIONAPPS_WREP.
Verify that the work repository (jdbc URL) points to the Oracle Fusion Applications database.

22.1.10 Verify Database Connections

Verify that the JDBC data server URLs point to the Oracle Fusion Applications database.

Navigate to Topology, then Physical Architecture, and then Oracle.
Double-click the ORACLE_FUSION data server.
On the Definitions page, verify that the Connection User is FUSION_ODI_STAGE.
Enter the password.
In the Instance/db link (Data Server) field, enter the instance for the Oracle Fusion Applications database.

Use the following format if the instance name is not registered with the Transparent Network Substrate (TNS) service: <host>:<port>/<instance_name>. If the instance name is registered with the TNS service, specify only the instance name.
Click JDBC.
Ensure that the URL in the JDBC URL field points to the Oracle Fusion Applications database.
Expand and open the child schema: ORACLE_FUSION.FUSION.
Ensure that the Default box is selected.
Verify that FUSION is entered as the value in the Schema field.
Verify that FUSION_ODI_STAGE is entered as the value in the Work Schema field.

Perform the same steps for the ORACLE_WORK_HCM data server. However, ensure that the value of both the schema and the work schema is FUSION_ODI_STAGE.

22.1.11 Configure File Technology Connections

The ODI work directories previously defined now need to be configured in the topology so that ODI can make use of them.

Using ODI Studio, configure files in topology.

Navigate to Topology, then Physical Architecture - File.
Double-click FILE_ROOT_HCM.
Verify that the value of JDBC Driver is com.sunopsis.jdbc.driver.file.FileDriver.
Verify that the value of JDBC URL is jdbc:snps:dbfile.
Expand and open the child physical schema.
For Directory (Schema), provide the directory path defined for FILE_ROOT_HCM.
Provide the same value for Directory (Work Schema).
Ensure that the Default box is selected.

Use the same steps to configure FILE_OUTPUT_HCM using the directory path for FILE_OUTPUT_HCM instead of FILE_ROOT_HCM.

22.1.12 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 the deployment. The default name is DBCLIENT and it is placed in the parent directory of MW_HOME. Refer to this directory as DBCLIENT ORACLE_HOME.
Verify the existence of DBCLIENT ORACLE_HOME/bin/sqlldr.
Change the directory to ODI ORACLE_HOME/bin.

Create a script named sqlldr that contains the following:

#!/bin/sh
ORACLE_HOME=<DBCLIENT ORACLE_HOME>
export ORACLE_HOME
$ORACLE_HOME/bin/sqlldr $*
#

Make the script executable using the following command.
```
chmod +x sqlldr
```

22.1.13 Configure the Oracle Web Services Manager for Interaction with the Source Application Web Services

Configure the Oracle Web Services Manager certificate key with the user credentials for a Simple Object Access Protocol (SOAP) interaction with the source application Web services.

The user credentials correspond to the source application user with entitlement to invoke the source application Web service.

Log in to the Enterprise Manager Console as a Weblogic_Administrator user.
Access HcmDomain under the Weblogic Domain.
Open Security - Credentials.
Access and expand the key map oracle.wsm.security.
Click Credential Key to search for the key FUSION_APPS_HCM_HR2HR_APPLOGIN-KEY.
Click Edit to update the credentials.
Set the user name and password of the source application user.

22.1.14 Set up the HCM Configuration for Coexistence Parameters

After the FTP and Oracle Data Integrator directory paths have been created, set up the related parameters in Oracle Fusion HCM.

Log in to Oracle Fusion Applications.

MANDATORY: The Oracle Fusion Applications user must have the appropriate roles to set up and configure Oracle Fusion applications. At least, ensure that the user is assigned the View All data role for the HCM Application Administrator job role. For details on setting up implementation users, see Define Implementation Users in the Oracle Fusion Applications Coexistence for HCM Implementation Guide.

Go to Navigator - Tools - Setup and Maintenance and perform the following tasks:

Find and initiate the Manage HCM Configuration for Coexistence task to bring up the Manage HCM Configuration for Coexistence parameters page.

Set up the following parameters.

Parameter	Description
On Demand FTP Root Directory	Mounted root directory of the server
ODI Context	The logical name for the group containing logical-to-physical mappings for connections in Oracle Data Integrator. The default value in Oracle Data Integrator is DEVELOPMENT. This value is case sensitive. Therefore, ensure that it is completely uppercase.
ODI User	The Oracle Data Integrator user name
ODI Password	The password associated with the Oracle Data Integrator user name
ODI Work Repository	The repository that contains the Oracle Data Integrator related code definitions. The default value in Oracle Data Integrator is `FUSIONAPPS_WREP`.
ODI Root Directory	The local directory where Oracle Data Integrator processes files and creates work and log files. It is the directory path defined for `FILE_ROOT_HCM`, when creating the Oracle Data Integrator directories.

It is possible now to implement Oracle Fusion Talent and Oracle Fusion Workforce Compensation using the Coexistence for HCM offering, available from the Setup and Maintenance work area of Oracle Fusion Applications.

22.2 Recommended Memory Requirement for Oracle Fusion Human Capital Management Workforce Reputation Management Product

This section is only applicable to use the Oracle Fusion HCM Workforce Reputation Management product packaged with the Workforce Deployment, or Workforce Development product offerings. To provision an environment with these two product offerings, see Select Product Offerings.

The physical machine hosting Oracle Fusion HCM Workforce Reputation Management (WorkforceReputationServer_1) Managed Server must have a minimum of 24 GB of memory. Allocate 8 GB of memory to the Oracle Fusion HCM Workforce Reputation Management (WorkforceReputationServer_1) Managed Server. The Oracle Fusion HCM Workforce Reputation Management externalization process may use up to 16 GB of memory.

To specify memory allocation for the Oracle Fusion HCM Workforce Reputation Management (WorkforceReputationServer_1) Managed Server:

Edit the fusionapps_start_params.properties file located under APPLICATIONS_CONFIG/domains/<host>/HCMDomain/config, by replacing the line:

fusion.HCMDomain.WorkforceReputationCluster.default.minmaxmemory.main=-Xms512m -Xmx2048

with

fusion.HCMDomain.WorkforceReputationCluster.default.minmaxmemory.main=-Xms4096m -Xmx8192m
Save the fusionapps_start_params.properties file.
Restart Oracle Fusion HCM Workforce Reputation Management (WorkforceReputationServer_1) managed server either from the WebLogic console or Enterprise Management for the Oracle Fusion HCM domain. See Perform Basic Administrative Tasks in the Oracle Fusion Applications Administrator's Guide.

22.3 Create and Update an ISAM Vertex Database

To successfully run the US or Canadian Payroll, create an Indexed Sequential Access Method (ISAM) database using the data file provided by Vertex. Once the ISAM database is created, process the data file each month to maintain accurate payroll results. Vertex makes the data file available on a monthly basis.

22.3.1 Create and Update an ISAM Database for Microsoft Windows

To create the ISAM database for Applications running on Windows, follow these instructions.

In the environment.properties file, ensure that the $VERTEX_TOP variable is set for the appropriate environment.
Copy the utility and library files under $VERTEX_TOP/utils and $VERTEX_TOP/lib and place them in a Windows local directory, such as C:\Vertex_Util-Lib.
Copy the latest Vertex data file (qfpt.dat) to the local directory used to create the ISAM database, such as C:\Vertex_Data.
From the local directory containing the utilities and library files (in this case C:\Vertex_Util-Lib), run cbmaint.
On the installer screen, select Create Database and Payroll Tax Database.
Provide the local directory path used to create the ISAM database (in this case, C:\Vertex_Data). The ISAM database files get created in this directory.
From the local directory containing the utilities and library files (in this case C:\Vertex_Util-Lib), run vprtmupd to populate the ISAM database files.
On the Installer screen, select Update Payroll Tax Database.
Provide the local directory path where the Vertex data file qfpt.dat is available (in this case C:\Vertex_Data).
Provide the directory path where ISAM database was created (in this case C:\Vertex_Data). The ISAM database files residing in this directory get updated. The update process takes some time.
Backup the database file and the related files under $VERTEX_TOP/data, if any, in case there is a need to revert to the earlier ISAM database.
Copy the ISAM database files and all related files from the local directory (in this case C:\Vertex_Data), and place then under $VERTEX_TOP/data.
Provide users with complete permissions to all files under $VERTEX_TOP/data.

The ISAM database is available for use by the US Payroll application and the Canadian Payroll application.

22.3.2 Create and Update an ISAM Database for UNIX

To create the ISAM database for application running on UNIX, follow these instructions.

Set the environment variable LD_LIBRARY_PATH as the value of $VERTEX_TOP/lib.
Backup the database file and the related files under $VERTEX_TOP/data, if any, in case there is a need to revert to the earlier ISAM database.
Copy the latest Vertex data file (qfpt.dat) to $VERTEX_TOP/data.
From $VERTEX_TOP/utils, run cbmaint.
On the installer screen, select Create Database and Payroll Tax Database.
Provide the directory path used to create the ISAM database (in this case $VERTEX_TOP/data). The ISAM database files get created in this directory.
From the $VERTEX_TOP/utils, run vptmupd to populate the ISAM database files.
On the Installer screen, select Update Payroll Tax Database.
Provide the directory path where the Vertex Data file qfpt.dat is available (in this case $VERTEX_TOP/data).
Provide the directory path where ISAM database was created (in this case $VERTEX_TOP/data). The ISAM database files residing in this directory get updated. The update process takes some time.
Provide users with complete permissions ot all files under $VERTEX_TOP/data.

The ISAM databse is available for use by the US Payroll application and the Canadian Payroll application.

22.4 Next Steps

If the Oracle Fusion Incentive Compensation product offering has been installed, go to Complete Oracle Fusion Incentive Compensation Post-Installation Tasks . Otherwise, go to the section that corresponds to the product offering that is installed.