mtpti5iD/redhat-docs_dataset huggingface dataset:
7.18. binutils 7.18.1. RHBA-2015:1274 - binutils bug fix update Updated binutils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The binutils packages provide a set of binary utilities, including "ar" (for creating, modifying and extracting from archives), "as" (a family of GNU assemblers), "gprof" (for displaying call graph profile data), "ld" (the GNU linker), "nm" (for listing symbols from object files), "objcopy" (for copying and translating object files), "objdump" (for displaying information from object files), "ranlib" (for generating an index for the contents of an archive), "readelf" (for displaying detailed information about binary files), "size" (for listing the section sizes of an object or archive file), "strings" (for listing printable strings from files), "strip" (for discarding symbols), and "addr2line" (for converting addresses to file and line). Bug Fix BZ# 1175590 On IBM System z, the linker sometimes generated undesirable runtime relocations for thread-local-storage variables. These undesirable relocations could under certain circumstances cause execmod AVC errors. This bug has been fixed, and AVC errors are no longer returned in this scenario. Users of binutils are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Fuse 7.13 Product Overview 1.1. Fuse distributions Fuse 7.13 is provided in the form of two different distributions, as follows: Fuse standalone The classic distribution of Fuse, supported on multiple operating systems. This distribution is supported for the following container types: Apache Karaf JBoss Enterprise Application Platform (EAP) Spring Boot Fuse on OpenShift The distribution of Fuse for running integration applications on OpenShift (supported on the Red Hat Enterprise Linux operating system). In this case, the supported container types are provided in the form of docker-formatted container images: Java image (for Spring Boot) Apache Karaf image JBoss EAP image 1.2. Supported Configurations Important For users running Fuse with Java 8 on Karaf, it is recommended to use OpenJDK 8u282 or OpenJDK 8u302. Do not use OpenJDK 8u292, which has a known issue affecting the credential store (see ENTESB-16417 ). OracleJDK 1.8.0_291 is also affected by this issue. For information about supported configurations, standards, and components in version 7.13, see the following Customer Portal articles: Red Hat Fuse Supported Configurations Red Hat Fuse Supported Standards Red Hat Fuse Component Details

Commands:
8.175. redhat-release 8.175.1. RHEA-2013:1546 - redhat-release enhancement update for Red Hat Enterprise Linux 6.5 Enhanced redhat-release packages are now available for Red Hat Enterprise Linux 6.5. The redhat-release package contains licensing information regarding, and identifies the installed version of, Red Hat Enterprise Linux. These updated redhat-release packages reflect changes made for the release of Red Hat Enterprise Linux 6.5. Users of Red Hat Enterprise Linux 6 are advised to upgrade to these updated redhat-release packages, which add this enhancement.

Commands:
Chapter 2. Upgrading a host operating system from RHEL 8 to RHEL 9 You can perform a Red Hat Ceph Storage host operating system upgrade from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9 using the Leapp utility. Prerequisites A running Red Hat Ceph Storage 5.3 cluster. The following are the supported combinations of containerized Ceph daemons. For more information, see the How colocation works and its advantages section in the Red Hat Ceph Storage Installation Guide . Ceph Metadata Server ( ceph-mds ), Ceph OSD ( ceph-osd ), and Ceph Object Gateway ( radosgw ) Ceph Monitor ( ceph-mon ) or Ceph Manager ( ceph-mgr ), Ceph OSD ( ceph-osd ), and Ceph Object Gateway ( radosgw ) Ceph Monitor ( ceph-mon ), Ceph Manager ( ceph-mgr ), Ceph OSD ( ceph-osd ), and Ceph Object Gateway ( radosgw ) Procedure Deploy Red Hat Ceph Storage 5.3 on Red Hat Enterprise Linux 8.8 with service. Note Verify that the cluster contains two admin nodes, so that while performing host upgrade in one admin node (with _admin label), the second admin can be used for managing clusters. For full instructions, see Red Hat Ceph Storage installation in the Red Hat Ceph Storage Installation Guide and Deploying the Ceph daemons using the service specifications in the Operations guide . Set the noout flag on the Ceph OSD. Example Perform host upgrade one node at a time using the Leapp utility. Put respective node maintenance mode before performing host upgrade using Leapp. Syntax Example Enable the ceph tools repo manually when executing the leapp command with the --enablerepo parameter. Example Refer to Upgrading RHEL 8 to RHEL 9 within the Red Hat Enterprise Linux product documentation on the Red Hat Customer Portal. Important After performing in-place upgrade from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9, you need to manually enable and start the logrotate.timer service. Verify the new IMAGE_ID and VERSION of the Ceph cluster: Example Continue with the Red Hat Ceph Storage 5.3 to Red Hat Ceph Storage 7 upgrade by following the Upgrading the Red Hat Ceph Storage cluster steps in the Red Hat Ceph Storage Upgrade Guide .

Commands:
ceph osd set noout
ceph orch host maintenance enter HOST
ceph orch host maintenance enter host01
leapp upgrade --enablerepo rhceph-5-tools-for-rhel-9-x86_64-rpms
systemctl start logrotate.timer systemctl enable logrotate.timer
ceph version ceph orch ps
Chapter 55. Installing KIE Server with Oracle WebLogic Server After you have configured all required system properties in Oracle WebLogic Server, you can install KIE Server with Oracle WebLogic Server to streamline Red Hat Decision Manager application management. Prerequisites An Oracle WebLogic Server instance is configured as described in Chapter 54, Configuring Oracle WebLogic Server for KIE Server . Procedure Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options: Product: Process Automation Manager Version: 7.13.5 Download Red Hat Process Automation Manager 7.13.5 KIE Server for All Supported EE7 Containers . Extract the downloaded rhpam-7.13.5-kie-server-ee7.zip file to a temporary directory. In the WebLogic Administration Console, navigate to Deployments to view all existing applications. Click Install . Navigate to the temporary directory where you downloaded and extracted the rhpam-7.13.5-kie-server-ee7.zip file, and go to rhpam-7.13.5-kie-server-ee7/kie-server.war . Select the kie-server.war file and click to continue. Select Install this deployment as an application as the targeting style and click . Set the application name to kie-server and set the security model to DD Only . Leave the remaining options as default and click to continue. In the Additional Configuration section, choose No, I will review the configuration later and click Finish . 55.1. Verifying the KIE Server installation on Oracle WebLogic Server After you have installed KIE Server on Oracle WebLogic Server, verify that the installation was successful. Prerequisites An Oracle WebLogic Server instance is configured as described in Chapter 54, Configuring Oracle WebLogic Server for KIE Server . KIE Server is installed as described in Chapter 55, Installing KIE Server with Oracle WebLogic Server . Procedure Enter the KIE Server URL http://<HOST>:<PORT>/kie-server/services/rest/server in a web browser. Verify that KIE Server is running. If KIE Server is not running, stop and restart the Oracle WebLogic Server instance and try again to access the KIE Server URL.

Commands:
Chapter 2. Enhancements AMQ Streams 2.1 adds a number of enhancements. 2.1. Kafka 3.1.0 enhancements For an overview of the enhancements introduced with Kafka 3.1.0, refer to the Kafka 3.1.0 Release Notes . 2.2. OAuth configuration options New OAuth configuration properties have been introduced to the OAuth authentication configuration. The properties related to timeouts and extracting groups information. Timout properties oauth.connect.timeout.seconds specifies the maximum time in seconds to connect to an authorization server before a timeout. oauth.read.timeout.seconds specifies the maximum time in seconds to read from an authorization server before a timeout. The default is sixty seconds for both. Groups properties oauth.groups.claim specifies a JsonPath query to extract groups information from a JWT token or introspection endpoint response. Not set by default. oauth.groups.claim.delimiter specifies a delimiter to parse groups information when returned as a single delimited string. The default value is ',' (comma). Example OAuth configuration for a Kafka broker listener listener.name.client.oauthbearer.sasl.jaas.config=org.apache.kafka.common.security.oauthbearer.OAuthBearerLoginModule required \ # ... oauth.connect.timeout.seconds=60 oauth.read.timeout.seconds=60 oauth.groups.claim="USD.groups" oauth.groups.claim.delimiter="," See Rebalance performance tuning .

Commands:
listener.name.client.oauthbearer.sasl.jaas.config=org.apache.kafka.common.security.oauthbearer.OAuthBearerLoginModule required # oauth.connect.timeout.seconds=60 oauth.read.timeout.seconds=60 oauth.groups.claim="USD.groups" oauth.groups.claim.delimiter=","
Chapter 1. Overview of Builds Builds is an extensible build framework based on the Shipwright project , which you can use to build container images on an Red Hat OpenShift Service on AWS cluster. You can build container images from source code and Dockerfiles by using image build tools, such as Source-to-Image (S2I) and Buildah. You can create and apply build resources, view logs of build runs, and manage builds in your Red Hat OpenShift Service on AWS namespaces. Builds includes the following capabilities: Standard Kubernetes-native API for building container images from source code and Dockerfiles Support for Source-to-Image (S2I) and Buildah build strategies Extensibility with your own custom build strategies Execution of builds from source code in a local directory Shipwright CLI for creating and viewing logs, and managing builds on the cluster Integrated user experience with the Developer perspective of the Red Hat OpenShift Service on AWS web console Note Because Builds releases on a different cadence from Red Hat OpenShift Service on AWS, the Builds documentation is now available as a separate documentation set at builds for Red Hat OpenShift .

Commands:
B.4. Editor Preferences B.4.1. XML Document Preferences Important Please note that XML Document Modeling has been deprecated. XML Document Mapping Preferences provide ways to customize Mapping Diagram and Recursion Editor (XML) behavior. Figure B.3. XML Document Preferences Panel B.4.2. Table Editor Preferences Table Editor Preferences provide a way to customize the order and the information content for each model object type. Figure B.4. Table Editor Preferences Panel B.4.3. Transformation Editor Preferences Transformation Editor Preferences provide a way to customize SQL formatting, diagram layout, and default view entity properties. Figure B.5. Transformation Editor Preferences Panel B.4.4. VDB Editor Preferences VDB Editor Preferences provide a way to customize VDB editor behavior. Figure B.6. VDB Editor Preferences Panel

Commands:
2.8.9.5.2. ipset Commands The format of the ipset command is as follows: ipset [ options ] command [ command-options ] Where command is one of: create | add | del | test | destroy | list | save | restore | flush | rename | swap | help | version | - Allowed options are: -exist | -output [ plain | save | xml ] | -quiet | -resolve | -sorted | -name | -terse The create command is used to create a new data structure to store a set of IP data. The add command adds new data to the set, the data added is referred to as an element of the set. The -exist option suppresses error message if the element already exists, and it has a special role in updating a time out value. To change a time out, use the ipset add command and specify all the data for the element again, changing only the time out value as required, and using the -exist option. The test option is for testing if the element already exists within a set. The format of the create command is as follows: ipset create set-name type-name [ create-options ] The set-name is a suitable name chosen by the user, the type-name is the name of the data structure used to store the data comprising the set. The format of the type-name is as follows: method:datatype[ ,datatype[ ,datatype ] ] The allowed methods for storing data are: bitmap | hash | list The allowed data types are: ip | net | mac | port | iface When adding, deleting, or testing entries in a set, the same comma separated data syntax must be used for the data that makes up one entry, or element, in the set. For example: ipset add set-name ipaddr , portnum , ipaddr Note A set cannot contain IPv4 and IPv6 addresses at the same time. When a set is created it is bound to a family, inet for IPv4 or inet6 for IPv6 , and the default is inet . Example 2.3. Create an IP Set To create an IP set consisting of a source IP address, a port, and destination IP address, issue a command as follows: Once the set is created, entries can be added as follows: The set types have the following optional parameters in common. They must be specified when the set is created in order for them to be used: timeout - The value given with the create command will be the default value for the set created. If a value is given with the add command, it will be the initial non-default value for the element. Example 2.4. List an IP Set To list the contents of a specific IP Set, my-set , issue a command as follows: Omit the set name to list all sets. Example 2.5. Test the Elements of an IP Set Listing the contents of large sets is time consuming. You can test for the existence of an element as follows:

Commands:
~]# ipset create my-set hash:ip,port,ip
~]# ipset add my-set 192.168.1.2,80,192.168.2.2 ~]# ipset add my-set 192.168.1.2,443,192.168.2.2
~]# ipset list my-set Name: my-set Type: hash:ip,port,ip Header: family inet hashsize 1024 maxelem 65536 Size in memory: 8360 References: 0 Members: 192.168.1.2,tcp:80,192.168.2.2 192.168.1.2,tcp:443,192.168.2.2
~]# ipset test my-set 192.168.1.2,80,192.168.2.2 192.168.1.2,tcp:80,192.168.2.2 is in set my-set.
2. Installation Installation of Red Hat Enterprise Linux 4.9 is completed by upgrading from Red Hat Enterprise Linux 4.8. Important Before upgrading, ensure that the system has the most recent version of the up2date tool installed by running the command up2date up2date Warning Due to a known issue, if you are subscribed to the Red Hat Enterprise Linux 4 Extras channel and have the HelixPlayer package installed on your system, you must first manually remove the HelixPlayer package before updating the system to Red Hat Enterprise Linux 4.9. You can manually uninstall HelixPlayer by running the following command: Failing to uninstall the HelixPlayer package before updating your system may cause up2date to fail to update all packages to their Red Hat Enterprise Linux 4.9 versions. To update a Red Hat Enterprise Linux 4.8 installation, first ensure that the system is subscribed to the 4.9 channel, then use the up2date command: There is no media kit available for Red Hat Enterprise Linux 4.9.

Commands:
-e HelixPlayer
up2date --update
Chapter 8. Configuring the environment mode in KIE Server and Business Central You can set KIE Server to run in production mode or in development mode. Development mode provides a flexible deployment policy that enables you to update existing deployment units (KIE containers) while maintaining active process instances for small changes. It also enables you to reset the deployment unit state before updating active process instances for larger changes. Production mode is optimal for production environments, where each deployment creates a new deployment unit. In a development environment, you can click Deploy in Business Central to deploy the built KJAR file to a KIE Server without stopping any running instances (if applicable), or click Redeploy to deploy the built KJAR file and replace all instances. The time you deploy or redeploy the built KJAR, the deployment unit (KIE container) is automatically updated in the same target KIE Server. In a production environment, the Redeploy option in Business Central is disabled and you can click only Deploy to deploy the built KJAR file to a new deployment unit (KIE container) on a KIE Server. Procedure To configure the KIE Server environment mode, set the org.kie.server.mode system property to org.kie.server.mode=development or org.kie.server.mode=production . To configure the deployment behavior for a project in Business Central, go to project Settings General Settings Version and toggle the Development Mode option. Note By default, KIE Server and all new projects in Business Central are in development mode. You cannot deploy a project with Development Mode turned on or with a manually added SNAPSHOT version suffix to a KIE Server that is in production mode.

Commands:
Chapter 16. Fixed issues in Red Hat Process Automation Manager 7.13.5 Red Hat Process Automation Manager 7.13.5 provides increased stability and fixed issues listed in this section. 16.1. Business Central Cannot clone project by ssh when business central is integrated with LDAP [ RHPAM-4478 ] System error occurs when you access the Form asset or the Task form which have the listbox component [ RHPAM-4778 ] Duplicate signals received [ RHPAM-4813 ] 16.2. Process engine Deadlock is happening on SessionInfo and ProcessInstanceInfo tables [ RHPAM-4759 ] NPE occurs while parsing BPMN process after modifying from RHPAM 7.13.2 web designer [ RHPAM-4801 ] Timers not removed from session and TimerMappingInfo when jobHandle is not found [ RHPAM-4835 ] Duplicate timer created for Task SLA Due date with AsyncMode env setting [ RHPAM-4836 ] 16.3. KIE Server Backport DROOLS-7014 to Red Hat Decision Manager libraries [ RHDM-2006 ] An immutable KIE container is not deployed with auto scan in SpringBoot kie-server after upgrading to 7.13.1 [ RHPAM-4800 ] Exclusion on kie-server affects custom endpoints [ RHPAM-4876 ] 16.4. Decision engine Coercion from interger literal to BigDecimal bind variable [ RHDM-1991 ] Behavior of multiple updates in executable model is different from non-executable model [ RHDM-1993 ] Performance degradation when increasing concurrency of rule execution in multi threads [ RHDM-1994 ] Non-matching rule fires randomly and results in infinite-loop [ RHDM-2007 ] The Drools executable-model fails with BigDecimal coercion for method arguments [ RHDM-2014 ] EXISTS and NOT do not work correctly with multiple constraints with BigDecimal [ RHDM-2016 ] Drools executable-model fails with a bind variable to a calculation result of int and BigDecimal [ RHDM-2020 ]

Commands:
Chapter 250. Openshift Builds Component Available as of Camel version 2.17 The Kubernetes Builds component is one of Kubernetes Components which provides a producer to execute kubernetes build operations. 250.1. Component Options The Openshift Builds component has no options. 250.2. Endpoint Options The Openshift Builds endpoint is configured using URI syntax: with the following path and query parameters: 250.2.1. Path Parameters (1 parameters): Name Description Default Type masterUrl Required Kubernetes API server URL String 250.2.2. Query Parameters (20 parameters): Name Description Default Type apiVersion (producer) The Kubernetes API Version to use String dnsDomain (producer) The dns domain, used for ServiceCall EIP String kubernetesClient (producer) Default KubernetesClient to use if provided KubernetesClient operation (producer) Producer operation to do on Kubernetes String portName (producer) The port name, used for ServiceCall EIP String portProtocol (producer) The port protocol, used for ServiceCall EIP tcp String connectionTimeout (advanced) Connection timeout in milliseconds to use when making requests to the Kubernetes API server. Integer synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean caCertData (security) The CA Cert Data String caCertFile (security) The CA Cert File String clientCertData (security) The Client Cert Data String clientCertFile (security) The Client Cert File String clientKeyAlgo (security) The Key Algorithm used by the client String clientKeyData (security) The Client Key data String clientKeyFile (security) The Client Key file String clientKeyPassphrase (security) The Client Key Passphrase String oauthToken (security) The Auth Token String password (security) Password to connect to Kubernetes String trustCerts (security) Define if the certs we used are trusted anyway or not Boolean username (security) Username to connect to Kubernetes String 250.3. Openstack Component Available as of Camel 2.19 The openstack component is a component for managing your OpenStack applications. Maven users will need to add the following dependency to their pom.xml for this component: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-openstack</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> OpenStack service Camel Component Description OpenStack Cinder openstack-cinder Component to maintain OpenStack cinder. OpenStack Glance openstack-glance Component to maintain OpenStack glance. OpenStack Keystone openstack-keystone Component to maintain OpenStack keystone. OpenStack Neutron openstack-neutron Component to maintain OpenStack neutron. OpenStack Nova openstack-nova Component to maintain OpenStack nova. OpenStack Swift openstack-swift Component to maintain OpenStack swift.

Commands:
openshift-builds:masterUrl
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-openstack</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>
Chapter 11. steps 11.1. Enabling the Red Hat Virtualization Manager Repositories Register the system with Red Hat Subscription Manager, attach the Red Hat Virtualization Manager subscription, and enable Manager repositories. Procedure Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted: Note If you are using an IPv6 network, use an IPv6 transition mechanism to access the Content Delivery Network and subscription manager. Find the Red Hat Virtualization Manager subscription pool and record the pool ID: Use the pool ID to attach the subscription to the system: Note To view currently attached subscriptions: To list all enabled repositories: Configure the repositories: Enable the pki-deps module. Enable version 12 of the postgresql module. Synchronize installed packages to update them to the latest available versions. Additional resources For information on modules and module streams, see the following sections in Installing , managing , and removing user-space components Module streams Selecting a stream before installation of packages Resetting module streams Switching to a later stream Learn to create and manage Red Hat Gluster Storage using the Administration Portal in Managing Red Hat Gluster Storage using the RHV Administration Portal . Learn to create and manage virtual machines in the Red Hat Virtualization Virtual Machine Management Guide . Review the RHHI for Virtualization documentation on the Red Hat Customer Portal.

Commands:
subscription-manager register
subscription-manager list --available
subscription-manager attach --pool=pool_id
subscription-manager list --consumed
yum repolist
subscription-manager repos --disable='*' --enable=rhel-8-for-x86_64-baseos-rpms --enable=rhel-8-for-x86_64-appstream-rpms --enable=rhv-4.4-manager-for-rhel-8-x86_64-rpms --enable=fast-datapath-for-rhel-8-x86_64-rpms --enable=jb-eap-7.4-for-rhel-8-x86_64-rpms --enable=openstack-16.2-cinderlib-for-rhel-8-x86_64-rpms --enable=rhceph-4-tools-for-rhel-8-x86_64-rpms
yum module -y enable pki-deps
yum module -y enable postgresql:12
yum distro-sync