mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 7. Using Redis Cache with dynamic plugins You can use the Redis cache store to improve RHDH performance and reliability. Plugins in RHDH receive dedicated cache connections, which are powered by Keyv. 7.1. Installing Redis Cache in Red Hat Developer Hub Prerequisites You have installed Red Hat Developer Hub by using either the Operator or Helm chart. You have an active Redis server. For more information on setting up an external Redis server, see the Redis official documentation . Procedure Add the following code to your app-config.yaml file: backend: cache: store: redis connection: redis://user:pass@cache.example.com:6379 useRedisSets: true 7.2. Configuring Redis Cache in Red Hat Developer Hub 7.2.1. useRedisSets The useRedisSets option lets you decide whether to use Redis sets for key management. By default, this option is set to true . When useRedisSets is enabled ( true ): A namespace for the Redis sets is created, and all generated keys are added to that namespace, enabling group management of the keys. When a key is deleted, it's removed from the main storage and the Redis set. When using the clear function to delete all keys, every key in the Redis set is checked for deletion, and the set itself is also removed. Note In high-performance scenarios, enabling useRedisSets can result in memory leaks. If you are running a high-performance application or service, you must set useRedisSets to false . When you set useRedisSets to false , the keys are handled individually and Redis sets are not utilized. This configuration might lead to performance issues in production when using the clear function, as it requires iterating over all keys for deletion.

Commands:
backend: cache: store: redis connection: redis://user:pass@cache.example.com:6379 useRedisSets: true
35.4. Examining Log Files Log Viewer can be configured to display an alert icon beside lines that contain key alert words and a warning icon beside lines that contain key warning words. To add alerts words, select Edit => Preferences from the pulldown menu, and click on the Alerts tab. Click the Add button to add an alert word. To delete an alert word, select the word from the list, and click Delete . The alert icon is displayed to the left of the lines that contains any of the alert words. Figure 35.4. Alerts To add warning words, select Edit => Preferences from the pull-down menu, and click on the Warnings tab. Click the Add button to add a warning word. To delete a warning word, select the word from the list, and click Delete . The warning icon is displayed to the left of the lines that contains any of the warning words. Figure 35.5. Warning

Commands:
4.38. ctdb 4.38.1. RHBA-2011:1574 - ctdb bug fix and enhancement update Updated ctdb packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The ctdb packages provide a clustered database based on Samba's Trivial Database (TDB) used to store temporary data. The ctdb packages have been upgraded to upstream version 1.0.114, which provides a number of bug fixes over the version. (BZ# 701944 ) Bug Fix BZ# 728545 Prior to this update, the ctdb daemon leaked a file descriptor to anon_inodefs. This update modifies ctdb so that this file discriptor can no longer leak. Enhancement BZ# 672641 This update adds support for Clustered Samba on top of GFS2 as a Technology Preview. All users of ctdb are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 28. Billing API The Billing API provides a way to automate common billing processes. All the endpoints of the Billing API can be found in the Admin Portal under Documentation (?) > 3scale API Docs > Billing API . The Billing API requires a valid access token which meets the following requirements: it should belong to either an admin user of the provider account, or a member user with "Billing" permissions. it should include "Billing API" scope. Note that when an invoice ID is required as a parameter, it refers to the invoice ID, and not the Friendly invoice ID. The XML response of the API endpoints is mostly self-explanatory, and the fields of the Invoice represent the same information as in the web and PDF representation. Some notable fields of the response: creation_type : can have the following values: 'manual' for invoices created manually or 'background' for invoices created by the 3scale automated billing process. provider : the details of the API provider (the admin account), corresponds to the Issued by section of the invoice. buyer : the details of the developer account, corresponds to the Issued to section of the invoice. The XML representation of the invoice also includes the list of Line Items under the line-items field. For some line items, typically the ones created automatically, apart from the expected name, description, quantity and cost price, you can see the following: type : the type of the line item, can have the following values: LineItem::PlanCost - for line items for fixed plan costs. LineItem::VariableCost - for line items for variable costs. metric_id : for variable costs line items - the ID of the metric that the cost is associated with. contract_id : the ID of the service or application that the cost is associated with.

Commands:
Part V. Using the Showcase application for case management As a case worker or process administrator, you can use the Showcase application to manage and monitor case management applications while case work is carried out in Business Central. Case management differs from business process management (BPM) in that it focuses on the actual data being handled throughout the case and less on the sequence of steps taken to complete a goal. Case data is the most important piece of information in case handling, while business context and decision-making is in the hands of the human case worker. Use this document to install the Showcase application and start a case instance using the IT_Orders sample case management project in Business Central. Use Business Central to complete the tasks required to complete an IT Orders case. Prerequisites Red Hat JBoss Enterprise Application Platform 7.4 is installed. For installation information, see Red Hat JBoss Enterprise Application Platform 7.4 Installation Guide . Red Hat Process Automation Manager is installed on Red Hat JBoss EAP and configured with KIE Server. For more information see Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 . KieLoginModule is configured in standalone-full.xml . This is required to connect to KIE Server. For more information about configuring KIE Server, see Planning a Red Hat Process Automation Manager installation . Red Hat Process Automation Manager is running and you can log in to Business Central with a user that has both kie-server and user roles. For more information about roles, see Planning a Red Hat Process Automation Manager installation . The IT_Orders sample project has been imported in Business Central and deployed to KIE Server. For more information about case management, see Getting started with case management .

Commands:
1.2.5. Viewing Changes Viewing the Status To determine the current status of a working copy, change to the directory with the working copy and run the following command: svn status This displays information about all changes to the working copy ( A for a file that is scheduled for addition, D for a file that is scheduled for removal, M for a file that contains local changes, C for a file with unresolved conflicts, ? for a file that is not under revision control). Example 1.10. Viewing the status of a working copy Imagine that the directory with your working copy of a Subversion repository has the following contents: With the exception of ChangeLog , which is scheduled for addition to the Subversion repository, all files and directories within this directory are already under revision control. The TODO file, which is also under revision control, has been scheduled for removal and is no longer present in the working copy. The LICENSE file has been renamed to COPYING , and Makefile contains local changes. To display the status of such a working copy, type: Viewing Differences To view differences between a working copy and the checked out content, change to the directory with the working copy and run the following command: svn diff [ file ... ] This displays changes to all files in the working copy. If you are only interested in changes to a particular file, supply the file name on the command line. Example 1.11. Viewing changes to a working copy Imagine that the directory with your working copy of a Subversion repository has the following contents: All files in this directory are under revision control and Makefile contains local changes. To view these changes, type:

Commands:
project]USD ls AUTHORS ChangeLog COPYING doc INSTALL Makefile README src
project]USD svn status D LICENSE D TODO A ChangeLog A + COPYING M Makefile
project]USD ls AUTHORS ChangeLog COPYING CVS doc INSTALL Makefile README src
project]USD svn diff Makefile Index: Makefile =================================================================== --- Makefile (revision 1) +++ Makefile (working copy) @@ -153,7 +153,7 @@ -rmdir USD(man1dir) clean: - -rm -f USD(MAN1) + -rm -f USD(MAN1) USD(MAN7) %.1: %.pl USD(POD2MAN) --section=1 --release="Version USD(VERSION)" \
Chapter 6. Troubleshooting 6.1. About Troubleshooting Amazon EC2 EC2 provides an Alarm Status for each instance, indicating severe instance malfunction but the absence of such an alarm is no guarantee that the instance has started correctly and services are running properly. It is possible to use Amazon CloudWatch with its custom metric functionality to monitor instance services' health but use of an enterprise management solution is recommended. 6.2. Diagnostic Information In case of a problem being detected by the JBoss Operations Network, Amazon CloudWatch or manual inspection, common sources of diagnostic information are: /var/log also contains all the logs collected from machine startup, JBoss EAP, httpd and most other services. JBoss EAP log files can be found in /opt/rh/eap7/root/usr/share/wildfly/ . Access to these files is only available using an SSH session. See Getting Started with Amazon EC2 Linux Instances for more information about how to configure and establish an SSH session with an Amazon EC2 instance.

Commands:
Appendix A. Using your Red Hat subscription Red Hat Connectivity Link is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Managing your subscriptions Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. In the menu bar, click Subscriptions to view and manage your subscriptions. Revised on 2025-03-12 11:42:41 UTC

Commands:
8.118. mod_auth_kerb 8.118.1. RHBA-2013:0860 - mod_auth_kerb bug fix update Updated mod_auth_kerb packages that fix one bug are now available for Red Hat Enterprise Linux 6. The mod_auth_kerb package provides a module for the Apache HTTP Server designed to provide Kerberos authentication over HTTP. The module supports the Negotiate authentication method, which performs full Kerberos authentication based on ticket exchanges. Bug Fix BZ# 867153 Previously, when the KrbLocalUserMapping directive was enabled, mod_auth_kerb did not translate a principal name properly if the local name was of a higher length. Consequently, the Apache server returned the HTTP 500 error in such a scenario. A patch has been provided to address this issue and the module now correctly translates account names longer than their counterpart principal names. Users of mod_auth_kerb are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 10. Viewing diagnostics Use the Diagnostics tab to view diagnostic information about the JVM via the JVM DiagnosticCommand and HotspotDiangostic interfaces. Note The functionality is similar to the Diagnostic Commands view in Java Mission Control (jmc) or the command line tool jcmd. The plugin will provide corresponding jcmd commands in some scenarios. Procedure To retrieve the number of instances of loaded classes and the amount of bytes they take up, click Class Histogram . If the operation is repeated, the tab shows the difference since last run. To view the JVM diagnostic flag setting, click the JVM flags . For a running JVM, you can also modify the flag settings. Additional resources The supported JVM depends on the platform, for more information go to one of the following sources: http://www.oracle.com/technetwork/java/vmoptions-jsp-140102.html http://openjdk.java.net/groups/hotspot/docs/RuntimeOverview.html

Commands:
Chapter 6. Re-enabling accounts that reached the inactivity limit If Directory Server inactivated an account because it reached the inactivity limit, an administrator can re-enable the account. 6.1. Re-enabling accounts inactivated by the Account Policy plug-in You can re-enable accounts using the dsconf account unlock command or by manually updating the lastLoginTime attribute of the inactivated user. Prerequisites An inactivated user account. Procedure Reactivate the account using one of the following methods: Using the dsconf account unlock command: # dsidm -D "cn=Directory manager" ldap://server.example.com -b " dc=example,dc=com " account unlock " uid=example,ou=People,dc=example,dc=com " By setting the lastLoginTime attribute of the user to a recent time stamp: # ldapmodify -H ldap://server.example.com -x -D " cn=Directory Manager " -W dn: uid=example,ou=People,dc=example,dc=com changetype: modify replace: lastLoginTime lastLoginTime: 20210901000000Z Verification Authenticate as the user that you have reactivated. For example, perform a search: # ldapsearch -H ldap://server.example.com -x -D " uid=example,ou=People,dc=example,dc=com " -W -b " dc=example,dc=com -s base" If the user can successfully authenticate, the account was reactivated.

Commands:
dsidm -D "cn=Directory manager" ldap://server.example.com -b " dc=example,dc=com " account unlock " uid=example,ou=People,dc=example,dc=com "
ldapmodify -H ldap://server.example.com -x -D " cn=Directory Manager " -W dn: uid=example,ou=People,dc=example,dc=com changetype: modify replace: lastLoginTime lastLoginTime: 20210901000000Z
ldapsearch -H ldap://server.example.com -x -D " uid=example,ou=People,dc=example,dc=com " -W -b " dc=example,dc=com -s base"
4.5. Request Level Transactions Request level transactions are used when the request is not in the scope of a global or local transaction, which implies autoCommit is true . In a request level transaction, your application does not need to explicitly call commit or rollback, rather every command is assumed to be its own transaction that will automatically be committed or rolled back by the server. JBoss Data Virtualization can perform updates through virtual tables. These updates might result in an update against multiple physical systems, even though the application issues the update command against a single virtual table. Often, a user might not know whether the queried tables actually update multiple sources and require a transaction. For that reason, JBoss Data Virtualization allows your application to automatically wrap commands in transactions when necessary. Because this wrapping incurs a performance penalty for your queries, you can choose from a number of available wrapping modes to suit your environment. You need to choose between the highest degree of integrity and performance your application needs. For example, if your data sources are not transaction-compliant, you might turn transaction wrapping off to maximize performance.

Commands:
Chapter 3. Creating the Overcloud The creation of an Overcloud that uses IPv6 networking requires additional arguments for the openstack overcloud deploy command. For example: The above command uses the following options: --templates - Creates the Overcloud from the default Heat template collection. -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml - Adds an additional environment file to the Overcloud deployment. In this case, it is an environment file that initializes network isolation configuration for IPv6. -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml - Adds an additional environment file to the Overcloud deployment. In this case, it is an environment file that initializes network isolation configuration for IPv6. -e /home/stack/network-environment.yaml - Adds an additional environment file to the Overcloud deployment. In this case, it includes overrides related to IPv6. Ensure that network_data.yaml includes the setting ipv6: true . versions of Red Hat OpenStack director, included two routes: one for IPv6 on the External network (default) and one for IPv4 on the Control Plane. To use both default routes, ensure that the controller definition in roles_data.yaml contains both networks in default_route_networks (for example, default_route_networks: ['External', 'ControlPlane'] ). --ntp-server pool.ntp.org - Sets our NTP server. The Overcloud creation process begins and the director provisions your nodes. This process takes some time to complete. To view the status of the Overcloud creation, open a separate terminal as the stack user and run: 3.1. Accessing the Overcloud The director generates a script to configure and help authenticate interactions with your Overcloud from the director host. The director saves this file ( overcloudrc ) in your stack user's home directory. Run the following command to use this file: This loads the necessary environment variables to interact with your Overcloud from the director host's CLI. To return to interacting with the director's host, run the following command:

Commands:
openstack overcloud deploy --templates -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml -e /home/stack/templates/network-environment.yaml --ntp-server pool.ntp.org [ADDITIONAL OPTIONS]
source ~/stackrc heat stack-list --show-nested
source ~/overcloudrc
source ~/stackrc
1.4. A Look at the Token Management System (TMS) Certificate System creates, manages, renews, and revokes certificates, and it also archives and recovers keys. For organizations which use smart cards, the Certificate System has a token management system - a collection of subsystems with established relationships - to generate keys and requests and receive certificates to be used for smart cards. For information on this topic, see the following sections in the Red Hat Certificate System Planning, Installation, and Deployment Guide : Working with Smart Cards (TMS) Using Smart Cards

Commands:
Chapter 6. Network Policy As a user with the admin role, you can create a network policy for the netobserv namespace. 6.1. Creating a network policy for Network Observability You might need to create a network policy to secure ingress traffic to the netobserv namespace. In the web console, you can create a network policy using the form view. Procedure Navigate to Networking NetworkPolicies . Select the netobserv project from the Project dropdown menu. Name the policy. For this example, the policy name is allow-ingress . Click Add ingress rule three times to create three ingress rules. Specify the following in the form: Make the following specifications for the first Ingress rule : From the Add allowed source dropdown menu, select Allow pods from the same namespace . Make the following specifications for the second Ingress rule : From the Add allowed source dropdown menu, select Allow pods from inside the cluster . Click + Add namespace selector . Add the label, kubernetes.io/metadata.name , and the selector, openshift-console . Make the following specifications for the third Ingress rule : From the Add allowed source dropdown menu, select Allow pods from inside the cluster . Click + Add namespace selector . Add the label, kubernetes.io/metadata.name , and the selector, openshift-monitoring . Verification Navigate to Observe Network Traffic . View the Traffic Flows tab, or any tab, to verify that the data is displayed. Navigate to Observe Dashboards . In the NetObserv/Health selection, verify that the flows are being ingested and sent to Loki, which is represented in the first graph. 6.2. Example network policy The following annotates an example NetworkPolicy object for the netobserv namespace: Sample network policy kind: NetworkPolicy apiVersion: networking.k8s.io/v1 metadata: name: allow-ingress namespace: netobserv spec: podSelector: {} 1 ingress: - from: - podSelector: {} 2 namespaceSelector: 3 matchLabels: kubernetes.io/metadata.name: openshift-console - podSelector: {} namespaceSelector: matchLabels: kubernetes.io/metadata.name: openshift-monitoring policyTypes: - Ingress status: {} 1 A selector that describes the pods to which the policy applies. The policy object can only select pods in the project that defines the NetworkPolicy object. In this documentation, it would be the project in which the Network Observability Operator is installed, which is the netobserv project. 2 A selector that matches the pods from which the policy object allows ingress traffic. The default is that the selector matches pods in the same namespace as the NetworkPolicy . 3 When the namespaceSelector is specified, the selector matches pods in the specified namespace. Additional resources Creating a network policy using the CLI

Commands:
kind: NetworkPolicy apiVersion: networking.k8s.io/v1 metadata: name: allow-ingress namespace: netobserv spec: podSelector: {} 1 ingress: - from: - podSelector: {} 2 namespaceSelector: 3 matchLabels: kubernetes.io/metadata.name: openshift-console - podSelector: {} namespaceSelector: matchLabels: kubernetes.io/metadata.name: openshift-monitoring policyTypes: - Ingress status: {}
Chapter 1. New features and enhancements Red Hat JBoss Core Services (JBCS) 2.4.57 Service Pack 2 includes the following new features and enhancements. 1.1. JBCS support for Apache HTTP Server 2.4.57 on RHEL 9 From the 2.4.57 Service Pack 2 release onward, JBCS also provides an archive file distribution of the Apache HTTP Server 2.4.57 for Red Hat Enterprise Linux (RHEL) 9 systems. Important Support is available for installing JBCS on RHEL 9 from an archive file only. JBCS does not provide an RPM distribution of the Apache HTTP Server 2.4.57 for RHEL 9 systems. If you want to install the Apache HTTP Server from RPM packages on RHEL 9, you can use the Application Streams feature of RHEL. For more information about the different installation options, see the Red Hat JBoss Core Services Apache HTTP Server Installation Guide . Note The base archive file for installing the JBCS Apache HTTP Server 2.4.57 on RHEL 9 is named Red Hat JBoss Core Services Apache HTTP Server 2.4.57 Patch 02 for RHEL 9 x86_64 . 1.2. JBCS support for MDExternalAccountBinding JBCS 2.4.57 Service Pack 2 introduces support for the MDExternalAccountBinding directive. This directive enables you to configure values for Automated Certificate Management Environment (ACME) external account binding, which allows clients to bind registrations to an existing customer account on ACME servers. For more information, see MDExternalAccountBinding Directive .

Commands: