mtpti5iD/redhat-docs_dataset huggingface dataset:
Part II. Getting started with process services in Red Hat Process Automation Manager As a business rules and processes developer, you can use Business Central in Red Hat Process Automation Manager or the Red Hat Process Automation Manager BPMN modeler in VS Code to design business processes to meet specific business requirements. Red Hat Process Automation Manager provides sample projects in Business Central that contain business assets for reference purposes. This document describes how to create a new mortgage process project, data objects, and business process to familiarize yourself with Business Central and the process designer. You will then refer to the Mortgage_Process sample project included in Business Central to review the sample project's business rules, decision tables, and forms. You will build and deploy the Mortgage_Process sample project and execute the project's defined functionality. Prerequisites Red Hat JBoss Enterprise Application Platform 7.4 is installed. For details, see the Red Hat JBoss Enterprise Application Platform 7.4 Installation Guide . Red Hat Process Automation Manager is installed and configured with KIE Server. For more information, see Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 . Red Hat Process Automation Manager is running and you can log in to Business Central with the developer role. For more information, see Planning a Red Hat Process Automation Manager installation .

Commands:
4.34. cpufrequtils 4.34.1. RHBA-2011:1224 - cpufrequtils bugfix update An updated cpufrequtils package that fixes a bug is now available for Red Hat Enterprise Linux 6. The cpufrequtils package contains utilities that can be used to control the cpufreq interface provided by the kernel on hardware that supports CPU frequency scaling. Bug Fix BZ# 675734 Prior to this update, the cpufreq-aperf utility did not run on 32-bit systems due to an incorrect argument passed to the read() call. This problem has been fixed: the buffer size is now used instead of the size of the pointer and the cpufreq-aperf utility runs as expected. All users of cpufrequtils are advised to upgrade to this updated package, which resolves this bug.

Commands:
Chapter 4. Managing Virtual Data Optimizers using the Web Console 4.1. Creating a Virtual Data Optimizer using the Web Console Follow these steps to create a new VDO device. Log in to the Web Console. Click the hostname Storage . Click the + button beside VDO Devices . The Create VDO Device window opens. Figure 4.1. VDO Devices Figure 4.2. Create VDO Device window Specify a Name for the new VDO device. Specify the Disk to use for the new VDO device. Specify the Logical Size for the new VDO device. Specify the Index Memory size for the new VDO device. Check any Options you want the new VDO device to use. Click Create . 4.2. Growing the logical size of a VDO device using the Web Console Follow these steps to increase the logical size (the amount of data it can store by using compression and deduplication) of a VDO device. Log in to the Web Console. Click the hostname Storage . The Storage Dashboard page opens. Under VDO Devices , click the VDO device. The VDO Device Overview page opens. Click Grow . Figure 4.3. VDO device summary The Grow logical size of device window opens. Drag the slider or enter a numeric value to set the new logical size of the VDO device, and click Grow . 4.3. Disabling compression on a VDO device using the Web Console Follow these steps to prevent future writes to the VDO device being compressed. This does not affect the compression of existing data on the VDO device. Log in to the Web Console. Click the hostname Storage . The Storage Dashboard page opens. Under VDO Devices , click the VDO device. The VDO Device Overview page opens. Locate the Compression toggle. Figure 4.4. The Compression toggle Click the Compression toggle under the device summary so that OFF is displayed. 4.4. Disabling deduplication on a VDO device using the Web Console Follow these steps to prevent future writes to the VDO device being checked for duplication. This does not affect the deduplication of existing data on the VDO device. Log in to the Web Console. Click the hostname Storage . The Storage Dashboard page opens. Under VDO Devices , click the VDO device. The VDO Device Overview page opens. Locate the Deduplication toggle. Figure 4.5. The Deduplication toggle Click the Deduplication toggle under the device summary so that OFF is displayed. 4.5. Stopping a VDO device using the Web Console Follow these steps to stop a VDO device for maintenance operations or deletion. Prerequisites Stop any volumes running on the VDO device. Procedure Log in to the Web Console. Click the hostname Storage . The Storage Dashboard page opens. Under VDO Devices , click the VDO device. The VDO Device Overview page opens. Click Stop . Figure 4.6. The VDO device 4.6. Deleting a VDO device using the Web Console Follow these steps to delete a VDO device. Prerequisites Stop any volumes running on the VDO device. Stop the VDO device. Procedure Log in to the Web Console. Click the hostname Storage . The Storage Dashboard page opens. Under VDO Devices , click the VDO device. The VDO Device Overview page opens. Click Delete . Figure 4.7. The VDO device

Commands:
Preface Red Hat OpenShift Data Foundation 4.9 supports deployment on existing Red Hat OpenShift Container Platform (RHOCP) vSphere clusters in connected or disconnected environments along with out-of-the-box support for proxy environments. Note Both internal and external OpenShift Data Foundation clusters are supported on VMware vSphere. See Planning your deployment and Preparing to deploy OpenShift Data Foundation for more information about deployment requirements. To deploy OpenShift Data Foundation, start with the requirements in the Preparing to deploy OpenShift Data Foundation chapter and then follow any one of the below deployment process for your environment: Internal mode Deploy using dynamic storage devices Deploy using local storage devices Deploy standalone Multicloud Object Gateway component External mode

Commands:
2.2. Performance Older virtualization versions supported only a single CPU. As a result, virtual machines experienced noticeable performance limitations. This created a long-lasting misconception that virtualization solutions are slow. This is no longer the case. Modern virtualization technology has greatly improved the speed of virtual machines. Benchmarks show that virtual machines can run typical server applications nearly as efficiently as bare-metal systems: Red Hat Enterprise Linux 6.4 and KVM recorded an industry-leading TPC-C benchmark with an IBM DB2 database running in an entirely virtualized x86 environment and delivering 88% of bare-metal performance. Due to resource demands, databases have previously been reserved for bare-metal deployments only. The industry standard SAP Sales and Distribution (SD) Standard Application Benchmark found that Red Hat Enterprise Linux 6.2 and KVM performs at the virtualization efficiency of 85% compared to a bare-metal system running on identical hardware. Red Hat Enterprise Linux 6.1 and KVM achieved record-setting virtualization performance in the SPECvirt_sc2010 benchmark recorded by the Standard Performance Evaluation Corporation (SPEC), setting the best virtual performance mark of any published SPECvirt result. The SPECvirt_sc2010 metric measures the end-to-end performance of system components in virtualized data center servers. Note For more information on performance tuning for virtualization, refer to the Red Hat Enterprise Linux 6 Virtualization Tuning and Optimization Guide .

Commands:
8.6. Create a New Web Service View Model Important Please note that Web Service View Modeling has been deprecated. 8.6.1. Create a New Web Service View Model To create a new empty web service view model: Launch the New Model Wizard . Specify a unique model name. Select Web Service option from Model Class drop-down menu. Select View Model from Model Type drop-down menu. Click Finish . Note You can change the target location (i.e. project or folder) by selecting the Browse... button and selecting a project or folder within your workspace. In addition to creating a new empty web service view model, the following builder options are available: Copy from existing model of the same model class. Build from existing WSDL file(s) or URL. 8.6.2. Copy an Existing Web Service View Model This builder option performs a structural copy of the contents of an existing model to a newly defined model. You can choose a full copy or select individual model components for copy. To create a new Web Service view model by copying contents from another web service view model, complete first 4 steps from the Create a New Web Service View Model section and continue with these additional steps: Select the model builder labeled Copy from existing model of the same model class and click > . The Copy Existing Model dialog will be displayed. Select an existing Web Service view model from the workspace using the browse button. Select the Copy all descriptions option if desired. Click Finish . 8.6.3. Create a Web Service View Model from a WSDL File or URL This builder option creates a Web service model based on a user defined WSDL file and its referenced schemas. In addition, applicable XML schema files and XML View document models (optional) are created. To create a new Web Service View Model, complete first 4 steps from the Create a New Web Service View Model section and continue with these additional steps: Select the model builder labeled Build from existing WSDL file(s) or URL and click > . Complete the steps in the wizard. The remaining steps are the same as the process covered in Import WSDL Into Web Service at Section 9.10.1, "Import WSDL Into Web Service" . 8.6.4. Create a Web Service View Model from XML Document View Models Web Service models and their corresponding Interfaces and Operations can be generated in Teiid Designer from XML View model components. Namely, XML View Documents and XML View Document roots. To create a new Web service model from XML components: Select either a single XML Document or single XML Document root in the Model Explorer View. Right-click select Modeling > Create Web Service action . Fill in missing properties in Web Service Generation Wizard . Click Finish to generate model. When model generation is complete, a confirmation dialog is displayed. Click OK . Note Users can change the Web Service Model and Interface Name values (via "..." buttons) to use existing Web service model components. This will create a new operation in an existing model.

Commands:
7.5. Enabling Revocation Checking Revocation checking means that a Certificate System subsystem verifies that a certificate is both valid and not revoked when an agent or administrator attempts to access the instance's secure interfaces. This leverages a local OCSP service (either a CA's internal OCSP service or a separate OCSP responder) to check the revocation status of the certificate. OCSP configuration is covered in Section 7.6, "Using the Online Certificate Status Protocol (OCSP) Responder" . See Enabling Automatic Revocation Checking on the CA in the Red Hat Certificate System Planning, Installation, and Deployment Guide . See Enabling Certificate Revocation Checking for Subsystems in the Red Hat Certificate System Planning, Installation, and Deployment Guide .

Commands:
Chapter 30. Removing a Path to a Storage Device If you are removing a path to a device that uses multipathing (without affecting other paths to the device), then the general procedure is as follows: Procedure 30.1. Removing a Path to a Storage Device Remove any reference to the device's path-based name, like /dev/sd or /dev/disk/by-path or the major:minor number, in applications, scripts, or utilities on the system. This is important in ensuring that different devices added in the future will not be mistaken for the current device. Take the path offline using echo offline > /sys/block/sda/device/state . This will cause any subsequent I/O sent to the device on this path to be failed immediately. Device-mapper-multipath will continue to use the remaining paths to the device. Remove the path from the SCSI subsystem. To do so, use the command echo 1 > /sys/block/ device-name /device/delete where device-name may be sde , for example (as described in Procedure 29.1, "Ensuring a Clean Device Removal" ). After performing Procedure 30.1, "Removing a Path to a Storage Device" , the path can be safely removed from the running system. It is not necessary to stop I/O while this is done, as device-mapper-multipath will re-route I/O to remaining paths according to the configured path grouping and failover policies. Other procedures, such as the physical removal of the cable, followed by a rescan of the SCSI bus to cause the operating system state to be updated to reflect the change, are not recommended. This will cause delays due to I/O timeouts, and devices may be removed unexpectedly. If it is necessary to perform a rescan of an interconnect, it must be done while I/O is paused, as described in Chapter 34, Scanning Storage Interconnects .

Commands:
2.3. Block Allocation Issues This section provides a summary of issues related to block allocation in GFS2 file systems. Even though applications that only write data typically do not care how or where a block is allocated, a little knowledge about how block allocation works can help you optimize performance. 2.3.1. Leave Free Space in the File System When a GFS2 file system is nearly full, the block allocator starts to have a difficult time finding space for new blocks to be allocated. As a result, blocks given out by the allocator tend to be squeezed into the end of a resource group or in tiny slices where file fragmentation is much more likely. This file fragmentation can cause performance problems. In addition, when a GFS2 file system is nearly full, the GFS2 block allocator spends more time searching through multiple resource groups, and that adds lock contention that would not necessarily be there on a file system that has ample free space. This also can cause performance problems. For these reasons, it is recommended that you not run a file system that is more than 85 percent full, although this figure may vary depending on workload. 2.3.2. Have Each Node Allocate Its Own Files, If Possible Due to the way the distributed lock manager (DLM) works, there will be more lock contention if all files are allocated by one node and other nodes need to add blocks to those files. In GFS (version 1), all locks were managed by a central lock manager whose job was to control locking throughout the cluster. This grand unified lock manager (GULM) was problematic because it was a single point of failure. GFS2's replacement locking scheme, DLM, spreads the locks throughout the cluster. If any node in the cluster goes down, its locks are recovered by the other nodes. With DLM, the first node to lock a resource (like a file) becomes the "lock master" for that lock. Other nodes may lock that resource, but they have to ask permission from the lock master first. Each node knows which locks for which it is the lock master, and each node knows which node it has lent a lock to. Locking a lock on the master node is much faster than locking one on another node that has to stop and ask permission from the lock's master. As in many file systems, the GFS2 allocator tries to keep blocks in the same file close to one another to reduce the movement of disk heads and boost performance. A node that allocates blocks to a file will likely need to use and lock the same resource groups for the new blocks (unless all the blocks in that resource group are in use). The file system will run faster if the lock master for the resource group containing the file allocates its data blocks (it is faster to have the node that first opened the file do all the writing of new blocks). 2.3.3. Preallocate, If Possible If files are preallocated, block allocations can be avoided altogether and the file system can run more efficiently. Newer versions of GFS2 include the fallocate (1) system call, which you can use to preallocate blocks of data.

Commands:
Chapter 6. Additional Resources This chapter provides references to other relevant sources of information about Red Hat Software Collections 3.0 and Red Hat Enterprise Linux. 6.1. Red Hat Product Documentation The following documents are directly or indirectly relevant to this book: Red Hat Software Collections 3.0 Packaging Guide - The Packaging Guide for Red Hat Software Collections explains the concept of Software Collections, documents the scl utility, and provides a detailed explanation of how to create a custom Software Collection or extend an existing one. Red Hat Developer Toolset 7.0 Release Notes - The Release Notes for Red Hat Developer Toolset document known problems, possible issues, changes, and other important information about this Software Collection. Red Hat Developer Toolset 7.0 User Guide - The User Guide for Red Hat Developer Toolset contains more information about installing and using this Software Collection. Using Red Hat Software Collections Container Images - This book provides information on how to use container images based on Red Hat Software Collections. The available container images include applications, daemons, databases, as well as the Red Hat Developer Toolset container images. The images can be run on Red Hat Enterprise Linux 7 Server and Red Hat Enterprise Linux Atomic Host. Get Started with Containers - This guide contains a comprehensive overview of information about building and using docker-formatted container images on Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux Atomic Host. Using and Configuring Red Hat Subscription Manager - The Using and Configuring Red Hat Subscription Manager book provides detailed information on how to register Red Hat Enterprise Linux systems, manage subscriptions, and view notifications for the registered systems. Red Hat Enterprise Linux 6 Deployment Guide - The Deployment Guide for Red Hat Enterprise Linux 6 provides relevant information regarding the deployment, configuration, and administration of this system. Red Hat Enterprise Linux 7 System Administrator's Guide - The System Administrator's Guide for Red Hat Enterprise Linux 7 provides information on deployment, configuration, and administration of this system. 6.2. Red Hat Developer Blog Red Hat Developer Blog content is directed to designers and developers of applications based on Red Hat technologies. It contains links to product team blogs and other relevant internal and external resources. Its goal is to inform and engage the developer community with up-to-date information, best practices, opinion, product and program announcements as well as pointers to sample code and other resources. 6.3. Red Hat Developers Portal Red Hat Developers Portal provides an overview of Red Hat Software Collections and offers getting started content, including Hello world! examples.

Commands:
12.9. Sub-Collections 12.9.1. Files Sub-Collection The files sub-collection under each storage domain provides a way for clients to list available files. This sub-collection is specifically targeted to ISO storage domains, which contain ISO images and virtual floppy disks (VFDs) that an administrator uploads through Red Hat Virtualization Manager. The addition of a CD-ROM device to a VM requires an ISO image from the files sub-collection of an ISO storage domain. Example 12.15. Listing the files sub-collection of an ISO storage domain Like other resources, files have opaque id and href attributes. The name element contains the filename.

Commands:
GET /ovirt-engine/api/storagedomains/00f0d9ce-da15-4b9e-9e3e-3c898fa8b6da/files HTTP/1.1 Accept: application/xml HTTP/1.1 200 OK Content-Type: application/xml <files> <file id="en_winxp_pro_with_sp2.iso" href="/ovirt-engine/api/storagedomains/00f0d9ce-da15-4b9e-9e3e-3c898fa8b6da/files/ en_winxp_pro_with_sp2.iso"> <name>en_winxp_pro_with_sp2.iso</name> <type>iso</type> <storage_domain id="00f0d9ce-da15-4b9e-9e3e-3c898fa8b6da" href="/ovirt-engine/api/storagedomains/00f0d9ce-da15-4b9e-9e3e-3c898fa8b6da"/> </file> <file id="boot.vfd" href="/ovirt-engine/api/storagedomains/00f0d9ce-da15-4b9e-9e3e-3c898fa8b6da/files/ boot.vfd"> <name>boot.vfd</name> <type>vfd</type> <storage_doman id="00f0d9ce-da15-4b9e-9e3e-3c898fa8b6da" href="/ovirt-engine/api/storagedomains/00f0d9ce-da15-4b9e-9e3e-3c898fa8b6da"/> </file> </files>
Part I. Designing a decision service using DMN models As a business analyst or business rules developer, you can use Decision Model and Notation (DMN) to model a decision service graphically. The decision requirements of a DMN decision model are determined by a decision requirements graph (DRG) that is depicted in one or more decision requirements diagrams (DRDs). A DRD can represent part or all of the overall DRG for the DMN model. DRDs trace business decisions from start to finish, with each decision node using logic defined in DMN boxed expressions such as decision tables. Red Hat Decision Manager provides runtime support for DMN 1.1, 1.2, 1.3, and 1.4 models at conformance level 3, and design support for DMN 1.2 models at conformance level 3. You can design your DMN models directly in Business Central or with the Red Hat Decision Manager DMN modeler in VS Code, or import existing DMN models into your Red Hat Decision Manager projects for deployment and execution. Any DMN 1.1 and 1.3 models (do not contain DMN 1.3 features) that you import into Business Central, open in the DMN designer, and save are converted to DMN 1.2 models. For more information about DMN, see the Object Management Group (OMG) Decision Model and Notation specification . For a step-by-step tutorial with an example DMN decision service, see Getting started with decision services .

Commands:
7.8. Additional Resources There are several aspects to firewalls and the Linux Netfilter subsystem that could not be covered in this chapter. For more information, refer to the following resources. 7.8.1. Installed Documentation The Reference Guide has a comprehensive chapter on iptables , including definitions for all command options. The iptables man page contains a brief summary of the various options, as well. A list of common services and their port numbers can be found in Appendix C, Common Ports and in /etc/services .

Commands:
8.258. wget 8.258.1. RHBA-2014:1408 - wget bug fix update Updated wget packages that fix several bugs are now available for Red Hat Enterprise Linux 6. GNU Wget is a file retrieval utility which can use either the HTTP, HTTPS, or FTP protocol. Wget provides various useful features, such as the ability to work in the background while the user is logged out, recursive retrieval of directories, file name wildcard matching, or updating files in dependency on file timestamp comparison. Bug Fixes BZ# 909604 Prior to this update, Wget was missing support for Server Name Indication (SNI). As a consequence, Wget was unable to successfully validate certificates from a server using SNI, even if the certificate was valid. The SNI support has been ported to the Wget distributed in Red Hat Enterprise Linux 6, and Wget is now able to successfully validate certificates from any server using SNI, provided the certificate is valid. BZ# 960137 An error in the Wget code prevented Wget from parsing all web links in retrieved pages correctly. Consequently, some links were not followed and pages not retrieved when doing recursive retrieving. The source code has been fixed to parse web links correctly, and all valid links found in the downloaded pages are now parsed and followed correctly in the aforementioned scenario. BZ# 873216 Due to potential resource leaks in the Wget source code, Wget could leak memory in some situations. With this update, the source code has been patched to free resources that could potentially leak, thus fixing this bug. Users of wget are advised to upgrade to these updated packages, which fix these bugs.

Commands: