mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 7. Data Roles 7.1. Data Roles Data roles, also called entitlements, are sets of permissions defined per VDB that dictate data access (create, read, update, delete). Data roles use a fine-grained permission system that JBoss Data Virtualization will enforce at runtime and provide audit log entries for access violations. Refer to the Administration and Configuration Guide and Development Guide: Server Development for more information about Logging and Custom Logging. Prior to applying data roles, you should consider restricting source system access through the fundamental design of your VDB. Foremost, JBoss Data Virtualization can only access source entries that are represented in imported metadata. You should narrow imported metadata to only what is necessary for use by your VDB. When using Teiid Designer, you may then go further and modify the imported metadata at a granular level to remove specific columns or indicate tables that are not to be updated, etc. If data role validation is enabled and data roles are defined in a VDB, then access permissions will be enforced by the JBoss Data Virtualization Server. The use of data roles may be disabled system wide using the setting for the teiid subsystem policy-decider-module. Data roles also have built-in system functions (see Section 2.4.18, "Security Functions" ) that can be used for row-based and other authorization checks. The hasRole system function will return true if the current user has the given data role. The hasRole function can be used in procedure or view definitions to allow for a more dynamic application of security - which allows for things such as value masking or row level security. Note See the Security Guide for details on using an alternative authorization scheme. Warning Data roles are only checked if present in a VDB. A VDB deployed without data roles can be used by any authenticated user.

Commands:
2.10. numad numad is an automatic NUMA affinity management daemon. It monitors NUMA topology and resource usage within a system in order to dynamically improve NUMA resource allocation and management (and therefore system performance). Depending on system workload, numad can provide up to 50 percent improvements in performance benchmarks. It also provides a pre-placement advice service that can be queried by various job management systems to provide assistance with the initial binding of CPU and memory resources for their processes. numad monitors available system resources on a per-node basis by periodically accessing information in the /proc file system. It tries to maintain a specified resource usage level, and rebalances resource allocation when necessary by moving processes between NUMA nodes. numad attempts to achieve optimal NUMA performance by localizing and isolating significant processes on a subset of the system's NUMA nodes. numad primarily benefits systems with long-running processes that consume significant amounts of resources, and are contained in a subset of the total system resources. It may also benefit applications that consume multiple NUMA nodes' worth of resources; however, the benefits provided by numad decrease as the consumed percentage of system resources increases. numad is unlikely to improve performance when processes run for only a few minutes, or do not consume many resources. Systems with continuous, unpredictable memory access patterns, such as large in-memory databases, are also unlikely to benefit from using numad. For further information about using numad, see Section 6.3.5, "Automatic NUMA Affinity Management with numad" or Section A.13, "numad" , or refer to the man page:

Commands:
man numad
1.3.6. Committing Changes To share your changes with others and commit them to a CVS repository, change to the directory with its working copy and run the following command: cvs commit [ -m " commit message " ] Note that unless you specify the commit message on the command line, CVS opens an external text editor ( vi by default) for you to write it. For information on how to determine which editor to start, see Section 1.3.1, "Installing and Configuring CVS" . Example 1.22. Committing changes to a CVS repository Imagine that the directory with your working copy of a CVS repository has the following contents: In this working copy, ChangeLog is scheduled for addition to the CVS repository, Makefile already is under revision control and contains local changes, and the TODO file, which is also under revision control, has been scheduled for removal and is no longer present in the working copy. To commit these changes to the CVS repository, type:

Commands:
project]USD ls AUTHORS ChangeLog CVS doc INSTALL LICENSE Makefile README src
project]USD cvs commit -m "Updated the makefile." cvs commit: Examining . cvs commit: Examining doc RCS file: /home/john/cvsroot/project/ChangeLog,v done Checking in ChangeLog; /home/john/cvsroot/project/ChangeLog,v <-- ChangeLog initial revision: 1.1 done Checking in Makefile; /home/john/cvsroot/project/Makefile,v <-- Makefile new revision: 1.2; previous revision: 1.1 done Removing TODO; /home/john/cvsroot/project/TODO,v <-- TODO new revision: delete; previous revision: 1.1.1.1 done
Chapter 4. Supported operating systems and architectures .NET 9.0 is available for OpenShift Container Platform, Red Hat Enterprise Linux 8.10 and later, Red Hat Enterprise Linux 9.5 and later and Red Hat Enterprise Linux 10.0 and later .NET 9.0 is available on the x64_64 (64-bit Intel/AMD), aarch64 (64-bit ARM), ppc64le (64-bit IBM Power), and s390x (64-bit IBM Z) architectures. .NET 9.0 is available for Red Hat Enterprise Linux 8 and later Table 4.1. Supported deployment environments for .NET 9.0 Platform Architecture RPM Repository Red Hat Enterprise Linux 8 AMD64 and Intel 64 ( x86_64 ) IBM Z and LinuxONE ( s390x ) 64-bit ARM ( aarch64 ) IBM Power ( ppc64le ) dotnet-sdk-9.0 Appstream NOTE: The AppStream repositories are enabled by default in Red Hat Enterprise Linux 8. Red Hat Enterprise Linux 9 AMD64 and Intel 64 ( x86_64 ) IBM Z and LinuxONE ( s390x ) 64-bit Arm ( aarch64 ) IBM Power ( ppc64le ) dotnet-sdk-9.0 Appstream Red Hat Enterprise Linux 10 AMD64 and Intel 64 ( x86_64 ) IBM Z and LinuxONE ( s390x ) 64-bit ARM ( aarch64 ) IBM Power ( ppc64le ) dotnet-sdk-9.0 OpenShift Container Platform 4 AMD64 and Intel 64 ( x86_64 ) 64-bit ARM ( aarch64 ) IBM Power ( ppc64le ) IBM Z and LinuxONE ( s390x )

Commands:
Chapter 2. Configure User Access to manage integrations To configure cloud and Red Hat integrations, you must be a member of a group with the Cloud Administrator role. This group must be configured in User Access by an Organization Administrator. In the Red Hat Hybrid Cloud Console, an Organization Administrator performs the following high-level steps: Create a User Access group for cloud administrators. Add the Cloud Administrator role to the group. Add members (users with account access) to the group. Organization Administrator The Organization Administrator configures the User Access group for cloud administrators, then adds the Cloud Administrator role and users to the group. Cloud Administrator The Cloud Administrator configures how services interact with cloud and Red Hat integrations. The Cloud Administrator can add, remove, and edit integrations available in the Hybrid Cloud Console. Additional resources To learn more about User Access on the Hybrid Cloud Console, see the User Access Configuration Guide for Role-based Access Control (RBAC) . 2.1. Creating and configuring a Cloud Administrator group in the Hybrid Cloud Console An Organization Administrator of a Red Hat account creates a group with the Cloud Administrator role and adds members to the group. The members of this group can manage cloud and Red Hat integrations on the Hybrid Cloud Console. Prerequisites You are logged in to the Hybrid Cloud Console as a user who has Organization Administrator permission. If you are not an Organization Administrator, you must be a member of a group that has the User Access administrator role assigned to it. Procedure Click Settings > Identity & Access Management . Under Identity & Access Management , click User Access > Groups . Click Create group . Enter a group name, for example, Cloud Administrators , and a description, and then click . Find Cloud Administrator in the list of roles, select the checkbox to it, and then click . Add members to the group: Search for individual users or filter by username, email, or status. Select the checkbox for the users you want to add to the group, then click . Review the details and click Submit to finish creating the group. Verification Verify that your new group is listed on the Groups page. 2.2. Editing or removing a User Access group You can make changes to an existing User Access group in the Red Hat Hybrid Cloud Console and you can delete groups that are no longer needed. Prerequisites You are logged in to the Red Hat Hybrid Cloud Console and meet one of the following criteria: You are a user with Organization Administrator permissions. You are a member of a group that has the User Access administrator role assigned to it. Procedure Navigate to Red Hat Hybrid Cloud Console > Settings > Identity & Access Management > User Access > Groups . Click the options icon (...) on the far right of the group name row, and then click Edit or Delete . Make and save changes or delete the group.

Commands:
Chapter 4. Installing a cluster on vSphere using the Assisted Installer You can install OpenShift Container Platform on on-premise hardware or on-premise VMs by using the Assisted Installer. Installing OpenShift Container Platform by using the Assisted Installer supports x86_64 , AArch64 , ppc64le , and s390x CPU architectures. The Assisted Installer is a user-friendly installation solution offered on the Red Hat Hybrid Cloud Console. 4.1. Additional resources Installing OpenShift Container Platform with the Assisted Installer

Commands:
18.10. Keyboard Configuration To add multiple keyboard layouts to your system, select Keyboard from the Installation Summary screen. Upon saving, the keyboard layouts are immediately available in the installation program and you can switch between them by using the keyboard icon located at all times in the upper right corner of the screen. Initially, only the language you selected in the welcome screen is listed as the keyboard layout in the left pane. You can either replace the initial layout or add more layouts. However, if your language does not use ASCII characters, you might need to add a keyboard layout that does, to be able to properly set a password for an encrypted disk partition or the root user, among other things. Figure 18.6. Keyboard Configuration To add an additional layout, click the + button, select it from the list, and click Add . To delete a layout, select it and click the - button. Use the arrow buttons to arrange the layouts in order of preference. For a visual preview of the keyboard layout, select it and click the keyboard button. To test a layout, use the mouse to click inside the text box on the right. Type some text to confirm that your selection functions correctly. To test additional layouts, you can click the language selector at the top on the screen to switch them. However, it is recommended to set up a keyboard combination for switching layout. Click the Options button at the right to open the Layout Switching Options dialog and choose a combination from the list by selecting its check box. The combination will then be displayed above the Options button. This combination applies both during the installation and on the installed system, so you must configure a combination here in order to use one after installation. You can also select more than one combination to switch between layouts. Important If you use a layout that cannot accept Latin characters, such as Russian , Red Hat recommends additionally adding the English (United States) layout and configuring a keyboard combination to switch between the two layouts. If you only select a layout without Latin characters, you might be unable to enter a valid root password and user credentials later in the installation process. This can prevent you from completing the installation. Once you have made your selection, click Done to return to the Installation Summary screen. Note To change your keyboard configuration after you have completed the installation, visit the Keyboard section of the Settings dialogue window.

Commands:
7.113. libhbaapi 7.113.1. RHEA-2013:0416 - libhbaapi enhancement update Updated libhbaapi packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The libhbaapi library is the Host Bus Adapter (HBA) API library for Fibre Channel and Storage Area Network (SAN) resources. It contains a unified API that programmers can use to access, query, observe, and modify SAN and Fibre Channel services. Enhancement BZ#862386 This update converts libhbaapi code to a merged upstream repository at Open-FCoE.org. Consequently, the libhbaapi packages are no longer compiled from different sources, thus making maintenance and further development easier. Users of libhbaapi are not required to upgrade to these updated packages as the change introduced by them is purely formal and does not affect functionality.

Commands:
22.4.2. Installing from a Hard Drive The Select Partition screen applies only if you are installing from a disk partition (that is, you selected Hard Drive in the Installation Method dialog). This dialog allows you to name the disk partition and directory from which you are installing Red Hat Enterprise Linux. If you used the repo=hd boot option, you already specified a partition. Figure 22.5. Selecting Partition Dialog for Hard Drive Installation Select the partition containing the ISO files from the list of available partitions. DASD names begin with /dev/dasd . Each individual drive has its own letter, for example /dev/dasda or /dev/sda . Each partition on a drive is numbered, for example /dev/dasda1 or /dev/sda1 . For an FCP LUN, you would have to either boot (IPL) from the same FCP LUN or use the rescue shell provided by the linuxrc menus to manually activate the FCP LUN holding the ISOs as described in Section 25.2.1, "Dynamically Activating an FCP LUN" . Also specify the Directory holding images . Enter the full directory path from the drive that contains the ISO image files. The following table shows some examples of how to enter this information: Table 22.1. Location of ISO images for different partition types File system Mount point Original path to files Directory to use ext2, ext3, ext4 /home /home/user1/RHEL6.9 /user1/RHEL6.9 If the ISO images are in the root (top-level) directory of a partition, enter a / . If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as /home/ , and the images are in /home/new/ , you would enter /new/ . Important An entry without a leading slash may cause the installation to fail. Select OK to continue. Proceed with Chapter 23, Installation Phase 3: Installing Using Anaconda .

Commands:
Chapter 12. Downloading the Red Hat Process Automation Manager installation files You can use the installer JAR file or deployable ZIP files to install Red Hat Process Automation Manager. You can run the installer in interactive or command line interface (CLI) mode. Alternatively, you can extract and configure the Business Central and KIE Server deployable ZIP files. If you want to run Business Central without deploying it to an application server, download the Business Central Standalone JAR file. Download a Red Hat Process Automation Manager distribution that meets your environment and installation requirements. Note Red Hat Decision Manager is a subset of Red Hat Process Automation Manager. You must install Red Hat Process Automation Manager in order to use Red Hat Decision Manager. Procedure Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options: Product: Process Automation Manager Version: 7.13.5 Download one of the following product distributions, depending on your preferred installation method: Note You only need to download one of these distributions. If you want to use the installer to install Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4, download Red Hat Process Automation Manager 7.13.5 Installer ( rhpam-installer-7.13.5.jar ). The installer graphical user interface guides you through the installation process. If you want to install Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 using the deployable ZIP files, download the following files: Red Hat Process Automation Manager 7.13.5 KIE Server for All Supported EE8 Containers ( rhpam-7.13.5-kie-server-ee8.zip ) Red Hat Process Automation Manager 7.13.5 KIE Server Deployable for EAP 7 ( rhpam-7.13.5-business-central-eap7-deployable.zip ) To run Business Central without needing to deploy it to an application server, download Red Hat Process Automation Manager 7.13.5 Business Central Standalone ( rhpam-7.13.5-business-central-standalone.jar ).

Commands:
A. Revision History Revision History Revision 6.6.0-2 Thu Sep 8 2016 Christian Huffman Included list of modified packages between 6.6.0 and 6.6.1 Revision 6.6.0-1 Wed Sep 7 2016 Christian Huffman Updating for 6.6.1. Included component APIs. Revision 6.6.0-0 Tue Jan 5 2016 Christian Huffman Initial draft for 6.6.0.

Commands:
Chapter 4. 4.1.2 Release Notes 4.1. New Features This following major enhancement has been introduced in Red Hat Update Infrastructure 4.1.2. New RHUI Installer argument: --ignore-newer-rhui-packages Previously, when you reran an instance of RHUI Installer which was not up-to-date, RHUI Installer updated the RHUI packages if newer versions were available. As a result, the RHUI system would enter an inconsistent state since the older version of the RHUI Installer package was not aware of potential changes to the RHUI package set. In addition, running RHUI Installer to change a setting, without updating RHUI in the process, was not supported. With this update, when you rerun RHUI Installer, it checks whether a newer version is available. If available, RHUI Installer displays an error message stating that you must either update the RHUI Installer package, or rerun the RHUI Installer command using the --ignore-newer-rhui-packages argument. The --ignore-newer-rhui-packages argument prevents the installer from applying any RHUI updates. 4.2. Known Issues This part describes known issues in Red Hat Update Infrastructure 4.1.2. rhui-installer ignores custom RHUI CA when updating to a newer version of RHUI When updating from RHUI version 4.1.0 or older, rhui-installer ignores the existing custom RHUI CA and generates a new RHUI CA regardless of the parameter value set in the answer.yml file. Consequently, RHUI fails to recognize clients which use the older RHUI CA. To work around this problem, specify the custom RHUI CA when running the rhui-installer --rerun command. For more information, see Updating Red Hat Update Infrastructure .

Commands:
rhui-installer --rerun --user-supplied-rhui-ca-crt <custom_RHUI_CA.crt> --user-supplied-rhui-ca-key <custom_RHUI_CA_key>
Chapter 1. Multi-site deployments Red Hat build of Keycloak supports deployments that consist of multiple Red Hat build of Keycloak instances that connect to each other using its Infinispan caches; load balancers can distribute the load evenly across those instances. Those setups are intended for a transparent network on a single site. The Red Hat build of Keycloak high-availability guide goes one step further to describe setups across multiple sites. While this setup adds additional complexity, that extra amount of high availability may be needed for some environments. The different chapters introduce the necessary concepts and building blocks. For each building block, a blueprint shows how to set a fully functional example. Additional performance tuning and security hardening are still recommended when preparing a production setup.

Commands:
4.9. atlas 4.9.1. RHEA-2011:1582 - atlas enhancement update Updated atlas packages that add various enhancements are now available for Red Hat Enterprise Linux 6. The ATLAS (Automatically Tuned Linear Algebra Software) project is a research effort focusing on applying empirical techniques providing portable performance. The atlas packages provide C and Fortran77 interfaces to a portably efficient BLAS (Basic Linear Algebra Subprograms) implementation and routines from LAPACK (Linear Algebra PACKage). The atlas packages have been upgraded to upstream version 3.8.4, which adds a number of enhancements over the version. The atlas package now contains subpackages optimized for Linux on IBM System z architectures. (BZ# 694459 ) All users of atlas are advised to upgrade to these updated packages, which add these enhancements.

Commands:
18.17. Kdump Use this screen to select whether or not to use Kdump on this system. Kdump is a kernel crash dumping mechanism which, in the event of a system crash, captures information that can be invaluable in determining the cause of the crash. Note that if you enable Kdump , you must reserve a certain amount of system memory for it. As a result, less memory is available for your processes. If you do not want to use Kdump on this system, uncheck Enable kdump . Otherwise, set the amount of memory to reserve for Kdump . You can let the installer reserve a reasonable amount automatically, or you can set any amount manually. When your are satisfied with the settings, click Done to save the configuration and return to the screen. Figure 18.35. Kdump Enablement and Configuration

Commands:
12.6. Setting ethers Information for a Host NIS can host an ethers table which can be used to manage DHCP configuration files for systems based on their platform, operating system, DNS domain, and MAC address - all information stored in host entries in IdM. In Identity Management, each system is created with a corresponding ethers entry in the directory, in the ou=ethers subtree. This entry is used to create a NIS map for the ethers service which can be managed by the NIS compatibility plug-in in IdM. To configure NIS maps for ethers entries: Add the MAC address attribute to a host entry. For example: Open the nsswitch.conf file. Add a line for the ethers service, and set it to use LDAP for its lookup. Check that the ethers information is available for the client.

Commands:
cn=server,ou=ethers,dc=example,dc=com
[jsmith@server ~]USD kinit admin [jsmith@server ~]USD ipa host-mod --macaddress=12:34:56:78:9A:BC server.example.com
ethers: ldap
getent ethers server.example.com