AIM

MD.120 Installation
Instructions
Fusion Connect-HDL Automation
Solution

Author:
Creation Date: December 06, 2016
Last Updated: December 06, 2016
File Name:
Version: Draft

Approvals:

Process Owner

Project Manager

Oracle Project Manager

MD.120 Installation Instructions Doc Ref:Error: Reference source not
found
06 Dec2016

Document Control

Change Record
1

Date Author Version Change Reference

19-Dec-166 Draft No Previous Version

Reviewers

Name Position

Distribution

Copy No. Name Location

1

2
3
4

Note to Holders:
If you receive an electronic copy of this document and print it out, please write your
name on the equivalent of the cover page, for document control purposes.
If you receive a hard copy of this document, please write your name on the front
cover, for document control purposes.

Page 2 of 17
MD.120 Installation Instructions Doc Ref:Error: Reference source not
found
06 Dec2016

Contents

Document Control....................................................................................................................3
Installation Instructions for Fusion Connect – HDL Automation....................................4
Fusion HCM Component Installation...................................................................................5
Pre-Requisite Steps...........................................................................................................5
Pre-Installation Steps........................................................................................................7
Testing from Local Machine............................................................................................9
Installation Steps on UNIX DB Server...........................................................................9
Post Installation Steps.....................................................................................................14
Verification Checklist.....................................................................................................15
Security Concerns:..................................................................................................................16
Open and Closed Issues for this Deliverable.....................................................................17
Open Issues......................................................................................................................17
Closed Issues....................................................................................................................17

Page 3 of 17
Installation Instructions Doc Ref:
06 Dec2016

Installation Instructions for Fusion Connect – HDL Automation

Installation Summary:

This Installation document provides the steps that need to follow in eBs UAT to automate file transfer and
load initiation at fusion application side.
Environment Summary:

Application Name Type

Oracle eBs suite R12 UAT

Fusion Applications Rel11 Test Environment

Page 4 of 17
Installation Instructions Doc Ref:
06 Dec2016

Fusion HCM Component Installation

Pre-Requisite Steps

Sequence Step Details

Number Name

User should have Application Developer User role

1 User Role
User Should have access to UNIX DB Server
Note: Concurrent program for OCBC is deployed at DB Server.

2 Network Port 443 needs to be open and firewall setting should be enabled to
allow the request to fusion application from eBs server.

Page 5 of 17
Installation Instructions Doc Ref:
06 Dec2016

3 Java Run Time Standard instruction :

environment
Oracle Java 6 SE release 1.6.0_20 is the earliest version of the Oracle (/
Sun Microsystems) Java Runtime Environment that tested successfully
with the transfer tools. Oracle strongly recommends that the customer
leverage the latest Java 6 or 7 Oracle Java SE release update available so
as to ensure important bug and security fixes are applied. Obtain the
JVM name** and Java version by providing the "-version" option to the
java executable.

 Oracle Java SE versions prior to 1.6.0_18 have a cookie

handling issue present in the embedded JDK HTTP client
(java.net.HttpURLConnection) that results in the RIDCbase
transfer tool being unable to authenticate due to cookies not
being transmitted in outbound requests.
 Oracle Java SE versions prior to 1.6.0_20 are likely to see
SSLHandshakeException -'unable to find valid certification
path to requested target' when accessing Oracle cloudservers.
This is due to the default trust keystore (cacerts) certificate
contents in these older Java builds not being modern enough to
verify the server's SSL certificate.
 >>> ** OpenJDK 1.6 is not supported. All versions currently
tested of the open-source OpenJDK 1.6 (1.6.0_22 / 1.6.0_24 /
1.6.0_30) appear to exhibit the cookie handling issue present in
Oracle Java SE 1.6.0_18 and prior.
 OpenJDK 1.7 version 1.7.0_09 tested successfully with the
RIDC-based transfer utility.
Java can be downloaded from
http://www.oracle.com/technetwork/java/javase/downloads/java-
archive-downloads-javase6-419409.html

For OCBC:
As OCBC had JRE 1.5 and 1.6 deployed on their server. OCBC DBA
downloaded the JRE 1.8 and without installing, we changed the path
references to this version which can be further seen in Installation steps
section.

Page 6 of 17
Installation Instructions Doc Ref:
06 Dec2016

Pre-Installation Steps

Sequence Step Details

Number Name

1 Library Copy the OCBC HDL Automation.zip to the server from the
Files/Executable desktop
Jar

2 Host script The Host Script needs to copied to the server

XXHCM_FUSION_UC
M_UPLOAD.sh

Page 7 of 17
Installation Instructions Doc Ref:
06 Dec2016

3 Vault Key
A vault key must be created to hold the password of the fusion
application.
Option 1 :
sqlplus <Apps>/<Apps passwd> @$FND_TOP/sql/afvltput.sql
FQA FBL_USER <Password>

Eg :
SQL> @&FND_TOP/sql/afvltput.sql HCM_COEXISTENCE
FUSION_FTP_PASSWORD <PASSWORD>

Option 2 :
declare
  sysResp     number;
  appResp     number;

  l_module varchar2(30) := 'HCM_COEXISTENCE';

  l_key    varchar2(30) := 'FUSION_FTP_PWD';
  l_value  varchar2(500) := ‘xxx’;

begin

  -- get SYSTEM_ADMINISTRATOR resp and app ids for global init ..

  begin
    select RESPONSIBILITY_ID, APPLICATION_ID
    into   sysResp, appResp
    from   FND_RESPONSIBILITY
    where  RESPONSIBILITY_KEY = 'SYSTEM_ADMINISTRATOR';
    fnd_global.apps_initialize( 0, sysResp, appResp);
  exception
    when others then
      -- fail back to seeded values
      fnd_global.apps_initialize(0,20420,1);
  end;

  fnd_vault.put(l_module, l_key, l_value);

end;
/
commit;
Page 8 of 17
Installation Instructions Doc Ref:
06 Dec2016

Testing from Local Machine

Before testing the ODTU on the server we can also test if we can make the connection from the local machine:

Testing from Local

Machine.doc

Please note :
For the SOAP-based version, the URL is the one you have successfully used until now:
https://hdeo-test.fs.ap2.oraclecloud.com/idcws/GenericSoapPort

The /idcws context is not protected by OAM security, but instead is protected by the Oracle Web Services
Manager module (OWSM), so you have to add an extra parameter, in this case:
--policy=oracle/wss_username_token_over_ssl_client_policy

Installation Steps on UNIX DB Server

Fusion Connect –HDL Automation

Sequence Step Details

Number Name

1 Validate the Java As OCBC had JRE 1.5 and 1.6.0 deployed on their server. OCBC DBA
Run Time downloaded the JRE 1.8 and without installing, we changed the path
Environment references to this version which can be further seen in below steps

2 Copy the Copy the entire folder HDL_Automation.zip to any folder in db server
Library/Executa (later, we need to update the host script with this path)
ble Jar files to
any folder on
apps server

Page 9 of 17
Installation Instructions Doc Ref:
06 Dec2016

3 Copy the Host Copy the provided XXHCM_FUSION_UCM_UPLOAD_ALL.sh file to

script /app/glhrapp_conv/PROD/prodappl/ocgl/11.5.0/bin

4 Permissions Provide all permission to the file

XXHCM_FUSION_UCM_UPLOAD_ALL.sh using chmod

Page 10 of 17
Installation Instructions Doc Ref:
06 Dec2016

5 Create the Proxy Go to Command Prompt

Classes for
Run the below command by providing the instance specific host by going
DataLoader
into java bin folder :
Service
From Internet
wsimport -s "D:\HCMDataLoader" -d "D:\ HCMDataLoader"
https://{host}/hcmCommonDataLoader/HCMDataLoader?wsdl
From Oracle Intranet
set JAVA_TOOL_OPTIONS=-Djava.vendor="Sun Microsystems Inc."
-Djava.net.useSystemProxies=true -Dhttps.proxyHost=" www-proxy.uk.oracle.com "
-Dhttps.proxyPort=80
wsimport -httpproxy:www-proxy.uk.oracle.com:80 -s "D:\HCMDataLoader" -d
"D:\HCMDataLoader" https://{host}/hcmCommonDataLoader/HCMDataLoader?wsdl

Eg :
cd %JAVA_HOME%
cd bin
wsimport -httpproxy:www-proxy.uk.oracle.com:80 -s "D:\HCMDataLoader" -d
"D:\HCMDataLoader" https:// hdeo-
test.hcm.ap2.oraclecloud.com/hcmCommonDataLoader/HCMDataLoader?wsdl

Once the above command is ran successfully, we will be able to see the
artifacts related to DataLoaderService and will be available in mentioned
path

Run the below command from the above path

zip dataLoaderProxy.jar -r * -
or jar cf dataLoaderProxy.jar com sdo

Note: Proxy class needs to be generated for each instance(Dev,Test,Prod)

of fusion separately, because artifacts will differ

Move this jar file to the generic folder in the server

Page 11 of 17
Installation Instructions Doc Ref:
06 Dec2016

6 Copy the Proxy Copy the below Java file to the folder created for OCBC HDL Automation
Client Java File and compile.
and compile
This Java file has a parameter added for encryption type PGPUNSIGNED.

DataLoaderServiceSoapHttpPortClient.java

Note: The above attached is a program which takes into account the
encryption type parameter PGPUNSIGNED. This will have to be modified
according to the requirement.

Change the password in this java file according to instance

Page 12 of 17
Installation Instructions Doc Ref:
06 Dec2016

7 Update the Host Once all the permissions are given, modify
Script with the XXHCM_FUSION_UCM_UPLOAD_ALL.sh
path where
Paths needs to updated are
Library/Executa
ble jar’s are $JAVA_TOP
available
$MW_HOME
$PATH
e.g.
JAVACMD="/usr/java8_64/jre/bin/java"
export MW_HOME=$UCM_HOME/Middleware
And Also update the path in the below command to correct path in target
instance :

Page 13 of 17
Installation Instructions Doc Ref:
06 Dec2016

8 Execute the shell Eg :

script
cd /home/fusionc/Automation/ucm/generic

sh XXHCM_FUSION_UCM_UPLOAD_ALL.sh
OCHR_FUSION_IMAGE_20161130_193529.zip
/home/fusionc/Automation/obsolete

sh XXHCM_FUSION_UCM_UPLOAD_ALL.sh
OCHR_FUSION_SABA_20161130_193529.zip
/home/fusionc/Automation/obsolete

sh XXHCM_FUSION_UCM_UPLOAD_ALL.sh
FUSION_CONFIGURATION_1_20161130_193529.zip
/home/fusionc/Automation/obsolete

Post Installation Steps

Sequence Step Details

Number Name

1 Test run Once the Installation is done, as part of testing run Publish To Fusion
Concurrent Program

2 Schedule Once the Test Run is successful. Schedule the Result Set provided as
part of installation script for every 1 day.

Page 14 of 17
Installation Instructions Doc Ref:
06 Dec2016

Verification Checklist

Sequence Step Details

Number Name

1 Fusion Open the fusion application, go to Navigator Data Exchange Load

Application Data for Coexistence
Refresh the search results or search by the process id specified in the
process log file.
You should be able to see the file imported.

Page 15 of 17
Installation Instructions Doc Ref:
06 Dec2016

Security Concerns:
The password is not send in clear text because the communication is done over SSL.
Kindly note the below points:

1. In the parameters list, we are using as policy the (--

policy=)oracle/wss_username_token_over_ssl_client_policy.

This is the best policy for communication with cloud instances, as described in the below KM note:

-Best policy to use on client side when calling a web service from Cloud environment ( Doc ID
1603340.1 ).

2. This means that the username and password are sent as a token over SSL. The confirmation is there
in this manual:

https://docs.oracle.com/cd/E16764_01/web.1111/b32511/policies.htm#CHDHJJDE

Page 16 of 17
Installation Instructions Doc Ref:
06 Dec2016

Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

Page 17 of 17