Application-wide "env-entry"

Hi,
I'm creating a J2ee application using various EJB's and at least one WAR, all inside one single EAR file.
This app. is to be intalled at different clients. I'd like to be able to specify different properties ( server used, remote host addresses, etc.) in some part of the EAR that will be available using
(String)context.lookup("java:comp/env/" + name );
I have been able to customize individual EJB's using the <env-entry> tag in its DD but what about the being able to customize the whole application??
I'm been scouring docs and the net and I can't see any specific application.wide examples.
Many thanks for your help.
Terry Doyle

I faced the same problem some time ago. I went through the EJB 2.0 spec and the DTD of ejb-jar.xml. It appears that env-entry is for an EJB only. There is no 'global' env-entry.

Similar Messages

Env-entry-mapping in orion-application-client not available in JNDI lookup

I have an application client module in my EAR file that I've configured to auto-start.
It has a few env-entry defined in it's application-client.xml.
When I deploy the EAR file to OC4J 10.1.3, the application client module gets started and can access these env-entry properties from its JNDIContext.
Now, comes the problem. During the deployment process, I edit the Deployment Plan, and change the env-entry property values, and then deploy the application.
However, the application client module still gets the original values when it does the JNDI lookups of those env-entry names.
I have checked to see that OC4J creates an orion-application-client.xml during deployment and it shows the env-entry-mapping elements with the updated values.
Why is the JNDI lookup returning the values from application-client.xml and not the overriden values set in orion-application-client.xml?
I have tried this on OC4J 10.1.3, as well as 10.1.3.1.0 - got same behavior.
Is this a bug in OC4J? This seems to work fine with ejb modules, but not application client modules.
Thanks,
Kalpak

Avi!
Of course, I had tried it before I wrote the question. I put the modified xml file into the application area. After that AS restarts OC4J instance. And then I find my xml without any changes I made! I tried to do the same thing from the AS console. The same!
Leonid

Trailing spaces in env-entry-type elements

Hi,
We have been porting our EJB application from another app server over to Oracle iAS (9.0.3 Lite) and have encountered a rather frustrating problem.
We have an CMP (2.x) entity bean that has ejbSelect methods. There are corresponding <query> blocks in the ejb-jar.xml file for these methods. In the same ejb-jar.xml file there are <env-entry> blocks that setup a few things that are needed by the bean.
If the <env-entry-type> element is written as "<env-entry-type>java.lang.String </env-entry-type>" (note the trailing space after the type name) the following exception occurs during deployment of the ear file;
java.lang.InstantiationException: Failure to initialize EJBQL descriptors: com.sun.enterprise.deployment.xml.ContentTransformationException: java.lang.String is not an allowed property value type
     at com.evermind.server.ejb.deployment.EJBPackage.initializeEjbqlDescriptors(EJBPackage.java:2075)
     at com.evermind.server.ejb.deployment.EJBPackage.init(EJBPackage.java:2054)
     at com.evermind.server.ServerComponent.init(ServerComponent.java:208)
     at com.evermind.server.ejb.EJBPackageDeployment.getPackage(EJBPackageDeployment.java:672)
     at com.evermind.server.administration.ServerApplicationInstallation.finish(ServerApplicationInstallation.java:547)
     at com.evermind.server.administration.ServerApplicationInstallation.deploy(ServerApplicationInstallation.java:913)
     at com.evermind.server.administration.DefaultApplicationServerAdministrator.deploy(DefaultApplicationServerAdministrator.java:337)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:119)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
     at java.lang.Thread.run(Thread.java:479)
Error during deployment: Failure to initialize EJBQL descriptors: com.sun.enterprise.deployment.xml.ContentTransformationException: java.lang.String is not an allowed property value type
Removing the trailing space and the deployment proceeds to completion without exceptions.
I should also add that if the ejbSelect methods are remove d from the application and the trailing space left in place the resulting ear file will deploy sucessfully.
It is trivial to reproduce this problem with the ORMAP demo that ships with 9.0.3.
This was a really subtle problem that is not present on the *3* other appserver implementations that our application runs on. It was very frustrating to locate and perhaps some consideration could be given to how PCDATA is handled when parsing <env-entry-type> blocks.
Cheers,
Mick.

Hi ,
Create two Characteristic InfoObjects in BW With length 60 Char and then in the Transfer Rules of this two InfoObjects write the Formula using Left() and right() function present in the Formula Builder .
That is First infoObject Contains the Left 60 Char and next one Contains the right 60 Char.
Regards,
Vijay.

Query Reg env-entry in ejb jar xml

Hi,
I have the following tag in the ejb-jar of my application:
<env-entry>
<env-entry-name>postingDate</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>Request</env-entry-value>
</env-entry>
When a JNDI LookUp is done for this variable in the application, it doesn't pick up the value of the variable which is "Request" but it picks up the Value of the Posting Date.
I need to know how this works!
Just an Fyi, Posting Date is a date entered from the UI.

I feel it is like declaring global and local variables with the same name and trying to access that variable.

Issue with [env-entry] element in web.xml

I know it's possible to define [env-entry] elements in web.xml for environment
properties of a web application. But how do you access [env-entry] elements from
classes that do not exist within a web application? In other words, this is my
problem:
I have an EAR file, enterprise.ear, which contains the following...
employee.jar
employeeSearchEJB.jar
webApp1.war
META-INF/
application.xml
The employee.jar file is a utility archive that contains common classes, one of
which is a class called LogManager. LogManager needs to read environment properties
in order to initialize itself. Currently, LogManager reads these properties from
a property file, and therefore it needs to know the name of the property file
in order to access it. I dont like this approach because I'm forced to hard-code
the name of the property file in LogManager. I would rather leverage the power
of J2EE deployment descriptors and use the [env-entry] element to define the environment
properties for the LogManager class. Then, I would simply use JNDI to get the
values of the [env-entry] elements without ever having to specify their location
aside from the default JNDI context; java:comp/env, which is standard anyway.
The problem I'm having is that you can define the [env-entry] element in only
2 types of deployment descriptors; namely, web.xml and ejb-jar.xml, neither of
which are available to LogManager because LogManager exists at the EAR root level.
I was hoping application.xml supported the [env-entry] element, but it doesn't.
Any suggestions?
SAF

SAF,
I am not sure if this applies to you situation but if you create an initial context
instance and then grab the value using the jndi name within that context then
you should be able to grab that environment variable.
I have a helper class that is used as part of a deployed application. The helper
class doesn't have access to the Servlet context but it is created as part of
the application workflow. When it gets initiated it grabs an env-entry created
in the web.xml deployment descriptor to find the default url for a content path.
After I create an initialContext, I perform a initContext.lookup("jndi.env.entry.here")
where "jndi.env.entry.here" is the name specified in the env-entry tag.
This returns the value of the entry.
This works under both Jrun and Weblogic so my guess is it should work for you.
Again, I am assuming that your class will at least be able to grab a context
object to communicate back to the server.
Hope this helps,
Troy
"SAF" <[email protected]> wrote:
>
I know it's possible to define [env-entry] elements in web.xml for environment
properties of a web application. But how do you access [env-entry] elements
from
classes that do not exist within a web application? In other words, this
is my
problem:
I have an EAR file, enterprise.ear, which contains the following...
employee.jar
employeeSearchEJB.jar
webApp1.war
META-INF/
application.xml
The employee.jar file is a utility archive that contains common classes,
one of
which is a class called LogManager. LogManager needs to read environment
properties
in order to initialize itself. Currently, LogManager reads these properties
from
a property file, and therefore it needs to know the name of the property
file
in order to access it. I dont like this approach because I'm forced to
hard-code
the name of the property file in LogManager. I would rather leverage
the power
of J2EE deployment descriptors and use the [env-entry] element to define
the environment
properties for the LogManager class. Then, I would simply use JNDI to
get the
values of the [env-entry] elements without ever having to specify their
location
aside from the default JNDI context; java:comp/env, which is standard
anyway.
The problem I'm having is that you can define the [env-entry] element
in only
2 types of deployment descriptors; namely, web.xml and ejb-jar.xml, neither
of
which are available to LogManager because LogManager exists at the EAR
root level.
I was hoping application.xml supported the [env-entry] element, but it
doesn't.
Any suggestions?
SAF

Env-entry reachable from more than one bean

Is it possible to reach env-entries of one session-bean from another session-bean within same ejb-jar.xml?
Or is the only way to write them twice, once per each bean.

Greetings,
Is it possible to reach env-entries of one
session-bean from another session-bean within same
ejb-jar.xml?In theory, a JNDI namespace is hierarchical (a tree structure - like a filesystem) - and a server typically maintains a global namespace - so as long as your bean knows the lookup name of the entry it can be accessed regardless of the locality of the bean (ie. it may even exist in a separate application running on the same server!). However...
Or is the only way to write them twice, once per each
bean.The purpose of environment entries is to provide "post-compile time" customization to your beans and so ideally each bean should have it's own env-entries specific to it's needs. Additionally, depending on your vendor implementation private namespaces for env-entries might be provided and/or you may also get assembly/deployment errors for beans performing lookups against the namespace for which assembly mappings were not provided. In these cases you will have to devise a mechanism for the passing the env information between your beans (since the specification prohibits beans from modifying their runtime environments. ':-o ).
I hope this helpful.
Regards,
Tony "Vee Schade" Cook

Env-entry-mapping suppressed

Hi,
Did anyone try <env-entry-mapping> in orion-ejb-jar.xml? It seems that it is suppressed during deployment. The orion-ejb-jar.xml being generated into -deploymentDirectory place (specified or default) simply drops these mappings. The effect is that whatever had been specified in ejb-jar.xml prevails, with obvious, bad consequences.
Besides, I think I read somewhere that Deployer-supplied orion-ejb-jar.xml would only be augmented with missing specifications. This to me implies that nothing should be removed from it. Perhaps, then, THIS IS A BUG.
ORION TEAM: I'm running 9.0.3.0.0/NT. I'd appreciate your help and 'know-how', especially if you could offer something better than manually editing orion-ejb-jar.xml in -deploymentDirectory AFTER EACH SUCH TIME THE APPLICATION IS DEPLOYED!

Avi!
Of course, I had tried it before I wrote the question. I put the modified xml file into the application area. After that AS restarts OC4J instance. And then I find my xml without any changes I made! I tried to do the same thing from the AS console. The same!
Leonid

env-entry-mapping element is removed during deployment process

I overwrite the variable value defined in ejb-jar.xml by the one defined in orion-ejb-jar.xml using <env-entry-mapping> element. But after my appliocation has deployed I don't find this element in the application orion-ejb-jar.xml. Oracle AS just removes this element from the descriptor!
ejb-jar.xml:
<env-entry>
<env-entry-name>server</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>172.38.48.12</env-entry-value>
</env-entry>
orion-ejb-jar.xml:
<session-deployment name="Inventory" max-instances="-1" location="Inventory">
<env-entry-mapping name="server">dummy</env-entry-mapping>
</session-deployment>
Can anybode help?

Avi!
Of course, I had tried it before I wrote the question. I put the modified xml file into the application area. After that AS restarts OC4J instance. And then I find my xml without any changes I made! I tried to do the same thing from the AS console. The same!
Leonid

Global env-entry JNDI variables space for same ejb-jar.xml file

[Software]
jboss4.0.5
jdk 1.5
[Problem]
Is there any global <env-entry> tag for a Single EJB Module. Is there any way by which the JNDI variable can be accessed by all the modules except by binding the variables in the JNDI explixity in the code
Thanks in advance
CSJakharia

Unfortunately not. The EJB specification has always scoped the component environment
(java:comp/env) as a private environment for each EJB. The advantage is you can
assign entries within each bean easily without worrying about clashing with names selected
for other beans in the ejb-jar. That eases the process of assembling beans developed
separately into one ejb-jar since there is no possibility that their component environments
will clash.
However, the downside is just what you're pointing out, which is that in many cases
developers prefer to define a single dependency that is shared among all the
beans in the ejb module. That is the behavior of the component environment in a
web application.
We'll be looking into ways to simplify this for ejbs in a future revision of the specification.
--ken

Env-entry in web.xml and 6.0 sp4

Does anyone know if iws 6.0 sp4 supports env-entry elements in web.xml???
According to servlet specs 2.2 it should support it since it has JSP support.
From 2.3 specs:
"The following addtional elements exist in the web application deployment
descriptor to meet the requirements of web containers that are JSP enabled or part
of a J2EE application server. They are not required to be supported by containers
wishing to support only the servlet specification.:
� taglib
� syntax for looking up JNDI objects (env-entry, ejb-ref, ejb-local-ref, resourceref,
resource-env-ref)
See the DTD comments for further description of these elements."

Additional info...actually the code throws a NamingException.

Edit env-entry values from web.xml in the WLS console.

Hi guys!
Is it possible to define JNDI variables of type java.lang.String using WLS Console?
Thanks

I think this would require the use of a deployment plan, which you can learn about here: [http://e-docs.bea.com/wls/docs103/deployment/config.html] . This won't be as convenient as just editing the value directly in the admin console. In fact, it won't even prevent the requirement of redeploying the webapp. It will only allow you to make the change without rebuilding and repackaging the webapp.
It's questionable whether it's practical or meaningful to change env-entry values in a web.xml without redeployment, because even if you could change the values without redeploying, you'd have to reinitialize the servlet/filter with the changed environment parameter.
If you really need this dynamic reconfiguration ability, you might have to design the facility into your application, using some sort of polling or event handling capability.

Updated env-entries in web.xml

          We are using WLS 5.1 SP10.
          In a web-application we like to have some parameters (related to the webapp as
          a whole) which can easily be changed (without having to restart the server).
          What is the best way to do that?
          I was thinking of env-entries.
          But when I change them the web.xml is not reloaded and the changes have no affect.
          Is dynamic reload of web.xml possible under WLS5.1 SP10?
          When should env-entries be used, and when init-params?
          Init-params seems to be servlet(JSP) related, while the environment entries affect
          the web-app environment. Are there other elements to take in consideration?
          In the doc I found no real explanation of when to use what...
          Any help would be appreciated,
          Frederic
          Please send answers also to my e-mail: [email protected]


Hi,
these are only configurations and don't cause a harm or use resources. So I suggest to leave them in just in case yu need them later
Frank

Env-entry from web.xml not in generated plan.xml

Hello,
Recently I migrated a JDeveloper 10.1.3.4 project to 11.1.1.3 and from there to 11.1.2.4. When I deploy this project to an 10.3.5. weblogic server then the 'env-entry' entires in the web.xml are not available on the application server.
Even when i use weblogic.PlanGenerator with the -all option to create a plan.xml from the WAR-file the env-enties are not found.
The web.xml is like this:
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
id="WebApp_ID" version="2.5">
<listener>
<listener-class>com.sun.xml.ws.transport.http.servlet.WSServletContextListener</listener-class>
</listener>
<servlet>
<servlet-name>jaxrpc</servlet-name>
<servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>VersionServlet</servlet-name>
<servlet-class>nl.deltalloyd.alfa.keten.version.VersionServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>VersionServlet</servlet-name>
<url-pattern>/version</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>jaxrpc</servlet-name>
<url-pattern>/RelatieSoapHttpPort</url-pattern>
</servlet-mapping>
<jsp-config/>
<security-role>
<role-name>Administrators</role-name>
</security-role>
<resource-ref>
<res-ref-name>jdbc/AlfaDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<env-entry>
<env-entry-name>appl/version</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>2013.06</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>appl/releasedate</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>13-06-2013</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>appl/loglevel</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>INFO</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>appl/omgeving</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
<env-entry>
<env-entry-name>service/case</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>http://test.services.intranet.company.nl/GixoCaseWeb/services/CaseServiceHttp</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>mqueue/rc/host</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>nl001wwavm058.ad.intra</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>mqueue/rc/port</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>1414</env-entry-value>
</env-entry>
</web-app>
Maybe I missed something in the migration path. Can someone please help me.
With kind regard,
Martin

Let me describe my case in few more words...
I have some kind of client-server app. Clients have OC4J installed and they download myApp.ear and myApp_plan.dat files and by using script (Windows CMD batch file) clients install those files with admin_client.jar, OC4J's admin utility. The problem is that I have 2 different types of clients and I have client specific settings set in web.xml file and each time I compile myApp.ear I have to uncomment/comment some lines in web.xml.
So, to make a long story short, I need a way to deploy those settings separated from (outside of) myApp.ear. By following you link, I have read that orion-web.xml should reside inside WEB-INF folder of myApp.ear, which is not good for me.

SAXParseException in web.xml, not allowing the env-entry tag?????

          Dears, I have a WLS 5.1 sp6, and added a
          weblogic.httpd.webApp.demowar=/temp/alphaworks/servlet/demo_feat.war
          in weblogic.properties, and when I start the weblogic server occuring
          [ServletEntityResolver] : Could not resolve entity '-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN'. Check your
          dtd reference.
          ..<HTTP> Error parsing descriptor in Web application '/temp/alphaworks/servlet/demo_feat.war'
          org.xml.sax.SAXParseException: Element "web-app" does not allow "env-entry" here.
               at com.sun.xml.parser.Parser.error(Parser.java:2775)
          --------------- nested within: ------------------
          Received SAXParseException from Sun Parser at line 283, column -1: org.xml.sax.SAXParseException: Element "web-app" does not allow "env-entry" here.
               at weblogic.xml.dom.SunDOMParser.getDocument(SunDOMParser.java:72)
          Wed Dec 06 18:50:17 GMT-02:00 2000:<E> <HTTP> Error creating servlet context for Web application '/temp/alphaworks/servlet/demo_feat.war'
          java.lang.NullPointerException
               at weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java:626)
          any other default servlet (that comes with weblogic) works fine, and this .war runs good in
          Orion 1.4.4, adn J2EE RI 1.2.1 !
          in web.xml the dtd is from java.sun.com, and I chaged to http://localhost/servlet_2_2.dtd (where the url is fine, because I can download).


Double-check the DTD. WebLogic likes the XML to be in the same exact order
          as found in the DTD.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com
          +1.617.623.5782
          WebLogic Consulting Available
          "Claudio" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Dears, I have a WLS 5.1 sp6, and added a
          >
          > weblogic.httpd.webApp.demowar=/temp/alphaworks/servlet/demo_feat.war
          >
          > in weblogic.properties, and when I start the weblogic server occuring
          >
          > [ServletEntityResolver] : Could not resolve entity '-//Sun Microsystems,
          Inc.//DTD Web Application 2.2//EN'. Check your
          > dtd reference.
          >
          > ..<HTTP> Error parsing descriptor in Web application
          '/temp/alphaworks/servlet/demo_feat.war'
          > org.xml.sax.SAXParseException: Element "web-app" does not allow
          "env-entry" here.
          > at com.sun.xml.parser.Parser.error(Parser.java:2775)
          > .
          > .
          > .
          >
          > --------------- nested within: ------------------
          > Received SAXParseException from Sun Parser at line 283, column -1:
          org.xml.sax.SAXParseException: Element "web-app" does not allow "env-entry"
          here.
          > at weblogic.xml.dom.SunDOMParser.getDocument(SunDOMParser.java:72)
          > .
          > .
          > .
          >
          > Wed Dec 06 18:50:17 GMT-02:00 2000:<E> <HTTP> Error creating servlet
          context for Web application '/temp/alphaworks/servlet/demo_feat.war'
          > java.lang.NullPointerException
          > at weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java:626)
          >
          > any other default servlet (that comes with weblogic) works fine, and this
          .war runs good in
          > Orion 1.4.4, adn J2EE RI 1.2.1 !
          >
          > in web.xml the dtd is from java.sun.com, and I chaged to
          http://localhost/servlet_2_2.dtd (where the url is fine, because I can
          download).
          >
          >

How to retrieve "env-entry" in servlet code

i have a pretty straight-forward web app, which contains a servlet, among other things. the web app is packaged in .war, and it in turn is part of a .ear file. i am using WAS 640 sneak preview on windows xp.
in the web.xml file, i added the following lines:
<env-entry>
<description>some texts</description>
<env-entry-name>myapp.home</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>c:/myapp</env-entry-value>
</env-entry>
in my servlet code, i try to retrieve the value for "myapp.home" like this:
try
Context ctx = new InitialContext();
home = (String) ctx.lookup("java:comp/env/myapp.home");
} catch (Exception ex) {
ex.printStackTrace();
after .ear is deployed, i can see in the JDNI Registry (using Visual Admin Tool), myapp.home is added to the tree:
webContainer
-applications
--myCompany.com
---myEarFileName
myWebAppRoot
java:comp
env
myapp.home
the entry has the correct class name and object value.
when the servlet code that performs the jndi lookup is called, i get an exception:
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at : java:comp
??? QUESTIONS:
#1 what am i doing wrong?
#2 if the lookup name must contain the entire jndi tree as listed above, then how can this code be portable to other app servers?
thoughts are greatly appreciated.

thanks for the hints, but unfortunately they didn't work.
1. after switching the order of value and type in env-entry, rebuild/redeplpoy, same exception. the ordering probably didn't matter since even with the reversed order, the name and value showed up correctly under the jndi tree.
2. well, i tried giving it the full path, starting with 'webContainer', then 'applications' etc, separated by forward slash. now the exception says path to webContainer is not found.
so what gives? are there no standards?

Application-wide "env-entry"

Similar Messages

Maybe you are looking for