58 results about "Enterprise Java Bean" patented technology

A system for implementing voice services can include at least one virtual machine, such as a Java 2 Enterprise Edition (J2EE) virtual machine. The virtual machine can include a bean container for handling software beans, such as Enterprise Java Beans. The bean container can include a voice browser bean. The voice browser bean can include a VoiceXML browser.

Dynamic Multi-sourced Persisted Enterprise Java Bean (EJB) instances are dynamically created on a J2EE compliant Application Server to access data contained in multiple data source systems. This Dynamic Multi-sourced Persisted EJB is a general class responsible for dynamically aggregating source system information and securing it based on a Context definition. Individual EJB attributes that include mapping, caching and security definitions are mapped to individual pieces of data in source systems by the Context definition. A Context definition can be reloaded during execution as desired. Applications can access the Dynamic Multi-sourced Persisted EJB directly, or use a Session EJB to create a static interface to the dynamically mapped, cached and secured data. Using an attribute securing element, a security engine enforces access requirements on a system-wide basis.

An invention is disclosed managing the replicated and migration capable state for an enterprise Java bean (EJB) application. The invention includes executing a Java application on a server that includes an entity bean. In addition, a replicated state manager is executed that includes program instructions for managing an in-memory state of the Java application, and program instructions for replicating the in-memory state of the Java application to a replicated state server. The replicated state server can be a memory replicated state server, or a disk replicated state server. To facilitate application state management, embodiments of the present invention store states of the entity beans objects using state objects, which are updated in response to changes in the state of the application. Hence, the embodiments of the present invention define a logical separation between the application and the state objects.

A system or method enables a two tier computer application to operate in a three tier computer environment without specific programming for the three tier environment. Such a system or method receives a database call at a computer system and maps the database call to a general programming language call of a computer application. The general programming language call is executed to invoke functions of the computer application that correspond to functions of the database call. The general programming language call may be an Enterprise Java Bean (EJB) call. An application server receives the database call and maps the database call to the general programming language call. In response to executing the general programming language call, the application server generates a second database call to the database that may either correspond directly or indirectly to the database call received at the application server. The database calls may both be SQL calls. The general computer programming language may have EJB components that are analyzed to determine the correspondence between the database elements and the elements of the components that access the database elements. Methods of the EJB components may be identified for use in determining the correspondence. The methods may be identified by searching for a method of the form <command prefix>XXX, where the prefix is a “get” or “set” method.

A method and apparatus for generating a service data object based service pattern for an EJB model is provided. Definitions of session bean façade, SDOs, and queries are defined in entity beans. When the definitions are processed, SDOs, related SDOs, and queries for SDOs are added to the session bean façade. At run time, a client may manipulate the SDOs and apply changes to the SDOs via a mediator obtained from a mediator cache. The mediator persists the SDOs to a data graph without interfering the entity bean.

Exemplary methods, systems, and products are disclosed for managing transactions for Enterprise Java Beans (“EJBs”) that typically include receiving in an EJB container a plurality of container managed transactions for EJB components having container managed persistence. Each transaction typically comprises at least one computer program instruction affecting a data value of an EJB component, and typical embodiments include combining two or more of the transactions into a single transaction. Typical embodiments also include combining two or more of the instructions into a single instruction. Embodiments may include maintaining, by an EJB container, a pool of open transactions.

A system and method are provided for communicating with a Structured Query Language (SQL) statement generator. In an embodiment, an SQL mapper factory receives an object-relational mapping schema to define a mapping between one or more persistence fields of one or more Enterprise Java Beans (EJBs) and one or more tables of a database. An SQL mapper implementation may be selected based, at least in part, on a value specified in a properties file. In an embodiment, the SQL mapper implementation may be generated based, at least in part, on the object-relational mapping schema.

A method and system for injecting exceptions into a JAVA enterprise application during execution of the JAVA enterprise application is disclosed. The Java enterprise application includes multiple Enterprise JAVA Bean (EJB) classes. The EJB classes include one or more EJB methods. Each EJB is scanned for exceptions, and corresponding interface points of the EJB. The exceptions are automatically injected at the corresponding interface points based on scanning the EJB. The exceptions are then thrown to callers of the EJB methods. The exceptions are thrown before beginning execution of business logic of the EJB methods. Finally, the response of the JAVA enterprise application to the injected exceptions is analyzed.

The present invention discloses a method and an arrangement for using a platform independent model comprising one or more state machines, and a generic middleware platform for orthogonally mapping the platform independent model to a source code and/or byte code platform, where an asynchronic behaviour is shown on the modelling level, and the source code or byte code level is achieved using message oriented middleware application API adapted for message exchange between clients both in point to point and publish/subscribe messaging regime and, persistency for one or more state machines is achieved using one or more modules adapted for database transactions, where the modules may handle concurrent access from multiple clients to the database.

Converting SQL databases to Enterprise JAVA Beans, when using conventional methods, has become a tedious, error-prone, time-consuming task. The invention, called BeanGrinder, automates the task so that a process hitherto taking days or weeks can be accomplished in matters of minutes. The user selects the databases to be converted, the tables for the resulting data, the target location, and the application server. Then, the user runs the BeanGrinder before running two batch command file programs to complete the task. The user is relieved of the need to write special conversion programs for every database to be converted.

This application is for an audio message-driven customer interaction queuing system for retail, help desk or any public web page in a support context, allowing web page visitors to utter questions into a browser-resident recorder application similar to a Walkie-Talkie. These questions then queue along with originating web page information and are distributed to customer service agents. These agents can then research the question, using the web page as reference, and respond with an audio message, played upon the recorder application by the user after some brief service interval. The invention includes client, server and agent elements. The Client resides in a standard browser on a PC. The Client as initially instantiated consists of a Macromedia Flash interface driving an ActiveX control and JavaScript using audio encoding/decoding codecs. The Server consists of Java Servlets, Enterprise Java Beans, a web and application server and generic database technology. The Agent consists of a browser partitioned into areas to accommodate customer URL viewing, Connection Management (to service multiple customers concurrently), and a Client for message playback/record/send functions.

Single port initial context access to an Enterprise Java Bean (“EJB”) including providing EJBs, including an EJB used by a client of a Java application; deploying the Java application, including deploying, at a fixed node and port, an application server for initial context lookup; selecting through the application server a home object for the EJB used by the client; and instantiating through the home object the EJB used by the client. Providing EJBs typically includes providing database records representing EJBs, each of which includes data describing the name of an EJB, a version of the EJB, and a node and port where an instance of the EJB may be deployed. Selecting a home object typically includes creating a context object, where the context object includes a providerURL, and the providerURL includes the node and port of the application server.

The present invention relates to a description and implementation method of ThreadBean in an Enterprise Java Bean (EJB) container. In the description and implementation method of ThreadBean in an EJB (Enterprise Java Bean) container, the ThreadBean is defined using EJB to which an independent thread is allocated such that looping is performed while a message entering a determined message target is processed or a business logic periodically driven to perform a specific work is processed.

A method of interfacing with a remote engine can include the step of instantiating at least one stateful bean, such as a stateful session Enterprise Java Bean. For each stateful bean instance, an engine can be allocated. Each stateful bean instance can be associated with an allocated engine, where each stateful bean instance can operate as an interface for accessing the associated engine. Each associated stateful bean can then be added to a bean pool so that bean instances in the bean pool are available for handling requests.

A system and method are provided for a query language mapping architecture. In an embodiment, the query language mapping architecture includes an Enterprise Java Bean (EJB) interpreting layer to receive one or more EJB persistence requests and to translate the one or more EJB persistence requests to command sequences. In an embodiment, the query language mapping architecture may also include a Structured Query Language (SQL) assembly layer to receive the command sequences from the EJB interpreting layer and to assemble one or more SQL statements based, at least in part, on the command sequences.

An object oriented query such as an enterprise java bean query is translated into a corresponding relational query by identifying an inter-hierarchal relationship relating two or more object oriented hierarchies; identifying a source object oriented hierarchy of the inter-hierarchal relationship; mapping the source object oriented hierarchy into corresponding source relational tables; building a source series of joins between the source relational tables, the source series being ordered in a top-down order from a root of the source object oriented hierarchy; identifying a target class of the inter-hierarchal relationship; mapping the target object oriented hierarchy into corresponding target relational tables; building a target series of joins between the target relational tables, the target series comprising a first target series and a second target series, the first target series corresponding to the target class, a root of the target object oriented hierarchy, and intervening nodes between the target class and the root of the target object oriented hierarchy, and the second target series corresponding to nodes in leaves of the target object oriented hierarchy located below the target class; and combining the source series of joins and the target series of joins into the corresponding relational query. For a query selection based upon a plurality of relationships between the object oriented hierarchies, the steps may be repeated for each of the plurality of relationships. The combined series of joins may be further reordered by recursively finding a join relationship between a current node and a preceding node in the combined series of joins. To improve performance, a join above a target of a relationship is built as an inner join, and a join below the target of relationship is built as an outer join.

The invention relates to a method for managing a network comprising a plurality of network components, and to a corresponding network management system. According to the invention, information about the network is persistently stored by filing object references in a database. Object references are used for the unambiguous identification of an object, and an object is a program representation of a network component, containing an executable program routine which, when called, emits data containing the information to be stored, as a return value. The program routine can be localized by-means of the respective filed object reference. The persistent storage of network management data by means of dynamic object references enables a network management program to access novel types or categories of objects, during its run-time, without necessitating an upgrade or a service interruption. The objects are preferably JAVA objects or EJB (Enterprise Java Beans) objects. Preferably, the implementation is carried out in CORBA. The database containing the object references is preferably a relational database.

Features of Enterprise Java Bean (EJB), Enterprise Printing Bean (EPB), JAVA, J2EE, and document authoring are combined to enable a robust enterprise printing architecture. A Java object encapsulates a print job specification and provides a framework enabling access control to print jobs as well as providing audit capabilities. Print control languages can be specified using methods provided by the Java object. Actual process implementation can be supplied via a server enabling another layer of security and control. A user wanting to securely print a job supplies appropriate credentials to the print job bean to gain access to the content and print server credentials allow printing of the print job. The EJB API is extendable to enable all of the J2EE capabilities found on standard EJBs to be applied to print Jobs. Further, a new Java API provides a more powerful page description language than that found in other printing languages.

A system and method are provided for interacting with a persistence layer. In an embodiment, a persistence layer may receive a representation of Enterprise Java Bean (EJB) metadata. The persistence layer may determine whether the representation of Enterprise Java Bean (EJB) metadata is compatible with a version of the EJB specification. In an embodiment, a representation of an Object-Relational (OR) mapping schema may be generated based, at least in part, on the representation of EJB metadata.

A system to load test a computer system is provided. The system comprises a test script to generate transactions including a basis transaction, the basis transaction operable to initiate a conversation with a stateful enterprise java bean, and a non-basis transaction. The system also comprises a forecast and a transaction iteration calculator, the transaction iteration calculator operable to determine how often the non-basis transaction executes relative to the basis transaction. For a non-basis transaction having a forecast less than the forecast of the basis-transaction, the non-basis transaction executes once if the number given by a randomly selected number between zero and the basis transaction forecast is less than the forecast of the non-basis transaction forecast and zero times otherwise. For a non-basis transaction having a forecast more than the forecast of the basis-transaction, the non-basis transaction may execute according to another calculation. A script controller is also provided.