A problem determining the JNDI Name of a local EJB with WL 8.1

Hi,
I created a very simple local EJB and deployed it with Weblogic8.1. When I test
it in the Weblogic server admin page, I got the following message:
"The EJB MyLocal has not been tested successfully. There was a problem determining
the JNDI Name of the given bean."
Can anyone help figure out the problem?
Thanks
Henry

Does the ejb have a target server specified?
Does the Ejb have a Jndi binding as specified in the <local-jndi-name></local-jndi-name>
element of weblogic-ejb-jar.xml?
thanks,
Deepak
"Henry" <[email protected]> wrote:
>
>
Hi,
I created a very simple local EJB and deployed it with Weblogic8.1. When
I test
it in the Weblogic server admin page, I got the following message:
"The EJB MyLocal has not been tested successfully. There was a problem
determining
the JNDI Name of the given bean."
Can anyone help figure out the problem?
Thanks
Henry

Similar Messages

WLS10.3.1 : How to overload the jndi name of a stateless EJB

Hi,
I am trying to overload the jndi name of a stateless bean defined in an application by using a weblogic-ejb-jar.xml descriptor file.
This does not work.
The ear contains a jar that have a weblogic-ejb-jar.xml file in its META-INF directory. The file is :
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>HelloWorldBean</ejb-name>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>TOTO</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
This is the code of my bean :
package test;
import javax.ejb.Local;
import javax.ejb.Remote;
import javax.ejb.Stateless;
@Stateless( name = "HelloWorldBean", mappedName="HWBean")
@Local( IHelloWorldLocal.class)
@Remote( IHelloWorldRemote.class)
public class HelloWorldBean implements IHelloWorldLocal, IHelloWorldRemote
public void sayHello(String name) {
System.out.println( "Hello " + name + "!!!!");
The bean implements the following interfaces :
package test;
public interface IHelloWorldRemote extends IHelloWorld {
package test;
public interface IHelloWorldLocal extends IHelloWorld {
package test;
public interface IHelloWorld {
public void sayHello( String name);
When i browse the JNDI tree, i see the bean registered with the mapped name attribute (HWBean#test.IHelloWorldRemote) but i don't see any bean registered with the name provided by the weblogic-ejb-jar.xml (TOTO)
My standalone client can't perform a lookup using the JNDI name 'TOTO' but reaches the bean when using 'HWBean#test.IHelloWorldRemote'
It seem's that the overload of the Jndi name using the weblogic-ejb-jar file descriptor doesn't work.
Can you help me to solve the problem.
Thanks.

Thank you, my sample works fine with the following weblogic-ejb-jar.xml :
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>HelloWorldBean</ejb-name>
<enable-call-by-reference>true</enable-call-by-reference>
<stateless-session-descriptor>
<business-interface-jndi-name-map>
<business-remote>test.IHelloWorldRemote</business-remote>
<jndi-name>TOTO</jndi-name>
</business-interface-jndi-name-map>
</stateless-session-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>

Determining the BFile name

I was going through Steve Muench's book titled: "Building Oracle XML applications" and i was trying to refer to the file claim77804.xml in the xml directory which i created. I followed the book and i typed in the following code and the error came up:
SQL> SELECT DBMS_LOB.getLenght ( BFileName ('XMLFILES', 'claim77804.xml
2 AS length
3 FROM dual;
SELECT DBMS_LOB.getLenght ( BFileName ('XMLFILES', 'claim77804.xml'))
ERROR at line 1:
ORA-00904: invalid column name
I was working on CLOBs and i created the basic CLOB table:
CREATE TABLE xml_documents (
docname VARCHAR2(200) PRIMARY KEY,
xmldoc CLOB,
timestamp DATE
This worked fine but when i tried adding a database trigger, the following happened:
SQL> CREATE TRIGGER xml_documents_timestamp
2 BEFORE INSERT OR UPDATE ON xml_documents
3 FOR EACH ROW
4 BEGIN
5 :new.timestamp := SYSDATE;
6 END;
7
8
9
10
The numbers just keep coming. I have installed the PL/SQL XDK which includes the XMldom and XMLParser etc.
Thanks for your cooperation

Is it using a local interface and NOT a remote interface? I found that local interfaces
were not found even though they appear in the list of EJB jndi names.
Matthew Summers <[email protected]> wrote:
I'm using JBuilder9's EJB Designer to create CMP Entity Beans. After
successful deployment to WLS8.1, I use the mydomain> EJB Deployments>
myEJB>Testing>Test This EJB tool, I get the following error:
"The EJB myEJB has not been tested successfully. There was a problem
determining the JNDI Name of the given bean."
I didn't have this issue when I was running WLS7.1. I'm not doing
anything differently in JBuilder9 than when I was running WLS7.1.
Any Ideas? Help? Please?

The DataSource with the JNDI name: MyDataSource could not be located.

hi,
I created a connection pool myconnectionpool and i create a data source MyDataSource with jndi name as mydsn.
in my weblogic-cmp-rdbms-jar.xml i gave
<data-source-name>MyDataSource</data-source-name> and
When i deploy the bean i am getting following exception.
Unable to deploy EJB: containerManaged from cmp7.jar:
weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: MyDataSource could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:128)
     at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:213)
     at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:185)
     at weblogic.ejb20.manager.DBManager.setup(DBManager.java:160)
     at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:928)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1216)
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:850)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:70)
     at weblogic.j2ee.Application.addComponent(Application.java:253)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:144)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:301)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:255)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:206)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:716)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:698)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:380)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:902)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:480)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:208)
     at $Proxy34.updateDeployments(Unknown Source)
     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:3724)
     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1584)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:337)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:233)
     at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:61)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:852)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:273)
     at weblogic.Server.main(Server.java:33)
Where i went wrong?
Thanks in advance
phani

Hi ,
I have the same problem .when i look into JNDI tree view the jndi name is listed. but it saying error below listed.
my
ejb-name:=containerManaged
datasourcename=EX_DataSource
jndi-name=EX_JNDI
<Feb 14, 2005 3:10:08 PM IST> <Error> <Deployer> <149231> <The slave deployer was unable to set the activatio
true for the application EX_Container
weblogic.management.ApplicationException: activate failed forEX_Container
Module Name: EX_Container, Error: Exception activating module: EJBModule(EX_Container,status=PREPARED)
Unable to deploy EJB: containerManaged from EX_Container.jar:
The DataSource with the JNDI name: EX_DataSource could not be located. Please ensure that the DataSource has
ed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
TargetException:
Unable to deploy EJB: containerManaged from EX_Container.jar:
The DataSource with the JNDI name: EX_DataSource could not be located. Please ensure that the DataSource has
ed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1093)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1022)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLife
ava:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:65)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
at weblogic.Server.main(Server.java:32)
my weblogic-ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN'
'http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>containerManaged</ejb-name>
<entity-descriptor>
<persistence>
     <persistence-use>
     <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
     <type-version>7.0</type-version>
     <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
     </persistence-use>
</persistence>
</entity-descriptor>
<jndi-name>EX_JNDI</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
<?xml version="1.0"?>
<!DOCTYPE weblogic-rdbms-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB RDBMS Persistence//EN'
'http://www.bea.com/servers/wls700/dtd/weblogic-rdbms20-persistence-700.dtd'>
weblogic-cmp-rdbms-jar.xml file
<weblogic-rdbms-jar>
<weblogic-rdbms-bean>
<ejb-name>containerManaged</ejb-name>
<data-source-name>EX_DataSource</data-source-name>
<table-map>
<table-name>ejbAccounts</table-name>
<field-map>
<cmp-field>accountId</cmp-field>
<dbms-column>id</dbms-column>
</field-map>
<field-map>
<cmp-field>balance</cmp-field>
<dbms-column>bal</dbms-column>
</field-map>
<field-map>
<cmp-field>accountType</cmp-field>
<dbms-column>type</dbms-column>
</field-map>
</table-map>
</weblogic-rdbms-bean>
<create-default-dbms-tables>DropAndCreateAlways</create-default-dbms-tables>
</weblogic-rdbms-jar>
ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>containerManaged</ejb-name>
<home>containerBN.EX.AccountHome</home>
<remote>containerBN.EX.Account</remote>
<ejb-class>containerBN.EX.AccountBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>AccountBean</abstract-schema-name>
<cmp-field>
<field-name>accountId</field-name>
</cmp-field>
<cmp-field>
<field-name>balance</field-name>
</cmp-field>
<cmp-field>
<field-name>accountType</field-name>
</cmp-field>
<primkey-field>accountId</primkey-field>
<query>
<query-method>
<method-name>findBigAccounts</method-name>
<method-params>
<method-param>double</method-param>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.balance > ?1]]>
</ejb-ql>
</query>
<query>
<query-method>
<method-name>findAccount</method-name>
<method-params>
<method-param>double</method-param>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.balance = ?1]]>
</ejb-ql>
</query>
<query>
<query-method>
<method-name>findNullAccounts</method-name>
<method-params>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.accountType IS NULL]]>
</ejb-ql>
</query>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>containerManaged</ejb-name>
     <method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
<ejb-client-jar>EX_Container.jar</ejb-client-jar>
</ejb-jar>
pls lhelp me .
my email id: [email protected]
thanks in advance.
Sudhakar.M

JDBC Datasource creation via ANT doesn't expose the JNDI name

I'm using the wlconfig ANT task to create a Datasource (& JDBC connectionpool) on the weblogic server. The datasource is created fine, and I can test it using the console.
The problem is that the provided JNDI name isn't exposed in the JNDI tree. This seems to be related to the fact that the following element is generated in the config/jdbc/CP-PoolName-2164-jdbc.xml
<jdbc-data-source>
<name>PoolName</name>
<internal-properties>
*<property>*
*<name>LegacyType</name>*
*<value>1</value>*
*</property>*
When removing the LegacyType 1 property from the JDBC config xml, the JNDI name is exposed fine.
I've used the instructions located at [http://edocs.bea.com/wls/docs100/programming/ant_tasks.html] where an example of a JDBCConnectionPool creation is provided.
The 10.3 documentation doesn't include the example anymore, but I'm having the problem both on BEA Weblogic 10.0 and Oracle Weblogic 10.3
<wlconfig url="t3://localhost:7001" username="weblogic" password="weblogic">
bq. <query domain="base_domain" type="Server" name="AdminServer" property="adminserver"/>
bq. <create type="JDBCConnectionPool" name="MediumSecureOnlineNode1Pool" property="customPool1">
bq. bq. <set attribute="CapacityIncrement" value="1"/> \\ <set attribute="DriverName" value="oracle.jdbc.OracleDriver"/> \\ <set attribute="InitialCapacity" value="1"/> \\ <set attribute="MaxCapacity" value="10"/> \\ <set attribute="Password" value="pass"/> \\ <set attribute="Properties" value="user=username"/> \\ <set attribute="RefreshMinutes" value="0"/> \\ <set attribute="ShrinkPeriodMinutes" value="15"/> \\ <set attribute="ShrinkingEnabled" value="true"/> \\ <set attribute="TestConnectionsOnCreate" value="true"/> \\ <set attribute="TestConnectionsOnRelease" value="true"/> \\ <set attribute="TestConnectionsOnReserve" value="true"/> \\ <set attribute="TestTableName" value="SQL SELECT 1 FROM DUAL"/> \\ <set attribute="URL" value="jdbc:oracle:thin:@localhost:1521"/> \\ <set attribute="Targets" value="${adminserver}"/>
</create>
As we would like to automate the process of configuring our weblogic instances using ANT, is there a way to create JDBC datasources that don't have the LegacyType 1 element included in the config ?

Curious if you were ever able to find a resolution to this issue?
I am facing the same thing now with our Ant scripts and WL10.3 connection pools/datasources.
I would like to either specify a different LegacyType or suppress it altogether. Any help would be appreciated.
Many thanks,
Steve

Unable to bind EJB Home Interface to the JNDI name

Why do I get this error?? What is the jndi-name in weblogic-ejb-jar.xml
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
Unable to bind EJB Home Interface to the JNDI name:
com.sempire.builder.business
_component.Organization. The error was:
javax.naming.NameAlreadyBoundException: Organization is already bound;
remaining
name 'com.sempire.builder.business_component'
<<no stack trace available>>

Slava,
In case I change the name of the jndi name to a unique name. I still get the same
problem. I checked for multiple occurences, but there aren't any.
My web.xml file is:
<ejb-local-ref>
<description>
Reference EJB resources in Weblogic Resources
</description>
<ejb-ref-name>GangsterEJB</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>com.sempire.builder.business_component.GangsterHome</local-home>
<local>com.sempire.builder.business_component.Gangster</local>
</ejb-local-ref>
My weblogic-ejb-jar.xml file is:
<weblogic-enterprise-bean>
<ejb-name>GangsterEJB</ejb-name>
<entity-descriptor>
<persistence>
<persistence-type>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-type>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
</persistence-use>
</persistence>
</entity-descriptor>
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/GangsterDB</res-ref-name>
<jndi-name>oraclePool</jndi-name>
</resource-description>
</reference-descriptor>
<local-jndi-name>Gangster_test</local-jndi-name>
</weblogic-enterprise-bean>
I do not get the problem.
Thank you
Ronak Parekh
"Slava Imeshev" <[email protected]> wrote:
Hi Ronak,
This exception means that you already have a bean
with the same JNDI name. Search your weblogic-ejb-jar.xml files
for multiple occurrences of the name and fix the problem.
Regards,
Slava Imeshev
"Ronak Parekh" <[email protected]> wrote in message
news:[email protected]...
Why do I get this error?? What is the jndi-name in weblogic-ejb-jar.xml
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
Unable to bind EJB Home Interface to the JNDI name:
com.sempire.builder.business
_component.Organization. The error was:
javax.naming.NameAlreadyBoundException: Organization is already bound;
remaining
name 'com.sempire.builder.business_component'
<<no stack trace available>>

Error when determining the PSA name

I am on BW3.5, trying to load a delta that has been loading for 2+ years with no problems. The load today is getting the error message: "RSAODS 132 Error when determining the PSA name"
I've looked in OSS Notes and there is nothing with this error message. This is CCA Actual data that loads to PSA > ODS > Cube. The PSA load is red and the entry in the ODS is also red. Thanks

Hello Keith,
Not sure just check following, might help.
This might be because of insufficent authorization ( did you changed anything on authorization company wide decision?)
Or this might be brcause of insufficent tablespace or something?
Sarhan.

Error from ejbc: The JNDI name of bean

hi~
i have a problem .
to deploy , i did test bean like this..
java -classpath %CLASSPATH% -Dweblogic.home=%WL_HOME% weblogic.ejbc -compiler javac
old.jar new.jar
ERROR: Error from ejbc: The JNDI name of bean c was not set
ERROR: ejbc found errors
thank..^^
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN'
'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>c</ejb-name>
<home>c1.cHome</home>
<remote>c1.c</remote>
<ejb-class>c1.cEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>c</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

What's your weblogic-ejb-jar.xml file?
"oh ki sung" <[email protected]> wrote in message
news:3cc8499a$[email protected]..
>
hi~
i have a problem .
to deploy , i did test bean like this..
java -classpath %CLASSPATH% -Dweblogic.home=%WL_HOME%weblogic.ejbc -compiler javac
old.jar new.jar
ERROR: Error from ejbc: The JNDI name of bean c was not set
ERROR: ejbc found errors
thank..^^
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD EnterpriseJavaBeans 1.1//EN'
'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>c</ejb-name>
<home>c1.cHome</home>
<remote>c1.c</remote>
<ejb-class>c1.cEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>c</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

How can IC WebClient determine the host name for free seating?

Hi,
I want to determine the host name at CRM application server by ICI interface for free seating scenario.
There is a TCODE CRMM_IC_GFS to set 'Host Name Identification Applet'. But when I check on it, all buttions in IC Webclient disappeared. I followed the note 812399 to change Java security configuration, but the synptom still exist. Do anybody now how to? Thanks!
BR,
Hao

To run a public VPN server, you need to do the following:
1. Give the gateway either a static external address or a dynamic DNS name. The latter must be a DNS record on a public DNS registrar, not on the server itself. Also in the latter case, you must run a background process to keep the DNS record up to date when your IP address changes.
2. Give the VPN server a static address on the local network.
3. Forward external UDP ports 500, 1701, and 4500 (for L2TP) and TCP port 1723 (for PPTP) to the corresponding ports on the VPN server.
4. Configure any firewall in use to pass this traffic.

How to determine the Cluster name ?

Grid version : 11.2.0.3 on Solaris 10
When we start installing Grid Infrastructure, we specify a Cluster Name.
Question1.
How can I determine the cluster name of a 11.2 RAC Cluster ? We maintain a DB inventory. For each cluster , we want to specify the Cluster name.Hence we require the cluster name .
Question2.
The cluster name is of no functional importance. Right ? I don't remember using Cluster Name in any commands (srvctl, crsctl,...)

To determine the cluster name,[oracle@iron1 ~]$ olsnodes -c
ironcluster
[oracle@iron1 ~]$I wouldn't say it has much technical significance, though it is used as a default in a few other names.
John Watson
Oracle Certified Master DBA
http://skillbuilders.com

The DataSource with the JNDI name: contentDataSource could not be located

Hello,
We try to deploy our system/application to the servers that structed as
Machine one has:
1 administration domain
1 managed domain
Machine two has :
1 managed domain which is administrated by machine one.
I was trying to deploy the UI(portal application) to managed domain under Machine one. I got
error message as following:
Exception:weblogic.management.ApplicationException: activate failed for content.jar Module: content.jar Error: Exception activating module: EJBModule(content.jar,status=PREPARED) Unable to deploy EJB: ValueBean from content.jar: [EJB:011028]The DataSource with the JNDI name: contentDataSource could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
I have portalFrameworkPool Data Sources deployed to both managed domains.
when I deploy the application to the server that has one one domain(both adminstrator domain and application domain are in one), it is fine.
Can some one with same experience, or BEA people provide some help on this? Very appreciate any help on this issue.
Thanks in advance.
Christina

:-p
If you go to each Managed Server on the console, you can see the Service tab and then go to JDBC. Under JDBC you can see all the pool connections. Instead of localhost they should be pointing to the specific hostname or ip address of the adminserver and the pointbase port on that server (9093 by default) so the EAR files can be correctly deployed and then the JNDI Tree will look exactly the same on both servers. Change all the connection pools to use the specific hostname instead of localhost. Hope this works for you.

How to get the JNDI name of an EJB from within itself

Hello,
I'm trying to find a way to get the JNDI name of a session bean from
within itself.
In the application I'm working on we need to support multiple
customers. In order to do that, each EJB has a normal home and remote
interface, a base class bean implementation and different children
bean implemetations for each customer (when the logic for the
customers is different). JNDI is used to get the proper implementation
based on the customer.
I've got an EJB that provides some services that are the same for all
customers, except for the fact that it contains one variable that
should have a different value depending on the customer. I don't want
to creat subclasses just for that. What I want is to be able to get
the JNDI name and set the variable based on the it.
Is there a way to get the JNDI name for the EJB from within itself?
TIA
MJ

Hi Pradeep,
Please try referring to this post which is discussed earliar and seems its also answered.
http://forums.adobe.com/thread/504861
Thanks,
Bhasker Chari

How to Set the JNDI name in J2EE 1.4 ??

Hello,
I am sure i am have done everything right except for the JNDI name ! I have recently shifted to J2EE 1.4. I was using j2EE 1.2.
So kindly tell me how should i set me JNDI name in the deploytool.
Here is the exception i got when i tried to run my application without having set any JNDI name !!
http://img220.imageshack.us/img220/832/hellodt5.gif
Thanks.

There are 2 types of descriptors:
standard and portable deployment descriptors (e.g. ejb-jar.xml, web.xml, application.xml, etc)
vendor specific deployment plan (e.g., sun-ejb-jar.xml, sun-web.xml, sun-application.xml, jboss.xml, weblogic.xml, etc)
When you are developing ejb apps with glassfish, or JavaEE SDK, or Sun Java System Application Server, you usually package all descriptors in META-INF directory inside the jar.
You can also create portable apps that do not contain any vendor specific deployment plans. So you can deploy it to any appserver. At deployment time, you then specify an option to pass the deployment plan to deploy tool. This is required by JSR 88 and all J2EE- or JavaEE-compliant appserver must support this.
In Glassfish, JavaEE SDK, or SJSAS, you can:
$SJSAS_HOME/bin/asadmin deploy --deploymentplan /tmp/deploy-plan.jar /tmp/my-ejb.jar
where /tmp/deploy-plan.jar is a jar file containing sun-ejb-jar.xml for the deployable ejb-jar:
jar tvf deployment-plan.jar
0 Thu Oct 12 11:55:00 EDT 2006 META-INF/
106 Thu Oct 12 11:54:58 EDT 2006 META-INF/MANIFEST.MF
570 Thu Oct 12 11:55:00 EDT 2006 sun-ejb-jar.xml

Get the jndi names

i have the next code for conect to one weblogic server.
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.T3InitialContextFactory");
p.put(Context.PROVIDER_URL, url);
using the jndi name i can load the ejb but how can i list the jndi names?
thanks

I am using ejb 2, jdk 1.4.2 and weblogic 8.1 and for listing i haven't list() into the context.
can you help me please?
thanks

I have multiple emails associated with my i phone, but can't get my mac to associate some of the email names because it is associated with other apple id , but it's my id. how can i get around this?

I have multiple emails associated with my i phone, but can't get my mac to associate some of the email names because it is associated with other apple id , but it's my id. how can i get around this?

- Try contacting iTunes for the password problem:
Apple - Support - iTunes - Contact Us
- For the other problem you can try a reset. Nothing will be lost
Reset iPod touch: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- The next standard thing to do is to download/install a new app but you cant 'do that.
- Instead, try restoring from backup.

A problem determining the JNDI Name of a local EJB with WL 8.1

Similar Messages

Maybe you are looking for