OdiStartScen always using "OracleDIAgent" physical agent (ODI-17554)

Question

Hi. I received an ODI package (A) which contains an invocation to other ODI package (B) through an OdiStartScen call in the flow diagram.
The OdiStartScen call doesn't set the context nor the agent codes (just set the scene name, the version as -1 and the invocation mode as asynchronous).
In my topology, I have three physical agents: OracleDIAgent (for "Production" context), OracleDIAgent_T (for "Test" context) and OracleDIAgent_D (for "Development" context). I have just one logical agent which choose between the physical ones through the context distribution previously described.
If I execute the "parent" package (A), it doesn't matter if a choose whatever context (for example, "Development" or "Test"), the OdiStartScen call to package (B) always is routed to the "OracleDIAgent" physical agent (the "Production" one).
Moreover, if I delete all my agents (specially "OracleDIAgent"), create just the ones which correspond to "Development" (the physical OracleDIAgent_D and the logical one) and execute the "parent" package, I receive the following error when the execution reaches the OdiStartScen call:
ODI-1426: Agent OracleDIAgent is not defined in the topology for the master repository.
Caused By: com.sunopsis.core.SnpsInexistantObjectException: ODI-17554: Agent "OracleDIAgent" does not exist.
I'm confused.
Any help in clarifying this behaviour would be much appreciated.
Notes:
- the agent which first receive the execution order (for package A) is an Java EE Agent (WebLogic 11g)
- the project comes from 11.1.1.5 and now is deployed on a 11.1.1.6 through export/import.
Thanks,
Esteban

Answer 1

Hi Phanikanth, actdi, thank you for your answers.
It seem the cause is one missing step in the Java EE Agent WebLogic domain creation. According the "Fusion Middleware Installation Guide for Oracle Data Integrator" [1], the default Java EE agent created from the static WebLogic template is called "OracleDIAgent"; if you want to use another name, you have to create a new template from ODI Studio and use it to create the Java EE Agent domain. In our case, all the Java EE Agents were created using the default template.
[1]
http://docs.oracle.com/cd/E23943_01/core.1111/e16453/configure.htm
3.3 Configuring Java EE Components
3.3.1 Declaring the Java EE Agent in Topology