mtpti5iD/redhat-docs_dataset huggingface dataset:
5.6.3. Removing a Member from a Failover Domain To remove a member from a failover domain, follow these steps: At the left frame of the the Cluster Configuration Tool , click the failover domain that you want to change (listed under Failover Domains ). At the bottom of the right frame (labeled Properties ), click the Edit Failover Domain Properties button. Clicking the Edit Failover Domain Properties button causes the Failover Domain Configuration dialog box to be displayed ( Figure 5.10, " Failover Domain Configuration : Configuring a Failover Domain" ). At the Failover Domain Configuration dialog box, in the Member Node column, click the node name that you want to delete from the failover domain and click the Remove Member from Domain button. Clicking Remove Member from Domain removes the node from the Member Node column. Repeat this step for each node that is to be deleted from the failover domain. (Nodes must be deleted one at a time.) When finished, click Close . At the Cluster Configuration Tool , perform one of the following actions depending on whether the configuration is for a new cluster or for one that is operational and running: New cluster - If this is a new cluster, choose File => Save to save the changes to the cluster configuration. Running cluster - If this cluster is operational and running, and you want to propagate the change immediately, click the Send to Cluster button. Clicking Send to Cluster automatically saves the configuration change. If you do not want to propagate the change immediately, choose File => Save to save the changes to the cluster configuration.

Commands:
7.124. mcelog 7.124.1. RHBA-2015:1303 - mcelog bug fix and enhancement update Updated mcelog packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The mcelog packages contain a daemon that collects and decodes Machine Check Exception (MCE) data on AMD64 and Intel 64 machines. Note The mcelog packages have been upgraded to upstream version 109, which provides a number of bug fixes and enhancements over the version. Notably, mcelog now supports Intel Core i7 CPU architectures. (BZ# 1145371 ) Users of mcelog are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 10. About Red Hat Process Automation Manager Red Hat Process Automation Manager is the Red Hat middleware platform for creating business automation applications and microservices. It enables enterprise business and IT users to document, simulate, manage, automate, and monitor business processes and policies. It is designed to empower business and IT users to collaborate more effectively, so business applications can be changed easily and quickly. The product is made up of Business Central and KIE Server. KIE Server is the server where rules and other artifacts are executed. It is used to instantiate and execute rules and solve planning problems. KIE Server provides the runtime environment for business assets and accesses the data stored in the assets repository (knowledge store). Business Central is the graphical user interface where you create and manage business rules that KIE Server executes. It enables you to perform the following tasks: Create, manage, and edit your rules, processes, and related assets. Manage connected KIE Server instances and their KIE containers (deployment units). Execute runtime operations against processes and tasks in KIE Server instances connected to Business Central. Business Central is also available as a standalone JAR file. You can use the Business Central standalone JAR file to run Business Central without needing to deploy it to an application server. Red Hat JBoss Enterprise Application Platform (Red Hat JBoss EAP) 7.4 is a certified implementation of the Java Enterprise Edition 8 (Java EE 8) full and web profile specifications. Red Hat JBoss EAP provides preconfigured options for features such as high availability, clustering, messaging, and distributed caching. It also enables users to write, deploy, and run applications using the various APIs and services that Red Hat JBoss EAP provides. The instructions in this document explain how to install Red Hat Process Automation Manager in a Red Hat JBoss EAP 7.4 server instance. For instructions on how to install Red Hat Process Automation Manager in other environments, see the following documents: Installing and configuring KIE Server on IBM WebSphere Application Server Installing and configuring KIE Server on Oracle WebLogic Server Deploying an Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform 4 using Operators Deploying an Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform 3 using templates For information about supported components, see the following documents: What is the mapping between Red Hat Process Automation Manager and the Maven library version? Red Hat Process Automation Manager 7 Supported Configurations

Commands:
10.8. Preparser If it is desirable to manipulate incoming queries prior to being handled by Teiid logic, then a custom pre-parser can be installed. Use the PreParser interface provided in the org.teiid.api jar to plug-in a pre-parser for the Teiid engine. See Setting up the build environment to start development. import org.teiid.PreParser; ... package com.something; public class CustomPreParser implements PreParser { @Override public String preParse(String command, CommandContext context) { //manipulate the command } } , build a JAR archive with above implementation class and create a file named org.teiid.PreParser in the META-INF/services directory with these contents: com.something.CustomPreParser The JAR has now been built. Deploy it in the JBoss AS as a module under jboss-as/modules directory. Now create a module: Create a directory called jboss-as/modules/com/something/main. In it create a "module.xml" file with these contents: <?xml version="1.0" encoding="UTF-8"?> <module xmlns="urn:jboss:module:1.0" name="com.something"> <resources> <resource-root path="something.jar" /> </resources> <dependencies> <module name="javax.api"/> <module name="javax.resource.api"/> <module name="org.jboss.teiid.common-core"/> <module name="org.jboss.teiid.teiid-api" /> </dependencies> </module> Copy the jar file under this same directory. Make sure you add any additional dependencies if required by your implementation class under dependencies. Use the command line interface or modify the configuration to set the preparser-module in the Teiid subsystem configuration to the appropriate module name. Restart the server Important Development Considerations Changing the incoming query to a different type of statement is not recommended as are any modifications to the number or types of projected symbols.

Commands:
import org.teiid.PreParser; package com.something; public class CustomPreParser implements PreParser { @Override public String preParse(String command, CommandContext context) { //manipulate the command } }
com.something.CustomPreParser
<?xml version="1.0" encoding="UTF-8"?> <module xmlns="urn:jboss:module:1.0" name="com.something"> <resources> <resource-root path="something.jar" /> </resources> <dependencies> <module name="javax.api"/> <module name="javax.resource.api"/> <module name="org.jboss.teiid.common-core"/> <module name="org.jboss.teiid.teiid-api" /> </dependencies> </module>
Chapter 26. Monitoring Stratis file systems As a Stratis user, you can view information about Stratis volumes on your system to monitor their state and free space. Important Stratis is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview . 26.1. Displaying information about Stratis volumes You can lists statistics about your Stratis volumes, such as the total, used, and free size or file systems and block devices belonging to a pool, by using the stratis utility. Standard Linux utilities such as df report the size of the XFS file system layer on Stratis, which is 1 TiB. This is not useful information, because the actual storage usage of Stratis is less due to thin provisioning, and also because Stratis automatically grows the file system when the XFS layer is close to full. Important Regularly monitor the amount of data written to your Stratis file systems, which is reported as the Total Physical Used value. Make sure it does not exceed the Total Physical Size value. Prerequisites Stratis is installed. See Installing Stratis . The stratisd service is running. Procedure To display information about all block devices used for Stratis on your system: To display information about all Stratis pools on your system: To display information about all Stratis file systems on your system: Additional resources stratis(8) man page on your system 26.2. Viewing a Stratis pool by using the web console You can use the web console to view an existing Stratis pool and the file systems it contains. Prerequisites You have installed the RHEL 8 web console. You have enabled the cockpit service. Your user account is allowed to log in to the web console. For instructions, see Installing and enabling the web console . The stratisd service is running. You have an existing Stratis pool. Procedure Log in to the RHEL 8 web console. Click Storage . In the Storage table, click the Stratis pool you want to view. The Stratis pool page displays all the information about the pool and the file systems that you created in the pool.

Commands:
stratis blockdev Pool Name Device Node Physical Size State Tier my-pool /dev/sdb 9.10 TiB In-use Data
stratis pool Name Total Physical Size Total Physical Used my-pool 9.10 TiB 598 MiB
stratis filesystem Pool Name Name Used Created Device my-pool my-fs 546 MiB Nov 08 2018 08:03 /dev/stratis/ my-pool/my-fs
Chapter 3. Disabling the hot corner functionality on GNOME Shell The GNOME environment provides the hot corner functionality, which is enabled by default. This means that when you move the cursor to the area of the upper-left corner and push the cursor to the screen corner, the Activities Overview menu opens automatically. However, you may want to disable this feature to not open Activities Overview unintentionally. 3.1. Disabling hot corner using Settings To disable the hot corner functionality using the Settings application, follow this procedure. Note This procedure disables the hot corner functionality for a single user. Procedure Open the Settings application by clicking the gear button. In the Settings application, go to Multitasking . In the General section, disable the Hot Corner button. Disabling hot corner using the Settings application 3.2. Disabling hot corner using gsettings To disable the hot corner functionality using the gsettings command-line utility, follow this procedure. Procedure Disable the hot corner feature: Verification Optionally, verify that the hot corner feature is disabled: 3.3. Disabling the hot corner functionality for all users To disable the hot corner functionality for all users, you need to create a dconf profile. Procedure Create the user profile in the /etc/dconf/profile/user file. Create a file in the /etc/dconf/db/local.d/ directory, for example /etc/dconf/db/local.d/00-interface , with the following content: Create a file in the /etc/dconf/db/local.d/locks directory, for example /etc/dconf/db/local.d/locks/00-interface , with the following content: The configuration file locks down the /org/gnome/desktop/interface/enable-hot-corners key for all users. This key controls whether the hot corner is enabled. Update the system databases for the changes to take effect. Ensure that all users log out. The changes take effect when users log back in.

Commands:
gsettings set org.gnome.desktop.interface enable-hot-corners false
gsettings get org.gnome.desktop.interface enable-hot-corners false
user-db:user system-db:local
Specify the dconf path GSettings key names and their corresponding values enable-hot-corners='FALSE'
Prevent users from changing values for the following keys: /org/gnome/desktop/interface/enable-hot-corners
dconf update
Chapter 3. Using Red Hat Single Sign-On with Spring Boot Red Hat Single Sign-On client adapters are libraries that make it very easy to secure applications and services with Red Hat Single Sign-On. You can use the Keycloak Spring Boot adapter to secure your Spring Boot project. 3.1. Using Red Hat Single Sign-On with Spring Boot Container To secure a Spring Boot application, add the Keycloak Spring Boot adapter JAR to your project. The Keycloak Spring Boot adapter takes advantage of Spring Boot's autoconfiguration feature so all you need to do is add the Keycloak Spring Boot starter to your project. Procedure To manually add the Keycloak Spring Boot starter, add the following to your project's pom.xml . Add the Adapter BOM dependency. Configure your Spring Boot project to use Keycloak. Instead of a keycloak.json file, you can configure the realm for the Spring Boot Keycloak adapter using the normal Spring Boot configuration. For example, add following configuration to src/main/resources/application.properties file. You can disable the Keycloak Spring Boot Adapter (for example in tests) by setting keycloak.enabled = false . To configure a Policy Enforcer, unlike keycloak.json , policy-enforcer-config must be used instead of just policy-enforcer . Specify the Java EE security configuration in the web.xml . The Spring Boot Adapter will set the login-method to KEYCLOAK and configure the security-constraints at the time of startup. An example configuration is given below. Note: If you plan to deploy your Spring Application as a WAR then do not use the Spring Boot Adapter. Use the dedicated adapter for the application server or servlet container you are using. Your Spring Boot should also contain a web.xml file.

Commands:
<dependency> <groupId>org.keycloak</groupId> <artifactId>keycloak-spring-boot-starter</artifactId> </dependency>
<dependencyManagement> <dependencies> <dependency> <groupId>org.keycloak.bom</groupId> <artifactId>keycloak-adapter-bom</artifactId> <version>3.4.17.Final-redhat-00001</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement>
keycloak.realm = demorealm keycloak.auth-server-url = http://127.0.0.1:8080/auth keycloak.ssl-required = external keycloak.resource = demoapp keycloak.credentials.secret = 11111111-1111-1111-1111-111111111111 keycloak.use-resource-role-mappings = true
keycloak.securityConstraints[0].authRoles[0] = admin keycloak.securityConstraints[0].authRoles[1] = user keycloak.securityConstraints[0].securityCollections[0].name = insecure stuff keycloak.securityConstraints[0].securityCollections[0].patterns[0] = /insecure keycloak.securityConstraints[1].authRoles[0] = admin keycloak.securityConstraints[1].securityCollections[0].name = admin stuff keycloak.securityConstraints[1].securityCollections[0].patterns[0] = /admin
1.3. Setting Up a Typing Break Typing for a long period of time can be not only tiring, but it can also increase the risk of serious health problems, such as carpal tunnel syndrome. One way of preventing this is to configure the system to enforce typing breaks. To do so, select System Preferences Keyboard from the panel, click the Typing Break tab, and select the Lock screen to enforce typing break check box. Figure 1.8. Typing Break Properties To increase or decrease the allowed typing time before the break is enforced, click the up or down button to the Work interval lasts label respectively. You can do the same with the Break interval lasts setting to alter the length of the break itself. Finally, select the Allow postponing of breaks check box if you want to be able to delay the break in case you need to finish the work. The changes take effect immediately. Figure 1.9. Taking a break time you reach the time limit, you will be presented with a screen advising you to take a break, and a clock displaying the remaining time. If you have enabled it, the Postpone Break button will be located at the bottom right corner of the screen.

Commands:
Chapter 7. Reviewing monitoring dashboards OpenShift Container Platform 4.9 provides a comprehensive set of monitoring dashboards that help you understand the state of cluster components and user-defined workloads. Use the Administrator perspective to access dashboards for the core OpenShift Container Platform components, including the following items: API performance etcd Kubernetes compute resources Kubernetes network resources Prometheus USE method dashboards relating to cluster and node performance Figure 7.1. Example dashboard in the Administrator perspective Use the Developer perspective to access Kubernetes compute resources dashboards that provide the following application metrics for a selected project: CPU usage Memory usage Bandwidth information Packet rate information Figure 7.2. Example dashboard in the Developer perspective Note In the Developer perspective, you can view dashboards for only one project at a time. 7.1. Reviewing monitoring dashboards as a cluster administrator In the Administrator perspective, you can view dashboards relating to core OpenShift Container Platform cluster components. Prerequisites You have access to the cluster as a user with the cluster-admin role. Procedure In the Administrator perspective in the OpenShift Container Platform web console, navigate to Observe Dashboards . Choose a dashboard in the Dashboard list. Some dashboards, such as etcd and Prometheus dashboards, produce additional sub-menus when selected. Optional: Select a time range for the graphs in the Time Range list. Select a pre-defined time period. Set a custom time range by selecting Custom time range in the Time Range list. Input or select the From and To dates and times. Click Save to save the custom time range. Optional: Select a Refresh Interval . Hover over each of the graphs within a dashboard to display detailed information about specific items. 7.2. Reviewing monitoring dashboards as a developer Use the Developer perspective to view Kubernetes compute resources dashboards of a selected project. Prerequisites You have access to the cluster as a developer or as a user. You have view permissions for the project that you are viewing the dashboard for. Procedure In the Developer perspective in the OpenShift Container Platform web console, navigate to Observe Dashboard . Select a project from the Project: drop-down list. Select a dashboard from the Dashboard drop-down list to see the filtered metrics. Note All dashboards produce additional sub-menus when selected, except Kubernetes / Compute Resources / Namespace (Pods) . Optional: Select a time range for the graphs in the Time Range list. Select a pre-defined time period. Set a custom time range by selecting Custom time range in the Time Range list. Input or select the From and To dates and times. Click Save to save the custom time range. Optional: Select a Refresh Interval . Hover over each of the graphs within a dashboard to display detailed information about specific items. Additional resources Monitoring project and application metrics using the Developer perspective 7.3. steps Accessing third-party UIs

Commands:
Chapter 15. Unsubscribing developers from a service As an admin, you can unsubscribe developers from a service. You may need to do this for one specific developer, or for multiple developers, in the event of a service deprecation. 15.1. Unsubscribing a single developer from services Unsubscribe a single developer from a service they are subscribed to through the Admin Portal: In the Admin Portal's Dashboard, navigate to Audience > Accounts > Listing > [select an account] > Service Subscriptions . Select Unsubscribe for the service that you want to remove the developer from. 15.2. Unsubscribing multiple developers from services Perform a bulk action to unsubscribe multiple developers from a deprecated or deleted service: Note This method only applies to services that have been deleted or suspended. You cannot perform a bulk unsubscription action on active services. In the Dashboard, navigate to: Audience > Accounts > Subscriptions . Do bulk state change. Using the service dropdown menu, identify the service from which you want to unsubscribe developers. Using the checkboxes on the left, select the developers you want to unsubscribe. Select Change State > Suspend to suspend the selected developer subscriptions. Remember that service plans need to be enabled.

Commands:
Chapter 20. Configuring Pre-Acknowledgments Jakarta Messaging specifies three acknowledgement modes: AUTO_ACKNOWLEDGE CLIENT_ACKNOWLEDGE DUPS_OK_ACKNOWLEDGE In some cases you can afford to lose messages in the event of a failure, so it would make sense to acknowledge the message on the server before delivering it to the client. This extra mode is supported by JBoss EAP messaging and is called pre-acknowledge mode. The disadvantage of pre-acknowledging on the server before delivery is that the message will be lost if the server's system crashes after acknowledging the message but before it is delivered to the client. In that case, the message is lost and will not be recovered when the system restarts. Depending on your messaging case, pre-acknowledge mode can avoid extra network traffic and CPU usage at the cost of coping with message loss. An example use case for pre-acknowledgement is for stock price update messages. With these messages, it might be reasonable to lose a message in event of a crash since the price update message will arrive soon, overriding the price. Note If you use pre-acknowledge mode, you will lose transactional semantics for messages being consumed since they are being acknowledged first on the server, not when you commit the transaction. 20.1. Configuring the Server A connection factory can be configured to use pre-acknowledge mode by setting its pre-acknowledge attribute to true using the management CLI as below: 20.2. Configuring the Client Pre-acknowledge mode can be configured in the client's JNDI context environment, for example, in the jndi.properties file: Alternatively, to use pre-acknowledge mode using the Jakarta Messaging API, create a Jakarta Messaging Session with the ActiveMQSession.PRE_ACKNOWLEDGE constant. // messages will be acknowledge on the server *before* being delivered to the client Session session = connection.createSession(false, ActiveMQJMSConstants.PRE_ACKNOWLEDGE);

Commands:
/subsystem=messaging-activemq/server=default/connection-factory=RemoteConnectionFactory:write-attribute(name=pre-acknowledge,value=true)
java.naming.factory.initial=org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory connection.ConnectionFactory=tcp://localhost:8080?preAcknowledge=true
// messages will be acknowledge on the server *before* being delivered to the client Session session = connection.createSession(false, ActiveMQJMSConstants.PRE_ACKNOWLEDGE);