mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Package Namespace Change for JBoss EAP 8.0 This section provides additional information for the package namespace changes in JBoss EAP 8.0. JBoss EAP 8.0 provides full support for Jakarta EE 10 and many other implementations of the Jakarta EE 10 APIs. An important change supported by Jakarta EE 10 for JBoss EAP 8.0 is the package namespace change. 3.1. javax to jakarta Namespace change A key difference between Jakarta EE 8 and EE 10 is the renaming of the EE API Java packages from javax.* to jakarta.* . This follows the move of Java EE to the Eclipse Foundation and the establishment of Jakarta EE. Adapting to this namespace change is the biggest task of migrating an application from JBoss EAP 7 to JBoss EAP 8. To migrate applications to Jakarta EE 10, you must complete the following steps: Update any import statements or other source code uses of EE API classes from the javax package to the jakarta package. Update the names of any EE-specified system properties or other configuration properties that begin with javax to begin with jakarta . For any application-provided implementations of EE interfaces or abstract classes that are bootstrapped using the java.util.ServiceLoader mechanism, change the name of the resource that identifies the implementation class from META-INF/services/javax.[rest_of_name] to META-INF/services/jakarta.[rest_of_name] . Note The Red Hat Migration Toolkit can assist in updating the namespaces in the application source code. For more information, see How to use Red Hat Migration Toolkit for Auto-Migration of an Application to the Jakarta EE 10 Namespace . In cases where source code migration is not an option, the Open Source Eclipse Transformer project provides bytecode transformation tooling to transform existing Java archives from the javax namespace to the jakarta namespace. Note This change does not affect javax packages that are part of Java SE. Additional resources For more information, see The javax to jakarta Package Namespace Change . Revised on 2024-02-21 14:02:49 UTC

Commands:
14.12.3. Dumping Storage Volume Information to an XML File vol-dumpxml --pool pool-or-uuid vol-name-or-key-or-path command takes the volume information as an XML dump to a specified file. This command requires a --pool pool-or-uuid , which is the name or UUID of the storage pool the volume is in. vol-name-or-key-or-path is the name or key or path of the volume to place the resulting XML file.

Commands:
18.5.3. DMZs and IPTables You can create iptables rules to route traffic to certain machines, such as a dedicated HTTP or FTP server, in a demilitarized zone ( DMZ ). A DMZ is a special local subnetwork dedicated to providing services on a public carrier, such as the Internet. For example, to set a rule for routing incoming HTTP requests to a dedicated HTTP server at 10.0.4.2 (outside of the 192.168.1.0/24 range of the LAN), NAT uses the PREROUTING table to forward the packets to the appropriate destination: With this command, all HTTP connections to port 80 from outside of the LAN are routed to the HTTP server on a network separate from the rest of the internal network. This form of network segmentation can prove safer than allowing HTTP connections to a machine on the network. If the HTTP server is configured to accept secure connections, then port 443 must be forwarded as well.

Commands:
iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination 10.0.4.2:80
Chapter 13. Removing The steps for removing the Red Hat build of OpenTelemetry from an OpenShift Container Platform cluster are as follows: Shut down all Red Hat build of OpenTelemetry pods. Remove any OpenTelemetryCollector instances. Remove the Red Hat build of OpenTelemetry Operator. 13.1. Removing an OpenTelemetry Collector instance by using the web console You can remove an OpenTelemetry Collector instance in the Administrator view of the web console. Prerequisites You are logged in to the web console as a cluster administrator with the cluster-admin role. For Red Hat OpenShift Dedicated, you must be logged in using an account with the dedicated-admin role. Procedure Go to Operators Installed Operators Red Hat build of OpenTelemetry Operator OpenTelemetryInstrumentation or OpenTelemetryCollector . To remove the relevant instance, select Delete ... Delete . Optional: Remove the Red Hat build of OpenTelemetry Operator. 13.2. Removing an OpenTelemetry Collector instance by using the CLI You can remove an OpenTelemetry Collector instance on the command line. Prerequisites An active OpenShift CLI ( oc ) session by a cluster administrator with the cluster-admin role. Tip Ensure that your OpenShift CLI ( oc ) version is up to date and matches your OpenShift Container Platform version. Run oc login : USD oc login --username=<your_username> Procedure Get the name of the OpenTelemetry Collector instance by running the following command: USD oc get deployments -n <project_of_opentelemetry_instance> Remove the OpenTelemetry Collector instance by running the following command: USD oc delete opentelemetrycollectors <opentelemetry_instance_name> -n <project_of_opentelemetry_instance> Optional: Remove the Red Hat build of OpenTelemetry Operator. Verification To verify successful removal of the OpenTelemetry Collector instance, run oc get deployments again: USD oc get deployments -n <project_of_opentelemetry_instance> 13.3. Additional resources Deleting Operators from a cluster Getting started with the OpenShift CLI

Commands:
oc login --username=<your_username>
oc get deployments -n <project_of_opentelemetry_instance>
oc delete opentelemetrycollectors <opentelemetry_instance_name> -n <project_of_opentelemetry_instance>
oc get deployments -n <project_of_opentelemetry_instance>
Chapter 11. Executing a business process in Business Central After you build and deploy the project that contains your business process, you can execute the defined functionality for the business process. As an example, this procedure uses the Mortgage_Process sample project in Business Central. In this scenario, you input data into a mortgage application form acting as the mortgage broker. The MortgageApprovalProcess business process runs and determines whether or not the applicant has offered an acceptable down payment based on the decision rules defined in the project. The business process either ends the rule testing or requests that the applicant increase the down payment to proceed. If the application passes the business rule testing, the bank approver reviews the application and either approves or denies the loan. Prerequisites KIE Server is deployed and connected to Business Central. For more information about KIE Server configuration, see Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 . Procedure In Business Central, go to Menu Projects and select a space. The default space is MySpace. In the upper-right corner of the window, click the arrow to Add Project and select Try Samples . Select the Mortgage_Process sample and click Ok . On the project page, select Mortgage_Process . On the Mortgage_Process page, click Build . After the project has built, click Deploy . Go to Menu Manage Process Definitions . Click anywhere in the MortgageApprovalProcess row to view the process details. Click the Diagram tab to view the business process diagram in the editor. Click New Process Instance to open the Application form and input the following values into the form fields: Down Payment : 30000 Years of amortization : 10 Name : Ivo Annual Income : 60000 SSN : 123456789 Age of property : 8 Address of property : Brno Locale : Rural Property Sale Price : 50000 Click Submit to start a new process instance. After starting the process instance, the Instance Details view opens. Click the Diagram tab to view the process flow within the process diagram. The state of the process is highlighted as it moves through each task. Click Menu Manage Tasks . For this example, the user or users working on the corresponding tasks are members of the following groups: approver : For the Qualify task broker : For the Correct Data and Increase Down Payment tasks manager : For the Final Approval task As the approver, review the Qualify task information, click Claim and then Start to start the task, and then select Is mortgage application in limit? and click Complete to complete the task flow. In the Tasks page, click anywhere in the Final Approval row to open the Final Approval task. Click Claim to claim responsibility for the task, and click Complete to finalize the loan approval process. Note The Save and Release buttons are only used to either pause the approval process and save the instance if you are waiting on a field value, or to release the task for another user to modify.

Commands:
2.34. RHEA-2011:0608 - new package: python-rhsm A new python-rhsm package is now available for Red Hat Enterprise Linux 6. The new python-rhsm package provides access to the Subscription Management tools. It helps users to understand specific products which are installed on their machines and specific subscriptions which their machines consume. This enhancement update adds a new python-rhsm package to Red Hat Enterprise Linux 6. (BZ# 661863 ) All users requiring python-rhsm should install this newly-released package, which adds this enhancement.

Commands:
3.7. Turning on Packet Forwarding and Nonlocal Binding In order for the Keepalived service to forward network packets properly to the real servers, each router node must have IP forwarding turned on in the kernel. Log in as root and change the line which reads net.ipv4.ip_forward = 0 in /etc/sysctl.conf to the following: The changes take effect when you reboot the system. Load balancing in HAProxy and Keepalived at the same time also requires the ability to bind to an IP address that are nonlocal , meaning that it is not assigned to a device on the local system. This allows a running load balancer instance to bind to an IP that is not local for failover. To enable, edit the line in /etc/sysctl.conf that reads net.ipv4.ip_nonlocal_bind to the following: The changes take effect when you reboot the system. To check if IP forwarding is turned on, issue the following command as root : /usr/sbin/sysctl net.ipv4.ip_forward To check if nonlocal binding is turned on, issue the following command as root : /usr/sbin/sysctl net.ipv4.ip_nonlocal_bind If both the above commands return a 1 , then the respective settings are enabled.

Commands:
net.ipv4.ip_forward = 1
net.ipv4.ip_nonlocal_bind = 1
Chapter 2. Sizing requirements for Red Hat Developer Hub Scalability of Red Hat Developer Hub requires significant resource allocation. The following table lists the sizing requirements for installing and running Red Hat Developer Hub, including both the Developer Hub application and Developer Hub database components. Table 2.1. Recommended sizing for running Red Hat Developer Hub Components Red Hat Developer Hub application Red Hat Developer Hub database Central Processing Unit (CPU) 4 vCPU 2 vCPU Memory 16 GB 8 GB Storage size 2 GB 20 GB Replicas 2 or more 3 or more

Commands:
7.257. trace-cmd 7.257.1. RHBA-2013:0423 - trace-cmd bug fix and enhancement update Updated trace-cmd packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The trace-cmd packages contain a command-line tool that interfaces with the ftrace utility in the kernel. Bug Fixes BZ#746656 The trace-cmd extract command read a buffer multiple times even after an EOF condition. Consequently, the output of the trace-cmd command contained duplicate data. With this update, the trace-cmd utility has been modified to respect the EOF condition and avoid duplication of data in its output. BZ#879792 When using the latency tracer, the start_threads() function was not called. Calling the stop_threads() function without first calling start_threads() caused the trace-cmd record command to terminate with a segmentation fault because PIDs were not initialized. Consequently, the trace.dat file was not generated. With this update, stop_threads() is not called unless start_threads() is called first. As a result, the segmentation fault no longer occurs. Enhancement BZ# 838746 Previously, the trace-cmd record command was able to filter ftrace data based on a single PID only. With this update, multiple PIDs can be specified by using the "-P" option. Users of trace-cmd are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 2. Eclipse Temurin 11.0.20.1 release notes Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. Review the following release notes for an overview of the changes from the Eclipse Temurin 11.0.20.1 patch release. Note For all the other changes and security fixes, see OpenJDK 11.0.20.1 Released . Fixed Invalid CEN header error on valid .zip files OpenJDK 11.0.20 introduced additional validation checks on the ZIP64 fields of .zip files (JDK-8302483). However, these additional checks caused validation failures on some valid .zip files with the following error message: Invalid CEN header (invalid zip64 extra data field size) . To fix this issue, OpenJDK 11.0.20.1 supports zero-length headers and the additional padding that some ZIP64 creation tools produce. From OpenJDK 11.0.20 onward, you can disable these checks by setting the jdk.util.zip.disableZip64ExtraFieldValidation system property to true . See JDK-8313765 (JDK Bug System) Increased default value of jdk.jar.maxSignatureFileSize system property OpenJDK 11.0.20 introduced a jdk.jar.maxSignatureFileSize system property for configuring the maximum number of bytes that are allowed for the signature-related files in a Java archive (JAR) file ( JDK-8300596 ). By default, the jdk.jar.maxSignatureFileSize property was set to 8000000 bytes (8 MB), which was too small for some JAR files. OpenJDK 11.0.20.1 increases the default value of the jdk.jar.maxSignatureFileSize property to 16000000 bytes (16 MB). See JDK-8313216 (JDK Bug System) Fixed NullPointerException when handling null addresses In OpenJDK 11.0.20, when the serviceability agent encountered null addresses while generating thread dumps, the serviceability agent produced a NullPointerException . OpenJDK 11.0.20.1 handles null addresses appropriately. See JDK-8243210 (JDK Bug System)

Commands:
Chapter 7. Catalog exclusion by labels or expressions You can exclude catalogs by using match expressions on metadata with the NotIn or DoesNotExist operators. The following CRs add an example.com/testing label to the unwanted-catalog-1 and unwanted-catalog-2 cluster catalogs: Example cluster catalog CR apiVersion: olm.operatorframework.io/v1 kind: ClusterCatalog metadata: name: unwanted-catalog-1 labels: example.com/testing: "true" spec: source: type: Image image: ref: quay.io/example/content-management-a:latest Example cluster catalog CR apiVersion: olm.operatorframework.io/v1 kind: ClusterCatalog metadata: name: unwanted-catalog-2 labels: example.com/testing: "true" spec: source: type: Image image: ref: quay.io/example/content-management-b:latest The following cluster extension CR excludes selection from the unwanted-catalog-1 catalog: Example cluster extension CR that excludes a specific catalog apiVersion: olm.operatorframework.io/v1 kind: ClusterExtension metadata: name: <example_extension> spec: namespace: <example_namespace> serviceAccount: name: <example_extension>-installer source: sourceType: Catalog catalog: packageName: <example_extension>-operator selector: matchExpressions: - key: olm.operatorframework.io/metadata.name operator: NotIn values: - unwanted-catalog-1 The following cluster extension CR selects from catalogs that do not have the example.com/testing label. As a result, both unwanted-catalog-1 and unwanted-catalog-2 are excluded from catalog selection. Example cluster extension CR that excludes catalogs with a specific label apiVersion: olm.operatorframework.io/v1 kind: ClusterExtension metadata: name: <example_extension> spec: namespace: <example_namespace> serviceAccount: name: <example_extension>-installer source: sourceType: Catalog catalog: packageName: <example_extension>-operator selector: matchExpressions: - key: example.com/testing operator: DoesNotExist

Commands:
apiVersion: olm.operatorframework.io/v1 kind: ClusterCatalog metadata: name: unwanted-catalog-1 labels: example.com/testing: "true" spec: source: type: Image image: ref: quay.io/example/content-management-a:latest
apiVersion: olm.operatorframework.io/v1 kind: ClusterCatalog metadata: name: unwanted-catalog-2 labels: example.com/testing: "true" spec: source: type: Image image: ref: quay.io/example/content-management-b:latest
apiVersion: olm.operatorframework.io/v1 kind: ClusterExtension metadata: name: <example_extension> spec: namespace: <example_namespace> serviceAccount: name: <example_extension>-installer source: sourceType: Catalog catalog: packageName: <example_extension>-operator selector: matchExpressions: - key: olm.operatorframework.io/metadata.name operator: NotIn values: - unwanted-catalog-1
apiVersion: olm.operatorframework.io/v1 kind: ClusterExtension metadata: name: <example_extension> spec: namespace: <example_namespace> serviceAccount: name: <example_extension>-installer source: sourceType: Catalog catalog: packageName: <example_extension>-operator selector: matchExpressions: - key: example.com/testing operator: DoesNotExist
Part V. Deprecated Functionality This part provides an overview of functionality that has been deprecated in all minor releases up to Red Hat Enterprise Linux 7.4. Deprecated functionality continues to be supported until the end of life of Red Hat Enterprise Linux 7. Deprecated functionality will likely not be supported in future major releases of this product and is not recommended for new deployments. For the most recent list of deprecated functionality within a particular major release, refer to the latest version of release documentation. Deprecated hardware components are not recommended for new deployments on the current or future major releases. Hardware driver updates are limited to security and critical fixes only. Red Hat recommends replacing this hardware as soon as reasonably feasible. A package can be deprecated and not recommended for further use. Under certain circumstances, a package can be removed from a product. Product documentation then identifies more recent packages that offer functionality similar, identical, or more advanced to the one deprecated, and provides further recommendations.

Commands:
2.4. Configuring Red Hat JBoss Data Grid for Authorization Authorization is configured at two levels: the cache container (CacheManager), and at the single cache. CacheManager The following is an example configuration for authorization at the CacheManager level: Example 2.4. CacheManager Authorization (Declarative Configuration) Each cache container determines: whether to use authorization. a class which will map principals to a set of roles. a set of named roles and the permissions they represent. You can choose to use only a subset of the roles defined at the container level. Roles Roles may be applied on a cache-per-cache basis, using the roles defined at the cache-container level, as follows: Example 2.5. Defining Roles Important Any cache that is intended to require authentication must have a listing of roles defined; otherwise authentication is not enforced as the no-anonymous policy is defined by the cache's authorization. Programmatic CacheManager Authorization (Library Mode) The following example shows how to set up the same authorization parameters for Library mode using programmatic configuration: Example 2.6. CacheManager Authorization Programmatic Configuration Important The REST protocol is not supported for use with authorization, and any attempts to access a cache with authorization enabled will result in a SecurityException . Report a bug

Commands:
<cache-container name="local" default-cache="default"> <security> <authorization> <identity-role-mapper /> <role name="admin" permissions="ALL"/> <role name="reader" permissions="READ"/> <role name="writer" permissions="WRITE"/> <role name="supervisor" permissions="ALL_READ ALL_WRITE"/> </authorization> </security> </cache-container>
<local-cache name="secured"> <security> <authorization roles="admin reader writer supervisor"/> </security> </local-cache>
GlobalConfigurationBuilder global = new GlobalConfigurationBuilder(); global .security() .authorization() .principalRoleMapper(new IdentityRoleMapper()) .role("admin") .permission(CachePermission.ALL) .role("supervisor") .permission(CachePermission.EXEC) .permission(CachePermission.READ) .permission(CachePermission.WRITE) .role("reader") .permission(CachePermission.READ); ConfigurationBuilder config = new ConfigurationBuilder(); config .security() .enable() .authorization() .role("admin") .role("supervisor") .role("reader");
probe::ioscheduler_trace.elv_issue_request Name probe::ioscheduler_trace.elv_issue_request - Fires when a request is Synopsis ioscheduler_trace.elv_issue_request Values rq_flags Request flags. disk_minor Disk minor number of request. disk_major Disk major no of request. elevator_name The type of I/O elevator currently enabled. rq Address of request. name Name of the probe point Description scheduled.

Commands:
Chapter 5. steps After completing the tutorial, consider the following steps: Explore the tutorial further. Use the MySQL command line client to add, modify, and remove rows in the database tables, and see the effect on the topics. Keep in mind that you cannot remove a row that is referenced by a foreign key. Plan a Debezium deployment. You can install Debezium in OpenShift or on Red Hat Enterprise Linux. For more information, see the following: Installing Debezium on OpenShift Installing Debezium on RHEL Revised on 2024-10-09 02:25:11 UTC

Commands: