mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix D. Using AMQ Broker with the examples The AMQ .NET examples require a running message broker with a queue named amq.topic . Use the procedures below to install and start the broker and define the queue. D.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . D.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... D.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named amq.topic . USD <broker-instance-dir> /bin/artemis queue create --name amq.topic --address amq.topic --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. D.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2021-08-24 14:23:27 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name amq.topic --address amq.topic --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
Chapter 69. Using list and map collections in test scenarios The test scenarios designer supports list and map collections for both DMN-based as well as rules-based test scenarios. You can create and define a collection like a list or a map as the value of a particular cell in both GIVEN and EXPECT columns. For rules-based test scenarios, the designer supports the following collections: java.util.Collection java.util.List java.util.ArrayList java.util.LinkedList java.util.Map java.util.HashMap java.util.LinkedHashMap java.util.TreeMap Note The test scenarios designer does not support java.util.Set collections. For map entries, you must set the entry key as a String data type. To pass the parameter in the EXPECT column of Rule-based collection editor use the actualValue keyword whereas use the ? keyword in DMN-based test scenario. Procedure Set the column type first (use a field whose type is a list or a map). Double click a cell in the column to input a value. To create the list values for the data objects in the collection editor popup: Select Create List . Click Add new item . Enter the required value and click the check icon to save each collection item that you add. Click Save . To edit an item from the collection, click the pencil icon in the collection popup editor. Click Save changes . To delete an item from the collection, click the bin icon in the collection popup editor. To define the list values for the data objects in the collection editor popup: Select Define List . Use the MVEL or FEEL expression to define a list value in the text field. Rule-based test scenario uses MVEL expression language and DMN-based test scenario uses FEEL expression language. Click Save . To create the map values for the data objects in the collection editor popup: Select Create Map . Click Add new item . Enter the required value and click the check icon to save each collection item that you add. Click Save . To edit an item from the collection, click the pencil icon in the collection popup editor. Click Save changes . To delete an item from the collection, click the bin icon in the collection popup editor. To define the map values for the data objects in the collection editor popup: Select Define Map . Use the MVEL or FEEL expression to define a map value in the text field. Rule-based test scenario uses MVEL expression language and DMN-based test scenario uses FEEL expression language. Click Save . Note To define the map values for DMN-based test scenario, you can add a fact and use the FEEL expression, instead of using the collection editor. Click Remove to delete the entire collection.

Commands:
Chapter 2. Connectivity Link features Connectivity Link includes the following main features to secure, protect, connect, and observe your cloud applications and APIs: Multicloud application connectivity DNS provider integrations: Amazon Web Services Route 53 Google Cloud DNS MicroSoft Azure DNS High availability and disaster recovery Global load balancing Application portability Application connectivity configuration Endpoint health and status checks Automatic TLS certificate generation Universal authentication Kubernetes ingress policy management Global DNS policy TLS policy Auth policy Rate limiting policy Traffic weighting and distribution User role-based design Multicluster administration Observability dashboards and alerts OpenShift web console dynamic plug-in Composable API management API designer and API registry Design, test, and deploy APIs API security and governance Advanced metrics collection Flexible integration with open source tooling API-level policies for authentication, authorization, and rate limiting Additional resources Kuadrant project website Apicurio project website

Commands:
10.2. Is Your Hardware Compatible? Red Hat Enterprise Linux 7 (big endian) is compatible with IBM Power Systems servers which use the POWER7, POWER8, and POWER9 processor series. POWER6 processors and older are no longer supported. Red Hat Enterprise Linux also offers a little endian variant for IBM Power Systems. This variant is currently compatible with POWER8 and POWER9 processors, and is supported as a KVM guest on Red Hat Enterprise Virtualization for Power, on PowerVM, and PowerNV (bare metal). The most recent list of supported hardware can be found in the Red Hat Hardware Compatibility List , available online at https://access.redhat.com/ecosystem/search/#/category/Server . Also see Red Hat Enterprise Linux technology capabilities and limits for general information about system requirements.

Commands:
4.5. Available Network Services While user access to administrative controls is an important issue for system administrators within an organization, keeping tabs on which network services are active is of paramount importance to anyone who administers and operates a Linux system. Many services under Red Hat Enterprise Linux behave as network servers. If a network service is running on a machine, then a server application called a daemon is listening for connections on one or more network ports. Each of these servers should be treated as potential avenue of attack. 4.5.1. Risks To Services Network services can pose many risks for Linux systems. Below is a list of some of the primary issues: Denial of Service Attacks (DoS) - By flooding a service with requests, a denial of service attack can bring a system to a screeching halt as it tries to log and answer each request. Script Vulnerability Attacks - If a server is using scripts to execute server-side actions, as Web servers commonly do, a cracker can mount an attack on improperly written scripts. These script vulnerability attacks can lead to a buffer overflow condition or allow the attacker to alter files on the system. Buffer Overflow Attacks - Services which connect to ports numbered 0 through 1023 must run as an administrative user. If the application has an exploitable buffer overflow, an attacker could gain access to the system as the user running the daemon. Because exploitable buffer overflows exist, crackers use automated tools to identify systems with vulnerabilities, and once they have gained access, they use automated rootkits to maintain their access to the system. Note The threat of buffer overflow vulnerabilities is mitigated in Red Hat Enterprise Linux by ExecShield , an executable memory segmentation and protection technology supported by x86-compatible uni- and multi-processor kernels. ExecShield reduces the risk of buffer overflow by separating virtual memory into executable and non-executable segments. Any program code that tries to execute outside of the executable segment (such as malicious code injected from a buffer overflow exploit) triggers a segmentation fault and terminates. Execshield also includes support for No eXecute ( NX ) technology on AMD64 platforms and eXecute Disable ( XD ) technology on Itanium and EM64T systems. These technologies work in conjunction with ExecShield to prevent malicious code from running in the executable portion of virtual memory with a granularity of 4kb of executable code, lowering the risk of attack from stealthy buffer overflow exploits. For more information about ExecShield and NX or XD technologies, refer to the whitepaper entitled New Security Enhancements in Red Hat Enterprise Linux v.3, Update 3 , available at the following URL: http://www.redhat.com/solutions/info/whitepapers/ To limit exposure to attacks over the network, all services that are unused should be turned off.

Commands:
15.3. Configure Lock Striping (Library Mode) Lock striping is disabled by default in Red Hat JBoss Data Grid. Configure lock striping in JBoss Data Grid's Library mode using the useLockStriping parameter as demonstrated in the following procedure. Procedure 15.1. Configure Lock Striping (Library Mode) The concurrencyLevel is used to specify the size of the shared lock collection use when lock striping is enabled. The isolationLevel parameter specifies the cache's isolation level. Valid isolation levels are READ_COMMITTED and REPEATABLE_READ . The lockAcquisitionTimeout parameter specifies time (in milliseconds) after which a lock acquisition attempt times out. The useLockStriping parameter specifies whether a pool of shared locks are maintained for all entries that require locks. If set to FALSE , locks are created for each entry in the cache. If set to TRUE , lock striping is enabled and shared locks are used as required from the pool. The writeSkewCheck check determines if a modification to the entry from a different transaction should roll back the transaction. Write skew set to true requires isolation_level set to REPEATABLE_READ . The default value for writeSkewCheck and isolation_level are FALSE and READ_COMMITTED respectively. The writeSkewCheck parameter can be only used with OPTIMISTIC transactions and it requires entry versioning to be enabled, with SIMPLE versioning scheme. Report a bug

Commands:
<infinispan> <!-- Additional configuration elements here --> <default> <locking concurrencyLevel="USD{VALUE}" isolationLevel="USD{LEVEL}" lockAcquisitionTimeout="USD{TIME}" useLockStriping="USD{TRUE/FALSE}" writeSkewCheck="USD{TRUE/FALSE}" /> <!-- Additional configuration elements here --> </default> </infinispan>
19. Architecture Specific Notes Red Hat Enterprise Linux 6 is architecturally complete, and all supported architectures are now available. Red Hat Enterprise Linux 6 will not provide support for the Intel(R) Itanium(R) architecture. All Itanium-related development will be incorporated into Red Hat Enterprise Linux 5 exclusively. Through March 2014, Red Hat Enterprise Linux 5 will provide support, deliver new features, and enable new Itanium hardware in accordance with the published Red Hat Enterprise Linux product life-cycle. In addition, extended support for Red Hat Enterprise Linux 5 for Itanium is available up to March 2017 from selected OEMs. On the POWER architecture, Red Hat Enterprise Linux 6 requires a POWER6 or higher CPU. POWER5 processors are not supported on Red Hat Enterprise Linux 6.

Commands:
7.3. Locating Entries in Distribution Mode The consistent hash algorithm used in Red Hat JBoss Data Grid's distribution mode can locate entries deterministically, without multicasting a request or maintaining expensive metadata. A PUT operation can result in as many remote calls as specified by the num_copies parameter, while a GET operation executed on any node in the cluster results in a single remote call. In the background, the GET operation results in the same number of remote calls as a PUT operation (specifically the value of the num_copies parameter), but these occur in parallel and the returned entry is passed to the caller as soon as one returns. Report a bug

Commands:
Appendix F. Revision History Revision History Revision 10.0-3 Wed Mar 8 2017 Steven Levine Version for 6.9 GA Publication Revision 10.0-1 Fri Dec 16 2016 Steven Levine Version for 6.9 Beta Publication Revision 9.0-5 Tue Nov 29 2016 Steven Levine Updating document for 6.8. Revision 9.0-4 Wed Apr 27 2016 Steven Levine Preparing document for 6.8 GA publication. Revision 9.0-3 Wed Mar 9 2016 Steven Levine Initial revision for Red Hat Enterprise Linux 6.8 Beta release Revision 8.0-16 Mon Jul 13 2015 Steven Levine Republish version for Red Hat Enterprise Linux 6.7 Revision 8.0-14 Wed Jul 8 2015 Steven Levine Initial revision for Red Hat Enterprise Linux 6.7 Revision 8.0-13 Tue Apr 14 2015 Steven Levine Initial revision for Red Hat Enterprise Linux 6.7 Beta release Revision 7.0-9 Wed Oct 8 2014 Steven Levine Initial revision for Red Hat Enterprise Linux 6.6 Revision 7.0-8 Thu Aug 7 2014 Steven Levine Initial revision for Red Hat Enterprise Linux 6.6 Beta release Revision 6.0-14 Wed Nov 13 2013 Steven Levine Initial revision for Red Hat Enterprise Linux 6.5 Revision 6.0-10 Fri Sep 27 2013 Steven Levine Initial revision for Red Hat Enterprise Linux 6.5 Beta release Revision 5.0-19 Mon Feb 18 2013 John Ha Initial revision for Red Hat Enterprise Linux 6.4 Revision 5.0-12 Mon Nov 27 2012 Steven Levine Initial revision for Red Hat Enterprise Linux 6.4 Beta release Revision 4.0-2 Fri Jun 15 2012 Steven Levine Initial revision for Red Hat Enterprise Linux 6.3 Revision 3.0-1 Mon Sep 19 2011 Steven Levine Initial revision for Red Hat Enterprise Linux 6.2 Beta release Revision 2.0-1 Thu May 19 2011 Steven Levine Initial revision for Red Hat Enterprise Linux 6.1 Revision 1.0-1 Wed Nov 10 2010 Steven Levine Initial release for Red Hat Enterprise Linux 6

Commands:
Chapter 2. Installing .NET 9.0 .NET 9.0 is included in the AppStream repositories for RHEL 8. The AppStream repositories are enabled by default on RHEL 8 systems. You can install the .NET 9.0 runtime with the latest 9.0 Software Development Kit (SDK). When a newer SDK becomes available for .NET 9.0, you can install it by running sudo dnf install . Prerequisites Installed and registered RHEL 8.10 with attached subscriptions. For more information, see Interactively installing RHEL from installation media . Procedure Install .NET 9.0 and all of its dependencies: Verification Verify the installation: The output returns the relevant information about the .NET installation and the environment.

Commands:
sudo dnf install dotnet-sdk-9.0 -y
dotnet --info
probe::nfsd.proc.read Name probe::nfsd.proc.read - NFS server reading file for client Synopsis nfsd.proc.read Values size read bytes vec struct kvec, includes buf address in kernel address and length of each buffer version nfs version uid requester's user id count read bytes client_ip the ip address of client proto transfer protocol offset the offset of file gid requester's group id vlen read blocks fh file handle (the first part is the length of the file handle)

Commands:
13.2. LDAP Terminology Any discussion of LDAP requires a basic understanding of a set of LDAP-specific terms: entry - A single unit within an LDAP directory. Each entry is identified by its unique Distinguished Name (DN) . attributes - Information directly associated with an entry. For example, an organization could be represented as an LDAP entry. Attributes associated with the organization might include a fax number, an address, and so on. People can also be represented as entries in an LDAP directory, with common attributes such as the person's telephone number and email address. Some attributes are required, while other attributes are optional. An objectclass definition sets which attributes are required for each entry. Objectclass definitions are found in various schema files, located in the /etc/openldap/schema/ directory. For more information, refer to Section 13.5, "The /etc/openldap/schema/ Directory" . LDIF - The LDAP Data Interchange Format (LDIF) is an ASCII text representation of LDAP entries. Files used for importing data to LDAP servers must be in LDIF format. An LDIF entry looks similar to the following example: Each entry can contain as many < attrtype >: < attrvalue > pairs as needed. A blank line indicates the end of an entry. Warning All < attrtype > and < attrvalue > pairs must be defined in a corresponding schema file to use this information. Any value enclosed within a < and a > is a variable and can be set whenever a new LDAP entry is created. This rule does not apply, however, to < id > . The < id > is a number determined by the application used to edit the entry.

Commands:
[< id >] dn: < distinguished name > < attrtype >: < attrvalue > < attrtype >: < attrvalue > < attrtype >: < attrvalue >
Chapter 16. Getting started with perf As a system administrator, you can use the perf tool to collect and analyze performance data of your system. 16.1. Introduction to perf The perf user-space tool interfaces with the kernel-based subsystem Performance Counters for Linux (PCL). perf is a powerful tool that uses the Performance Monitoring Unit (PMU) to measure, record, and monitor a variety of hardware and software events. perf also supports tracepoints, kprobes, and uprobes. 16.2. Installing perf This procedure installs the perf user-space tool. Procedure Install the perf tool: 16.3. Common perf commands perf stat This command provides overall statistics for common performance events, including instructions executed and clock cycles consumed. Options allow for selection of events other than the default measurement events. perf record This command records performance data into a file, perf.data , which can be later analyzed using the perf report command. perf report This command reads and displays the performance data from the perf.data file created by perf record . perf list This command lists the events available on a particular machine. These events will vary based on performance monitoring hardware and software configuration of the system. perf top This command performs a similar function to the top utility. It generates and displays a performance counter profile in realtime. perf trace This command performs a similar function to the strace tool. It monitors the system calls used by a specified thread or process and all signals received by that application. perf help This command displays a complete list of perf commands. Additional resources Add the --help option to a subcommand to open the man page.

Commands:
dnf install perf
Chapter 15. Storage LVM snapshots sometimes cause system hang The system sometimes becomes unresponsive when using LVM snapshots and when file system blocks are not aligned on snapshot chunk boundaries. This is caused by a complex interaction between Device Mapper snapshots and per-process bio queuing, which might lead to a cyclic dependency and deadlock. If you are affected by this problem, please upgrade to Red Hat Enterprise Linux 7, which fixes the deadlock. The fix is too invasive to be included in Red Hat Enterprise Linux 6 at this production phase. (BZ#1073220)

Commands:
Assessing and Monitoring Security Policy Compliance of RHEL Systems with FedRAMP Red Hat Insights 1-latest Understanding the Security Compliance Status of your Red Hat Enterprise Linux Infrastructure Red Hat Customer Content Services

Commands:
[user@insights]USD cat /etc/redhat-release
dnf info scap-security-guide-0.1.57-3.el8_4
dnf install scap-security-guide-0.1.57-3.el8_4
insights-client --compliance
insights-client --compliance insights-client --collector malware-detection
crontab -e
10 20 * * * /bin/insights-client --compliance 10 21 * * * /bin/insights-client --collector malware-detection
insights-client --compliance-policies
insights-client --compliance-assign <ID>.
insights-client --compliance-unassign <ID>
USE [master] GO CREATE LOGIN [assessmentLogin] with PASSWORD= N'<*PASSWORD*>' ALTER SERVER ROLE [sysadmin] ADD MEMBER [assessmentLogin] GO
echo "assessmentLogin" > /var/opt/mssql/secrets/assessment echo "<*PASSWORD*>" >> /var/opt/mssql/secrets/assessment
chmod 0600 /var/opt/mssql/secrets/assessment chown mssql:mssql /var/opt/mssql/secrets/assessment
yum -y install powershell
su mssql -c "/usr/bin/pwsh -Command Install-Module SqlServer"
/bin/curl -LJ0 -o /opt/mssql/bin/runassessment.ps1 https://raw.githubusercontent.com/microsoft/sql-server-samples/master/samples/manage/sql-assessment-api/RHEL/runassessment.ps1 chown mssql:mssql /opt/mssql/bin/runassessment.ps1 chmod 0700 /opt/mssql/bin/runassessment.ps1
mkdir /var/opt/mssql/log/assessments/ chown mssql:mssql /var/opt/mssql/log/assessments/ chmod 0700 /var/opt/mssql/log/assessments/
su mssql -c "pwsh -File /opt/mssql/bin/runassessment.ps1"
insights-client
cp mssql-runassessment.service /etc/systemd/system/ cp mssql-runassessment.timer /etc/systemd/system/ chmod 644 /etc/systemd/system/
systemctl enable --now mssql-runassessment.timer
insights-client --group=<name-you-choose>
tags --- group: eastern-sap name: Jane Example contact: jexample@corporate.com Zone: eastern time zone Location: - gray_rack - basement Application: SAP
tags --- group: eastern-sap location: Boston description: - RHEL8 - SAP key 4: value
insights-client
vi /etc/insights-client/tags.yaml
cat /etc/insights-client/tags.yaml group: redhat location: Brisbane/Australia description: - RHEL8 - SAP security: strict network_performance: latency
insights-client