mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Overview AMQ Broker is a high-performance messaging implementation based on ActiveMQ Artemis. It uses an asynchronous journal for fast message persistence, and supports multiple languages, protocols, and platforms. 1.1. Key features AMQ Broker provides the following features: Clustering and high availability options Fast, native-IO persistence Supports local transactions Supports XA transactions when using AMQ Core Protocol JMS and AMQ OpenWire JMS clients Written in Java for broad platform support Multiple management interfaces: AMQ Management Console, Management APIs, and JMX 1.2. Supported standards and protocols AMQ Broker supports the following standards and protocols: Wire protocols: Core Protocol AMQP 1.0 MQTT OpenWire (Used by A-MQ 6 clients) STOMP JMS 2.0 Note The details of distributed transactions (XA) within AMQP are not provided in the 1.0 version of the specification. If your environment requires support for distributed transactions, it is recommended that you use the AMQ Core Protocol JMS. 1.3. Supported configurations Refer to the article " Red Hat AMQ 7 Supported Configurations " on the Red Hat Customer Portal for current information regarding AMQ Broker supported configurations. 1.4. Document conventions This document uses the following conventions for the sudo command, file paths, and replaceable values. The sudo command In this document, sudo is used for any command that requires root privileges. You should always exercise caution when using sudo , as any changes can affect the entire system. For more information about using sudo , see The sudo Command . About the use of file paths in this document In this document, all file paths are valid for Linux, UNIX, and similar operating systems (for example, /home/... ). If you are using Microsoft Windows, you should use the equivalent Microsoft Windows paths (for example, C:\Users\... ). Replaceable values This document sometimes uses replaceable values that you must replace with values specific to your environment. Replaceable values are lowercase, enclosed by angle brackets ( < > ), and are styled using italics and monospace font. Multiple words are separated by underscores ( _ ) . For example, in the following command, replace <install_dir> with your own directory name. USD <install_dir> /bin/artemis create mybroker

Commands:
<install_dir> /bin/artemis create mybroker
Chapter 4. Running the playbook After you define variable settings, you can run the playbook to begin the automated installation process. You can run a playbook by using the ansible-playbook command on the control node or by using the Red Hat Ansible automation controller . The JBoss EAP collection then handles all installation and deployment tasks automatically. Note The following procedure assumes that you have created and updated a custom playbook. Prerequisites You have enabled an automated deployment of JBoss EAP . You are familiar with general Ansible concepts and creating Ansible playbooks. For more information, see the Ansible documentation . Your playbook also includes an appropriate link to the location where you have defined your variables. For example: The preceding example assumes that you have defined variables in a vars.yml file. Replace <path_to_vars_file> with the appropriate path. Your playbook also specifies the eap_install and eap_systemd roles. For example: Note The eap_install role controls the installation of JBoss EAP. The eap_systemd role controls the YAML-based configuration of JBoss EAP subsystems and the setup of JBoss EAP as an eap service that is managed by systemd . Red Hat Enterprise Linux (RHEL) version 8 or 9 is already installed on your target hosts. Procedure Perform either of the following steps: On your Ansible control node, enter the following command: In the preceding command, replace <playbook_name> with the name you have assigned to your playbook. The preceding command assumes that your user account supports passwordless authentication. Note If your user account requires password authentication, you can run the preceding command with the --ask-sudo-pass option and specify the required password when prompted. For example: USD ansible-playbook <playbook_name> .yml --ask-sudo-pass Use the Red Hat Ansible automation controller to run your playbook. For more information about getting started with the automation controller, see the Red Hat Ansible Automation Platform documentation page.

Commands:
--- [...] vars_files: - <path_to_vars_file> /vars.yml [...]
--- [...] roles: - eap_install - eap_systemd [...]
ansible-playbook <playbook_name> .yml
Chapter 10. Providing feedback about the Red Hat Hybrid Cloud Console You can help Red Hat improve the Red Hat Hybrid Cloud Console by providing feedback about your experience. Prerequisites You are logged in to the Hybrid Cloud Console. Procedure Click the Feedback button on the right side of the Hybrid Cloud Console window. Note Not all pages in the Hybrid Cloud Console have the Feedback button. Select the option for the type of feedback that you want to provide: To enter general feedback about your experience with the Red Hat Hybrid Cloud Console, click Share feedback : Enter your feedback and then click Submit feedback . Red Hat product teams review the feedback and might contact you for further information. To stay informed about research opportunities for the Hybrid Cloud Console click Yes, I would like to hear about research opportunities . Your email address is added to the screen. To report a non-urgent issue, click Report a bug : Enter details about the issue and then click Submit feedback . Red Hat product teams review the issue and might contact you for further information. To stay informed about research opportunities for the Hybrid Cloud Console click Yes, I would like to hear about research opportunities . Your email address is added to the screen. If your issue is urgent, click Open a support case . The Customer support page opens: For information about opening a support case, see Section 3.1, "Opening a support case" . To stay informed about research opportunities for the Hybrid Cloud Console click Yes, I would like to hear about research opportunities . Your email address is added to the screen. To participate in feedback sessions, usability tests, and interviews with the Red Hat User Research Team, click Inform the direction of Red Hat . Select click Yes, I would like to hear about research opportunities . Your email address is added to the screen. Click Join mailing list .

Commands:
4.5. Adding Function Support Refer to the section on user defined functions for adding new functions to Red Hat JBoss Data Virtualization. This example will show you how to declare support for the function and modify how the function is passed to the data source. Following is a summary of all coding steps in supporting a new scalar function: Override the capabilities method to declare support for the function (REQUIRED) Implement a FunctionModifier to change how a function is translated and register it for use (OPTIONAL) There is a capabilities method getSupportedFunctions() that declares all supported scalar functions. An example of an extended capabilities class to add support for the "abs" absolute value function: package my.connector; import java.util.ArrayList; import java.util.List; public class ExtendedJDBCExecutionFactory extends JDBCExecutionFactory { @Override public List getSupportedFunctions() { List supportedFunctions = new ArrayList(); supportedFunctions.addAll(super.getSupportedFunctions()); supportedFunctions.add("ABS"); return supportedFunctions; } } In general, it is a good idea to call super.getSupportedFunctions() to ensure that you retain any function support provided by the translator you are extending. This may be all that is needed to support a Red Hat JBoss Data Virtualization function if the JDBC data source supports the same syntax as Red Hat JBoss Data Virtualization. The built-in SQL translation will translate most functions as: "function(arg1, arg2, ...)".

Commands:
package my.connector; import java.util.ArrayList; import java.util.List; public class ExtendedJDBCExecutionFactory extends JDBCExecutionFactory { @Override public List getSupportedFunctions() { List supportedFunctions = new ArrayList(); supportedFunctions.addAll(super.getSupportedFunctions()); supportedFunctions.add("ABS"); return supportedFunctions; } }
4.12. Using Google Cloud Deployment Manager to Deploy Multiple Instances Using the google cloud deployment manager facilitates creation of multiple RGHS instances. Log in and authenticate to Google Cloud by following the steps listed at https://cloud.google.com/sdk/gcloud/#gcloud.auth . Copy the configuration contents in the Section 4.16, "Appendix: Configuration files for Red Hat Gluster Storage Deployment" . Run the following gcloud command:

Commands:
gcloud deployment-manager deployments create rghs --config glusterfs-config.yaml
D.10. Problems View The Problems View displays validation errors, warnings, or information associated with a resource contained in open projects within your workspace. Figure D.21. Problems View By default, the Problems View is included in the Teiid Designer perspective. If the Problems View is not showing in the current perspective, click Window > Show View > Other > General > Problems . There are 5 columns in the view's table which include: Description - A description of the problem preceded by a severity icon (i.e., error , warning , or info ). Resource - The name of the resource. Path - The project name. Location - The object within the resource that has a validation error. type - Type of validation item.

Commands:
A.4. The VDSM Hook Domain XML Object VDSM uses the libvirt domain XML format to define virtual machines. The UUID of the virtual machine may be deduced from the domain XML, but it is also available as the environment variable vmId . When hook scripts are started, the _hook_domxml variable is appended to the environment. This variable contains the path of the libvirt domain XML representation of the relevant virtual machine. Some hooks are an exception to this rule. The following hooks contain the XML representation of the NIC, not the virtual machine: *_nic_hotplug_* *_nic_hotunplug_* *_update_device *_device_create *_device_migrate_* Important The before_migration_destination and before_dehibernation hooks currently receive the domain XML from the source host. The domain XML at the destination will be different.

Commands:
4.310. swig 4.310.1. RHBA-2011:0933 - swig bug fix update An updated swig package that fixes one bug is now available for Red Hat Enterprise Linux 6. Simplified Wrapper and Interface Generator (SWIG) is a software development utility for connecting C, C++ and Objective C programs with a variety of high-level programming languages. SWIG is primarily used with Perl, Python and Tcl/TK, but it has also been extended to Java, Eiffel and Guile. SWIG is normally used to create high-level interpreted programming environments, systems integration, and as a tool for building user interfaces. Bug Fix BZ# 679713 Prior to this update, the swig utility emitted a nonexistent "zend_error_noreturn" function call instead of the "zend_error" call into a generated PHP code. This bug has been fixed in this update, and swig now correctly emits only the "zend_error" call as expected. All users of swig are advised to upgrade to this updated package, which fixes this bug.

Commands:
3.4. Continuous Execution The RequestOptions object may be used to specify a special type of continuous async execution via the continuous or setContinuous methods. In continuous mode the statement will be continuously re-executed. This is intended for consuming real-time or other data streams processed through a SQL plan. A continuous query will only terminate on an error or when the statement is explicitly closed. The SQL for a continuous query is no different than any other statement. Care should be taken to ensure that retrievals from non-continuous sources is appropriately cached for reuse, such as by using materialized views or session scoped temp tables. A continuous query must return a result set, must be executed with a forward-only resultset, and cannot be used in the scope of a transaction. Since resource consumptions is expected to be different in a continuous plan, it does not count against the server max active plan limit. Typically custom sources will be used to provide data streams. When the client wishes to end the continuous query, the Statement.close() or Statement.cancel() method should be called. Typically your callback will close whenever it no long needs to process results. See also the ContinuousStatementCallback for use as the StatementCallback for additional methods related to continuous processing.

Commands:
Chapter 6. Domain Management Identity Service (keystone) domains are additional namespaces you can create in keystone. You would use keystone domains to partition users, groups, and projects. These separate domains can also be configured to authenticate users in different LDAP or Active Directory environments. For more information see Integrate with Identity Service . Note Identity Service includes a built-in domain called Default . It is suggested you reserve this domain only for service accounts, and create a separate domain for user accounts. 6.1. View a List of Domains You can view a list of domains using openstack domain list . For example: Note If this command is not available, check you have enabled keystone v3 for your command line session. 6.2. Create a New Domain You can create a new domain using openstack domain create . For example: 6.3. View the Details of a Domain You can view the details of a domain using openstack domain show . For example: 6.4. Disable a Domain You can disable a domain using --disable . For example: Confirm the domain has been disabled: You can then re-enable the domain, if required:

Commands:
openstack domain list +----------------------------------+------------------+---------+--------------------+ | ID | Name | Enabled | Description | +----------------------------------+------------------+---------+--------------------+ | 3abefa6f32c14db9a9703bf5ce6863e1 | TestDomain | True | | | 69436408fdcb44ab9e111691f8e9216d | corp | True | | | a4f61a8feb8d4253b260054c6aa41adb | federated_domain | True | | | default | Default | True | The default domain | +----------------------------------+------------------+---------+--------------------+
openstack domain create TestDomain +-------------+----------------------------------+ | Field | Value | +-------------+----------------------------------+ | description | | | enabled | True | | id | 3abefa6f32c14db9a9703bf5ce6863e1 | | name | TestDomain | +-------------+----------------------------------+
openstack domain show TestDomain +-------------+----------------------------------+ | Field | Value | +-------------+----------------------------------+ | description | | | enabled | True | | id | 3abefa6f32c14db9a9703bf5ce6863e1 | | name | TestDomain | +-------------+----------------------------------+
openstack domain set TestDomain --disable
openstack domain show TestDomain +-------------+----------------------------------+ | Field | Value | +-------------+----------------------------------+ | description | | | enabled | False | | id | 3abefa6f32c14db9a9703bf5ce6863e1 | | name | TestDomain | +-------------+----------------------------------+
openstack domain set TestDomain --enable
Chapter 5. Web Administration Log Levels In Web Administration, the log messages of different components and services are logged by tendrl-node-agent . It receives all the log messages from other components via a socket and logs the messages using syslog . tendrl-node-agent logs messages for the following Web Administration components: Server-side Web Administration components : tendrl-monitoring-integration tendrl-notifier Storage node-side Web Administration components : tendrl-gluster-integration These are the available log levels for Web Administration: DEBUG INFO WARNING ERROR (Default) CRITICAL Note The log levels are case-sensitive. Input the log levels in uppercase format to avoid any error messages. To change the default log level ( ERROR ), follow these steps: Open the logging configuration yaml file in an editor: Change the log level by modifying all instances of level variables under handlers and root : 1 Enter new log level 2 Enter new log level 3 Enter new log level Restart the tendrl-node-agent service by:

Commands:
/etc/tendrl/node-agent/node-agent_logging.yaml
handlers: console: class: logging.StreamHandler level: ERROR 1 stream: ext://sys.stdout info_file_handler: class: logging.handlers.SysLogHandler facility: local5 address: /dev/log level: ERROR 2 root: level: ERROR 3 handlers: [console, info_file_handler]
service tendrl-node-agent restart
8.4. Installing a Clone Subsystem Using an HSM Normally, clone subsystems are created using a PKCS #12 file containing the system keys of the master subsystem. This file is generated during the installation of the master subsystem by setting the pki_backup_keys to True in the configuration file you use for the installation along with the defined value for the pki_backup_password option, or by exporting the keys using the PKCS12Export tool. You cannot generate a PKCS #12 file using PKCS12Export when using an HSM because the keys cannot be retrieved from the HSM. Instead, the clone subsystem should either be pointed to the HSM used by the master subsystem, so that it can access the same keys. Alternatively, if using a separate HSM, clone the keys to this HSM using the utilities provided by the HSM vendor. You must provide access to the master subsystem's key before running the pkispawn utility. As Certificate System uses no PKCS #12 when installing with an HSM, you do not need to set the parameters in the configuration file for the location of a PKCS #12 file and its password. The following examples provide configuration parameters required for generating a CA clone and list options from the [CA] section of the respective PKI configuration file: For generating a non-HSM CA clone: For generating a CA clone using an HSM: Note In order for the master subsystem to share the same certificates and keys with its clones, the HSM must be on a network that is in shared mode and accessible by all subsystems.

Commands:
[CA] pki_clone=True pki_clone_pkcs12_password=Secret123 pki_clone_pkcs12_path=<path_to_pkcs12_file> pki_clone_replicate_schema=True pki_clone_uri=https:// <master_ca_host_name>:<master_ca_https_port>
[CA] pki_clone=True pki_clone_replicate_schema=True pki_clone_uri=https:// <master_ca_host_name>:<master_ca_https_port>
Chapter 21. Kernel Kernel Media support The following features are presented as Technology Previews: The latest upstream video4linux Digital video broadcasting Primarily infrared remote control device support Various webcam support fixes and improvements Package: kernel-2.6.32-642 Linux (NameSpace) Container [LXC] Linux containers provide a flexible approach to application runtime containment on bare-metal systems without the need to fully virtualize the workload. Red Hat Enterprise Linux 6 provides application level containers to separate and control the application resource usage policies through cgroups and namespaces. This release includes basic management of container life-cycle by allowing creation, editing and deletion of containers using the libvirt API and the virt-manager GUI. Linux Containers are a Technology Preview. Packages: libvirt-0.10.2-60 , virt-manager-0.9.0-29 Diagnostic pulse for the fence_ipmilan agent, BZ# 655764 A diagnostic pulse can now be issued on the IPMI interface using the fence_ipmilan agent. This new Technology Preview is used to force a kernel dump of a host if the host is configured to do so. Note that this feature is not a substitute for the off operation in a production cluster. Package: fence-agents-4.0.15-12

Commands:
8.3.5. Network Connectivity to the Backup Site A data center is not of much use if it is totally disconnected from the rest of the organization that it serves. Depending on the disaster recovery plan and the nature of the disaster itself, your user community might be located miles away from the backup site. In these cases, good connectivity is vital to restoring production. Another kind of connectivity to keep in mind is that of telephone connectivity. You must ensure that there are sufficient telephone lines available to handle all verbal communication with your users. What might have been a simple shout over a cubicle wall may now entail a long-distance telephone conversation; so plan on more telephone connectivity than might at first appear necessary.

Commands:
Chapter 6. Changing how your system behaves when you close the laptop lid When you close the lid of your laptop, it suspends by default to save battery. You can customize this behavior according to your preferences. WARNING Some laptops can overheat if they are left running with the lid closed, especially in confined spaces. Consider whether changing this setting is safe for your laptop, especially if you intend to keep the laptop running with the lid closed for extended periods of time. Prerequisites Administrative access. Procedure Open the /etc/systemd/logind.conf configuration file. Look for the line that says HandleLidSwitch=suspend . If the line starts with the # symbol, remove it to enable the setting. Replace suspend with one of the following options: poweroff to shut down the computer. lock to lock the screen. ignore to do nothing. For example, to lock the screen upon closing the lid, use this setting: Save your changes and close the editor.

Commands:
HandleLidSwitch=lock
Chapter 11. Supported Configurations Supported configurations for the AMQ Streams 2.5 release. 11.1. Supported platforms The following platforms are tested for AMQ Streams 2.5 running with Kafka on the version of OpenShift stated. Platform Version Architecture OpenShift Container Platform 4.12 and later x86_64, s390x (IBM Z and IBM(R) LinuxONE), aarch64 (64-bit ARM) OpenShift Container Platform 4.13 and later ppc64le (IBM Power) OpenShift Dedicated Latest x86_64 Microsoft Azure Red Hat OpenShift Latest x86_64 Red Hat OpenShift Service on AWS Latest x86_64 Red Hat MicroShift Latest x86_64 Note Support for aarch64 (64-bit ARM) applies to AMQ Streams 2.5 when running Kafka 3.5.x only. Unsupported features Red Hat MicroShift does not support Kafka Connect's build configuration for building container images with connectors. AMQ Streams running on IBM Power ppc64le, IBM Z s390x, or IBM(R) LinuxONE s390x architecture is unsupported on disconnected OpenShift Container Platform environments. Additionally, the IBM Z and IBM(R) LinuxONE s390x architecture does not support AMQ Streams OPA integration. 11.2. Supported Apache Kafka ecosystem In AMQ Streams, only the following components released directly from the Apache Software Foundation are supported: Apache Kafka Broker Apache Kafka Connect Apache MirrorMaker Apache MirrorMaker 2 Apache Kafka Java Producer, Consumer, Management clients, and Kafka Streams Apache ZooKeeper Note Apache ZooKeeper is supported solely as an implementation detail of Apache Kafka and should not be modified for other purposes. Additionally, the cores or vCPU allocated to ZooKeeper nodes are not included in subscription compliance calculations. In other words, ZooKeeper nodes do not count towards a customer's subscription. 11.3. Additional supported features Kafka Bridge Drain Cleaner Cruise Control Distributed Tracing See also, Chapter 13, Supported integration with Red Hat products . 11.4. Storage requirements Kafka requires block storage; file storage options like NFS are not compatible. Additional resources For information on the supported configurations for the AMQ Streams 2.2 LTS release, see the AMQ Streams Supported Configurations article on the customer portal.

Commands: