G06F9/45

Automatic Audit Logging of Events in Software Applications Performing Regulatory Workloads
20170308712 · 2017-10-26 ·

Automatically generating audit logs is provided. Audit log statement insertion points are identified in components of an application based on a static code analysis identifying start and end operations on sensitive data in the components of the application. The application is instrumented with audit log statements at the audit log statement insertion points in the components of the application. Audit logs of monitored sensitive data activity events in the application are generated using the audit log statements at the audit log statement insertion points in the components of the application.

Call Management Method and Apparatus

A system and method for handling calls at a call facility wherein each call is handled by a distinct call container instance, the system comprising a platform server programmed to perform the steps of maintaining an idle container inventory for handling new incoming calls, upon receiving a new call, assigning the new call to one of the idle containers in the inventory, upon completion of a call within one of the containers, causing the container that completed the call to be killed, monitoring the idle container inventory and stage instantiation of additional idle containers to replenish the idle container inventory as containers complete calls and are killed off.

WARNING DATA MANAGEMENT FOR DISTRIBUTED APPLICATION DEVELOPMENT

Aspects of the disclosure relate to using a set of warning data to manage distributed development of an application in a computing environment. In embodiments, the computing environment may include a distributed computing environment or a stream computing environment. A first portion of the application may be developed by a first user. A second portion of the application may be received by the first user. The second portion of the application may be compiled and developed by a second user. Based on the set of warning data, a curative action for utilization to develop the application may be formulated. The curative action may be carried-out to develop the application.

WARNING DATA MANAGEMENT WITH RESPECT TO AN EXECUTION PHASE

Aspects of the disclosure relate to managing a set of warning data with respect to an execution phase in a computing environment. In embodiments, the computing environment may include a distributed computing environment or a stream computing environment. The set of warning data may be detected with respect to the execution phase. In embodiments, the set of warning data may be coupled with a computing artifact. In embodiments, the computing artifact may include a compilation which has a computing object in association with the set of warning data. Using the set of warning data, an execution action which pertains to the computing artifact may be determined. In embodiments, the execution action may include a code deployment to a set of computing units, a run-time check modification, or a process attribute modification. The execution action which pertains to the computing artifact may be performed.

WARNING DATA MANAGEMENT WITH RESPECT TO A COMPILATION PHASE

Aspects of the disclosure relate to managing a set of warning data with respect to a compilation phase in a computing environment. In embodiments, the computing environment may include a distributed computing environment or a stream computing environment. The set of warning data may be detected with respect to the compilation phase. By analyzing the set of warning data, it may be identified that the set of warning data relates to a computing object. In embodiments, the computing object may include a set of implementation code. The set of warning data may be established in association with the computing object.

Message oriented construction of web services

A selection of graphical message flow primitives defined within the message flow builder that each graphically represent and define message-oriented logic of an operation for the Web service are graphically assembled. Each graphical message flow primitive is defined within the message flow builder as a representation of a unit of work usable to define message flow patterns of Web service operation flow types and each includes a Web service operational processing logic definition of the representation of the respective unit of work usable to generate executable Web service logic. Selected ones of the graphical message flow primitives are graphically interconnected to represent a flow of messages to create a message-oriented Web service definition. The executable Web service logic defined within the message flow builder by each one of the interconnected selected graphical message flow primitives within the created message-oriented Web service definition is generated to construct the Web service.

Software solution for cooperative memory-side and processor-side data prefetching

A solution for cooperative data prefetching that enables software control of a memory-side data prefetch and/or a processor-side data prefetch is provided. In one embodiment, the invention provides a solution for generating an application, in which access to application data for the application is improved (e.g., optimized) in program code for the application. In particular, a push request, for performing a memory-side data prefetch of the application data, and a prefetch request, for performing a processor-side data prefetch, are added to the program code. The memory-side data prefetch results in the application data being copied from a first data store to a second data store that is faster than the first data store while the processor-side data prefetch results in the application data being copied from the second data store to a third data store that is faster than the second data store.

Method and system for splitting scheduling problems into sub-problems
09798947 · 2017-10-24 · ·

A computing system receives user input of scheduling problem data. The scheduling problem data relates to a scheduling problem and includes one or more stations and tasks to be performed by at least one station. The computing system constructs a graph problem using the scheduling problem data. The graph problem includes a graph. The computing system cuts the graph into sub-graphs using a cut algorithm to create a cut result that satisfies a threshold and identifies one or more task exceptions from the sub-graphs in the cut result. The one or more task exceptions are tasks that can be assigned to more than one sub-graph. The computing system creates scheduling sub-problems pertaining to the one or more task exceptions using the cut result.

User grey cell

In various embodiments, a user grey cell is disclosed. The user grey cell comprises a simplified logical implementation of a black box cell identified in a software and/or hardware design. The internal functionality of the black box cell is undefined, hidden, or encrypted, and thus is not available for timing analysis. The user grey cell for the black box cell provides sufficient clocking and register information to allow for accurate CDC, false path, and multi-cycle path analysis, and provides a way for designers to locate and repair clock domain crossing violations before the design is implemented in hardware. In various embodiments, a method for user grey cell analysis is disclosed. The method comprises identifying one or more black box cells in a user design. The method further comprises determining which of the input and/or output pins of each of the black box cells are in use by the user design. The method further comprises selecting a user grey cell for one or more of the black box cells, wherein a user grey cell comprises a simplified logic implementation for the black box cell, sufficient to perform CDC, false path, and multi-cycle path analysis. The selected user grey cells may be used in place of the black box cells for CDC, false path, and multi-cycle path analysis.

Precompiling locally-stored instructions for a web application
09798532 · 2017-10-24 · ·

Systems and methods for accessing locally-stored content for a web application are disclosed. In some aspects, a user input for requesting a web application is received at a client computing device. A network request for the web application is provided via a network. That software code for the web application is stored in local storage of the client computing device is determined. The stored software code for the web application is placed into a random access memory (RAM) of the client computing device. At least a portion of the stored software code is precompiled prior to receiving a response to the network request.