mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix A. Using your subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the AMQ Streams for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-04-29 12:49:16 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
Chapter 372. XML Beans DataFormat (deprecated) Available as of Camel version 1.2 XmlBeans is a Data Format which uses the XmlBeans library to unmarshal an XML payload into Java objects or to marshal Java objects into an XML payload. from("activemq:My.Queue"). unmarshal().xmlBeans(). to("mqseries:Another.Queue"); 372.1. Options The XML Beans dataformat supports 2 options, which are listed below. Name Default Java Type Description prettyPrint false Boolean To enable pretty printing output nicely formatted. Is by default false. contentTypeHeader false Boolean Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSon etc. 372.2. Spring Boot Auto-Configuration The component supports 3 options, which are listed below. Name Description Default Type camel.dataformat.xmlbeans.content-type-header Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSon etc. false Boolean camel.dataformat.xmlbeans.enabled Enable xmlbeans dataformat true Boolean camel.dataformat.xmlbeans.pretty-print To enable pretty printing output nicely formatted. Is by default false. false Boolean 372.3. Dependencies To use XmlBeans in your camel routes you need to add the dependency on camel-xmlbeans which implements this data format. If you use maven you could just add the following to your pom.xml, substituting the version number for the latest & greatest release (see the download page for the latest versions). <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-xmlbeans</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>

Commands:
from("activemq:My.Queue"). unmarshal().xmlBeans(). to("mqseries:Another.Queue");
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-xmlbeans</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>
20.31. Deleting Storage Volumes The virsh vol-delete vol pool command deletes a given volume. The command requires a the name or UUID of the storage pool the volume is in as well as the name of the storage volume. In lieu of the volume name the key or path of the volume to delete may also be used. Example 20.91. How to delete a storage volume The following example deletes a storage volume named new-vol , which contains the storage pool vdisk :

Commands:
virsh vol-delete new-vol vdisk vol new-vol deleted
Chapter 3. Practical tutorial: Log into the Dashboard Builder Now that you know a little about what the Dashboard Builder can do, you can log into it and have a look for yourself. 3.1. Prerequisites Name Description Red Hat JBoss Data Virtualization Red Hat JBoss Data Virtualization must be installed and running. (Please refer back to the Getting Started Guide if you need a refresher on this.) Dashboard Builder Account and Password You must have a valid account and password. (You would have set this up during installation.) A pre-configured data source Red Hat JBoss Data Virtualization must be connected to a data source before you proceed with this work. 3.2. Log into the Dashboard Builder Navigate to JBoss Dashboard Builder in your web browser. The default location is http://localhost:8080/dashboard/ . Log in using a valid username and password.

Commands:
12.8.3. Configuring the Virtual Machine to Use a vHBA LUN After a storage pool is created for a vHBA, add the vHBA LUN to the virtual machine configuration. Find available LUNs First, use the virsh vol-list command in order to generate a list of available LUNs on the vHBA. For example: The list of LUN names displayed will be available for use as disk volumes in virtual machine configurations. Add the vHBA LUN to the virtual machine Add the vHBA LUN to the virtual machine by specifying in the virtual machine's XML: the device type as lun or disk in the <disk> parameter, and the source device in the <source> parameter. Note this can be entered as /dev/sdaN , or as a symbolic link generated by udev in /dev/disk/by-path|by-id|by-uuid|by-label , which can be found by running the virsh vol-list pool command. For example: <disk type='block' device='lun'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-path/pci-0000\:04\:00.1-fc-0x203400a0b85ad1d7-lun-0'/> <target dev='sda' bus='scsi'/> </disk>

Commands:
virsh vol-list vhbapool_host3 Name Path ------------------------------------------------------------------------------ unit:0:4:0 /dev/disk/by-path/pci-0000:10:00.0-fc-0x5006016844602198-lun-0 unit:0:5:0 /dev/disk/by-path/pci-0000:10:00.0-fc-0x5006016044602198-lun-0
<disk type='block' device='lun'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-path/pci-0000\:04\:00.1-fc-0x203400a0b85ad1d7-lun-0'/> <target dev='sda' bus='scsi'/> </disk>
8.2. Required Time Management Parameters for Red Hat Enterprise Linux Guests For certain Red Hat Enterprise Linux guest virtual machines, additional kernel parameters are required for their system time to be synchronised correctly. These parameters can be set by appending them to the end of the /kernel line in the /etc/grub2.cfg file of the guest virtual machine. Note Red Hat Enterprise Linux 5.5 and later, Red Hat Enterprise Linux 6.0 and later, and Red Hat Enterprise Linux 7 use kvm-clock as their default clock source. Running kvm-clock avoids the need for additional kernel parameters, and is recommended by Red Hat. The table below lists versions of Red Hat Enterprise Linux and the parameters required on the specified systems. Table 8.1. Kernel parameter requirements Red Hat Enterprise Linux version Additional guest kernel parameters 7.0 and later on AMD64 and Intel 64 systems with kvm-clock Additional parameters are not required 6.1 and later on AMD64 and Intel 64 systems with kvm-clock Additional parameters are not required 6.0 on AMD64 and Intel 64 systems with kvm-clock Additional parameters are not required 6.0 on AMD64 and Intel 64 systems without kvm-clock notsc lpj= n Note The lpj parameter requires a numeric value equal to the loops per jiffy value of the specific CPU on which the guest virtual machine runs. If you do not know this value, do not set the lpj parameter.

Commands:
Part I. Introduction to Red Hat OpenStack Platform and OpenShift Container Platform Bare Metal Hardware Certification Program Use this guide to learn about the steps required to achieve Red Hat OpenStack Platform and Red Hat OpenShift Container Platform bare metal hardware certification. Important The Red Hat Hardware Certification Program presumes an advanced level of hardware and Red Hat product knowledge and skills. The Red Hat product support is neither offered nor covered in the Red Hat Hardware Certification Program, but is available for purchase separately.

Commands:
31.4. Adding HBAC Service Groups HBAC service groups can simplify HBAC rules management: instead of adding individual services to an HBAC rule, you can add a whole service group. To add an HBAC service group, you can use: the IdM web UI (see the section called "Web UI: Adding an HBAC Service Group" ) the command line (see the section called "Command Line: Adding an HBAC Service Group" ) Web UI: Adding an HBAC Service Group Select Policy Host-Based Access Control HBAC Service Groups . Click Add to add an HBAC service group. Enter a name for the service group, and click Add and Edit . On the service group configuration page, click Add to add an HBAC service as a member of the group. Figure 31.7. Adding HBAC Services to an HBAC Service Group Command Line: Adding an HBAC Service Group Use the ipa hbacsvcgroup-add command to add an HBAC service group. For example, to add a group named login : Use the ipa hbacsvcgroup-add-member command to add an HBAC service as a member of the group. For example, to add the sshd service to the login group:

Commands:
ipa hbacsvcgroup-add Service group name: login -------------------------------- Added HBAC service group "login" -------------------------------- Service group name: login
ipa hbacsvcgroup-add-member Service group name: login [member HBAC service]: sshd Service group name: login Member HBAC service: sshd ------------------------- Number of members added 1 -------------------------
16.21. Installation Complete Congratulations! Your Red Hat Enterprise Linux installation is now complete! The installation program prompts you to prepare your system for reboot. Remember to remove any installation media if it is not ejected automatically upon reboot. After your computer's normal power-up sequence has completed, Red Hat Enterprise Linux loads and starts. By default, the start process is hidden behind a graphical screen that displays a progress bar. Eventually, a login: prompt or a GUI login screen (if you installed the X Window System and chose to start X automatically) appears. The first time you start your Red Hat Enterprise Linux system in run level 5 (the graphical run level), the FirstBoot tool appears, which guides you through the Red Hat Enterprise Linux configuration. Using this tool, you can set your system time and date, install software, register your machine with Red Hat Network, and more. FirstBoot lets you configure your environment at the beginning, so that you can get started using your Red Hat Enterprise Linux system quickly. Chapter 34, Firstboot will guide you through the configuration process.

Commands:
Part V. Designing a decision service using spreadsheet decision tables As a business analyst or business rules developer, you can define business rules in a tabular format in spreadsheet decision tables and then upload the spreadsheets to your project in Business Central. These rules are compiled into Drools Rule Language (DRL) and form the core of the decision service for your project. Note You can also design your decision service using Decision Model and Notation (DMN) models instead of rule-based or table-based assets. For information about DMN support in Red Hat Decision Manager 7.13, see the following resources: Getting started with decision services (step-by-step tutorial with a DMN decision service example) Designing a decision service using DMN models (overview of DMN support and capabilities in Red Hat Decision Manager) Prerequisites The space and project for the decision tables have been created in Business Central. Each asset is associated with a project assigned to a space. For details, see Getting started with decision services .

Commands:
23.9. NUMA Node Tuning After NUMA node tuning is done using virsh edit , the following domain XML parameters are affected: <domain> ... <numatune> <memory mode="strict" nodeset="1-4,^3"/> </numatune> ... </domain> Figure 23.11. NUMA node tuning Although all are optional, the components of this section of the domain XML are as follows: Table 23.6. NUMA node tuning elements Element Description <numatune> Provides details of how to tune the performance of a NUMA host physical machine by controlling NUMA policy for domain processes. <memory> Specifies how to allocate memory for the domain processes on a NUMA host physical machine. It contains several optional attributes. The mode attribute can be set to interleave , strict , or preferred . If no value is given it defaults to strict . The nodeset attribute specifies the NUMA nodes, using the same syntax as the cpuset attribute of the <vcpu> element. Attribute placement can be used to indicate the memory placement mode for the domain process. Its value can be either static or auto . If the <nodeset> attribute is specified it defaults to the <placement> of <vcpu> , or static . auto indicates the domain process will only allocate memory from the advisory nodeset returned from querying numad and the value of the nodeset attribute will be ignored if it is specified. If the <placement> attribute in vcpu is set to auto , and the <numatune> attribute is not specified, a default <numatune> with <placement> auto and strict mode will be added implicitly.

Commands:
<domain> <numatune> <memory mode="strict" nodeset="1-4,^3"/> </numatune> </domain>
7.32. crash 7.32.1. RHBA-2013:0317 - crash bug fix and enhancement update Updated crash packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The crash packages provide a self-contained tool that can be used to investigate live systems, and kernel core dumps created from the netdump, diskdump, kdump, and Xen/KVM "virsh dump" facilities from Red Hat Enterprise Linux. Note The crash packages have been upgraded to upstream version 6.1.0, which provides a number of bug fixes and enhancements over the version. (BZ# 840051 ) Bug Fix BZ#843093 A recent time-keeping backport to the Red Hat Enterprise Linux 6 kernel caused the crash utility to fail during initialization with the "crash: cannot resolve: xtime" error message. This update modifies crash to recognize and handle the time-keeping change in the kernel so that crash now successfully starts up as expected. Enhancements BZ#739094 The crash utility has been modified to support dump files in the firmware-assisted dump (fadump) format for the 64-bit PowerPC architecture. BZ# 834260 The "struct -o" option has been enhanced to accept a virtual address argument. If an address argument is entered, the structure members are prepended by their virtual address. BZ# 834276 The "bt" command has been enhanced by adding new "-s" and "[-xd]" options that allow displaying symbol names plus their offset in each frame. The default behavior is unchanged where only the symbol name is displayed. The symbol offset is expressed in the default output format, which can be overridden using the "-x" (hexadecimal) or "-d" (decimal) options. All users of crash are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
5.109. iok 5.109.1. RHBA-2012:1164 - iok bug fix update Updated iok packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The iok package contains an Indic on-screen virtual keyboard that supports the Assamese, Bengali, Gujarati, Hindi, Kannada, Marathi, Malayalam, Punjabi, Oriya, Sindhi, Tamil and Telugu languages. Currently, iok works with Inscript and xkb keymaps for Indian languages, and is able to parse and display non-Inscript keymaps as well. Bug Fixes BZ# 814541 , BZ# 814548 Previously, when saving a keymap with a specified name, predefined naming convention was followed and the file name was saved with the "-" prefix without noticing the user. With this update, if the user attempts to save a keymap, a dialog box displaying the required file name format appears. BZ# 819795 This update provides the complete iok translation for all supported locales. All users of iok are advised to upgrade to these updated packages, which fix these bugs. 5.109.2. RHBA-2012:0392 - iok bug fix update An updated iok package that fixes multiple bugs is now available for Red Hat Enterprise Linux 6. The iok package contains an Indic on-screen virtual keyboard that supports the Assamese, Bengali, Gujarati, Hindi, Kannada, Marathi, Malayalam, Punjabi, Oriya, Sindhi, Tamil and Telugu languages. Currently, iok works with Inscript and xkb keymaps for Indian languages, and is able to parse and display non-Inscript keymaps as well. The iok package has been upgraded to upstream version 1.3.13, which provides a number of bug fixes over the version. Bug Fixes BZ# 736992 Due to xkb keymaps being rewritten in a recent update of the xkeyboard-config package, the iok's language list contained incorrect xkb keymap names when selecting the Hindi X Keyboard Extension (XKB). To fix this problem, the iok's xkb parser has been rewritten. BZ# 752667 Previously, iok looked for files with the ".mim" suffix in the "~/.m17n" directory instead of the "~/.m17n.d" directory. This update modifies the directory path to the correct "~/.m17n.d" so that the user-defined keymap files are saved in the correct directory. BZ# 752668 Previously, when using the on-screen keyboard, mouse clicks on various characters worked as expected. However, finger inputs failed because the first selected character was selected regardless of what characters the user selected . With this update, users can use the drag-and-drop feature when running iok in advanced mode (the "iok -a" command), which allows users to drag the first key button over the second button. The drag-and-drop feature is not available in iok's default mode. BZ# 798592 Due to a small size of the xkb name array, if the user selected the xkb-Malayalam keymap (enhanced Indian Script with the Rupee sign), and then pressed the "To English" button, the iok utility could terminate unexpectedly. With this update, the size of the xkb name array has been increased so that the utility no longer crashes in the described scenario. All users of iok are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Chapter 13. Creating a new image from an existing customized build by using Insights image builder You can recreate an existing customized RHEL image by using Insights image builder. It recreates the exact image you want to recreate, but the new image is recreated with a different UUID. Additionally, the new image fetches the package updates and refreshes the content with those updates. You can customize this new image with additional customizations according to your requirements. 13.1. Creating a new image from an existing build To recreate a new image from an existing compose, follow the steps: Prerequisites You created an image and customized it according to your requirements. Procedure From the Image Builder dashboard, select the image you want to create an image from. From the Node options icon (⫶), select Recreate image . The Create image wizard opens. Note If the image status is Expired , click directly the Recreate image button. Optional: If you want to make any modifications to the image, such as adding new packages, navigate to the appropriate step using the menu on the left to make the customizations. Click . On the Review page, click Create image . The Insights image builder Images dashboard opens. The image build starts to recreate the image. You can see details such as the Image name, UUID, the cloud target environment, the image operating system release and the status of the image creation. Verification From the Status column, check if the image is Ready . Optional: Click Image details to display additional information about the recreated image.

Commands:
Chapter 5. The High Availability add-on The High Availability add-on provides on-demand failover services between nodes within a cluster. The add-on is available with a separate subscription. For details, see the Support Policies for RHEL High Availability Clusters . The following table lists all the packages available with the High Availability add-on along with their license. Package License awscli ASL 2.0 and MIT booth GPLv2+ booth-arbitrator GPLv2+ booth-core GPLv2+ booth-site GPLv2+ booth-test GPLv2+ clufter-bin GPLv2+ clufter-cli GPLv2+ clufter-common GPLv2+ clufter-lib-ccs GPLv2+ clufter-lib-general GPLv2+ clufter-lib-pcs GPLv2+ corosync BSD corosync-qdevice BSD corosync-qnetd BSD corosynclib-devel BSD fence-agents-aliyun GPLv2+ and LGPLv2+ and ASL 2.0 and BSD and MIT fence-agents-aws GPLv2+ and LGPLv2+ fence-agents-azure-arm GPLv2+ and LGPLv2+ fence-agents-gce GPLv2+ and LGPLv2+ and MIT fence-agents-openstack GPLv2+ and LGPLv2+ and ASL 2.0 and MIT and Python libknet1 LGPLv2+ libknet1-compress-bzip2-plugin LGPLv2+ libknet1-compress-lz4-plugin LGPLv2+ libknet1-compress-lzma-plugin LGPLv2+ libknet1-compress-lzo2-plugin LGPLv2+ libknet1-compress-plugins-all LGPLv2+ libknet1-compress-zlib-plugin LGPLv2+ libknet1-crypto-nss-plugin LGPLv2+ libknet1-crypto-openssl-plugin LGPLv2+ libknet1-crypto-plugins-all LGPLv2+ libknet1-plugins-all LGPLv2+ libnozzle1 LGPLv2+ pacemaker GPL-2.0-or-later AND LGPL-2.1-or-later pacemaker-cli GPL-2.0-or-later AND LGPL-2.1-or-later pacemaker-cts GPL-2.0-or-later AND LGPL-2.1-or-later pacemaker-doc CC-BY-SA-4.0 pacemaker-libs-devel GPL-2.0-or-later AND LGPL-2.1-or-later pacemaker-nagios-plugins-metadata GPLv3 pacemaker-remote GPL-2.0-or-later AND LGPL-2.1-or-later pcs GPL-2.0-only AND Apache-2.0 AND MIT AND BSD-3-Clause AND (Apache-2.0 OR BSD-3-Clause) AND (BSD-2-Clause OR Ruby) AND (BSD-2-Clause OR GPL-2.0-or-later) AND (GPL-2.0-only or Ruby) pcs-snmp GPL-2.0-only and BSD-2-Clause python3-azure-sdk MIT and ASL 2.0 and MPLv2.0 and BSD and Python python3-boto3 ASL 2.0 python3-botocore ASL 2.0 python3-clufter GPLv2+ and GFDL python3-fasteners ASL 2.0 python3-gflags BSD python3-google-api-client ASL 2.0 python3-httplib2 MIT python3-oauth2client ASL 2.0 python3-pacemaker LGPL-2.1-or-later python3-s3transfer ASL 2.0 python3-uritemplate BSD resource-agents GPLv2+ and LGPLv2+ resource-agents-aliyun GPLv2+ and LGPLv2+ and ASL 2.0 and BSD and MIT resource-agents-gcp GPLv2+ and LGPLv2+ and BSD and ASL 2.0 and MIT and Python resource-agents-paf PostgreSQL spausedd BSD

Commands: