mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Viewing and editing Rest DSL components Apache Camel supports multiple approaches to defining REST services. In particular, Apache Camel provides the REST DSL (Domain Specific Language), which is a simple but powerful API that can be layered over any REST component and provides integration with the OpenAPI 2.0 specification . OpenAPI (formerly Swagger ) is a vendor-neutral and portable open description format for API services. For information about using the Camel Rest DSL, see the "Defining REST services" chapter of the Apache Camel Development Guide . With the Fuse Tooling, you can view and edit Rest DSL components that are in your Camel Context file. You can also configure your Fuse Integration project to expose your REST API to an OpenAPI client as described here: https://access.redhat.com/articles/4296981 . 3.1. Viewing a graphical representation of Rest DSL components To view the REST DSL components in your Camel Context file in graphical mode: Open the Camel Context file in the route editor. Click the REST tab to the view the Rest DSL components. The REST Configuration section displays these configuration options: Component - The Camel component to use for the REST transport. Context Path - The leading context-path for the REST services. You can use this option for components, such as Servlet, where the web application is deployed using a context-path. Port - The port number that exposes the REST service. Binding Mode - The binding mode for JSON or XML format messages. Possible values are: off (the default), auto , json , xml , or json_xml . Host - The hostname to use for exposing the REST service. Click a REST element to view its associated operations (for example, GET , POST , PUT , and DELETE ) in the REST Operations section. Click a REST element or a REST operation to view its properties in the Properties view. 3.2. Editing Rest DSL components in the graphical view You can add, edit, or delete REST elements in your project's Camel Context file in the REST tab. To add a new REST element: In the REST elements section, click the + button. A REST element is added to the list of REST elements . In the Properties view, edit the REST element properties. To add a REST operation to a REST element: In the list of REST elements , select a REST element. In the REST operations section, click the + button. The Add REST Operation dialog box opens. Specify the ID , URI , and Operation Type . Optionally, select a Referenced Route ID . Click Finish . The new operation shows in the list of REST operations for the selected REST element. To edit a REST element or operation, select it in the REST tab and then edit its property values in the Properties tab. To remove a selected REST element or operation, click the x button. 3.3. Viewing and editing the Rest DSL source code You can also view and edit Rest DSL components in the Source tab: Open the Camel Context file in the route editor. Click the route editor's Source tab and then edit the code. Optionally, click the REST tab to see the changes in the graphical view. To save your changes, select File Save .

Commands:
Chapter 6. Removing systems in a group from the Group details view If you no longer want a system in a group in the Insights Inventory application, you can remove it by using the Group details view. For example, if a system no longer needs to be managed with the other systems in a group, you can remove it. Prerequisites You have a Red Hat Hybrid Cloud Console account. You have registered the systems you plan to group with the Insights Inventory application. Procedure Access Red Hat Hybrid Cloud Console platform and log in. From the console dashboard, navigate to Red Hat Insights > RHEL > Inventory > Groups . In the Groups page: Click the group from which you want to remove systems from the Inventory. The Group page opens, showing the current systems. From the Immutable (OSTree) tab, select the systems that you want to remove. Click the More options (...) icon and choose Remove from group . A window alert asks that you confirm that you want to remove the system from the group. Click Remove . A popup alert informs you that the action was successful. Verification Check that the system is no longer part of the group.

Commands:
18.3. Linux RAID Subsystems RAID in Linux is composed of the following subsystems: Linux Hardware RAID Controller Drivers Hardware RAID controllers have no specific RAID subsystem in Linux. Because they use special RAID chipsets, hardware RAID controllers come with their own drivers; these drivers allow the system to detect the RAID sets as regular disks. mdraid The mdraid subsystem was designed as a software RAID solution for Linux; it is also the preferred solution for software RAID under Linux. This subsystem uses its own metadata format, generally referred to as native mdraid metadata. mdraid also supports other metadata formats, known as external metadata. Red Hat Enterprise Linux 7 uses mdraid with external metadata to access ISW / IMSM (Intel firmware RAID) sets. mdraid sets are configured and controlled through the mdadm utility. dmraid The dmraid tool is used on a wide variety of firmware RAID implementations. dmraid also supports Intel firmware RAID, although Red Hat Enterprise Linux 7 uses mdraid to access Intel firmware RAID sets. Note dmraid has been deprecated since the Red Hat Enterprise Linux 7.5 release. It will be removed in a future major release of Red Hat Enterprise Linux. For more information, see Deprecated Functionality in the Red Hat Enterprise Linux 7.5 Release Notes.

Commands:
24.2.3. Environment Variables Use the Environment tab to configure options for specific variables to set, pass, or unset for CGI scripts. Sometimes it is necessary to modify environment variables for CGI scripts or server-side include (SSI) pages. The Apache HTTP Server can use the mod_env module to configure the environment variables which are passed to CGI scripts and SSI pages. Use the Environment Variables page to configure the directives for this module. Use the Set for CGI Scripts section to set an environment variable that is passed to CGI scripts and SSI pages. For example, to set the environment variable MAXNUM to 50 , click the Add button inside the Set for CGI Script section, as shown in Figure 24.5, "Environment Variables" , and type MAXNUM in the Environment Variable text field and 50 in the Value to set text field. Click OK to add it to the list. The Set for CGI Scripts section configures the SetEnv directive. Use the Pass to CGI Scripts section to pass the value of an environment variable when the server is first started to CGI scripts. To see this environment variable, type the command env at a shell prompt. Click the Add button inside the Pass to CGI Scripts section and enter the name of the environment variable in the resulting dialog box. Click OK to add it to the list. The Pass to CGI Scripts section configures the PassEnv directive. Figure 24.5. Environment Variables To remove an environment variable so that the value is not passed to CGI scripts and SSI pages, use the Unset for CGI Scripts section. Click Add in the Unset for CGI Scripts section, and enter the name of the environment variable to unset. Click OK to add it to the list. This corresponds to the UnsetEnv directive. To edit any of these environment values, select it from the list and click the corresponding Edit button. To delete any entry from the list, select it and click the corresponding Delete button. To learn more about environment variables in the Apache HTTP Server, refer to the following:

Commands:
http://httpd.apache.org/docs-2.0/env.html
Chapter 4. Adding security notices With Red Hat Advanced Cluster Security for Kubernetes, you can add security notices that users see when they log in. You can also set up an organization-wide message or disclaimers on the top or bottom of the RHACS portal. This message can serve as a reminder of corporate policies and notify employees of the appropriate policies. Alternatively, you might want to display these messages for legal reasons, for example, to warn users that their actions are audited. 4.1. Adding a custom login message The display of a warning message before login warns malicious or uninformed users about the consequences of their actions. Prerequisites You must have the Administration role with read permission to view the login message configuration options. You must have the Administration role with write permission to modify, enable or disable the login message. Procedure In the RHACS portal, go to Platform Configuration System Configuration . On the System Configuration view header, click Edit . Enter your login message in the Login Configuration section. To enable the login message, turn on the toggle in the Login Configuration section. Click Save . 4.2. Adding a custom header and footer You can place custom text in a header and footer and configure the text and its background color. Prerequisites You must have the Administration role with read permission to view the custom header and footer configuration options. You must have the Administration role with write permission to modify, enable or disable the custom header and footer. Procedure In the RHACS portal, go to Platform Configuration System Configuration . On the System Configuration view header, click Edit . Under the Header Configuration and Footer Configuration sections, enter the header and footer text. Customize the header and footer Text Color , Size , and Background Color . To enable the header, turn on the toggle in the Header Configuration section. To enable the footer, turn on the toggle in the Footer Configuration section. Click Save .

Commands:
Chapter 40. Importing projects from Git repositories Git is a distributed version control system. It implements revisions as commit objects. When you save your changes to a repository, a new commit object in the Git repository is created. Business Central uses Git to store project data, including assets such as rules and processes. When you create a project in Business Central, it is added to a Git repository that is embedded in Business Central. If you have projects in other Git repositories, you can import those projects into the Business Central Git repository through Business Central spaces. Prerequisites Red Hat Decision Manager projects exist in an external Git repository. You have the credentials required for read access to that external Git repository. Procedure In Business Central, click Menu Design Projects . Select or create the space into which you want to import the projects. The default space is MySpace . To import a project, do one of the following: Click Import Project . Select Import Project from the drop-down list. In the Import Project window, enter the URL and credentials for the Git repository that contains the projects that you want to import and click Import . The projects are added to the Business Central Git repository and are available from the current space.

Commands:
14.9.4. Useful Websites http://www.samba.org/ - Homepage for the Samba distribution and all official documentation created by the Samba development team. Many resources are available in HTML and PDF formats, while others are only available for purchase. Although many of these links are not Red Hat Enterprise Linux specific, some concepts may apply. http://samba.org/samba/archives.html - Active email lists for the Samba community. Enabling digest mode is recommended due to high levels of list activity. Samba newsgroups - Samba threaded newsgroups, such as gmane.org, that use the NNTP protocol are also available. This an alternative to receiving mailing list emails.

Commands:
probe::stap.cache_add_src Name probe::stap.cache_add_src - Adding C code translation to cache Synopsis stap.cache_add_src Values dest_path the path the .c file is going to (incl filename) source_path the path the .c file is coming from (incl filename) Description Fires just before the file is actually moved. Note: if moving the kernel module fails, this probe will not fire.

Commands:
8.3.3. Scanning the System The main functionality of SCAP Workbench is to perform security scans on a selected system in accordance with the given XCCDF or data stream file. To evaluate your system against the selected security policy, follow these steps: Select a security policy by using either the Open SCAP Security Guide window, or Open Other Content in the File menu and search the respective XCCDF, SCAP RPM or data stream file. Warning Selecting a security policy results in the loss of any customization changes that were not saved. To re-apply the lost options, you have to choose the available profile and customization content again. Note that your customizations may not be applicable with the new security policy. To use a pre-arranged a file with customized security content specific to your use case, you can load this file by clicking on the Customization combo box. You can also create a custom tailoring file by altering an available security profile. For more information, see Section 8.3.4, "Customizing Security Profiles" . Select the (no customization) option if you do not want to use any customization for the current system evaluation. This is the default option if no customization was selected. Select the (open customization file...) option to search for the particular tailoring file to be used for the current system evaluation. If you have previously used some customization file, SCAP Workbench remembers this file and adds it to the list. This simplifies repetitive application of the same scan. Select a suitable security profile by clicking the Profile combo box. To modify the selected profile, click the Customize button. For more information about profile customization, see Section 8.3.4, "Customizing Security Profiles" . Select either of two Target radio buttons to scan either a local or a remote machine. If you have selected a remote system, specify it by entering the user name, host name, and the port information as shown in the following example. If you have previously used the remote scan, you can also select a remote system from a list of recently scanned machines. Figure 8.3. Specifying a Remote System You can allow automatic correction of the system configuration by selecting the Remediate check box. With this option enabled, SCAP Workbench attempts to change the system configuration in accordance with the security rules applied by the policy, should the related checks fail during the system scan. Warning If not used carefully, running the system evaluation with the remediation option enabled could render the system non-functional. Click the Scan button to initiate the system scan.

Commands:
7.79. hivex 7.79.1. RHBA-2013:0433 - hivex bug fix update Updated hivex packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Hivex is a library for extracting the contents of Windows Registry "hive" files, which is designed to be secure against corrupted or malicious registry files. Hive files are undocumented binary files. Bug Fixes BZ#822741 Previously, the description of the package contained inappropriate text. This update provides a correction of the language used and now, the spec file contains only neutral expressions. BZ# 841924 Certain hive files that had a very large number of child nodes under a single parent node could not be parsed. A patch has been added to allow read-only access to these child nodes. Users of hivex are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 2. Recovery for zone-aware HA applications with RWX storage Applications that are deployed with topologyKey: topology.kubernetes.io/zone , have one or more replicas scheduled in each data zone, and are using shared storage, that is, ReadWriteMany (RWX) CephFS volume, recovers on the active zone within 30-60 seconds for new connections. The short pause is for HAProxy to refresh connections if a router pod is now offline in the failed data zone. An example of this type of application is detailed in the Install Zone Aware Sample Application section. Important When you install the sample application, power off the OpenShift Container Platform nodes (at least the nodes with OpenShift Data Foundation devices) to test the failure of a data zone in order to validate that your file-uploader application is available, and you can upload new files.

Commands:
Chapter 13. Known issues in Red Hat Decision Manager 7.13.4 This section lists known issues with Red Hat Decision Manager 7.13.4. 13.1. Business Central Business Central EAP7 deployable zip from 7.13.4 cannot be updated by the update tool [ RHPAM-4838 ] Issue: If you use the update tool to update an Red Hat Decision Manager 7.13.4 rhpam-business-central-eap7-deployable installation to release 7.13.4SP1, the update fails with the following error: Workaround: Download the build.metadata file attached to RHPAM-4838 to the business-central.war/META-INF directory in your Business Central installation. Run the update tool again.

Commands:
ERROR - The patch is not valid for the distribution and version!
7.152. papi 7.152.1. RHEA-2015:1313 - papi enhancement update Updated papi packages that add one enhancement are now available for Red Hat Enterprise Linux 6. PAPI (Performance Application Programming Interface) is a software library that provides a specification of cross-platform interfaces to hardware performance counters on modern microprocessors. These counters exist as a small set of registers that count events, which are occurrences of specific signals related to a processor's function. Monitoring these events allows developers to track performance-related events, such as cache misses, instructions retired, and clock cycles, to better understand the performance issues of the software. PAPI uses libpfm to select the performance monitoring events for the various processors. Enhancement BZ# 831752 The support for Intel Core and Intel Xeon v3 family processors, as well as certain Intel Pentium and Intel Celeron family processors, has been added to PAPI. As a result, developers can now use PAPI on machines with the these processors. Note that this feature has been added only to version 5 of PAPI. For the PAPI 4 libraries, included in the packages for compatibility, these processors remain unsupported. Users of papi are advised to upgrade to these updated packages, which add this enhancement.

Commands:
4.5. Growing a File System The gfs_grow command is used to expand a GFS file system after the device where the file system resides has been expanded. Running a gfs_grow command on an existing GFS file system fills all spare space between the current end of the file system and the end of the device with a newly initialized GFS file-system extension. When the fill operation is completed, the resource index for the file system is updated. All nodes in the cluster can then use the extra storage space that has been added. The gfs_grow command must be run on a mounted file system, but only needs to be run on one node in a cluster. All the other nodes sense that the expansion has occurred and automatically start using the new space. To verify that the changes were successful, use the gfs_grow command with the -T (test) and -v (verbose) flags. Running the command with those flags displays the current state of the mounted GFS file system. Usage MountPoint Specifies the GFS file system to which the actions apply. Comments Before running the gfs_grow command: Back up important data on the file system. Display the volume that is used by the file system to be expanded by running a gfs_tool df MountPoint command. Expand the underlying cluster volume with LVM. For information on administering LVM volumes, see the LVM Administrator's Guide After running the gfs_grow command, run a df command to check that the new space is now available in the file system. Examples In this example, the file system on the /gfs1 directory is expanded. In this example, the state of the mounted file system is checked. Complete Usage MountPoint Specifies the directory where the GFS file system is mounted. Device Specifies the device node of the file system. Table 4.3, "GFS-specific Options Available While Expanding A File System" describes the GFS-specific options that can be used while expanding a GFS file system. Table 4.3. GFS-specific Options Available While Expanding A File System Option Description -h Help. Displays a short usage message. -q Quiet. Turns down the verbosity level. -T Test. Do all calculations, but do not write any data to the disk and do not expand the file system. -V Displays command version information. -v Turns up the verbosity of messages.

Commands:
gfs_grow MountPoint
gfs_grow /gfs1
gfs_grow -Tv /gfs1
gfs_grow [ Options ] { MountPoint | Device } [ MountPoint | Device ]
Chapter 4. Overview of tested deployment models Red Hat tests Ansible Automation Platform 2.5 with a defined set of topologies to give you opinionated deployment options. Deploy all components of Ansible Automation Platform so that all features and capabilities are available for use without the need to take further action. Red Hat tests the installation of Ansible Automation Platform 2.5 based on a defined set of infrastructure topologies or reference architectures. Enterprise organizations can use one of the enterprise topologies for production deployments to ensure the highest level of uptime, performance, and continued scalability. Organizations or deployments that are resource constrained can use a growth topology. It is possible to install the Ansible Automation Platform on different infrastructure topologies and with different environment configurations. Red Hat does not fully test topologies outside of published reference architectures. Use a tested topology for all new deployments. 4.1. Installation and deployment models The following table outlines the different ways to install or deploy Ansible Automation Platform: Table 4.1. Ansible Automation Platform installation and deployment models Mode Infrastructure Description Tested topologies RPM Virtual machines and bare metal The RPM installer deploys Ansible Automation Platform on Red Hat Enterprise Linux by using RPMs to install the platform on host machines. Customers manage the product and infrastructure lifecycle. RPM growth topology RPM mixed growth topology RPM enterprise topology RPM mixed enterprise topology Containers Virtual machines and bare metal The containerized installer deploys Ansible Automation Platform on Red Hat Enterprise Linux by using Podman which runs the platform in containers on host machines. Customers manage the product and infrastructure lifecycle. Container growth topology Container enterprise topology Operator Red Hat OpenShift The Operator uses Red Hat OpenShift Operators to deploy Ansible Automation Platform within Red Hat OpenShift. Customers manage the product and infrastructure lifecycle. Operator growth topology Operator enterprise topology

Commands:
Chapter 148. StrimziPodSet schema reference Full list of StrimziPodSet schema properties Important StrimziPodSet is an internal AMQ Streams resource. Information is provided for reference only. Do not create, modify or delete StrimziPodSet resources as this might cause errors. 148.1. StrimziPodSet schema properties Property Description spec The specification of the StrimziPodSet. StrimziPodSetSpec status The status of the StrimziPodSet. StrimziPodSetStatus

Commands: