mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Initial Load Balancer Add-On Configuration After installing Red Hat Enterprise Linux, you must take some basic steps to set up the LVS router and the real servers. This chapter covers these initial steps in detail. Note The LVS router node that becomes the active node once Load Balancer Add-On is started is also referred to as the primary node . When configuring Load Balancer Add-On, use the Piranha Configuration Tool on the primary node. 2.1. Configuring Services on the LVS Router The Red Hat Enterprise Linux installation program installs all of the components needed to set up Load Balancer Add-On, but the appropriate services must be activated before configuring Load Balancer Add-On. For the LVS router, set the appropriate services to start at boot time. There are three primary tools available for setting services to activate at boot time under Red Hat Enterprise Linux : the command line program chkconfig , the ncurses-based program ntsysv , and the graphical Services Configuration Tool . All of these tools require root access. Note To attain root access, open a shell prompt and use the su - command followed by the root password. For example: On the LVS router, there are three services which need to be set to activate at boot time: The piranha-gui service (primary node only) The pulse service The sshd service If you are clustering multi-port services or using firewall marks, you must also enable the iptables service. It is best to set these services to activate in both runlevel 3 and runlevel 5. To accomplish this using chkconfig , type the following command for each service: /sbin/chkconfig --level 35 daemon on In the above command, replace daemon with the name of the service you are activating. To get a list of services on the system as well as what runlevel they are set to activate on, issue the following command: /sbin/chkconfig --list Warning Turning any of the above services on using chkconfig does not actually start the daemon. To do this use the /sbin/service command. See Section 2.3, "Starting the Piranha Configuration Tool Service" for an example of how to use the /sbin/service command.

Commands:
su - Password: root password
Chapter 2. Installing .NET 6.0 To install .NET on RHEL 7 you need to first enable the .NET software repositories and install the scl tool. Prerequisites Installed and registered RHEL 7 with attached subscriptions. For more information, see Registering the System and Attaching Subscriptions . Procedure Enable the .NET software repositories: Replace variant with server , workstation or hpc-node depending on what RHEL system you are running (RHEL 7 Server, RHEL 7 Workstation, or HPC Compute Node, respectively). Verify the list of subscriptions attached to your system: Install the scl tool: Install .NET 6.0 and all of its dependencies: Enable the rh-dotnet60 Software Collection environment: You can now run dotnet commands in this bash shell session. If you log out, use another shell, or open up a new terminal, the dotnet command is no longer enabled. Warning Red Hat does not recommend permanently enabling rh-dotnet60 because it may affect other programs. If you want to enable rh-dotnet permanently, add source scl_source enable rh-dotnet60 to your ~/.bashrc file. Verification steps Verify the installation: The output returns the relevant information about the .NET installation and the environment.

Commands:
sudo subscription-manager repos --enable=rhel-7- variant -dotnet-rpms
sudo subscription-manager list --consumed
sudo yum install scl-utils -y
sudo yum install rh-dotnet60 -y
scl enable rh-dotnet60 bash
dotnet --info
Chapter 2. Fixed Issues 2.1. AMQ JMS CVE-2020-9488 - Improper validation of certificate with host mismatch in Apache Log4j SMTP appender This issue was resolved by updating the client's Log4j dependency. 2.2. AMQ Resource Adapter CVE-2020-14297 , CVE-2020-14307 , CVE-2020-11113 - Vulnerabilities in the example code In earlier releases of the product, AMQ Resource Adapter contained an example program subject to the listed vulnerabilities. In this release, the vulnerabilities are addressed in a new example program.

Commands:
Chapter 13. Validating schemas with the Red Hat build of Apicurio Registry You can use the Red Hat build of Apicurio Registry with Streams for Apache Kafka. Apicurio Registry is a datastore for sharing standard event schemas and API designs across API and event-driven architectures. You can use Apicurio Registry to decouple the structure of your data from your client applications, and to share and manage your data types and API descriptions at runtime using a REST interface. Apicurio Registry stores schemas used to serialize and deserialize messages, which can then be referenced from your client applications to ensure that the messages that they send and receive are compatible with those schemas. Apicurio Registry provides Kafka client serializers/deserializers for Kafka producer and consumer applications. Kafka producer applications use serializers to encode messages that conform to specific event schemas. Kafka consumer applications use deserializers, which validate that the messages have been serialized using the correct schema, based on a specific schema ID. You can enable your applications to use a schema from the registry. This ensures consistent schema usage and helps to prevent data errors at runtime. Additional resources Red Hat build of Apicurio Registry product documentation Red Hat build of Apicurio Registry is built on the Apicurio Registry open source community project available on GitHub: Apicurio/apicurio-registry

Commands:
Chapter 9. Directory Server RFC support Find the list of notable supported LDAP-related RFCs. Note that it is not a complete list of RFCs that Directory Server supports. 9.1. LDAPv3 Features Technical Specification Road Map ( RFC 4510 ) This is a tracking document and does not contain requirements. The Protocol ( RFC 4511 ) Supported with the following exceptions: RFC 4511 Section 4.4.1. Notice of Disconnection : Directory Server terminates the connections in this case. RFC 4511 Section 4.5.1.3. SearchRequest.derefAliases : LDAP aliases are not supported. RFC 4511 Section 4.13. IntermediateResponse Message Directory Information Models ( RFC 4512 ) Supported with the following exceptions: RFC 4512 Section 2.4.2. Structural Object Classes : Directory Server supports entries with multiple structural object classes. RFC 4512 Section 2.6. Alias Entries RFC 4512 Section 4.1.2. Attribute Types : The attribute type COLLECTIVE is not supported. RFC 4512 Section 4.1.4. Matching Rule Uses RFC 4512 Section 4.1.6. DIT Content Rules RFC 4512 Section 4.1.7. DIT Structure Rules and Name Forms RFC 4512 Section 5.1.1. altServer Note that RFC 4512 enables LDAP servers to not support the previously listed exceptions. For further details, see RFC 4512 Section 7.1. Server Guidelines . Authentication Methods and Security Mechanisms ( RFC 4513 ) Supported. String Representation of Distinguished Names ( RFC 4514 ) Supported. String Representation of Search Filters ( RFC 4515 ) Supported. Uniform Resource Locator ( RFC 4516 ) Supported. However, this RFC is mainly focused on LDAP clients. Syntaxes and Matching Rules ( RFC 4517 ) Supported. Exceptions: directoryStringFirstComponentMatch integerFirstComponentMatch objectIdentifierFirstComponentMatch objectIdentifierFirstComponentMatch keywordMatch wordMatch Internationalized String Preparation ( RFC 4518 ) Supported. Schema for User Applications ( RFC 4519 ) Supported. entryUUID Operational Attribute ( RFC 4530 ) Supported. Content Synchronization Operation ( RFC 4533 ) Supported. 9.2. Authentication methods Anonymous SASL Mechanism ( RFC 4505 ) Not supported. Note that RFC 4512 does not require the ANONYMOUS SASL mechanism. However, Directory Server supports LDAP anonymous binds. External SASL Mechanism ( RFC 4422 ) Supported. Plain SASL Mechanism ( RFC 4616 ) Not supported. Note that RFC 4512 does not require the PLAIN SASL mechanism. However, Directory Server supports LDAP anonymous binds. SecurID SASL Mechanism ( RFC 2808 ) Not supported. However if a Cyrus SASL plug-in exists, Directory Server can use it. Kerberos V5 (GSSAPI) SASL Mechanism ( RFC 4752 ) Supported. CRAM-MD5 SASL Mechanism ( RFC 2195 ) Supported. Digest-MD5 SASL Mechanism ( RFC 2831 ) Supported. One-time Password SASL Mechanism ( RFC 2444 ) Not supported. However if a Cyrus SASL plug-in exists, Directory Server can use it. 9.3. X.509 Certificates schema and attributes support LDAP Schema Definitions for X.509 Certificates ( RFC 4523 ) Attribute types and object classes: Supported. Syntaxes: Not supported. Directory Server uses binary and octet syntax. Matching rules: Not supported.

Commands:
3.7. Supported Image Customizations A number of image customizations are supported in blueprints. In order to make use of these options, you need to initially configure them in the blueprint and then use the command push to import the modified blueprint to Image Builder. Note These customizations are not currently supported in the accompanying `cockpit-composer` GUI. Set the image host name User specifications for the resulting system image Only the user name is required, you can leave out any other lines. Replace PASSWORD-HASH with the actual password hash. To generate the hash, use a command such as: Important To generate the hash, you must have the python3 package on your system. Use the following command to install the package: Replace PUBLIC-SSH-KEY with the actual public key. Repeat this block for every user you want to include. Group specifications for the resulting system image Repeat this block for every group you want to include. Set an existing user's ssh key Note This option is only applicable for existing users. To create a user and set an ssh key, use the User specifications for the resulting system image customization. Append a kernel boot parameter option to the defaults Set the image host name Add a group for the resulting system image Only the name is required and GID is optional. Set the timezone and the Network Time Protocol (NTP) servers for the resulting system image If you do not set a timezone, the system uses Universal Time, Coordinated (UTC) as default. Setting NTP servers is optional. Set the locale settings for the resulting system image Setting both language and keyboard options is mandatory. You can add multiple languages. The first language you add will be the primary language and the other languages will be secondary. Set the firewall for the resulting system image You can use the numeric ports, or theirs names from the `/etc/services` file to enable or disable lists. Set which services to enable during the boot time You can control which services to enable during the boot time. Some image types already have services enabled or disabled so that the image works correctly and this setup cannot be overridden.

Commands:
[customizations] hostname = " baseimage "
[[customizations.user]] name = " USER-NAME " description = " USER-DESCRIPTION " password = " PASSWORD-HASH " key = " PUBLIC-SSH-KEY " home = /home" /USER-NAME/ " shell = " /usr/bin/bash " groups = ["users", "wheel"] uid = NUMBER gid = NUMBER
python3 -c 'import crypt,getpass;pw=getpass.getpass();print(crypt.crypt(pw) if (pw==getpass.getpass("Confirm: ")) else exit())'
yum install python3
[[customizations.group]] name = " GROUP-NAME " gid = NUMBER
[[customizations.sshkey]] user = " root " key = " PUBLIC-SSH-KEY "
[[customizations.kernel]] append = " KERNEL-OPTION "
[customizations] hostname = " BASE-IMAGE "
[[customizations.group]] name = " USER-NAME " gid = NUMBER
[customizations.timezone] timezone = " TIMEZONE " ntpservers = NTP-SERVER
[customizations.locale] language = " [LANGUAGE] " keyboard = " KEYBOARD "
[customizations.firewall] port = " [PORTS] "
[customizations.services] enabled = " [SERVICES] " disabled = " [SERVICES] "
Chapter 48. QuotasPluginKafka schema reference Used in: KafkaClusterSpec The type property is a discriminator that distinguishes use of the QuotasPluginKafka type from QuotasPluginStrimzi . It must have the value kafka for the type QuotasPluginKafka . Property Property type Description type string Must be kafka . producerByteRate integer The default client quota on the maximum bytes per-second that each client can publish to each broker before it is throttled. Applied on a per-broker basis. consumerByteRate integer The default client quota on the maximum bytes per-second that each client can fetch from each broker before it is throttled. Applied on a per-broker basis. requestPercentage integer The default client quota limits the maximum CPU utilization of each client as a percentage of the network and I/O threads of each broker. Applied on a per-broker basis. controllerMutationRate number The default client quota on the rate at which mutations are accepted per second for create topic requests, create partition requests, and delete topic requests, defined for each broker. The mutations rate is measured by the number of partitions created or deleted. Applied on a per-broker basis.

Commands:
16.5. Other Commands This section describes tools that are simpler equivalents to using guestfish to view and edit guest virtual machine disk images. virt-cat is similar to the guestfish download command. It downloads and displays a single file to the guest virtual machine. For example: virt-edit is similar to the guestfish edit command. It can be used to interactively edit a single file within a guest virtual machine. For example, you may need to edit the grub.conf file in a Linux-based guest virtual machine that will not boot: virt-edit has another mode where it can be used to make simple non-interactive changes to a single file. For this, the -e option is used. This command, for example, changes the root password in a Linux guest virtual machine to having no password: virt-ls is similar to the guestfish ls , ll and find commands. It is used to list a directory or directories (recursively). For example, the following command would recursively list files and directories under /home in a Linux guest virtual machine:

Commands:
virt-cat RHEL3 /etc/ntp.conf | grep ^server server 127.127.1.0 # local clock
virt-edit LinuxGuest /boot/grub/grub.conf
virt-edit LinuxGuest /etc/passwd -e 's/^root:.*?:/root::/'
virt-ls -R LinuxGuest /home/ | less
8.102. libxml2 8.102.1. RHBA-2013:1737 - libxml2 bug fix update Updated libxml2 packages that fix one bug are now available for Red Hat Enterprise Linux 6. The libxml2 library is a development toolbox providing the implementation of various XML standards. Bug Fix BZ# 863166 Previously, parsing an XML file containing entities loaded via Document Type Definition (DTD) using the XML::LibXML module could lead to a missing entity error as XML::LibXML did not load entities DTD. A patch has been applied to address this problem and XML files are parsed successfully in this scenario. Users of libxml2 are advised to upgrade to these updated packages, which fix this bug. The desktop must be restarted (log out, then log back in) for this update to take effect.

Commands:
Chapter 3. Red Hat build of OpenJDK features The latest Red Hat build of OpenJDK 11 release might include new features. Additionally, the latest release might enhance, deprecate, or remove features that originated from Red Hat build of OpenJDK 11 releases. Note For all the other changes and security fixes, see OpenJDK 11.0.19 Released . Red Hat build of OpenJDK new features and enhancements Review the following release notes to understand new features and feature enhancements that are included with the Red Hat build of OpenJDK 11.0.19 release: SSLv2Hello and SSLv3 protocols removed from default-enabled TLS protocols SSLv2Hello and SSLv3 are versions of the SSL protocol that are disabled by default, because they have not been considered secure for some time. The SSLv2Hello and SSLv3 protocols are superseded by the more secure and modern TLS protocol and users can switch to TLS versions 1.2 or 1.3. With release Red Hat build of OpenJDK 11.0.19, the list of default-enabled protocols no longer includes SSLv2Hello and SSLv3. Therefore, even if you remove SSLv3 from the jdk.tls.disabledAlgorithms security property, the following methods will no longer return SSLv3: SSLServerSocket.getEnabledProtocols() SSLEngine.getEnabledProtocols() SSLParameters.getProtocols() Now, if you want to enable SSLv3, you must use the jdk.tls.client.protocols or jdk.tls.server.protocols system properties on the command line, or call one of the following methods to enable SSLv3 programmatically: SSLSocket.setEnabledProtocols() SSLServerSocket.setEnabledProtocols() SSLEngine.setEnabledProtocols() See JDK-8190492 (JDK Bug System) . Certigna (Dhimyotis) root certificate authority (CA) certificate added In release Red Hat build of OpenJDK 11.0.19, the cacerts truststore includes the Certigna (Dhimyotis) root certificate: Name: Certigna (Dhimyotis) Alias name: certignarootca Distinguished name: CN=Certigna, O=Dhimyotis, C=FR See JDK-8245654 (JDK Bug System) . listRoots method returns all available drives on Windows In releases, the java.io.File.listRoots() method on Windows systems filtered out any disk drives that were not accessible or did not have media loaded. However, this filtering led to observable performance issues. Now, with release Red Hat build of OpenJDK 11.0.19, the listRoots method returns all available disk drives unfiltered. See JDK-8208077 (JDK Bug System) . Enhanced Swing platform support In earlier releases of Red Hat build of OpenJDK, HTML object tags rendered embedded in Swing HTML components. With release Red Hat build of OpenJDK 11.0.19, rendering only occurs if you set the new system property swing.html.object to true. By default, the swing.html.object property is set to false. JDK bug system reference ID: JDK-8296832.

Commands:
Chapter 17. Deleting applications To delete an application via the Admin Portal, you need to follow these steps: Option 1 : Delete an application from the list of all applications for [Your_API_name]. In the Dashboard, click [Your_API_name] . Click the Overview tab. From the left panel on the Overview page, click Applications . Choose Listing . Click on an application. You will see a page containing details of the application. Click Edit . To delete the application, click Delete . You will see a confirmation message. Click Ok to confirm the deletion. Option 2 : Delete an application based on a specific application plan. In the Admin Portal, click Dashboard . Choose API . Under Published Application Plans , choose an application. Click on an application. You will see a page containing details of the application. Click Edit . To delete the application, click Delete . You will see a confirmation message. Click Ok to confirm the deletion. Alternatively, you can also delete an application via 3scale API Docs, with the operation called Application Delete .

Commands:
4.3. Setting Index Scan Limits In large directories, the search results list can get huge. A directory with a million inetorgperson entries would have a million entries that were returned with a filter like (objectclass=inetorgperson) , and an index for the sn attribute would have at least a million entries in it. Loading a long ID list from the database significantly reduces search performance. The configuration parameter, nsslapd-idlistscanlimit , sets a limit on the number of IDs that are read before a key is considered to match the entire primary index (meaning the search is treated as an unindexed search with a different set of resource limits). For large indexes, it is actually more efficient to treat any search which matches the index as an unindexed search. The search operation only has to look in one place to process results (the entire directory) rather than searching through an index that is nearly the size of a directory, plus the directory itself. The default value of the nsslapd-idlistscanlimit attribute is 4000 , which is gives good performance for a common range of database sizes and access patterns. It's usually not necessary to change this value. If the database index is slightly larger than the 4000 entries, but still significantly smaller than the overall directory, then raising the scan limit improves searches which would otherwise hit the default limit of 4000. On the other hand, lowering the limit can significantly speed up searches that would otherwise hit the 4000 entry limit, but where it is not necessary to scan every entry. 4.3.1. Setting an Index Scan Limit Using the Command Line To set an index scan limit using the command line: For example, to set the number of entry IDs that Directory Server searches during a search operation to 8000 : Restart the Directory Server instance: 4.3.2. Setting an Index Scan Limit Using the Web Console To set an index scan limit using the Web Console: Open the Directory Server user interface in the web console. For details, see Logging Into Directory Server Using the Web Console section in the Red Hat Directory Server Administration Guide . Select the instance. On the Database tab, select Global Database Configuration . Update the value in the ID List Scan Limit field. Click Save Configuration . Click the Actions button, and select Restart Instance .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com backend config set --idlistscanlimit=8000
dsctl instance_name restart
Appendix A. Using your subscription AMQ is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. A.1. Accessing your account Procedure Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. A.2. Activating a subscription Procedure Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. A.3. Downloading release files To access .zip, .tar.gz, and other release files, use the customer portal to find the relevant files for download. If you are using RPM packages or the Red Hat Maven repository, this step is not required. Procedure Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ product. The Software Downloads page opens. Click the Download link for your component. A.4. Registering your system for packages To install RPM packages for this product on Red Hat Enterprise Linux, your system must be registered. If you are using downloaded release files, this step is not required. Procedure Go to access.redhat.com . Navigate to Registration Assistant . Select your OS version and continue to the page. Use the listed command in your system terminal to complete the registration. For more information about registering your system, see one of the following resources: Red Hat Enterprise Linux 6 - Registering the system and managing subscriptions Red Hat Enterprise Linux 7 - Registering the system and managing subscriptions Red Hat Enterprise Linux 8 - Registering the system and managing subscriptions Revised on 2020-12-03 08:53:12 UTC

Commands:
Chapter 11. Supported integration with Red Hat products AMQ Streams 2.5 supports integration with the following Red Hat products: Red Hat Single Sign-On Provides OAuth 2.0 authentication and OAuth 2.0 authorization. For information on the functionality these products can introduce to your AMQ Streams deployment, refer to the product documentation. 11.1. Red Hat Single Sign-On AMQ Streams supports the use of OAuth 2.0 token-based authorization through Red Hat Single Sign-On Authorization Services , which allows you to manage security policies and permissions centrally. Additional resources Red Hat Single Sign-On Supported Configurations Revised on 2024-09-04 16:24:13 UTC

Commands: