Abstract: Embodiments relate to improving efficiency of data analytics performed on sets of entity data in which different entity properties having very different update frequencies. Time-based analytical queries track the entity states at each moment within a given time window. Analytical queries are executed over a massive number of entity states while using a reasonable memory footprint. The technique partitions the entity properties into partial historical snapshots of data and combines the partial snapshots on demand only as needed to execute analytical queries over business entities. A complete entity state having values for all entity properties is not required to execute most queries. Only partial snapshots including values referenced by the query need to be combined to satisfy the query. Using partial snapshots minimizes data replication, and the snapshots can be efficiently combined into entity states sufficient for query execution.

Abstract: A system includes one or more processors to request access tokens from a token service computer, cache the access tokens and related information in a token cache, transmit the access tokens with a resource request to a resource server, and receive requested resources in response to the resource request. The resource server transmits representations of requested resources to computing devices having valid tokens. The access tokens and related information including credentials information and token metadata are stored in the token cache.

Abstract: A system includes one or more processors to request access tokens from a token service computer, cache the access tokens and related information in a token cache, transmit the access tokens with a resource request to a resource server, and receive requested resources in response to the resource request. The resource server transmits representations of requested resources to computing devices having valid tokens. The access tokens and related information including credentials information and token metadata are stored in the token cache.

Abstract: Aspects of the present disclosure extend to methods and systems for extending services to existing enterprise systems. In various aspects, one or more service clients may be implemented to provide various functionalities for invoking a specific service that may be protocol dependent. The service client defines a set of standard service properties to specify how to access the specific service. An asset of an enterprise system intending to consume the service may integrate with the service client of the specific service and provide the standard service properties to the service client for service invocation.

Abstract: A system includes one or more processors to request access tokens from a token service computer, cache the access tokens and related information in a token cache, transmit the access tokens with a resource request to a resource server, and receive requested resources in response to the resource request. The resource server transmits representations of requested resources to computing devices having valid tokens. The access tokens and related information including credentials information and token metadata are stored in the token cache.

Abstract: A system includes one or more processors to request access tokens from a token service computer, cache the access tokens and related information in a token cache, transmit the access tokens with a resource request to a resource server, and receive requested resources in response to the resource request. The resource server transmits representations of requested resources to computing devices having valid tokens. The access tokens and related information including credentials information and token metadata are stored in the token cache.

Abstract: Aspects of the present disclosure extend to methods and systems for extending services to existing enterprise systems. In various aspects, one or more service clients may be implemented to provide various functionalities for invoking a specific service that may be protocol dependent. The service client defines a set of standard service properties to specify how to access the specific service. An asset of an enterprise system intending to consume the service may integrate with the service client of the specific service and provide the standard service properties to the service client for service invocation.

Abstract: A method and software for processing a server page is disclosed, in which a resource file is generated for each server page. The resource contains the markup text of the server page. When the server page is translated into a servlet, a static class initializer is included to read the resource file and initialize static class variables with the markup text. The initialized class is then loaded into a shored memory that is accessible to different processes.

Abstract: A system and method for caching type information for parts (e.g., parameters) of an operation passed in a web service request. When an untyped request (i.e., a request in which the data types of operation parts are omitted) is received at a web service server from a client, a cache is examined to determine if type information for the requested operation's parts exists. If not, a cache entry specific to that operation is created and populate with the necessary type information (e.g., from a WSDL document corresponding to the web service). The type information for the operation, and any global type information (i.e., for data types global to the web service), is merged for use in unmarshalling the untyped request. The operation is invoked, and any results are returned to the client.

Abstract: Techniques for utilizing a time-to-live timeout on a logical connection to a resource (e.g., a database) from a cache are provided. When a logical connection to the resource is obtained, a timeout is set specifying the amount of time the logical connection can be utilized. If the timeout expires, the logical connection is closed and the underlying physical connection can be returned to the cache.

Abstract: A method and software for processing a database statement submitted by a client application to a database system is described. A database statement is precompiled based on a string received from the client application and cached in response to a call from the client application to close the precompiled database statement. The caching may be implicit or explicit or a combination of both. With implicit caching, the precompiled statement is saved in a cache in association with the string used to precompile the database statement; with explicit caching, the precompiled statement is saved in a cache in association with a user specified key.

Abstract: Techniques for utilizing a time-to-live timeout on a logical connection to a resource (e.g., a database) from a cache are provided. When a logical connection to the resource is obtained, a timeout is set specifying the amount of time the logical connection can be utilized. If the timeout expires, the logical connection is closed and the underlying physical connection can be returned to the cache.

Abstract: A system and method for caching type information for parts (e.g., parameters) of an operation passed in a web service request. When an untyped request (i.e., a request in which the data types of operation parts are omitted) is received at a web service server from a client, a cache is examined to determine if type information for the requested operation's parts exists. If not, a cache entry specific to that operation is created and populate with the necessary type information (e.g., from a WSDL document corresponding to the web service). The type information for the operation, and any global type information (i.e., for data types global to the web service), is merged for use in unmarshalling the untyped request. The operation is invoked, and any results are returned to the client.

Abstract: A document style operation performed by a service provider is immediately invoked at a server by placing a SOAPAction value that requests that operation in an HTTP SOAP request message. The SOAPAction value is a two-part string, the first part of which indicates that the SOAPAction value contains the specification of a desired operation, and the second part of which uniquely identifies that operation. When the HTTP server that provides the Web service receives the HTTP request, the SOAPAction header is evaluated to determine whether the first part is present and, if it is, the second part is used to directly identify and call a specified operation. The SOAP envelope portion of the request message contains any argument data that is to be passed to the designated procedure. The SOAPAction value may be obtained from an available WSDL service description disseminated by the service provider.

Abstract: A method and software for processing a server page is disclosed, in which a resource file is generated for each server page. The resource contains the markup text of the server page. When the server page is translated into a servlet, a static class initializer is included to read the resource file and initialize static class variables with the markup text. The initialized class is then loaded into a shored memory that is accessible to different processes.