Are
you inclined to use HCM Extracts feature, just because it has features like
output file encryption, built in SFTP integration point then think again… if
your main goal is to achieve pure outbound files from Fusion, with above
mentioned features then, let me tell you that these are possible even in Fusion
BI Publisher.
you inclined to use HCM Extracts feature, just because it has features like
output file encryption, built in SFTP integration point then think again… if
your main goal is to achieve pure outbound files from Fusion, with above
mentioned features then, let me tell you that these are possible even in Fusion
BI Publisher.
In this blog article, I will summarize the process to follow to implement
PGP/GPG encryption in Fusion BI Publisher.
The
encryption process is as follows:
encryption process is as follows:
Inbound:
public keys exchange should be done between Fusion cloud and originator system.
public keys exchange should be done between Fusion cloud and originator system.
1. Oracle
generates PGP public key, and provides us the same in the SR as an attachment
generates PGP public key, and provides us the same in the SR as an attachment
2. We
have to provide the originator system public key in the SR. the same will be
imported in to cloud HCM server (i.e., HCM APPL_TOP)
have to provide the originator system public key in the SR. the same will be
imported in to cloud HCM server (i.e., HCM APPL_TOP)
SLA:
3 -4 working days; depends on the SR severity
3 -4 working days; depends on the SR severity
Outbound:
1. Client
has to provide source system (i.e., in most of the cases it is external gateway
using which the source & target are being integrated) public key in the SR
has to provide source system (i.e., in most of the cases it is external gateway
using which the source & target are being integrated) public key in the SR
2. Oracle
imports the source system public key into BI Publisher server and
SFTP server, by BI team and Cloud-Ops respectively.
imports the source system public key into BI Publisher server and
SFTP server, by BI team and Cloud-Ops respectively.
3. Oracle
configures the BI publisher with target SFTP server details and the encryption
PGP public key details such as “Real Name”, “Email Address”, “Encryption
Type”, “Signed/Un signed”, which are used while
generating encryption PGP public
key for client source system.
configures the BI publisher with target SFTP server details and the encryption
PGP public key details such as “Real Name”, “Email Address”, “Encryption
Type”, “Signed/Un signed”, which are used while
generating encryption PGP public
key for client source system.
4. Test
the outbound interface. Run any BIP report in Fusion, in the report viewer,
click on send -> specify FTP as delivery option -> give the FTP
parameters. Output delivery to SFTP server should be successful.
the outbound interface. Run any BIP report in Fusion, in the report viewer,
click on send -> specify FTP as delivery option -> give the FTP
parameters. Output delivery to SFTP server should be successful.
SLA:
2 weeks; depends on the SR severity
2 weeks; depends on the SR severity
Once
the FTP Server has been defined with PGP encryption we can confirm the FTP
Server which has been defined and you can then test delivery to it. This would
work in the same way as any normal FTP delivery from HCM Extract, the PGP
encryption would be applied implicitly during the delivery. As long as you use
the FTP Server definition that has been configured for PGP encryption you will
receive encrypted files.
the FTP Server has been defined with PGP encryption we can confirm the FTP
Server which has been defined and you can then test delivery to it. This would
work in the same way as any normal FTP delivery from HCM Extract, the PGP
encryption would be applied implicitly during the delivery. As long as you use
the FTP Server definition that has been configured for PGP encryption you will
receive encrypted files.
Encryption
types supported:
types supported:
PGP – Unsigned
PGP – Signed
Note: Currently
Oracle is not supporting encryption keys with size beyond 2048
Oracle is not supporting encryption keys with size beyond 2048
Supported
documents: (MOS)
documents: (MOS)
Fusion
Applications BI Publisher : How to request configuration of Public/Private key
encryption for delivery from BI Publisher to external FTP Servers ( Doc ID
1987283.1 )
Applications BI Publisher : How to request configuration of Public/Private key
encryption for delivery from BI Publisher to external FTP Servers ( Doc ID
1987283.1 )
Hi Malla Nice article.. once the configuration are done and SFTP server added up in the BI adminstration page.. then where i can set up the delivery option for my BI report… do i have to create a new Custom Job for that,cant i do that through the BI agent ???
Such a great Blog. Got to know a lot of information. I would be thankful if you share more information about encrypted file transfer.
encrypted file transfer