International Business Machines Corporation

Colette Manoni

Daniel S Gritter

Marc Henri Coq

Robert O Dryfoos

Richard W Potts, Jr

Trent Balta

Gerald B Strait

Collin Walling

Eugene E Nitka

Luis Angel D Bathen

Matthew J Sykes

Barry P Gower

Mei-Hui Wang

Bradd A Kadlecik

Barry M Baker

Corey McQuay

Dennis Fallon

Dulce Beatriz Ponceleon

Christopher Daniel Filachek

Joshua B Wisniewski

Hong Deng

Renata Rand McFadden

Glenn I Katzen

James D Johnston, Jr

Sarat Vemuri

Richard E Reynolds

Mark Spies

Sunil Shenoi

Yuk S Tam

Jodi E Everdon

Jennifer A Thompson

Barry M Goldberg

An example operation may include one or more of identifying a group of blockchain member devices attempting to establish a trusted group communication channel, assigning each of the blockchain member devices public/private key pairs, publishing the public keys of the blockchain member devices in a list, identifying a request from a first blockchain member device requesting a private key, associated with a second blockchain member device, be applied to a predetermined nonce value, responsive to identifying a response to the request, verifying, via a public key assigned to the first blockchain member device, that the second blockchain member device is a trusted member of the group of blockchain member devices, and responsive to verifying the second blockchain member device is a trusted member of the group of blockchain member devices, permitting communication between the first blockchain member device and the second blockchain member device on the trusted group communication channel.

Ad-hoc trusted groups on a blockchain

An example operation may include one or more of: creating a document that defines procedures to create an ad-hoc group having an original peer, to add a new peer to the ad-hoc group and to remove of one or more of the original peer and the new peer; maintaining, via a memory, a cryptographic distributed ledger based on the document and peer data associated with the ad-hoc group; encrypting the document; encrypting the cryptographic distributed ledger; providing the encrypted cryptographic distributed ledger to the ad-hoc group; decrypting the encrypted document; modifying the document; decrypting the encrypted cryptographic distributed ledger; updating the cryptographic distributed ledger; encrypting the modified document to create an encrypted modified document; encrypting the updated cryptographic distributed ledger; and providing the updated encrypted cryptographic distributed ledger to the ad-hoc group.

Consensus based ad-hoc group creation

An example operation may include one or more of storing a unique identification code encapsulating encoded information about a trusted group of member devices within a decentralized network, the unique identification code being generated by the trusted group of member devices, decoding the stored unique identification code to generate decoded information which verifies that the user device is a member device of the trusted group of member devices and provides contact information for other member devices of the trusted group of member devices, and establishing a communication session with the trusted group of member devices based on the contact information obtained by decoding the unique identification code.

Trusted group identification code

Techniques are provided for replicating database contents to network-enabled remote systems, and limiting such replication with respect to sensitive database contents. An indication is received that a subset of record fields in a database comprise sensitive data. The subset of indicated record fields are flagged based on the received indication. At least a portion of the database is replicated to multiple remote systems, such that for at least a first of the remote systems, data associated with a larger plurality of record fields is provided to the remote system. For at least a second of the remote systems, based on the flagging of the subset of indicated record fields, only data associated with record fields other than the flagged subset is provided to the remote system.

Protecting sensitive information when replicating data to remote systems

A processor-implemented method for designing, developing, implementing and maintaining a core service related to a database is provided. The processor-implemented method may include displaying a graphical user interface and identifying, from the graphical user interface, the core service. Then the processor-implemented method may include determining, from the graphical user interface, a type of folder request based on the identified core service and accessing a folder based on the determining of the type of folder request. The processor-implemented method may further include determining a lock order based on the accessed folder; and manipulating the accessed folder based on the determining of the lock order.

Core service build / deployment for hierarchical database

A method of dynamic linkage including: receiving a request to launch a program; checking a system memory for the program; reserving a unique memory block of the system memory for the program and loading the program into the unique memory block if the program is not found in the memory of the system; performing internal memory relocations for the program if the program is not found in the memory of the system; ensuring that a library required by the program has been loaded into the system memory if the program is not found in the memory of the system; and invoking the program.

Methods, systems and computer program products for dynamic linkage

A common symbol table is generated, which includes symbols of a plurality of independent applications. The symbols included in the common symbol table are common symbols of the applications. The bulky information associated with the common symbols are stored in the common symbol table, and stubs used to locate the common symbols are stored in local tables of the applications.

Generating a common symbol table for symbols of independent applications

A system, method and computer program product for a user to verify that a network resource address is trusted. At least one entity registration is stored at a server. Each entity registration comprises an identity of an entity and entity addressing information associated with the identity of the entity. The existence of at least one entity whose identity is included in the at least one entity registration is confirmed. A query comprising a target addressing information is received from a client. If the target addressing information matches the entity addressing information, the identity of the entity associated with the entity addressing information is determined and a result comprising the identity of the entity associated with the entity addressing information matching the target addressing information is transmitted to the client. If no entity addressing information matches the target addressing information, an indication of such is transmitted to the client.

System and method for user to verify a network resource address is trusted

Managing shared data objects to share data between computer processes, including a method for executing a plurality of independent processes on an application server, the processes including a first process and a second process. A shared memory utilized by the plurality of independent processes is provided. A single copy of the data and metadata are stored in the shared memory. The metadata includes an address of the data. The first process initiates the storing of the data in the shared memory. An address of the metadata is transferred from the first process to the second process to notify the second process about the data. The second process determines the address of the shared memory by reading the metadata. The data in the shared memory is accessed by the second process.

Managing shared data objects to provide visibility to shared memory

A system for sharing data between computer processes. The system includes a processor configured to implement a method that includes executing a plurality of independent processes on an application server, the processes including a first process and a second process. A shared memory utilized by the plurality of independent processes is provided. A single copy of the data and metadata are stored in the shared memory. The metadata includes an address of the data. The first process initiates the storing of the data in the shared memory. An address of the metadata is transferred from the first process to the second process to notify the second process about the data. The second process determines the address of the shared memory by reading the metadata. The data in the shared memory is accessed by the second process.

In an embodiment of the present invention the Java Virtual Machine (JVM) System Scope Initializer works on the premise of generating one JVM instance to be used by all processes system wide. An advantage in the present invention is that all processes that would normally otherwise have to instantiate a JVM, which can be on the order of millions of instructions (per process) can in large part be avoided realizing instead a tremendous system resource savings system wide. Another advantage can be that all processes that would normally otherwise have to instantiate a JVM, which can have a memory footprint on the order of megabytes (per process), can share the same memory view again realizing tremendous system resource savings system wide.

JVM system scope initializer

Debugging of a transaction across multiple processors is facilitated by having debug information follow the transaction from processor to processor. The transaction can be debugged across processors without predefining the transaction path, and without performing a debug registration process between the client controlling the debugging and each processor of the multiple processors.

Debugging transactions across multiple processors

A system and method for obtaining performance data from software compiled with or without trace hooks is provided. A software application is entered and a trace data flag is set to off. For each module initiated by the software application, the trace data flag is set to on if the module is registered with a performance analyzer tool. If the module does have trace data hooks and the trace data flag is on, then, a request is transmitted to the performance analyzer tool to record trace data. If the module does not have trace data hooks and the trace flag is on, a request is transmitted to the performance analyzer tool to record trace data in response to entering and exiting the module. When the software application exits, a report based on the trace data is received from the performance analyzer tool.

Method and system for obtaining performance data from software compiled with or without trace hooks

The use of aliases in the debugging of applications is facilitated. Aliases are used in debugging, even when the aliases are not known to the debug generation stage of the compiler. That is, aliases are used in debugging, even when debug information is not generated by the compiler for the aliases. In order to use the aliases in debugging, the aliases are resolved to their formal names, and then debug information corresponding to the formal names, and thus, the aliases, is obtained.

Facilitating the use of aliases during the debugging of applications

A high performance client/server editor and method for editing documents with improved performance. A server listening for editing requests from a client to edit a file located with the server spawns a thread for each editing request to handle that particular request. A client receiving input commands from a user for editing requests spawns a thread for each editing request received, enabling more than one editing request to be processed simultaneously. When an edit feature is invoked, the client sends a request to the server to download the file. While the file is downloading from the server to the client location, the client displays the first page of the file to the user to enable the user to start editing the file before the entire file is downloaded. The client handles the user's edit commands for portions of the file downloaded. If the user attempts to edit portions of the file not yet downloaded, the client sends a request to the server to handle the edit at the server location and send a response back to the client for display to the user by the client. Edit changes are sent to the server when user enters a save command. Alternatively, edit changes are sent to the server when bandwidth is available. When the user exits without saving these changes, the server discards the changes. In subsequent edit invokes of the same file, the client and server cooperate to download only those portions of the file which were changed since the last download.

Growing community of inventors

Brewster, NY, United States of America

Colette Manoni