High flexibility for ad hoc growth
In order to make a transaction in cryptocurrencies, you do not have to let your bank know about it as you would for "normal" money, but you have to use the Private Key to prove that you own the coins. The transaction looks like a piece of the puzzle. Half of the puzzle piece consists of information about the coin set, time and public address of the sender or receiver. The other half is the signature of the private key belonging to the sent public address. Both halves make this piece unique. Changing only one piece of information would completely change the whole transaction or the appearance of the puzzle piece. This transaction is transferred to the network or to the miner and is checked for correctness first. If everything fits, the transaction will be sent to other miners who will do the same. Otherwise, the transaction is ignored. Miners try to integrate the transactions into a block. This is called mining and we have described it so that the miners put the puzzle pieces together into a puzzle (block). A small part of a block to be integrated follows from the block that was previously mined. If all miners accept the correctness of a completed block, they will all work the next one immediately. The puzzle (block) is fixed and is irrevocably connected to the block before or after. The blocks form a chain and are called blockchain, which contains all the transactions that have ever been made and is visible and unchangeable by everyone. In doing so, blockchain replaces a central institution and avoids double-spending, which ultimately gives value to a cryptocurrency. Smart Contracts The biggest advance compared to Bitcoin and similar applications is that second-generation blockchains, such as Ethereum, use the so-called Turing-Complete script language Solidity. This enables calculations to be made within the blockchain. While Bitcoin allows only rudimentary multi-signature functions, Ethereum opens the door to much more complex operations called smart contracts. Smart contracts are contracts in which a decentralised blockchain ensures their unchangeability and execution.
Job scheduling: your system needs to run various automatic background jobs that consume resources. Your administrator must carefully schedule these tasks when user demand is low so they don't impact performance.
SAP Basis - operation, structure and definition
SAP Basis ensures smooth operation of the SAP Basis system. The SAP Basis system is a kind of operating system of the R/3 system or SAP ERP. It includes the three layers database, application and presentation. In addition, Basis includes many SAP middleware programs and administration tools. With Basis SAP applications can be used compatible and independent of operating system and database and can be enriched with the necessary data.
Many companies are struggling with the introduction and use of secinfo and reginfo files to secure SAP RFC gateways. We have developed a generator that supports the creation of the files. This blog post lists two SAP best practices for creating the secinfo and reginfo files to enhance the security of your SAP gateway and how the generator helps you do this. secinfo and reginfo Request generator Option 1: Restrictive procedure In the case of the restrictive solution approach, only in-system programmes are allowed. Therefore, external programmes cannot be used. However, since this is desired, the access control lists must be gradually expanded to include each programme required. Although this procedure is very restrictive, which speaks for safety, it has the very great disadvantage that, in the creation phase, links which are actually desired are always blocked. In addition, the permanent manual activation of individual connections represents a continuous effort. For large system landscapes, this procedure is very complex. Option 2: Logging-based approach An alternative to the restrictive procedure is the logging-based approach. To do this, all connections must be allowed first by the secinfo file containing the content USER=* HOST=* TP=* and the reginfo file contains the content TP=*. During the activation of all connections, a recording of all external programme calls and system registrations is made with the gateway logging. The generated log files can then be evaluated and the access control lists created. However, there is also a great deal of work involved here. Especially with large system landscapes, many external programmes are registered and executed, which can result in very large log files. Revising them and creating access control lists can be an unmanageable task. However, this process does not block any intentional connections during the compilation phase, which ensures the system will run non-disruptively.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
If errors occur, SPAM will interrupt the playback to ensure consistency of the recording.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
After all, each SAP Basis expert sees different transactions as important.