mtpti5iD/redhat-docs_dataset huggingface dataset:
7.22. RHEA-2014:1514 - new packages: xmlsec1, lasso, mod_auth_mellon New xmlsec1, lasso, mod_auth_mellon packages are now available for Red Hat Enterprise Linux 6. The mod_auth_mellon packages provide the mod_auth_mellon module that is an authentication service implementing the Security Assertion Markup Language (SAML) federation protocol version 2.0. It grants access based on the attributes received in assertions generated by an IDP server. The lasso packages provide the Lasso library that implements the Liberty Alliance Single Sign On standards, including the SAML and SAML2 specifications. It allows handling of the whole life-cycle of SAML-based federations, and provides bindings for multiple languages. The xmlsec1 packages provide XML Security Library, a C library based on LibXML2 and OpenSSL. The library was created with a goal to support major XML security standards "XML Digital Signature" and "XML Encryption". This enhancement update adds the xmlsec1, lasso, and mod_auth_mellon packages to Red Hat Enterprise Linux 6 in order to provide SAML Service Provider support in the Apache HTTP server. (BZ# 1083605 , BZ# 1087555 , BZ# 1090812 ) All users who require support for SAML-based federations in the Apache HTTP server are advised to install these new packages.

Commands:
Chapter 7. User Defined Functions 7.1. User Defined Functions You can extend the Red Hat JBoss Data Virtualization function library by creating User Defined Functions (UDFs), as well as User Defined Aggregate Functions (UDAFs). The following are used to define a UDF: Function Name - When you create the function name, keep these requirements in mind: You cannot overload existing Red Hat JBoss Data Virtualization functions. The function name must be unique among user-defined functions in its model for the number of arguments. You can use the same function name for different numbers of types of arguments. Hence, you can overload your user-defined functions. The function name cannot contain the '.' character. The function name cannot exceed 255 characters. Input Parameters - defines a type specific signature list. All arguments are considered required. Return Type - the expected type of the returned scalar value. Pushdown - can be one of REQUIRED, NEVER, ALLOWED. Indicates the expected pushdown behavior. If NEVER or ALLOWED are specified then a Java implementation of the function should be supplied. If REQUIRED is used, then user must extend the Translator for the source and add this function to its pushdown function library. invocationClass/invocationMethod - optional properties indicating the static method to invoke when the UDF is not pushed down. Deterministic - if the method will always return the same result for the same input parameters. Defaults to false. It is important to mark the function as deterministic if it returns the same value for the same inputs as this will lead to better performance. See also the Relational extension boolean metadata property "deterministic" and the DDL OPTION property "determinism". Note If using the pushdown UDF in Teiid Designer, the user must create a source function on the source model, so that the parsing will work correctly. Pushdown scalar functions differ from normal user-defined functions in that no code is provided for evaluation in the engine. An exception will be raised if a pushdown required function cannot be evaluated by the appropriate source.

Commands:
Chapter 9. MySQL The MySQL database is a multi-user, multi-threaded SQL database server that consists of the MySQL server daemon ( mysqld ) and many client programs and libraries. [7] In Red Hat Enterprise Linux, the mysql-server package provides MySQL. Run the rpm -q mysql-server command to see if the mysql-server package is installed. If it is not installed, run the following command as the root user to install it: 9.1. MySQL and SELinux When MySQL is enabled, it runs confined by default. Confined processes run in their own domains, and are separated from other confined processes. If a confined process is compromised by an attacker, depending on SELinux policy configuration, an attacker's access to resources and the possible damage they can do is limited. The following example demonstrates the MySQL processes running in their own domain. This example assumes the mysql package is installed: Run the getenforce command to confirm SELinux is running in enforcing mode: The getenforce command returns Enforcing when SELinux is running in enforcing mode. Run the service mysqld start command as the root user to start mysqld : Run the ps -eZ | grep mysqld command to view the mysqld processes: The SELinux context associated with the mysqld processes is unconfined_u:system_r:mysqld_t:s0 . The second last part of the context, mysqld_t , is the type. A type defines a domain for processes and a type for files. In this case, the mysqld processes are running in the mysqld_t domain. [7] Refer to the MySQL project page for more information.

Commands:
~]# yum install mysql-server
~]USD getenforce Enforcing
~]# service mysqld start Initializing MySQL database: Installing MySQL system tables... [ OK ] Starting MySQL: [ OK ]
~]USD ps -eZ | grep mysqld unconfined_u:system_r:mysqld_safe_t:s0 6035 pts/1 00:00:00 mysqld_safe unconfined_u:system_r:mysqld_t:s0 6123 pts/1 00:00:00 mysqld
Chapter 2. Apache Maven and Red Hat Decision Manager Spring Boot applications Apache Maven is a distributed build automation tool used in Java application development to create, manage, and build software projects. Maven uses standard configuration files called Project Object Model (POM) files to define projects and manage the build process. POM files describe the module and component dependencies, build order, and targets for the resulting project packaging and output using an XML file. This ensures that the project is built in a correct and uniform manner. A Maven repository stores Java libraries, plug-ins, and other build artifacts. The default public repository is the Maven 2 Central Repository, but repositories can be private and internal within a company to share common artifacts among development teams. Repositories are also available from third parties. You can use the online Maven repository with your Spring Boot projects or you can download the Red Hat Decision Manager Maven repository. The recommended approach is to use the online Maven repository with your Spring Boot projects. Maven settings used with a repository manager or repository on a shared server provide better control and manageability of projects.

Commands:
Chapter 9. Using canonicalized DNS host names in IdM DNS canonicalization is disabled by default on Identity Management (IdM) clients to avoid potential security risks. For example, if an attacker controls the DNS server and a host in the domain, the attacker can cause the short host name, such as demo , to resolve to a compromised host, such as malicious.example.com . In this case, the user connects to a different server than expected. This procedure describes how to use canonicalized host names on IdM clients. 9.1. Adding an alias to a host principal By default, Identity Management (IdM) clients enrolled by using the ipa-client-install command do not allow to use short host names in service principals. For example, users can use only host/demo.example.com@EXAMPLE.COM instead of host/demo@EXAMPLE.COM when accessing a service. Follow this procedure to add an alias to a Kerberos principal. Note that you can alternatively enable canonicalization of host names in the /etc/krb5.conf file. For details, see Enabling canonicalization of host names in service principals on clients . Prerequisites The IdM client is installed. The host name is unique in the network. Procedure Authenticate to IdM as the admin user: Add the alias to the host principal. For example, to add the demo alias to the demo.examle.com host principal: 9.2. Enabling canonicalization of host names in service principals on clients Follow this procedure to enable canonicalization of host names in services principals on clients. Note that if you use host principal aliases, as described in Adding an alias to a host principal , you do not need to enable canonicalization. Prerequisites The Identity Management (IdM) client is installed. You are logged in to the IdM client as the root user. The host name is unique in the network. Procedure Set the dns_canonicalize_hostname parameter in the [libdefaults] section in the /etc/krb5.conf file to false : 9.3. Options for using host names with DNS host name canonicalization enabled If you set dns_canonicalize_hostname = true in the /etc/krb5.conf file as explained in Enabling canonicalization of host names in service principals on clients , you have the following options when you use a host name in a service principal: In Identity Management (IdM) environments, you can use the full host name in a service principal, such as host/demo.example.com@EXAMPLE.COM . In environments without IdM, but if the RHEL host as a member of an Active Directory (AD) domain, no further considerations are required, because AD domain controllers (DC) automatically create service principals for NetBIOS names of the machines enrolled into AD.

Commands:
kinit admin
ipa host-add-principal demo.example.com --principal= demo
[libdefaults] dns_canonicalize_hostname = true
Chapter 10. Debezium Server (Developer Preview) Debezium Server is a ready-to-use application that streams change events from a data source directly to a configured data sink without relying on an Apache Kafka Connect infrastructure. Important Debezium Server is Developer Preview software only. Developer Preview software is not supported by Red Hat in any way and is not functionally complete or production-ready. Do not use Developer Preview software for production or business-critical workloads. Developer Preview software provides early access to upcoming product software in advance of its possible inclusion in a Red Hat product offering. Customers can use this software to test functionality and provide feedback during the development process. This software might not have any documentation, is subject to change or removal at any time, and has received limited testing. Red Hat might provide ways to submit feedback on Developer Preview software without an associated SLA. For more information about the support scope of Red Hat Developer Preview software, see Developer Preview Support Scope . 10.1. Debezium Server sink destinations For this Developer Preview release of Debezium Server, you can configure the following sink destinations: Apache Kafka Redis Streams Note The Debezium community documentation refers to the use of several other data sinks. For this Developer Preview release, configure Debezium Server to use one of the data sinks in the preceding list. 10.2. Change event streaming with Debezium Server and an Apache Kafka event sink vs. with Kafka Connect and the Debezium connectors Debezium Server includes connectors that can send event data directly to a Kafka sink. It does not require you to deploy connectors or deploy a Kafka Connect cluster. If you already run an Apache Kafka cluster, you can use that cluster to test Debezium Server by configuring the cluster as a sink destination. Note Running Debezium Server with a Kafka sink does not provide some features that are available when you run the Debezium source connectors on Kafka Connect. For example, a Debezium Server connector can use only a single task to write to a data sink, whereas, most connectors that run on Kafka Connect can use multiple tasks. Also, Debezium Server does not provide advanced features, such as customized automatic topic creation. 10.3. Deploying and using Debezium Server You can obtain the Developer Preview version of Debezium Server from the Software Downloads on the Red Hat Customer Portal. For information about how to deploy and use Debezium Server, see the Debezium community documentation . Additional resources For information about deploying Debezium connectors to Kafka Connect, see the source connector documentation . Revised on 2024-10-10 19:36:09 UTC

Commands:
Chapter 86. DockerOutput schema reference Used in: Build The type property is a discriminator that distinguishes use of the DockerOutput type from ImageStreamOutput . It must have the value docker for the type DockerOutput . Property Description image The full name which should be used for tagging and pushing the newly built image. For example quay.io/my-organization/my-custom-connect:latest . Required. string pushSecret Container Registry Secret with the credentials for pushing the newly built image. string additionalKanikoOptions Configures additional options which will be passed to the Kaniko executor when building the new Connect image. Allowed options are: --customPlatform, --insecure, --insecure-pull, --insecure-registry, --log-format, --log-timestamp, --registry-mirror, --reproducible, --single-snapshot, --skip-tls-verify, --skip-tls-verify-pull, --skip-tls-verify-registry, --verbosity, --snapshotMode, --use-new-run. These options will be used only on OpenShift where the Kaniko executor is used. They will be ignored on OpenShift. The options are described in the Kaniko GitHub repository . Changing this field does not trigger new build of the Kafka Connect image. string array type Must be docker . string

Commands:
A.3. Accessing Red Hat Documentation Red Hat Product Documentation located at https://access.redhat.com/documentation/ serves as a central source of information. It provides different kinds of books from release and technical notes to installation, user, and reference guides in HTML, PDF, and EPUB formats. The following is a brief list of documents that are directly or indirectly relevant to this book: Red Hat Software Collections 3.8 Release Notes - The Release Notes for Red Hat Software Collections 3.8 document the major features and contains other information about Red Hat Software Collections, a Red Hat offering that provides a set of dynamic programming languages, database servers, and various related packages. Red Hat Developer Toolset 12.1 User Guide - The User Guide for Red Hat Developer Toolset 12.1 contains information about Red Hat Developer Toolset, a Red Hat offering for developers on the Red Hat Enterprise Linux platform. Using Software Collections, Red Hat Developer Toolset provides current versions of the GCC compiler, GDB debugger and other binary utilities. Using Red Hat Software Collections 3.8 Container Images - This guide provides information on how to use container images based on Red Hat Software Collections. The available container images include applications, daemons, and databases. The images can be run on Red Hat Enterprise Linux 7 Server and Red Hat Enterprise Linux Atomic Host. Red Hat Enterprise Linux 7 Developer Guide - The Developer Guide for Red Hat Enterprise Linux 7 provides detailed description of Red Hat Developer Toolset features, as well as an introduction to Red Hat Software Collections, and information on libraries and runtime support, compiling and building, debugging, and profiling. Red Hat Enterprise Linux 7 System Administrator's Guide - The System Administrator's Guide for Red Hat Enterprise Linux 7 documents relevant information regarding the deployment, configuration, and administration of Red Hat Enterprise Linux 7. Red Hat Enterprise Linux 6 Developer Guide - The Developer Guide for Red Hat Enterprise Linux 6 provides detailed description of Red Hat Developer Toolset features, as well as an introduction to Red Hat Software Collections, and information on libraries and runtime support, compiling and building, debugging, and profiling. Red Hat Enterprise Linux 6 Deployment Guide - The Deployment Guide for Red Hat Enterprise Linux 6 documents relevant information regarding the deployment, configuration, and administration of Red Hat Enterprise Linux 6.

Commands:
Red Hat OpenStack Services on OpenShift Certification Workflow Guide Red Hat Software Certification 2025 For Use with Red Hat OpenStack 18 Red Hat Customer Content Services

Commands:
subscription-manager register
subscription-manager list --available*
subscription-manager attach --pool=<pool_ID>
subscription-manager repos --enable=cert-1-for-rhel-9-x86_64-rpms
dnf install redhat-certification dnf install redhat-certification-rhoso
rhoso-cert-init
share.share_network_id <network_uuid> share.alt_share_network_id <network_uuid> share.admin_share_network_id <network_uuid> share.security_service <security_service_mapping> share.backend_replication_type <replication_style> share.username_for_user_rules <Username> share.override_ip_for_nfs_access <IP/CIDR> volume.build_interval 10 volume.build_timeout 300 volume.storage_protocol <iSCSI, FC, NVMe-TCP, NFS, etc.> volume.vendor_name <Driver's vendor name>
rhoso-cert-run
rhoso-cert-logs
rhoso-cert-logs Spawning a pod to access the logs in PVC rhoso-cert-cinder-6f855 pod/rhoso-cert-cinder-logs created Waiting for the rhoso-cert-cinder-logs pod to be ready Saving tempest logs Saving logs from the individual Tempest pods: Saving rhoso-cert-cinder-volumes-workflow-step-0-q9btc.log Saving rhoso-cert-cinder-backups-workflow-step-1-5p9xf.log Saving rhoso-cert-cinder-multi-attach-volume-workflow-step-2-zpwh2.log Saving rhoso-cert-cinder-consistency-groups-workflow-step-3-tmb24.log Collect a must-gather report? [y/N] : n Done. Logs are stored in rhoso-cert-cinder-2024-Aug-01_11-48-08
rhoso-cert-save
rhoso-cert-cleanup
cp /usr/share/redhat-certification-rhoso/rhoso-cert-debug.yaml <current test directory>
rhoso-cert-init rhoso-cert-run
rhoso-cert-test-accounts
rhoso-cert-cleanup
rhoso-cert-init
sudo rhcert-cli login sudo rhcert-cli upload
rhcert-cli login
rhcert-cli upload
rhcert-cli upload --certification-id xxxxx --description "Any file description" --file /var/log/redhat-certification/xyz.tgz
[user1@testsystem ~]USD sudo rhcert-cli upload Please enter the Certification ID: 625817 Please enter description: Cinder result file upload Please enter the result path: /var/log/redhat-certification/rhoso-cert-cinder-2024-Jul-31_04-25-24.tgz Uploading zip files to Red Hat for the Certification ID: 625817 Authorization failed Please visit https://sso.redhat.com/auth/realms/redhat-external/device?user_code=FOJQ-BLZS and grant the authorization for this host Have you granted the authorization? (yes|no) yes response: yes response: True
Success: Test results rhoso-cert-cinder-2024-Jul-31_04-25-24.tgz uploaded to certification ID 625817
Chapter 139. KafkaBridgeProducerSpec schema reference Used in: KafkaBridgeSpec Full list of KafkaBridgeProducerSpec schema properties Configures producer options for the Kafka Bridge. Example Kafka Bridge producer configuration apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaBridge metadata: name: my-bridge spec: # ... producer: enabled: true config: acks: 1 delivery.timeout.ms: 300000 # ... Use the producer.config properties to configure Kafka options for the producer as keys. The values can be one of the following JSON types: String Number Boolean Exceptions You can specify and configure the options listed in the Apache Kafka configuration documentation for producers . However, Streams for Apache Kafka takes care of configuring and managing options related to the following, which cannot be changed: Kafka cluster bootstrap address Security (encryption, authentication, and authorization) Consumer group identifier Properties with the following prefixes cannot be set: bootstrap.servers sasl. security. ssl. If the config property contains an option that cannot be changed, it is disregarded, and a warning message is logged to the Cluster Operator log file. All other supported options are forwarded to Kafka Bridge, including the following exceptions to the options configured by Streams for Apache Kafka: Any ssl configuration for supported TLS versions and cipher suites Important The Cluster Operator does not validate the keys or values of config properties. If an invalid configuration is provided, the Kafka Bridge deployment might not start or might become unstable. In this case, fix the configuration so that the Cluster Operator can roll out the new configuration to all Kafka Bridge nodes. 139.1. KafkaBridgeProducerSpec schema properties Property Property type Description enabled boolean Whether the HTTP producer should be enabled or disabled. The default is enabled ( true ). config map The Kafka producer configuration used for producer instances created by the bridge. Properties with the following prefixes cannot be set: ssl., bootstrap.servers, sasl., security. (with the exception of: ssl.endpoint.identification.algorithm, ssl.cipher.suites, ssl.protocol, ssl.enabled.protocols).

Commands:
apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaBridge metadata: name: my-bridge spec: # producer: enabled: true config: acks: 1 delivery.timeout.ms: 300000 #
Chapter 12. Configuring the transactions subsystem 12.1. Configuring the transactions subsystem When you manage an enterprise application that processes financial transactions, order management, or other critical workflows, you need to ensure reliable operations and data consistency. The transactions subsystem in JBoss EAP gives you full control over the Transaction Manager TM, letting you configure timeout values, enable transaction logging, and collect statistics. If your application runs across multiple systems and transaction propagation is required then at least one of JBoss Remoting or JTS needs to be enabled. JBoss EAP uses the Narayana transaction manager to handle transactions efficiently. It supports industry-standard protocols like Jakarta Transactions, JTS, and Web Services Transactions. Whether you update databases, send messages, or coordinate distributed services, the transactions subsystem ensures consistency, reliability, and resilience. Additional resources Managing Transactions on JBoss EAP . Note Please note that this link directs you to the Managing Transactions Guide for JBoss EAP 7.4. We are currently in the process of updating the documentation for Red Hat JBoss Enterprise Application Platform 8.0. This link will be updated once the new documentation is complete.

Commands:
Preface This guide provides information and instructions for implementing Fuse transactional applications. The information is organized as follows: Chapter 1, Introduction to transactions Chapter 2, Getting started with transactions on Karaf (OSGi) Chapter 3, Interfaces for configuring and referencing transaction managers Chapter 4, Configuring the Narayana transaction manager Chapter 5, Using the Narayana transaction manager Chapter 6, Using JDBC data sources Chapter 7, Using JMS connection factories Chapter 8, About Java connector architecture Chapter 9, Writing a Camel application that uses transactions

Commands:
5.3.9. Activating and Deactivating Volume Groups When you create a volume group it is, by default, activated. This means that the logical volumes in that group are accessible and subject to change. There are various circumstances for which you need to make a volume group inactive and thus unknown to the kernel. To deactivate or activate a volume group, use the -a ( --available ) argument of the vgchange command. The following example deactivates the volume group my_volume_group . If clustered locking is enabled, add 'e' to activate or deactivate a volume group exclusively on one node or 'l' to activate or/deactivate a volume group only on the local node. Logical volumes with single-host snapshots are always activated exclusively because they can only be used on one node at once. You can deactivate individual logical volumes with the lvchange command, as described in Section 5.4.10, "Changing the Parameters of a Logical Volume Group" , For information on activating logical volumes on individual nodes in a cluster, see Section 5.7, "Activating Logical Volumes on Individual Nodes in a Cluster" .

Commands:
vgchange -a n my_volume_group