Import Application - Traditional CopyApp Simplified.

1. IMPORT HFM Application
Requirements: -
11.1.2.4.200
HFM Applicationinthe Source Environment.
Steps: -
DB (Oracle) – Linkingand GrantingRoles.
Credits to the DBAs Hanumantharao Ballana and Ajith Hanbalshivappa for helping in granting the roles and linking,
of which the import would not have been successful.
Importingthe applicationfromthe Source tothe Destination
Linkingthe DB
Connectto the Destination HFMSchemaand create a Linkto the Source HFMSchema.Eg: If the
requirementistoimportthe applicationsfromaTestto DevelopmentEnvironment.Connecttothe
DevelopmentHFMSchemacreate linktothe TestSchema. So indevelopmentenvironmentthe TEST
HFM applicationswill be displayedandavailable forimport.
A name has to be givenforthe Linkin thisscenariothe name given inthisexperiment isAPP_IMPORT.
The belowSQL Commandcreatesa linktothe Test Schema.
create databaselink APP_IMPORT
connectto TEST_HFM_SCHEMA
identified by Password
using 'SERVICENAME';
Priorto checkingif the linkconnects successfully,make sure thatthe contents of the tnsnames.orafile
fromthe TestEnvironmentare copiedtothe Developmenttnsnames.ora.
Eg:
ServiceName=
(DESCRIPTION =
(ADDRESS= (PROTOCOL=TCP)(HOST= name.domain.com)(PORT=1521))
(CONNECT_DATA =
(SERVER= DEDICATED)
(SERVICE_NAME=ServiceName)
)
)

2. Connectioncheck.
The belowwasdone byusingSQL Developer.
In the belowexample APP_IMPORTisthe name of the linkand the connectionissuccessful.
Confirmthe HFMUTIL_PKG is foundunderthe Packages
Priorto performinganimportGrant the roles explicitly tothe Schema.
GRANT ALTER SESSION TO "<Schema_name>";
GRANT CREATE PROCEDURE TO "<Schema_name>";
GRANT CREATE SEQUENCE TO "<Schema_name>";
GRANT CREATE SESSION TO "<Schema_name>";
GRANT CREATE VIEWTO "<Schema_name>";
GRANT UNLIMITED TABLESPACETO "<Schema_name>";
GRANT CREATE TYPE TO "<Schema_name>";
GRANT CREATE TABLE TO "<Schema_name>";
GRANT CREATE DATABASELINKTO "<Schema_name>";
The requiredprivilegesshouldbe grantedexplicitly.
Navigate > Administer>ConsolidationAdministration

3. ImportApplication
Database Links/LinkedServers: APP_IMPORT– EPM_SYS_HFM (Link_NAME– Schema NAME) this is
the linkfor the Test EnvironmentSchema.
Source Application –Speedislisted,whichwe are going to import to the Developmentenvironment.
DestinationApplication –Speed(same name given)
DestinationCluster: Devclusterdisplayed,hiddenforspecificreasons.
User Managementproject – HFM
ImportAudit…- Nothingselected,canbe selectedasperrequirement.

4. ClickImportApplication
Warningis displayed.Clickok. Priortoclickingok,confirmif the source appisin adminmode sothat no
userscan loginandthe loggedinuserswill be loggedoff.
Anothertabopenswhere the progressof the importisdisplayed. ClickRefreshtoRefreshthe statusof
the Import.

5. Completedstatuswill be displayedif the Importissuccessful.
Log locationandthe file name.
Do a refreshandthe importedapplicationwill be displpayed.
The applicationisimportedasa Classicapplication,thoughthe source isanEPM Application.The
Importedapplicationcouldthenbe transformedasanEPM Application.
Openingthe Importedapplicationinthe destinationenvironment.

6. Comparingthe applicationinthe Source Environment.
Thisconcludesthe ImportApplicationanew feature inHFMversion11.1.2.4