Abstract: A method, apparatus, and computer instructions are provided for implementing container managed uses, ownerships, and references in an enterprise JavaBean™ environment. A user may specify a uses, ownership, reference relationships between entity beans and sessions in a deployment descriptor file. When the file is processed, the present embodiment generates methods on the entity beans and allows the container to recognize the relationships, such that the user may access the session beans based on the specified relationships.

Abstract: A method, apparatus, and computer instructions are provided for implementing container managed uses, ownerships, and references in an enterprise JavaBean™ environment. A user may specify a uses, ownership, reference relationships between entity beans and sessions in a deployment descriptor file. When the file is processed, the present embodiment generates methods on the entity beans and allows the container to recognize the relationships, such that the user may access the session beans based on the specified relationships.

Abstract: Mapping Enterprise Java Bean (“EJB”) attributes to database schema including providing a first metamap including one or more abstracted variable characteristics of a first database schema and creating from the first metamap a second metamap for a second database schema including varying one or more of the abstracted variable characteristics to conform to the second database schema. Typical embodiments also include synchronizing, in response to methods invoked on the EJB and in dependence upon the second metamap, the state of the EJB with a persistent data store having the second database schema. In typical embodiments, synchronizing the state of the EJB with a persistent data store having the second database schema also includes creating records, updating records, and deleting records in the persistent data store.

Abstract: A system and method for navigating relationships between beans using filters and container managed relationships are provided. With the system and method, filters are specified in the relationship definition of a deployment descriptor of a bean. The filters generate additional predicates to the WHERE clauses in SQL SELECT statements generated based on the contents of the deployment descriptor. Moreover, these filters may be defined such that method parameters may be passed into the resulting deployed code to thereby make them more flexible. Therefore, with the system and method, rather than defining filters programmatically in methods of a bean's implementation class, filters are defined declaratively in the deployment descriptor of the bean. Since these filters are specified in the deployment descriptor of the bean, they are accessible to clients of the bean through the local interface.

Abstract: Exemplary methods, systems, and products are described for normalized measurement of computer resource usage by use of benchmarks of performance that reduce the complexity of calculating customer charges for use of computer resources in a hosted environment. More particularly, exemplary methods, systems, and products are described for normalized measurement of computer resource usage that include calculating a normalization coefficient for a computer resource of a type, measuring actual usage of the resource by a user, and calculating normalized usage in dependence upon the normalization coefficient and the actual usage. Calculating a normalization coefficient is typically carried out in dependence upon a benchmark value for the computer resource and upon benchmark values for a multiplicity of computer resources of the type.

Abstract: A method, apparatus, and computer instructions are provided for implementing container managed uses, ownerships, and references in an enterprise JavaBean™ environment. A user may specify a uses, ownership, reference relationships between entity beans and sessions in a deployment descriptor file. When the file is processed, the present embodiment generates methods on the entity beans and allows the container to recognize the relationships, such that the user may access the session beans based on the specified relationships.

Abstract: A method, apparatus, and computer instructions for implementing container managed streams in an enterprise JavaBean™ environment. Uses, ownership, reference relationships between entity beans and sessions are specified in a deployment descriptor file. When an input data stream is received for a batch job, the file is processed and a method is generated on the entity beans, wherein the method allows for creating a container managed ownership entity representing a stream object for the input data stream, associates an entity bean with the stream, and returns the last unprocessed object in the stream to the user. A method may also be generated on the entity beans for creating a stream object for an output data stream, associating an entity bean with the stream, rerouting an object to the stream object, and appending the stream object to the end of the batch job queue.

Abstract: An improved method, apparatus, and computer instructions for creating and running batch jobs in an object oriented environment, such as a J2EE environment. A request to execute a batch job is received. A deployment descriptor file is processed to identify a batch bean to be invoked. This batch job session bean processes the request, parses deployment descriptor file that comprises definitions of relationships between other helper classes, entity and session beans. The identified batch bean is invoked to execute the batch job step in the order described in the deployment descriptor applying checkpoints at intervals specified in the descriptor.

Abstract: Mapping Enterprise Java Bean (“EJB”) attributes to database schema including providing a first metamap including one or more abstracted variable characteristics of a first database schema and creating from the first metamap a second metamap for a second database schema including varying one or more of the abstracted variable characteristics to conform to the second database schema. Typical embodiments also include synchronizing, in response to methods invoked on the EJB and in dependence upon the second metamap, the state of the EJB with a persistent data store having the second database schema. In typical embodiments, synchronizing the state of the EJB with a persistent data store having the second database schema also includes creating records, updating records, and deleting records in the persistent data store.

Abstract: Methods, systems, and media to automatically deploy an, e.g., a JS2EE file between environments are disclosed. Embodiments include hardware and/or software for selecting one or more applications in an original system for export. The applications along with their corresponding application data, configuration data, and descriptor files, are compressed into one or more archive files such as Enterprise Archives (EARs). Variable configuration data associated with the target environment is identified so the values of the variable configuration data can be adapted for the target environment. Then, the target environment is adapted for installation of the application and the application is installed in the target environment. Advantageously, this deployment of the application may reduce the chance of user error, require less J2EE knowledge and script maintenance, and complete faster than deployments effected manually.

Abstract: Systems and methods for selectively deploying enterprise software are provided. For each deployable software component (exemplified by, but not limited to Enterprise JavaBeans, or “EJB”s) in an preselected input archive file, interfaces of deployable software components identified in a first and second descriptor file in, respectively, the preselected input archive file and a preselected output archive file are compared. If tan interface miscompares for a first deployable software component, the first deployable software component is tagged. Additionally, if an interface miscompares for a second deployable software the second deployable software component is also tagged. Each tagged deployable software component is deployed.