Abstract: A method, system, and program for managing escalating resource needs within a grid environment are provided. A job is submitted into a first selection of resources in a grid environment from among a hierarchy of discrete sets of resources accessible in the grid environment. Discrete sets of resources may include locally accessible resources, enterprise accessible resources, capacity on demand resources, and grid resources. The performance of the first selection of resources is monitored and compared with a required performance level for the job. If the required performance level is not met, then the discrete sets of resources are queried for available resources to meet the required performance level in an order designated by said hierarchy. Available resources in a next discrete set of resource from the hierarchy of discrete sets of resources are added to a virtual organization of resources handling the job within the grid environment.

Abstract: A method, system, and program managing analysis of a degraded service in a grid environment are provided. In a grid environment of multiple diverse systems, a service availability management agent is enabled to receive multiple types of error messages generated from the multiple diverse systems within the grid environment. Each error message is parsed to determine a general error indicator. Then, the service availability management agent attempts to resolve the general error indicator and return a solution to each parsed error message. Solutions may include an adjustment of resource usage by a particular service, an explanation of a particular error message, or a recommendation of alternate resources. The service availability management agent preferably specifies the transmission of the solution in a format specified for the requester system.

Abstract: A method, system, and program for maintaining application operations within a suboptimal grid environment are provided. An application profile expresses the operational requirements of an application across multiple heterogeneous resource platforms and expresses the priority of modular breakdown of an application so that usage of resources by the application can be adjusted when suboptimal conditions are detected for the application. The application is submitted to at least one resource node from among multiple resource nodes within a grid environment. Then, a service availability management agent monitors a performance status of the at least one resource node. The service availability management agent compares the performance status with an operational requirement specified for the platform of the at least one resource node in the application profile.

Abstract: A method, system, and program for minimizing complex decisions to allocate additional resources to a job submitted to a grid environment are provided. First, at least one decision to allocate additional resources to at least one previously submitted job is stored in a decision cache, wherein said the least one decision is stored according to at least one characteristic of the at least one previously submitted job. When another job is submitted to the grid environment needs additional resources, the characteristic of the currently submitted job is compared with the characteristics of previous submitted jobs. If there is a match, then the previously made decision associated with the matching characteristic controls allocation of additional resources for the currently submitted job, such that complex decision making for allocation of additional resources is minimized by reusing previously stored decisions to allocate additional resources.

Abstract: In a service-oriented architecture, service requests and responses are processed in such a manner as to minimize the latency problems of existing protocols. Accumulated client service requests are packaged together with workflow information specifying the order of execution of the requests into a single message which is transmitted to the server side of the network connection. On the server side of the network connection, the individual requests are extracted from the message together with the workflow information and routed to the intended service providers, where they are executed in the order specified by the workflow information. Responses to the service requests are similarly packaged into a return message which is transmitted back to the client side, where the responses are extracted from the message and routed to the originating clients. In a preferred embodiment, individual requests and responses are conveyed as attachments to a Simple Object Access Protocol (SOAP) message.

Abstract: A method and apparatus for invoking a service in a service-oriented architecture in which a client invokes such service from a service provider using a selected transport binding. A service binding for a service invocation from the service provider is first negotiated in a negotiation process using a first transport binding. The service invocation is then handled using the service binding negotiated in the negotiation process. A client may first determine whether a server is capable of negotiating a service binding. If the server is capable of negotiating a service binding, the client negotiates a service binding with the server. Otherwise, a service binding is selected on the basis on diagnostic information available to the client without negotiating with the server. Separate service bindings may be negotiated for each of several portions of a communication path, either by the client and service provider or by intermediaries along the communication path.

Abstract: A method and system for managing state data of a service in a service-oriented architecture by establishing a gateway for service-oriented state comprising: configuring an extensible, pluggable interface to support for extensible processor interfaces; data query support on service state data, automated notification capability on service state to a client; and automated data transform on service state data to a client format; defining an interface framework for interaction between a service and the gateway. The method also includes establishing an extensible meta-data definition comprising an extensible set of service state data attributes including state data qualifiers, constraints, and access mechanisms; and utilizing one or more pluggable processors configured to utilize the extensible meta-data definition for interfaces and decision making based on the meta-data.

Abstract: A method and apparatus for generating service state data and extensible meta-data information with a service oriented state data generator (SSDG) comprising: establishing a platform independent, extensible meta-data model for the meta-data information; obtaining state data schema based on a service state data description; defining an extensible set of meta-data attributes and templates corresponding to the meta data based on requirements of a service; and utilizing the meta-data model and based on the state data schema and the attributes, generating service state data based on the service state data schema; and The service state data including at least one of: state data, state data logical mapping, state data physical mapping, meta-data associated with the service state data and meta-data model correlations associated with the meta-data.

Abstract: A method for mapping Open Grid Services Architecture (OSGA) service data to a native resource representation thereof includes defining a set of standard mapping rules for service data descriptions in a service-oriented architecture, wherein the set of standard mapping rules are implemented through an OSGA Service Data Mapping Language (OSDML) configured to support complex mapping through extensible language features.

Abstract: A method for dynamically associating type information about extensible messages in a service-oriented architecture includes configuring a simple object access protocol (SOAP) message header to include message meta-data and semantics, thereby facilitating a dynamic exchange of semantic type information for open content message exchange between a sender and a receiver.

Abstract: A method and system for creating a dynamic client side service proxy framework using meta-data and introspection capabilities of Open Grid Services Architecture (OGSA) service data is disclosed. The system and method include defining an Open Grid Service Invocation Factory configured to create a service proxy and introspecting an Open Grid Service Infrastructure (OGSI) service based on information exposed by the service. An OGSI Service Invocation Proxy is created defining a set of dynamic interfaces based on service introspection and a meta-data inspection interface of the Service Invocation Proxy. The Service Invocation Proxy exposes both static port type interfaces and dynamic interfaces to support more flexibility of the client.

Abstract: A method and system for managing service state data of a service in a service-oriented architecture by establishing a pluggable meta-data processor comprising: establishing a platform independent, extensible meta-data information model to define meta-data about service state data; establishing an extensible meta-data definition comprising an extensible set of service state data attributes; configuring one or more extensible semantic processors; configuring a controller meta-data processor; and defining contracts among the semantic processors.

Abstract: A system for electronically ordering items having at least one supplier computer system for storing at least one catalog containing the items offered by a supplier and a customer computer system with the improvement of a public computer system comprising an index to the items in the catalogs on the at least one supplier computer system, means for querying the index on the public computer system for a desired item in response to a request for the desired item from the customer computer system and means for generating a pointer for the customer computer system to catalog information about the desired item in the catalog on the at least one supplier system which has been identified by the query of the index.

Abstract: A first computer system determines whether a URL contains a first value corresponding to an encapsulating protocol. If the URL contains a value corresponding to an encapsulating protocol, the first computer system determines whether the URL contains an operation protocol key indicating that the URL contains a second value corresponding to an operation protocol. If the URL contains a second value corresponding to an operation protocol, the first computer system selects the operation protocol as the protocol to be employed by the first computer system in issuing a communication to a second computer system. A second computer system determines whether a URL it receives contains a first value corresponding to an operation protocol. If the URL contains a first value corresponding to an operation protocol, the second computer system provides a resource targeted to a first computer system in accordance with an encapsulating protocol.

Abstract: An advanced windows management system permits a user to customize views from a plurality of frame windows into a single target window. A view includes display information that corresponds to an underlying program. The user selects views from the frame windows, and the user specifies a target window for placement of the views, including the arrangement of the views, in the target window via a drag and drop operation. In response, the advanced windows management system docks and displays the selected views in the target window. The views may comprise textual, graphical and control information for a plurality of editors or tools used in software development. Through use of the advanced windows management system, a user generates editor windows that include views from tools and editors. Thus, the user is permitted to customize the editor window to include views for editors used on a project.

Abstract: A geometry management system provides an initial bottom-up layout that determines the ideal and default sizes of objects including the pages, views, and frame windows. The geometry management system further includes a top down configuration to handle resizing of a window including the objects contained in the window. The geometry management system includes geometry manager objects, container objects, and child objects. At design or layout time, the child objects are placed in a parent container via a drag and drop operation. The geometry management system specifies size parameters through negotiation among the child objects, the containers, and the high level geometry manager. When a child object requires resizing, the child object requests geometry from the parent container object. Based on the specified parameters, the container determines whether a given geometry is feasible. If the parameters are acceptable, the container implements the geometry.

Abstract: The present invention identifies and separates the spatial grouping element from the management element in a geometry management scheme. The management element provides a constraint-resolution engine. A spatial grouping element can describe spatial groupings for graphic user interface (GUI) elements. A spatial group captures and encapsulates the set of constraints that describe the layout of a small portion of a user interface. A higher level spatial group can capture the constraints among the other spatial groups. The present invention provides independent, lightweight spatial-grouping elements that are incorporated into the constraint language of a geometry manager. Further, the present invention allows a GUI component to be grouped with multiple spatial-grouping elements. The present invention restricts the effect of a grouping element to a subset of the available set of dimensions. The present invention minimizes the number of geometry management elements.