Oracle® Fusion
Applications Post-Installation Guide 11g Release 1 (11.1.3) Part Number E22380-04 |
Contents |
Previous |
Next |
This chapter contains the following:
Setting Up Oracle Fusion Human Capital Management Coexistence: Procedures
Creating an ISAM Vertex Database: Procedures
Oracle Fusion Human Capital Management (HCM) Coexistence functionality enables you to integrate your existing Oracle Human Resource applications with a hosted Oracle Fusion HCM implementation. As a result of the integration, you can use Oracle Fusion Workforce Compensation and talent management functionality alongside your existing setup.
Using Oracle Fusion HCM Coexistence, you can extract, transform, and transport files from PeopleSoft Enterprise or Oracle E-Business Suite and intelligently synchronize selected business object data between your source application and Oracle Fusion HCM applications. For more information, refer to Coexistence for HCM Offering: Overview.
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, you need to set up the connections in the source application as well. The instructions for configuring the source application are available in the following guides:
Integrating Peoplesoft HRMS 8.9 with Fusion Talent and Workforce Compensation
HCM Coexistence - Oracle EBS - Oracle Fusion Talent and Workforce Compensation
Prerequisites
Use the Oracle Fusion Applications Provisioning framework to provision a new Oracle Fusion Applications environment. For information about using the Oracle Fusion Applications Provisioning framework, see the Oracle Fusion Applications Installation Guide.
In addition to the components installed using the Oracle Fusion Applications Provisioning framework, Oracle Fusion HCM Coexistence requires the following products to be installed.
Adobe Reader
Oracle Application Development Framework Desktop Integration (ADFDi)
Microsoft Office 2007
For more details, see topic Coexistence for HCM Offering: Overview.
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 above entries are replaced correctly during deployment. Ensure that the Protocol, Host and Port tokens are assigned valid values for the application domain.
When you create the Oracle Fusion Applications Provisions framework, it creates an FTP server and installs Oracle WebCenter. Ensure that the server is configured on port 20 and 21 and start the server.
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 (Operating System User) |
Password |
User Home Directory |
Permissions |
Comments |
---|---|---|---|---|---|
BPEL/SOA |
|
|
/fusion |
Read and write for current directory and child levels only |
User account used with Oracle Fusion SOA FTP Adapter configuration. |
Customer 1 |
|
|
/fusion/E_<ENTERPRISE_ID> |
Read and write for current directory and child levels only |
The |
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 as follows.
Access FtpAdapter.rar 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.
To set up Oracle Data Integrator for 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.
Before performing the above steps, ensure that the following is set up.
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
You need to manually create 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 Value |
---|---|---|
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 |
/home/ODI_ROOT_DIRECTORY/E_<eid> |
Note
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 Web logic domain that runs the Oracle Data Integrator agent, and the SOA process.
After you have created the directories, 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
Note
Use JDBC connection and credentials to validate and ensure that the connections refer to the correct database.
Use Oracle Data Integrator Studio to verify the work directories and repository configuration.
Go to Topology - Repositories - Work Repositories.
Double-click FUSIONAPPS_WREP.
Verify that the work repository (jdbc URL) points to your Oracle Fusion database.
Verify that the JDBC data server URLs point to the Oracle Fusion Applications database.
Go to Topology - Physical Architecture - 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: ORALCE_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.
Note
Perform the same steps for the ORACLE_WORK_HCM data server. However, ensure that value of both the schema and work schema are FUSION_ODI_STAGE.
The ODI work directories you defined now need to be configured in the topology so that ODI can make use of them.
Using ODI Studio, configure files in topology.
Go to Topology - 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 that you defined for FILE_ROOT_HCM.
Provide the same value for Directory (Work Schema).
Ensure that the Default box is selected.
Use the same steps again to configure FILE_OUTPUT_HCM using the directory path for FILE_OUTPUT_HCM instead of FILE_ROOT_HCM.
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 sqlldr containing 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
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.
Sign 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.
After you have created the FTP and Oracle Data Integrator directory paths, you need to setup the related parameters in Oracle Fusion HCM.
Sign into the Oracle Fusion application.
Note
Oracle Fusion Application 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, refer to the HCM Coexistence 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. Note 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 |
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 |
You are now ready 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.
To successfully run the US Payroll, you need to create an Indexed Sequential Access Method (ISAM) database using the data file provided by Vertex. Once the ISAM database is created, you need to process the data file each month to maintain accurate payroll results. Vertex makes available the data file on a monthly basis.
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 where you want 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 where you want 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.
Take a backup of 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 file and all related files from the local directory (in this case C:\Vertex_Data), and place them 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.
To create the ISAM database for applications running on UNIX, follow these instructions.
Set the appropriate environment variable
(for the given platform) as the value of $VERTEX_TOP/lib
, as per the following specification:
UNIX System |
Environment Variable |
---|---|
AIX |
|
HP-UX 11.11 |
|
Others |
|
Take a backup of 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 where you want to create the ISAM database (in this case $VERTEX_TOP/data). The ISAM database files get created in this directory.
From $VERTEX_TOP/utils, run vprtmupd 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 to all files under $VERTEX_TOP/data.
The ISAM database is available for use by the US Payroll application.