Abstract: A method, apparatus and program product facilitate the collaborative development of an algorithm by, in part, displaying an algorithm associated with a performance attribute, and receiving user input relating to the algorithm from a plurality of networked users. The performance attribute of the algorithm may be automatically modified based on the user input. The modified performance attribute may be displayed to the plurality of networked users. A query may be received from a user interested in the algorithm. In response to the user query, the algorithm may be located from among a plurality of algorithms. For instance, the algorithm may be located from among the plurality of algorithms by matching the performance attribute to a criterion of the user query. Alternatively or additionally, the algorithm may be located by matching the performance attribute to a profile of the user submitting the user query.

Abstract: An apparatus, system, and storage medium that in an embodiment receive a key parameter from a container-managed persistent bean, determine that the container-managed persistent bean is associated with a non-relational data store, creating a web service input message with the key parameter, and invoke a web service function with the web service input message to interface with a non-relational data store. The determination that the container-managed persistent bean is associated with a non-relational data store may be based on deployment description extension settings specified by a bean assembler. In this way, a container-managed persistent bean may be used to access a non-relational data store.

Abstract: A computer implemented method, data processing system, and computer program product for providing a generic sequencing service for ordering processing requests in a scalable business integration environment. When a request is received at a sequencing component, the operation specified in the request is identified. A determination is then made as to whether to sequence the operation according to a sequencing specification. If the operation is to be sequenced, key information of the operation is classified according to the sequencing specification. A lock on the request is then requested using the operation and the key information. Responsive to the lock being granted, a determination is then made as to whether the request is synchronous or asynchronous. If the request is synchronous, the target service component is invoked synchronously. If the request is asynchronous, the target service component is invoked asynchronously.

Abstract: A method, apparatus and program product facilitate the collaborative development of an algorithm by, in part, displaying an algorithm associated with a performance attribute, and receiving user input relating to the algorithm from a plurality of networked users. The performance attribute of the algorithm may be automatically modified based on the user input. The modified performance attribute may be displayed to the plurality of networked users. A query may be received from a user interested in the algorithm. In response to the user query, the algorithm may be located from among a plurality of algorithms. For instance, the algorithm may be located from among the plurality of algorithms by matching the performance attribute to a criterion of the user query. Alternatively or additionally, the algorithm may be located by matching the performance attribute to a profile of the user submitting the user query.

Abstract: A method, that in an embodiment receives a key parameter from a container-managed persistent bean, determines that the container-managed persistent bean is associated with a non-relational data store, creating a web service input message with the key parameter, and invokes a web service function with the web service input message to interface with a non-relational data store. The determination that the container-managed persistent bean is associated with a non-relational data store may be based on deployment description extension settings specified by a bean assembler. In this way, a container-managed persistent bean may be used to access a non-relational data store.

Abstract: An apparatus, system, and storage medium that in an embodiment receive a key parameter from a container-managed persistent bean, determine that the container-managed persistent bean is associated with a non-relational data store, creating a web service input message with the key parameter, and invoke a web service function with the web service input message to interface with a non-relational data store. The determination that the container-managed persistent bean is associated with a non-relational data store may be based on deployment description extension settings specified by a bean assembler. In this way, a container-managed persistent bean may be used to access a non-relational data store.

Abstract: A computer implemented method, data processing system, and computer program product for providing a generic sequencing service for ordering processing requests in a scalable business integration environment. When a request is received at a sequencing component, the operation specified in the request is identified. A determination is then made as to whether to sequence the operation according to a sequencing specification. If the operation is to be sequenced, key information of the operation is classified according to the sequencing specification. A lock on the request is then requested using the operation and the key information. Responsive to the lock being granted, a determination is then made as to whether the request is synchronous or asynchronous. If the request is synchronous, the target service component is invoked synchronously. If the request is asynchronous, the target service component is invoked asynchronously.

Abstract: A generic lock manager service is provided which allows locks and lock requests to be recovered across system failures and restarts. When a lock request that includes a request to isolate a particular data object is received, the lock manager service examines a lock request queue to determine if the queue contains a second lock request for the data object specified in the lock request. If no second lock request is present, a sequence identifier is assigned to the lock request indicating a lock request processing order for the data object specified in the lock request, and the lock request is persisted in a persistent storage. If a second lock request is present, a maximum sequence identifier of all lock requests directed to the data object is identified. The next higher sequence identifier is assigned to the lock request and the lock request is also persisted in a persistent storage.

Abstract: A framework for use with object-oriented programming systems provides a common message processing system structure that can be placed on any OOP platform and be configured to support any e-mail message protocol standard or specific mail server function. The framework defines an e-mail message as a number of distinct objects, each of which contains information that describes some portion of the message. All messages received by a system in which the framework is implemented are defined on this core object structure. Another set of objects and methods define the processing steps required for a mail server to process a message. A message is received as a class of message objects, which are assigned a message type that determines the subsequent processing steps to which the message object is subjected. As a message is processed, the objects of which it is comprised are changed, so that the message processing can be interrupted and then resumed without loss or duplication of processing steps.

Abstract: A framework for use with object-oriented programming systems provides a common message processing system structure that can be placed on any OOP platform and be configured to support any e-mail message protocol standard or specific mail server function. The framework defines an e-mail message as a number of distinct objects, each of which contains information that describes some portion of the message. All messages received by a system in which the framework is implemented are defined on this core object structure. Another set of objects and methods define the processing steps required for a mail server to process a message. A message is received as a class of message objects, which are assigned a message type that determines the subsequent processing steps to which the message object is subjected. As a message is processed, the objects of which it is comprised are changed, so that the message processing can be interrupted and then resumed without loss or duplication of processing steps.

Abstract: A framework for use with object-oriented programming systems provides a common message processing system structure that can be placed on any OOP platform and be configured to support any e-mail message protocol standard or specific mail server function. The framework defines an e-mail message as a number of distinct objects, each of which contains information that describes some portion of the message. All messages received by a system in which the framework is implemented are defined on this core object structure. Another set of objects and methods define the processing steps required for a mail server to process a message. A message is received as a class of message objects, which are assigned a message type that determines the subsequent processing steps to which the message object is subjected. As a message is processed, the objects of which it is comprised are changed, so that the message processing can be interrupted and then resumed without loss or duplication of processing steps.

Abstract: A framework for use with object-oriented programming systems provides a common message processing system structure that can be placed on any OOP platform and be configured to support any e-mail message protocol standard or specific mail server function. The framework defines an e-mail message as a number of distinct objects, each of which contains information that describes some portion of the message. All messages received by a system in which the framework is implemented are defined on this core object structure. Another set of objects and methods define the processing steps required for a mail server to process a message. A message is received as a class of message objects, which are assigned a message type that determines the subsequent processing steps to which the message object is subjected. As a message is processed, the objects of which it is comprised are changed, so that the message processing can be interrupted and then resumed without loss or duplication of processing steps.