mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Enhancements This section describes a highlighted set of enhancements and new features in AMQ Broker 7.9. For a complete list of enhancements in the release, see AMQ Broker 7.9.0 Enhancements . Note If you require the latest AMQ Broker Long Term Support (LTS) release version, see AMQ Broker 7.8 . AMQP server connections A broker can initiate connections to other endpoints using the AMQP protocol. This means, for example, that the broker can connect to other AMQP servers and create elements on those connections. This feature is implemented using the <broker-connection> element as described in Configuring AMQ Broker . Operator supports watching all or multiple namespaces In releases, you installed the AMQ Broker Operator in every namespace you required a broker deployment. Starting in 7.9, the AMQ Broker Operator supports watching all or multiple namespaces for broker custom resources. For more information, see Deploying AMQ Broker on OpenShift . Note If you have already installed a version of the AMQ Broker Operator in a namespace on your cluster, Red Hat recommends that you do not install the AMQ Broker Operator 7.9 version to watch that namespace to avoid potential conflicts. Temporary queue namespace In AMQ Broker 7.9, you can specify a temporary-queue-namespace in the broker.xml configuration file. You can then specify address settings that match the namespace and the broker applies those settings to all temporary queues. If a temporary queue namespace does not exist, temporary queues use the same address settings configuration as other queues. For more information, see Applying specific address settings to temporary queues in Configuring AMQ Broker . Operator channels The AMQ Broker Operator Red Hat Integration - AMQ Broker for RHEL 8 (Multiarch) is available with the following channels: 7.x - This channel will install 7.9 and update to 7.10 at some point in the future. If you want to install 7.10 now, you can subscribe to the 7.10.x channel. 7.8.x - This is the Long Term Support (LTS) channel. To determine which Operator to choose, see the Red Hat Enterprise Linux Container Compatibility Matrix . Hosts verified by default The default value for verifyHost has changed from false to true when applied to connectors. All inter-broker connections now verify hosts by default. The default value for acceptors continues to be false . Enabling the Prometheus plugin using a CR You can enable the Prometheus plugin on OpenShift using a CR in addition to enabling the plugin using an environment variable. Both options are described in Deploying AMQ Broker for On-Premise .

Commands:
10.2. QEMU Guest Agent The QEMU guest agent runs inside the guest and allows the host machine to issue commands to the guest operating system using libvirt. The guest operating system then responds to those commands asynchronously. This chapter covers the libvirt commands and options available to the guest agent. Important Note that it is only safe to rely on the guest agent when run by trusted guests. An untrusted guest may maliciously ignore or abuse the guest agent protocol, and although built-in safeguards exist to prevent a denial of service attack on the host, the host requires guest co-operation for operations to run as expected. Note that QEMU guest agent can be used to enable and disable virtual CPUs (vCPUs) while the guest is running, thus adjusting the number of vCPUs without using the hot plug and hot unplug features. Refer to Section 14.13.6, "Configuring Virtual CPU Count" for more information. 10.2.1. Install and Enable the Guest Agent Install qemu-guest-agent on the guest virtual machine with the yum install qemu-guest-agent command and make it run automatically at every boot as a service (qemu-guest-agent.service).

Commands:
Chapter 2. Installing Red Hat build of OpenJDK 17 for Microsoft Windows with the archive This procedure describes how to manually install Red Hat build of OpenJDK 17 for Microsoft Windows using the archive. Procedure Download the archive of Red Hat build of OpenJDK 17 for Microsoft Windows. Extract the contents of an archive to a directory of your choice. Note Extracting the contents of an archive to a directory path that does not contain spaces is recommended. Update the PATH as below: Add the bin directory contained in your Red Hat build of OpenJDK 17 for Microsoft Windows installation path to the %PATH% environment variable: If the path contains spaces, use the shortened path name. Restart Command Prompt to reload the environment variables. Verify the Red Hat build of OpenJDK 17 for Microsoft Windows is successfully installed, run java -version command in a command prompt and you must get the following output: The %JAVA_HOME% environment variable must also be set to use some developer tools. Set the %JAVA_HOME% environment variable as follows: Open Command Prompt as an administrator. Set the value of the environment variable to your Red Hat build of OpenJDK 17 for Microsoft Windows installation path: If the path contains spaces, use the shortened path name. Restart Command Prompt to reload the environment variables.

Commands:
C:\> setx /m PATH "%PATH%;C:\Progra~1\RedHat\java-17-openjdk-17.0.0.0.35-1\bin"
openjdk version "17" 2021-09-14 LTS OpenJDK Runtime Environment 21.9 (build 17+35-LTS) OpenJDK 64-Bit Server VM 21.9 (build 17+35-LTS, mixed mode, sharing)
C:\> setx /m JAVA_HOME "C:\Progra~1\RedHat\java-17-openjdk-17.0.0.0.35-1"
Appendix A. List of tickets by component Bugzilla and JIRA tickets are listed in this document for reference. The links lead to the release notes in this document that describe the tickets. Component Tickets Ansible - Configuration Management Bugzilla:2181595 Fact Bugzilla:1972308 Hammer Jira:SAT-23753 Installation Jira:SAT-20206 , Jira:SAT-21163 Logging Jira:SAT-20206 Provisioning Bugzilla:2153548 , Jira:SAT-18663 Puppet Bugzilla:2087067 Registration Bugzilla:1994654 , Bugzilla:2155444 , Bugzilla:2180568 Remote Execution Jira:SAT-19794 , Jira:SAT-20749 SCAP Plugin Jira:SAT-22421 Settings Jira:SAT-19793 , Jira:SAT-23934 Upgrades Jira:SAT-21163 Users & Roles Jira:SAT-18126 other Jira:SAT-23132 , Jira:SAT-24730 , Jira:SAT-22617 , Jira:SAT-17368 , Jira:SAT-20753 , Jira:SAT-20947 , Jira:SAT-20990 , Jira:SAT-20393 , Jira:SAT-20206 , Jira:SAT-20910 , Jira:SAT-19793 , Jira:SAT-24698 , Jira:SAT-24552 , Jira:SAT-19794 , Jira:SAT-20746 , Jira:SAT-20745 , Jira:SAT-18663 , Jira:SAT-18123 , Jira:SAT-20749 , Jira:SAT-23753 , Jira:SAT-24557 , Jira:SAT-20862 , Jira:SAT-21137 , Jira:SAT-23881 , Jira:SAT-21163 , Jira:SAT-22241

Commands:
4.7. Direct I/O Direct I/O is a feature of the file system whereby file reads and writes go directly from the applications to the storage device, bypassing the operating system read and write caches. Direct I/O is used only by applications (such as databases) that manage their own caches. An application invokes direct I/O by opening a file with the O_DIRECT flag. Alternatively, GFS can attach a direct I/O attribute to a file, in which case direct I/O is used regardless of how the file is opened. When a file is opened with O_DIRECT , or when a GFS direct I/O attribute is attached to a file, all I/O operations must be done in block-size multiples of 512 bytes. The memory being read from or written to must also be 512-byte aligned. One of the following methods can be used to enable direct I/O on a file: O_DIRECT GFS file attribute GFS directory attribute 4.7.1. O_DIRECT If an application uses the O_DIRECT flag on an open() system call, direct I/O is used for the opened file. To cause the O_DIRECT flag to be defined with recent glibc libraries, define _GNU_SOURCE at the beginning of a source file before any includes, or define it on the cc line when compiling.

Commands:
Chapter 8. Integrating with Red Hat Process Automation Manager You can integrate Red Hat Process Automation Manager with other products and components, such as Spring Boot, Red Hat Fuse, and Red Hat Single Sign-On. 8.1. Red Hat Process Automation Manager Spring Boot business applications Spring Framework is a Java platform that provides comprehensive infrastructure support for developing Java applications. Spring Boot is a lightweight framework based on Spring Boot starters. Spring Boot starters are pom.xml files that contain a set of dependency descriptors that you can include in your Spring Boot project. Red Hat offers support and maintenance for Red Hat Process Automation Manager Spring Boot projects as part of Red Hat Runtimes. Red Hat Process Automation Manager Spring Boot business applications are flexible, UI-agnostic logical groupings of individual services that provide certain business capabilities. Business applications are based on Spring Boot starters. They are usually deployed separately and can be versioned individually. A complete business application enables a domain to achieve specific business goals, for example, order management or accommodation management. After you create and configure your business application, you can deploy it to an existing service or to the cloud, through OpenShift. 8.2. Integrating Red Hat Fuse Fuse is a distributed, cloud-native integration platform that is part of an agile integration solution. Its distributed approach enables teams to deploy integrated services where required. You can install Red Hat Fuse on the Apache Karaf container platform or Red Hat JBoss Enterprise Application Platform and then install and configure Red Hat Process Automation Manager in that container. 8.3. Integrating Red Hat Single Sign-On Red Hat Single Sign-On (RH-SSO) is a single sign-on solution that you can use to secure your browser applications with your REST web services and Git access. When you integrate Red Hat Process Automation Manager with RH-SSO, you create an SSO and identity management (IDM) environment for Red Hat Process Automation Manager. The session management feature of RH-SSO enables you to use a single authentication for different Red Hat Process Automation Manager environments on the internet. Red Hat Process Automation Manager supports RH-SSO 7.5 on Red Hat JBoss EAP 7.4.

Commands:
5.236. perl-IPC-Run 5.236.1. RHBA-2012:1336 - perl-IPC-Run bug fix update Updated perl-IPC-Run packages that fix one bug are now available for Red Hat Enterprise Linux 6. The perl-IPC-Run packages provide a mechanism for Perl scripts to interact with child processes. Bug Fix BZ# 856840 Prior to this update, the IO::Pty Perl module was not loaded when using the command "IPC::Run::harness" with the ">pty>" argument if the perl-IO-Tty package was not installed. As a consequence, the Perl code failed. This update adds a perl-IO-Tty dependency to the perl-IPC-Run packages. All users of perl-IPC-Run are advised to upgrade to these updated packages, which fix this bug.

Commands:
function::user_string2 Name function::user_string2 - Retrieves string from user space with alternative error string. Synopsis Arguments addr The user space address to retrieve the string from. err_msg The error message to return when data isn't available. General Syntax user_string2:string(addr:long, err_msg:string) Description Returns the null terminated C string from a given user space memory address. Reports the given error message on the rare cases when userspace data is not accessible.

Commands:
function user_string2:string(addr:long,err_msg:string)
Chapter 62. Deploying custom tasks Work item handlers, as custom code, are created outside of Red Hat Process Automation Manager. To use the code in your custom task, the code must be deployed to the server. Work item handler projects must be Java JAR files that can be placed into a Maven repository. In Red Hat Process Automation Manager you can deploy custom tasks using two methods: Within a Business Central custom task repository. For more information, see Managing and monitoring business processes in Business Central . Outside of Business Central, you can manually copy the JAR files into the Maven repository. 62.1. Using a Business Central custom task repository You can enable, disable, and deploy custom tasks within a Business Central custom task repository. For more information, see Managing custom tasks in Business Central . 62.2. Uploading JAR Artifact to Business Central You can upload the work item handler JAR to the Business Central Maven repository using Business Central admin settings. Procedure In Business Central, select the Admin icon in the top-right corner of the screen and select Artifacts . Click Upload . In the Artifact Upload window, click the Choose File icon. Navigate to the location of the work item handler JAR, select the file and click Open . In the pop-up dialog, click the Upload icon. The artifact is uploaded and can now be viewed on the Artifacts page and referenced. 62.3. Manually copying work item definitions to Business Central Maven repository Business Central automatically creates or reuses the Maven repository folder. By default the location is based on the location of the user launched Red Hat JBoss EAP. For example, the full default path would be <startup location>/repositories/kie/global . It is possible to replicate a standard Maven repository folder layout of <groupId>/<artifactId>/<versionId>/ in this folder and copy work item handler JAR files to this location. For example: Any artifacts copied in this fashion are available to Red Hat Process Automation Manager without a server restart. Viewing the artifact in the Business Central Artifacts page requires clicking Refresh .

Commands:
<startup location>/repositories/kie/global/com/redhat/myworkitem/1.0.0-SNAPSHOT/myworkitems-1.0.0-SNAPSHOT.jar
12.15. File Translator 12.15.1. File Translator The file translator exposes stored procedures to leverage file system resources exposed by the file resource adapter. It will commonly be used with the TEXTTABLE or XMLTABLE table functions to use CSV or XML formatted data. See Section 2.6.8, "Nested Tables: TEXTTABLE" and Section 2.6.9, "Nested Tables: XMLTABLE" . The file translator is implemented by the org.teiid.translator.file.FileExecutionFactory class and known by the translator type name file . Note The resource adapter for this translator is provided by configuring the file data source in the JBoss EAP instance. See the Red Hat JBoss Data Virtualization Administration and Configuration Guide for more configuration information. 12.15.2. File Translator: Execution Properties Table 12.10. Execution Properties Name Description Default Encoding The encoding that must be used for CLOBs returned by the getTextFiles procedure. The system default encoding ExceptionIfFileNotFound Throw an exception in getFiles or getTextFiles if the specified file/directory does not exist. true (false in releases) 12.15.3. File Translator: Usage Retrieve all files as BLOBs with an optional extension at the given path. If the extension path is specified, then it will filter all of the files in the directory referenced by the base path. If the extension pattern is not specified and the path is a directory, then all files in the directory will be returned. Otherwise the single file referenced will be returned. If the path does not exist, then no results will be returned if ExceptionIfFileNotFound is false, otherwise an exception will be raised. Retrieve all files as CLOB(s) with the an optional extension at the given path. getTextFiles will retrieve the same files as getFiles , only the results will be CLOB values using the encoding execution property as the character set. Save the CLOB, BLOB, or XML value to the given path. The path is a reference to either a new file location or an existing file to overwrite completely. Note Native or direct query execution is not supported on the File Translator.

Commands:
call getFiles('path/*.ext')
call getTextFiles('path/*.ext')
call saveFile('path', value)
10.3. Nodes Unable to Rejoin Cluster after Fence or Reboot If your nodes do not rejoin the cluster after a fence or reboot, check for the following things: Clusters that are passing their traffic through a Cisco Catalyst switch may experience this problem. Ensure that all cluster nodes have the same version of the cluster.conf file. If the cluster.conf file is different on any of the nodes, then nodes may be unable to join the cluster post fence. As of Red Hat Enterprise Linux 6.1, you can use the following command to verify that all of the nodes specified in the host's cluster configuration file have the identical cluster configuration file: For information on the ccs command, see Chapter 6, Configuring Red Hat High Availability Add-On With the ccs Command and Chapter 7, Managing Red Hat High Availability Add-On With ccs . Make sure that you have configured chkconfig on for cluster services in the node that is attempting to join the cluster. Ensure that no firewall rules are blocking the node from communicating with other nodes in the cluster.

Commands:
ccs -h host --checkconf
Chapter 5. Technology Previews This chapter provides a list of all available Technology Preview features in this release. Technology Preview features are currently not supported under Red Hat Gluster Storage subscription services, may not be functionally complete, and are generally not suitable for production environments. However, these features are included for customer convenience and to provide wider exposure to the feature. Customers may find these features useful in a non-production environment. Customers are also free to provide feedback and functionality suggestions for a Technology Preview feature before it becomes fully supported. Errata will be provided for high-severity security issues. During the development of a Technology Preview feature, additional components may become available to the public for testing. Red Hat intends to fully support Technology Preview features in future releases. Note All Technology Preview features in Red Hat Enterprise Linux 6.10 and 7.7 are also considered technology preview features in Red Hat Gluster Storage 3.5. For more information on the technology preview features available in Red Hat Enterprise Linux 6.10, see the Technology Previews chapter of the Red Hat Enterprise Linux 6.10 Technical Notes. For Red Hat Enterprise Linux 7.7, see Technology Previews . 5.1. SMB Multi-Channel Multi-Channel is an SMB version 3 feature that allows the client to bind multiple transport connections into one authenticated SMB session. This allows for increased fault tolerance and throughput for clients running Windows 8 and newer and Windows Server 2012 and newer. See SMB3 Multi-Channel with Samba on Red Hat Gluster Storage (Technology Preview) for more information.

Commands:
21.2.3. Additional Resources For more information about vsftpd configuration, see the following resources. 21.2.3.1. Installed Documentation The /usr/share/doc/vsftpd- version-number / directory - The TUNING file contains basic performance-tuning tips and the SECURITY/ directory contains information about the security model employed by vsftpd . vsftpd -related man pages - There are a number of man pages for the daemon and the configuration files. The following lists some of the more important man pages. Server Applications vsftpd (8) - Describes available command-line options for vsftpd . Configuration Files vsftpd.conf (5) - Contains a detailed list of options available within the configuration file for vsftpd . hosts_access (5) - Describes the format and options available within the TCP wrappers configuration files: hosts.allow and hosts.deny . Interaction with SELinux man ftpd_selinux - Contains a description of the SELinux policy governing ftpd processes as well as an explanation of the way SELinux labels need to be assigned and Booleans set. 21.2.3.2. Online Documentation About vsftpd and FTP in General http://vsftpd.beasts.org/ - The vsftpd project page is a great place to locate the latest documentation and to contact the author of the software. http://slacksite.com/other/ftp.html - This website provides a concise explanation of the differences between active and passive-mode FTP . Red Hat Enterprise Linux Documentation Red Hat Enterprise Linux 6 Security-Enhanced Linux - The Security-Enhanced Linux for Red Hat Enterprise Linux 6 describes the basic principles of SELinux and documents in detail how to configure and use SELinux with various services such as the Apache HTTP Server, Postfix, PostgreSQL, or OpenShift. It explains how to configure SELinux access permissions for system services managed by systemd. Red Hat Enterprise Linux 6 Security Guide - The Security Guide for Red Hat Enterprise Linux 6 assists users and administrators in learning the processes and practices of securing their workstations and servers against local and remote intrusion, exploitation, and malicious activity. It also explains how to secure critical system services. Relevant RFC Documents RFC 0959 - The original Request for Comments ( RFC ) of the FTP protocol from the IETF . RFC 1123 - The small FTP -related section extends and clarifies RFC 0959. RFC 2228 - FTP security extensions. vsftpd implements the small subset needed to support TLS and SSL connections. RFC 2389 - Proposes FEAT and OPTS commands. RFC 2428 - IPv6 support.

Commands:
7.245. system-config-kdump 7.245.1. RHBA-2013:0292 - system-config-kdump bug fix and enhancement update Updated system-config-kdump packages that fix three bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The system-config-kdump packages provide a graphical tool to configure kernel crash dumping via kdump and kexec. Bug Fixes BZ#811104 An attempt to use system-config-kdump on the IBM System z machines caused an error message to appear. As a consequence, users were unable to choose the specific kernel. This bug has been fixed and the user can choose the required kernel in this situation. BZ#829386 On IBM PowerPC computers, the system-config-kdump tool used the first crashkernel parameter instead of the last one and a traceback was returned when crashkernel value was set to "auto". With this update, system-config-kdump uses the last crashkernel parameter and allows this parameter to be set to "auto". As a result, tracebacks are no longer returned in the described scenario. BZ#858280 Because some actions take longer time to finish, and the return timeout value was set too low, the front end did not receive an answer in an appropriate time, and displayed an error message. The return timeout has been set to 5 minutes and system-config-kdump works as expected now. Enhancement BZ#852766 This enhancements adds support for firmware-assisted dump (fadump) for IBM PowerPC computers. The user is now also allowed to choose between kdump and fadump. All users of system-config-kdump are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
6.9. Certificate System Operating System Users and Groups When installing Certificate System, the pkiuser account and the corresponding pkiuser group are automatically created. Certificate System uses this account and group to start services. As part of a post-installation procedure, you will later be instructed to create an operating system user for each Certificate System administrator who should be able to start and stop or directly configure the instance on the operating system. For details, see the Section 7.10, "Post-installation Tasks" .

Commands:
C. Revision History Revision History Revision 1-6.12 Fri Feb 27 2015 Laura Bailey Rebuild for sort order. Revision 1-6.10 Wed Jan 22 2014 Eliska Slobodova Added the missing eCryptfs Technology Preview. Revision 1-6.8 Mon Jun 17 2013 Eliska Slobodova Fixed broken links and links pointing to the old Product Documentation site. Revision 1-6.7 Wed May 20 2012 Martin Prpic Republished Technical Notes to update list of included advisories. For more information, refer to the Important note in the Package Updates appendix of this book. Revision 1-5 Thu May 19 2011 Ryan Lerch Removed Package Manifest data. Provided link to new Package Manifest document Revision 1-5 Tue Nov 16 2010 Ryan Lerch Fixed invalid links Revision 1-0 Wed Nov 10 2010 Ryan Lerch Initial Release of the Technical Notes

Commands: