mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix A. MSI-based installer properties The Red Hat build of OpenJDK for Windows MSI-based installer includes the JDK Files component and the following optional properties: Table A.1. Red Hat build of OpenJDK for Windows MSI-based installer properties Property Description Default value OpenJDK Runtime - Windows Registry The following registry keys are set HKLM\Software\JavaSoft\JDK\<version>, entries: JavaHome: <INSTALLDIR> RuntimeLib: <INSTALLDIR>\bin\server\jvm.dll HKLM\Software\JavaSoft\JDK, entries: CurrentVersion: <version> Yes OpenJDK Runtime - Path Variable Adds the Runtime to the Path variable so it is available from the command line. Yes OpenJDK Runtime - JAVA_HOME System Variable JAVA_HOME is used by some programs to find the Java runtime. No OpenJDK Runtime - REDHAT_JAVA_HOME System Variable REDHAT_JAVA_HOME can be used by some programs to find the Red Hat build of OpenJDK runtime. No OpenJDK Runtime - Jar Files Association This enables Jar files to be run from within Windows Explorer. No Mission Control - Files Contains files that are installed in the <installdir> \missioncontrol directory. No Mission Control - Path Variable Appends <installdir> \missioncontrol to the system PATH environment variable. No Revised on 2024-05-09 16:49:09 UTC

Commands:
Chapter 2. Deploying Red Hat build of OpenJDK application in containers You can deploy Red Hat build of OpenJDK applications in containers and have them run when the container is loaded. Procedure Copy the application JAR to the /deployments directory in the image JAR file. For example, the following shows a brief Dockerfile that adds an application called testubi.jar to the Red Hat build of OpenJDK 21 UBI8 image:

Commands:
FROM registry.access.redhat.com/ubi8/openjdk-17 COPY target/testubi.jar /deployments/testubi.jar
Chapter 15. Managing using qdmanage The qdmanage tool is a command-line tool for viewing and modifying the configuration of a running router at runtime. Note If you make a change to a router using qdmanage , the change takes effect immediately, but is lost if the router is stopped. If you want to make a permanent change to a router's configuration, you must edit the router's /etc/qpid-dispatch/qdrouterd.conf configuration file. You can use qdmanage with the following syntax: This specifies: One or more optional connection options to specify the router on which to perform the operation, or to supply security credentials if the router only accepts secure connections. If you do not specify any connection options, qdmanage connects to the router listening on localhost and the default AMQP port (5672). The operation to perform on the router. One or more optional options to specify a configuration entity on which to perform the operation or how to format the command output. When you enter a qdmanage command, it is executed as an AMQP management operation request, and then the response is returned as command output in JSON format. For example, the following command executes a query operation on a router, and then returns the response in JSON format: Additional resources For more information about qdmanage , see the qdmanage man page .

Commands:
qdmanage [ <connection-options> ] <operation> [ <options> ]
qdmanage query --type listener [ { "stripAnnotations": "both", "addr": "127.0.0.1", "multiTenant": false, "requireSsl": false, "idleTimeoutSeconds": 16, "saslMechanisms": "ANONYMOUS", "maxFrameSize": 16384, "requireEncryption": false, "host": "0.0.0.0", "cost": 1, "role": "normal", "http": false, "maxSessions": 32768, "authenticatePeer": false, "type": "org.apache.qpid.dispatch.listener", "port": "amqp", "identity": "listener/0.0.0.0:amqp", "name": "listener/0.0.0.0:amqp" } ]
5.50. ding-libs 5.50.1. RHBA-2012:0799 - ding-libs bug fix update Updated ding-libs packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The ding-libs packages contain a set of libraries used by the System Security Services Daemon (SSSD) and other projects and provide functions to manipulate filesystem pathnames (libpath_utils), a hash table to manage storage and access time properties (libdhash), a data type to collect data in a hierarchical structure (libcollection), a dynamically growing, reference-counted array (libref_array), and a library to process configuration files in initialization format (INI) into a library collection data structure (libini_config). Bug Fixes BZ# 736074 Prior to this update, memory could become corrupted if the initial table size exceeded 1024 buckets. This update modifies libdhash so that large initial table sizes now correctly allocate memory. BZ# 801393 Prior to this update, buffers were filled and one character above the allocated size would be set to the null terminator if the combination of two strings,concatenated by the function path_concat(), exceeded the size of the destination buffer. This update modifies the underlying code so that the null terminator is no longer added after the end of the buffer. All users of ding-libs are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 6. Migrating business processes to the new process designer The legacy process designer in Business Central is deprecated in Red Hat Process Automation Manager 7.13.5. It will be removed in a future Red Hat Process Automation Manager release. The legacy process designer will not receive any new enhancements or features. If you intend to use the new process designer, start migrating your processes to the new designer. Create all new processes in the new process designer. Note The process engine will continue to support the execution and deployment of business processes generated with the legacy designer into KIE Server. If you have a legacy business process that is functioning and that you do not intend to change, it is not mandatory to migrate to the new designer at this time. You can only migrate business processes that contain supported business process nodes in the new designer. More nodes will be added in future versions of Red Hat Process Automation Manager. Prerequisites You have an existing project that contains a business process asset that was created with the legacy process designer. Procedure In Business Central, click Menu Design Projects . Click the project you want to migrate, for example Mortgage_Process . Click Ok to open the project's asset list. Click the project's Business Process asset to open it in the legacy process designer. Click Migrate Migrate Diagram . Figure 6.1. Migration confirmation message Select Yes or No to confirm if you made changes. This option is only available if you have made changes to your legacy business process. Figure 6.2. Save diagram changes confirmation If the migration is successful, the business process opens in the new process designer and the business process name's extension changes from *.bpmn2 to *.bpmn. If the migration is unsuccessful due to an unsupported node type, Business Central displays the following error message: Figure 6.3. Migration failure message

Commands:
Chapter 2. Configuring and deploying a Red Hat OpenStack Platform HCI The following procedure describes the high-level steps involved in configuring and deploying a Red Hat OpenStack Platform (RHOSP) HCI. Each step is expanded on in subsequent sections. Procedure Prepare the predefined custom overcloud role for hyperconverged nodes, ComputeHCI . Configure resource isolation . Map storage management network ports to NICs . Deploy the overcloud . (Optional) Scale the hyperconverged nodes .

Commands:
Chapter 4. Upgrading an SAP NetWeaver system 4.1. Upgrading an SAP NetWeaver Non-Cloud or BYOS Cloud RHEL system Follow the Upgrading from RHEL 8 to RHEL 9 guide to upgrade your SAP NetWeaver non-cloud or BYOS cloud RHEL 8.* system to RHEL 9.*. At the end of chapter Chapter 6. Verifying the post-upgrade state , verify that only the normal , eus , or e4s repositories are enabled and the RHEL release lock is set to 9.X , where X is a desired minor release. 4.2. Upgrading an SAP NetWeaver Cloud PAYG RHEL system The upgrade of SAP NetWeaver or other SAP application systems hosted on cloud provider PAYG instances is very similar to the upgrade of SAP HANA systems hosted on cloud provider PAYG instances. All non-HANA specific steps listed earlier in the SAP HANA systems upgrade on cloud provider PAYG instances procedure should be applied to complete the upgrade of SAP NetWeaver or other SAP application systems hosted on cloud provider PAYG instances. The only difference is the repo channel for standalone SAP NetWeaver hosts on Microsoft Azure PAYG instances. When upgrading standalone NetWeaver or other SAP applications hosts on Microsoft Azure PAYG instances which correspond to RHEL for SAP Applications SKU, use --channel eus instead of --channel e4s . In other cases, --channel e4s is always used. After the upgrade with --channel eus , the system will have the following Red Hat repositories: # yum repolist rhel-9-for-x86_64-appstream-eus-rhui-rpms rhel-9-for-x86_64-baseos-eus-rhui-rpms rhel-9-for-x86_64-sap-netweaver-eus-rhui-rpms The repolist may contain other non-Red Hat repositories, namely custom repositories of cloud providers for RHUI configuration. Note The current supported upgrade path for SAP NetWeaver and other SAP application systems on all cloud providers are the two latest EUS/E4S releases which are supported by Leapp for non-HANA systems as per the Upgrading from RHEL 8 to RHEL 9 document. As always, run all the upgrade steps, including the preparation and pre-upgrade steps, on a test system first until you have verified that the upgrade can be performed successfully in your production environment.

Commands:
yum repolist rhel-9-for-x86_64-appstream-eus-rhui-rpms rhel-9-for-x86_64-baseos-eus-rhui-rpms rhel-9-for-x86_64-sap-netweaver-eus-rhui-rpms
D.4. Outline View The Outline View is a utility view which provides both at tree view dedicated to a specific model (open in an editor) and a scaled thumbnail diagram representative of the diagram open in the corresponding Diagram Editor . You can show the Outline View by clicking its tab. If there is no open editors, the view indicates that Outline is not available . If a Model Editor is open, then the root of the displayed tree will be the model for the editor that is currently in focus in Teiid Designer (tab on top).

Commands:
7.221. samba4 7.221.1. RHSA-2013:0506 - Moderate: samba4 security, bug fix and enhancement update Updated samba4 packages that fix one security issue, multiple bugs, and add various enhancements are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Samba is an open-source implementation of the Server Message Block (SMB) or Common Internet File System (CIFS) protocol, which allows PC-compatible machines to share files, printers, and other information. Note The samba4 packages have been upgraded to upstream version 4.0.0, which provides a number of bug fixes and enhancements over the version. In particular, improved interoperability with Active Directory (AD) domains. SSSD now uses the libndr-krb5pac library to parse the Privilege Attribute Certificate (PAC) issued by an AD Key Distribution Center (KDC). The Cross Realm Kerberos Trust functionality provided by Identity Management, which relies on the capabilities of the samba4 client library, is included as a Technology Preview. This functionality and server libraries, is included as a Technology Preview. This functionality uses the libndr-nbt library to prepare Connection-less Lightweight Directory Access Protocol (CLDAP) messages. Additionally, various improvements have been made to the Local Security Authority (LSA) and Net Logon services to allow verification of trust from a Windows system. Because the Cross Realm Kerberos Trust functionality is considered a Technology Preview, selected samba4 components are considered to be a Technology Preview. For more information on which Samba packages are considered a Technology Preview, refer to Table 5.1, "Samba4 Package Support" in the Release Notes . (BZ# 766333 , BZ# 882188 ) Security Fix CVE-2012-1182 A flaw was found in the Samba suite's Perl-based DCE/RPC IDL (PIDL) compiler, used to generate code to handle RPC calls. This could result in code generated by the PIDL compiler to not sufficiently protect against buffer overflows. Bug Fix BZ# 878564 Prior to this update, if the Active Directory (AD) server was rebooted, Winbind sometimes failed to reconnect when requested by "wbinfo -n" or "wbinfo -s" commands. Consequently, looking up users using the wbinfo tool failed. This update applies upstream patches to fix this problem and now looking up a Security Identifier (SID) for a username, or a username for a given SID, works as expected after a domain controller is rebooted. All users of samba4 are advised to upgrade to these updated packages, which fix these issues and add these enhancements. Warning: If you upgrade from Red Hat Enterprise Linux 6.3 to Red Hat Enterprise Linux 6.4 and you have Samba in use, you should make sure that you uninstall the package named "samba4" to avoid conflicts during the upgrade.

Commands:
Chapter 8. Using Fernet keys for encryption in the overcloud Fernet is the default token provider, that replaces uuid . You can review your Fernet deployment and test that tokens are working correctly. Fernet uses three types of keys, which are stored in /var/lib/config-data/puppet-generated/keystone/etc/keystone/fernet-keys . The highest-numbered directory contains the primary key, which generates new tokens and decrypts existing tokens. 8.1. Reviewing the Fernet deployment To test that Fernet tokens are working correctly, retrieve the IP address of the Controller node, SSH into the Controller node, and review the settings of the token driver and provider. Procedure Retrieve the IP address of the Controller node: SSH into the Controller node: Retrieve the values of the token driver and provider settings: Test the Fernet provider: The result includes the long Fernet token.

Commands:
[stack@director ~]USD source ~/stackrc [stack@director ~]USD openstack server list -------------------------------------- ------------------------- -------- ---------------------+ | ID | Name | Status | Networks | -------------------------------------- ------------------------- -------- ---------------------+ | 756fbd73-e47b-46e6-959c-e24d7fb71328 | overcloud-controller-0 | ACTIVE | ctlplane=192.0.2.16 | | 62b869df-1203-4d58-8e45-fac6cd4cfbee | overcloud-novacompute-0 | ACTIVE | ctlplane=192.0.2.8 | -------------------------------------- ------------------------- -------- ---------------------+
[tripleo-admin@overcloud-controller-0 ~]USD ssh tripleo-admin@192.0.2.16
[tripleo-admin@overcloud-controller-0 ~]USD sudo crudini --get /var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf token driver sql [tripleo-admin@overcloud-controller-0 ~]USD sudo crudini --get /var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf token provider fernet
[tripleo-admin@overcloud-controller-0 ~]USD exit [stack@director ~]USD source ~/overcloudrc [stack@director ~]USD openstack token issue ------------ -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | ------------ -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | expires | 2016-09-20 05:26:17+00:00 | | id | gAAAAABX4LppE8vaiFZ992eah2i3edpO1aDFxlKZq6a_RJzxUx56QVKORrmW0-oZK3-Xuu2wcnpYq_eek2SGLz250eLpZOzxKBR0GsoMfxJU8mEFF8NzfLNcbuS-iz7SV-N1re3XEywSDG90JcgwjQfXW-8jtCm-n3LL5IaZexAYIw059T_-cd8 | | project_id | 26156621d0d54fc39bf3adb98e63b63d | | user_id | 397daf32cadd490a8f3ac23a626ac06c | ------------ -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
8.4.7. System Upgrades and pacemaker_remote As of Red Hat Enterprise Linux 6.8, if the pacemaker_remote service is stopped on an active Pacemaker Remote node, the cluster will gracefully migrate resources off the node before stopping the node. This allows you to perform software upgrades and other routine maintenance procedures without removing the node from the cluster. Once pacemaker_remote is shut down, however, the cluster will immediately try to reconnect. If pacemaker_remote is not restarted within the resource's monitor timeout, the cluster will consider the monitor operation as failed. If you wish to avoid monitor failures when the pacemaker_remote service is stopped on an active Pacemaker Remote node, you can use the following procedure to take the node out of the cluster before performing any system administration that might stop pacemaker_remote Warning For Red Hat Enterprise Linux release 6.7 and earlier, if pacemaker_remote stops on a node that is currently integrated into a cluster, the cluster will fence that node. If the stop happens automatically as part of a yum update process, the system could be left in an unusable state (particularly if the kernel is also being upgraded at the same time as pacemaker_remote ). For Red Hat Enterprise Linux release 6.7 and earlier you must use the following procedure to take the node out of the cluster before performing any system administration that might stop pacemaker_remote . Use the following procedure to take a node out of a cluster when performing maintenance on a node running pacemaker_remote : Stop the node's connection resource with the pcs resource disable resourcename , which will move all services off the node. For guest nodes, this will also stop the VM, so the VM must be started outside the cluster (for example, using virsh ) to perform any maintenance. Perform the desired maintenance. When ready to return the node to the cluster, re-enable the resource with the pcs resource enable .

Commands:
11.6.3. Related Books Sendmail by Bryan Costales with Eric Allman et al; O'Reilly &Associates - A good Sendmail reference written with the assistance of the original creator of Delivermail and Sendmail. Removing the Spam: Email Processing and Filtering by Geoff Mulligan; Addison-Wesley Publishing Company - A volume that looks at various methods used by email administrators using established tools, such as Sendmail and Procmail, to manage spam problems. Internet Email Protocols: A Developer's Guide by Kevin Johnson; Addison-Wesley Publishing Company - Provides a very thorough review of major email protocols and the security they provide. Managing IMAP by Dianna Mullet and Kevin Mullet; O'Reilly &Associates - Details the steps required to configure an IMAP server. Security Guide ; Red Hat, Inc - The Server Security chapter explains ways to secure Sendmail and other services.

Commands:
Chapter 6. Red Hat Ansible Automation Platform best practices This section covers Ansible Automation Platform product use that has specific content or context for using Ansible Automation Platform as a service. 6.1. Configure automation to use instance groups Red Hat Ansible Automation Platform Service on AWS requires that customers implement their own automation execution plane. Job templates must use a customer-configured instance or container group to run. If omitted, job runs can seem non-functional and eventually time out due to automation execution failure. Each job template must be assigned to a customer-configured instance group to function. 6.2. Syncing content with private automation hub Private automation hub allows you to attempt to sync all content between automation hub or Ansible Galaxy. However, this synchronization fails due to the storage and resource demands of such a large task. When syncing content from external sources, limit the synchronization to the collections your organization plans to use, focusing on recent or known used versions to reduce the synchronization scope.

Commands:
Chapter 26. Extending a Stratis volume with additional block devices You can attach additional block devices to a Stratis pool to provide more storage capacity for Stratis file systems. You can do it manually or by using the web console. 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. Adding block devices to a Stratis pool You can add one or more block devices to a Stratis pool. Prerequisites Stratis is installed. See Installing Stratis . The stratisd service is running. The block devices that you are adding to the Stratis pool are not in use and not mounted. The block devices that you are adding to the Stratis pool are at least 1 GiB in size each. Procedure To add one or more block devices to the pool, use: Additional resources stratis(8) man page on your system 26.2. Adding a block device to a Stratis pool by using the web console You can use the web console to add a block device to an existing Stratis pool. You can also add caches as a block device. 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. A Stratis pool is created. The block devices on which you are creating a Stratis pool are not in use and are not mounted. Each block device on which you are creating a Stratis pool is at least 1 GB. Procedure Log in to the RHEL 8 web console. For details, see Logging in to the web console . Click Storage . In the Storage table, click the Stratis pool to which you want to add a block device. On the Stratis pool page, click Add block devices and select the Tier where you want to add a block device as data or cache. If you are adding the block device to a Stratis pool that is encrypted with a passphrase, enter the passphrase. Under Block devices , select the devices you want to add to the pool. Click Add .

Commands:
stratis pool add-data my-pool device-1 device-2 device-n
10.3. DDL Example 10.2. Sample vdb.xml file <vdb name="{vdb-name}" version="1"> <model name="{model-name}" type="PHYSICAL"> <source name="AccountsDB" translator-name="oracle" connection-jndi-name="java:/oracleDS"/> <metadata type="DDL"> **DDL Here** </metadata> </model> </vdb> This is applicable to both source and view models. When DDL is specified as the metadata import type, the model's metadata can be defined as DDL. See the section about DDL Metadata in Red Hat JBoss Data Virtualization Development Guide: Reference Material .

Commands:
<vdb name="{vdb-name}" version="1"> <model name="{model-name}" type="PHYSICAL"> <source name="AccountsDB" translator-name="oracle" connection-jndi-name="java:/oracleDS"/> <metadata type="DDL"> **DDL Here** </metadata> </model> </vdb>
Chapter 4. Clair security scanner Clair v4 (Clair) is an open source application that leverages static code analyses for parsing image content and reporting vulnerabilities affecting the content. Clair is packaged with Red Hat Quay and can be used in both standalone and Operator deployments. It can be run in highly scalable configurations, where components can be scaled separately as appropriate for enterprise environments. For more information about Clair security scanner, see Vulnerability reporting with Clair on Red Hat Quay .

Commands: