Java and EJB Skills

Hi Everybody,
I know we need to know little to bit of Java for Java Mapping. Do we also need to know EJB for any reason? What is the skill level or how deep we need to knwo about EJB. Is there any document or thread which gives some info.
Thanks you.

Hi sonia,,,
Stefan is absolutely correct..
Java mapping and UDF coding just require simple java ....no EJB concept involved in tht...
EJB concept is required for creating adapter modules ....
Regards ,
Sushil

Similar Messages

Webdynpro java and EJB integration

Hi,
I am new to Webdynpro Java, would require your help in the following area:
my requirement is I need to read values from oracle database using EJB/Java Beans and display the same using webdynpro JAVA(as user interface).
Pls suggest the possible solution with required docs & videos(if possible)
FYI:
Tools: NWDS 7.0, SAP portal 7.3
Thanks
Nag

Hello Nag,
there are two possibilities to use your ejb in WD4J:
1. Via JNDI Lookup
try {
        InitialContext ctx = new InitialContext();
        <YourEJBInterface Class> service = (<YourEJBInterface Class>) ctx.lookup(<JNDI-Name>);
} catch (NamingException e) {
        throw new RuntimeException(e);
2. Via EJB Model:
here a guide --> http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70d2638c-4b04-2d10-d2a3-992fdf1e3d55?quicklink=index&…
hope this helps.
Regards
Tobi

Can't create EJB from existing .java AND ejb-jar.xml entries

I've noticed that I can create the source files for an EJB outside of JDeveloper, then I can do the "Create Entity Bean" thing, and specify the path to the source files, and it will use those source files, instead of forcing me to create them again.
However, I've noticed that if I manually add the information to the "ejb-jar.xml" file, and then try to add the bean, it won't let me. I've found I have to delete the entry from the ejb-jar.xml file and let JDeveloper control the creation of the fields, even if I know exactly what needs to be set.

If you are adding/modifying ejb-jar.xml outside JDeveloper and trying to see the changes.
Save the ejb-jar.xml file which is being modified externally
Select ejb-jar.xml in JDeveloper
and do View | Refresh
This will load in the changes (providing the source path has been set properly)
raghu
JDev Team

Starting up j2ee and EJB deployment tool on Windows 98

I will start off this question with an apology if it is too stupid,
basic, or placed in the wrong group. I am relatively new to the world
of Java and even newer to the world of Server-side Java and EJBs.
However, I am plugging away.
I am using my trusty 4 year old system with Windows 98 second edition
to dabble with Server-side Java and EJB applications. I am using
Tomcat 4.0 as my server. When I try and start the j2ee server or the
EJB deployment tool I get the following scrolling messages:
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Syntax error
Syntax error
Syntax error
Out of environment space
Bad command or file name
I have tried to adjust the memory settings in the DOS window with no
success. My question has three parts:
1) Can these applications be run using Windows 98 and if so what are
the exact DOS window memory settings for this?
2) Where exactly can I find the documentation that specifies this?
(please be specific as possible as I have read the readme.txt files
supplied with j2ee)
3) Should this and similar questions be posted in another
group/section?
I truly appreciate anyone's help with this.
Sincerely,
Tim

You're going to have a lot of pain unless you upgrade to Windows 2000 or XP.
In the mean time, set your environment size much larger (google for "Out of
environment space") and use WinOne from http://www.cia.com.au/luke/ ...
that's how I scraped by on Windows 98 for a while.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Tim" <[email protected]> wrote in message
news:[email protected]..
I will start off this question with an apology if it is too stupid,
basic, or placed in the wrong group. I am relatively new to the world
of Java and even newer to the world of Server-side Java and EJBs.
However, I am plugging away.
I am using my trusty 4 year old system with Windows 98 second edition
to dabble with Server-side Java and EJB applications. I am using
Tomcat 4.0 as my server. When I try and start the j2ee server or the
EJB deployment tool I get the following scrolling messages:
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Out of environment space
Syntax error
Syntax error
Syntax error
Out of environment space
Bad command or file name
I have tried to adjust the memory settings in the DOS window with no
success. My question has three parts:
1) Can these applications be run using Windows 98 and if so what are
the exact DOS window memory settings for this?
2) Where exactly can I find the documentation that specifies this?
(please be specific as possible as I have read the readme.txt files
supplied with j2ee)
3) Should this and similar questions be posted in another
group/section?
I truly appreciate anyone's help with this.
Sincerely,
Tim

Java Beans and EJBs

Hi friends,
I am quite new to Java and am interested in understanding EJBs and their use in deploying distributed applications.
I am not sure if I am supposed to first understand Java Beans before jumping to EJBs. I did read some of the messages under the Java Beans forum page but am confused..please help!!!
Regards,
Ritu

if I am supposed to first understand Java Beans before jumping to EJBsYes! Even before understanding objects and inheritence and so on.

[Java and all else] How do you document DB design?

Hello,
Although most of the technical choices are explicit in SQL (UniqueKey & ForeignKey constraints, indexes,...), the semantics of the data columns and their constraints seem better served as plain human-readable comments ("ID column: identifies the plane copy; 6 figures are enough as we don't expect to sell more than 1 million planes in a foreseeable future...").
In my current system, (EJB-based, but the DB schema is not created by the JPA-compliant ORM, but via SQL scripts), I see the following ways to write and maintain this documentation:
- SQL comments in the schema creation and patch scripts
- Javadoc comments in the Java source of the Entity classes.
- UML notes in UML diagrams(1)
- external "Architecture and design" document.
All 4 of them are used, sometimes inconsistently, for various parts of the design choices; I mean, the docs do not contradict themselves (not yet, but it's a mere question of time), but some tables are commented in SQL scripts, others are in design docs, and the details for some columns are in entity javadocs. Although each developer may find it handier to "write" the doc via his preferred medium, it becomes increasingly difficult to "maintain" theoverall documentation.
Our current situation is that most of the project team members are Java developers, so it would probably be better accepted and served if we standardized that we document DB tables and columns in Java source, but I am worried that:
- someone else pouring over our DB (ex: DBA helping us to optimize things, or other team developping a data-mining tool to leverage the historical data in DB) may not be as comfortable with Java
- this may not cover all design choices of the DB schema:
- - - - first, although that is the case currently, in the future there might not be a 100% 1-1 mapping between e.g. each entity class and a DB table. Maybe some columns will not need to be mapped anymore,...
- - - - second, I fear some DB constructs are not amenable to Java counterparts; no accurate idea there, I'm not an SQL nor JPA expert, but I presume Indexes, table partitioning, tablespaces, for example (yes, the DBMS is Oracle :o) are not taken into account in JPA mapping.
And if we document those choices at the SQL level (my preferred idea so far), this will gradually make the javadocs in the entities obsolete, or removed altogether, and that will make future maintenance of the Java source risky.
How do you document your DB design in general?
Do you have specific advices for my case?
Thanks in advance,
J.
(1) Just for the record, here are a few posts that refer to modelling the DB in UML:
[A post on this forum highlighting that UML 1.4 standardizes a notation for RDB modelling|http://forums.sun.com/thread.jspa?messageID=1383724#1383724]
[A DB modelling tutorial|http://www.tomjewett.com/dbdesign/dbdesign.php] (not sure whether it leverages the standard mentioned above :o)
P.S.: "Java and all else" as in, damn, I'd love to use the familiar JDC forums and people to discuss not only Java-related issues, but also [all other things that surround Java|http://forums.sun.com/thread.jspa?threadID=5422264&tstart=0] (other technologies, processes, people) and enable to make workable systems out of Java code.

jduprez wrote:
Thank you again.
A couple more questions:
2. Table, and proc dictionary maintained as one or more text files. Those files and schema are all in source control.Do you mean, a proprietary text format (a la tabledesign.txt), or +.sql+ source files? Again, you seem to suggest the scehma info is present in two locations.I didn't say two locations unless you meant files. Then yes.Yes I meant two files. I trust the team to get the doc file lagging a few revisions behind the SQL file, and to correct that I would have to include one more step in the review process (e.g. "review CM actions to check that the doc file is updated consistently with the SQL source").
The tool I wrote would throw errors if the comment file didn't match the schema. And if comments were not provided. That of course doesn't stop someone from documenting a table with "a table".
You can of course keep the addtional info as special comments in the SQL, but when I did this, and even in retrospect, it seems better and perhaps easier to keep them seperate. I have done special comments in SQL before and it seems a bit of a kluge but you do have the single source. But in that case I was the only one maintaining it too.What do you mean by "special"?For code generation I have a schema file with the following (pseudo sql.)
    create mytable
       mytable_id int,
       column_foo varchar(10);
       column_fum varchar(20)
        -- Query: for_a_query (column_foo, column_fum)
    )The generator consumes the schema and generates the standard CRUD which would include a query based on the primary key.
The above comment is used to provide an additional query where the proc is named 'for_a_query' (munged with table name) and takes two parameters (column_foo, column_fum) whose type/name matches those of the table.
If we don't try to generate a browseable HTML out of the schema (although the idea is appealing, I don't have the resource to make such a tool), do you see anything kludgy in maintaining SQL comments interpersed within DDL code?
Of course that is doable.

JDBC, JMS and EJB transactions - possible problem?

Hello,
          I am using Oracle 9, Weblogic 8.1 SP 4, MyEclipse and
          XDoclet.
          In my current project I have the following piece of code
          in one of my message driven beans (code cited as pseudocode
          without unnecessary details):
          * @ejb.bean name="MyMessageProcessor"
          * display-name="Display name for a MyMessageProcessor"
          * jndi-name="ejb/MyMessageProcessor"
          * description="Bean MyMessageProcessor"
          * destination-type="javax.jms.Queue"
          * transaction-type="Container"
          * acknowledge-mode="Auto-acknowledge"
          * subscription-durability="Durable"
          * generate="false"
          * @ejb.transaction type="Required"
          public class MyMessageProcessor implements MessageDrivenBean, MessageListener {
          public void onMessage(Message msg) {
               try {
                    //obtaining connections to two different databases via JNDi
                    java.sql.Connection connOne =
                    ((DataSource)ctx.lookup("DataSourceOne")).getConnection();
                    java.sql.Connection connTwo =
                         ((DataSource)ctx.lookup("DataSourceTwo")).getConnection();
                    // performing some UPDATEs and INSERTs on connOne and connTwo
                    // calling some other methods of this bean
                    //creating the reply JMS message and sending it to another JMS queue
                    Message msgTwo = this.createReplyMessage(msg)
                    this.queueSender.send(msgTwo);
                    //commiting everything
                    this.queueSession.commit();
               } catch (Exception ex) {
               try {
                    if (this.queueSession!=null) this.queueSession.rollback();
               } catch (JMSException JMSEx) {};
               this.context.setRollbackOnly();
          Some days ago (before the final remarks from my client) there used to be only one DataSource configurated on the basis of the
          connection pool with non-XA jdbc driver. Everything worked fine
          including the transactions (if anything wrong happend not only wasn't the replymessage sent, but also no changes were written
          to database and the incomming message was thrown back to the my bean's
          queue).
          When I deployed the second DataSource I was informed by an error message, that only one non-transactional resource may
          participate in a global transaction. When I changed both datasources
          to depend on underlying datasources with transatcional (XA) jdbc drivers, everything stopped working. Even if
          EJB transaction was theoretically successfully rolledbacked, the changed were written to the database
          and the JMS message wasn't resent to the JMS queue.
          So here are my questions:
               1. How to configure connection pools to work in such situations? What JDBC drivers should I choose?
               Are there any global server configurations, which may influence this situation?
               2. Which jdbc drivers should I choose so that the container was able to rollback the database transactions
               (of course, if necessary)?
               3. Are there any JMS Queue settings, which would disable the container to send message back to the
               queue in case of setRollbackOnly()? How should be the Queue configurated?
          As I am new to the topic and the deadline for the project seems to be too close I would be grateful
          for any help.
          This message was sent to EJB list and JDBC list.
          Sincerely yours,
          Marcin Zakidalski

Hi,
          I found these information extremely useful and helpful.
          The seperate transaction for sending messages was, of course, unintentional. Thanks a lot.
          Anyway, I still have some problems. I have made some changes to the
          code cited in my previous mail. These changes included changing QueueSessions
          to non-transactional. I also set the "Honorate global transactions" to true.
          I am using XA JDBC driver. After setting "Enable local transactions" to false
          (I did it, because I assume that JDBC transactions should be part on the global
          EJB transaction) I got the following error:
          java.sql.SQLException: SQL operations are not allowed with no global transaction by default for XA drivers. If the XA
          driver supports performing SQL operations with no global transaction, explicitly allow it by setting
          "SupportsLocalTransaction" JDBC connection pool property to true. In this case, also remember to complete the local
          transaction before using the connection again for global transaction, else a XAER_OUTSIDE XAException may result. To
          complete a local transaction, you can either set auto commit to true or call Connection.commit() or Connection.rollback().
          I have also inspected the calls of methods of bean inside of onMessage() method just to check, whether
          the transactions are correctly initialized (using the weblogic.transaction.Transaction class).
          My questions are as follows:
          1. Any suggestions how to solve it? I have gone through the google answers on that problem and only
          thing I managed to realize that JDBC must start its own transaction. Is there any way to prohibit it
          from doing that? Can using setAutocommit(true/false) change the situation for better?
          2. How to encourage the JDBC driver to be a part of EJB transaction?
          3. As I have noticed each of ejb method has its own transactions (transactions have different
          Xid). Each method of the bean has "required" transaction attribute. Shouldn't it work in such
          way that if already started transaction exists it is used by the called method?
          4. The DataSources are obtained in my application via JNDI and in the destination environment I will have slight
          impact on the configuration of WebLogic. What is least problematic and most common WebLogic configuration which would
          enable JDBC driver to participate in the EJB transaction? Is it the WebLogic configuration problem or can it be
          solved programmically?
          Currently my module works quite fine when "enable local transactions" for DataSources is set to true, but this way
          I am loosing the ability to perform all actions in one transaction.
          Any suggestions / hints are more than welcomed. This message was posted to jdbc list and ejb list.
          Marcin

OC4J 9.0.3 and EJB 1.1 deployments???

I can not deploy my ejb1.1 beans on 9.0.3 container.
OC4J crashes with an XML parse error as a null pointer exception.
If I remove my O-R mappings from my orion-ejb-jar.xml file, the container starts up ok (app wont run as it needs the mappings)
9.0.3 docs claim I should be able to use my 1.1 ejb in this ejb 2.0 container.
Solaris release notes for 9.0.3 claim I must migrate to ejb2.0
Someone else posted this same question but got no replies.
Anyone else deployed ejb1.1 with OR mappings in 9.0.3 successfully yet?
thanks

I have tried migrating to an ejb2.0 set of beans and ejb-jar.xml file.
With no <query> tags installed for my finders I notice that a typical finder produces this:

This is vastly different from the 1.1 orion-ejb-jar.xml which would list ALL column names in the finder - hence how am I going to do a findAll? The currently generated sql is way off. Deployment of the "ormap" demo also shows a lack of column names in the generated SQL finder methods in orion-ejb-jar.xml.
Further, as soon as I introduce the query in the 2.0 version of ejb-jar.xml, the container dies with a null pointer exception. Removing this from the ejb-jar and bean deploys. Useless, cause theres no finders though.
Also, attempts to add to the <finder-method query=...> tag yield container crashes with null pointers too.
This is not very robust to say the least. Can you provide names of jar files that would cause such exceptions?
When NO query tag is inserted in the ejb-jar file, attempts to run a sample client using findByPrimaryKey return successfully but use of findAll causes timeouts similar to whats described in
"finders giving "timeout expired waiting for an instance" after 0, 1, or 2 calls" in this same forum.
Heres the query out of the ejb-jar.xml file...
<query>
<query-method>
<method-name>findAll</method-name>
<method-params></method-params>
</query-method>
<ejb-ql>
SELECT OBJECT(o) from IspTb o
</ejb-ql>
</query>
IspTb is the <abstract-schema-name> Tables exist in db.
The full error...which prevents deployment of the ejbs and hence no rewrite of the orion-ejb-jar file.
=========
10/23/02 1:54 PM: javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
10/23/02 1:54 PM: java.lang.NullPointerException
10/23/02 1:54 PM: at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
10/23/02 1:54 PM: at java.lang.ClassLoader.loadClass(ClassLoader.java:287)
10/23/02 1:54 PM: at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:135)
10/23/02 1:54 PM: at java.lang.ClassLoader.loadClass(ClassLoader.java:287)
10/23/02 1:54 PM: at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:135)
10/23/02 1:54 PM: at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getClass(PersistenceDescriptor.java:767)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getStateClass(PersistenceDescriptor.java:753)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getCMPFieldType(PersistenceDescriptor.java:1302)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.initializeFieldInfo(PersistenceDescriptor.java:1052)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getPersistentFieldInfo(PersistenceDescriptor.java:805)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.<init>(SQLGenerator.java:151)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.generateSQL(SQLGenerator.java:360)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.generateSQL(SQLGenerator.java:309)
10/23/02 1:54 PM: at com.evermind.server.ejb.deployment.EJBPackage.translateEjbqlQeries(EJBPackage.java:2100)
10/23/02 1:54 PM: at com.evermind.server.ejb.compilation.Compilation.translateEjbqlQeries(Compilation.java:140)
10/23/02 1:54 PM: at com.evermind.server.ejb.compilation.Compilation.compile(Compilation.java:178)
10/23/02 1:54 PM: at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:551)
10/23/02 1:54 PM: at com.evermind.server.Application.postInit(Application.java:431)
10/23/02 1:54 PM: at com.evermind.server.Application.setConfig(Application.java:136)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1635)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.initializeApplications(ApplicationServer.java:1585)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1240)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:93)
10/23/02 1:54 PM: at java.lang.Thread.run(Thread.java:479)
10/23/02 1:54 PM: javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getClass(PersistenceDescriptor.java:770)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getStateClass(PersistenceDescriptor.java:753)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getCMPFieldType(PersistenceDescriptor.java:1302)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.initializeFieldInfo(PersistenceDescriptor.java:1052)
10/23/02 1:54 PM: at com.sun.enterprise.deployment.PersistenceDescriptor.getPersistentFieldInfo(PersistenceDescriptor.java:805)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.<init>(SQLGenerator.java:151)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.generateSQL(SQLGenerator.java:360)
10/23/02 1:54 PM: at com.sun.ejb.sqlgen.SQLGenerator.generateSQL(SQLGenerator.java:309)
10/23/02 1:54 PM: at com.evermind.server.ejb.deployment.EJBPackage.translateEjbqlQeries(EJBPackage.java:2100)
10/23/02 1:54 PM: at com.evermind.server.ejb.compilation.Compilation.translateEjbqlQeries(Compilation.java:140)
10/23/02 1:54 PM: at com.evermind.server.ejb.compilation.Compilation.compile(Compilation.java:178)
10/23/02 1:54 PM: at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:551)
10/23/02 1:54 PM: at com.evermind.server.Application.postInit(Application.java:431)
10/23/02 1:54 PM: at com.evermind.server.Application.setConfig(Application.java:136)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1635)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.initializeApplications(ApplicationServer.java:1585)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1240)
10/23/02 1:54 PM: at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:93)
10/23/02 1:54 PM: at java.lang.Thread.run(Thread.java:479)

OC4J EJBQL and EJB 2.0 features

Hello Debu Panda and All
I've got all howtos and I mangaged to get some parts of OC4J [Oracle9iAS (9.0.3.0.0) Containers for J2EE (build 020323.1689)] working.
There are still some issues that are stalling our development. Could you please comment on them, maybe providing an estimate of when they will be solved/implemented?
First of all, a little background. Our application uses many Java Swing application clients that connect to the EAR application in the container.
The ear application has the following structure:
All database access (Oracle 8i, located in its own server) is done exclusively by means of CMP entity beans. A entity bean may access other entity beans. There are workflow session beans (stateful and stateless) that access the entity beans. All clients see only the workflow session beans (session beans fagade).
Our applicatoin is complex, having more than 80 session beans and more than 25 entity beans (not counting entity beans that exist only to represent relationships among entity beans).
There goes the questions:
1) It seems that entity beans cannot currently be referenced by remote interfaces. We couldn't deploy our application using it. Since we could use only local interfaces fot entity beans, thats what is been done now.
2) There is no CMR supported. Is this true?
3) EJBQL seems to be very limited. In the howto examples there are EJBQL statements that compare two numbers. However, when we tried to use String comparisons, it didn't work. Here is the statement:
"SELECT DISTINCT OBJECT(p) FROM Person p WHERE p.name = ?1"
If I compile, package and deploy the ear applicatin with the above EJBQL statement, OC4J generates an exception when executing the finder method. The exception is:
"java.rmi.NoSuchObjectException: Session has timed out
at com.evermind.server.ejb.StatefulSessionEJBObject.throwPassivisat
ception(StatefulSessionEJBObject.java:188)
at Cad023Remote_StatefulSessionBeanWrapper0.obterPessoasPorParteNom
023Remote_StatefulSessionBeanWrapper0.java:754)
at java.lang.reflect.Method.invoke(Native Method)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:8
at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)"
If I remove the where clause, the expection is gone. However, I get all records. ;-)
4) It seems that all EJBQL clauses must be capitalized. Is this true?
FINALY)
Is there a newer OC4J build that could use to get the development going? Do you know where there will be one? Is there any way of contacting the OC4J development team to report bugs?
If you would like, we could discuss it in private e-mail (please use my private mail [email protected]).
Thanks for your attention,
Luis Fernando Soeiro
Hi !! OC4J 9.0.3 developer's preview has most features of EJB 2.0. We are working on updating on our docs and samples for EJB 2.0
Please look at the following URL that has some How Tos on EJB 2.0 features such Local Interfacea, EJB QL, etc : http://otn.oracle.com/tech/java/oc4j/htdocs/oc4j-how-to.html#ejb
regards
Debu Panda
Oracle --------------------------
Luis Soeiro <mailto:[email protected]> <mailto:[email protected]>Type : Question Date : Apr 11, 2002 15:15 PT Hello
Some colleagues and I are trying to port a large project from JBOSS to OC4J. We used JBOSS 3.0 (beta) in order to evaluate EJB2.0 features and see if we could use it. We already have OC4J in production, but only as a JSP/Servlet container. The next step would be to deploy our EJB application to OC4J.
We have read the material and it is written that OC4J (developers preview) is EJB 2.0 compliant. However, the specific documentation and the examples don't show how to specify OC4J specifc XML files. We absolutely need CMR and Local Interfaces, because we don't have the time required to downgrade our JBoss EJB2.0 application to the EJB 1.1 specification. We have over 80 Session Beans and over 20 Entity Beans.
Is there anybody there that can confirm that OC4J developer's preview is really EJB2.0 compliant? If so, could you send me some pointers to information about OC4J container specifc deployment descriptors? The docs listed at the web site don't have EJB2.0 features listed, nor does the Oracle samples.
Thanks for your attention,
desperately,
Luis Fernando Soeiro

HI,
I worked out CMR and EJB-QL with single bean.
Using CMR, it is possible to get one bean reference through other bean, but
When I tried EJB-QL with bean to bean navigation then I run into problem.

Communication between Abap and Java and Java to Abap

HI,
I have installed BI 7.0 and the user complaints that BEx WEB Application Designer Query results are not showing up in the WEB URL Link.
and the BI user suggests that communication between Abap to java and Java to Abap has to be done?
How to setup ABAP to JAVA and JAVA to ABAP communication?
Regards,
Magham.

Hi,
Jco conn from ABAP to Java
=====================
You can use the JCO RFC Provider Service of the Web Application Server for your ABAP to Java calls.
The steps involved in that are
1. Configure destination in SM59 in SAP.
2. Create RFC Destination in Visual Admin.
3. Create a stateless session bean with JNDI name as the name of calling function module in SAP.
4. Add a business method public void processFunction(JCO.Funtion fn) which is called by the JCO RFC Provider Service. The name should be 'processFunction'.
5. Set library references in application-j2ee-engine.xml to type weak for the following
a. com.sap.mw.jco.
b. com.sap.tc.Logging (if you are using the logging api )
Here is the sample code for the EJB biz method
Business Method.
public void processFunction(JCO.Function function) {
try {
// Get the import parameters for the function module
JCO.ParameterList importList = function.getImportParameterList();
logger.infoT("The value sent is" +
(String)importList.getValue("USER_NAME"));
// Set the export parameter value for the function module
JCO.ParameterList export = function.getExportParameterList();
export.setValue("From EJB", "RETURN");
function.setExportParameterList(export);
catch (java.lang.Exception e) {
e.printStackTrace();
Jco conn from Java to others(ex:ABAP)
=====================-==========
Open Visual Admin(C:\usr\sap\SID\JCxx\j2ee\admin\go.bat) and connect to server
Go to Destinations service
Open HTTP Settings Tab
Add/Edit destination SLD_DataSupplier and type following values
URL http://xyz.corp:53000
Authentication - BASIC
User dynproxxx
Password - bp52st000
Press save and test (if you get response code 200 everything is o.k.)
Add/Edit other HTTP Destination named SLD_Client with the same values as SLD_DataSupplier:
URL http://xyz.corp:53000
Authentication - BASIC
User dynproxxx
Password - bp52st000
Press save and test (if you get response code 200 everything is o.k.)
Go to SLD Data Supplier service.
Press the button named: Send the Data to SLD and confirm triggering SLD Data transfer (if you receive successful message everything is o.k.).
===================
following blog might helpfull
=======================
/people/michal.krawczyk2/blog/2005/03/10/registering-a-new-technical-system-in-sld--abap-based
for basic infor
==============
http://help.sap.com/saphelp_nw04s/helpdata/en/21/84570b3ae14e77b3047c82218974b9/frameset.htm
Award points if it helps

Error in Career and Job= Skills Profile

I have the following issue:
In the application of Career and Job=>Skills Profile. When I want add a new qualification, the system display the following message of error:
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NullPointerException
    at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.getNextPerspective(FcXssPcd.java:518)
    at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.getNextPerspective(InternalFcXssPcd.java:190)
    at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.getNextPerspective(FcXssPcdInterface.java:168)
    at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.getNextPerspective(InternalFcXssPcdInterface.java:160)
    at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.getNextPerspective(InternalFcXssPcdInterface.java:252)
    ... 69 more
java.lang.NullPointerException
     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.getNextPerspective(FcXssPcd.java:518)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.getNextPerspective(InternalFcXssPcd.java:190)
     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.getNextPerspective(FcXssPcdInterface.java:168)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.getNextPerspective(InternalFcXssPcdInterface.java:160)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.getNextPerspective(InternalFcXssPcdInterface.java:252)
     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcd.getNextPerspective(CcXssPcd.java:246)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcd.getNextPerspective(InternalCcXssPcd.java:172)
     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcdInterface.getNextPerspective(CcXssPcdInterface.java:135)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface.getNextPerspective(InternalCcXssPcdInterface.java:132)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface$External.getNextPerspective(InternalCcXssPcdInterface.java:192)
     at com.sap.xss.essservices.cc.ccesspcd.CcEssPcd.getNextPerspective(CcEssPcd.java:220)
     at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcd.getNextPerspective(InternalCcEssPcd.java:157)
     at com.sap.xss.essservices.cc.ccesspcd.CcEssPcdInterface.getNextPerspective(CcEssPcdInterface.java:135)
     at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcdInterface.getNextPerspective(InternalCcEssPcdInterface.java:132)
     at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcdInterface$External.getNextPerspective(InternalCcEssPcdInterface.java:210)
     at com.sap.pcuigp.xssutils.ccxss.CcXss.getNextPerspective(CcXss.java:238)
     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.getNextPerspective(InternalCcXss.java:157)
     at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.getNextPerspective(CcXssInterface.java:121)
     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.getNextPerspective(InternalCcXssInterface.java:128)
     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.getNextPerspective(InternalCcXssInterface.java:188)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:479)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseEvent(FPMComponent.java:938)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseEvent(FPMComponent.java:1101)
     at com.sap.xss.hr.skl.detail.VcSklDetail.addChanges(VcSklDetail.java:206)
     at com.sap.xss.hr.skl.detail.wdp.InternalVcSklDetail.addChanges(InternalVcSklDetail.java:236)
     at com.sap.xss.hr.skl.detail.Detail.onActiononAddChanges(Detail.java:220)
     at com.sap.xss.hr.skl.detail.wdp.InternalDetail.wdInvokeEventHandler(InternalDetail.java:235)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
     at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1356)
     at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:869)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
In the log trace of portal nwa.
com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent
sap.com/tc~wd~dispwda
I made a trace using the t.code ST01 and the system not show error of authorizations. I checked the t.code SLG1 and the system not show none log.
Please anyone can help me with suggestions for solve this issue,
Regards
Carmen

I assigned the role SAP_ALL but the issue continue.
I checked the skills catalog and qualifications and all is Ok.
I don`t understand the cause of this error.
Thanks in advance,
Regards
Carmen G

SAS9.1 Persistence and EJB lookups (not registered in JNDI?)

I am trying to deploy a very basic EJB3 module to test my learning. The module deploys via the Admin Console without apparnet error. Unfortunately, when using the generated test page for the web-service, I am having total failure which seems to be around the persistence unit and EJBs not being created in the JNDI.
I have an @Stateless/@WebService bean:
package com.flexit.buslogic;
import java.util.logging.Level;
import javax.ejb.Stateless;
import javax.ejb.EJB;
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebService;
import com.flexit.persistence.eao.OwnerFacade;
@WebService
@Stateless
public class CreateOwner {
     @EJB
     private OwnerFacade ownerFacade;
     public CreateOwner(){}
     @WebMethod
     public Integer addOwner (
               @WebParam(name="Name") String name){
         LogUtil.log("Add owner request " +
                    "received for "+name,
                    Level.INFO, null);
        return ownerFacade.findAll().size();
}The OwnerFacade EJB injection fails with avax.ejb.EJBException: nested exception is: javax.ejb.CreateException: Could not create stateless EJBIf I instantiate a 'normal' reference to OwnerFacade (ie OwnerFacade ownerFacade = new OwnerFacade(); I get a similar error in the OwnerFacade EJB in relation to an attempt to inject an EntityManager:
package com.flexit.persistence.eao;
import java.util.List;
import java.util.logging.Level;
import javax.ejb.Stateless;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
import com.flexit.persistence.LogUtil;
import com.flexit.persistence.Owner;
@Stateless
public class OwnerFacade implements OwnerFacadeLocal, OwnerFacadeRemote {
     // fields
     @PersistenceContext(unitName="FlexIBuildPU")
     private EntityManager entityManager;
     public OwnerFacade () {
          if (entityManager == null) {
               LogUtil.log("unable to get an Entity Manager Instance", Level.SEVERE, null);
...The constructor logs that the entityManager is, indeed, null.
I have tried the code on SAS9 and 9.1 and using the default JavaDB and a MySQL connection pool (successful ping) and datasource (named 'jdbc/FlexDBDS') created through the Admin Console. The persistence unit is defined in a persistence.xml file in the META-INF folder:
<?xml version="1.0" encoding="UTF-8"?>
     <persistence xmlns="http://java.sun.com/xml/ns/persistence"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
         http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0">
          <persistence-unit name="FlexIBuildPU" transaction-type="JTA">
               <jta-data-source>jdbc/FlexDBDS</jta-data-source>
          </persistence-unit>
</persistence>Can anyone please save me from tearing my hair out (more)?

Have managed to resolve. There were two problems
First I was attempting to access a session bean directly rather than via an interface (eejit!) - ie:
@EJB OwnerFacade ownerFacadewhen it should have been:
@EJB OwnerFacadeLocal ownerFacadeSecond, the persistence unit wasn't created properly. In playing around with persistence.xml I moved from:
<?xml version="1.0" encoding="UTF-8"?>
     <persistence xmlns="http://java.sun.com/xml/ns/persistence"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
         http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0">
          <persistence-unit name="FlexIBuildPU" transaction-type="JTA">
               <description>This unit manages BMS units, owners, offers, and acceptance.</description>
               <jta-data-source>jdbc/FlexDBDS</jta-data-source>
               <properties>
                      <property name="toplink.jdbc.driver" value="com.mysql.jdbc.Driver"/>
                      <property name="toplink.ddl-generation" value="create-tables"/>
               </properties>
          </persistence-unit>
</persistence>to:
<?xml version="1.0" encoding="UTF-8"?>
     <persistence xmlns="http://java.sun.com/xml/ns/persistence"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
         http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0">
          <persistence-unit name="FlexIBuildPU" transaction-type="JTA">
               <description>This unit manages BMS units, owners, offers, and acceptance.</description>
               <jta-data-source>jdbc/FlexDBDS</jta-data-source>
               <properties>
                      <property name="toplink.jdbc.driver" value="com.mysql.jdbc.Driver"/>
                      <property name="toplink.application-location" value="C:\ddl\flexdb\"/>
                      <property name="toplink.create-ddl-jdbc-file-name" value="create.sql"/>
                      <property name="toplink.drop-ddl-jdbc-file-name" value="drop.sql"/>
                      <property name="toplink.ddl-generation.output-mode" value="both"/>
                      <property name="toplink.ddl-generation" value="create-tables"/>
               </properties>
          </persistence-unit>
</persistence>It seems the very action of writing the sql to file helps with the binding. It seems so extraordinary that I think I must of made another mistake which was corrected along the way. In any event, the properties specifying output files may prove useful to others. :)

Database and ejb access in Input Processor, custom Validator

Hi guys,
I know the Portal docs recommend that database and ejb calls should be done in
a Pipeline Component. Are transactions the only concern?
I'd like to validate two fields. This can be easily accomplished by a an ejb
method call that returns a boolean for one, and by running a simple select statement
for the other. Are there any risks to creating custom validator classes to do
this?
Thanks

David,
Here are the characterstics of Pipelines and IPs:
Inputprocessors:
- Web App scope (classloaded by webapp classloader)
- simple java class
Pipelines/Pipeline Components:
- Enterprise App scope (available to all webapps)
- java class or EJB
- can be transactional (can even rollback PipelineSession)
- Pipelines executed from within the EJB container
There is nothing illegal about putting EJB calls and JDBC calls into an Inputprocessor.
For simple validation, this is probably okay. However, when doing heavy business
logic, having the Pipeline manage a single transaction for your PCs is wonderful.
PJL
"David Sun" <[email protected]> wrote:
>
Hi guys,
I know the Portal docs recommend that database and ejb calls should be
done in
a Pipeline Component. Are transactions the only concern?
I'd like to validate two fields. This can be easily accomplished by
a an ejb
method call that returns a boolean for one, and by running a simple select
statement
for the other. Are there any risks to creating custom validator classes
to do
this?
Thanks

Porblem with Java Proxy EJB deploy to XI through NWDI

Situation - I have a web app in Server A (WAS7), it needs to call a java proxy in Server B (XI WAS7). I want to deploy the Java Proxy EJB into the landscape using NWDI. To do this I created an external library with public parts that contains the required jars to build the java proxies. These are aii_msg_runtime.jar, aii_proxy_xirt.jar, and aii_utilxi_misc.jar. The EJB module used part is mapped to the library's public parts. Everything builds fine and the deployment was successful into XI.
Problem - When my web application makes a remote call to the java proxy in XI, NoClassDefFoundError occurs. The first jar that it complain about was aii_util_cimaccess.jar. I included this jar into the library and redeployed. Called the java proxy again, and got another NoClassDefFoundError exception. Now it wanted the lrcclient.jar. I included that into the library and redeployed. Now it wanted another jar. The issue is that all these jars are in the XI server and I shouldn't have to add them as part of the library. Is there a SCA out there that contains these jars, or did I just forget to mark a checkbox somewhere when creating the EJB so that it would reference the XI jars without me adding them to the library?
Note - This architecture works fine without having to add the jars above, if I deploy the Java Proxy EJB from my workspace to XI through the SDM process available through NWDS. This only breaks when I deploy through NWDI.
Thank you in advance.

HI,
please see the below link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bc7f08e1-0901-0010-b1bd-80966009d8f0
http://help.sap.com/saphelp_nw2004s/helpdata/en/40/00be09879f114aa1ec46c2afa4445b/frameset.htm
To add On-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9221b490-0201-0010-0e90-8cc75cde876c
http://help.sap.com/saphelp_webas630/helpdata/en/cb/f4bc3d42f46c33e10000000a11405a/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/eaeb475d-0c01-0010-f5a4-d7a8eb185793
Regards
Chilla

Servlet jndi lookup to remote EJB, servlet and EJB not in the same application

Hi,
I think that the subject explain my problem.
I have Oracle IAS9i 9.0.2.0.0, and JDeveloper 9.0.2.829
I have deployed and EJB in IAS9i and i want to use from the developer machines, which have JDeveloper.
how can i to do remote calls from JDeveloper?.
I have modifed the orion-application.xml, and added remote=true.
I have modifed the rmi.xml and added the hosts where the Jdeveloper placed.
Any ideas?
Thanks and cheers
P.D The app server and jdeveloper are in the same net.
if it is posible replys me to [email protected] too.

Steps to access a remote EJB from within OC4J
++++++++++++++++++++++++++++++++++++++++++++++
1) Deploy EJB application (ApplicationRemote) to remote container (REMOTE)
"java -jar admin.jar -deploy ormi://REMOTE.hostname:REMOTE.port REMOTE.username REMOTE.password -deploy -file ApplicationRemote.ear
-deploymentName ApplicationRemote"
2) Ensure that local application (ApplicationLocal) has ejb-ref tags for remote EJBs accessed (in web.xml or ejb-jar.xml)
3) Deploy to local container (LOCAL) an empty application (ApplicationEmpty) with the same name as the remote application (ApplicationRemote)
"java -jar admin.jar -deploy ormi://LOCAL.hostname:LOCAL.port LOCAL.username LOCAL.password -deploy -file ApplicationEmpty.ear -deploymentName
ApplicationRemote"
5) Deploy local application (ApplicationLocal) to local container (LOCAL)
"java -jar admin.jar -deploy ormi://LOCAL.hostname:LOCAL.port LOCAL.username LOCAL.password -deploy -file ApplicationLocal.ear -deploymentName
ApplicationLocal"
4)Restart local container
ApplicationEmpty should consist of just an application.xml file - no modules. The same file can be deployed with different application names for all the remote
applications that must be accessed.
ApplicationLocal should access the remote EJB by using the following JNDI properties
java.naming.factory.initial = "com.evermind.server.rmi.RMIInitialContextFactory"
java.naming.provider.url = "ormi://REMOTE.hostname:REMOTE.port/ApplicationRemote"
java.naming.security.principal = "REMOTE.username"
java.naming.security.credentials = "REMOTE.password"
regards
Debu Panda

Java and EJB Skills

Similar Messages

Maybe you are looking for