Deployment

Deploys an application to a specified product.

Execute Deploy
Parameters(ApplicationName, InstanceName, ApplicationServer, HubProject, ClearAll, CheckIntegrity, waitforcompletion, deployOption, Notes)
Values('AppName', 'HFM931', 'localhost:1423', 'Default Application Group', 'false', 'false', 'true', 'true', ‘AppView’, 'deploy comments sample');

ApplicationName—The name of an existing application. You cannot use #Shared as the application name for a deployment.

InstanceName—Name of the instance to deploy to.

Note:

The instance name is required and should be the same as the name of the logical web application (LWA) defined in the registry. There may be multiple logical web application names; you can use any of these names. However, after you deploy the application, you must use the logical web application name used when you deployed the application.

ApplicationServer—Name of the application server to deploy to.

HubProject—Oracle Hyperion Shared Services project to add the deployed application to.

ClearAll—Deletes all dimension members in the application database and any corresponding data, journals, and intercompany transactions. (Available for Consolidation applications only.) Allowed values:

  • True

  • False

CheckIntegrity—Checks the metadata against the data to ensure integrity. (Available for Consolidation applications only.) Allowed values:

  • True

  • False

deployOption—Specifies the type of deployment that you want to perform. The default value is AppView, which deploys the application only.

WaitForCompletion—If set to True, the Batch Client waits for the job to finish. If set to False, the Batch Client submits the job and continues. Allowed values:

  • True

  • False

For Planning applications:

datasourceName—Creates a data source with the name that you specify. This value is a string.

CreateOutline—Creates the Essbase outline if you are deploying the application for the first time. Allowed values:

  • True

  • False

RefreshOutline—Refreshes the application database after changing the application structure. Allowed values:

  • True

  • False

CreateSecurityFilters—Stores access permissions in an encrypted data file (Essbase.sec). Allowed values:

  • True

  • False

SharedMembersSecurityFilters—Applies access permissions to shared members. Allowed values:

  • True

  • False

ValidateSecurityFilterLimit—Identifies security filters that exceed the Oracle Essbase security filter limit of 64 KB per row. This validates filter size to ensure it does not exceed the size limit before building Oracle Essbase security filters. Allowed values:

  • True

  • False

Notes—Optionally stores any comments or notes that you may want to add regarding the deployment.