mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 13. Data Grid Modules for Red Hat JBoss EAP To use Data Grid inside applications deployed to Red Hat JBoss EAP, you should install Data Grid modules that: Let you deploy applications without packaging Data Grid JAR files in your WAR or EAR file. Allow you to use a Data Grid version that is independent to the one bundled with Red Hat JBoss EAP. Important Red Hat JBoss EAP (EAP) applications can directly handle the infinispan subsystem without the need to separately install Data Grid modules. Red Hat provides support for this functionality since EAP version 7.4. However, your deployment requires the EAP modules to use advanced capabilities such as indexing and querying. 13.1. Installing Data Grid Modules Download and install Data Grid modules for Red Hat JBoss EAP. Prerequisites JDK 8 or later. An existing Red Hat JBoss EAP installation. Procedure Log in to the Red Hat customer portal. Download the ZIP archive for the modules from the Data Grid software downloads . Extract the ZIP archive and copy the contents of modules to the modules directory of your Red Hat JBoss EAP installation so that you get the resulting structure: USDEAP_HOME/modules/system/add-ons/rhdg/org/infinispan/rhdg-8.4 13.2. Configuring Applications to Use Data Grid Modules After you install Data Grid modules for Red Hat JBoss EAP, configure your application to use Data Grid functionality. Procedure In your project pom.xml file, mark the required Data Grid dependencies as provided . Configure your artifact archiver to generate the appropriate MANIFEST.MF file. pom.xml <dependencies> <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-core</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-cachestore-jdbc</artifactId> <scope>provided</scope> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <configuration> <archive> <manifestEntries> <Dependencies>org.infinispan:rhdg-8.4 services</Dependencies> </manifestEntries> </archive> </configuration> </plugin> </plugins> </build> Data Grid functionality is packaged as a single module, org.infinispan , that you can add as an entry to your application's manifest as follows: MANIFEST.MF AWS dependencies If you require AWS dependencies, such as S3_PING, add the following module to your application's manifest:

Commands:
<dependencies> <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-core</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-cachestore-jdbc</artifactId> <scope>provided</scope> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <configuration> <archive> <manifestEntries> <Dependencies>org.infinispan:rhdg-8.4 services</Dependencies> </manifestEntries> </archive> </configuration> </plugin> </plugins> </build>
Manifest-Version: 1.0 Dependencies: org.infinispan:rhdg-8.4 services
Manifest-Version: 1.0 Dependencies: com.amazonaws.aws-java-sdk:rhdg-8.4 services
Chapter 3. Test environment The test environment is the platform where you run both the product undergoing certification and the certification tests. It must comply with the following requirements: Requirement Justification Red Hat Enterprise Linux (RHEL) must be installed on a certified platform (hardware, hypervisor, or cloud instance). Ensures that the underlying physical or virtual platform does not introduce issues that might impact testing. The test environment must not make any modifications to RHEL kernel and user packages beyond those identified as acceptable configuration changes in the RHEL documentation. Any non-Red Hat kernel modules are subject to further inspection. Changes to Red Hat components might impact supportability for our customers. RHEL must not contain components with critical or important vulnerabilities. Ensures that the product undergoing certification is compatible with the security updates that customers are expected to install in their environments. SELinux must be enabled and running in enforcing mode. Ensures that the product undergoing certification is compatible with the recommended security settings. Red Hat Insights must be installed and running. Ensures compatibility with the platform's solution for proactive risk management.

Commands:
Chapter 5. Allocating additional resources to OpenShift AI users As a cluster administrator, you can allocate additional resources to a cluster to support compute-intensive data science work. This support includes increasing the number of nodes in the cluster and changing the cluster's allocated machine pool. Prerequisites You have credentials for administering clusters in OpenShift Cluster Manager ( https://console.redhat.com/openshift/ ). For more information about configuring administrative access in OpenShift Cluster Manager, see Configuring access to clusters in OpenShift Cluster Manager . If you intend to increase the size of a machine pool by using accelerators, you have enabled GPU support in OpenShift AI. This includes installing the Node Feature Discovery operator and NVIDIA GPU Operators. For more information, see Installing the Node Feature Discovery operator and Enabling NVIDIA GPUs . You have an AWS or GCP instance with the capacity to create larger container sizes. For compute-intensive operations, your AWS or GCP instance has enough capacity to accommodate the largest container size, XL . Procedure Log in to OpenShift Cluster Manager ( https://console.redhat.com/openshift/ ). Click Clusters . The Clusters page opens. Click the name of the cluster you want to allocate additional resources to. Click Actions Edit node count . Select a Machine pool from the list. Select the number of nodes assigned to the machine pool from the Node count list. Click Apply . Verification The additional resources that you allocated to the cluster appear on the Machine Pools tab.

Commands:
10.7. Cluster-Controlled Services Fails to Migrate If a cluster-controlled service fails to migrate to another node but the service will start on some specific node, check for the following conditions. Ensure that the resources required to run a given service are present on all nodes in the cluster that may be required to run that service. For example, if your clustered service assumes a script file in a specific location or a file system mounted at a specific mount point then you must ensure that those resources are available in the expected places on all nodes in the cluster. Ensure that failover domains, service dependency, and service exclusivity are not configured in such a way that you are unable to migrate services to nodes as you would expect. If the service in question is a virtual machine resource, check the documentation to ensure that all of the correct configuration work has been completed. Increase the resource group manager's logging, as described in Section 10.6, "Cluster Service Will Not Start" , and then read the messages logs to determine what is causing the service start to fail to migrate.

Commands:
Appendix A. Revision History Revision History Revision 3.1-4 Wed Dec 20 2023 Lenka Spackova Fixed broken links and anchors. Revision 3.1-3 Fri Nov 12 2021 Lenka Spackova Updated Section 4.9, "Database Connectors" . Revision 3.1-2 Tue Dec 18 2018 Lenka Spackova Fixed syntax of a command in the PostgreSQL migration chapter. Revision 3.1-1 Thu May 03 2018 Lenka Spackova Release of Red Hat Software Collections 3.1 Release Notes. Revision 3.1-0 Wed Mar 04 2018 Lenka Spackova Release of Red Hat Software Collections 3.1 Beta Release Notes.

Commands:
function::user_string_n2_quoted Name function::user_string_n2_quoted - Retrieves and quotes string from user space Synopsis Arguments addr the user space address to retrieve the string from inlen the maximum length of the string to read (if not null terminated) outlen the maximum length of the output string Description Reads up to inlen characters of a C string from the given user space memory address, and returns up to outlen characters, where any ASCII characters that are not printable are replaced by the corresponding escape sequence in the returned string. Note that the string will be surrounded by double quotes. On the rare cases when userspace data is not accessible at the given address, the address itself is returned as a string, without double quotes.

Commands:
user_string_n2_quoted:string(addr:long,inlen:long,outlen:long)
Appendix B. Revision History Revision History Revision 0.4-33 Wed Mar 08 2017 Jiri Herrmann Prepared the book for the 6.9 GA release Revision 0.4-31 Mon Dec 20 2016 Jiri Herrmann Prepared the book for the 6.9 Beta release Revision 0.4-30 Mon May 10 2016 Jiri Herrmann Prepared the book for the 6.8 GA release Revision 0.4-23 Tue Mar 01 2016 Jiri Herrmann Prepared the book for the 6.8 beta release Revision 0.4-22 Thu Oct 08 2015 Jiri Herrmann Cleaned up the Revision History Revision 0.4-21 Fri Oct 10 2014 Scott Radvan Version for 6.6 GA release.

Commands:
probe::ioscheduler_trace.elv_abort_request Name probe::ioscheduler_trace.elv_abort_request - Fires when a request is aborted. Synopsis Values disk_major Disk major no of request. rq Address of request. name Name of the probe point elevator_name The type of I/O elevator currently enabled. disk_minor Disk minor number of request. rq_flags Request flags.

Commands:
ioscheduler_trace.elv_abort_request
8.176. perl-WWW-Curl 8.176.1. RHBA-2014:0588 - perl-WWW-Curl bug fix update Updated perl-WWW-Curl packages that fix one bug are now available for Red Hat Enterprise Linux 6. The perl-WWW-Curl packages provide a Perl extension interface for libcurl. Bug Fix BZ# 984894 Previously, accessing the value of the CURLINFO_PRIVATE option caused a program to terminate unexpectedly with a segmentation fault. This update fixes this by ensuring that CURLINFO_PRIVATE is an accessible scalar string. As a result, programs can now access CURLINFO_PRIVATE as expected. Users of perl-WWW-Curl are advised to upgrade to these updated packages, which fix this bug.

Commands:
18.2. XML Representation of a Virtual Machine Pool Example 18.1. An XML representation of a virtual machine pool

Commands:
<vmpool href="/ovirt-engine/api/vmpools/2d2d5e26-1b6e-11e1-8cda-001320f76e8e"> id="2d2d5e26-1b6e-11e1-8cda-001320f76e8e" <actions> <link href="/ovirt-engine/api/vmpools/2d2d5e26-1b6e-11e1-8cda-001320f76e8e/allocatevm" rel="allocatevm"/> </actions> <name>VMPool1</name> <description>Virtual Machine Pool 1</description> <size>2</size> <cluster href="/ovirt-engine/api/clusters/99408929-82cf-4dc7-a532-9d998063fa95"/> id="99408929-82cf-4dc7-a532-9d998063fa95" <template href="/ovirt-engine/api/templates/00000000-0000-0000-0000-000000000000"/> id="00000000-0000-0000-0000-000000000000" <prestarted_vms>0</prestarted_vms> <max_user_vms>1</max_user_vms> </vmpool>
4.162. lohit-oriya-fonts 4.162.1. RHEA-2011:1137 - lohit-oriya-fonts enhancement update An updated lohit-oriya-fonts package which adds one enhancement is now available for Red Hat Enterprise Linux 6. The lohit-oriya-fonts package provides a free Oriya TrueType/OpenType font. Enhancement BZ# 691293 Unicode 6.0, the most recent major version of the Unicode standard, introduces the Indian Rupee Sign (U+20B9), the new official Indian currency symbol. With this update, the lohit-oriya-fonts package now includes a glyph for this new character. All users requiring the Indian rupee sign should install this updated package, which adds this enhancement.

Commands:
Chapter 7. Sources The updated Red Hat Ceph Storage source code packages are available at the following location: For Red Hat Enterprise Linux 8: http://ftp.redhat.com/redhat/linux/enterprise/8Base/en/RHCEPH/SRPMS/ For Red Hat Enterprise Linux 9: https://ftp.redhat.com/redhat/linux/enterprise/9Base/en/RHCEPH/SRPMS/

Commands:
Chapter 2. Supported Configurations For information on supported configurations, see Red Hat AMQ Broker 7 Supported Configurations . Minimum Java version At a minimum, AMQ Broker 7.11 requires Java version 11 to run. Openwire support AMQ 7 Broker has provided support for the Openwire protocol since its release in 2017 as a means to migrate client applications to AMQ 7. With the release of AMQ Broker 7.9.0 in 2021, the Openwire protocol was deprecated and customers were encouraged to migrate their existing Openwire client applications to one of the fully supported protocols of AMQ 7 (CORE, AMQP, MQTT, or STOMP). Starting with the AMQ Broker 8.0 release, the Openwire protocol will be removed from AMQ Broker.

Commands:
5.3. Remote Query When executing remote queries the cacheManager must be an instance of RemoteCacheManager , and an example configuration utilizing a RemoteCacheManager is found below for both Java and blueprint.xml: Using only Java Using Blueprint and Java Java RemoteCacheManagerFactory class: Java InfinispanQueryExample class: blueprint.xml: The remote_query_cache is an arbitrary name for a cache that holds the data, and the results of the query will be a list of domain objects stored as a CamelInfinispanOperationResult header. In addition, there are the following requirements: The RemoteCacheManager must be configured to use ProtoStreamMarshaller . The ProtoStreamMarshaller must be registered with the RemoteCacheManager 's serialization context. The .proto descriptors for domain objects must be registered with the remote JBoss Data Grid server. For more details on how to setup a RemoteCacheManager , see the Remote Querying section of the Red Hat JBoss Data Grid Infinispan Query Guide . Report a bug

Commands:
from("direct:start") .setHeader(InfinispanConstants.OPERATION, InfinispanConstants.QUERY) .setHeader(InfinispanConstants.QUERY_BUILDER, new InfinispanQueryBuilder() { public Query build(QueryFactory<Query> queryFactory) { return queryFactory.from(User.class).having("name").like("%abc%") .toBuilder().build(); } }) .to("infinispan://localhost?cacheContainer=#cacheManager&cacheName=remote_query_cache") ;
public class RemoteCacheManagerFactory { ConfigurationBuilder clientBuilder; public RemoteCacheManagerFactory(String hostname, int port) { clientBuilder = new ConfigurationBuilder(); clientBuilder.addServer() .host(hostname).port(port); } public RemoteCacheManager newRemoteCacheManager() { return new RemoteCacheManager(clientBuilder.build()); } }
public class InfinispanQueryExample { public InfinispanQueryBuilder getBuilder() { return new InfinispanQueryBuilder() { public Query build(QueryFactory<Query> queryFactory) { return queryFactory.from(User.class) .having("name") .like("%abc%") .toBuilder().build(); } } } }
<bean id="remoteCacheManagerFactory" class="com.jboss.datagrid.RemoteCacheManagerFactory"> <argument value="localhost"/> <argument value="11222"/> </bean> <bean id="cacheManager" factory-ref="remoteCacheManagerFactory" factory-method="newRemoteCacheManager"> </bean> <bean id="queryBuilder" class="org.example.com.InfinispanQueryExample"/> <camelContext id="route" xmlns="http://camel.apache.org/schema/blueprint"> <route> <from uri="direct:start"/> <setHeader headerName="CamelInfinispanOperation"> <constant>CamelInfinispanOperationQuery</constant> </setHeader> <setHeader headerName="CamelInfinispanQueryBuilder"> <method ref="queryBuilder" method="getBuilder"/> </setHeader> <to uri="infinispan://localhost?cacheContainer=#cacheManager&cacheName=remote_query_cache"/> </route> </camelContext>
Chapter 3. Internal storage services Red Hat OpenShift Data Foundation service is available for consumption internally to the Red Hat OpenShift Container Platform that runs on the following infrastructure: Amazon Web Services (AWS) Bare metal VMware vSphere Microsoft Azure Google Cloud Red Hat OpenStack 13 or higher (installer-provisioned infrastructure) [Technology Preview] IBM Power IBM Z and IBM(R) LinuxONE ROSA with hosted control planes (HCP) Creation of an internal cluster resource results in the internal provisioning of the OpenShift Data Foundation base services, and makes additional storage classes available to the applications.

Commands:
36.3. Downloading the Upgraded Kernel There are several ways to determine if an updated kernel is available for the system. Security Errata - Go to the following location for information on security errata, including kernel upgrades that fix security issues: Via Quarterly Updates - Refer to the following location for details: Via Red Hat Network - Download and install the kernel RPM packages. Red Hat Network can download the latest kernel, upgrade the kernel on the system, create an initial RAM disk image if needed, and configure the boot loader to boot the new kernel. For more information, refer to http://www.redhat.com/docs/manuals/RHNetwork/ . If Red Hat Network was used to download and install the updated kernel, follow the instructions in Section 36.5, "Verifying the Initial RAM Disk Image" and Section 36.6, "Verifying the Boot Loader" , only do not change the kernel to boot by default. Red Hat Network automatically changes the default kernel to the latest version. To install the kernel manually, continue to Section 36.4, "Performing the Upgrade" .

Commands:
http://www.redhat.com/apps/support/errata/
http://www.redhat.com/apps/support/errata/rhlas_errata_policy.html
Chapter 4. Insights for Red Hat Enterprise Linux advisor service executive report You can download a high-level report summarizing the status of your infrastructure and designed for an executive audience. Executive reports are one to two-page PDF files showing the following information: Identified recommendations by severity Recently identified recommendations by category Top three recommendations in your infrastructure based on the greatest total risk and the greatest number of systems exposed 4.1. Downloading an advisor service executive report Use the following procedure to download an executive report from the advisor service. Procedure Navigate to the Operations > Advisor > Recommendations page and log in if necessary. Located in the upper-right corner of the Recommendations page, click the Download executive report link. Select to open or save the file and click OK . If downloaded, check your download location for the PDF file.

Commands:
4.158. lohit-bengali-fonts 4.158.1. RHEA-2011:1141 - lohit-bengali-fonts enhancement update An updated lohit-bengali-fonts package which adds one enhancement is now available for Red Hat Enterprise Linux 6. The lohit-bengali-fonts package provides a free Bengali TrueType/OpenType font. Enhancement BZ# 691285 Unicode 6.0, the most recent major version of the Unicode standard, introduces the Indian Rupee Sign (U+20B9), the new official Indian currency symbol. With this update, the lohit-bengali-fonts package now includes a glyph for this new character. All users requiring the Indian rupee sign should install this updated package, which adds this enhancement.

Commands:
4.248. python-qpid 4.248.1. RHBA-2011:1666 - python-qpid bug fix update An updated python-qpid package is now available for Red Hat Enterprise Linux 6. The python-qpid package provides a python client library for the Apache Qpid implementation of the Advanced Message Queuing Protocol (AMQP). The python-qpid package has been upgraded to upstream version 0.12. (BZ# 706993 ) Users of python-qpid are advised to upgrade to this updated package.

Commands:
Chapter 13. Removing the trust using the IdM Web UI You can remove the Identity Management (IdM)/Active Directory (AD) trust using the IdM Web UI. Prerequisites You have obtained a Kerberos ticket. For details, see Logging in to IdM in the Web UI: Using a Kerberos ticket . Procedure Log in to the IdM Web UI with administrator privileges. For details, see Accessing the IdM Web UI in a web browser . In the IdM Web UI, click the IPA Server tab. In the IPA Server tab, click the Trusts tab. Select the trust you want to remove. Click the Delete button. In the Remove trusts dialog box, click Delete . Remove the trust object from your Active Directory configuration. Note Removing the trust configuration does not automatically remove the ID range IdM has created for AD users. This way, if you add the trust again, the existing ID range is re-used. Also, if AD users have created files on an IdM client, their POSIX IDs are preserved in the file metadata. To remove all information related to an AD trust, remove the AD user ID range in the ID Ranges tab after removing the trust configuration and trust object. Verification If the trust has been successfully deleted, the Web UI displays a green pop-up with the text:

Commands:
Appendix C. Using AMQ Broker with the examples The AMQ OpenWire JMS examples require a running message broker with a queue named exampleQueue . Use the procedures below to install and start the broker and define the queue. C.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . C.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... C.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named exampleQueue . USD <broker-instance-dir> /bin/artemis queue create --name exampleQueue --address exampleQueue --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. C.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2021-08-24 14:28:08 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name exampleQueue --address exampleQueue --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
Preface Welcome to the Red Hat JBoss Core Services version 2.4.57 Service Pack 4 release. Red Hat JBoss Core Services Apache HTTP Server is an open source web server developed by the Apache Software Foundation . The Apache HTTP Server includes the following features: Implements the current HTTP standards, including HTTP/1.1 and HTTP/2 Supports Transport Layer Security (TLS) encryption through OpenSSL , which provides secure connections between the web server and web clients Supports extensible functionality through the use of modules, some of which are included with the Red Hat JBoss Core Services Apache HTTP Server

Commands: