mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 7. Choosing and obtaining a Red Hat Ansible Automation Platform installer Choose the Red Hat Ansible Automation Platform installer you need based on your Red Hat Enterprise Linux environment internet connectivity. Review the scenarios below and determine which Red Hat Ansible Automation Platform installer meets your needs. 7.1. Installing with internet access Choose the Red Hat Ansible Automation Platform installer if your Red Hat Enterprise Linux environment is connected to the internet. Installing with internet access retrieves the latest required repositories, packages, and dependencies. Choose one of the following ways to set up your Ansible Automation Platform installer. Tarball install Navigate to the Red Hat Ansible Automation Platform download page . Click Download Now for the Ansible Automation Platform <latest-version> Setup . Extract the files: USD tar xvzf ansible-automation-platform-setup-<latest-version>.tar.gz RPM install Install the Ansible Automation Platform Installer Package v.2.3 for RHEL 8 for x86_64 USD sudo dnf install --enablerepo=ansible-automation-platform-2.3-for-rhel-8-x86_64-rpms ansible-automation-platform-installer v.2.3 for RHEL 9 for x86-64 USD sudo dnf install --enablerepo=ansible-automation-platform-2.3-for-rhel-9-x86_64-rpms ansible-automation-platform-installer Note dnf install enables the repo as the repo is disabled by default. When you use the RPM installer, the files are placed under the /opt/ansible-automation-platform/installer directory. 7.2. Installing without internet access Use the Red Hat Ansible Automation Platform Bundle installer if you are unable to access the internet, or would prefer not to install separate components and dependencies from online repositories. Access to Red Hat Enterprise Linux repositories is still needed. All other dependencies are included in the tar archive. Procedure Navigate to https://access.redhat.com/downloads/content/480 Click Download Now for the Ansible Automation Platform <latest-version> Setup Bundle . Extract the files: USD tar xvzf ansible-automation-platform-setup-bundle-<latest-version>.tar.gz

Commands:
tar xvzf ansible-automation-platform-setup-<latest-version>.tar.gz
sudo dnf install --enablerepo=ansible-automation-platform-2.3-for-rhel-8-x86_64-rpms ansible-automation-platform-installer
sudo dnf install --enablerepo=ansible-automation-platform-2.3-for-rhel-9-x86_64-rpms ansible-automation-platform-installer
tar xvzf ansible-automation-platform-setup-bundle-<latest-version>.tar.gz
Chapter 5. Managing integrations in the Hybrid Cloud Console From the Integrations page, you can edit integrations, pause or resume data collection, or remove existing integrations from the Hybrid Cloud Console. Prerequisites You are logged in to the Red Hat Hybrid Cloud Console as an Organization Administrator or as a user with Cloud Administrator permissions. You have a cloud or Red Hat integration in the Hybrid Cloud Console. Procedure Go to Settings > Integrations . Find the integration you want to edit under the Cloud or Red Hat tab. Click the options icon (...) to the integration and select one of the following tasks: Pause : Temporarily disable data collection for connected Hybrid Cloud Console services. If the integration is currently paused, click Resume to continue collecting data for connected services. Remove : Permanently delete the integration and all collected data from the Hybrid Cloud Console. Edit : View integration details and make changes to the integration configuration in the Hybrid Cloud Console. You can rename the integration, check its availability, connect additional services, or edit the configuration or remove connected services. Verification Go to the Integrations page and confirm that your desired changes have been made.

Commands:
C.16. RecoveryAdmin org.infinispan.transaction.xa.recovery.RecoveryAdminOperations The RecoveryAdmin component exposes tooling for handling transaction recovery. Table C.26. Operations Name Description Signature forceCommit Forces the commit of an in-doubt transaction. String forceCommit(long p0) forceCommit Forces the commit of an in-doubt transaction String forceCommit(int p0, byte[] p1, byte[] p2) forceRollback Forces the rollback of an in-doubt transaction. String forceRollback(long p0) forceRollback Forces the rollback of an in-doubt transaction String forceRollback(int p0, byte[] p1, byte[] p2) forget Removes recovery info for the given transaction. String forget(long p0) forget Removes recovery info for the given transaction. String forget(int p0, byte[] p1, byte[] p2) showInDoubtTransactions Shows all the prepared transactions for which the originating node crashed. String showInDoubtTransactions() 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
7.2. Impact Printers Impact printers are the oldest printing technologies still in active production. Some of the largest printer vendors continue to manufacture, market, and support impact printers, parts, and supplies. Impact printers are most functional in specialized environments where low-cost printing is essential. The three most common forms of impact printers are dot-matrix , daisy-wheel , and line printers . 7.2.1. Dot-Matrix Printers The technology behind dot-matrix printing is quite simple. The paper is pressed against a drum (a rubber-coated cylinder) and is intermittently pulled forward as printing progresses. The electromagnetically-driven printhead moves across the paper and strikes the printer ribbon situated between the paper and printhead pin. The impact of the printhead against the printer ribbon imprints ink dots on the paper which form human-readable characters. Dot-matrix printers vary in print resolution and overall quality with either 9 or 24-pin printheads. The more pins per inch, the higher the print resolution. Most dot-matrix printers have a maximum resolution of around 240 dpi (dots per inch). While this resolution is not as high as those possible in laser or inkjet printers, there is one distinct advantage to dot-matrix (or any form of impact) printing. Because the printhead must strike the surface of the paper with enough force to transfer ink from a ribbon onto the page, it is ideal for environments that must produce carbon copies through the use of special multi-part documents. These documents have carbon (or other pressure-sensitive material) on the underside and create a mark on the sheet underneath when pressure is applied. Retailers and small businesses often use carbon copies as receipts or bills of sale.

Commands:
Chapter 19. Authentication and Interoperability Use of AD and LDAP sudo providers The Active Directory (AD) provider is a back end used to connect to an AD server. In Red Hat Enterprise Linux 7.2, using the AD sudo provider together with the LDAP provider is supported as a Technology Preview. To enable the AD sudo provider, add the sudo_provider=ad setting in the [domain] section of the sssd.conf file. DNSSEC available as Technology Preview in Identity Management Identity Management servers with integrated DNS now support DNS Security Extensions (DNSSEC), a set of extensions to DNS that enhance security of the DNS protocol. DNS zones hosted on Identity Management servers can be automatically signed using DNSSEC. The cryptographic keys are automatically generated and rotated. Users who decide to secure their DNS zones with DNSSEC are advised to read and follow these documents: DNSSEC Operational Practices, Version 2: http://tools.ietf.org/html/rfc6781#section-2 Secure Domain Name System (DNS) Deployment Guide: http://dx.doi.org/10.6028/NIST.SP.800-81-2 DNSSEC Key Rollover Timing Considerations: http://tools.ietf.org/html/rfc7583 Note that Identity Management servers with integrated DNS use DNSSEC to validate DNS answers obtained from other DNS servers. This might affect the availability of DNS zones that are not configured in accordance with recommended naming practices described in the Red Hat Enterprise Linux Networking Guide: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Configure_Host_Names.html#sec-Recommended_Naming_Practices . Nunc Stans event framework available for Directory Server A new Nunc Stans event framework to handle multiple simultaneous connections has been added as Technology Preview. The framework allows supporting several thousand active connections with no performance degradation. It is disabled by default. Browser for the JSON-RPC API in IdM is available This update implements a browser for the JSON-RPC API in Identity Management. The browser can be used to view the API. Note that this feature is experimental and the API is not yet supported. New packages: ipsilon The ipsilon packages provide the Ipsilon identity provider service for federated single sign-on (SSO). Ipsilon links authentication providers and applications or utilities to allow for SSO. It includes a server and utilities to configure Apache-based service providers. The Ipsilon server and toolkit is designed to configure Apache-based identity Service Providers. The server is a pluggable self-contained mod_wsgi application that provides federated SSO to web applications. Ipsilon is introduced in this release as a Technology Preview. Customers are advised not to consider integration of this service for production environments at this time.

Commands:
Chapter 36. Configuring the environment mode in KIE Server and Business Central You can set KIE Server to run in production mode or in development mode. Development mode provides a flexible deployment policy that enables you to update existing deployment units (KIE containers) while maintaining active process instances for small changes. It also enables you to reset the deployment unit state before updating active process instances for larger changes. Production mode is optimal for production environments, where each deployment creates a new deployment unit. In a development environment, you can click Deploy in Business Central to deploy the built KJAR file to a KIE Server without stopping any running instances (if applicable), or click Redeploy to deploy the built KJAR file and replace all instances. The time you deploy or redeploy the built KJAR, the deployment unit (KIE container) is automatically updated in the same target KIE Server. In a production environment, the Redeploy option in Business Central is disabled and you can click only Deploy to deploy the built KJAR file to a new deployment unit (KIE container) on a KIE Server. Procedure To configure the KIE Server environment mode, set the org.kie.server.mode system property to org.kie.server.mode=development or org.kie.server.mode=production . To configure the deployment behavior for a project in Business Central, go to project Settings General Settings Version and toggle the Development Mode option. Note By default, KIE Server and all new projects in Business Central are in development mode. You cannot deploy a project with Development Mode turned on or with a manually added SNAPSHOT version suffix to a KIE Server that is in production mode.

Commands:
7.255. tog-pegasus 7.255.1. RHBA-2013:0418 - tog-pegasus bug fix and enhancement update Updated tog-pegasus packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. OpenPegasus Web-Based Enterprise Management (WBEM) Services for Linux enables management solutions that deliver increased control of enterprise resources. WBEM is a platform and resource independent of Distributed Management Task Force (DMTF) standard that defines a common information model and communication protocol for monitoring and controlling resources from diverse sources. Note The tog-pegasus package has been upgraded to upstream version 2.12.0, which provides a number of bug fixes and enhancements over the version. (BZ#739118, BZ#825471) Bug Fixes BZ#812892 Previously, non-array properties of CMPI instances were not checked for NULL values in the cimserver daemon (OpenPegasus CIM server). This led to an unexpected termination of cimserver. This update provides an upstream patch for cimserver. Now, cimserver correctly returns instances with non-array properties including those containing NULL values. BZ#869664 Prior to this update, all connections to cimserver were considered local host. Consequently, cimsever could not discern between local and remote connections and between granted and denied access. A patch has been provided to fix this bug. Now, cimserver is again capable of recognizing whether, firstly, connections are local or remote and, secondly, whether the access per user will be granted or denied. Enhancement BZ#716474 The cimserver daemon uses all of well-known ports based on CIM/WBEM technology for network communication. This update provides the user with an option to configure, which interfaces have to be used and to restrict cimserver to listen only on selected network interfaces. Users of tog-pegasus are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
B.36. kdelibs B.36.1. RHSA-2011:0464 - Moderate: kdelibs security update Updated kdelibs packages that fix two security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The kdelibs packages provide libraries for the K Desktop Environment (KDE). CVE-2011-1168 A cross-site scripting (XSS) flaw was found in the way KHTML, the HTML layout engine used by KDE applications such as the Konqueror web browser, displayed certain error pages. A remote attacker could use this flaw to perform a cross-site scripting attack against victims by tricking them into visiting a specially-crafted URL. CVE-2011-1094 A flaw was found in the way kdelibs checked the user specified hostname against the name in the server's SSL certificate. A man-in-the-middle attacker could use this flaw to trick an application using kdelibs into mistakenly accepting a certificate as if it was valid for the host, if that certificate was issued for an IP address to which the user specified hostname was resolved to. Note Note that as part of the fix, this update also introduces stricter handling for wildcards used in servers' SSL certificates. Users should upgrade to these updated packages, which contain backported patches to correct these issues. The desktop must be restarted (log out, then log back in) for this update to take effect.

Commands:
8.264. xz 8.264.1. RHBA-2014:0769 - xz bug fix update Updated xz packages that fix several bugs are now available for Red Hat Enterprise Linux 6. XZ Utils is an integrated collection of user-space file compression utilities based on the Lempel-Ziv-Markov chain algorithm (LZMA), which performs lossless data compression. The algorithm provides a high compression ratio while keeping the decompression time short. Bug Fixes BZ# 850898 Previously, the '-h' option of the xzgrep command was not included. As a consequence, the matching lines in the output were prefixed with the corresponding file names. This update adds the '-h' option, and running the 'xzgrep -h' command now suppresses the file name on output as expected. BZ# 863024 Prior to this update, running the 'xzgrep -l' command did not work correctly because the source code did not handle the '-q' option appropriately. As a consequence, an error message was displayed. A patch has been applied to handle the 'grep -q' command in the source code correctly. As a result, running the 'xzgrep -l' suppresses normal output and prints file names with a matching line as expected. BZ# 988703 The xzfgrep command is supposed to act as an alias for the 'xzgrep -F' command. Previously, this alias behavior was not set correctly, and the patterns were processed as regular expressions and not as fixed strings. As a consequence, running the xzfgrep command produced no output. With this update, xzfgrep command works as an alias of the 'xzgrep -F' command, and running the xzfgrep command returns correct output. BZ# 1108085 Previously, the xzgrep command returned exit status 1 when contents of one or more files did not match the requested pattern. With this update, xzgrep returns exit status 0 if there is at least one match of the pattern, which makes the xzgrep behavior consistent with the default grep command behavior. Users of xz are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 19. Configuring automatic crash dumps by using the kdump RHEL System Role To manage kdump using Ansible, you can use the kdump role, which is one of the RHEL System Roles available in RHEL 7.9. Using the kdump role enables you to specify where to save the contents of the system's memory for later analysis. 19.1. The kdump RHEL System Role The kdump System Role enables you to set basic kernel dump parameters on multiple systems. 19.2. kdump role parameters The parameters used for the kdump RHEL System Roles are: Role Variable Description kdump_path The path to which vmcore is written. If kdump_target is not null, path is relative to that dump target. Otherwise, it must be an absolute path in the root file system. Additional resources The makedumpfile(8) man page. For details about the parameters used in kdump and additional information about the kdump System Role, see the /usr/share/ansible/roles/rhel-system-roles.tlog/README.md file. 19.3. Configuring kdump using RHEL System Roles You can set basic kernel dump parameters on multiple systems using the kdump System Role by running an Ansible playbook. Warning The kdump role replaces the kdump configuration of the managed hosts entirely by replacing the /etc/kdump.conf file. Additionally, if the kdump role is applied, all kdump settings are also replaced, even if they are not specified by the role variables, by replacing the /etc/sysconfig/kdump file. Prerequisites The Ansible Core package is installed on the control machine. You have the rhel-system-roles package installed on the system from which you want to run the playbook. You have an inventory file which lists the systems on which you want to deploy kdump . Procedure Create a new playbook.yml file with the following content: --- - hosts: kdump-test vars: kdump_path: /var/crash roles: - rhel-system-roles.kdump Optional: Verify playbook syntax. Run the playbook on your inventory file: Additional resources For a detailed reference on kdump role variables, see the README.md or README.html files in the /usr/share/doc/rhel-system-roles/kdump directory. See Preparing the control node and managed nodes to use RHEL System Roles Documentation installed with the rhel-system-roles package /usr/share/ansible/roles/rhel-system-roles.kdump/README.html

Commands:
--- - hosts: kdump-test vars: kdump_path: /var/crash roles: - rhel-system-roles.kdump
ansible-playbook --syntax-check playbook.yml
ansible-playbook -i inventory_file /path/to/file/playbook.yml
8.3. Interface Control Scripts The interface control scripts activate and deactivated system interfaces. There are two primary interface control scripts, /sbin/ifdown and /sbin/ifup , that call on control scripts located in the /etc/sysconfig/network-scripts/ directory. The ifup and ifdown interface scripts are symbolic links to scripts in the /sbin/ directory. When either of these scripts are called, they require the value of the interface to be specified, such as: Warning The ifup and ifdown interface scripts are the only scripts that the user should use to bring up and take down network interfaces. The following scripts are described for reference purposes only. Two files used to perform a variety of network initialization tasks during the process of bringing up a network interface are /etc/rc.d/init.d/functions and /etc/sysconfig/network-scripts/network-functions . Refer to Section 8.4, "Network Function Files" for more information. After verifying that an interface has been specified and that the user executing the request is allowed to control the interface, the correct script brings the interface up or down. The following are common interface control scripts found within the /etc/sysconfig/network-scripts/ directory: ifup-aliases - Configures IP aliases from interface configuration files when more than one IP address is associated with an interface. ifup-ippp and ifdown-ippp - Brings ISDN interfaces up and down. ifup-ipsec and ifdown-ipsec - Brings IPsec interfaces up and down. ifup-ipv6 and ifdown-ipv6 - Brings IPv6 interfaces up and down. ifup-ipx - Brings up an IPX interface. ifup-plip - Brings up a PLIP interface. ifup-plusb - Brings up a USB interface for network connections. ifup-post and ifdown-post - Contains commands to be executed after an interface is brought up or down. ifup-ppp and ifdown-ppp - Brings a PPP interface up or down. ifup-routes - Adds static routes for a device as its interface is brought up. ifdown-sit and ifup-sit - Contains function calls related to bringing up and down an IPv6 tunnel within an IPv4 connection. ifup-sl and ifdown-sl - Brings a SLIP interface up or down. ifup-wireless - Brings up a wireless interface. Warning Removing or modifying any scripts in the /etc/sysconfig/network-scripts/ directory can cause interface connections to act irregularly or fail. Only advanced users should modify scripts related to a network interface. The easiest way to manipulate all network scripts simultaneously is to use the /sbin/service command on the network service ( /etc/rc.d/init.d/network ), as illustrated the following command: In this example, <action> can be either start , stop , or restart . To view a list of configured devices and currently active network interfaces, use the following command:

Commands:
ifup eth0
service network <action>
service network status
Preface You can extend Red Hat Ansible Automation Platform to connect to automation services catalog on cloud.redhat.com by using the Ansible Automation Platform setup or setup bundle installer. This is a Day 2 activity and requires setup of a service account that has write permissions on all basic resources and objects in automation controller: organizations, users, projects, job templates and inventories. The Catalog worker requires a set of variables assigned to hosts in your Red Hat Ansible Automation Platform network. Running the Catalog worker will create an application and an application token, install the necessary packages, and start the service. Important Support for automation services catalog is no longer available for Ansible Automation Platform from 2.4.

Commands: