Abstract: Disclosed techniques relate to enforcing table dependencies for a database schema when tables are maintained by separate database instances. In some embodiments, a database system generates configuration data based on foreign key constraints for multiple database tables. In some embodiments, in response to a request from an application server to access data, the database system accesses the configuration data (where the configuration data specifies a relationship between a field of a child table and a field of a parent table and at least a portion of the parent table is stored in a different database instance than the child table) and determines whether the request satisfies the specified relationship. In some embodiments, enforcing dependencies at an intermediate orchestration layer maintained by the database systems allows applications to submit requests without considering table dependencies.

Abstract: Among other things, embodiments of the present disclosure relate to distributing the determination of target audience lists across multiple clusters of nodes. Other embodiments may be described and/or claimed.

Abstract: Among other things, embodiments of the present disclosure relate to distributing the determination of target audience lists across multiple clusters of nodes. Other embodiments may be described and/or claimed.

Abstract: Disclosed techniques relate to enforcing table dependencies for a database schema when tables are maintained by separate database instances. In some embodiments, a database system generates configuration data based on foreign key constraints for multiple database tables. In some embodiments, in response to a request from an application server to access data, the database system accesses the configuration data (where the configuration data specifies a relationship between a field of a child table and a field of a parent table and at least a portion of the parent table is stored in a different database instance than the child table) and determines whether the request satisfies the specified relationship. In some embodiments, enforcing dependencies at an intermediate orchestration layer maintained by the database systems allows applications to submit requests without considering table dependencies.

Abstract: A system and method can provide a scalable data storage in a middleware environment. The system can include a cluster of replicated store daemon processes in a plurality of processing nodes, wherein each machine node can host a replicated store daemon process of the cluster of replicated store daemon processes. Additionally, the system can include one or more replicated stores associated with an application server the processing node. The replicated store daemon cluster can persist data from a replicated store to another node, the other node also being associated with the replicated store daemon cluster. The system and method can additionally support a messaging service in a middleware environment. The messaging service can use the replicated store to store a copy of a message in the local processing node and on another processing node associated with the same replicated store daemon cluster.

Abstract: In accordance with an embodiment, a system and method provides a dynamic clustered messaging service in an application server environment. A cluster includes one or more servers operating within the application server environment and is configured to vary a number of the servers based on a service load of applications running on the cluster. The number also varies based on failure and restart of the servers. A messaging service for communicating messages between components of the applications includes instances of messaging service artifacts running on the one or more servers. A placement engine operating on the cluster is configured to migrate the instances of messaging service artifacts between the one or more servers based on a set of rules as the number of the one or more servers in the cluster expands and contracts and as a number of the instances of messaging service artifacts expands and contracts.

Abstract: In accordance with an embodiment, a system and method provides a dynamic clustered messaging service in an application server environment. A cluster includes one or more servers operating within the application server environment and is configured to vary a number of the servers based on a service load of applications running on the cluster. The number also varies based on failure and restart of the servers. A messaging service for communicating messages between components of the applications includes instances of messaging service artifacts running on the one or more servers. A placement engine operating on the cluster is configured to migrate the instances of messaging service artifacts between the one or more servers based on a set of rules as the number of the one or more servers in the cluster expands and contracts and as a number of the instances of messaging service artifacts expands and contracts.

Abstract: A system and method can provide a scalable data storage in a middleware environment. The system can include a cluster of replicated store daemon processes in a plurality of processing nodes, wherein each machine node can host a replicated store daemon process of the cluster of replicated store daemon processes. Additionally, the system can include one or more replicated stores associated with an application server the processing node. The replicated store daemon cluster can persist data from a replicated store to another node, the other node also being associated with the replicated store daemon cluster. The system and method can additionally support a messaging service in a middleware environment. The messaging service can use the replicated store to store a copy of a message in the local processing node and on another processing node associated with the same replicated store daemon cluster.

Abstract: The present invention enables messaging service users to programmatically and administratively control the system's behavior in the event of an external resource failure. A destination pause/resume feature enables the user to “pause” and “resume” the production and consumption of messages, that are newly produced or produced as a result of “in flight work” completion, on a given destination or all the destinations hosted by a single messaging service server programmatically. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Abstract: Disclosed herein is a system and method for client interoperability. In one embodiment, a method for client interoperability comprises establishing a network connection between a client and a proxy. The client requests a connection factory from the proxy. The proxy then obtains the connection factory from an application server using a Java Naming and Directory Interface (JNDI). Using the connection factory, a connection to a connection host from the client is created. When the client sends a message, the proxy receives the message and routes the message to a destination server. Similarly, when the client receives a message, the proxy receives the message from a destination server and passes the message to the client. The client can be specifically configured to extend JMS operability to a desired language. In one embodiment the client is a .NET client.

Abstract: Embodiments provide mechanisms and methods for configuring a messaging component of an application. These mechanisms and methods can enable embodiments to configure message objects, i.e., software objects relating to messaging, with the messages. The ability of embodiments to configure message objects with messages can enable application developers, for example, to package custom code, for example, as message objects combined with messages and/or parameters into an archive convenient for distributing to one or more servers, clients or other computational entities. The distributed archive can be readily accessed by these computational entities, enabling embodiments to achieve improved configuration of the messaging component of a distributed system.

Abstract: Disclosed herein is a system and method for client interoperability. In one embodiment, a method for client interoperability comprises establishing a network connection between a client and a proxy. The client requests a connection factory from the proxy. The proxy then obtains the connection factory from an application server using a Java Naming and Directory Interface (JNDI). Using the connection factory, a connection to a connection host from the client is created. When the client sends a message, the proxy receives the message and routes the message to a destination server. Similarly, when the client receives a message, the proxy receives the message from a destination server and passes the message to the client. The client can be specifically configured to extend JMS operability to a desired language. In one embodiment the client is a .NET client.

Abstract: A Web-based interface for using a mark-up language (JMSML) to access JMS/JMX interfaces. The invention comprises a Web Application (Servlet) interface that enables the JMSML user to enter and execute the JMSML program via a Web browser. The interface provides a simple form, wherein the user can type in the JMSML commands and specify the server's connection information (for example the URL) on which the user wants to execute the JMSML commands. This enables the user to perform remote administration, monitoring and management of a server's JMS subsystem, from anywhere on a wide area network or the Internet.

Abstract: A system and method for Java Message Service Mark-up Language (JMSML). The system includes an extensible engine that performs the task of parsing input data and converting it to Java JMS/JMX API, and then executes the JMSML program.

Abstract: A command-line interface for using a mark-up language (JMSML) to access JMS/JMX interfaces. The invention comprises a system including a Java stand alone client, acting as the command line interface to execute the JMSML program. The user can specify the JMSML program name, location along with the server's connection information (for example the URL) as command line parameters. This interface then validates these parameters and executes the given JMSML program. This interface requires the JMSML engine JAR file in the CLASSPATH of the user's execution environment.

Abstract: An integrated development environment for using a mark-up language (JMSML) to access JMS/JMX interfaces. The invention comprises a JMSML Integrated Development Environment in which a Graphical User Interface (GUI) is provided to enable the user to develop JMSML application. Using this IDE, the user can Edit, Manage and Execute and see the execution results of the JMSML program all within this IDE. The IDE provides the user two ways to write the JMSML program. One way is to type in the JMSML XML code using the Source Editor and another way is to visually assemble the JMSML components from the GUI toolbars provides in the Design Editor that in turn will generate the JMSML XML source code.

Abstract: The present invention enables messaging service users to programmatically and administratively control the system's behavior in the event of an external resource failure. A destination pause/resume feature enables the user to “pause” and “resume” the production and consumption of messages, that are newly produced or produced as a result of “in flight work” completion, on a given destination or all the destinations hosted by a single messaging service server programmatically. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Abstract: Embodiments provide mechanisms and methods for configuring a messaging component of an application. These mechanisms and methods can enable embodiments to configure message objects, i.e., software objects relating to messaging, with the messages. The ability of embodiments to configure message objects with messages can enable application developers, for example, to package custom code, for example, as message objects combined with messages and/or parameters into an archive convenient for distributing to one or more servers, clients or other computational entities. The distributed archive can be readily accessed by these computational entities, enabling embodiments to achieve improved configuration of the messaging component of a distributed system.

Abstract: A Web-based interface for using a mark-up language (JMSML) to access JMS/JMX interfaces. The invention comprises a Web Application (Servlet) interface that enables the JMSML user to enter and execute the JMSML program via a Web browser. The interface provides a simple form, wherein the user can type in the JMSML commands and specify the server's connection information (for example the URL) on which the user wants to execute the JMSML commands. This enables the user to perform remote administration, monitoring and management of a server's JMS subsystem, from anywhere on a wide area network or the Internet.

Abstract: An integrated development environment for using a mark-up language (JMSML) to access JMS/JMX interfaces. The invention comprises a JMSML Integrated Development Environment in which a Graphical User Interface (GUI) is provided to enable the user to develop JMSML application. Using this IDE, the user can Edit, Manage and Execute and see the execution results of the JMSML program all within this IDE. The IDE provides the user two ways to write the JMSML program. One way is to type in the JMSML XML code using the Source Editor and another way is to visually assemble the JMSML components from the GUI toolbars provides in the Design Editor that in turn will generate the JMSML XML source code.