mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 8. Cloud integrations on the Hybrid Cloud Console You can integrate some public clouds and third-party applications with the Hybrid Cloud Console. For information about integrating third-party applications to receive event notifications, see Integrating the Red Hat Hybrid Cloud Console with third-party applications . A cloud integration on the Red Hat Hybrid Cloud Console is an association with a public cloud service, application, or provider that supplies data to a Hybrid Cloud Console service. Services on the Hybrid Cloud Console use the integrations service to connect with public cloud providers and other services or tools to collect information for the service. You can integrate the following public clouds with the Hybrid Cloud Console: Amazon Web Services (AWS) Microsoft Azure Google Cloud Oracle Cloud You can also connect your Red Hat OpenShift Container Platform environment to the Hybrid Cloud Console as a cloud integration to use with the cost management service on the console. You can add and manage cloud and Red Hat integrations from the Integrations* page, located in the Hybrid Cloud Console Settings menu. The Integrations service uses a wizard to help you connect cloud and Red Hat integrations to the Hybrid Cloud Console. For cloud integrations, you can associate the provider with Red Hat services, including cost management, launch images, and the Red Hat Enterprise Linux (RHEL) management bundle. For Red Hat integrations, you can add Red Hat OpenShift Container Platform. Associating a service is optional for cloud integrations, but is required for Red Hat integrations. For detailed information about adding cloud or Red Hat integrations to the Red Hat Hybrid Cloud Console, see Configuring cloud integrations for Red Hat services .

Commands:
14.7.7. Setting and Displaying the Node Memory Parameters The node-memory-tune [shm-pages-to-scan] [shm-sleep-milisecs] [shm-merge-across-nodes] command displays and allows you to set the node memory parameters. There are three parameters that may be set with this command: shm-pages-to-scan - sets the number of pages to scan before the shared memory service goes to sleep. shm-sleep-milisecs - sets the number of milliseconds that the shared memory service will sleep before the scan shm-merge-across-nodes - specifies if pages from different NUMA nodes can be merged. Values allowed are 0 and 1 . When set to 0 , the only pages that can be merged are those that are physically residing in the memory area of the same NUMA node. When set to 1 , pages from all of the NUMA nodes can be merged. The default setting is 1 .

Commands:
Chapter 2. Installation This chapter guides you through the steps to install AMQ OpenWire JMS in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To build programs with AMQ OpenWire JMS, you must install Apache Maven . To use AMQ OpenWire JMS, you must install Java. 2.2. Using the Red Hat Maven repository Configure your Maven environment to download the client library from the Red Hat Maven repository. Procedure Add the Red Hat repository to your Maven settings or POM file. For example configuration files, see Section B.1, "Using the online repository" . <repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository> Add the library dependency to your POM file. <dependency> <groupId>org.apache.activemq</groupId> <artifactId>activemq-client</artifactId> <version>5.11.0.redhat-630416</version> </dependency> The client is now available in your Maven project. 2.3. Installing a local Maven repository As an alternative to the online repository, AMQ OpenWire JMS can be installed to your local filesystem as a file-based Maven repository. Procedure Use your subscription to download the AMQ Broker 7.8.2 Maven repository .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-broker-7.8.2-maven-repository.zip On Windows, right-click the .zip file and select Extract All . Configure Maven to use the repository in the maven-repository directory inside the extracted install directory. For more information, see Section B.2, "Using a local repository" . 2.4. Installing the examples Procedure Use your subscription to download the AMQ Broker 7.8.2 .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-broker-7.8.2.zip On Windows, right-click the .zip file and select Extract All . When you extract the contents of the .zip file, a directory named amq-broker-7.8.2 is created. This is the top-level directory of the installation and is referred to as <install-dir> throughout this document.

Commands:
<repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository>
<dependency> <groupId>org.apache.activemq</groupId> <artifactId>activemq-client</artifactId> <version>5.11.0.redhat-630416</version> </dependency>
unzip amq-broker-7.8.2-maven-repository.zip
unzip amq-broker-7.8.2.zip
8.8. Replication Traffic on Internal Networks Some cloud providers charge less for traffic over internal IP addresses than for traffic over public IP addresses, or do not charge at all for internal network traffic (for example, GoGrid ). To take advantage of lower rates, you can configure Red Hat JBoss Data Grid to transfer replication traffic using the internal network. With such a configuration, it is difficult to know the internal IP address you are assigned. JBoss Data Grid uses JGroups interfaces to solve this problem. Report a bug

Commands:
2.5. Advanced Configuration Features such as server discovery, load balancing, failover, retry, and retry delay, may be customized if the default policy is not appropriate. Refer to the org.teiid.net.socket.ServerDiscovery interface and default implementation org.teiid.net.socket.UrlServerDiscovery for more information on customization. The UrlServerDiscovery implementation provides the following features: discovery of servers from URL hosts (including the data source server and alternative servers) random selection for load balancing and failover one connection attempt per host no biasing black listing Typically you'll want to extend the UrlServerDiscovery so that it can be used as the fall-back strategy and to only implement the necessary changed methods. It is important to consider that one ServerDiscovery instance will be created for each connection. Any sharing of information between instances should be done through static state or some other shared lookup. Your customized server discovery class must be referenced by the discoveryStrategy connection/DataSource property using its full class name.

Commands:
Chapter 7. Red Hat Decision Manager reference implementations Red Hat Decision Manager provides reference implementations that you can use as starter applications. They are included in the Red Hat Process Automation Manager 7.13.5 Reference Implementations download, available on the Red Hat Decision Manager Software Downloads page in the Red Hat Customer Portal. Employee Rostering reference implementation The employee rostering reference implementation enables you to create an application that assigns employees to shifts on various positions in an organization. For example, you can use the application to distribute shifts in a hospital between nurses, guard duty shifts across a number of locations, or shifts on an assembly line between workers. Vehicle route planning reference implementation The vehicle route planning reference implementation enables you to create an application that solves a vehicle route planning problem with real-world maps, roads, and vehicles delivering goods to locations, each with a specific capacity. For more information, see the README file in the vehicle routing ZIP file, included in the reference implementation download. School timetable reference implementation The school timetable reference implementation enables you to build a REST application on Spring Boot that associates lessons with rooms and time slots and avoids conflicts by considering student and teacher constraints. High available event-driven decisioning reference implementation The high available event-driven decisioning reference implementation enables you to deploy Drools engine code that requires stateful processing, including rules developed with complex event processing, in an OpenShift environment. Doing this enables the decision engine to process complex event series with high availability.

Commands:
21.13. Missing Characters on Guest Console with Japanese Keyboard On a Red Hat Enterprise Linux 6 host, connecting a Japanese keyboard locally to a machine may result in typed characters such as the underscore (the _ character) not being displayed correctly in guest consoles. This occurs because the required keymap is not set correctly by default. With Red Hat Enterprise Linux 3 and Red Hat Enterprise Linux 6 guests, there is usually no error message produced when pressing the associated key. However, Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5 guests may display an error similar to the following: To fix this issue in virt-manager , perform the following steps: Open the affected guest in virt-manager . Click View Details . Select Display VNC in the list. Change Auto to ja in the Keymap pull-down menu. Click the Apply button. Alternatively, to fix this issue using the virsh edit command on the target guest: Run virsh edit <target guest> Add the following attribute to the <graphics> tag: keymap='ja' . For example:

Commands:
atkdb.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0). atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
<graphics type='vnc' port='-1' autoport='yes' keymap='ja' />
5.156. libservicelog 5.156.1. RHBA-2012:0988 - libservicelog bug fix update Updated libservicelog packages that fix one bug are now available for Red Hat Enterprise Linux 6. The libservicelog packages provide a library for logging service-related events to the servicelog database, and a number of command-line utilities for viewing the contents of the database. Bug Fix BZ# 814171 Prior to this update, the "servicelog_manage --truncate" command cleared only the "events" table. As a consequence, the other tables were not deleted. This update modifies the option "servicelog_event_delete()" function so that all rows in all tables associated with a deleted event are correctly deleted. Now, the tables for "callouts", "os", "rtas", "enclosure" and "repair_actions" are cleared together with the "events" table. All users of libservicelog are advised to upgrade to these updated packages, which fix this bug.

Commands:
7.2. The Storage Pool Manager The Storage Pool Manager (SPM) is a role given to one of the hosts in the data center enabling it to manage the storage domains of the data center. The SPM entity can be run on any host in the data center; the Red Hat Virtualization Manager grants the role to one of the hosts. The SPM does not preclude the host from its standard operation; a host running as SPM can still host virtual resources. The SPM entity controls access to storage by coordinating the metadata across the storage domains. This includes creating, deleting, and manipulating virtual disks (images), snapshots, and templates, and allocating storage for sparse block devices (on SAN). This is an exclusive responsibility: only one host can be the SPM in the data center at one time to ensure metadata integrity. The Red Hat Virtualization Manager ensures that the SPM is always available. The Manager moves the SPM role to a different host if the SPM host encounters problems accessing the storage. When the SPM starts, it ensures that it is the only host granted the role; therefore it will acquire a storage-centric lease. This process can take some time.

Commands:
5.366. xorg-x11-drv-wacom 5.366.1. RHBA-2012:0801 - xorg-x11-drv-wacom bug fix and enhancement update Updated xorg-x11-drv-wacom packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-wacom packages provide an X Window System input device driver that allows the X server to handle Wacom tablets with extended functionality. The xorg-x11-drv-wacom package has been upgraded to upstream version 0.13.0, which provides a number of bug fixes and enhancements over the version. (BZ# 752642 ) Bug Fixes BZ# 734256 Prior to this update, the xorg-x11-drv-wacom driver allowed users only to use a pointer-focusing model. As a consequence, a dual-monitor layout on certain hardware could lead to an offset between the pen position and the cursor position. This update modifies the mapping offset in screen mode to provide new multi-screen handling. BZ# 802385 Prior to this update, xorg-x11-drv-wacom driver could, under certain circumstances, encounter an "off by one" error in the array access of files and a null dereference. This update modifies the array indexing and checks for the right allocation before dereferencing. Enhancements BZ# 801319 This update adds xorg-x11-drv-wacom to HPC Compute Node ( v. 6 ). Now, xorg-x11-drv-wacom is a dependency for the gnome-settings-daemon and the control-center. BZ# 818038 This update adds support for the Wacom Intuos4 Wireless device. All users of xorg-x11-drv-wacom are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
6.2. Upgrading Packages The IdM server packages are updated when the system packages are updated: This is the easiest way to upgrade the server because it automatically pulls in updates for related services, like SSSD, which provide Identity Management functionality. To upgrade the IdM server packages specifically, run yum on the master server: It can take several seconds for the update process to apply all of the changes. Note It is not necessary to update all servers and replicas at precisely the same time; the IdM servers will still work with each other and replicate data successfully. The older IdM servers will simply lack the new features.

Commands:
yum update
yum update ipa-server
Chapter 3. Red Hat build of OpenJDK features The latest Red Hat build of OpenJDK 17 release might include new features. Additionally, the latest release might enhance, deprecate, or remove features that originated from Red Hat build of OpenJDK 17 releases. Note For all the other changes and security fixes, see OpenJDK 17.0.6 Released . Red Hat build of OpenJDK enhancements Red Hat build of OpenJDK 17 provides enhancements to features originally created in releases of Red Hat build of OpenJDK. Enhanced BMP bounds By default, Red Hat build of OpenJDK 17.0.6 disables loading a linked International Color Consortium (ICC) profile in a BMP image. You can enable this functionality by setting the new sun.imageio.bmp.enabledLinkedProfiles property to true . This property replaces the old sun.imageio.plugins.bmp.disableLinkedProfiles property See JDK-8295687 (JDK Bug System) . Improved banking of sounds Previously, the SoundbankReader implementation, com.sun.media.sound.JARSoundbankReader , downloaded a JAR soundbank from a URL. For Red Hat build of OpenJDK 17.0.6, this behavior is now disabled by default. To re-enable the behavior, set the new system property jdk.sound.jarsoundbank to true . See JDK-8293742 (JDK Bug System) . Enhanced Datagram Transport Layer Security (DTLS) performance Red Hat build of OpenJDK now exchanges DTLS cookies for all new and resumed handshake communications. To re-enable the release behavior, set the new system property jdk.tls.enableDtlsResumeCookie to false . See JDK-8287411 (JDK Bug System) . Added note for LoginModule implementation The Red Hat build of OpenJDK 9 release changed the Set implementation, which holds principals and credentials, so that the implementation can reject null values. Any attempts to call add(null) , contains(null) , or remove(null) would throw a NullPointerException message. The Red Hat build of OpenJDK 9 release did not update the logout() method in the LoginModule implementation to check for null values. These values could occur because of a failed login attempt, which can cause a logout() call to throw a NullPointerException message. The Red Hat build of OpenJDK 17.0.6 release updates the LoginModule implementations to check for null values. Additionally, the release adds an implementation note to the specification that states the change also applies to third-party modules. The note advises developers of third-party modules to verify that a logout() method does not throw a NullPointerException message. See JDK-8015081 (JDK Bug System). See JDK-8282730 (JDK Bug System).

Commands:
33.3. Adding a Samba (SMB) Printer You can add a Samba (SMB) based printer share by clicking the New Printer button in the main Printer Configuration Tool window to display the window in Figure 33.2, " Adding a Printer " . Enter a unique name for the printer in the Printer Name field. The printer name can contain letters, numbers, dashes (-), and underscores (_); it must not contain any spaces. You can also use the Description and Location fields to further distinguish this printer from others that may be configured on your system. Both of these fields are optional, and may contain spaces. Figure 33.5. Adding a SMB Printer As shown in Figure 33.5, "Adding a SMB Printer" , available SMB shares are automatically detected and listed in the Share column. Click the arrow ( ) beside a Workgroup to expand it. From the expanded list, select a printer. If the printer you are looking for does not appear in the list, enter the SMB address in the smb:// field. Use the format computer name/printer share . In Figure 33.5, "Adding a SMB Printer" , the computer name is dellbox , while the printer share is r2 . In the Username field, enter the username to access the printer. This user must exist on the SMB system, and the user must have permission to access the printer. The default user name is typically guest for Windows servers, or nobody for Samba servers. Enter the Password (if required) for the user specified in the Username field. You can then test the connection by clicking Verify . Upon successful verification, a dialog box appears confirming printer share accessibility. , select the printer type. Refer to Section 33.5, "Selecting the Printer Model and Finishing" for details. Warning Samba printer usernames and passwords are stored in the printer server as unencrypted files readable by root and lpd. Thus, other users that have root access to the printer server can view the username and password you use to access the Samba printer. As such, when you choose a username and password to access a Samba printer, it is advisable that you choose a password that is different from what you use to access your local Red Hat Enterprise Linux system. If there are files shared on the Samba print server, it is recommended that they also use a password different from what is used by the print queue.

Commands:
Chapter 4. Knative Eventing Knative Eventing on OpenShift Container Platform enables developers to use an event-driven architecture with serverless applications. An event-driven architecture is based on the concept of decoupled relationships between event producers and event consumers. Event producers create events, and event sinks , or consumers, receive events. Knative Eventing uses standard HTTP POST requests to send and receive events between event producers and sinks. These events conform to the CloudEvents specifications , which enables creating, parsing, sending, and receiving events in any programming language. Knative Eventing supports the following use cases: Publish an event without creating a consumer You can send events to a broker as an HTTP POST, and use binding to decouple the destination configuration from your application that produces events. Consume an event without creating a publisher You can use a trigger to consume events from a broker based on event attributes. The application receives events as an HTTP POST. To enable delivery to multiple types of sinks, Knative Eventing defines the following generic interfaces that can be implemented by multiple Kubernetes resources: Addressable resources Able to receive and acknowledge an event delivered over HTTP to an address defined in the status.address.url field of the event. The Kubernetes Service resource also satisfies the addressable interface. Callable resources Able to receive an event delivered over HTTP and transform it, returning 0 or 1 new events in the HTTP response payload. These returned events may be further processed in the same way that events from an external event source are processed. 4.1. Using the Knative broker for Apache Kafka The Knative broker implementation for Apache Kafka provides integration options for you to use supported versions of the Apache Kafka message streaming platform with OpenShift Serverless. Kafka provides options for event source, channel, broker, and event sink capabilities. Knative broker for Apache Kafka provides additional options, such as: Kafka source Kafka channel Kafka broker Kafka sink 4.2. Additional resources Installing the KnativeKafka custom resource . Red Hat AMQ Streams documentation Red Hat AMQ Streams TLS and SASL on Apache Kafka documentation Event delivery

Commands:
5.5. Setting up a Linux Client Through Kickstart A kickstart enrollment automatically adds a new system to the IdM domain at the time it is provisioned. This requires pre-creating the hosts on the IdM server, with a predefined password that can be used to authenticate to complete the enrollment operation. Create the host entry on the IdM server and set a temporary Kerberos password for the entry. When the ipa-client-install script is run normally (interactively), it prompts for authentication credentials to access the IdM domain. However, when the script is run automatically, the system has to have some way to access the IdM domain without using an existing IdM user; this is done by setting the host principal in the script and using a Kerberos password (configured for the host account) to access the IdM domain. For example: The password expires after the first authentication attempt. After enrollment completes, the host is authenticated using its keytab. Include the ipa-client package with the other install packages. Create a post-install instruction that ensures SSH keys are generated before enrollment, runs the ipa-client-install script, passes all the required information to access and configure the IdM domain services, and specifies the pre-set password. Use the --unattended option to instruct the script to run non-interactively. Note Red Hat recommends not to start the sshd service prior to the kickstart enrollment. While starting sshd before enrolling the client generates the SSH keys automatically, using the above script is the preferred solution. Run the kickstart script.

Commands:
[jsmith@server ~]USD ipa host-add kickstart-server.example.com --password=secret
%packages @ X Window System @ Desktop @ Sound and Video ipa-client
%post --log=/root/ks-post.log Generate SSH keys to ensure that ipa-client-install uploads them to the IdM server /usr/bin/ssh-keygen -q -t rsa -f /etc/ssh/ssh_host_rsa_key -C '' -N '' chmod 600 /etc/ssh/ssh_host_rsa_key chmod 644 /etc/ssh/ssh_host_rsa_key.pub /sbin/restorecon /etc/ssh/ssh_host_rsa_key.pub /usr/bin/ssh-keygen -q -t rsa1 -f /etc/ssh/ssh_host_key -C '' -N '' chmod 600 /etc/ssh/ssh_host_key chmod 644 /etc/ssh/ssh_host_key.pub /sbin/restorecon /etc/ssh/ssh_host_key.pub /usr/bin/ssh-keygen -q -t dsa -f /etc/ssh/ssh_host_dsa_key -C '' -N '' chmod 600 /etc/ssh/ssh_host_dsa_key chmod 644 /etc/ssh/ssh_host_dsa_key.pub /sbin/restorecon /etc/ssh/ssh_host_dsa_key.pub Get the hostname to set as the host principal /bin/hostname > /tmp/hostname.txt Run the client install script /usr/sbin/ipa-client-install --domain= EXAMPLEDOMAIN --enable-dns-updates --mkhomedir -w secret --realm= EXAMPLEREALM --server= server.example.com --unattended