mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Preparation for migration Red Hat build of OpenJDK 17 includes changes that might require you to reconfigure your applications, which were already successfully deployed on Red Hat build of OpenJDK version 8 or 11. You can ensure an effective migration plan by completing the following tasks, as appropriate: If you currently use Red Hat build of OpenJDK 8, review the Major differences between Red Hat build of OpenJDK 8 and Red Hat build of OpenJDK 11 section to familiarize yourself with the changes that are available from version 11 onward. Review the Major differences between Red Hat build of OpenJDK 11 and Red Hat build of OpenJDK 17 section to familiarize yourself with the changes that are available from version 17 onward. Integrate the differences into your migration plan. Red Hat provides a migration toolkit for applications (MTA) tool that you can use to help with your migration tasks. You can use the MTA tool to migrate Java applications from Red Hat build of OpenJDK version 8 or 11 to Red Hat build of OpenJDK 17. Additional resources For more information about the installation of Red Hat build of OpenJDK 17 on RHEL, see the Installing and using Red Hat build of OpenJDK 17 on RHEL guide. For more information about the installation of Red Hat build of OpenJDK 17 on Microsoft Windows, see the Installing and using Red Hat build of OpenJDK 17 for Windows guide. For more information about switching between Red Hat build of OpenJDK versions on RHEL, see Interactively selecting a system-wide Red Hat build of OpenJDK version on RHEL in the Configuring Red Hat build of OpenJDK 17 on RHEL guide. For more information about the MTA tool, see the Introduction to the Migration Toolkit for Applications guide.

Commands:
Chapter 1. About this release The release notes provide high-level coverage of the features that have been implemented in Red Hat Developer Hub 1.2 and document known issues in this release. Some features within this release may be available as a Technology Preview, providing access to upcoming product features, enabling customers to test functionality and to provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, read Technology Preview Support Scope . Benefits of Red Hat Developer Hub include: Increased developer productivity : Increases productivity by eliminating common organizational challenges, enabling seamless collaboration, and providing clear guidelines for creating, developing, and deploying applications. Unified self-service dashboard : Provides development teams with a unified dashboard covering various aspects such as Git, CI/CD, SAST/DAST, Supply Chain, OpenShift/Kubernetes cluster, JIRA, monitoring, API, documentation, and more, facilitated by over 150 plugins. All curated by a platform engineering team, aligning with the company's best practices. Best practices through software templates : Automates organizational best practices by encoding common tasks such as creating new applications, running Ansible jobs, and establishing CI/CD pipelines for production deployment in Git. Scalable technical documentation : Code and documentation resides in the same repository, eliminating dependencies on proprietary document systems. Efficient onboarding for new developers : New developers quickly adapt and become productive within a short timeframe. Robust enterprise Role-Based Access Control (RBAC) : Empowers administrators to create roles, assign users or groups to roles, and implement robust security policies for enhanced access control.

Commands:
Chapter 13. Kernel Processes reading the /proc/stat file cause high CPU usage CPU usage is high on the system when many processes are reading the /proc/stat file. This is caused by contention on the sparse_irq_lock kernel lock. To work around this problem, add the kstat_irq_nolock argument on the kernel command line. This disables the lock and lowers CPU usage, but it might lead to the system becoming unresponsive in extremely rare cases due to a race condition. (BZ#1544565)

Commands:
F.8. Metadata Menu The Metadata menu provides Teiid Designer specific actions. Figure F.10. Metadata Menu The Metadata menu contains the following actions: Update Model from Source - If the selected model is a relational source model that was originally created via JDBC Import, then the model will be updated based on changes in the database schema. Show System Catalog - Opens the System Catalog view. Show Datatype Hierarchy - Opens the Datatype Hierarchy view. Show SQL Reserved Words - Opens the SQL Reserved Words view. Convert to Enterprise Datatypes - Adds an additional property to simple datatypes within your selected schema model to label them as enterprise datatypes. Show Model Statistics - Opens the Model Statistics dialog for the selected model. Build Model Imports - Reconciles all model import dependencies for the selected model.

Commands:
Chapter 4. Publishing applications with .NET 6.0 .NET 6.0 applications can be published to use a shared system-wide version of .NET or to include .NET. The following methods exist for publishing .NET 6.0 applications: Single-file application - The application is self-contained and can be deployed as a single executable with all dependent files contained in a single binary. Note Single-file application deployment is not available on IBM Z and LinuxONE. Framework-dependent deployment (FDD) - The application uses a shared system-wide version of .NET. Note When publishing an application for RHEL, Red Hat recommends using FDD, because it ensures that the application is using an up-to-date version of .NET, built by Red Hat, that uses a set of native dependencies. Self-contained deployment (SCD) - The application includes .NET. This method uses a runtime built by Microsoft. Note SCD is not available on IBM Z and LinuxONE. Prerequisites Existing .NET application. For more information on how to create a .NET application, see Creating an application using .NET . 4.1. Publishing .NET applications The following procedure outlines how to publish a framework-dependent application. Procedure Publish the framework-dependent application: Replace my-app with the name of the application you want to publish. Optional: If the application is for RHEL only, trim out the dependencies needed for other platforms: Replace architecture based on the platform you are using: For Intel: x64 For IBM Z and LinuxONE: s390x For 64-bit Arm: arm64

Commands:
dotnet publish my-app -f net6.0 -c Release
dotnet publish my-app -f net6.0 -c Release -r rhel.8- architecture --self-contained false
27.3. Online Resources For z/VM publications, refer to http://www.vm.ibm.com/library/ . For System z I/O connectivity information, refer to http://www.ibm.com/systems/z/hardware/connectivity/index.html . For System z cryptographic coprocessor information, refer to http://www.ibm.com/security/cryptocards/ . Sharing and maintaining RHEL 5.3 Linux under z/VM . Brad Hinson and Mike MacIsaac . http://www.linuxvm.org/Present/misc/ro-root-RH5.pdf .

Commands:
Chapter 5. DM-Multipath Administration and Troubleshooting This chapter will provide information on administering DM-Multipath on a running system. 5.1. Automatic Configuration File Generation with Multipath Helper You can generate a basic configuration for multipath devices on Red Hat Enterprise Linux with the Multipath Helper application. The application gives you options to create multipath configurations with custom aliases, device blacklists, and settings for the characteristics of individual multipath devices. Upon completion, the application generates an installation script that includes the configuration parameters you selected and it provides a multipath.conf configuration file for review. The Multipath Helper application can be found at https://access.redhat.com/labsinfo/multipathhelper .

Commands:
8.185. ppc64-diag 8.185.1. RHBA-2014:1445 - ppc64-diag bug fix and enhancement update Updated ppc64-diag packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The ppc64-diag packages provide diagnostic tools for Linux on the 64-bit PowerPC platforms. The platform diagnostics write events reported by the firmware to the service log, provide automated responses to urgent events, and notify system administrators or connected service frameworks about the reported events. This update also fixes the following bug: Note The ppc64-diag packages have been upgraded to upstream version 2.6.6, which provides a number of bug fixes and enhancements over the version. (BZ# 929278 ) This update also fixes the following bug: Bug Fix BZ# 988237 Previously, there were file conflicts between the ppc64-diag and powerpc-utils packages. As a consequence, installation of Red Hat Enterprise Linux which contained recent versions of these packages failed. This update fixes the conflicts between ppc64-diag and powerpc-utils, and installation of Red Hat Enterprise Linux now completes successfully. The ppc64-diag packages have been upgraded to upstream version 2.6.6, which provides a number of bug fixes and enhancements over the version. (BZ#929278) In addition, this update adds the following Enhancement BZ# 949612 This update adds the LightPath Diagnostics framework to the ppc64-diag tool set. This new feature helps identify failed hardware components through LED lights and then facilitate replacement. All users of ppc64-diag are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
probe::signal.send Name probe::signal.send - Signal being sent to a process Synopsis Values send2queue Indicates whether the signal is sent to an existing sigqueue name The name of the function used to send out the signal task A task handle to the signal recipient sinfo The address of siginfo struct si_code Indicates the signal type sig_name A string representation of the signal sig The number of the signal shared Indicates whether the signal is shared by the thread group sig_pid The PID of the process receiving the signal pid_name The name of the signal recipient Context The signal's sender.

Commands:
signal.send
4.115. kdebase 4.115.1. RHBA-2011:1200 - kdebase bug fix update Updated kdebase packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The K Desktop Environment (KDE) is a graphical desktop environment for the X Window System. The kdebase package includes core applications for KDE. Bug Fixes BZ# 631481 Prior to this update, when starting another instance of the konsole application in an already running konsole instance, the spurious "Undecodable sequence: \001b(hex)[?1034h" message was displayed. This bug has been fixed in this update and no longer occurs. BZ# 609039 Prior to this update, the System Settings application in KDE became unresponsive when entering a password in order to apply changes in the About Me dialog. With this update, the bug has been fixed so that entering a password works properly. All users of kdebase are advised to upgrade to these updated packages, which fix these bugs.

Commands:
probe::vm.write_shared_copy Name probe::vm.write_shared_copy - Page copy for shared page write. Synopsis Values name Name of the probe point zero Boolean indicating whether it is a zero page (can do a clear instead of a copy). address The address of the shared write. Context The process attempting the write. Description Fires when a write to a shared page requires a page copy. This is always preceded by a vm.shared_write.

Commands:
vm.write_shared_copy
7.193. selinux-policy 7.193.1. RHBA-2015:1375 - selinux-policy bug fix and enhancement update Updated selinux-policy packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The selinux-policy packages contain the rules that govern how confined processes run on the system. Bug Fixes BZ# 1198047 , BZ# 1198057 , BZ# 1198060 , BZ# 1198064 , BZ# 1198071 , BZ# 1198077 , BZ# 1198165 , BZ# 1202935 , BZ# 1203756 , BZ# 1207140 , BZ# 1212729 When the /etc/nsswitch.conf file was modified so that the SSSD service was used for various lookups, certain services were not able to communicate with SSSD due to insufficient SELinux policy rules. With this update, the SELinux policy has been modified to allow the services to work as expected in this situation. BZ# 1198436 , BZ# 1215632 , BZ# 1228197 , BZ# 1228197 , BZ# 1219317 , BZ# 1221929 With this update, SELinux policy rules for the glusterd, ctdbd, samba, and nagios services have been fixed to allow the Gluster layer product to work with SELinux properly. Enhancement BZ# 1153712 When writing SELinux policy rules that allow random services to read or execute general files located, for example, in the /etc/ or /usr/ directories, policy writers had to add additional rules for each service. These updated selinux-policy packages introduce the new "base_ro_file_type" and "base_file_type" SELinux attributes, which policy writers can use to declare global rules against a rule per service. Users of selinux-policy are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 2. Installation This chapter guides you through the steps to install AMQ Python in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To install packages on Red Hat Enterprise Linux, you must register your system . To use AMQ Python, you must install Python in your environment. 2.2. Installing on Red Hat Enterprise Linux Procedure Use the subscription-manager command to subscribe to the required package repositories. If necessary, replace <variant> with the value for your variant of Red Hat Enterprise Linux (for example, server or workstation ). Red Hat Enterprise Linux 7 USD sudo subscription-manager repos --enable=amq-clients-2-for-rhel-7- <variant> -rpms Red Hat Enterprise Linux 8 USD sudo subscription-manager repos --enable=amq-clients-2-for-rhel-8-x86_64-rpms Use the yum command to install the python-qpid-proton and python-qpid-proton-docs packages. USD sudo yum install python-qpid-proton python-qpid-proton-docs For more information about using packages, see Appendix B, Using Red Hat Enterprise Linux packages . 2.3. Installing on Microsoft Windows Procedure Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Clients entry in the INTEGRATION AND AUTOMATION category. Click Red Hat AMQ Clients . The Software Downloads page opens. Download the AMQ Clients 2.9.0 Python .whl file for your Python version. Python 3.6 python_qpid_proton-0.33.0-cp36-cp36m-win_amd64.whl Python 3.8 python_qpid_proton-0.33.0-cp38-cp38-win_amd64.whl Open a command prompt window and use the pip install command to install the .whl file. Python 3.6 > pip install python_qpid_proton-0.33.0-cp36-cp36m-win_amd64.whl Python 3.8 > pip install python_qpid_proton-0.33.0-cp38-cp38-win_amd64.whl

Commands:
sudo subscription-manager repos --enable=amq-clients-2-for-rhel-7- <variant> -rpms
sudo subscription-manager repos --enable=amq-clients-2-for-rhel-8-x86_64-rpms
sudo yum install python-qpid-proton python-qpid-proton-docs
> pip install python_qpid_proton-0.33.0-cp36-cp36m-win_amd64.whl
> pip install python_qpid_proton-0.33.0-cp38-cp38-win_amd64.whl
Chapter 152. Hystrix Component Available as of Camel version 2.18 The hystrix component integrates Netflix Hystrix circuit breaker in Camel routes. For more details see the Hystrix EIP documentation. Maven users will need to add the following dependency to their pom.xml for this component: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-hystrix</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> 152.1. Spring Boot Auto-Configuration The component supports 3 options, which are listed below. Name Description Default Type camel.component.hystrix.mapping.enabled Enables the automatic mapping of the hystrics metric servlet into the Spring web context. true Boolean camel.component.hystrix.mapping.path Endpoint for hystrix metrics servlet. /hystrix.stream String camel.component.hystrix.mapping.servlet-name Name of the Hystrix metrics servlet. HystrixEventStreamServlet String

Commands:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-hystrix</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>
Chapter 1. Important considerations when tuning IdM Identity Management's component services are tuned to work in an optimal way for most deployments. As a System Administrator, you may want to adjust the performance of IdM services to suit the demands of your specific environment. Important considerations Each IdM deployment is a unique combination of hardware, software, networking, data, workloads, and many other factors. Adjustments that benefit one environment may be detrimental to another. Performance-tuning is an iterative, experimental process. Red Hat recommends making adjustments to only one variable at a time and monitoring its impact in your environment. After achieving the desired result with one variable, adjust the variable while continuing to monitor the performance of adjustments.

Commands:
8.4. Comparing java.util.concurrent.ConcurrentMap and javax.cache.Cache APIs Here is a brief comparison of the data manipulation APIs provided by java.util.concurrent.ConcurrentMap and javax.cache.Cache APIs: Table 8.1. java.util.concurrent.ConcurrentMap and javax.cache.Cache Comparison Operation store and no return N/A store and return value store if not present retrieve delete if present delete and return value delete conditional replace if present replace and return value replace conditional Comparing the two APIs it can be seen that, where possible, JCache avoids returning the value to avoid operations doing expensive network or IO operations. This is an overriding principle in the design of the JCache API. In fact, there is a set of operations that are present in java.util.concurrent.ConcurrentMap , but are not present in the javax.cache.Cache because they could be expensive to compute in a distributed cache. The only exception is iterating over the contents of the cache: Table 8.2. javax.cache.Cache avoiding returns Operation calculate size of cache N/A return all keys in the cache N/A return all values in the cache N/A return all entries in the cache N/A iterate over the cache use iterator() method on keySet, values, or entrySet Report a bug

Commands:
java.util.concurrent.ConcurrentMap<K,V>
javax.cache.Cache<K,V>
void put(K key)
V put(K key)
V getAndPut(K key)
V putIfAbsent(K key, V Value)
boolean putIfAbsent(K key, V value)
V get(Object key)
V get(K key)
V remove(Object key)
boolean remove(K key)
V remove(Object key)
V getAndRemove(K key)
boolean remove(Object key, Object value)
boolean remove(K key, V oldValue)
V replace(K key, V value)
boolean replace(K key, V value)
V replace(K key, V value)
V getAndReplace(K key, V value)
boolean replace(K key, V oldValue, V newValue)
boolean replace(K key, V oldValue, V newValue)
java.util.concurrent.ConcurrentMap<K,V>
javax.cache.Cache<K,V>
int size()
Set<K> keySet()
Collection<V> values()
Set<Map.Entry<K, V>> entrySet()
Iterator<Cache.Entry<K, V>> iterator()
Chapter 14. Virtualization Configuration options can be used to exclude weak ciphers Previously, libvirt depended on the hard-coded cipher defaults in GnuTLS . This made it possible to use weak ciphers. With this update, configuration options to exclude weak ciphers have been added to the libvirtd.conf and libvirt.conf files. In addition, TLS priority support was added to libvirt URIs. As a a result, the list of used ciphers can be customized to exclude weak ciphers. (BZ# 1333415 ) Improved Hyper-V storage driver performance The storvsc Hyper-V storage driver was updated from upstream. This provides moderate performance improvement of I/O operations when using the Hyper-V storvsc driver for certain workloads. (BZ#1352824) Hyper-V clock source changed to use the TSC page With this update, the Time Stamp Counter (TSC) page is used as the Hyper-V clock source. The TSC page provides a more efficient way of computing the per-guest reference counter value than the previously used model-specific register (MSR). As a result, kernel operations that involve reading time stamps are now faster. Note that this feature is only supported on 64-bit kernels. (BZ#1365049) Setting the account password is now possible for any guest user The guest-set-user-password command has been introduced for the QEMU guest agent. This allows setting the account password for any guest user, including the root, when using QEMU and KVM. (BZ# 1303906 )

Commands:
10.8. RAID and Other Disk Devices Some storage technology requires special consideration when using Red Hat Enterprise Linux. Generally, it is important to understand how these technologies are configured, visible to Red Hat Enterprise Linux, and how support for them might have changed between major versions. 10.8.1. Hardware RAID RAID (Redundant Array of Independent Disks) allows a group, or array, of drives to act as a single device. Configure any RAID functions provided by the mainboard of your computer, or attached controller cards, before you begin the installation process. Each active RAID array appears as one drive within Red Hat Enterprise Linux. 10.8.2. Software RAID On systems with more than one hard drive, you can use the Red Hat Enterprise Linux installation program to operate several of the drives as a Linux software RAID array. With a software RAID array, RAID functions are controlled by the operating system rather than dedicated hardware. These functions are explained in detail in Section 13.15.4, "Manual Partitioning" . Note When a pre-existing RAID array's member devices are all unpartitioned disks/drives, the installer will treat the array itself as a disk and will not provide a way to remove the array. 10.8.3. USB Disks You can connect and configure external USB storage after installation. Most such devices are recognized by the kernel and available for use at that time. Some USB drives might not be recognized by the installation program. If configuration of these disks at installation time is not vital, disconnect them to avoid potential problems.

Commands:
Chapter 1. Prerequisites for establishing a trust This documentation aims to help you create a trust between your Identity Management (IdM) server and Active Directory (AD), where both servers are located in the same forest. Prerequisites First, read the Planning a cross-forest trust between Identity Management and Active Directory document. AD is installed with a domain controller on it. The IdM server is installed and running. For details, see Installing Identity Management . Both the AD server and the IdM server must have their clocks in sync because Kerberos requires a maximum delay of five minutes in communication. Unique NetBIOS names for each of the servers placed in the trust because the NetBIOS names are critical for identifying the AD domain. The NetBIOS name of an AD or IdM domain is usually the first part of the corresponding DNS domain. If the DNS domain is ad.example.com , the NetBIOS name is typically AD . However, it is not required. Important is that the NetBIOS name is just one word without periods. The maximum length of a NetBIOS name is 15 characters. The IdM system must have the IPv6 protocol enabled in the kernel. If IPv6 is disabled, then the CLDAP plug-in used by the IdM services fails to initialize. NOTE In RHEL 7, synchronization and trust were two possible approaches to indirect integration of RHEL systems to Active Directory (AD). In RHEL 8, synchronization is deprecated and in RHEL 9, it is not available any more. To integrate IdM and AD, use the trust approach instead. To migrate from synchronization to trust in RHEL 8, see Migrating an existing environment from synchronization to trust in the context of integrating a Linux domain with an Active Directory domain .

Commands: