mtpti5iD/redhat-docs_dataset huggingface dataset:
Part I. Upgrading your Red Hat build of OptaPlanner projects to OptaPlanner 8 If you have OptaPlanner projects that you created with the OptaPlanner 7 or earlier pubic API and you want to upgrade your project code to OptaPlanner 8, review the information in this guide. This guide also includes changes to implementation classes which are outside of the pubic API. The OptaPlanner public API is a subset of the OptaPlanner source code that enables you to interact with OptaPlanner through Java code. So that you can upgrade to higher OptaPlanner versions within the same major release, OptaPlanner follows semantic versioning . This means that you can upgrade from OptaPlanner 7.44 to OptaPlanner 7.48 for example without breaking your code that uses the OptaPlanner public API. The OptaPlanner public API classes are compatible within the versions of a major OptaPlanner release. However, when Red Hat releases a new major release, disrupting changes are sometimes introduced to the public API. OptaPlanner 8 is a new major release and some of the changes to the public API are not are not compatible with earlier versions of OptaPlanner. OptaPlanner 8 will be the foundation for the 8.x series for the few years. The changes to the public API that are not compatible with earlier versions that were required for this release were made for the long term benefit of this project. Table 1. Red Hat Decision Manager and Red Hat build of OptaPlanner versions Decision Manager OptaPlanner 7.7 7.33 7.8 7.39 7.9 7.44 7.10 7.48 7.11 8.5 Every upgrade note has a label that indicates how likely it is that your code will be affected by that change. The following table describes each label: Table 2. Upgrade impact labels Label Impact Major Likely to affect your code. Minor Unlikely to affect your code, especially if you followed the examples, unless you have customized the code extensively. Any changes that are not compatible with earlier versions of OptaPlanner are annotated with the Public API tag.

Commands:
Chapter 3. Creating an application using .NET 8.0 Learn how to create a C# hello-world application. Procedure Create a new Console application in a directory called my-app : The output returns: A simple Hello World console application is created from a template. The application is stored in the specified my-app directory. Verification steps Run the project: The output returns:

Commands:
dotnet new console --output my-app
The template "Console Application" was created successfully. Processing post-creation actions Running 'dotnet restore' on my-app /my-app.csproj Determining projects to restore Restored /home/ username / my-app /my-app.csproj (in 67 ms). Restore succeeded.
dotnet run --project my-app
Hello World!
Chapter 4. Resource Management Network priority cgroup resource controller Red Hat Enterprise Linux 6.3 introduces the Network Priority ( net_prio ) resource controller, which provides a way to dynamically set the priority of network traffic per each network interface for applications within various cgroups. For more information, refer to the Resource Management Guide . OOM control and notification API for cgroups The memory resource controller implements an Out-of-Memory (OOM) notifier which uses the new notification API. When enabled (by executing echo 1 > memory.oom_control ), an application is notified via eventfd when an OOM occurs. Note that OOM notification does not function for root cgroups. New numad package The numad package provides a daemon for NUMA (Non-Uniform Memory Architecture) systems that monitors NUMA characteristics. As an alternative to manual static CPU pinning and memory assignment, numad provides dynamic adjustment to minimize memory latency on an ongoing basis. The package also provides an interface that can be used to query the numad daemon for the best manual placement of an application. The numad package is introduced as a Technology Preview.

Commands:
2.7. GRUB Menu Configuration File The configuration file ( /boot/grub/grub.conf ), which is used to create the list of operating systems to boot in GRUB's menu interface, essentially allows the user to select a pre-set group of commands to execute. The commands given in Section 2.6, "GRUB Commands" can be used, as well as some special commands that are only available in the configuration file. 2.7.1. Configuration File Structure The GRUB menu interface configuration file is /boot/grub/grub.conf . The commands to set the global preferences for the menu interface are placed at the top of the file, followed by stanzas for each operating kernel or operating system listed in the menu. The following is a very basic GRUB menu configuration file designed to boot either Red Hat Enterprise Linux or Microsoft Windows 2000: This file configures GRUB to build a menu with Red Hat Enterprise Linux as the default operating system and sets it to autoboot after 10 seconds. Two sections are given, one for each operating system entry, with commands specific to the system disk partition table. Note Note that the default is specified as an integer. This refers to the first title line in the GRUB configuration file. For the Windows section to be set as the default in the example, change the default=0 to default=1 . Configuring a GRUB menu configuration file to boot multiple operating systems is beyond the scope of this chapter. Consult Section 2.9, "Additional Resources" for a list of additional resources.

Commands:
default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Red Hat Enterprise Linux AS (2.6.8-1.523) root (hd0,0) kernel /vmlinuz-2.6.8-1.523 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.8-1.523.img section to load Windows title Windows rootnoverify (hd0,0) chainloader +1
A.4. tuned Tuned is a tuning daemon that can adapt the operating system to perform better under certain workloads by setting a tuning profile. It can also be configured to react to changes in CPU and network use and adjusts settings to improve performance in active devices and reduce power consumption in inactive devices. To configure dynamic tuning behavior, edit the dynamic_tuning parameter in the /etc/tuned/tuned-main.conf file. Tuned then periodically analyzes system statistics and uses them to update your system tuning settings. You can configure the time interval in seconds between these updates with the update_interval parameter. For further details about tuned, see the man page:

Commands:
man tuned
D.2. Model Explorer View Teiid Designer allows you manage multiple projects containing multiple models and any corresponding or dependent resources. The Model Explorer provides a simple file-structured view of these resources. The Model Explorer (shown below) is comprised of a toolbar and a tree view. Figure D.2. Model Explorer View The toolbar consists of nine common actions: Preview Data - Executes a simple preview query (SELECT * FROM ) . Sort Model Contents - Sorts the contents of the models based on object type and alphabetizing. Refresh Markers - Refreshes error and warning markers for objects in tree. Up - Navigates up one folder/container location. (See Eclipse Help) Collapse All - Collapses all projects. Link with Editor - When object is selected in an open editor, this option auto-selects and reveals object in Model Explorer. Additional Actions The additional actions are shown in the following figure: Figure D.3. Additional Actions If the Show Imports checkbox is selected, the imports will be displayed directly under a model resource as shown below. Figure D.4. Show Model Imports Action

Commands:
1.3. Verify Downloaded Files Procedure 1.2. Verify File Checksums on Red Hat Enterprise Linux Obtain checksum values for the downloaded file Go to https://access.redhat.com/jbossnetwork/ . Log in if required. Select your Product and Version . Select the packages you want to verify. Once you have chosen them, navigate to the Software Details page. Take note of the MD5 and SHA-256 checksum values. Run a checksum tool on the file Navigate to the directory containing the downloaded file in a terminal window. Run md5sum downloaded_file . Run shasum downloaded_file . Example output: Compare the checksum values returned by the md5sum and shasum commands with the corresponding values displayed on the Software Details page. Download the file again if the two checksum values are not identical. A difference between the checksum values indicates that the file has either been corrupted during download or has been modified since it was uploaded to the server. Contact Red Hat Support for assistance if after several downloads the checksum does not successfully validate. Note No checksum tool is included with Microsoft Windows. Download a third-party MD5 application such as MD5 Summer from http://www.md5summer.org/ .

Commands:
[localhost]USD md5sum jboss-dv-installer-[VERSION]-redhat-[VERSION].jar MD5 (jboss-dv-installer-[VERSION]-redhat-[VERSION].jar) = 0d1e72a6b038d8bd27ed22b196e5887f [localhost]USD shasum jboss-dv-installer-[VERSION]-redhat-[VERSION].jar a74841391bd243d2ca29f31cd9f190f3f1bdc02d jboss-dv-installer-[VERSION]-redhat-[VERSION].jar
Chapter 34. Top Applications analytics graph The Top Applications analytics graph provides developers with a tool for optimizing API performance and gaining insights into usage patterns. Developers can identify high-performing applications, understand real-time metrics, and make data-driven decisions to enhance the overall API experience. The Top Applications analytics graph in Products > [Your_product_name] > Analytics > Top Applications shows data during periods for the time zone configured in the 3scale Admin Portal account. Top applications are retrieved based on fixed periods: The last 24 hours The last 7 days The last 30 days Date ranges, for example: from 09/27/2023 until 10/25/2023 If you search, for example using 05/17/2023 , the resulting graph shows the usage from 01/01/2023 to 12/31/2023 . This is the the calendar range which most closely fits the calendar period chosen by the user and the graph displayed is according to that calendar period. When checking Top Applications analytics there are 2 things to bear in mind: Top applications are retrieved based on fixed calendar period (day/week/month/year). The period is shown under the chart. Note: Between midnight 04/30/2023 and midnight 05/31/2023 means: from 2023/05/01 00:00:00 inclusive to 2023/06/01 00:00:00 exclusive, that is, until 2023/05/31 23:59:59 inclusive. The actual usage for the applications shown in the statistics are based on the user-selected period, not the calendar period. Therefore, sometimes there might be a situation where an application is displayed in the top applications view because it has a high usage in the calendar period, but has 0 usage for the actual selected period by the user. Example The user enters a date range using the calendar: from 10/25/2023 until 10/27/2022 . Based on that date range, a period is selected that matches the user-selected date range as closely as possible. This must comprise a single granularity, for example, 1 calendar day, 1 calendar month. The data store is queried for the top applications in that period: 10/25/2023 to 10/27/2023 . For the list of top applications returned, the usage is displayed using the user's original date range entered: 10/25/2023 to 10/27/2023 .

Commands:
8.12. Verifying Network Configuration Teaming for Redundancy Network redundancy is a process when devices are used for backup purposes to prevent or recover from a failure of a specific system. The following procedure describes how to verify the network configuration for teaming in redundancy: Procedure Ping the destination IP from the team interface. For example: View which interface is in active mode: enp1s0 is the active interface. Temporarily remove the network cable from the host. Note There is no method to properly test link failure events using software utilities. Tools that deactivate connections, such as ip or nmcli , show only the driver's ability to handle port configuration changes and not actual link failure events. Check if the backup interface is up: enp2s0 is now the active interface. Check if you can still ping the destination IP from the team interface:

Commands:
~]# ping -I team0 DSTADDR
~]# teamdctl team0 state setup: runner: activebackup ports: enp1s0 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up down count: 0 enp2s0 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up down count: 0 runner: active port: enp1s0
~]# teamdctl team0 state setup: runner: activebackup ports: enp1s0 link watches: link summary: down instance[link_watch_0]: name: ethtool link: down down count: 1 enp2s0 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up down count: 0 runner: active port: enp2s0
~]# ping -I team0 DSTADDR
B.96.4. RHSA-2011:0374 - Important: thunderbird security and bug fix update An updated thunderbird package that fixes one security issue and one bug is now available for Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this update as having important security impact. Mozilla Thunderbird is a standalone mail and newsgroup client. This erratum blacklists a small number of HTTPS certificates. (BZ# 689430 ) Bug Fix BZ# 683076 The RHSA-2011:0312 and RHSA-2011:0311 updates introduced a regression, preventing some Java content and plug-ins written in Java from loading. With this update, the Java content and plug-ins work as expected. All Thunderbird users should upgrade to this updated package, which resolves these issues. All running instances of Thunderbird must be restarted for the update to take effect.

Commands:
Chapter 1. Red Hat JBoss Web Server 6.0 Service Pack 4 Welcome to the Red Hat JBoss Web Server version 6.0 Service Pack 4 release. Red Hat JBoss Web Server is a fully integrated and certified set of components for hosting Java web applications. It consists of an application server (Apache Tomcat servlet container) and the Apache Tomcat Native Library. JBoss Web Server includes the following key components: Apache Tomcat is a servlet container in accordance with the Java Servlet Specification. JBoss Web Server contains Apache Tomcat 10.1. The Apache Tomcat Native Library improves Tomcat scalability, performance, and integration with native server technologies. Tomcat-vault is an extension for the JBoss Web Server that is used for securely storing passwords and other sensitive information used by a JBoss Web Server. The mod_cluster library enables communication between JBoss Web Server and the Apache HTTP Server mod_proxy_cluster module. The mod_cluster library enables you to use the Apache HTTP Server as a load balancer for JBoss Web Server. For more information about configuring mod_cluster , or for information about installing and configuring alternative load balancers such as mod_jk and mod_proxy , see the Apache HTTP Server Connectors and Load Balancing Guide . Apache portable runtime (APR) is a runtime that provides an OpenSSL-based TLS implementation for the HTTP connectors. JBoss Web Server provides a distribution of APR for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the APR package that the operating system provides. OpenSSL is a software library that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols and includes a basic cryptographic library. JBoss Web Server provides a distribution of OpenSSL for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the OpenSSL package that the operating system provides. This release of JBoss Web Server introduces Java 21 support. This release of JBoss Web Server provides OpenShift images based on Red Hat Enterprise Linux 8. Note Red Hat distributes the JBoss Web Server 6.0 Service Pack 4 release in RPM packages only. This service pack release is not available in archive file format.

Commands:
2.32. RHEA-2011:0622 - new package: python-netaddr A new python-netaddr package is now available for Red Hat Enterprise Linux 6. The python-netaddr package provides a network address representation and manipulation library for Python. The netaddr library allows Python applications to work with IPv4 and IPv6 addresses, subnetworks, non-aligned IP address ranges and sets, MAC addresses, Organizationally Unique Identifiers (OUI), Individual Address Blocks (IAB), and IEEE EUI-64 identifiers. This enhancement update adds the python-netaddr package to Red Hat Enterprise Linux 6. (BZ# 658557 ) All users who require python-netaddr should install this new package.

Commands:
Appendix A. Troubleshooting permission issues Satellite upgrades perform pre-upgrade checks. If the pre-upgrade check discovers permission issues, it fails with an error similar to the following one: If you see an error like this on your Satellite Server, identify and remedy the permission issues. Procedure On your Satellite Server, identify permission issues: Fix permission issues: Verification Rerun the check to ensure no permission issues remain:

Commands:
2024-01-29T20:50:09 [W|app|] Could not create role 'Ansible Roles Manager': ERF73-0602 [Foreman::PermissionMissingException]: some permissions were not found:
satellite-maintain health check --label duplicate_permissions
foreman-rake db:seed
satellite-maintain health check --label duplicate_permissions
6.5. Removing Lost Physical Volumes from a Volume Group If you lose a physical volume, you can activate the remaining physical volumes in the volume group with the --partial argument of the vgchange command. You can remove all the logical volumes that used that physical volume from the volume group with the --removemissing argument of the vgreduce command. You should run the vgreduce command with the --test argument to verify what you will be destroying. Like most LVM operations, the vgreduce command is reversible if you immediately use the vgcfgrestore command to restore the volume group metadata to its state. For example, if you used the --removemissing argument of the vgreduce command without the --test argument and find you have removed logical volumes you wanted to keep, you can still replace the physical volume and use another vgcfgrestore command to return the volume group to its state.

Commands:
Providing feedback on Workload Availability for Red Hat OpenShift documentation We appreciate your feedback on our documentation. Let us know how we can improve it. To do so: Go to the JIRA website. Enter a descriptive title in the Summary field. Enter your suggestion for improvement in the Description field. Include links to the relevant parts of the documentation. Enter your username in the Reporter field. Enter the affected versions in the Affects Version/s field. Click Create at the bottom of the dialog.

Commands:
9.5. Creating Rules Rules determine what certificate object is published in what location. Rules work independently, not in tandem. A certificate or CRL that is being published is matched against every rule. Any rule which it matches is activated. In this way, the same certificate or CRL can be published to a file, to an Online Certificate Status Manager, and to an LDAP directory by matching a file-based rule, an OCSP rule, and matching a directory-based rule. Rules can be set for each object type: CA certificates, CRLs, user certificates, and cross-pair certificates. The rules can be more detailed for different kinds of certificates or different kinds of CRLs. The rule first determines if the object matches by matching the type and predicate set up in the rule with the object. Where matching objects are published is determined by the publisher and mapper associated with the rule. Rules are created for each type of certificate the Certificate Manager issues. Modify publishing rules by doing the following: Log into the Certificate Manager Console. In the Configuration tab, select Certificate Manager from the navigation tree on the left. Select Publishing , and then Rules . The Rules Management tab, which lists configured rules, opens on the right. To edit an existing rule, select that rule from the list, and click Edit . This opens the Rule Editor window. To create a rule, click Add . This opens the Select Rule Plug-in Implementation window. Select the Rule module. This is the only default module. If any custom modules have been been registered, they are also available. Edit the rule. type . This is the type of certificate for which the rule applies. For a CA signing certificate, the value is cacert . For a cross-signed certificate, the value is xcert . For all other types of certificates, the value is certs . For CRLs, specify crl . predicate . This sets the predicate value for the type of certificate or CRL issuing point to which this rule applies. The predicate values for CRL issuing points, delta CRLs, and certificates are listed in Table 9.3, "Predicate Expressions" . enable . mapper . Mappers are not necessary when publishing to a file; they are only needed for LDAP publishing. If this rule is associated with a publisher that publishes to an LDAP directory, select an appropriate mapper here. Leave blank for all other forms of publishing. publisher . Sets the publisher to associate with the rule. Table 9.3, "Predicate Expressions" lists the predicates that can be used to identify CRL issuing points and delta CRLs and certificate profiles. Table 9.3. Predicate Expressions Predicate Type Predicate CRL Issuing Point issuingPointId== Issuing_Point_Instance_ID && isDeltaCRL==[true|false] To publish only the master CRL, set isDeltaCRL==false . To publish only the delta CRL, set isDeltaCRL==true . To publish both, set a rule for the master CRL and another rule for the delta CRL. Certificate Profile profileId== profile_name To publish certificates based on the profile used to issue them, set profileId== to a profile name, such as caServerCert . Note pkiconsole is being deprecated.

Commands:
pkiconsole https://server.example.com:8443/ca
13.5. Installing in the Graphical User Interface The graphical installation interface is the preferred method of manually installing Red Hat Enterprise Linux. It allows you full control over all available settings, including custom partitioning and advanced storage configuration, and it is also localized to many languages other than English, allowing you to perform the entire installation in a different language. The graphical mode is used by default when you boot the system from local media (a CD, DVD or a USB flash drive). Figure 13.2. The Installation Summary Screen The sections below discuss each screen available in the installation process. Note that due to the installer's parallel nature, most of the screens do not have to be completed in the order in which they are described here. Each screen in the graphical interface contains a Help button. This button opens the Yelp help browser displaying the section of the Red Hat Enterprise Linux Installation Guide relevant to the current screen. You can also control the graphical installer with your keyboard. Following table shows you the shortcuts you can use. Table 13.2. Graphical installer keyboard shortcuts Shortcut keys Usage Tab and Shift + Tab Cycle through active control elements (buttons, check boxes, and so on.) on the current screen Up and Down Scroll through lists Left and Right Scroll through horizontal toolbars and table entries Space and Enter Select or remove a highlighted item from selection and expand and collapse drop-down menus Additionally, elements in each screen can be toggled using their respective shortcuts. These shortcuts are highlighted (underlined) when you hold down the Alt key; to toggle that element, press Alt + X , where X is the highlighted letter. Your current keyboard layout is displayed in the top right hand corner. Only one layout is configured by default; if you configure more than layout in the Keyboard Layout screen ( Section 13.10, "Keyboard Configuration" ), you can switch between them by clicking the layout indicator.

Commands: