mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 8. Creating the mortgage-process project A project is a container for assets such as data objects, business processes, guided rules, decision tables, and forms. The project that you are creating is similar to the existing Mortgage_Process sample project in Business Central. Procedure In Business Central, go to Menu Design Projects . Red Hat Process Automation Manager provides a default space called MySpace , as shown in the following image. You can use the default space to create and test example projects. Figure 8.1. Default space Click Add Project . Enter mortgage-process in the Name field. Click Configure Advanced Options and modify the GAV fields with the following values: Group ID : com.myspace Artifact ID : mortgage-process Version : 1.0.0 Click Add . The Assets view of the project opens. 8.1. Modifying the Mortgage_Process sample project The Mortgage_Process sample project consists of predefined data objects, guided decision tables, guided rules, forms, and a business process. Using the sample project provides a quick way to get acclimated with Red Hat Process Automation Manager. In a real business scenario, you would create all of the assets by providing data that is specific to your business requirements. Navigate to the Mortgage_Process sample project to view the predefined assets. Procedure In Business Central, go to Menu Design Projects . In the upper-right corner of the screen, click the arrow to Add Project and select Try Samples . Select Mortgage_Process and click Ok . The Assets view of the project opens. Click an asset that you want to modify. All of the assets can be edited to meet your project requirements. 8.2. Creating a project using archetypes Archetypes are projects that are installed in Apache Maven repositories and contain a specific template structure. You can also generate parameterized versions of the project templates using archetypes. When you use an archetype to create a project, it is added to the Git repository that is connected to your Red Hat Process Automation Manager installation. Prerequisites You have created an archetype and added it to the Archetypes page in the Business Central Settings . For information about creating archetypes, see the Guide to Creating Archetypes . You have set a default archetype in your space in Business Central. For more information about archetypes management, see Configuring Business Central settings and properties . Procedure In Business Central, go to Menu Design Projects . Select or create the space into which you want to add a new project from an archetype template. Click Add Project . Type the project name and description in the Name and Description fields. Click Configure Advanced Options . Select the Based on template checkbox. Select the archetype from drop-down options if required. The default archetype is selected that is already set in the space. Click Add . The Assets view of the project opens based on the selected archetype template.

Commands:
3.5.3. Updating Group Authentication The gpasswd command administers /etc/group and /etc/gshadow files. Note that this command works only if run by a group administrator. Who is a group administrator? A group administrator can add and delete users as well as set, change, or remove the group password. A group can have more than one group administrator. The root user can add group administrators with the gpasswd -A users groupname where users is a comma-separated list of existing users you want to be group administrators (without any spaces between commas). For changing a group's password, run the gpasswd command with the relevant group name. You will be prompted to type the new password of the group. Example 3.20. Changing a Group Password The password for the group crowd has been changed. You can also remove the password from the named group by using the -r option.

Commands:
gpasswd groupname
~]# gpasswd crowd Changing password for group crowd New password: Re-enter new password:
gpasswd -r schoolmates
Chapter 4. Enabling required repositories You need to enable certain RHEL repositories to have access to packages required for the SAP HANA installation. For more information on what repositories to enable based on your version of SAP HANA, architecture of your host, and your RHEL minor version, see RHEL for SAP Configurator . Note that if you used redhat_sap.sap_rhsm ansible role to register and subscribe your RHEL server to RHEL for SAP Solutions repositories you can skip this step and proceed to Installing RHEL System Roles for SAP . For more information, see sap_rhsm section on the Ansible Galaxy portal. Prerequisites root access. Procedure Disable all the repositories: To enable the repositories, refer to Enable the Required Repositories . Additional resources How to subscribe to Update Services for SAP Solutions on RHEL 8

Commands:
subscription-manager repos --disable="*"
4.180. mingw32-qpid-cpp 4.180.1. RHBA-2011:1740 - mingw32-qpid-cpp bug fix and enhancement update An updated mingw32-qpid-cpp package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The mingw32-qpid-cpp package provides a message broker daemon that receives, stores, and routes messages using runtime libraries for AMQP client applications developed using Qpid C++. Clients exchange messages with an AMQP message broker using the Advanced Message Queuing Protocol (AMQP), an open standard application layer protocol. The mingw32-qpid-cpp package has been upgraded to upstream version 0.12, which provides a number of bug fixes and enhancements over the version. (BZ# 706994 ) All users of mingw32-qpid-cpp are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
7.322. rtkit 7.322.1. RHSA-2013:1282 - Important: rtkit security update An updated rtkit package that fixes one security issue is now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link associated with the description below. RealtimeKit is a D-Bus system service that changes the scheduling policy of user processes/threads to SCHED_RR (that is, realtime scheduling mode) on request. It is intended to be used as a secure mechanism to allow real-time scheduling to be used by normal user processes. Security Fix CVE-2013-4326 It was found that RealtimeKit communicated with PolicyKit for authorization using a D-Bus API that is vulnerable to a race condition. This could have led to intended PolicyKit authorizations being bypassed. This update modifies RealtimeKit to communicate with PolicyKit via a different API that is not vulnerable to the race condition. All rtkit users are advised to upgrade to this updated package, which contains a backported patch to correct this issue.

Commands:
Chapter 12. Postfix Postfix is an open-source Mail Transport Agent ( MTA ), which supports protocols like LDAP, SMTP AUTH (SASL), and TLS. [11] In Red Hat Enterprise Linux, the postfix package provides postfix. Run the rpm -q postfix command to see if the postfix package is installed. If it is not installed, run the following command as the root user to install it: 12.1. Postfix and SELinux When Postfix is enabled, it runs confined by default. Confined processes run in their own domains, and are separated from other confined processes. If a confined process is compromised by an attacker, depending on SELinux policy configuration, an attacker's access to resources and the possible damage they can do is limited. The following example demonstrates the Postfix and related processes running in their own domain. This example assumes the postfix package is installed and that the Postfix service has been started: Run the getenforce command to confirm SELinux is running in enforcing mode: The getenforce command returns Enforcing when SELinux is running in enforcing mode. Run the service postfix start command as the root user to start postfix : Run the ps -eZ | grep postfix command to view the postfix processes: In the output above, the SELinux context associated with the Postfix master process is system_u:system_r:postfix_master_t:s0 . The second last part of the context, postfix_master_t , is the type for this process. A type defines a domain for processes and a type for files. In this case, the master process is running in the postfix_master_t domain. [11] Refer to the Postfix project page for more information.

Commands:
~]# yum install postfix
~]USD getenforce Enforcing
~]# service postfix start Starting postfix: [ OK ]
~]USD ps -eZ | grep postfix system_u:system_r:postfix_master_t:s0 1651 ? 00:00:00 master system_u:system_r:postfix_pickup_t:s0 1662 ? 00:00:00 pickup system_u:system_r:postfix_qmgr_t:s0 1663 ? 00:00:00 qmgr
Chapter 8. System and Services systemd systemd is a system and service manager for Linux, and replaces SysV and Upstart used in releases of Red Hat Enterprise Linux. systemd is compatible with SysV and Linux Standard Base init scripts. systemd offers, among others, the following capabilities: Aggressive parallelization capabilities; Use of socket and D-Bus activation for starting services; On-demand starting of daemons; Managing of control groups; Creating of system state snapshots and restoring of the system state. For detailed information about systemd and its configuration, see System Administrator's Guide .

Commands:
Chapter 4. Integrating Serverless with OpenShift Pipelines Integrating Serverless with OpenShift Pipelines enables CI/CD pipeline management for Serverless services. Using this integration, you can automate the deployment of your Serverless services. 4.1. Prerequisites You have access to the cluster with cluster-admin privileges. The OpenShift Serverless Operator and Knative Serving are installed on the cluster. You have installed the OpenShift Pipelines Operator on the cluster. 4.2. Creating a service deployed by OpenShift Pipelines Using the OpenShift Container Platform web console, you can create a service that the OpenShift Pipelines deploys. Procedure In the OpenShift Container Platform web console Developer perspective, navigate to +Add and select the Import from Git option. In the Import from Git dialog, specify project metadata by doing the following: Specify the Git repository URL. If necessary, specify the context directory. This is the subdirectory inside the repository that contains the root of application source code. Optional: Specify the application name. By default, the repository name is used. Select the Serverless Deployment resource type. Select the Add pipeline checkbox. The pipeline is automatically selected based on the source code and its visualization is shown on the scheme. Specify any other relevant settings. Click Create to create the service. After the service creation starts, you are navigated to the Topology screen, where your service and the related trigger are visualized and where you can interact with them. Optional: Verify that the pipeline has been created and that the service is being built and deployed by navigating to the Pipelines page: To see the details of the pipeline, click the pipeline on the Pipelines page. To see the details about the current pipeline run, click the name of the run on the Pipelines page. 4.3. Additional resources Documentation for Red Hat OpenShift Pipelines

Commands:
7.141. mcelog 7.141.1. RHBA-2013:0285 - mcelog bug fix and enhancement update Updated mcelog packages that fix numerous bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The mcelog package contains a daemon that collects and decodes Machine Check Exception (MCE) data on AMD64 and Intel 64 machines. Note The mcelog packages have been upgraded to upstream version 0.6, which provides a number of bug fixes and enhancements over the version. (BZ#795931) Bug Fixes BZ#851406 The mcelog(8) man page contained incorrect information about usage of the "--supported" flag. This man page has been updated and the information is correct now. BZ#871249 Previously, the mcelog daemon ignored the 15h microarchitecture family of AMD processors and did not report the Machine Check Exception (MCE) errors. Consequently, reported errors were unavailable to system administrators. The 15h microarchitecture family of AMD processors has been included to the list of supported processors and mcelog reports MCE errors correctly in this case. Enhancement BZ#740915 This enhancement adds support for the Intel Core i5 and i7 processors to the mcelog packages. All users of mcelog are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
14.7. Comparison of DHCPv6 to radvd Dynamic Host configuration for IPv4 is mainly applied with DHCPv4. However, for IPv6 the following options are available: Manually Using the radvd daemon Using the DHCPv6 server Manually Manual addressing is always available. You can assign IPv6 addresses to a system using the tools described in Section 3.3.6, "Connecting to a Network Using nmcli" , Section 7.2, "Configure Bonding Using the Text User Interface, nmtui" , Section 3.6, "Configuring IP Networking with ip Commands" . Using the radvd Daemon A standards-compliant IPv6 network must provide router advertisements, thus IPv6 configuration options can be applied running the router advertisement daemon (radvd). The router advertisements provide the on-link information on which prefix is actually available locally on a physical LAN. On top of router advertisements, you can select either manual IPv6 configuration, automatic IPv6 configuration through router advertisements or the Dynamic Host Configuration Protocol (DHCPv6). For more details on configuring the radvd daemon, see Section 14.6, "Configuring the radvd daemon for IPv6 routers" . Using the DHCPv6 Server When address management is under central administration, the user can set up a DHCPv6 server. The availability of DHCPv6 is announced by flags in the router advertisement packets. Table 14.1. Comparison of DHCPv6 to radvd DHCPv6 radvd Guarantee random addresses to protect privacy. Provide information on a default gateway. Send further network configuration options to clients. For example, Network Time Protocol (NTP) servers, Session Initiation Protocol (SIP) servers, Preboot Execution Environment (iPXE) configuration. Map MAC addresses to IPv6 addresses. Note To correctly configure a network, use DHCPv6 in conjunction with radvd, as only router advertisements provide information on a default gateway.

Commands:
Chapter 1. Overview Product Life Cycle Note Red Hat Enterprise Linux 6 is now in the Maintenance Support 2 phase of the product life cycle. New functionality and new hardware enablement are not planned for availability in this phase. The updates are limited to qualified critical security fixes and business-impacting urgent issues. Please refer to Red Hat Enterprise Linux Life Cycle for more information. In-place Upgrade from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 As Red Hat Enterprise Linux subscriptions are not tied to a particular release, existing customers can update their Red Hat Enterprise Linux 6 infrastructure to Red Hat Enterprise Linux 7 at any time, free of charge, to take advantage of recent upstream innovations. An in-place upgrade offers a way of upgrading a system to a new major release of Red Hat Enterprise Linux by replacing the existing operating system. To perform an in-place upgrade, use the Preupgrade Assistant , a utility that checks the system for upgrade issues before running the actual upgrade, and that also provides additional scripts for the Red Hat Upgrade Tool . When you have solved all the problems reported by the Preupgrade Assistant , use the Red Hat Upgrade Tool to upgrade the system. For details regarding procedures and supported scenarios, see the Upgrading from RHEL 6 to RHEL 7 guide. Note that the Preupgrade Assistant and the Red Hat Upgrade Tool are available in the Red Hat Enterprise Linux 6 Extras repository . For instructions on upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 8 see the Upgrading from RHEL 6 to RHEL 8 document. If you are using CentOS Linux 6 or Oracle Linux 6, you can convert your operating system to RHEL 6 using the convert2rhel utility prior to upgrading to RHEL 7 or RHEL 8. For instructions, see How to convert from CentOS Linux or Oracle Linux to RHEL . Red Hat Insights Since Red Hat Enterprise Linux 6.7, the Red Hat Insights service is available. Red Hat Insights is a proactive service designed to enable you to identify, examine, and resolve known technical issues before they affect your deployment. Insights leverages the combined knowledge of Red Hat Support Engineers, documented solutions, and resolved issues to deliver relevant, actionable information to system administrators. The service is hosted and delivered through the Customer Portal or through Red Hat Satellite. To register your systems, follow the Getting Started Guide for Insights . Red Hat Customer Portal Labs Red Hat Customer Portal Labs is a set of tools in a section of the Customer Portal available at https://access.redhat.com/labs/ . The applications in Red Hat Customer Portal Labs can help you improve performance, quickly troubleshoot issues, identify security problems, and quickly deploy and configure complex applications. Some of the most popular applications are: Spectre And Meltdown Detector Registration Assistant Red Hat Code Browser Kickstart Generator Red Hat Product Certificates Load Balancer Configuration Tool Red Hat Network (RHN) System List Exporter Log Reaper Product Life Cycle Checker JVM Options Configuration Tool

Commands:
7.68. grub 7.68.1. RHBA-2015:1426 - grub bug fix update Updated grub packages that fix one bug are now available for Red Hat Enterprise Linux 6. The grub packages provide Grand Unified Boot Loader (GRUB), a boot loader capable of booting a wide variety of operating systems. Bug Fix BZ# 1177321 , BZ# 1206542 Previously, during the Pre-Boot Execution Environment (PXE) booting of a client configured to use the UEFI booting and the IP version 6 (IPv6) protocol, the client failed to display the expected selection menu as configured in the grub.cfg file and switched to the GRUB shell instead. With this update, the bug has been fixed so that the PXE boots the client and displays the operating system selection menu as configured in grub.cfg. Users of grub are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Deploying a Block Storage service custom back end The Red Hat OpenStack Platform director installs and manages a complete, Enterprise-grade OpenStack deployment with minimal manual configuration. For more information about the director, see the Installing and managing Red Hat OpenStack Platform with director guide. The Openstack environment that director creates is called the overcloud. The overcloud contains all the components that provide services to end users, including Block Storage. This document provides guidance about how to deploy a custom back end to the Block Storage service (cinder) on the overcloud. By default, the Block Storage service is installed on Controller nodes. Prerequisites You have already deployed the overcloud with the director. The overcloud has a functioning Block Storage service. You are familiar with Block Storage concepts and configuration. For more information about Block Storage, see Block Storage and Volumes in the Configuring persistent storage guide. Warning This procedure has been tested successfully in limited use cases. Ensure that you test your planned deployment on a non-production environment first. If you have any questions, contact Red Hat support.

Commands:
14.5. Memory Management Elements The API provides two configuration settings for a host's memory management. Kernel SamePage Merging (KSM) reduces references to memory pages from multiple identical pages to a single page reference. This helps with optimization for memory density. KSM uses the ksm element. Example 14.4. Setting KSM memory management Transparent Hugepage support expands the size of memory pages beyond the standard 4kB limit. This reduces memory consumption and increases host performance. Transparent Hugepage support uses the transparent_hugepages element. Example 14.5. Setting Transparent Hugepage memory management Availability of Transparent Hugepage support is found in the capabilities collection.

Commands:
PUT /ovirt-engine/api/hosts/2ab5e1da-b726-4274-bbf7-0a42b16a0fc3 HTTP/1.1 Accept: application/xml Content-Type: application/xml <host id="2ab5e1da-b726-4274-bbf7-0a42b16a0fc3" href="/ovirt-engine/api/hosts/2ab5e1da-b726-4274-bbf7-0a42b16a0fc3"> <ksm>true</ksm> </host>
PUT /ovirt-engine/api/hosts/2ab5e1da-b726-4274-bbf7-0a42b16a0fc3 HTTP/1.1 Accept: application/xml Content-Type: application/xml <host id="2ab5e1da-b726-4274-bbf7-0a42b16a0fc3" href="/ovirt-engine/api/hosts/2ab5e1da-b726-4274-bbf7-0a42b16a0fc3"> <transparent_hugepages>true</transparent_hugepages> </host>
Chapter 4. User Authentication User authentication enables you to verify the identity of users by adding usernames and assigning them to security roles. In AMQ Broker 7, this process is similar to AMQ 6. However, there are some differences in terminology, configuration file locations, and configuration syntax. Once you understand the differences, there are several methods you can use to configure user access to your broker instance. 4.1. User Authentication Changes In both AMQ Broker 7 and AMQ 6, authentication is provided by pluggable login modules based on the Java Authentication and Authorization Service (JAAS). However, groups in AMQ 6 are now called roles in AMQ Broker 7. In addition, the names and locations of the login modules have changed in AMQ Broker 7. Login Module Location in AMQ 6 Location in AMQ Broker 7 Users etc/users.properties BROKER_INSTANCE_DIR /etc/artemis-users.properties Roles (groups) etc/groups.properties BROKER_INSTANCE_DIR /etc/artemis-roles.properties The syntax for adding users and roles is also different. In AMQ 6 Non-privileged users could be added and assigned a password and security role in the users.properties file: In AMQ Broker 7 Users and roles are assigned in separate login modules. You add users in the artemis-users.properties file: You assign users to a security role in the artemis-roles.properties file: 4.2. How User Authentication is Configured You can access the AMQ 7 broker instance using the default username and password that you created when you created the broker instance. To enable additional users to access the broker instance, you can configure user authentication for the broker using any of the following methods: Authentication Method Description Guest Authentication Enables anonymous access. In this configuration, any user who connects without credentials or with the wrong credentials will be authenticated automatically and assigned a specific user and role. For more information, see Enabling Guest Access in Configuring AMQ Broker . Basic User and Password Authentication For each user, you must define a username and password and assign a security role. Users can only access the broker instance using these credentials. For more information, see Adding Users in Configuring AMQ Broker . Certificate-Based Authentication Users are authenticated using SSL certificates. For more information, see Adding Certificate-based Authentication in Configuring AMQ Broker . LDAP Authentication Users are authenticated and authorized by checking the credentials against user data stored in a central X.500 directory server. For more information, see Using LDAP for Authentication in Configuring AMQ Broker .

Commands:
USER = PASSWORD , ROLE
USER = PASSWORD
ROLE = USER