Upload large Application Snapshot files to PBCS using EPM Automate


As I recently discovered when trying to upload an Application Snapshot from my client's Production environment to my client's Test environment, once an Application Snapshot gets too large you will receive the below error when attempting to upload the snapshot through your browser:


The file I was attempting to upload was around 4GB but I am unsure of the official size limit for uploading files through your browser. However, as your application is used over time it will continue to grow and, before you know it, your snapshot size will have reached this limit (whatever it may be!)

To get around this issue, we can use the EPM Automate command UploadFile.

The UploadFile command is used to upload a file from your local computer to the PBCS server. The file being uploaded could contain data, metadata, other application artefacts or be an entire Application Snapshot backup.

The syntax for using the UploadFile command in a batch file is as follows:

Call epmautomate login USERNAME PASSWORD URL IDENTITYDOMAIN
Call epmautomate uploadfile "FILENAME"
Call epmautomate logout

Where the parameters in the above script are as follows: 
  • USERNAME - the user name of the service administrator 
  • PASSWORD - the password of the service administrator
  • URL – the URL of the PBCS service instance that you wish to connect to
  • IDENTITYDOMAIN – the identity domain of the PBCS service instance
  • "FILENAME" – the full name and path of the file (from your local computer) that you wish to upload to your PBCS service
The above syntax will upload the file to the default location. For Application Snapshots, this will be the Migration section of PBCS. The Snapshot will then be available to import to your PBCS environment using the normal Import functionality within the migration area of PBCS.
 

Comments

  1. BB5 October 2018 at 08:02

    Hi. Great post on uploading snapshots! I have a question for you. Our snapshots are too large so we have to use the epmautomate uploadfile command. I used the steps outlined above. The file is uploaded but does not show up under the Migration Snapshot area in PBCS but rather in the inbox/outbox explorer. How do I get the snapshot to upload to the correct place?

    ReplyDelete
    Replies
    1. Lydia Maksoud14 November 2018 at 08:01

      Hi, the above syntax ("Call epmautomate uploadfile", followed by the file name only)should upload the Snapshot into the migration area in PBCS as this is the default area for Snapshot zip folders. Hope that helps!

      Delete
  2. krajowy1 February 2019 at 12:07

    It does not.

    ReplyDelete

Post a Comment

Popular posts from this blog

Executing Smart View Retrievals using VBA

Image
When working with Hyperion systems, Smart View is a key tool used for reporting, as well as inputting data. It provides a valuable link between Hyperion and Excel, which allows users to retrieve data from the database straight into Excel with ease. Smart View functions are available through the Smart View toolbar and can be used with Essbase, HFM, Planning or Cloud connections. Occasionally, it is necessary to perform Smart View functions behind the scenes using VBA code, rather than manually using the Smart View toolbar. For example, a spreadsheet which will refresh all the Essbase retrieval sheets on opening, so that users can view the most up to date data, without having to remember to refresh each of the retrieval sheets themselves. This blog will be cover how to retrieve data using a Smart View refresh function in VBA. For more information about Smart View Excel VBA functions, go to the Oracle Hyperion Smart View Developers Guide .  System Requirements T
Read more

Loading Actuals from Fusion ERP Cloud to PBCS

Image
If you’re looking to set up a data load of Actuals from ERP to PBCS and have heard this is an “Out of the box” integration, then good news! Not only is the OOTB connector included within PBCS Data Management but the integration is simple to setup and to schedule using EPM Automate. This blog will detail how to setup the ERP to PBCS connector in Data Management and some of the common errors found when running the data load. The first thing to know about this integration is that the data source is actually the ASO Essbase cube which sits underneath the Fusion ERP tables, holding the period Actuals values. This ERP Essbase cube is created using job ‘Create General Ledger Balances Cube’ when configuring the ERP system. This cube must be created before the integration can be set up correctly and can be accessed directly via Smart View for reconciliations. Set up the Source System As this is an Oracle built connector, it’s as simple as providing a name for the source system
Read more

Loading multi-period row data files using Data Management

Image
The ability to load multi-period data with the Period and/or Year in the rows is not particularly new (since release 16.10), however it is something that most people seem to forget is possible in Data Management. This really is something worth remembering as it eliminates the need to either split the data files into one file per month or try to pivot the month into the columns. In order to set this up, let’s firstly look at how to add the Period and Year columns to the import format. Add the Period and Year columns using the Add -> Source Period Row dropdown, and input: The Source Column name – e.g. PERIOD The Field Number (file column) – e.g. 3 Any required expressions for that field  As these are Period/Year dimensions, the mappings are not held in the usual Data Load Mappings area. Instead they are configured in the Period Mappings , under the Source Mapping tab. Select the Source System as File to add a new mapping calendar for loading the data file
Read more