EJB to JSP Integration Tool

          Hello,
          I am looking for the command line version of
          java weblogic.servlet.ejb2jsp.gui.Main
          What is it and where is the doco please?
          Thank you,
          T

          Got it sorry ;-)
          As simple as weblogic.servlet.ejb2jsp.Main
          t

Similar Messages

TagLib created by EJB to JSP Integration Tool

          Hi, I've an EJB deployed on WebLogic 6.1 and I'm using WebLogic's EJB to JSP Integration
          Tool to create JSP Tag Libraries.
          I've written a jsp look like this.
          <%@ taglib uri="WEB-INF/abc-tags.tld" prefix="abc" %>


In web.xml include a <taglib> element
          taglib>
          <taglib-uri>/abc-tags</taglib-uri>
          <taglib-location>WEB-INF/abc-tags.tld</taglib-location>
          </taglib>
          Gary Tam wrote:
          > Hi, I've an EJB deployed on WebLogic 6.1 and I'm using WebLogic's EJB to JSP Integration
          > Tool to create JSP Tag Libraries.
          > I've written a jsp look like this.
          >
          > <%@ taglib uri="WEB-INF/abc-tags.tld" prefix="abc" %>

HELP with EJB to JSP Integration tool WLS 7.0

          Hi,
          Has anyone used the EJB2JSP Integration tool in WLS 7.0? I can't find any documenation
          except for the page at http://edocs.bea.com/wls/docs70/jsp/ejb2jsp.html. It is
          not much help. I can get the graphical tool to run, but not import a .jar file.
          This is the error I get when trying to open an ejb.jar.
          C:\bea\user_projects\myTestDomain\applications\DefaultWebApp\WEB-INF\classes\EJB\Spike>java
          weblogic.servlet.ejb2jsp.gui.Main
          error occurred: java.lang.NullPointerException
          java.lang.NullPointerException
          at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:287)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
          at weblogic.servlet.ejb2jsp.Utils.createBeanDescriptor(Utils.java:343)
          at weblogic.servlet.ejb2jsp.Utils.createDefaultDescriptor(Utils.java:314)
          at weblogic.servlet.ejb2jsp.Utils.createDefaultDescriptor(Utils.java:266)
          at weblogic.servlet.ejb2jsp.gui.Main.loadFromPaths(Main.java:391)
          at weblogic.servlet.ejb2jsp.gui.Main.doNew(Main.java:378)
          at weblogic.servlet.ejb2jsp.gui.Main$5.run(Main.java:575)
          at weblogic.servlet.ejb2jsp.gui.MainWorker.run(Main.java:757)
          at java.lang.Thread.run(Thread.java:479)
          error occurred: java.lang.NullPointerException
          java.lang.NullPointerException
          at weblogic.servlet.ejb2jsp.gui.Main.doNew(Main.java:379)
          at weblogic.servlet.ejb2jsp.gui.Main$5.run(Main.java:575)
          at weblogic.servlet.ejb2jsp.gui.MainWorker.run(Main.java:757)
          at java.lang.Thread.run(Thread.java:479)
          Is this error and the fix to it obvious to someone else? If so, I would appreciate
          some help!
          THank you!!
          Wendy


Try weblogic.servlet.ejb2jsp.gui.Main
Kris

Re: Accessing EJB through JSP

          Can anyone guide me to a tuorial thru which I can learn how to invoke EJBs thru
          JSP pages.
          Thanks..Kevin


EJB to JSP Integration
          http://edocs.bea.com/wls/docs61/jsp/ejb2jsp.html
          Kevin wrote:
          > Can anyone guide me to a tuorial thru which I can learn how to invoke EJBs thru
          > JSP pages.
          >
          > Thanks..Kevin

EJB/JSP integration?

Hi,
I have written an application that has EJBs, and JSPs that invoke the
EJBs. It works on WebLogic 5.1.
I want to package this application up in such a way that it can be
deployed on any kind of J2EE application server.
Using JBoss, I discovered that the JSPs by default do not have access to
the interfaces supplied in the EJBs. i.e. I have to make copies of the
EJB's home and remote interfaces, and put them where the JSP files can
find them.
This messing about was not neccessary with WebLogic. WebLogic knew to look
in the EJB JAR files.
So my question : For compatibility, should I create multiple copies of my
EJB's interfaces, or is WebLogic's developer-friendly behaviour the
correct one?
Thanks, Martin.

Weblogic 5.1 uses an architecture that is very unique. Consider it the
exception, not the rule. You can NOT support a single deployment binary
with WL 5.1 and other servers.
The Weblogic 6.0 architecture is much closer to the others, and
significantly better than the reference implementation's architecture. In
6.0 you should be able to make a single app (EAR) that deploys to other
servers as well.
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"martin" <[email protected]> wrote in message
news:3a6f070e$[email protected]..
Hi,
I have written an application that has EJBs, and JSPs that invoke the
EJBs. It works on WebLogic 5.1.
I want to package this application up in such a way that it can be
deployed on any kind of J2EE application server.
Using JBoss, I discovered that the JSPs by default do not have access to
the interfaces supplied in the EJBs. i.e. I have to make copies of the
EJB's home and remote interfaces, and put them where the JSP files can
find them.
This messing about was not neccessary with WebLogic. WebLogic knew to look
in the EJB JAR files.
So my question : For compatibility, should I create multiple copies of my
EJB's interfaces, or is WebLogic's developer-friendly behaviour the
correct one?
Thanks, Martin.

Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.

          Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.
          Acelet is the leader in J2EE tools area. If you google "j2ee tools",
          "j2ee logging", "j2ee scheduler" or alike, you will find Acelet
          is at the top of the result.
          Super 4.00 comes with:
          SuperEnvironment
          SuperLogging
          SuperPeekPoke
          SuperReport
          SuperScheduler
          SuperStress
          and SuperPatrol, as a schedule job.
          The evaluation edition can be anonymously downloaded from:
          http://www.ACElet.com.
          Super is a component based monitor and administration tool
          for EJB/J2ee. It provides built-in functionality as well as
          extensions, as SuperComponents. Users can install
          SuperComponents onto it, or uninstall them from it.
          Super has the following functions:
          * A J2EE monitor.
          * A gateway to J2EE/EJB servers from different vendors.
          * A framework holding user defined SuperComponents.
          * A full-featured J2EE logging and J2EE tracing tool for centralized,
          chronological logging.
          * An EJB tool for Peeking and Poking attributes from EJBs.
          * An EJB Stress test tool.
          * A J2EE global environment tool.
          * A J2EE report tool.
          * A J2EE Scheduler tool.
          * A J2EE Business patrol tool.
          It is written entirely in the Java(TM) programming language.
          The current version support:
          * JOnAS 2.4 and 2.6
          * SunONE 7.0
          * Universal servers.
          * Weblogic 6.1, 7.0 and 8.1
          * Websphere 4.0 and 5.0.2
          * jBoss 3.0 and 3.2
          ********** What is new:
          Version 4.00 November, 2003
          Enhancement:
          1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
          (with/without proxy) protocol mode for SuperEnvironment,
          SuperLogging, SuperReport and SuperScheduler.
          2. SuperLogging 4.00: tracing can work on both live database and retired database.
          3. SuperReport 3.00: works for both live database and retired database.
          4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table
          Panel.
          Bug fix:
          1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
          Version 3.00 July, 2003
          Enhancement:
          1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart"
          scope,
          with enhancements and bug fixes.
          2. SuperLoggingLibrary 3.00: Support mail server which requires user name and
          password.
          Add MenuTreePanel.
          3. Improved GUI and document.
          4. Add support to WebLogic 8.1.
          Bug fix:
          1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
          2. SuperScheduler 2.0: Startup should never be reported as missed.
          3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
          Version 2.20 Jan. 2003
          Enhancement:
          1. Add desktop and start menu shortcuts for MS-Windows.
          2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
          3. SuperLogging 2.40: Add new sendAlarmEmail() method.
          4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
          direct database is not practical; Allow user to choose
          favorite logging software; Add Last day as Monthly
          repeating attribute.
          Change:
          1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
          Bug fix:
          1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
          open Environment Manager.
          2. SuperLogging client 1.52: Annoying exception thrown when you use
          JDK 1.4 (the program runs okay).
          3. SuperPeekPoke 1.61: Fix bug where input object contains
          java.lang.Double and alike.
          4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
          PatrolAlarm for SuperPatrol; Composite task with members;
          Non-scheduled run on other host; Around edges of last
          days in Monthly with holiday policy.
          Version 2.10 July 2002
          Enhancement:
          1. SuperScheduler 1.3: Add Future View to check future schedule in
          both text and Gantt-chart mode.
          2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
          activities.
          3. SuperEnvironment 1.3: uses new graphic package adding print and
          preference facilities.
          4. SuperPeekPoke 1.6: uses new graphic package adding print and
          preference facilities.
          5. SuperStress 1.21: uses new graphic package.
          Bug fix:
          1. SuperStress 1.21: fixed graphic related bugs.
          Version 2.01 June 2002
          Enhancement:
          1. Add options for Look & Feel.
          2. Preference is persistent now.
          Bug fix:
          1. Installation for WebLogic 7.0: extEnv may not be installed on the
          right place, so SuperLibrar on the server side was not loaded and
          causes other problems.
          Version 2.00 June 2002
          Enhancement:
          1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
          when any Doer causes things to change.
          2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
          3. SuperReport 1.2: Support default HTML browser for reading HTML document.
          4. Support WebLogic 7.0.
          5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
          6. SuperEnvironment 1.21: New SuperEnvironment tour.
          Bug fix:
          1. WebSphere Envoy did not always list all JNDI names.
          Version 1.90 May 2002
          Enhancement:
          1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
          2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
          effective period. Add Patrol job type as SuperPatrol.
          3. Add support for both JOnAS and jBoss.
          4. Add more elements on Report criteria.
          Change:
          1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
          and descend.
          2. New log database.
          Bug fix:
          1. Alert email should be sent once in the interval, regarding number of servers
          in the clustering.
          2. Minor bug fixes to make errors handled better on SuperLogging.
          3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
          them.
          4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
          Version 1.80 March 2002
          Enhancement:
          1. Add new component: SuperScheduler
          Bug fix:
          1. SuperLogging: Verbose should ignore class registration.
          2. SuperLogging-tracing: an exception was thrown if the java class without package
          name.
          Version 1.70 January 2002
          Enhancement:
          1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
          weblogic 6.1, need download an application).
          2. Add alias names for log threshold as new Java suggests.
          3. New component: SuperReport.
          Change:
          1. SuperLogging: Log database parameters are specified in a properties file, instead
          of EJB's deployment descriptor. It is more convenient and it avoids some potential
          problems. No change for development, easier for administration.
          Bug fix:
          1. Add Source Path Panel now accepts both directory and jar file.
          2. Bug in SuperEnvironment example (for version 1.60 only).
          Version 1.60 December 2001
          Enhancement:
          1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
          2. Add timeout parameter to logging access.
          3. New installation program with A). Easy install. B). Remote command line install.
          4. Support EJB 2.0 for Weblogic 6.1.
          5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
          was supported since version 1.5).
          Change:
          1. Poke: argument list is set at define time, not invoke time.
          2. Default log database change to server mode from web server mode, booting performance
          to 10-20 times.
          Bug fix:
          1. If the returned object is null, Peek did not handle it correctly.
          2. If the value was too big, TimeSeries chart did not handle it correctly. Now
          it can handle up to 1.0E300.
          3. Help message was difficult to access in installation program.
          4. Source code panel now both highlights and marks the line in question (before
          it was only highlight using JDK 1.2, not JDK 1.3).
          5. Delete an item on PeekPoke and add a new one generated an error.
          Version 1.50 August, 2001
          Enhancement:
          1. Source code level tracing supports EJB, JSP, java helper and other
          programs which are written in native languages (as long as you
          write correct log messages in your application).
          2. Redress supports JSP now.
          3. New installation with full help document: hope it will be easier.
          4. Support WebSphere 4.0
          Version 1.40 June, 2001
          Enhancement:
          1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
          and PieView for GlobalProperties.
          GlobalProperties is an open source program from Acelet.
          2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
          Changes:
          1. The structure of log database changed. You need delete old installation and
          install everything new.
          2. The format of time stamp of SuperLogging changed. It is not locale dependent:
          better for report utilities.
          3. Time stamp of SuperLogging added machine name: better for clustering environment.
          Bug fix:
          1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
          Style Panel may not show up.
          Version 1.30 May, 2001
          Enhancement:
          1. Add ConnectionPlugin support.
          2. Add support for Borland AppServer.
          Version 1.20 April, 2001
          Enhancement:
          1. Redress with option to save a backup file
          2. More data validation on Dump Panel.
          3. Add uninstall for Super itself.
          4. Add Log Database Panel for changing the log database parameters.
          5. Register Class: you can type in name or browse on file system.
          6. New tour with new examples.
          Bug fix:
          1. Redress: save file may fail.
          2. Install Bean: some may fail due to missing manifest file. Now, it is treated
          as foreign beans.
          3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
          on the original file, do not need copy to a temporary directory anymore.
          4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
          Now it pick up all availble ones and give warning messages.
          5. Stress: Launch>Save>Cancel generated a null pointer exception.
          Changes:
          1. installLogDatabase has been changed from .zip file to .jar file.
          2. SuperLogging: If the log database is broken, the log methods will not try to
          access the log database. It is consistent with the document now.
          3. SuperLogging will not read system properties now. You can put log database
          parameters in SuperLoggingEJB's deployment descriptor.
          Version 1.10 Feb., 2001
          Enhancement:
          1. Re-written PeekPoke with Save/Restore functions.
          2. New SuperComponent: SuperStress for stress test.
          3. Set a mark at the highlighted line on<font size=+0> the Source Code
          Panel (as a work-a-round for JDK 1.3).</font>
          4. Add support for WebLogic 6.0
          Bug fix:
          1. Uninstall bean does physically delete the jar file now.
          2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
          Version 1.00 Oct., 2000
          Enhancement:
          1. Support Universal server (virtual all EJB servers).
          2. Add Lost and Found for JNDI names, in case you need it.
          3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
          for Envoys which do not support JNDI list).
          Version 0.90: Sept, 2000
          Enhancement:
          1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
          and alike) as input values.
          2. Reworked help documents.
          Bug fix:
          1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
          further time-out.
          2. MDI related bugs under JDK 1.3.
          Version 0.80: Aug, 2000
          Enhancement:
          1. With full-featured SuperLogging.
          Version 0.72: July, 2000
          Bug fix:
          1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
          Version 0.71: July, 2000
          Enhancement:
          1. Re-worked peek algorithm, doing better for concurent use.
          2. Add cacellable Wait dialog, showing Super is busy.
          3. Add Stop button on Peek Panel.
          4. Add undeploy example button.
          Bug fix:
          1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
          1.2 and 1.3
          Version 0.70: July, 2000
          Enhancement:
          1. PeekPoke EJBs without programming.
          Bug fix:
          1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
          Changes:
          1. All changes are backward compatible, but you may need to recompile monitor
          windows defined by you.
          Version 0.61: June, 2000
          Bug fix:
          1. First time if you choose BUFFER as logging device, message will not show.
          2. Fixed LoggingPanel related bugs.
          Version 0.60: May, 2000
          Enhancement:
          1. Add DATABASE as a logging device for persistent logging message.
          2. Made alertInterval configurable.
          3. Made pace for tracing configurable.
          Bug fix:
          1. Fixed many bugs.
          Version 0.51, 0.52 and 0.53: April, 2000
          Enhancement:
          1. Add support to Weblogic 5.1 (support for Logging/Tracing and
          user defined GUI window, not support for regular monitoring).
          Bug fix:
          1. Context sensitive help is available for most of windows: press F1.
          2. Fix installation related problems.
          Version 0.50: April, 2000
          Enhancement:
          1. Use JavaHelp for help system.
          2. Add shutdown functionality for J2EE.
          3. Add support to Weblogic 4.5 (support for Logging/Tracing and
          user defined GUI window, not support for regular monitoring).
          Bug fix:
          1. Better exception handling for null Application.
          Version 0.40: March, 2000
          Enhancement:
          1.New installation program, solves installation related problems.
          2. Installation deploys AceletSuperApp application.
          3. Add deploy/undeploy facilities.
          4. Add EJB and application lists.
          Change:
          1.SimpleMonitorInterface: now more simple.
          Version 0.30: January, 2000
          Enhancement:
          1. Add realm support to J2EE
          2. Come with installation program: you just install what you want
          the first time you run Super.
          Version 0.20: January, 2000
          Enhancement:
          Add support to J2EE Sun-RI.
          Change:
          1. Replace logging device "file" with "buffer" to be
          compliant to EJB 1.1. Your code do not need to change.
          Version 0.10: December, 1999
          Enhancement:
          1. provide SimpleMonitorInterface, so GUI experience is
          not necessary for developing most monitoring applications.
          2. Sortable table for table based windows by mouse
          click (left or right).
          Version 0.01 November., 1999:
          1. Bug fix: An exception thrown when log file is large.
          2. Enhancement: Add tour section in Help information.
          Version 0.00: October, 1999
          Thanks.

How to add License Key For Integration Tool kit For SAP in Linux Server

Dear Experts,
We are Using BO XI R3.1 SP3 Enterprise Version ,Integration Tool Kit For SAP,Live Office.
The Server is Linux Server.
But while generating reports in Infoview it is giving error like ""_check that you are licensed to access SAP Data Source_".
So we came to know that license Key might Expire for Integraton Tool Kit For SAP in Bo Server.
So can you tell me how to add the license key For BO XI R3.1 SP3 Integration Tool Kit For SAP in Linux Server.
Thanks & Regards,
Venkat

On Unix / Linux you should be able to leverage the response from Raphael and change:
Location＝%BOBJDIR%/bobje/data/.bobj/registry/software/business objects/suite 11.5/sap/keycode/.registry
For more information verify the below link
[How do you update the SAP Integration Kit license?;
Regrads
Pardhu

Calling EJB from JSP in SSL Mode

Hi,
I need to call an EJB from JSP in SSL Mode.
How can i do that.
Regards,
S.V.Satish Kumar

In that case you can refer to the following documents:
Using JPA: http://help.sap.com/saphelp_nwce711/helpdata/en/44/eba6292f446c30e10000000a114a6b/frameset.htm
Accessing persistence functionality in EJB 3.0: http://help.sap.com/saphelp_nwce711/helpdata/en/46/307a2a50094f09e10000000a114a6b/frameset.htm
Tell me, if these documents help you. Otherwise, I will search for more information on the topic.
Best regards,
Ekaterina

How to use EJB in JSP...urgent!!!

hello,
i am novice programmer in EJB.
i am using weblogic 6.1 ...
my problem is how to use EJB in jsp page.
my code is as follow..but its not displaying any result.
<%@ page import="javax.naming.InitialContext,
javax.naming.Context,
java.util.Properties,
firstEJB.First,
firstEJB.FirstHome"%>
<%
     long t1 = System.currentTimeMillis();
     System.out.println(t1);
     Properties props = new Properties();
     p.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.TengahInitialContextFactory");
     props.put(Context.PROVIDER_URL, "localhost:7001");
     Context ctx = new InitialContext(props);
     FirstHome home = (FirstHome)ctx.lookup("FirstEJB");
     First bean = home.create();
     String time = bean.getTime();
     bean.remove();
     ctx.close();
     long t2 = System.currentTimeMillis();
%>
<html>
     <head>
          <style>p { font-family:Verdana;font-size:12px; }</style>
     </head>
     <body>
          <p>Message received from bean = "<%= time %>".<br>Time taken :
          <%= (t2 - t1) %> ms.</p>
     </body>
</html>
please tell me the solution.

Hi, I don't know if it may be the cuase of your problems, but you should narrow the Object obtained doing the lookup, like this:
FirstHome home = (FirstHome) PortableRemoteObject.narrow(ctx.lookup("FirstEJB"), FirstHome.class);

How to master good design with EJB and JSP?

I use JSP to calling EJB. But the .jsp file is complex and it's difficult to maintain...I just want to work higher efficent with EJB,JSP and JavaBean. I want to know is there a good design with EJB and JSP? and is there any good material about MVC for EJB,JSP and JavaBean?

You should read the J2EE blueprint available on this website. Better download the PDF, and print it for yourself so you can read it anytime.

HOW can I call EJB with JSP?

Hi, I'm working with JSP and want to include some EJB. I dont know how can I access EJB through JSP. I dont know if I use the right code in JSP for calling EJB. Did someone know how to use that? Can someone tell me if is the right code in JSP in my example?
Thanks, Kristjan
THIS IS THE JSP: (useejb.jsp)
<%@ taglib uri="http://xmlns.oracle.com/j2ee/jsp/tld/ojsp/ejbtaglib.tld" prefix="EJB" %>
<%@ page import="mypackage1.MySessionEJB" %>
<%@ page import="mypackage1.MySessionEJBHome" %>
<%@ page import="mypackage1.impl.MySessionEJBBean" %>
<HTML>
<head><TITLE>USEBEAN</TITLE></head>
<body>
<EJB:useHome id="mySessionEJBHome" type="mypackage1.MySessionEJBHome" location="java:comp/env/ejb/mySessionEJB" local="false" />
<EJB:useBean id="mySessionEJBBean" type="mypackage1.impl.MySessionEJBBean" local="false">
<EJB:createBean instance="<%=mySessionEJBHome.create() %>" />
</EJB:useBean>
<%= mySessionEJBBean.calc() %>
</body>
</html>
THIS IS THE EJB CODE:(MySessionEJBBean.java)
package mypackage1.impl;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import java.lang.String.*;
public class MySessionEJBBean implements SessionBean
public void ejbCreate(){}
public void ejbActivate(){}
public void ejbPassivate(){}
public void ejbRemove(){}
public void setSessionContext(SessionContext ctx){}
public String calc(String value)
return value + value;
public String zanka(String x)
return x;
(MySessionEJB.java)
package mypackage1;
import javax.ejb.EJBObject;
import java.rmi.RemoteException;
public interface MySessionEJB extends EJBObject
public String calc(String value) throws RemoteException;
String zanka(String x) throws RemoteException;
(MySessionEJBHome.java)
package mypackage1;
import javax.ejb.EJBHome;
import java.rmi.RemoteException;
import javax.ejb.CreateException;
public interface MySessionEJBHome extends EJBHome
public MySessionEJB create() throws RemoteException, CreateException;
}

You might want to look at using a Java Bean wrapper, this can be done automically using WebSphere. It creates what is called an access bean which the JSP imports.
HTH,
J.Clancey

Integration tool

What is the Diff between B1i and iBOLT tool ?

Hi Chetan,
B1iP is the integration technology designed by SAP for integration between SAP R/3, SAP B1, and a variety of other sources. iBolt is also an integration tool, developed by Magic Software.
To the best of my knowledge, the following is a quick list of differences between B1iP and iBolt:
1) B1iP is provided free of cost by SAP, iBolt has its own licensing model and pricing.
2) B1iP is more suited for developing generic integration products, while iBolt is more suited for developing projects based on individual customer requirements.
3) iBolt has existing connectors for a variety of sources outside of SAP, including Salesforce and JDEdwards, such connectors would have to be developed for B1iP.
4) B1iP's allows you to develop integration scenarios easily on top a generic framework, or develop a custom framework based on your requirements. I'm not sure how the same would be accomplished through iBolt.
Possibly someone more familiar with iBolt can comment more on it.
HTH,
Dhruv

JSP WYSIWYG Tools

Hello all,
What's the deal with JSP WYSIWYG tools? Is Dreamweaver still the only option? I have been searching for a way to rapidly develop JSP pages. I want to "drag and drop" beans onto the pages. I did see IBM's WS Studio, but it's a huge download, and I think it is expensive. I tried to find a plugin for eclipse, but the closest plugin to what I would like to use is MyEclipse workbench, but it does not seem to have the visual "drag and drop".
This may sound bad to diehard Java fans, but Microsoft's Visual Studio has a great WYSIWYG tool for C# ASP.NET!
MS Visual Studio is also expensive, but my company has an MSDN subscription which includes VS, so I could use that for free, but I would like to stay true to my Java roots and use a Java product!
Someone please help me. Any suggestions would be great.
Thanks.
-Rob Corbin

What is wrong with Dreamweaver.Another new tool is coming for developing jsp pages from SUN called Creator..U can try it that.
It is not yet realesed,a good tool for developing web pages.
Anand

ODI-1241: Oracle Data Integrator tool execution fails.

Hi
I'm getting the following error while running the OdiOSCommand command. I'm running dos2unix command to convert text files from dos to unix format.
Application tier is on a different host to the ODI setup. Getting the following error. Please help resolve this issue.
Error : ODI-1226: Step OdiOSCommand fails after 1 attempt(s).
ODI-1241: Oracle Data Integrator tool execution fails.
Caused By: com.sunopsis.dwg.function.SnpsFunctionBaseException: ODI-30038: OS command returned 1.

The issue was with the value set for the OUTPUT_DIR variable. It was pointing to the wrong location.
After setting it correctly the package completed successfully.
Thanks for all your replies.
To anwser your question. We are finding junk data and need to run the command to remove them from the input files which are coming from a different source.
Edited by: user761125 on Jun 3, 2012 11:38 PM

What r the integration tools used in SAP

Hi all,
Please let me know What r the integration tools used in SAP

BAPI - These are published programs which is used to upload data i
nto SAP system.
BADI - This is a program enhancement technique. SAP pr
ovides BADI openings in the standard programs. You need to search for the s
uitable BADI as ur requirement and then do the coding and plug in the progr
am.
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
Afrasyab

EJB to JSP Integration Tool

Similar Messages

Maybe you are looking for