mtpti5iD/redhat-docs_dataset huggingface dataset:
5.7. Choose an Installation Boot Method You can use several methods to boot the Red Hat Enterprise Linux 7 installation program. The method you choose depends upon your installation media. Your system's firmware (BIOS of UEFI) settings might need to be changed to allow booting from removable media such as a DVD or a USB flash drive. See Section 7.1.1, "Booting from Physical Media" for information. Note Installation media must remain mounted throughout installation, including during execution of the %post section of a kickstart file. Full installation DVD or USB drive You can create bootable media from the full installation DVD ISO image. In this case, a single DVD or USB drive can be used to complete the entire installation - it will serve both as a boot device and as an installation source for installing software packages. See Chapter 3, Making Media for instructions on how to make a full installation DVD or USB drive. Minimal boot CD, DVD or USB Flash Drive A minimal boot CD, DVD or USB flash drive is created using a small ISO image, which only contains data necessary to boot the system and start the installation. If you use this boot media, you will need an additional installation source from which packages will be installed. See Section 3.2, "Making Installation USB Media" for instructions on making boot CDs, DVDs and USB flash drives. PXE Server A preboot execution environment (PXE) server allows the installation program to boot over the network. After you boot the system, you complete the installation from a different installation source, such as a local hard drive or a location on a network. For more information on PXE servers, see Chapter 24, Preparing for a Network Installation .

Commands:
13.5. Test Replication on the Application Use the following instructions to test that cache entries are replicating from the first server instance to the second as desired. Procedure 13.4. Test Replication on the Application Access the First Server Access the first application server and enter the key and value. Access the first application server in a browser window using the following URL: Insert the key foo . Insert the value bar . Access the Second Server Access the second application server and enter the key and value. Access the second application server in a browser window using the following URL: Click Get Some . Get the key foo . Click Put Some More . Insert the key mykey . Insert the value myvalue . Get All Keys and Values Access the first server and request all keys. Access the first application server in a browser window using the following URL: Click Get Some . Click Get All to request all key and values. Result As the results of the last step show, all the data added at each server has been replicated to the other server. Note Entries expire after 60 seconds from the most recent update. Directly Access Keys in the Cache To interact with predefined servlets or to directly store and retrieve keys from the cache, use the following URLs: Report a bug

Commands:
http://localhost:8080/jboss-helloworld-jdg
http://localhost:8180/jboss-helloworld-jdg
http://localhost:8080/jboss-helloworld-jdg
http://localhost:8080/jboss-helloworld-jdg/TestServletPut
http://localhost:8180/jboss-helloworld-jdg/TestServletGet
7.247. system-config-language 7.247.1. RHBA-2012:1213 - system-config-language bug fix update An updated system-config-language package that fixes one bug is now available for Red Hat Enterprise Linux 6. The system-config-language is a graphical user interface that allows the user to change the default language of the system. Bug Fix BZ#819811 When using system-config-language in a non-English locale, some of the messages in the GUI were not translated. Consequently, non-English users were presented with untranslated messages. With this update, all message strings have been translated. All users of system-config-language are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 6. steps After you have installed AMQ Broker and created a standalone broker with the default configuration settings, you can configure it to meet your messaging requirements, connect messaging client applications to it, and monitor and manage it. Additional resources are available to help you complete these goals. Configuring the broker Use Configuring AMQ Broker to configure the broker to meet your requirements. You can configure: The broker to accept client connections The address space (including point-to-point and publish-subscribe messaging) Message persistence Broker resource consumption (including resource limits, message paging, and large message support) Duplicate message detection Logging Securing the broker Use Configuring AMQ Broker to implement any of the following methods to secure the broker: Guest/anonymous access control Basic user and password access control Certificate-based access control LDAP integration Kerberos integration Setting up clustering and high availability Use Configuring AMQ Broker to add additional brokers to form a broker cluster and increase messaging throughput. You can also configure high availability to increase messaging reliability. Creating messaging client applications Use AMQ Clients Overview to learn about AMQ Clients and how it can help you to create messaging client applications that connect to the broker and produce and consume messages. Monitoring and managing the broker Use Managing AMQ Broker to monitor and manage your broker (or brokers) once they are running.

Commands:
18.2. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. The following types are used with CVS. Different types allow you to configure flexible access: cvs_data_t This type is used for data in a CVS repository. CVS can only gain full access to data if it has this type. cvs_exec_t This type is used for the /usr/bin/cvs binary.

Commands:
8.266. yum-rhn-plugin 8.266.1. RHBA-2014:1536 - yum-rhn-plugin bug fix update An updated yum-rhn-plugin package that fixes one bug is now available for Red Hat Enterprise Linux 6. The yum-rhn-plugin package allows the Yum package manager to access content from Red Hat Network. Bug Fix BZ# 1051972 An attempt to install a package that was not available or visible to YUM resulted in an empty transaction error. With this update, yum-rhn-plugin reports that the package is unavailable in this situation. Users of yum-rhn-plugin are advised to upgrade to this updated package, which fixes this bug.

Commands:
30.6.3. Configuring the OS/400 Boot Loader The /boot/vmlinitrd- <kernel-version> file is installed when you upgrade the kernel. However, you must use the dd command to configure the system to boot the new kernel. As root, issue the command cat /proc/iSeries/mf/side to determine the default side (either A, B, or C). As root, issue the following command, where <kernel-version> is the version of the new kernel and <side> is the side from the command: Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.

Commands:
dd if=/boot/vmlinitrd- <kernel-version> of=/proc/iSeries/mf/ <side> /vmlinux bs=8k
25.7. iSCSI This section describes the iSCSI API and the iscsiadm utility. Before using the iscsiadm utility, install the iscsi-initiator-utils package first by running yum install iscsi-initiator-utils . In Red Hat Enterprise Linux 7, the iSCSI service is lazily started by default. If root is not on an iSCSI device or there are no nodes marked with node.startup = automatic then the iSCSI service will not start until an iscsiadm command is run that requires iscsid or the iscsi kernel modules to be started. For example, running the discovery command iscsiadm -m discovery -t st -p ip:port will cause iscsiadm to start the iSCSI service. To force the iscsid daemon to run and iSCSI kernel modules to load, run systemctl start iscsid.service . 25.7.1. iSCSI API To get information about running sessions, run: This command displays the session/device state, session ID (sid), some negotiated parameters, and the SCSI devices accessible through the session. For shorter output (for example, to display only the sid-to-node mapping), run: or These commands print the list of running sessions with the format: Example 25.3. Output of the iscsisadm -m session Command For example: For more information about the iSCSI API, refer to /usr/share/doc/iscsi-initiator-utils- version /README .

Commands:
iscsiadm -m session -P 3
iscsiadm -m session -P 0
iscsiadm -m session
driver [ sid ] target_ip:port,target_portal_group_tag proper_target_name
iscsiadm -m session tcp [2] 10.15.84.19:3260,2 iqn.1992-08.com.netapp:sn.33615311 tcp [3] 10.15.85.19:3260,3 iqn.1992-08.com.netapp:sn.33615311
5.127. jss 5.127.1. RHBA-2012:0920 - jss bug fix update Updated jss packages that fix several bugs are now available for Red Hat Enterprise Linux 6. JSS (Java Security Services) is a Java binding to Network Security Services (NSS), which provides SSL/TLS network protocols and other security services in the Public Key Infrastructure (PKI) suite. JSS is primarily utilized by the Certificate Server. Bug Fixes BZ# 767768 During key archival process, DRM (Data Recovery Manager) decrypted user's private keys and then re-encrypted the keys for storage purposes. The reverse process took place during key recovery; therefore, the private key was not processed in a token at all times as the decrypted private key was present in the DRM memory between the time of decryption and encryption. This update adds the secure PKCS #12 and PKCS #5 v2.0 support, support for wrapping and unwrapping private keys in their token, and secure private key handling for TMS (Token Management System) key recovery to Red Hat Certificate System 8.1. As a result, the key archival operations now happen in the token. BZ# 767771 The "kra.storageUnit.hardware" configuration parameter did not exist in DRM's CS.cfg after upgrade. Consequently, if parameter "kra.storageUnit.hardware" was defined, recovery operations failed and the server returned the following error message: This update modifies the jss, pki-kra, pki-common components so that the "kra.storageUnit.hardware" configuration parameter is processed correctly. As a result, the key archival and recovery process is successful on in-place upgraded and migrated instances. BZ# 767773 Previously, JSS was using the HSM (Hardware Security Module) token name as manufacturer ID. If the HSM token name differed from the manufacturer ID, the key archival and recovery failed. This update adds logic to JSS so that it can recognize the currently supported HSMs: nCipher and SafeNet. Key archival and recovery in TMS and non-TMS Common Criteria environments now work as expected. All users of jss are advised to upgrade to these updated packages, which fix these bugs.

Commands:
PKCS #12 Creation Failed java.lang.IllegalArgumentException: bagType or bagContent is null
B.63. openswan B.63.1. RHSA-2010:0892 - Moderate: openswan security update Updated openswan packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Openswan is a free implementation of Internet Protocol Security (IPsec) and Internet Key Exchange (IKE). IPsec uses strong cryptography to provide both authentication and encryption services. These services allow you to build secure tunnels through untrusted networks. CVE-2010-3302 , CVE-2010-3308 Two buffer overflow flaws were found in the Openswan client-side XAUTH handling code used when connecting to certain Cisco gateways. A malicious or compromised VPN gateway could use these flaws to execute arbitrary code on the connecting Openswan client. CVE-2010-3752 , CVE-2010-3753 Two input sanitization flaws were found in the Openswan client-side handling of Cisco gateway banners. A malicious or compromised VPN gateway could use these flaws to execute arbitrary code on the connecting Openswan client. Red Hat would like to thank the Openswan project for reporting these issues. Upstream acknowledges D. Hugh Redelmeier and Paul Wouters as the original reporters. All users of openswan are advised to upgrade to these updated packages, which contain backported patches to correct these issues. After installing this update, the ipsec service will be restarted automatically.

Commands:
6.2. Determining the Required Cache Sizes The dsconf monitor dbmon command enables you to monitor cache statistics at runtime. To display the statistics, enter: Optionally, pass the -b back_end or -x option to the command to display the statistics for a specific back end or the index. If your caches are sufficiently sized, the number in DN Cache Count matches the values in the Cache Count backend entries. Additionally, if all of the entries and DNs fit within their respective caches, the Entry Cache Count count value matches the DN Cache Count value. The output of the example shows: Only 2.2% free database cache is left: However, to operate efficiently, at least 15% free database cache is required. To determine the optimal size of the database cache, calculate the sizes of all *.db and *.db4 files in the /var/lib/dirsrv/slapd- instance_name /db/ directory including subdirectories and the changelog database, and add 12% for overhead. To set the database cache, see Section 6.5, "Setting the Database Cache Size" . The DN cache of the userroot database is well-chosen: The DN cache of the database contains 100000 records, 69,8% of the cache is free, and each DN in memory requires 130 bytes on average. To set the DN cache, see Section 6.4, "Setting the Size of the DN Cache" . The statistics on the entry cache of the userroot database indicates that the entry cache value should be increased for better performance: The entry cache contains in this database 50000 records and only 2 Kilobytes of free space are left. To enable Directory Server to cache all 100000 DNs, the cache must be increased to minimum of 890 MB (100000 DNs * 8,9 KB average entry size). However, Red Hat recommends to round the minimum required size to the highest GB and double the result. In this example, the entry cache should be set to 2 Gigabytes. To set the entry cache, see Section 6.3, "Manually Setting the Entry Cache Size" .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com monitor dbmon DB Monitor Report: 2020-06-24 11:31:27 -------------------------------------------------------- Database Cache: - Cache Hit Ratio: 50% - Free Space: 397.31 KB - Free Percentage: 2.2% - RO Page Drops: 0 - Pages In: 2934772 - Pages Out: 219075 Normalized DN Cache: - Cache Hit Ratio: 60% - Free Space: 19.98 MB - Free Percentage: 99.9% - DN Count: 100000 - Evictions: 9282348 Backends: - dc=example,dc=com (userroot): - Entry Cache Hit Ratio: 66% - Entry Cache Count: 50000 - Entry Cache Free Space: 2.0 KB - Entry Cache Free Percentage: 0.8% - Entry Cache Average Size: 8.9 KB - DN Cache Hit Ratio: 21% - DN Cache Count: 100000 - DN Cache Free Space: 4.29 MB - DN Cache Free Percentage: 69.8% - DN Cache Average Size: 130.0 B
Database Cache: - Free Space: 397.31 KB - Free Percentage: 2.2%
Backends: - dc=example,dc=com (userroot): - DN Cache Count: 100000 - DN Cache Free Space: 4.29 MB - DN Cache Free Percentage: 69.8% - DN Cache Average Size: 130.0 B
Backends: - dc=example,dc=com (userroot): - Entry Cache Count: 50000 - Entry Cache Free Space: 2.0 KB - Entry Cache Free Percentage: 0.8% - Entry Cache Average Size: 8.9 KB
5.5. Configuring IPv6 Settings To configure IPv6 settings, follow the procedure described in Section 5.4, "Configuring IPv4 Settings" and click the IPv6 menu entry. Method Ignore - Choose this option if you want to ignore IPv6 settings for this connection. Automatic - Choose this option to use SLAAC to create an automatic, stateless configuration based on the hardware address and router advertisements (RA). Automatic, addresses only - Choose this option if the network you are connecting to uses router advertisements (RA) to create an automatic, stateless configuration, but you want to assign DNS servers manually. Automatic, DHCP only - Choose this option to not use RA, but request information from DHCPv6 directly to create a stateful configuration. Manual - Choose this option if you want to assign IP addresses manually. Link-Local Only - Choose this option if the network you are connecting to does not have a DHCP server and you do not want to assign IP addresses manually. Random addresses will be assigned as per RFC 4862 with prefix FE80::0 . Addresses DNS servers - Enter a comma separated list of DNS servers. Search domains - Enter a comma separated list of domain controllers. If you need to configure static routes, click the Routes button and for more details on configuration options, see Section 4.3, "Configuring Static Routes with GUI" .

Commands:
Chapter 5. System Specifications List The most recent list of supported hardware can be found at https://hardware.redhat.com/ . The installation program automatically detects and installs your computer's hardware. Although you should make sure that your hardware meets the minimum requirements to install Red Hat Enterprise Linux (refer to Section 3.2, "Is Your Hardware Compatible?" ) you do not usually need to supply the installation program with any specific details about your system. However, when performing certain types of installation, some specific details might be useful or even essential. If you plan to use a customized partition layout, record: The model numbers, sizes, types, and interfaces of the hard drives attached to the system. For example, Seagate ST3320613AS 320 GB on SATA0, Western Digital WD7500AAKS 750 GB on SATA1. This will allow you to identify specific hard drives during the partitioning process. If you are installing Red Hat Enterprise Linux as an additional operating system on an existing system, record: The mount points of the existing partitions on the system. For example, /boot on sda1 , / on sda2 , and /home on sdb1 . This will allow you to identify specific partitions during the partitioning process. If you plan to install from an image on a local hard drive: The hard drive and directory that holds the image. If you plan to install from a network location, or install on an iSCSI target: The make and model numbers of the network adapters on your system. For example, Netgear GA311. This will allow you to identify adapters when manually configuring the network. IP, DHCP, and BOOTP addresses Netmask Gateway IP address One or more name server IP addresses (DNS) If any of these networking requirements or terms are unfamiliar to you, contact your network administrator for assistance. If you plan to install from a network location: The location of the image on an FTP server, HTTP (web) server, HTTPS (web) server, or NFS server - see Section 8.3.5, "Installing via FTP, HTTP, or HTTPS" and Section 8.3.4, "Installing via NFS" for examples. If you plan to install on an iSCSI target: The location of the iSCSI target. Depending on your network, you might also need a CHAP username and password, and perhaps a reverse CHAP username and password - see Section 9.6.1.1, " Advanced Storage Options " . If you are installing using Intel iSCSI Remote Boot: All attached iSCSI storage devices must be disabled, otherwise the installation will succeed but the installed system will not boot. If your computer is part of a domain: You should verify that the domain name will be supplied by the DHCP server. If not, you will need to input the domain name manually during installation.

Commands:
Chapter 7. KafkaListenerAuthenticationTls schema reference Used in: GenericKafkaListener The type property is a discriminator that distinguishes use of the KafkaListenerAuthenticationTls type from KafkaListenerAuthenticationScramSha512 , KafkaListenerAuthenticationOAuth , KafkaListenerAuthenticationCustom . It must have the value tls for the type KafkaListenerAuthenticationTls . Property Description type Must be tls . string

Commands:
Chapter 11. Red Hat Decision Manager roles and users To access Business Central or KIE Server, you must create users and assign them appropriate roles before the servers are started. You can create users and roles when you install Business Central or KIE Server. If both Business Central and KIE Server are running on a single instance, a user who is authenticated for Business Central can also access KIE Server. However, if Business Central and KIE Server are running on different instances, a user who is authenticated for Business Central must be authenticated separately to access KIE Server. For example, if a user who is authenticated on Business Central but not authenticated on KIE Server tries to view or manage process definitions in Business Central, a 401 error is logged in the log file and the Invalid credentials to load data from remote server. Contact your system administrator. message appears in Business Central. This section describes Red Hat Decision Manager user roles. Note The admin , analyst , and rest-all roles are reserved for Business Central. The kie-server role is reserved for KIE Server. For this reason, the available roles can differ depending on whether Business Central, KIE Server, or both are installed. admin : Users with the admin role are the Business Central administrators. They can manage users and create, clone, and manage repositories. They have full access to make required changes in the application. Users with the admin role have access to all areas within Red Hat Decision Manager. analyst : Users with the analyst role have access to all high-level features. They can model projects. However, these users cannot add contributors to spaces or delete spaces in the Design Projects view. Access to the Deploy Execution Servers view, which is intended for administrators, is not available to users with the analyst role. However, the Deploy button is available to these users when they access the Library perspective. rest-all : Users with the rest-all role can access Business Central REST capabilities. kie-server : Users with the kie-server role can access KIE Server REST capabilities.

Commands: