FDM Upgrade to system11.

We are running into issues upgrading to system 11. Some of the custom dimensions in HFM were unused and we did not bother to map them in system9. We are having an issue when doing the upgrade since the new version requires all the custom dimensions to be active and mapped i.e. * to None.
We have a lot of maps and validation rules which need update and are looking for easier ways for a workaround i.e. some script change that could solve the issue.
Has anyone encountered the issue and how was it solved.
Thanks in advance !!!

My game plan for doing this is a SQL script to create a mapping item for each map/dimemsion that maps * to [None]. Not sure if there is a better official option, but this should work just fine. I'm actually working on this exact thing next week. I'll let you know how that turns out and will share script if it works to plan.

Similar Messages

  • Upgrading FDM 11.1.1 to 11.1.1.3

    Hi there,
    I need some help understanding the FDM upgrade process from 11.1.1 to 11.1.1.3
    First of all, the doc states that if you are already on 11.x then 11.1.1.3 is considered a maintenace release.
    However the install doc also states that FDM must first be uninstalled before installing 11.1.1.3.
    I have the following questions:
    - Do we really need to uninstall FDM 11.1.1 prior to installing 11.1.1.3 or does the uninstall only apply to pre System11 versions?
    - If I have to unsinstall FDM, what is the best way to keep my adapters configurations? Obviously by installing 11.1.1.3 I will need to import the new adapters. How can I "copy" my existing adapters config to the new adapters? What is the best practice?
    Thanks for your help.
    Seb

    1) check upgrade in new env with copy application (just restore backup db and app folders in new place )
    becouse FDQm will do upgrade database schema and maybe u recive error on constraint
    2) u can use old adapters in new FDQM
    3) u realy need to uninstall
    ER

  • Upgrade/Migrate Planning application from 11.1.1.1 to 11.1.2.3

    I have installed 11.1.2.3 on Window 2008 R2 servers.  Our old environment is on  11.1.1.1 is still up and running on different server(windows 2003).  I have successfully completed the following:
    1.     All Hyperion products (HSS,BIPLUS,CALC MGR,EPMA,Planning,FDME installed successfully and everything working fine.
    2.     I am able migrate the all FR reports successfully(Export/Import method) and Yet to test the reports after application migration.
    3.     I created  Planning apps in the new system which is similar to old application , I can open the Planning Application Administrator via WorkSpace URL.
    My question :1) Can i migrate Planning repository DB schema from SQL server 2005 to New application schema on SQL server 2008.
                                (There is any update required before and all the repository table of 11.1.2.3  similar to 11.1.1.1 
                       2) How can i migrate the Business rules to  Calc manager(.i.e 11.1.1.1 to 11.1.2.3)
                       3)How can i migrate the FDM application (.i.e 11.1.1.1 to 11.1.2.3)
    Please let me know if you need any further information.

    First of all 11.1.1.1 to 11.1.2.3 direct migration is not supported so if you have issue upgrading planning then unfortunately that may be the reason.
    SQL Server 2005 to 2008 should be ok but if you are concerned then upgrade the sql server 2005 version to 11.1.2.3 then use LCM to change database versions.
    Business Rules read the following support doc - "Hyperion Business Rules (HBR) to Calculation Manager Migration White Paper (Doc ID 1528121.1)"
    FDM - Upgrade utility.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • FDM & ERPI to FDMEE - Upgrade approach/challenges ?

    Hello,
    We are in FDM/ERPI 11.1.2.2.300 (used for loading data from EBS and file systems into HFM 11.1.2.2.300) and planning to upgrade (within the existing environment [in-place upgrade]) to 11.1.2.3. As we see that FDM/ERPI are integrated together as FDMEE in 11.1.2.3, we had big grey area on how FDMEE would function in contrast to disparate FDM/ERPI.
    We needed inputs from veterans or anyone who had experienced the upgrade to answer the follwing queries.
    Queries:
    [1] We have come to know that FDM and ERPI are integrated together as FDMEE in 11.1.2.3.
         [a] Since we have FDM and ERPI as separate components in 11.1.2.2.300, how should FDM and ERPI components be upgraded to FDMEE ? Any specific steps / approach that need to be followed ?
         [b] Are there any known issues / challenges involved in upgrading from disparate FDM & ERPI to FDMEE ?
         [c] How would ERPI artifacts (of 11.1.2.2.300) function in FDMEE - Are there any specific migration or any manual set-up required post-upgrade (to 11.1.2.3) to have ERPI artifacts (like source system, period mapping, location, import formats, data load mapping etc)      functioning in FDMEE ?
         [d] Similarly how would FDM artifacts (from 11.1.2.2.300) function in FDMEE ? Are there any specific migration or manual set-up required post-upgrade (to 11.1.2.3) to have FDM artifacts (like mapping, validation rules etc) functioning in FDMEE ?
    [2] Since only ODI 11.1.1.7 is compatible with 11.1.2.3 (from Compatability matrix), how do we upgrade ODI from 11.1.1.6 to 11.1.1.7 ? Are there any patch available to upgrade or should we uninstall ODI 11.1.1.6 and install ODI 11.1.1.7 ?
    Any insightful response will be helpful for us as it would help us to gain clarity/confidence and comfort in upgrading to 11.1.2.3.
    Regards,
    Sathish

    hello Sathish
    As you are upgrading from 11.1.2.2.300 to EPM 11.1.2.3 (within the existing environment [in-place upgrade]) , it's called Applying maintenance release EPM 11.1.2.3 on EPM 11.1.2.2
    [a] when you apply maintenance release , FDM 11.1.2.2 gets upgraded to FDM 11.1.2.3 ,
         and ERPi gets upgraded to FDMEE 11.1.2.3
    [b] i have not faced any issue while upgrading FDM
    [c] please check epm_install.pdf for EPM 11.1.2.3 for upgradation  task for FDM and FDMEE  (see page 257 / 258)
    regards,
    -DM

  • Upgrading FDM applications from 11.1.1.3 to 11.1.2.2

    We have freshly installed FDM 11.1.2.2 on a new server and I am trying to migrate our existing 11.1.1.3 applications. I first need to upgrade the scema for these applications. The documentation for this procedure is scarce but I was able to do the following:
    - Copied Application folders from FDMDATA in source (11.1.1.3) to target (11.1.2.2).
    - Opened Workbench in 11.1.2.2 and chose 'Add application' and added the application by referencing the app path to the newly copied files and new DB and schema information.
    - Ran the schema upgrade utility for the newly added application. I am now able to open the new application successfully in 11.1.2.2.
    My problem is that I need to import the .XML file with all of the application elements such as locations, scripts, adaptors, etc from the old 11.1.1.3 FDM server. When I try to do this, it says that the .XML file is from an old schema and it cannot import it.
    I am sure I missed a step somewhere to get the XML file upgraded but I am not sure where. How can I upgrade the XML file itself?

    All the application elements etc such as locations, mappings etc will have be contained in the 11.1.1.3 DB schema which you ran the update on so no need for the XML file. Things such as scripts are contained in the application directory structure you copied accross so you have those as well. As for the adapters you will need to import and register the latest version of the adpaters which are compatible with the 11.1.2.2 FDM release and configure them as appropriate to refrence your target systems, so you don't need to import from the old XML for that. In short you don't need to import the XML file as part of the migration activity.

  • FDM schema upgrade error 91-Object variable or With block variable not set

    Hi,
    I try to upgrade FDM schema to 11.1.2.1 using FDM Workbench Client.
    From log it looks like we go fine through first 4 steps.
    When it comes to metadata (5 step) FDM gives the same error:
    Step 5: Updating Metadata Failed!
    91-Object variable or With block variable not set
    User that logs into the app is domain admin.
    I just check out that shared folder (FDM folder) has write permission for this user.
    DB user set in connection properties is DB owner.
    Under Dcomcnfg identity set to the right domain user in the following:
    HFMServer
    HFMService
    HSXServer
    HSVDataSource
    Any idea what is wrong?
    regards
    Karol

    idea looks good.
    Completely forgot to install Excel but we have to organize 64Bit version.
    For now 5 points as this is helpfull :) will check tomorrow morning
    thanks
    Karol

  • Changing HFM adapter after upgrading FDM 11.1.1.3 to 11.1.2.1

    Hi,
    I have upgraded FDM from version 11.1.1.3 to 11.1.2.1. The last step I guess is to re-register the adapters to 11.1.2.1 version - FM11x-G5-E
    Does any know how to achieve that with out re-building the mappings?
    Or any pointers is appreciated!
    Thanks,
    PM

    The adapter is not tied to the mapping table. You just need to import the adapter XML and then register and configure the adapter on each FDM application server in the environment:
    a) Login to the FDM application via the workbench client
    b) Choose File > Import and choose the FM11x-G5-E.XML file and choose "open"
    c) Click "Select All" and click "import" to import the adapter into the application
    d) Copy the "AdapterComponents" folder that was contained in the adapter .zip file to the Oraclle\Middleware\EPMSystem11R1\Products\FinancialDataQuality\SharedComponents directory
    e) Choose File > Register Adapter and choose the AdapterComponents\fdmFm11xG5E\fdmFM11xG5E.dll file and choose "open"
    f) Right-Click on the FM11x-G5-E adapter and choose"configure" and enter the FDM Service account username/password/confirm password/domain and click OK. **NOTE: this is the account that was used for the FDM configs (App Server, Load Balance Server, Task Manager, Web Config)
    g) Choose Tools > Application Settings and change the System Code to the FM11x-G5-E adapter
    You can then syncronzie the settings from the old adapter to the new adapter by right-clicking on the Fm11x-G5-E adapter and choose "Syncronize" and choose the FM11x-G5-C adapter as the source and click OK to copy the settings to the new adapter.
    You may have to update the target periods and categories in the Control Tables on the web.
    That should be everything.

  • MSAD upgrade to 2008 R2 - user authentication - HFM FDM 9.3 DM 11.1

    Looking to see if planned MSAD upgrade from 2003 to 2008 R2 will require any HFM, FDM or Disclosure Management administration to avoid possible user authentication errors? I understand they are compatible, but that doesn't necessarily mean connections will be uninterrupted. Anyone been there?

    What was the error in the schema update utility?
    The schema update log would be in the outbox\logs directory of the FDM application that is being upgraded.

  • Can FDM handle more than one year at a time?

    Hi,
    I'm trying to load a multi-load file through FDM with the target being an Essbase cube and the source being a text file. The file is for 36 months which crosses 3 years. The problem is Oracle support is saying FDM can only handle one calendar year at a time and we need to load 3 separate files.
    The file imports and validates ok. And the export only pushes data to the first year '2010' but it doesn't error out.
    Any ideas?

    If you use an excel file as the source, you can load all 36 periods.
    You can also modify the adaptor to support this action but I would caution you that doing so will cause support to no longer support your application without requiring you to import a non customized adaptor. This also has consequences for when upgrading.
    Let me add, FDM support is the best in the business. I have never had a situation where what they told me was incorrect. What you are trying to accomplish would be a custom solution that should be implemented by an experienced FDM resource that understands the impact of the customization.
    Edited by: TonyScalese on May 6, 2010 3:10 PM

  • Upgrade R12.0.4 DB 10.2.0.3 to 11.1.0.7

    Hi All,
    I have followed the below steps to upgrade R12 DB on SLES 10 SP2 from 10g to 11g
    3- Perform pre-requsites for patch 6928236
    4- Apply INTEROPERABILITY PATCH 6928236
    5- Apply TXK - 12.0.4 Consolidated Patch 1 7207440
    6- Perform patch 7207440 post install steps
    7- Apply patch 6400501 to applicaition tier, follow these steps:
         cd /oracle/apps/prod/a*/a*/a*
    . ./APPSPROD_prod.env
    export PATH=$PATH:$ORACLE_HOME/OPatch
    cd /oracle/patches/apps/6400501
         opatch lsinventory -invPtrLoc $INST_TOP/admin/oraInst.loc
    opatch apply -invPtrLoc $INST_TOP/admin/oraInst.loc
    After patch is applied do the following:
    cd $ORACLE_HOME/forms/lib
    make -f ins_forms.mk install
    cd $ORACLE_HOME/reports/lib
    `
    8- Apply timezone V4 patch 5632264 to 10g DB (OLD DB) using opatch apply. shutdown and start it up again for the change to take effect
         export PATH=$PATH:$ORACLE_HOME/OPatch
         cd /oracle/patches/db/5632264
         opatch lsinventory -invPtrLoc $ORACLE_HOME/oraInst.loc
         opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc     
    9- gedit /home/oracle/.bash_profile Create (create it if it doesn't exist) and write in it
    # Oracle Settings
    TMP=/tmp; export TMP
    TMPDIR=$TMP; export TMPDIR
    ORACLE_BASE=/oracle/apps/prod/db11; export ORACLE_BASE
    ORACLE_HOME=$ORACLE_BASE/tech_st/11.1.0; export ORACLE_HOME
    ORACLE_SID=PROD; export ORACLE_SID
    LD_LIBRARY_PATH=$ORACLE_HOME/lib; export LD_LIBRARY_PATH
    PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH; export PATH
    PERL5LIB=$ORACLE_HOME/perl/lib/5.8.3:$ORACLE_HOME/perl/lib/site_perl/5.8.3 export PERL5LIB
    TNS_ADMIN=$ORACLE_HOME/network/admin; export TNS_ADMIN
    10- Install Oracle Database 11gR1 software only using the command
    ./runInstaller -invPtrLoc /oracle/apps/prod/db11/tech_st/11.1.0/admin/oui/PROD_prod/oraInventory/oraInst.loc
    In the Installation Types window, use the Product Languages button to select any languages other than American English that are used by your Applications database instance. Choose the Enterprise Edition installation type. In the subsequent windows, select the options not to upgrade an existing database and to install the database software only. Select Oracle Home Name to be PROD_db111_RDBMS
    11- Install Oracle Database 11g Products from the 11g Examples CD using the command
    ./runInstaller -invPtrLoc /oracle/apps/prod/db11/tech_st/11.1.0/admin/oui/PROD_prod/oraInventory/oraInst.loc
    In the Installation Types window, use the Product Languages button to select any languages other than American English that are used by your Applications database instance.
    12- Set ENV variables in /home/oracle/.bash_profile
    ORACLE_BASE=/oracle/apps/prod/db11; export ORACLE_BASE
    ORACLE_HOME=$ORACLE_BASE/tech_st/11.1.0; export ORACLE_HOME
    LD_LIBRARY_PATH=$ORACLE_HOME/lib; export LD_LIBRARY_PATH
    PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH; export PATH
    PERL5LIB=$ORACLE_HOME/perl/lib/5.8.3:$ORACLE_HOME/perl/lib/site_perl/5.8.3 export PERL5LIB
    13- Install Oracle Database 11gR1 Patchest 7 using the command
    ./runInstaller -invPtrLoc /oracle/apps/prod/db11/tech_st/11.1.0/admin/oui/PROD_prod/oraInventory/oraInst.loc
    14- Run $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/nls/data/old/cr9idata.pl
    15- Add the following line to /home/oracle/.bash_profile ORA_NLS10=/oracle/apps/prod/db11/tech_st/11.1.0/nls/data/9idata; export ORA_NLS10
    16- export $PATH:$ORACLE_HOME/OPatch
    17- cp $ORACLE_HOME/oraInst.loc /etc
    18- opatch lsinventory
    19- Apply patch 7486407 to 11g home using
         opatch apply
    20- Apply patch 7684818 to 11g home using
         opatch napply -skip_subset -skip_duplicate
    21- Gather stats for dictionary tables on the 10g DB (OLD DB) using exec dbms_stats.gather_dictionary_stats;
    22- Extende old Database tablespace SYSAUX to be 500 using the following command
    A- alter database datafile '/oracle/apps/prod/db/apps_st/data/sysaux01.dbf' resize 500m;
    B- alter database datafile '/oracle/apps/prod/db/apps_st/data/sysaux01.dbf' autoextend on;
    23- Run the Oracle Net Configuration Assistant, to start Oracle Net Configuration Assistant run
    netca from $ORACLE_HOME/bin.
    24- Edit /etc/oratab and add the following line PROD:/oracle/apps/prod/db/tech_st/10.2.0:N otherwise DBUA will not find the old DB
    25- MANDATORY STEP: Copy the initPROD.ora file from Linux Patches to $ORACLE_HOME/dbs
    26- copy new DB oraInst.loc to etc cp $ORACLE_HOME/oraInst.loc /etc/oraInst.loc
    26- Upgrade the Database Using the Database Upgrade Assistant from 11gR1 database and follow the steps
         run dbua to start the Database Upgrade Assistant
    The upgrade failes in the post-upgrade steps were it's creating the control file for the new database (during the DBUA i have specifed that i need to move DB files to a new location) with the error ORA-01166: file number 288 is larger than MAXDATAFILES (100) ORA-01110: data file 288: '$ORACLE_HOME/apps_st/data/PROD/system10.dbf'
    I have checked DB_FILES in initPROD.ora and it's 512 I also checked the MAXDATAFILES in the control file from source 10g DB and it's 512 (i used alter database backup controfile to trace to get the maxdatafiles value)
    Any ideas how to fix this issue?
    Appreciate your help.
    Mohammed Tammous

    Create a sql script file create_controlfile.sql. Open a trace log, and find something similar to:
    show sqlprompt
    set sqlprompt 'SQL>'
    Create controlfile reuse set database "INSTANCE_NAME"
    MAXINSTANCES 8
    MAXLOGHISTORY 1
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    Datafile
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/system01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/system02.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/system03.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/system04.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/system05.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/ctxd01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/owad01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_queue02.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/odm.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/olap.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_tools1.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_ref03.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/xx_cdf_data1.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/xx_cdf_idx1.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/system10.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/system06.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/portal01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/system07.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/system09.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/system08.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/system11.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/undo01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_txn_data01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_txn_ind01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_ref01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_int01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_summ01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_nolog01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_archive01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_queue01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_media01.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_txn_data02.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_txn_data03.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_txn_ind02.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_txn_ind03.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_txn_ind04.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_txn_ind05.dbf',
    '/disk1/dbtier/db/oradata/INSTANCE_NAME/a_ref02.dbf',
    '/disk1/dbtier/data/sysaux01.dbf'
    LOGFILE GROUP 1 (>'/disk1/dbtier/db/oradata/INSTANCE_NAME/log01a.dbf',>'/disk1/dbtier/db/oradata/INSTANCE_NAME/log01b.dbf' ) SIZE 10240K,
    GROUP 2 (>'/disk1/dbtier/db/oradata/INSTANCE_NAME/log02a.dbf',>'/disk1/dbtier/db/oradata/INSTANCE_NAME/log02b.dbf' ) SIZE 10240K RESETLOGS;
    set heading off
    set timing off
    set pagesize 0
    set feedback off
    set linesize 2048
    set sqlprompt 'SQL_ENGINE_END_OF_SQL'
    show sqlprompt
    set sqlprompt 'SQL>'Copy this to your create_controlfile.sql and change MAXDATAFILES 100 to MAXDATAFILES 1024. Then connect to database with sqlplus as sysdba user and run @create_controlfile.sql

  • Cannot edit data model after upgrading to 10.1.3.4.1

    Hi,
    I've recently upgraded from 10.1.3.4 to 10.1.3.4.1 running under Tomcat 6.
    But now I cannot work with data models anymore. When I click on 'New' while Report > Data Model is selected, a new model is created but I cannot work with it.
    While editing an existing report, clicking on a data model does nothing. In IE8, I can see the following error message:
    Webpage error details
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; FDM; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
    Timestamp: Sun, 13 Sep 2009 10:12:06 UTC
    Message: 'ds_fixed_schema' is null or not an object
    Line: 746
    Char: 5
    Code: 0
    URI: http://...:8080/xmlpserver/js/xdoeditor/datasetpanel.js
    Any help would be greatly appreciated.

    I dont think BIP is certified on IE8 yet. would recommend either dropping back a version or using FF
    Tim

  • Weblogic 10.3.5 error during upgrade to  JSF 2.0

    I created a very simple test application using Jdev 11.1.2.0 which deployed well aganist the IntegratedWeblogicServer.
    I copied the deployed project from ${MW_HOME}/jdeveloper/system11.1.2.0.38.59.69/o.j2ee/drs/TestApplication to ${WEBLOGIC_SERVER_HOME}/user_projects/applications/base_domain_t1/TestApplication.
    Both the weblogic servers have identical config.xml files and similar set of directories. On doing some research over this error, I found out similar errors occuring while upgrade for JBoss and Glassfish servers too.
    Any pointers on what the problem could be?
    <Apr 11, 2011 1:59:10 PM PDT> <Error> <javax.enterprise.resource.webcontainer.jsf.config> <BEA-000000> <Critical error during deployment:
    com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
    at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:351)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:222)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: java.lang.NullPointerException
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.<init>(UnifiedRenderKit.java:129)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.createRenderKit(UnifiedRenderKit.java:111)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKitFactory.getRenderKit(UnifiedRenderKitFactory.java:59)
    at org.apache.myfaces.trinidadinternal.renderkit.CoreRenderKitFactory.getRenderKit(CoreRenderKitFactory.java:55)
    at com.sun.faces.config.processor.RenderKitConfigProcessor.addRenderKits(RenderKitConfigProcessor.java:236)
    at com.sun.faces.config.processor.RenderKitConfigProcessor.process(RenderKitConfigProcessor.java:155)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.ManagedBeanConfigProcessor.process(ManagedBeanConfigProcessor.java:266)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.ValidatorConfigProcessor.process(ValidatorConfigProcessor.java:116)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.ConverterConfigProcessor.process(ConverterConfigProcessor.java:122)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.ComponentConfigProcessor.process(ComponentConfigProcessor.java:113)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:333)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:112)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:212)
    at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:332)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:222)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Apr 11, 2011 1:59:10 PM PDT> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null.
    java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:290)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    Truncated. see log file for complete stacktrace
    Caused By: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
    at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:351)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:222)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.NullPointerException
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.<init>(UnifiedRenderKit.java:129)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.createRenderKit(UnifiedRenderKit.java:111)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKitFactory.getRenderKit(UnifiedRenderKitFactory.java:59)
    at org.apache.myfaces.trinidadinternal.renderkit.CoreRenderKitFactory.getRenderKit(CoreRenderKitFactory.java:55)
    at com.sun.faces.config.processor.RenderKitConfigProcessor.addRenderKits(RenderKitConfigProcessor.java:236)
    Truncated. see log file for complete stacktrace
    >
    <Apr 11, 2011 1:59:10 PM PDT> <Error> <javax.enterprise.resource.webcontainer.jsf.config> <BEA-000000> <Unexpected exception when attempting to tear down the Mojarra runtime
    java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory
    at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:800)
    at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:302)
    at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:104)
    at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:323)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
    at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3224)
    at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:247)
    at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:461)
    at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1535)
    at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:507)
    at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:387)
    at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
    at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
    at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
    at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
    at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:547)
    at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
    at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:192)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:184)
    at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:642)
    at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:63)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Apr 11, 2011 1:59:10 PM PDT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'TestApplication'.
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.NullPointerException
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.<init>(UnifiedRenderKit.java:129)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.createRenderKit(UnifiedRenderKit.java:111)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKitFactory.getRenderKit(UnifiedRenderKitFactory.java:59)
    at org.apache.myfaces.trinidadinternal.renderkit.CoreRenderKitFactory.getRenderKit(CoreRenderKitFactory.java:55)
    at com.sun.faces.config.processor.RenderKitConfigProcessor.addRenderKits(RenderKitConfigProcessor.java:236)
    Truncated. see log file for complete stacktrace
    >

    Here is the stack trace. A quick online search points me to pages asking me to isolate jsf2.0 from any myfaces implementations. Not sure if that is the problem or how to resolve it.
    <Apr 11, 2011 3:14:21 PM PDT> <Error> <javax.enterprise.resource.webcontainer.jsf.config> <BEA-000000> <Critical error during deployment:
    com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
    at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:351)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:222)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: java.lang.NullPointerException
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.<init>(UnifiedRenderKit.java:129)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.createRenderKit(UnifiedRenderKit.java:111)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKitFactory.getRenderKit(UnifiedRenderKitFactory.java:59)
    at org.apache.myfaces.trinidadinternal.renderkit.CoreRenderKitFactory.getRenderKit(CoreRenderKitFactory.java:55)
    at com.sun.faces.config.processor.RenderKitConfigProcessor.addRenderKits(RenderKitConfigProcessor.java:236)
    at com.sun.faces.config.processor.RenderKitConfigProcessor.process(RenderKitConfigProcessor.java:155)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.ManagedBeanConfigProcessor.process(ManagedBeanConfigProcessor.java:266)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.ValidatorConfigProcessor.process(ValidatorConfigProcessor.java:116)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.ConverterConfigProcessor.process(ConverterConfigProcessor.java:122)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.ComponentConfigProcessor.process(ComponentConfigProcessor.java:113)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:333)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:112)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110)
    at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:212)
    at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:332)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:222)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Apr 11, 2011 3:14:21 PM PDT> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null.
    java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:290)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    Truncated. see log file for complete stacktrace
    Caused By: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
    at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:351)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:222)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.NullPointerException
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.<init>(UnifiedRenderKit.java:129)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.createRenderKit(UnifiedRenderKit.java:111)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKitFactory.getRenderKit(UnifiedRenderKitFactory.java:59)
    at org.apache.myfaces.trinidadinternal.renderkit.CoreRenderKitFactory.getRenderKit(CoreRenderKitFactory.java:55)
    at com.sun.faces.config.processor.RenderKitConfigProcessor.addRenderKits(RenderKitConfigProcessor.java:236)
    Truncated. see log file for complete stacktrace
    >
    <Apr 11, 2011 3:14:21 PM PDT> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.StackOverflowError.
    java.lang.StackOverflowError
    at javax.faces.FactoryFinder$FactoryManagerCache.getApplicationFactoryManager(FactoryFinder.java:698)
    at javax.faces.FactoryFinder$FactoryManagerCache.access$100(FactoryFinder.java:666)
    at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:300)
    at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:104)
    at com.sun.faces.util.MessageFactory.getApplication(MessageFactory.java:280)
    Truncated. see log file for complete stacktrace
    >
    <Apr 11, 2011 3:14:21 PM PDT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'TestApplication'.
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.NullPointerException
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.<init>(UnifiedRenderKit.java:129)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKit.createRenderKit(UnifiedRenderKit.java:111)
    at oracle.adfinternal.view.faces.unified.renderkit.UnifiedRenderKitFactory.getRenderKit(UnifiedRenderKitFactory.java:59)
    at org.apache.myfaces.trinidadinternal.renderkit.CoreRenderKitFactory.getRenderKit(CoreRenderKitFactory.java:55)
    at com.sun.faces.config.processor.RenderKitConfigProcessor.addRenderKits(RenderKitConfigProcessor.java:236)
    Truncated. see log file for complete stacktrace
    >

  • Steps to upgrade HFM (EPMA) from 11.1.1.3 to 11.1.2.1/11.1.2.2

    Hi,
    Can someone please let me know how to upgrade the EPM-HFM application in 2/3 steps.
    I know how to upgrade if it is classis application just by upgrading the database in EPM System Configurator.
    What happens or need to be done if it was built in EPMA? Just upgrade schemas of both EPMA & HFM in Configurator?
    Any pointers are appreciated!
    Thanks in advance,
    PM

    Please post this to the HFM Discussion Forum, this is the FDM Discussion Forum.

  • HFM 11.1.2.1 to 11.1.2.2 upgrade - applications not visible in workspace

    Hi Gurus,
                        Recently upgraded HFM system in distributed environment from version 11.1.2.1 to 11.1.2.2 on MS Win 2008 R2 platform and Oracle 11g database. There are two servers as follows:
    Machine 1:     Foundation
                           Reporting
                           Workspace
                            HFM Web
    Machine 2: Foundation common components
                       HFM
                       FDM
    Applied maintenance release, configured existing databases for individual components and deployed to application server on existing domain (on Machine 1 WebLogic) which went fine. Lastly configured web server on Foundation (Machine 1 - Oracle HTTP). Then executed the HFM schema upgrade utility.
    Workspace & shared services are working fine, HFM apps are appearing in shared services, hfm text appears using hfm url, services are running fine. Issue is that HFM applications do not show up on workspace.
    Oracle support suggested applying adf patches, HFM 303 & 305 patches, but the problem remains even after applying all the suggested patches. Is this a bug in 11.1.2.2? Please help.
    Thanks,
    Hamminder

    Hi Hamm,
    The fact that you are saying that "hfm text appears using hfm url" can mean that you have not configured the workspace web server after you configured the HFM. Have you done that?
    As another test, have you tried toy connect to HFM via smartview to an existing app?
    Regards,
    Thanos

  • DCOM Component Not Found after Essbase Adapter Configured for FDM 11.1.2.2

    We are migrating FDM from version 11.1.1.3 to 11.1.2.2 following the official guide.
    After schema update, we can log in to the FDM Workbench fine, but we are having trouble when upgrading Essbase adapter.
    The existing adapter is outdated (for Essbase 11.1.1.3), and we followed the document to import, register, configure new Essbase adapter.
    However, after machine profile, adapter options (which application to connect and so on) are set, we tried to configure dimension mappings.
    In the "Target Dimension" field in the "Dimension" tab of adapter configuration window, it only shows "Connection failed." in the drop down list.
    Then we discovered that we need 32-bit Essbase Runtime client after reading an Oracle KM Article, then we copied it from Essbase server and set the environment variables.
    After doing so, and register the adapter again, now the dimension is shown in the pop-up window when configuring dimension of the Essbase adapter.
    The progress of our FDM adapter registration:
    1. Import the adapter ES11X-G4-J.xml in FDM workbench.
    2. Put the upsES11XG4J.exe file under <EPM_Oracle_Home>\common\EssbaseRTC\bin
    3. Create a system environment variable ESSBASEPATH with value "<EPM_Oracle_Home>\common\EssbaseRTC\11.1.2.0" and add following value to PATH environment variable: "<EPM_Oracle_Home>\bin-32; %ESSBASEPATH%\bin; <EPM_Oracle_Home>\products\Essbase\EssbaseClient-32\bin", where the <EPM_Oracle_Home> resemble our EPM location.
    4. Register the adapter from "File -> Register Adapter" in workbench and select the upsES11XG4J.exe file.
    5. Executed "Run -> dcomcnfg" trying to update the launching user right for corresponding DCOM component (upsES11XG4J.cluHypWindowEB) but could not find it there.
    Does anyone encountered this situation before?

    Thanks Jeff.
    Sorry I didn't notice your reply here, since Oracle Support has answered that for Windows Server 2008 R2, this step is no longer needed when configuring FDM Essbase Adapter. That's sweet.
    Warm Regards,
    John

Maybe you are looking for