mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 13. Creating users You can create as many Business Central users as you require. User privileges and settings are controlled by the roles assigned to a user and the groups that a user belongs to. For this example, you must create two new users: Katy who will act as the bank's loan manager and approver, and Bill who will act as the broker requesting the loan. For more information on creating users, see the Creating users chapter of Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 . In Business Central, you can use groups and roles to control permissions for a collection of users. You can create as many groups and roles as you want but a group must have at least one user. For this example, the user or users working on the tasks must be assigned to one or more of the following groups and roles: approver group: For the Qualify task broker group: For the Correct Data and Increase Down Payment tasks manager role: For the Final Approval task Procedure Click the gear icon in the upper-right corner and click Users . Click , enter Katy , click , and click Create . Click Yes to set a password, enter Katy in both fields, and click Change . Enter Bill , click , and click Create . Click Yes to set a password, enter Bill in both fields, and click Change . Click the Groups tab and click , enter approver , and click . Select Katy from the user list, and click Add selected users . Enter broker , and click . Select Bill from the user list, and click Add selected users . Click the Users tab, select Katy , and click Edit Roles Add roles . Select manager , click Add to selected roles , and click Save . Click the Groups tab and click Edit Groups Add to groups . Select approver and kie-server , and click Add to selected groups . Click Save . Click the Users tab, select Bill from the user list, and click Edit Roles Add roles . Select user , and click Add to selected roles . Click the Groups tab, click , select kie-server , and click Add to selected groups . Click Save .

Commands:
Chapter 1. Migrating Red Hat Single Sign-On 7.6 to Red Hat build of Keycloak The purpose of this guide is to document the steps that are required to successfully migrate Red Hat Single Sign-On 7.6 to Red Hat build of Keycloak 24.0. The instructions address migration of the following elements: Red Hat Single Sign-On 7.6 server Operator deployments on OpenShift Template deployments on OpenShift Applications secured by Red Hat Single Sign-On 7.6 Custom providers Custom themes This guide also includes guidelines for migrating upstream Keycloak to Red Hat build of Keycloak 24.0. Before you start the migration, you might consider installing a new instance of Red Hat build of Keycloak to become familiar with the changes for this release. See the Red Hat build of Keycloak Getting Started Guide .

Commands:
3.5.3. Incrementing Associated Values Use ++ to increment the associated value of a unique key in an array, as in: Again, you can also use a handler function for your index_expression . For example, if you wanted to tally how many times a specific process performed a read to the virtual file system (using the event vfs.read ), you can use the following probe: Example 3.14. vfsreads.stp In Example 3.14, "vfsreads.stp" , the first time that the probe returns the process name gnome-terminal (that is the first time gnome-terminal performs a VFS read), that process name is set as the unique key gnome-terminal with an associated value of 1. The time that the probe returns the process name gnome-terminal , SystemTap increments the associated value of gnome-terminal by 1. SystemTap performs this operation for all process names as the probe returns them.

Commands:
array_name [ index_expression ] ++
probe vfs.read { reads[execname()] ++ }
3.2.3. Autotools Documentation Red Hat Enterprise Linux 6 includes man pages for autoconf , automake , autoscan and most tools included in the Autotools suite. In addition, the Autotools community provides extensive documentation on autoconf and automake on the following websites: http://www.gnu.org/software/autoconf/manual/autoconf.html http://www.gnu.org/software/autoconf/manual/automake.html The following is an online book describing the use of Autotools. Although the above online documentation is the recommended and most up to date information on Autotools, this book is a good alternative and introduction. http://sourceware.org/autobook/ For information on how to create Autotools input files, see: http://www.gnu.org/software/autoconf/manual/autoconf.html#Making-configure-Scripts http://www.gnu.org/software/autoconf/manual/automake.html#Invoking-Automake The following upstream example also illustrates the use of Autotools in a simple hello program: http://www.gnu.org/software/hello/manual/hello.html

Commands:
Chapter 6. GNOME Shell Extensions GNOME Shell in Red Hat Enterprise Linux 7 does not support applets, which were used to customize the default GNOME 2 interface in Red Hat Enterprise Linux 5 and 6. GNOME 3 replaces applets with GNOME Shell extensions . Extensions can modify the default GNOME Shell interface and its parts, such as window management and application launching. 6.1. Replacement for the Clock Applet GNOME 2 in Red Hat Enterprise Linux 5 and 6 featured the Clock applet, which provided access to the date, time, and calendar from the GNOME 2 Panel. In Red Hat Enterprise Linux 7, that applet is replaced by the Clocks application, which is provided by the gnome-clocks package. The user can access that application by clicking the calendar on GNOME Shell's top bar and selecting Open Clocks . Figure 6.1. Open Clocks Getting More Information See Section 11.1, "What Are GNOME Shell Extensions?" for more detailed information on what GNOME Shell extensions are and how to configure and manage them.

Commands:
Chapter 2. Starting Fuse on JBoss EAP server Fuse on JBoss EAP supports both the standalone mode and domain mode. This chapter explains how to start the server in either standalone mode or domain mode. 2.1. Starting JBoss EAP in standalone mode The commands in this section Fuse explain how to start JBoss EAP as a standalone server. Prerequisites JBoss EAP 7.4.16 is installed. Procedure For Red Hat Enterprise Linux , run the following command: EAP_HOME/bin/standalone.sh For Microsoft Windows Server , run the following command: EAP_HOME\bin\standalone.bat 2.2. Starting JBoss EAP in domain mode The commands in this section explain how to start Fuse on JBoss EAP as a domain server. Prerequisites JBoss EAP 7.4.16 is installed. Procedure For Red Hat Enterprise Linux , run the following command: EAP_HOME/bin/domain.sh For Microsoft Windows Server , run the following command: EAP_HOME\bin\domain.bat Additional resources To obtain a list of parameters that you can pass to the start-up scripts, enter the -h parameter. For more information about starting and stopping JBoss Enterprise Application Platform using alternative and more advanced methods, see the Red Hat JBoss Enterprise Application Platform Configuration Guide .

Commands:
Chapter 6. Kafka breaking changes This section describes any changes to Kafka that required a corresponding change to Streams for Apache Kafka to continue to work. 6.1. Using Kafka's example file connectors Kafka no longer includes the example file connectors FileStreamSourceConnector and FileStreamSinkConnector in its CLASSPATH and plugin.path by default. Streams for Apache Kafka has been updated so that you can still use these example connectors. The examples now have to be added to the plugin path like any connector. Streams for Apache Kafka provides an example connector configuration file with the configuration required to deploy the file connectors as KafkaConnector resources: examples/connect/source-connector.yaml See Deploying example KafkaConnector resources and Extending Kafka Connect with connector plugins .

Commands:
Chapter 9. Container Images Based on Red Hat Software Collections 3.2 Component Description Supported architectures Application Images rhscl/nodejs-10-rhel7 Node.js 10 platform for building and running applications (EOL) x86_64, s390x, ppc64le rhscl/php-72-rhel7 PHP 7.2 platform for building and running applications (EOL) x86_64, s390x, ppc64le Daemon Images rhscl/nginx-114-rhel7 nginx 1.14 server and a reverse proxy server (EOL) x86_64, s390x, ppc64le Database Images rhscl/mysql-80-rhel7 MySQL 8.0 SQL database server x86_64, s390x, ppc64le Legend: x86_64 - AMD64 and Intel 64 architectures s390x - 64-bit IBM Z ppc64le - IBM POWER, little endian All images are based on components from Red Hat Software Collections. The images are available for Red Hat Enterprise Linux 7 through the Red Hat Container Registry. For detailed information about components provided by Red Hat Software Collections 3.2, see the Red Hat Software Collections 3.2 Release Notes . For more information about the Red Hat Developer Toolset 8.0 components, see the Red Hat Developer Toolset 8 User Guide . For information regarding container images based on Red Hat Software Collections 2, see Using Red Hat Software Collections 2 Container Images . EOL images are no longer supported.

Commands:
7.6. RHEA-2013:1642 - new packages: redhat-support-lib-python and redhat-support-tool New redhat-support-lib-python and redhat-support-tool packages are now available for Red Hat Enterprise Linux 6. The redhat-support-lib-python package provides a Python library that developers can use to easily write software solutions that leverage Red Hat Access subscription services. The redhat-support-tool utility facilitates console-based access to Red Hat's subscriber services and gives Red Hat subscribers more venues for accessing the content and services available to them as Red Hat customers. Further, it enables our customers to integrate and automate their helpdesk services with our subscription services. The capabilities of this package include: * Red Hat Access Knowledge Base article and solution viewing from the console (formatted as man pages). * Viewing, creating, modifying, and commenting on customer support cases from the console. * Attachment uploading directly to a customer support case or to ftp://dropbox.redhat.com/ from the console. * Full proxy support (that is, FTP and HTTP proxies). * Easy listing and downloading of attachments in customer support cases from the console. * Red Hat Access Knowledge Base searching on query terms, log messages, and other parameters, and viewing search results in a selectable list. * Easy uploading of log files, text files, and other sources to the Red Hat Access automatic problem determination engine for diagnosis. * Various other support-related commands. Detailed usage information for the tool can be found in the Red Hat Customer Portal at https://access.redhat.com/site/articles/445443 This enhancement update adds the redhat-support-lib-python and redhat-support-tool packages to Red Hat Enterprise Linux 6. (BZ# 987159 , BZ# 869395 , BZ# 880776 , BZ# 987171 , BZ# 987169 , BZ# 987163 ) All users who require redhat-support-lib-python and redhat-support-tool are advised to install these new packages.

Commands:
7.217. rpmdevtools 7.217.1. RHBA-2012:1313 - rpmdevtools bug fix update Updated rpmdevtools packages that fix one bug are now available for Red Hat Enterprise Linux 6. The rpmdevtools packages contain scripts and (X)Emacs support files to aid in development of RPM packages. Bug Fix BZ#730770 Prior to this update, the sample spec files referred to a deprecated BuildRoot tag. The tag was ignored if it was defined. This update removes the BuildRoot tags from all sample spec files. All users of rpmdevtools are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 3. Logging into automation controller after installation After you install automation controller, you must log in. Procedure With the login information provided after your installation completed, open a web browser and log in to the automation controller by navigating to its server URL at: https://<CONTROLLER_SERVER_NAME>/ Use the credentials specified during the installation process to login: The default username is admin . The password for admin is the value specified. Click the More Actions icon ... to the desired user. Click Edit . Edit the required details and click Save .

Commands:
19.8. Expert Options This section provides information about expert options. KVM Virtualization -enable-kvm QEMU-KVM supports only KVM virtualization and it is used by default if available. If -enable-kvm is used and KVM is not available, qemu-kvm fails. However, if -enable-kvm is not used and KVM is not available, qemu-kvm runs in TCG mode, which is not supported. Disable Kernel Mode PIT Reinjection -no-kvm-pit-reinjection No Shutdown -no-shutdown No Reboot -no-reboot Serial Port, Monitor, QMP -serial <dev> -monitor <dev> -qmp <dev> Supported devices are: stdio - standard input/output null - null device file :<filename> - output to file. tcp :[<host>]:<port>[,server][,nowait][,nodelay] - TCP Net console. unix :<path>[,server][,nowait] - Unix domain socket. mon :<dev_string> - Any device above, used to multiplex monitor too. none - disable, valid only for -serial. chardev :<id> - character device created with -chardev. Monitor Redirect -mon <chardev_id>[,mode=[readline|control]][,default=[on|off]] Manual CPU Start -S RTC -rtc [base=utc|localtime|date][,clock=host|vm][,driftfix=none|slew] Watchdog -watchdog model Watchdog Reaction -watchdog-action <action> Guest Memory Backing -mem-prealloc -mem-path /dev/hugepages SMBIOS Entry -smbios type=0[,vendor=<str>][,<version=str>][,date=<str>][,release=%d.%d] -smbios type=1[,manufacturer=<str>][,product=<str>][,version=<str>][,serial=<str>][,uuid=<uuid>][,sku=<str>][,family=<str>]

Commands:
3.2. Tracking Configuration History Data from the Red Hat Virtualization History Database (called ovirt_engine_history ) can be used to track the engine database. The ETL service, ovirt-engine-dwhd , tracks three types of changes: A new entity is added to the engine database - the ETL Service replicates the change to the ovirt_engine_history database as a new entry. An existing entity is updated - the ETL Service replicates the change to the ovirt_engine_history database as a new entry. An entity is removed from the engine database - A new entry in the ovirt_engine_history database flags the corresponding entity as removed. Removed entities are only flagged as removed. The configuration tables in the ovirt_engine_history database differ from the corresponding tables in the engine database in several ways. The most apparent difference is they contain fewer configuration columns. This is because certain configuration items are less interesting to report than others and are not kept due to database size considerations. Also, columns from a few tables in the engine database appear in a single table in ovirt_engine_history and have different column names to make viewing data more convenient and comprehensible. All configuration tables contain: a history_id to indicate the configuration version of the entity; a create_date field to indicate when the entity was added to the system; an update_date field to indicate when the entity was changed; and a delete_date field to indicate the date the entity was removed from the system.

Commands:
Chapter 51. New Drivers Storage Drivers nvme-fabrics nvme-rdma nvmet nvmet-rdma nvme-loop qedi qedf Network Drivers qedr rdma_rxe ntb_transport ntb_perf mdev vfio_mdev amd-xgbe atlantic libcxgb ena rocker amd8111e nfp mlxsw_core mlxsw_i2c mlxsw_spectrum mlxsw_pci mlxsw_switchx2 mlxsw_switchib mlxsw_minimal Graphics Drivers and Miscellaneous Drivers ccp chcr uio_hv_generic usbip-core vhost_vsock tpm_tis_spi gpio-amdpt joydev sdio_uart ptp_kvm mei_wdt dell-rbtn dell-smo8800 intel-hid dell-smbios skx_edac kvmgt pinctrl-intel pinctrl-sunrisepoint pinctrl-amd dax_pmem dax nfit ledtrig-usbport

Commands:
Chapter 10. Post-deployment configuration suggestions Depending on your requirements, you may want to perform some additional configuration on your newly deployed Red Hat Hyperconverged Infrastructure for Virtualization. This section contains suggested steps for additional configuration. Details on these processes are available in Maintaining Red Hat Hyperconverged Infrastructure for Virtualization . 10.1. Configure notifications See Configuring Event Notifications in the Administration Portal to configure email notifications. 10.2. (Optional)Configure Host Power Management The Red Hat Virtualization Manager 4.4 is capable of rebooting hosts that have entered a non-operational or non-responsive state, as well as preparing to power off under-utilized hosts to save power. This functionality depends on a properly configured power management device. See Configuring Host Power Management Settings for further information. 10.3. Configure backup and recovery options Red Hat recommends configuring at least basic disaster recovery capabilities on all production deployments. See Configuring backup and recovery options in Maintaining Red Hat Hyperconverged Infrastructure for Virtualization for more information.

Commands:
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 Process Automation Manager and Red Hat build of OptaPlanner versions Process Automation 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:
19.6.2. Online Documentation How to configure postfix with TLS? - A Red Hat Knowledgebase article that describes configuring postfix to use TLS. The Red Hat Knowledgebase article How to Configure a System to Manage Multiple Virtual Mailboxes Using Postfix and Dovecot describes managing multiple virtual users under one real-user account using Postfix as Mail Transporting Agent (MTA) and Dovecot as IMAP server. http://www.sendmail.org/ - Offers a thorough technical breakdown of Sendmail features, documentation and configuration examples. http://www.sendmail.com/ - Contains news, interviews and articles concerning Sendmail, including an expanded view of the many options available. http://www.postfix.org/ - The Postfix project home page contains a wealth of information about Postfix. The mailing list is a particularly good place to look for information. http://www.fetchmail.info/fetchmail-FAQ.html - A thorough FAQ about Fetchmail. http://www.procmail.org/ - The home page for Procmail with links to assorted mailing lists dedicated to Procmail as well as various FAQ documents. http://www.spamassassin.org/ - The official site of the SpamAssassin project.

Commands:
Chapter 10. Optimizing routing The OpenShift Container Platform HAProxy router can be scaled or configured to optimize performance. 10.1. Baseline Ingress Controller (router) performance The OpenShift Container Platform Ingress Controller, or router, is the ingress point for ingress traffic for applications and services that are configured using routes and ingresses. When evaluating a single HAProxy router performance in terms of HTTP requests handled per second, the performance varies depending on many factors. In particular: HTTP keep-alive/close mode Route type TLS session resumption client support Number of concurrent connections per target route Number of target routes Back end server page size Underlying infrastructure (network/SDN solution, CPU, and so on) While performance in your specific environment will vary, Red Hat lab tests on a public cloud instance of size 4 vCPU/16GB RAM. A single HAProxy router handling 100 routes terminated by backends serving 1kB static pages is able to handle the following number of transactions per second. In HTTP keep-alive mode scenarios: Encryption LoadBalancerService HostNetwork none 21515 29622 edge 16743 22913 passthrough 36786 53295 re-encrypt 21583 25198 In HTTP close (no keep-alive) scenarios: Encryption LoadBalancerService HostNetwork none 5719 8273 edge 2729 4069 passthrough 4121 5344 re-encrypt 2320 2941 The default Ingress Controller configuration was used with the spec.tuningOptions.threadCount field set to 4 . Two different endpoint publishing strategies were tested: Load Balancer Service and Host Network. TLS session resumption was used for encrypted routes. With HTTP keep-alive, a single HAProxy router is capable of saturating a 1 Gbit NIC at page sizes as small as 8 kB. When running on bare metal with modern processors, you can expect roughly twice the performance of the public cloud instance above. This overhead is introduced by the virtualization layer in place on public clouds and holds mostly true for private cloud-based virtualization as well. The following table is a guide to how many applications to use behind the router: Number of applications Application type 5-10 static file/web server or caching proxy 100-1000 applications generating dynamic content In general, HAProxy can support routes for up to 1000 applications, depending on the technology in use. Ingress Controller performance might be limited by the capabilities and performance of the applications behind it, such as language or static versus dynamic content. Ingress, or router, sharding should be used to serve more routes towards applications and help horizontally scale the routing tier. For more information on Ingress sharding, see Configuring Ingress Controller sharding by using route labels and Configuring Ingress Controller sharding by using namespace labels . You can modify the Ingress Controller deployment using the information provided in Setting Ingress Controller thread count for threads and Ingress Controller configuration parameters for timeouts, and other tuning configurations in the Ingress Controller specification.

Commands: