Wednesday 3 August 2016

[SOLVED] [Error] Deployer :Failed to initialize the application 'oraclediagent' due to error weblogic.application.ModuleException: Failed to load webapp: 'oraclediagent'.

Error: After implementing high availability in OBIEE when started, biserver_2 state changed to Admin.

error:

"<Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oraclediagent' due to error weblogic.application.ModuleException: Failed to load webapp: 'oraclediagent'."


Cause:
In our environment we have total 3 managed servers

  • bi_server1
  • bi_server2
  • odi_server1
and all the servers are deployed in bi_cluster. As we have bi_server2 is in different machine and only we are going for scale out of bi system, ODI related files will not be there in machine 2.

But when starting bi_server2 it tries to load odi related files also because odi and bi_server is hosted in bi_cluser.

Solution:
 
 Below mentioned applications are trying to deploy in bi_cluser.


/home/oracle/MWHome/Oracle_ODI1/setup/manual/oracledi-agent/oracle.odi-agent_11.1.1.jar 
/home/oracle/MWHome/Oracle_ODI1/setup/manual/oracledi-sdk/oracle.odi-sdk_11.1.1.jar 
/home/oracle/MWHome/Oracle_ODI1/setup/manual/oracledi-metadata-navigator/odiconsole.ear 
/home/oracle/MWHome/Oracle_ODI1/setup/manual/oracledi-agent/oraclediagent.ear 

So edit the config.xml file and manually edit the target for the above applications from bi_cluster to bi_server1,odi_server1,AdminServer so the applications will not try to deploy in bi_server2.

Eg of the config file.

"<library>
    <name>oracle.odi-sdk#11.1.1.5.0@11.1.1.5.0.1</name>
    <target>bi_server1,odi_server1,AdminServer</target>
    <module-type>jar</module-type>
    <source-path>/home/oracle/MWHome/Oracle_ODI1/setup/manual/oracledi-sdk/oracle.odi-sdk_11.1.1.jar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
  </library>"

No comments:

Post a Comment