mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Getting started This chapter guides you through the steps to set up your environment and run a simple messaging program. 3.1. Prerequisites To build the example, Maven must be configured to use the Red Hat repository or a local repository . You must install the examples . You must have a message broker listening for connections on localhost . It must have anonymous access enabled. For more information, see Starting the broker . You must have a queue named exampleQueue . For more information, see Creating a queue . 3.2. Running your first example The example creates a consumer and producer for a queue named exampleQueue . It sends a text message and then receives it back, printing the received message to the console. Procedure Use Maven to build the examples by running the following command in the <install-dir> /examples/features/standard/queue directory. USD mvn clean package dependency:copy-dependencies -DincludeScope=runtime -DskipTests The addition of dependency:copy-dependencies results in the dependencies being copied into the target/dependency directory. Use the java command to run the example. On Linux or UNIX: USD java -cp "target/classes:target/dependency/*" org.apache.activemq.artemis.jms.example.QueueExample On Windows: > java -cp "target\classes;target\dependency\*" org.apache.activemq.artemis.jms.example.QueueExample For example, running it on Linux results in the following output: USD java -cp "target/classes:target/dependency/*" org.apache.activemq.artemis.jms.example.QueueExample Sent message: This is a text message Received message: This is a text message The source code for the example is in the <install-dir> /examples/features/standard/queue/src directory. Additional examples are available in the <install-dir> /examples/features/standard directory.

Commands:
mvn clean package dependency:copy-dependencies -DincludeScope=runtime -DskipTests
java -cp "target/classes:target/dependency/*" org.apache.activemq.artemis.jms.example.QueueExample
> java -cp "target\classes;target\dependency\*" org.apache.activemq.artemis.jms.example.QueueExample
java -cp "target/classes:target/dependency/*" org.apache.activemq.artemis.jms.example.QueueExample Sent message: This is a text message Received message: This is a text message
36.3.2. Blacklisting a Driver As described in Section 36.1.2, "Booting into Rescue Mode" , the rdblacklist kernel option blacklists a driver at boot time. To continue to blacklist the driver on subsequent boots, add the rdblacklist option to the line in /boot/grub/grub.conf that describes your kernel. To blacklist the driver when the root device is mounted, add a blacklist entry in a file under /etc/modprobe.d/ . Boot the system into rescue mode with the command linux rescue rdblacklist= name_of_driver , where name_of_driver is the driver that you need to blacklist. Follow the instructions in Section 36.1.2, "Booting into Rescue Mode" and do not choose to mount the installed system as read only. Open the /mnt/sysimage/boot/grub/grub.conf file with the vi text editor: Identify the default kernel used to boot the system. Each kernel is specified in the grub.conf file with a group of lines that begins title . The default kernel is specified by the default parameter near the start of the file. A value of 0 refers to the kernel described in the first group of lines, a value of 1 refers to the kernel described in the second group, and higher values refer to subsequent kernels in turn. Edit the kernel line of the group to include the option rdblacklist= name_of_driver , where name_of_driver is the driver that you need to blacklist. For example, to blacklist the driver named foobar : Save the file and exit vi . Create a new file under /etc/modprobe.d/ that contains the command blacklist name_of_driver . Give the file a descriptive name that will help you find it in future, and use the filename extension .conf . For example, to continue to blacklist the driver foobar when the root device is mounted, run: Reboot the system. You no longer need to supply rdblacklist manually as a kernel option until you update the default kernel. If you update the default kernel before the problem with the driver has been fixed, you must edit grub.conf again to ensure that the faulty driver is not loaded at boot time.

Commands:
vi /mnt/sysimage/boot/grub/grub.conf
kernel /vmlinuz-2.6.32-71.18-2.el6.i686 ro root=/dev/sda1 rhgb quiet rdblacklist=foobar
echo "blacklist foobar" >> /mnt/sysimage/etc/modprobe.d/blacklist-foobar.conf
6.2.3. Creating the Logical Volume The following command creates the striped logical volume striped_logical_volume from the volume group volgroup01 . This example creates a logical volume that is 2 gigabytes in size, with three stripes and a stripe size of 4 kilobytes.

Commands:
lvcreate -i3 -I4 -L2G -nstriped_logical_volume volgroup01 Rounding size (512 extents) up to stripe boundary size (513 extents) Logical volume "striped_logical_volume" created
Part IV. Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss Web Server Red Hat Decision Manager is a subset of Red Hat Process Automation Manager. Starting with this release, the distribution files for Red Hat Decision Manager are replaced with Red Hat Process Automation Manager files. There are no Decision Manager artifacts. The Red Hat Decision Manager subscription, support entitlements, and fees remain the same. Red Hat Decision Manager subscribers will continue to receive full support for the decision management and optimization capabilities of Red Hat Decision Manager. The business process management (BPM) capabilities of Red Hat Process Automation Manager are exclusive to Red Hat Process Automation Manager subscribers. They are available for use by Red Hat Decision Manager subscribers but with development support services only. Red Hat Decision Manager subscribers can upgrade to a full Red Hat Process Automation Manager subscription at any time to receive full support for BPM features. This document describes how to install Red Hat Process Automation Manager 7.13 on JBoss Web Server. Note Support for Red Hat Decision Manager on Red Hat JBoss Web Server and Apache Tomcat is now in the maintenance phase. Red Hat will continue to support Red Hat Process Automation Manager on these platforms with the following limitations: Red Hat will not release new certifications or software functionality. Red Hat will release only qualified security patches that have a critical impact and mission-critical bug fix patches. In the future, Red Hat might direct customers to migrate to new platforms and product components that are compatible with the Red Hat hybrid cloud strategy. Prerequisites You have reviewed the information in Planning a Red Hat Decision Manager installation . You have installed Red Hat JBoss Web Server 5.5.1. For information about installing Red Hat JBoss Web Server, see the Red Hat JBoss Web Server Installation Guide .

Commands:
Chapter 7. Creating an OAuth application in GitHub The following sections describe how to authorize Red Hat Quay to integrate with GitHub by creating an OAuth application. This allows Red Hat Quay to access GitHub repositories on behalf of a user. OAuth integration with GitHub is primarily used to allow features like automated builds, where Red Hat Quay can be enabled to monitor specific GitHub repositories for changes like commits or pull requests, and trigger contain image builds when those changes are made. 7.1. Create new GitHub application Use the following procedure to create an OAuth application in Github. Procedure Log into GitHub Enterprise . In the navigation pane, select your username Your organizations . In the navigation pane, select Applications Developer Settings . In the navigation pane, click OAuth Apps New OAuth App . You are navigated to the following page: Enter a name for the application in the Application name textbox. In the Homepage URL textbox, enter your Red Hat Quay URL. Note If you are using public GitHub, the Homepage URL entered must be accessible by your users. It can still be an internal URL. In the Authorization callback URL , enter https://<RED_HAT_QUAY_URL>/oauth2/github/callback . Click Register application to save your settings. When the new application's summary is shown, record the Client ID and the Client Secret shown for the new application.

Commands:
4.2. RHEA-2012:0797 - new packages: crash-gcore-command New crash-gcore-command packages are now available for Red Hat Enterprise Linux 6. The crash-gcore-command extension module is used to dynamically add a gcore command to a running crash utility session on a kernel dumpfile. The command will create a core dump file for a specified user task program that was running when a kernel crashed. The resultant core dump file may then be used with gdb. This enhancement update adds the crash-gcore-command packages to Red Hat Enterprise Linux 6. (BZ# 692799 ) All users who require the crash-gcore-command should install these new packages.

Commands:
Chapter 8. Removing Windows nodes You can remove a Windows node by deleting its host Windows machine. 8.1. Deleting a specific machine You can delete a specific machine. Note You cannot delete a control plane machine. Prerequisites Install an OpenShift Container Platform cluster. Install the OpenShift CLI ( oc ). Log in to oc as a user with cluster-admin permission. Procedure View the machines that are in the cluster and identify the one to delete: USD oc get machine -n openshift-machine-api The command output contains a list of machines in the <clusterid>-worker-<cloud_region> format. Delete the machine: USD oc delete machine <machine> -n openshift-machine-api Important By default, the machine controller tries to drain the node that is backed by the machine until it succeeds. In some situations, such as with a misconfigured pod disruption budget, the drain operation might not be able to succeed in preventing the machine from being deleted. You can skip draining the node by annotating "machine.openshift.io/exclude-node-draining" in a specific machine. If the machine being deleted belongs to a machine set, a new machine is immediately created to satisfy the specified number of replicas.

Commands:
oc get machine -n openshift-machine-api
oc delete machine <machine> -n openshift-machine-api
Chapter 72. Running a test scenario locally In Red Hat Process Automation Manager, you can either run the test scenarios directly in Business Central or locally using the command line. Procedure In Business Central, go to Menu Design Projects and click the project name. On the Project's home page, select the Settings tab. Select git URL and click the Clipboard to copy the git url. Open a command terminal and navigate to the directory where you want to clone the git project. Run the following command: Replace your_git_project_url with relevant data like git://localhost:9418/MySpace/ProjectTestScenarios . Once the project is successfully cloned, navigate to the git project directory and execute the following command: Your project's build information and the test results (such as, the number of tests run and whether the test run was a success or not) are displayed in the command terminal. In case of failures, make the necessary changes in Business Central, pull the changes and run the command again.

Commands:
git clone your_git_project_url
mvn clean test
1.3. Hardware Compatibility Hardware specifications change almost daily, it is recommended that all systems be checked for compatibility. The most recent list of supported hardware can be found in the Red Hat Gluster Storage Server Compatible Physical, Virtual Server and Client OS Platforms List , available online at https://access.redhat.com/knowledge/articles/66206 . You must ensure that your environments meets the hardware compatibility outlined in this article. Hardware specifications change rapidly and full compatibility is not guaranteed. Hardware compatibility is a particularly important concern if you have an older or custom-built system.

Commands:
probe::signal.sys_tkill Name probe::signal.sys_tkill - Sending a kill signal to a thread Synopsis Values name Name of the probe point sig_name A string representation of the signal sig The specific signal sent to the process pid_name The name of the signal recipient sig_pid The PID of the process receiving the kill signal Description The tkill call is analogous to kill(2), except that it also allows a process within a specific thread group to be targeted. Such processes are targeted through their unique thread IDs (TID).

Commands:
signal.sys_tkill
Chapter 1. Installing and configuring CUPS You can use CUPS to print from a local host. You can also use this host to share printers in the network and act as a print server. Procedure Install the cups package: If you configure a CUPS as a print server, edit the /etc/cups/cupsd.conf file, and make the following changes: If you want to remotely configure CUPS or use this host as a print server, configure on which IP addresses and ports the service listens: By default, CUPS listens only on localhost interfaces ( 127.0.0.1 and ::1 ). Specify IPv6 addresses in square brackets. Important Do not configure CUPS to listen on interfaces that allow access from untrustworthy networks, such as the internet. Configure which IP ranges can access the service by allowing the respective IP ranges in the <Location /> directive: In the <Location /admin> directive, configure which IP addresses and ranges can access the CUPS administration services: With these settings, only the hosts with the IP addresses 192.0.2.15 and 2001:db8:1::22 can access the administration services. Optional: Configure IP addresses and ranges that are allowed to access the configuration and log files in the web interface: If you run the firewalld service and want to configure remote access to CUPS, open the CUPS port in firewalld : If you run CUPS on a host with multiple interfaces, consider limiting the access to the required networks. Enable and start the cups service: Verification Use a browser, and access http:// <hostname> :631 . If you can connect to the web interface, CUPS works. Note that certain features, such as the Administration tab, require authentication and an HTTPS connection. By default, CUPS uses a self-signed certificate for HTTPS access and, consequently, the connection is not secure when you authenticate. steps Configuring TLS encryption on a CUPS server Optional: Granting administration permissions to manage a CUPS server in the web interface Adding a printer to CUPS by using the web interface Using and configuring firewalld

Commands:
dnf install cups
Listen 192.0.2.1:631 Listen [2001:db8:1::1]:631
<Location /> Allow from 192.0.2.0/24 Allow from [2001:db8:1::1]/32 Order allow,deny </Location>
<Location /admin> Allow from 192.0.2.15/32 Allow from [2001:db8:1::22]/128 Order allow,deny </Location>
<Location /admin/conf> Allow from 192.0.2.15/32 Allow from [2001:db8:1::22]/128 </Location> <Location /admin/log> Allow from 192.0.2.15/32 Allow from [2001:db8:1::22]/128 </Location>
firewall-cmd --permanent --add-port=631/tcp firewall-cmd --reload
systemctl enable --now cups
Chapter 6. Additional Resources This chapter provides references to other relevant sources of information about Red Hat Software Collections 3.5 and Red Hat Enterprise Linux. 6.1. Red Hat Product Documentation The following documents are directly or indirectly relevant to this book: Red Hat Software Collections 3.5 Packaging Guide - The Packaging Guide for Red Hat Software Collections explains the concept of Software Collections, documents the scl utility, and provides a detailed explanation of how to create a custom Software Collection or extend an existing one. Red Hat Developer Toolset 9.1 Release Notes - The Release Notes for Red Hat Developer Toolset document known problems, possible issues, changes, and other important information about this Software Collection. Red Hat Developer Toolset 9.1 User Guide - The User Guide for Red Hat Developer Toolset contains more information about installing and using this Software Collection. Using Red Hat Software Collections Container Images - This book provides information on how to use container images based on Red Hat Software Collections. The available container images include applications, daemons, databases, as well as the Red Hat Developer Toolset container images. The images can be run on Red Hat Enterprise Linux 7 Server and Red Hat Enterprise Linux Atomic Host. Getting Started with Containers - This guide contains a comprehensive overview of information about building and using container images on Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux Atomic Host. Using and Configuring Red Hat Subscription Manager - The Using and Configuring Red Hat Subscription Manager book provides detailed information on how to register Red Hat Enterprise Linux systems, manage subscriptions, and view notifications for the registered systems. Red Hat Enterprise Linux 6 Deployment Guide - The Deployment Guide for Red Hat Enterprise Linux 6 provides relevant information regarding the deployment, configuration, and administration of this system. Red Hat Enterprise Linux 7 System Administrator's Guide - The System Administrator's Guide for Red Hat Enterprise Linux 7 provides information on deployment, configuration, and administration of this system. 6.2. Red Hat Developers Red Hat Developer Program - The Red Hat Developers community portal. Overview of Red Hat Software Collections on Red Hat Developers - The Red Hat Developers portal provides a number of tutorials to get you started with developing code using different development technologies. This includes the Node.js, Perl, PHP, Python, and Ruby Software Collections. Red Hat Developer Blog - The Red Hat Developer Blog contains up-to-date information, best practices, opinion, product and program announcements as well as pointers to sample code and other resources for those who are designing and developing applications based on Red Hat technologies.

Commands:
Chapter 2. Installation This chapter guides you through the steps to install AMQ Ruby in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To install packages on Red Hat Enterprise Linux, you must register your system . To use AMQ Ruby, you must install Ruby in your environment. 2.2. Installing on Red Hat Enterprise Linux Procedure Use the subscription-manager command to subscribe to the required package repositories. If necessary, replace <variant> with the value for your variant of Red Hat Enterprise Linux (for example, server or workstation ). Red Hat Enterprise Linux 7 USD sudo subscription-manager repos --enable=amq-clients-2-for-rhel-7- <variant> -rpms Red Hat Enterprise Linux 8 USD sudo subscription-manager repos --enable=amq-clients-2-for-rhel-8-x86_64-rpms Use the yum command to install the rubygem-qpid_proton and rubygem-qpid_proton-doc packages. USD sudo yum install rubygem-qpid_proton rubygem-qpid_proton-doc For more information about using packages, see Appendix B, Using Red Hat Enterprise Linux packages .

Commands:
sudo subscription-manager repos --enable=amq-clients-2-for-rhel-7- <variant> -rpms
sudo subscription-manager repos --enable=amq-clients-2-for-rhel-8-x86_64-rpms
sudo yum install rubygem-qpid_proton rubygem-qpid_proton-doc
Chapter 5. Network considerations for NFV The undercloud host requires at least the following networks: Provisioning network - Provides DHCP and PXE-boot functions to help discover bare-metal systems for use in the overcloud. External network - A separate network for remote connectivity to all nodes. The interface connecting to this network requires a routable IP address, either defined statically, or generated dynamically from an external DHCP service. The minimal overcloud network configuration includes the following NIC configurations: Single NIC configuration - One NIC for the provisioning network on the native VLAN and tagged VLANs that use subnets for the different overcloud network types. Dual NIC configuration - One NIC for the provisioning network and the other NIC for the external network. Dual NIC configuration - One NIC for the provisioning network on the native VLAN, and the other NIC for tagged VLANs that use subnets for different overcloud network types. Multiple NIC configuration - Each NIC uses a subnet for a different overcloud network type. For more information on the networking requirements, see Preparing your undercloud networking in the Director Installation and Usage guide.

Commands:
function::ucallers Name function::ucallers - Return first n elements of user stack backtrace Synopsis Arguments n number of levels to descend in the stack (not counting the top level). If n is -1, print the entire stack. Description This function returns a string of the first n hex addresses from the backtrace of the user stack. Output may be truncated as per maximum string length (MAXSTRINGLEN). Note To get (full) backtraces for user space applications and shared shared libraries not mentioned in the current script run stap with -d /path/to/exe-or-so and/or add --ldd to load all needed unwind data.

Commands:
ucallers:string(n:long)
Chapter 4. Securing the Fuse Console To secure the Fuse Console on EAP: Disable the Fuse Console's proxy servlet when deploying to AWS If you want to deploy a standalone Fuse application to Amazon Web Services (AWS), you should disable the Fuse Console's proxy servlet by setting the hawtio.disableProxy system property to true . Note When you disable the Fuse Console proxy servlet, the Fuse Console's Connect tab is disabled and you cannot connect to other JVMs from the Fuse Console. If you want to deploy more than one Fuse application on AWS, you must deploy the Fuse Console for each application. Set HTTPS as the required protocol You can use the hawtio.http.strictTransportSecurity property to require web browsers to use the secure HTTPS protocol to access the Fuse Console. This property specifies that web browsers that try to use HTTP to access the Fuse Console must automatically convert the request to use HTTPS. Use public keys to secure responses You can use the hawtio.http.publicKeyPins property to secure the HTTPS protocol by telling the web browser to associate a specific cryptographic public key with the Fuse Console to decrease the risk of "man-in-the-middle" attacks with forged certificates. Procedure Set the hawtio.http.strictTransportSecurity and the hawtio.http.publicKeyPins properties in the system-properties section of the USDEAP_HOME/standalone/configuration/standalone*.xml file as shown in the following example: (For deploying on AWS only) To disable the Fuse Console's proxy servlet, set the hawtio.disableProxy property in the system-properties section of the USDEAP_HOME/standalone/configuration/standalone*.xml file as shown in the following example: Additional resources For a description of the hawtio.http.strictTransportSecurity property's syntax, see the description page for the HTTP Strict Transport Security (HSTS) response header. For a description of the hawtio.http.publicKeyPins property's syntax, including instructions on how to extract the Base64 encoded public key, see the description page for the HTTP Public Key Pinning response header.

Commands:
<property name="hawtio.http.strictTransportSecurity" value="max-age=31536000; includeSubDomains; preload"/> <property name="hawtio.http.publicKeyPins" value="pin-sha256=cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs"; max-age=5184000; includeSubDomains"/>
<property name="hawtio.disableProxy" value="true"/>