File Upload EPM-FTP using Integration Cloud Implementation Guide
File Upload EPM-FTP using Integration Cloud Implementation Guide
Disclaimer 1
Introduction 1
Pre-requisite 1
Integration Flow 1
EPM_REST_CONNECTION Connection 4
FTP_CONNECTION Connection 5
Integration Steps 10
Step 1 11
Step 2 11
Step 3 11
Step 4 12
Step 5 12
Step 6 13
Step 7 18
OIC 19
EPM 20
Debugging 20
Security 22
Useful information 23
The file is read from the FTP location and then transferred to EPM cloud via a REST adapter connection.
Refer to EPM documentation for the REST service used in this flow.
https://docs.oracle.com/cloud/latest/epm-common/PREST/toc.htm
https://docs.oracle.com/cloud/latest/epm-common/PREST/upload.htm#PREST-lcm_rest_apis_3
This sample integration flow works on EPM Cloud release 18.03 or later and OIC 18.1.5 or later. In the
package, there is an implementation guide, which has the step-by-step instructions. There is an OIC
archive file - you import the archive to your OIC environment, make necessary configurations, and the
integration will work.
To download the package, please access this article on Oracle Cloud Customer Connect. If it's your first
time accessing Oracle Cloud Customer Connect, you will need to register by clicking the "Register"
button at the top right.
This sample integration is not part of the standard Oracle product. Oracle will not maintain it for future
changes or the particular requirements. If you need to update the integration, please refer to OIC
documentation.
Pre-requisite
Oracle Integration Cloud 18.1.5
Integration Flow
Below is the integration flow.
Once imported you will see the following integration flow created.
Two connections with names “EPM_REST_CONNECTION” and “FTP_CONNECTION” will appear under the
Connection page.
EPM_REST_CONNECTION Connection
On the Edit connection page for “EPM_REST_CONNECTION”, click Configure Connectivity. Enter your EPM Cloud
service URL, for example: https://planning-xyzcom.stg-pbcs.us1.oraclecloud.com. Click OK to close the dialog.
Click Configure Security and then provide the user credentials for your EPM cloud service. Then click OK.
FTP_CONNECTION Connection
On the Edit connection page for “FTP_CONNECTION”, click Configure Connectivity. Enter FTP/ SFTP server
details and click OK.
Then click Test and make sure the connection is successful. Click Save and Close.
To modify any of these, click on the Edit icon on the table row under the Value column.
Repeat the steps for all the required/desired fields and then click Close.
Save the integration by clicking on Save and then click Close to close the integration.
Below are the detailed steps of the sample integration. To configure or run the integration, you do not need to walk
through all the steps. To update the integration or build more features upon the sample, you can go through each
step.
Step 2
This is the Assignment step to initialize a few variables used later in the integration flow.
These variables are already covered in the section “Modify the integration”.
Step 3
This is mapping to the request schema for Download File Operation from FTP location. The variables initialized in
previous steps are mapped directly to corresponding fields in Download File Request.
Step 5
This is the mapping to Request schema for REST service to upload the file to EPM.
» The “File Reference” represents the stream of the file downloaded from FTP location. This is mapped directly to
the “streamReference, for example the application-octet stream of the REST request used to upload the file to
EPM.
» The variable $assign_epm_file_name is mapped to the path parameter “file_name” of the REST request.
» There is a query parameter “q” required for REST request. The value of “q” is determined based on two
parameters: “size” of the file, “$assign_epm_file_folder” variable.
» If the destination EPM folder where the file has to be uploaded is not specified, “$assign_epm_file_folder” would
be empty and then the value of q is constructed as following string:
{isLast:true,isFirst:true,chunkSize:size}
» If the destination EPM folder is specified, “$assign_epm_file_folder” would not be empty and then the value of q is
constructed as following string:
{ isLast:true,isFirst:true,chunkSize:size, extDirPath: "$assign_epm_file_folder" }
Step 6
This step specifies the REST endpoint details to upload the file to EPM. Refer to EPM documentation for details on
the REST service used for upload.
https://docs.oracle.com/cloud/latest/epm-common/PREST/upload.htm#PREST-lcm_rest_apis_3
To specify the query parameter, “Add and review parameters for this endpoint” is checked.
To specify request payload type, “Configure a request payload for this endpoint” is checked.
To specify the response type and schema, “Configure this endpoint to receive the response” is checked.
https://docs.oracle.com/cloud/latest/epm-common/CEPMA/toc.htm
OIC
You can check the status of the integration from the Monitoring page in OIC.
Debugging
You can view the messages generated during the flow execution by going to the Tracking page on OIC if tracing
was enabled during activation.
The below user accounts are used in the sample integration. It is the responsibility of the customer to manage the
accounts and security.
OIC user account Login, import, modify, and run the integration.
EPM Cloud user account Invoke the REST service on EPM cloud to upload the file
Integration Cloud
https://docs.oracle.com/en/cloud/paas/integration-cloud-service
EPM Cloud
https://cloud.oracle.com/epm-cloud
https://docs.oracle.com/cloud/latest/epm-common/PREST/toc.htm
https://docs.oracle.com/cloud/latest/epm-common/PREST/upload.htm#PREST-lcm_rest_apis_3
EPM Automate
https://docs.oracle.com/cloud/latest/epm-common/CEPMA/toc.htm
REST Adapter
https://docs.oracle.com/en/cloud/paas/integration-cloud-service/icsre/getting-started-rest-adapter.html
FTP Adapter
https://docs.oracle.com/en/cloud/paas/integration-cloud-service/icsft/getting-started-oracle-ftp-cloud-adapter.html
CONNECT W ITH US
blogs.oracle.com/oracle
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means,
twitter.com/oracle electronic or mechanical, for any purpose, without our prior written permission.
oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.