mtpti5iD/redhat-docs_dataset huggingface dataset:
8.210. sapconf 8.210.1. RHBA-2014:1424 - sapconf bug fix update Updated sapconf package that fixes several bugs is now available for Red Hat Enterprise Linux 6. The sapconf package contains a script that checks the basic installation of Red Hat Enterprise Linux and modifies it according to SAP requirements. The script ensures that all necessary packages are installed and that configuration parameters are set correctly to run SAP software. Bug Fixes BZ# 1024356 In certain situations, the sapconf script created the /etc/hosts file in an incorrect format, thus the file did not return the fully qualified domain name (FQDN). As a consequence, SAP installation failed unexpectedly. With this update, the script has been edited to handle situations when the incorrect /etc/hosts file was created. In addition, when FQDN is not returned properly, the script exits with the error code 4. BZ# 1025187 Previously, the manual page for the sapconf script was missing. This update adds the missing manual page to the sapconf package. BZ# 1040617 Due to a bug in the underlying source code, the sapconf script was unable to verify if a virtual guest was a VMware guest. Consequently, an attempt to use sapconf on such a guest failed. With this update, sapconf recognizes the VMware guests as expected. BZ# 1051017 The order of reading limit files in Red Hat Enterprise Linux is as follows: First is read the /etc/security/limits.conf file and then the limit files located in the /etc/security/limits.d/ directory according to the C localization functions. When an entry is specified in two or more files, the entry that is read last takes effect. Previously, the sapconf script wrote entries to /etc/security/limits.conf, which could cause the sapconf entries to be overwritten by the same entries in files located in /etc/security/limits.d/. With this update, a separate sapconf limit file has been added to /etc/security/limits.d/ to anticipate this bug. BZ# 1083651 When the sapconf script updated the /etc/hosts file, permissions of that file were incorrectly modified. This update applies a patch to fix this bug, and sapconf no longer overwrites the file's permissions. Users of sapconf are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Chapter 1. Overview Red Hat OpenShift Data Foundation is software-defined storage that is optimized for container environments. It runs as an operator on OpenShift Container Platform to provide highly integrated and simplified persistent storage management for containers. Red Hat OpenShift Data Foundation is integrated into the latest Red Hat OpenShift Container Platform to address platform services, application portability, and persistence challenges. It provides a highly scalable backend for the generation of cloud-native applications, built on a technology stack that includes Red Hat Ceph Storage, the Rook.io Operator, and NooBaa's Multicloud Object Gateway technology. Red Hat OpenShift Data Foundation is designed for FIPS. When running on RHEL or RHEL CoreOS booted in FIPS mode, OpenShift Container Platform core components use the RHEL cryptographic libraries submitted to NIST for FIPS Validation on only the x86_64, ppc64le, and s390X architectures. For more information about the NIST validation program, see Cryptographic Module Validation Program . For the latest NIST status for the individual versions of the RHEL cryptographic libraries submitted for validation, see Compliance Activities and Government Standards . Red Hat OpenShift Data Foundation provides a trusted, enterprise-grade application development environment that simplifies and enhances the user experience across the application lifecycle in a number of ways: Provides block storage for databases. Shared file storage for continuous integration, messaging, and data aggregation. Object storage for cloud-first development, archival, backup, and media storage. Scale applications and data exponentially. Attach and detach persistent data volumes at an accelerated rate. Stretch clusters across multiple data-centers or availability zones. Establish a comprehensive application container registry. Support the generation of OpenShift workloads such as Data Analytics, Artificial Intelligence, Machine Learning, Deep Learning, and Internet of Things (IoT). Dynamically provision not only application containers, but data service volumes and containers, as well as additional OpenShift Container Platform nodes, Elastic Block Store (EBS) volumes and other infrastructure services. 1.1. About this release Red Hat OpenShift Data Foundation 4.18 (RHXX-xxxx-xxxx) is now available. New enhancements, features, and known issues that pertain to OpenShift Data Foundation 4.18 are included in this topic. Red Hat OpenShift Data Foundation 4.18 is supported on the Red Hat OpenShift Container Platform version 4.18. For more information, see Red Hat OpenShift Data Foundation Supportability and Interoperability Checker . For Red Hat OpenShift Data Foundation life cycle information, refer Red Hat OpenShift Data Foundation Life Cycle .

Commands:
Appendix B. Revision history 0.1-5 Thu Jan 30 2025, Gabriela Fialova ( gfialova@redhat.com ) Added an Known Issue Jira:RHELDOCS-19603 (IdM SSSD) 0.1-4 Wed Dec 4 2024, Gabriela Fialova ( gfialova@redhat.com ) Updated the Customer Portal labs section Updated the Installation section 0.1-3 Fri August 9 2024, Brian Angelica ( bangelic@redhat.com ) Added a Known Issue RHEL-11397 (Installer and image creation) 0.1-2 Fri June 7 2024, Brian Angelica ( bangelic@redhat.com ) Updated a Known Issue in Jira:RHELDOCS-17954 (Red Hat Enterprise Linux System Roles). 0.1-1 Fri May 10 2024, Brian Angelica ( bangelic@redhat.com ) Updated Tech Preview in BZ#1690207 . 0.1-0 Thu May 9 2024, Gabriela Fialova ( gfialova@redhat.com ) Updated a known issue BZ#1730502 (Storage). 0.0-9 Mon April 29 2024, Gabriela Fialova ( gfialova@redhat.com ) Added an enhancement BZ#2093355 (Security). 0.0-8 Mon March 4 2024, Lucie Varakova ( lvarakova@redhat.com ) Added a bug fix Jira:SSSD-6096 (Identity Management). 0.0-7 Thu February 29 2024, Lucie Varakova ( lvarakova@redhat.com ) Added a deprecated functionality Jira:RHELDOCS-17641 (Networking). 0.0-6 Tue February 13 2024, Lucie Varakova ( lvarakova@redhat.com ) Added a deprecated functionality Jira:RHELDOCS-17573 (Identity Management). 0.0-5 Fri February 2 2024, Lucie Varakova ( lvarakova@redhat.com ) Added a known issue BZ#1834716 (Security). Updated the Jira:RHELDOCS-16755 deprecated functionality note (Containers). 0.0-4 Fri January 19 2024, Lucie Varakova ( lvarakova@redhat.com ) Added an enhancement related to Python Jira:RHELDOCS-17369 (Dynamic programming languages, web and database servers). Added an enhancement Jira:RHELDOCS-16367 (The web console). 0.0-3 Wed January 10 2024, Lucie Varakova ( lvarakova@redhat.com ) Added a rebase BZ#2196425 (Identity Management). Updated the Jira:RHELPLAN-156196 new feature description (Supportability). Added deprecated functionality Jira:RHELDOCS-17380 (Security). Other minor updates. 0.0-2 Thu November 16 2023, Lenka Spackova ( lspackova@redhat.com ) Node.js 20 is now fully supported ( BZ#2186718 ). 0.0-1 Wed November 15 2023, Lucie Varakova ( lvarakova@redhat.com ) Release of the Red Hat Enterprise Linux 8.9 Release Notes. 0.0-0 Wed September 27 2023, Lucie Varakova ( lvarakova@redhat.com ) Release of the Red Hat Enterprise Linux 8.9 Beta Release Notes.

Commands:
Chapter 14. Fixed issues in Red Hat Decision Manager 7.13.4 Red Hat Decision Manager 7.13.4 provides increased stability and fixed issues listed in this section. 14.1. Business Central Dashbuilder does not support the type MILLISECOND [ RHPAM-4659 ] Standalone Business Central does not start on Red Hat Enterprise Linux (RHEL) [ RHPAM-4715 ] Data filter is not working as expected [ RHPAM-4664 ] 14.2. KIE Server The ClassNotFoundException occurs when launching a business application with the command mvn spring-boot:run [ RHDM-1984 ] Behavior of the ClassCastException exception changed after RHPAM 7.13.0 for empty values in the request [ RHPAM-4725 ] The NoSuchMethodError occurs when retrieving Kie server information on SpringBoot [ RHPAM-4714 ] The productized cxf-rt-bindings-soap dependency in kie-camel is invalid [ RHPAM-4683 ] The NullPointerException (NPE) occurs on TupleSetsImpl.setNextTuple with SubnetworkTuple [ RHDM-1968 ] 14.3. Red Hat OpenShift Container Platform Upgrade JBoss Enterprise Application Server to 7.4.12 on RHPAM and BAMOE images [ RHPAM-4762 ] Unable to set direct-verification=true individually in LDAP realm by operator [ RHPAM-4754 ] Unable to connect to an external PostgreSQL database over SSL from kie-server on OpenShift Container Platform [ RHPAM-4740 ] Do not set URL envs if the jdbcUrl property is not set [ RHPAM-4713 ] Legacy datasource scripts do not consider XA properties for the mariadb driver [ RHPAM-4712 ] Correctly set the XA Connection URL property [ RHPAM-4711 ] KIE Server configMap points to SSL routes when SSL is disabled [ RHPAM-4709 ] Can't login into Business Central without SSL configured [ RHPAM-4705 ] NoSuchMethodException : Method setURL not found [ RHPAM-4704 ] The pom.xml file in rhpam-7-openshift-image/quickstarts/router-ext contains the wrong version [ RHPAM-4682 ] 14.4. Decision engine Unnecessary warning message appears when executing a DRL file [ RHPAM-4758 ] The NullPointerException error occurs in MemoryFileSystem when kbase.name is empty in kmodule.xml [ RHPAM-4755 ] With a non-executable model and the mvel dialect, when the modify-block is placed inside a block such as the if-block in RHS, the modify does not work correctly [ RHDM-1985 ] After upgrading to 7.13.2, rules fire incorrectly when BigDecimal equality is involved in a pattern [ RHDM-1974 ] The executable model doesn't resolve bind variables from another pattern of the same type in method call in LHS for property reactivity [ RHDM-1969 ] The executable model doesn't resolve bind variables in a method call in LHS for property reactivity [ RHDM-1967 ]

Commands:
Chapter 7. Teiid Designer Examples 7.1. Teiid Designer Examples We are going to dive right into a couple examples of common tasks in this section. These examples will give you a quick introduction to the capabilities that are built into Teiid Designer to assist you with common design tasks. Specifically, we will introduce the following concepts: Guides The Guides View is a good starting point for many common modeling tasks. The view includes categorized Modeling Actions and also links to Cheat Sheets for common tasks. The categorized Modeling Actions simply group together all of the actions that you'll need to accomplish a task. You can launch the actions directly from the Guides view, rather than hunting through the various Teiid Designer menus. Cheat Sheets The Cheat Sheets go beyond even the categorized Action Sets, and walk you step-by-step through some common tasks. At each step, the data entered in the step is carried through the process when possible. After seeing the Guides and Cheat Sheets in action, subsequent chapters will offer detailed explanations of the various concepts and actions.

Commands:
Chapter 1. Support policy for Cryostat Red Hat supports a major version of Cryostat for a minimum of 6 months. Red Hat bases this figure on the time that the product gets released on the Red Hat Customer Portal. You can install and deploy Cryostat on Red Hat OpenShift Container Platform 4.10 or a later version that runs on an x86_64 architecture. Additional resources For more information about the Cryostat life cycle policy, see Red Hat build of Cryostat on the Red Hat OpenShift Container Platform Life Cycle Policy web page.

Commands:
Chapter 62. JSON Gson Gson is a Data Format which uses the Gson Library . from("activemq:My.Queue"). marshal().json(JsonLibrary.Gson). to("mqseries:Another.Queue"); 62.1. Dependencies When using json-gson with Red Hat build of Camel Spring Boot make sure to use the following Maven dependency to have support for auto configuration: <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-gson-starter</artifactId> </dependency> 62.2. Gson Options The JSON Gson dataformat supports 3 options, which are listed below. Name Default Java Type Description prettyPrint Boolean To enable pretty printing output nicely formatted. Is by default false. unmarshalType String Class name of the java type to use when unmarshalling. contentTypeHeader Boolean Whether the data format should set the Content-Type header with the type from the data format. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSON. 62.3. Spring Boot Auto-Configuration The component supports 4 options, which are listed below. Name Description Default Type camel.dataformat.json-gson.content-type-header Whether the data format should set the Content-Type header with the type from the data format. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSON. true Boolean camel.dataformat.json-gson.enabled Whether to enable auto configuration of the json-gson data format. This is enabled by default. Boolean camel.dataformat.json-gson.pretty-print To enable pretty printing output nicely formatted. Is by default false. false Boolean camel.dataformat.json-gson.unmarshal-type Class name of the java type to use when unmarshalling. String

Commands:
from("activemq:My.Queue"). marshal().json(JsonLibrary.Gson). to("mqseries:Another.Queue");
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-gson-starter</artifactId> </dependency>
Chapter 5. Secure Installation Security begins with the first time you put that CD or DVD into your disk drive to install Red Hat Enterprise Linux. Configuring your system securely from the beginning makes it easier to implement additional security settings later. 5.1. Disk Partitions Red Hat recommends creating separate partitions for /boot , / , /home , /tmp/ , and /var/tmp/ . If the root partition ( / ) becomes corrupt, your data could be lost forever. By using separate partitions, the data is slightly more protected. You can also target these partition for frequent backups. The purpose for each partition is different and we will address each partition. /boot - This partition is the first partition that is read by the system during the boot. The boot loader and kernel images that are used to boot your system into Red Hat Enterprise Linux are stored in this partition. This partition should not be encrypted. If this partition is included in / and that partition is encrypted or otherwise becomes unavailable, your system will not be able to boot. /home - When user data ( /home ) is stored in / instead of a separate partition, the partition can fill up causing the operating system to become unstable. Also, when upgrading your system to the version of Red Hat Enterprise Linux, it is a lot easier if you can keep your data in the /home partition as it will not be overwritten during installation. /tmp and /var/tmp/ - Both the /tmp and the /var/tmp/ directories are used to store data that does not need to be stored for a long period of time. However, if a lot of data floods one of these directories, it can consume all of your storage space. If this happens and these directories are stored within / , your system could become unstable and crash. For this reason, moving these directories into their own partitions is a good idea.

Commands:
Chapter 50. Case management Case management is an extension of Business Process Management (BPM) that enables you to manage adaptable business processes. BPM is a management practice used to automate tasks that are repeatable and have a common pattern, with a focus on optimization by perfecting a process. Business processes are usually modeled with clearly defined paths leading to a business goal. This requires a lot of predictability, usually based on mass-production principles. However, many real-world applications cannot be described completely from start to finish (including all possible paths, deviations, and exceptions). Using a process-oriented approach in certain cases can lead to complex solutions that are hard to maintain. Case management provides problem resolution for non-repeatable, unpredictable processes as opposed to the efficiency-oriented approach of BPM for routine, predictable tasks. It manages one-off situations when the process cannot be predicted in advance. A case definition usually consists of loosely coupled process fragments that can be connected directly or indirectly to lead to certain milestones and ultimately a business goal, while the process is managed dynamically in response to changes that occur during run time. In Red Hat Process Automation Manager, case management includes the following core process engine features: Case file instance A per case runtime strategy Case comments Milestones Stages Ad hoc fragments Dynamic tasks and processes Case identifier (correlation key) Case lifecycle (close, reopen, cancel, destroy) A case definition is always an ad hoc process definition and does not require an explicit start node. The case definition is the main entry point for the business use case. A process definition is introduced as a supporting construct of the case and can be invoked either as defined in the case definition or dynamically to bring in additional processing when required. A case definition defines the following new objects: Activities (required) Case file (required) Milestones Roles Stages

Commands:
Chapter 5. Installation environment options for Red Hat Decision Manager With Red Hat Process Automation Manager, you can set up a development environment to develop business applications, a runtime environment to run those applications to support decisions, or both. Development environment : Typically consists of one Business Central installation and at least one KIE Server installation. You can use Business Central to design decisions and other artifacts, and you can use KIE Server to execute and test the artifacts that you created. Runtime environment : Consists of one or more KIE Server instances with or without Business Central. Business Central has an embedded Process Automation Manager controller. If you install Business Central, use the Menu Deploy Execution servers page to create and maintain containers. If you want to automate KIE Server management without Business Central, you can use the headless Process Automation Manager controller. You can also cluster both development and runtime environments. A clustered development or runtime environment consists of a unified group or cluster of two or more servers. The primary benefit of clustering Red Hat Process Automation Manager development environments is high availability and enhanced collaboration, while the primary benefit of clustering Red Hat Process Automation Manager runtime environments is high availability and load balancing. High availability decreases the chance of data loss when a single server fails. When a server fails, another server fills the gap by providing a copy of the data that was on the failed server. When the failed server comes online again, it resumes its place in the cluster. Note Clustering of the runtime environment is currently supported on Red Hat JBoss EAP 7.4 and Red Hat OpenShift Container Platform only.

Commands:
Preface Standalone Manager installation is manual and customizable. You must install a Red Hat Enterprise Linux machine, then run the configuration script ( engine-setup ) and provide information about how you want to configure the Red Hat Virtualization Manager. Add hosts and storage after the Manager is running. At least two hosts are required for virtual machine high availability. In a local database environment, the Manager database and Data Warehouse database can be created automatically by the Manager configuration script. Alternatively, you can create these databases manually on the Manager machine before running engine-setup . See the Planning and Prerequisites Guide for information on environment options and recommended configuration. Table 1. Red Hat Virtualization Key Components Component Name Description Red Hat Virtualization Manager A service that provides a graphical user interface and a REST API to manage the resources in the environment. The Manager is installed on a physical or virtual machine running Red Hat Enterprise Linux. Hosts Red Hat Enterprise Linux hosts (RHEL hosts) and Red Hat Virtualization Hosts (image-based hypervisors) are the two supported types of host. Hosts use Kernel-based Virtual Machine (KVM) technology and provide resources used to run virtual machines. Shared Storage A storage service is used to store the data associated with virtual machines. Data Warehouse A service that collects configuration information and statistical data from the Manager. Standalone Manager Architecture The Red Hat Virtualization Manager runs on a physical server, or a virtual machine hosted in a separate virtualization environment. A standalone Manager is easier to deploy and manage, but requires an additional physical server. The Manager is only highly available when managed externally with a product such as Red Hat's High Availability Add-On. The minimum setup for a standalone Manager environment includes: One Red Hat Virtualization Manager machine. The Manager is typically deployed on a physical server. However, it can also be deployed on a virtual machine, as long as that virtual machine is hosted in a separate environment. The Manager must run on Red Hat Enterprise Linux 7. A minimum of two hosts for virtual machine high availability. You can use Red Hat Enterprise Linux hosts or Red Hat Virtualization Hosts (RHVH). VDSM (the host agent) runs on all hosts to facilitate communication with the Red Hat Virtualization Manager. One storage service, which can be hosted locally or on a remote server, depending on the storage type used. The storage service must be accessible to all hosts. Figure 1. Standalone Manager Red Hat Virtualization Architecture

Commands:
Chapter 4. Introduction to devfile in Dev Spaces Devfiles are yaml text files used for development environment customization. Use them to configure a devfile to suit your specific needs and share the customized devfile across multiple workspaces to ensure identical user experience and build, run, and deploy behaviours across your team. Red Hat OpenShift Dev Spaces-specific devfile features Red Hat OpenShift Dev Spaces is expected to work with most of the popular images defined in the components section of devfile. For production purposes, it is recommended to use one of the Universal Base Images as a base image for defining the Cloud Development Environment. Warning Some images can not be used as-is for defining Cloud Development Environment since Visual Studio Code - Open Source ("Code - OSS") can not be started in the containers with missing openssl and libbrotli . Missing libraries should be explicitly installed on the Dockerfile level e.g. RUN yum install compat-openssl11 libbrotli Devfile and Universal Developer Image You do not need a devfile to start a workspace. If you do not include a devfile in your project repository, Red Hat OpenShift Dev Spaces automatically loads a default devfile with a Universal Developer Image (UDI). Devfile Registry Devfile Registry contains ready-to-use community-supported devfiles for different languages and technologies. Devfiles included in the registry should be treated as samples rather than templates. Additional resources What is a devfile Benefits of devfile Devfile customization overview Devfile.io Customizing Cloud Development Environments

Commands: