1 Reply Latest reply on Oct 7, 2013 10:22 PM by Ayush Ganeriwal-Oracle

    odiconsole deployment fails


                          Hi there,


        I need your help in configuring my ODI J2EE agent on our FUSION R8 provisioned instance.



      The below are steps I have followed to configure ODIJ2EE agent however this deployment was never successful and I had experienced various mix and match error combinations.  Now I redid the below steps as it is and currently odiconsole has failed on 8001 port and oraclediagent was successful.  I need your help in triaging this further. 




      We have to manually perform the following steps, once for each domain that is created. This is required for most of the j2ee apps like ODI AGENT, ODICONSOLE, ODI-ESS etc

      1. 1. Verify APPID credentials in credential store:

      1. 2.  Check the JPS Config file

      Check the JPS domain configuration <domain_home>/config/fmwconfig/jps-config.xml and ensure that the default jpscontext has a "credstore"


              <serviceInstance name="credstore" provider="credstoressp" location="./">

                  <description>File Based Credential Store Service Instance</description>



              <jpsContext name="default">

                  <serviceInstanceRef ref="credstore"/>*

                  <serviceInstanceRef ref="policystore.xml"/>

                  <serviceInstanceRef ref="idstore.oid" />

                  <serviceInstanceRef ref="idstore.loginmodule" />



      1. 3. When ODI is deployed in Fusion Applications environment, the credential map name for various ODI AppIDs is pre-defined in Fusion Apps by the Fusion Apps provisioning.  Currently ODI uses a credential map name that is hardcoded to oracle.odi.credmap name.  For Fusion Apps environment, the credential map name is oracle.apps.security. So we need to provide a solution so that in Fusion Apps environment, a different credential map name can be specified and used.ODI runtime uses credential store for ODI JEE Agent, ODI Console, ODI-ESS bridge. The Fusion Apps credential map name for all ODI usecases is: oracle.apps.security In the set of instructions for provisioning ODI for Fusion Applications, a step needs to be added after ODI installation and before creating and deploying ODI JEE Agent and ODI Console.$ODI_HOME/common/bin/updateCredMapinEar.[sh| This script changes the default credential map name to oracle.apps.security, as follows:

      Cd .$ODI_HOME/common/bin

      ./updateCredMapInEar.sh -MAPNAME=oracle.apps.security

      This step regenerates ODI Console and ODI Agent EAR files 


      $ ODI_ORACLE_HOME /setup/manual/oracledi-metadata-navigator/odiconsole.ear

      1. 4. Create ODI J2EE Agent WLS Template

      cd $ODI_ORACLE_HOME/common/bin

      ./generate_agent_wls_template.sh <Agent Name> <Agent Context> <Credential Key> <template file location> <create ODI master repository jdbc data source true/false> <ODI master repository jdbc data source name> <jdbc url> <master repository schema name>

      1. 5. Update ODI repository information in $DOMAIN_HOME/config/oracledi/repositories.xml. Below example illustrates PSFT FSCM configuration.
      2. “FUSION_APPS_MIG_ODI_EBS_SUPER_APPID-KEY”  is used to stored ODI supervisor credential
      3. ODI master repositories JDBC name is “jdbc/odiMasterRepository”
      4. ODI work repositories JDBC name is “jdbc/odiWorkRepository”

      <repository id="Work Repository" standard="false" default="true" supervisorUserKey=" FUSION_APPS_MIG_ODI_EBS_SUPER_APPID-KEY ">

          <master url="jdbc/odiMasterRepository"/>

          <work url="jdbc/odiWorkRepository"/>


      <repository id="Master Repository" standard="false"  supervisorUserKey=" FUSION_APPS_MIG_ODI_EBS_SUPER_APPID-KEY">

             <master url="jdbc/odiMasterRepository"/>


      1. 6. Deploy ODI J2EE Agent App & Console
      2. Run WebLogic Middleware Configuration Wizard and choose the option of “Extend my domain using an existing application template”
      3. Extend the Domain with the above template generated:
      4. Select the Migration Domain directory:
      5. Select the ODI Agent WLS template generated from the previously step, for example, /tmp/Migration-ODI-Template.jar  or /scratch/Migration-ODI-Template.jar 
      6. Test the connections for ODI schemas (optional)
      7. Select Managed Services & deployment services
      8. Select the unique port for odi_server1, 8001 is the default port, if this port has been used by other server, please give some other one.
      9. Ignore the cluster section as we are configuring single server
      10. Select the Admin server & odi_server1 to deploy the ODI applications
      11. Select oraclediagent & odiconsole under odi_server1
      12. Select JDBC datasources odiMasterRepository & odiWorkRepository under AdminServer & odi_server1
      13. Extend the domain
      14. 7. Start up odi_server1 WLS Managed Server.  Both ODI Console and ODI agent should be running.

      If the agent is successful, we should see like this in web browser:

      http://<host>:8001/oraclediagent  will show the below message in a browser.

      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

      <Ping xmlns="xmlns.oracle.com/odi/OdiAgentMessages/V11" />

      Creating the Physical Agent:

      1. Start the Studio using the following command: <ODI_ORACLE_HOME>/oracledi/client/odi.sh
      2. Connect to the Master/Work Repository, go to the Topology Navigator, and create a new Physical Agent
      3. Name: OracleDiAgent
      4. Host: Host name of the managed server (simple domain) or proxy server (cluster)
      5. Port: Port of the managed server (simple domain) or proxy server (cluster)
      6. Web Application Context: oraclediagent

      Click Test to check your agent

      1. 9. Creating the logical Agent:

      Go to Logical architecture, right click on Agent , Create Logical agent & assign it to Physical agent.

      10 Restart Managed Servers:

      1. 1. Shut down odi_server1 WLS Managed Server.
      2. 11.  Now goto ODI studio , select OracleDiagent under Agents -> Test.  It should be successful.

      any help on this would be of great help.  There were multiple java errors found in log some one please let me know if the detailed log is needed to triage further