mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix F. Replication High Availability Configuration Elements The following tables list the valid ha-policy configuration elements when using a replication HA policy. Table F.1. Configuration Elements Available when Using Replication High Availability Name Description check-for-live-server Applies only to brokers configured as master brokers. Specifies whether the original master broker checks the cluster for another live broker using its own server ID when starting up. Set to true to fail back to the original master broker and avoid a "split brain" situation in which two brokers become live at the same time. The default value of this property is false . cluster-name Name of the cluster configuration to use for replication. This setting is only necessary if you configure multiple cluster connections. If configured, the the cluster configuration with this name will be used when connecting to the cluster. If unset, the first cluster connection defined in the configuration is used. group-name If set, backup brokers will only pair with live brokers that have a matching value for group-name . initial-replication-sync-timeout The amount of time the replicating broker will wait upon completion of the initial replication process for the replica to acknowledge that it has received all the necessary data. The default value of this property is 30,000 milliseconds. Note During this interval, any other journal-related operations are blocked. max-saved-replicated-journals-size Applies to backup brokers only. Specifies how many backup journal files the backup broker retains. Once this value has been reached, the broker makes space for each new backup journal file by deleting the oldest journal file. The default value of this property is 2 . allow-failback Applies to backup brokers only. Determines whether the backup broker resumes its original role when another broker such as the live broker makes a request to take its place. The default value of this property is true . restart-backup Applies to backup brokers only. Determines whether the backup broker automatically restarts after it fails back to another broker. The default value of this property is true . Revised on 2022-03-15 13:56:26 UTC

Commands:
14.2. Finding Entries Using the Web Console You can use the LDAP Browser in the web console to search for entries in the Directory Server databases. Directory Server searches for entries based on the attribute-value pairs stored in the entries, not based on the attributes used in the distinguished names (DN) of these entries. For example, if an entry has a DN of uid=user_name,ou=People,dc=example,dc=com , then a search for dc=example matches the entry only when dc:example attribute exists in this entry. Prerequisites You are logged in to the Directory Server web console. You have root permissions. Procedure In the web console, navigate to LDAP Browser Search . Expand and select the search criteria to filter entries: Table 14.1. Default Index Attributes Search Parameter Description Search base Specifies the starting point of the search. It is a distinguished name (DN) that currently exists in the database. Note The Search tabs opens with pre-defined search base, when you open an entry details in the Tree View or Table View , click on the Options menu (⫶) and select Search . Search Scope Select Subtree to search entries in the whole subtree starting from the search base and including all child entries. Select One Level to search entries starting from the search base and including only the first level of child entries. Select Base to search for attribute values only in the entry specified as the search base. Size Limit Set the maximum number of entries to return from a search operation. Time Limit Set the time in seconds the search engine can look for entries. Show Locking Toggle the switch to on to see the lock status of the found entries. Search Attributes Select attributes that take part in the search. You can choose from the predefined attributes and add custom ones. Type the attribute value in the search text field and press Enter . Note Directory Server records all search requests to the access log file, which you can view at Monitoring Logging Access Log . Optional: To further refine your search, use search filters in the Filter tab to search for entries.

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:16 UTC

Commands:
Chapter 10. Viewing threads You can view and monitor the state of threads. Procedure Click the Runtime tab and then the Threads subtab. The Threads page lists active threads and stack trace details for each thread. By default, the thread list shows all threads in descending ID order. To sort the list by increasing ID, click the ID column label. Optionally, filter the list by thread state (for example, Blocked ) or by thread name. To drill down to detailed information for a specific thread, such as the lock class name and full stack trace for that thread, in the Actions column, click More .

Commands:
2.2. Install Maven Maven is a build system for projects that use the Project Object Model (POM). It downloads package dependencies quickly and easily. If you have an infrastructure team providing your Red Hat JBoss Data Virtualization environment, you can skip this procedure. Otherwise, you will need to follow it to install Maven to build your projects. Prerequisites The following software must be installed: An archiving tool for extracting the contents of compressed files. Open JDK. Procedure 2.1. Install Maven Download Maven. Go to http://maven.apache.org/download.cgi . Download the apache-maven-[latest-version] ZIP file. Install and configure Maven. On Red Hat Enterprise Linux Extract the ZIP archive to the directory where you wish to install Maven. Open your .bash_profile file: Add the M2_HOME environment variable to the file: Add the M2 environment variable to the file: Add the variable USDJAVA_HOME/bin to set the path to the correct Java installation. Note Make sure JAVA_HOME is pointing to a valid location. Add the M2 environment variable to the file: Save the file and exit your text editor. Reload your profile: Run the following command to verify that Maven is installed successfully on your machine: On Microsoft Windows Extract the ZIP archive to the directory where you wish to install Maven. The subdirectory apache-maven-[latest-version] is created from the archive. Press Start+Pause|Break . The System Properties dialog box is displayed. Click the Advanced tab and click Environment Variables . Under System Variables, select Path . Click Edit and add the two Maven paths using a semicolon to separate each entry. Add the M2_HOME variable and set the path to C:\path\to\your\Maven . Add the M2 variable and set the value to %M2_HOME%\bin. Update or create the Path environment variable: Add the %M2% variable to allow Maven to be executed from the command line. Add the variable %JAVA_HOME%\bin to set the path to the correct Java installation. Click OK to close all the dialog boxes including the System Properties dialog box. Open Windows command prompt and run the following command to verify that Maven is installed successfully on your machine:

Commands:
vi ~/.bash_profile
export M2_HOME=/path/to/your/maven
export M2=USDM2_HOME/bin
export PATH=USDM2:USDPATH
source ~/.bash_profile
mvn --version
mvn --version
Chapter 11. Controlling access to the Admin Console Each realm created on the Red Hat build of Keycloak has a dedicated Admin Console from which that realm can be managed. The master realm is a special realm that allows admins to manage more than one realm on the system. This chapter goes over all the scenarios for this. 11.1. Master realm access control The master realm in Red Hat build of Keycloak is a special realm and treated differently than other realms. Users in the Red Hat build of Keycloak master realm can be granted permission to manage zero or more realms that are deployed on the Red Hat build of Keycloak server. When a realm is created, Red Hat build of Keycloak automatically creates various roles that grant fine-grain permissions to access that new realm. Access to The Admin Console and Admin REST endpoints can be controlled by mapping these roles to users in the master realm. It's possible to create multiple superusers, as well as users that can only manage specific realms. 11.1.1. Global roles There are two realm-level roles in the master realm. These are: admin create-realm Users with the admin role are superusers and have full access to manage any realm on the server. Users with the create-realm role are allowed to create new realms. They will be granted full access to any new realm they create. 11.1.2. Realm specific roles Admin users within the master realm can be granted management privileges to one or more other realms in the system. Each realm in Red Hat build of Keycloak is represented by a client in the master realm. The name of the client is <realm name>-realm . These clients each have client-level roles defined which define varying level of access to manage an individual realm. The roles available are: view-realm view-users view-clients view-events manage-realm manage-users create-client manage-clients manage-events view-identity-providers manage-identity-providers impersonation Assign the roles you want to your users and they will only be able to use that specific part of the administration console. Important Admins with the manage-users role will only be able to assign admin roles to users that they themselves have. So, if an admin has the manage-users role but doesn't have the manage-realm role, they will not be able to assign this role. 11.2. Dedicated realm admin consoles Each realm has a dedicated Admin Console that can be accessed by going to the url /admin/{realm-name}/console . Users within that realm can be granted realm management permissions by assigning specific user role mappings. Each realm has a built-in client called realm-management . You can view this client by going to the Clients left menu item of your realm. This client defines client-level roles that specify permissions that can be granted to manage the realm. view-realm view-users view-clients view-events manage-realm manage-users create-client manage-clients manage-events view-identity-providers manage-identity-providers impersonation Assign the roles you want to your users and they will only be able to use that specific part of the administration console.

Commands:
4.15. Disabling ptrace() The ptrace() system call allows one process to observe and control the execution of another process and change its memory and registers. This call is used primarily by developers during debugging, for example when using the strace utility. When ptrace() is not needed, it can be disabled to improve system security. This can be done by enabling the deny_ptrace Boolean, which denies all processes, even those that are running in unconfined_t domains, from being able to use ptrace() on other processes. The deny_ptrace Boolean is disabled by default. To enable it, run the setsebool -P deny_ptrace on command as the root user: To verify if this Boolean is enabled, use the following command: To disable this Boolean, run the setsebool -P deny_ptrace off command as root: Note The setsebool -P command makes persistent changes. Do not use the -P option if you do not want changes to persist across reboots. This Boolean influences only packages that are part of Red Hat Enterprise Linux. Consequently, third-party packages could still use the ptrace() system call. To list all domains that are allowed to use ptrace() , enter the following command. Note that the setools-console package provides the sesearch utility and that the package is not installed by default.

Commands:
~]# setsebool -P deny_ptrace on
~]USD getsebool deny_ptrace deny_ptrace --> on
~]# setsebool -P deny_ptrace off
~]# sesearch -A -p ptrace,sys_ptrace -C | grep -v deny_ptrace | cut -d ' ' -f 5
4.5. Testing Your Models Designing and working with data is often much easier when you can see the information you are working with. The Teiid Designer's Preview Data feature makes this possible and allows you to instantly preview the information described by any object, whether it's a physical table or a virtual view. In other words, you can test the views with actual data by simply selecting the table, view, procedure or XML document. The preview functionality insures that data access behavior in Teiid Designer will reliably match when the VDB is deployed to the Server. Previewing information is a fast and easy way to sample the data. Of course, to run more complicated queries like what your application likely uses, simply execute the VDB in Teiid Designer and type in any query or SQL statement. After creating your models, you can test them by using the Preview Data action. By selecting a desired table object and executing the action, the results of a simple query will be displayed in the Data Tools SQL Results view. This action is accessible throughout the Teiid Designer in various view toolbars and context menus. Previewable objects include: Relational table or view, including tables involving access patterns Relational procedure Web Service operation XML Document staging table Note If attempting to preview a relational access pattern, a web service operation or a relational procedure with input parameters, a dialog will request values for required parameters.

Commands:
8.4. Install the ODBC Driver on Microsoft Windows Prerequisites Administrative permissions are required. Procedure 8.1. Install the ODBC Driver on Microsoft Windows Download the correct ODBC driver package ( jboss-dv-psqlodbc-[version]- X .zip ) from https://access.redhat.com/jbossnetwork/ . Unzip the installation package. Double-click the jboss-dv-psqlodbc-[version]- X .msi file to start the installer. The installer wizard is displayed. Click . The End-User License Agreement will be displayed. Click I accept the terms in the License Agreement if you accept the licensing terms and then click . If you want to install in a different directory other than the default directory shown, click the Browse button and select a directory. Click . You are presented with a confirmation screen. Review the choices you have made and click to begin installation. Click Finish . Note Installation packages for different operating systems can be downloaded from http://access.redhat.com .

Commands:
20.5. Displaying Information about a Guest Virtual Machine and the Hypervisor The virsh list command will list guest virtual machines connected to your hypervisor that fit the search parameter requested. The output of the command has 3 columns in a table. Each guest virtual machine is listed with its ID, name, and state . A wide variety of search parameters is available for virsh list . These options are available on the man page, by running man virsh or by running the virsh list --help command. Note Note that this if this command only displays guest virtual machines created by the root user. If it does not display a virtual machine you know you have created, it is probable you did not create the virtual machine as root. Guests created using the virt-manager interface are by default created by root. Example 20.1. How to list all locally connected virtual machines The following example lists all the virtual machines your hypervisor is connected to. Note that this command lists both persistent and transient virtual machines. Example 20.2. How to list the inactive guest virtual machines The following example lists guests that are currently inactive, or not running. Note that the list only contains persistent virtual machines. In addition, the following commands can also be used to display basic information about the hypervisor: # virsh hostname - displays the hypervisor's host name, for example: # virsh sysinfo - displays the XML representation of the hypervisor's system information, if available, for example:

Commands:
virsh list --all Id Name State ------------------------------------------------ 8 guest1 running 22 guest2 paused 35 guest3 shut off 38 guest4 shut off
virsh list --inactive Id Name State ------------------------------------------------ 35 guest3 shut off 38 guest4 shut off
virsh hostname dhcp-2-157.eus.myhost.com
virsh sysinfo <sysinfo type='smbios'> <bios> <entry name='vendor'>LENOVO</entry> <entry name='version'>GJET71WW (2.21 )</entry> [...]
7.318. mysql 7.318.1. RHSA-2013:0772 - Important: mysql security update Updated mysql packages that fix several security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links associated with each description below. MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon (mysqld) and many client programs and libraries. Security Fix CVE-2012-5614 , CVE-2013-1506 , CVE-2013-1521 , CVE-2013-1531 , CVE-2013-1532 , CVE-2013-1544 , CVE-2013-1548 , CVE-2013-1552 , CVE-2013-1555 , CVE-2013-2375 , CVE-2013-2378 , CVE-2013-2389 , CVE-2013-2391 , CVE-2013-2392 This update fixes several vulnerabilities in the MySQL database server. Information about these flaws can be found on the Oracle Critical Patch Update Advisory page . These updated packages upgrade MySQL to version 5.1.69. For more information, refer to the MYSQL release notes located here: http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-68.html http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-69.html All MySQL users should upgrade to these updated packages, which correct these issues. After installing this update, the MySQL server daemon (mysqld) will be restarted automatically.

Commands:
Chapter 8. Set Up Replication Mode 8.1. About Replication Mode Red Hat JBoss Data Grid's replication mode is a simple clustered mode. Cache instances automatically discover neighboring instances on other Java Virtual Machines (JVM) on the same network and subsequently form a cluster with the discovered instances. Any entry added to a cache instance is replicated across all cache instances in the cluster and can be retrieved locally from any cluster cache instance. In JBoss Data Grid's replication mode, return values are locally available before the replication occurs. Report a bug

Commands:
Chapter 4. Supported platforms This section describes the different server platforms, hardware, tokens, and software supported by Red Hat Certificate System 10. 4.1. General requirements The minimal and recommended hardware for Red Hat Certificate System 10 are as follows: Minimal requirements CPU: 2 threads RAM: 2 GB Disk space: 20 GB The minimal requirements are based on the Red Hat Enterprise Linux 8 minimal requirements. For more information, see Red Hat Enterprise Linux technology capabilities and limits . Recommended requirements CPU: 4 or more threads, AES-NI support RAM: 8 GB or more Disk space: 80 GB or more 4.2. Server support See Chapter 6, Prerequisites for installation for supported system information. 4.3. Supported web browsers The only fully-tested browser is Mozilla Firefox, and to some extent, Chrome. However, in general, newer versions of browsers on major OS platforms are likely to work. 4.4. Supported Hardware Security Modules The following table lists Hardware Security Modules (HSM) supported by Red Hat Certificate System: HSM Firmware Appliance Software Client Software nCipher nShield Connect XC nShield_HSM_Firmware-12.72.1 12.71.0 SecWorld_Lin64-12.71.0 Thales TCT Luna Network HSM T-5000 with Luna-T7 internal card lunafw_update-7.11.1-4 7.11.0-25 LunaClient-7.11.1-5 Note While the Common Criteria evaluation tested using this Entrust HSM, any HSM is considered equivalent when it is at least FIPS 140-2 validated, provides PKCS#11 3.0 cryptographic services or higher, hardware protection for keys and supports the required algorithms. Some tokens that do not follow the PKCS #11 3.0 semantics will fail. For instance, some tokens do not properly support CKA_ID, which is a requirement for RHCS certificate and key provisioning of the token. NOTE Limited support for Thales Luna: Red Hat was not able to confirm that the Thales HSM unit supports AES key wrapping/unwrapping via OAEP. Please be aware that those features requiring support of this algorithm will not function without such support. These features include: KRA: key archival and recovery CMC SharedToken authentication mechanism for enrollments TKS TPS shared secret automatic transport during installation It is, however, observed that workarounds may be employed for some of these features, but at the cost of degraded security level or operational inconvenience. Another example is that a certain Safenet Luna model supports PKI private key extraction in its CKE - Key Export model, and only in non-FIPS mode. The Luna Cloning model and the CKE model in FIPS mode do not support PKI private key extraction.

Commands:
function::json_add_array_numeric_metric Name function::json_add_array_numeric_metric - Add a numeric metric to an array Synopsis Arguments array_name The name of the array the numeric metric should be added to. metric_name The name of the numeric metric. metric_description Metric description. An empty string can be used. metric_units Metic units. An empty string can be used. Description This function adds a numeric metric to an array, setting up everything needed.

Commands:
json_add_array_numeric_metric:long(array_name:string,metric_name:string,metric_description:string,metric_units:string)
Chapter 14. Configuring the Transactions Subsystem The transactions subsystem allows you to configure the Transaction Manager (TM) options, such as timeout values, transaction logging, statistics collection, and whether to use JTS. JBoss EAP provides transactional services using the Narayana framework. This framework leverages support for a broad range of transaction protocols based on standards, such as Jakarta Transactions, JTS, and Web Service transactions. For more information, see Managing Transactions on JBoss EAP .

Commands:
Chapter 22. Subsystem Control And maintenance This chapter provides information on how to control (start, stop, restart, and status check) a Red Hat Certificate System subsystem, as well as general maintenance (health check) recommendation. 22.1. Starting, Stopping, Restarting, and Obtaining Status Red Hat Certificate System subsystem instances can be stopped and started using the systemctl utility on Red Hat Enterprise Linux 8. Note You can also use the pki-server alias to start and stop instances: pki-server <command> <instance> is an alias to systemctl <command> pki-tomcatd@<instance>.service. . To start an instance: To stop an instance: To restart an instance: To display the status of an instance: unit_file has one of the following values: pki-tomcat : With watchdog disabled pki-tomcat-nuxwdog : With watchdog enabled

Commands:
systemctl start unit_file @ instance_name .service
pki-server start instance_name
systemctl stop unit_file @ instance_name .service
pki-server stop instance_name
systemctl restart unit_file @ instance_name .service
pki-server restart instance_name
systemctl status unit_file @ instance_name .service