mtpti5iD/redhat-docs_dataset huggingface dataset:
18.3. Using IPTables The first step in using iptables is to start the iptables service. Use the following command to start the iptables service: Note The ip6tables service can be turned off if you intend to use the iptables service only. If you deactivate the ip6tables service, remember to deactivate the IPv6 network also. Never leave a network device active without the matching firewall. To force iptables to start by default when the system is booted, use the following command: This forces iptables to start whenever the system is booted into runlevel 3, 4, or 5. 18.3.1. IPTables Command Syntax The following sample iptables command illustrates the basic command syntax: The -A option specifies that the rule be appended to <chain> . Each chain is comprised of one or more rules , and is therefore also known as a ruleset . The three built-in chains are INPUT, OUTPUT, and FORWARD. These chains are permanent and cannot be deleted. The chain specifies the point at which a packet is manipulated. The -j <target> option specifies the target of the rule; i.e., what to do if the packet matches the rule. Examples of built-in targets are ACCEPT, DROP, and REJECT. Refer to the iptables man page for more information on the available chains, options, and targets.

Commands:
service iptables start
chkconfig --level 345 iptables on
iptables -A <chain> -j <target>
Chapter 54. Starting dynamic tasks and processes You can add dynamic tasks and processes to a case during run time. Dynamic actions are a way to address changing situations, where an unanticipated change during the case requires a new task or process to be incorporated into the case. Use a case application to add a dynamic task during run time. For demonstration purposes, the Business Central distribution includes a Showcase application where you can start a new dynamic task or process for the IT Orders application. Prerequisites KIE Server is deployed and connected to Business Central. The IT Orders project is deployed to KIE Server. The Showcase application .war file has been deployed alongside Business Central. Procedure With the IT_Orders_New project deployed and running in KIE Server, in a web browser, navigate to the Showcase login page http://localhost:8080/rhpam-case-mgmt-showcase/ . Alternatively, if you have configured Business Central to display the Apps launcher button, use it to open a new browser window with the Showcase login page. Log in to the Showcase application using your Business Central login credentials. Select an active case instance from the list to open it. Under Overview Actions Available , click the button to New user task or New process task to add a new task or process task. Figure 54.1. Showcase dynamic actions To create a dynamic user task, start a New user task and complete the required information: To create a dynamic process task, start a new process task and complete the required information: To view a dynamic user task in Business Central, click Menu Track Task Inbox . The user task that was added dynamically using the Showcase application appears in the Task Inbox of users assigned to the task during task creation. Click the dynamic task in the Task Inbox to open the task. A number of action tabs are available from this page. Using the actions available under the task tabs, you can begin working on the task. In the Showcase application, click the refresh button in the upper-right corner. Case tasks and processes that are in progress appear under Overview Actions In progress . When you have completed working on the task, click the Complete button under the Work tab. In the Showcase application, click the refresh button in the upper-right corner. The completed task appears under Overview Actions Completed . To view a dynamic process task in Business Central, click Menu Manage Process Instances . Click the dynamic process instance in the list of available process instances to view information about the process instance. In the Showcase application, click the refresh button in the upper-right corner. Case tasks and processes that are in progress appear under Overview Actions In progress .

Commands:
7.98. krb5-auth-dialog 7.98.1. RHBA-2015:0812 - krb5-auth-dialog bug fix update Updated krb5-auth-dialog packages that fix one bug are now available for Red Hat Enterprise Linux 6. Kerberos is a networked authentication system which allows clients and servers to authenticate to each other with the help of a trusted third party, the Kerberos key distribution center. The krb5-auth-dialog packages contain a dialog that warns the user when their Kerberos credentials are about to expire and allows them to renew them. Bug Fix BZ# 848026 Previously, users could experience a disproportionate increase in memory utilization by krb5-auth-dialog after being logged in on VMware virtual machines for longer periods of time. To fix this bug, a patch has been applied. Now, the krb5-auth-dialog memory leak no longer occurs in this situation. Users of krb5-auth-dialog are advised to upgrade to these updated packages, which fix this bug.

Commands:
10.5. Testing Enrollment For information on testing enrollment through the profiles, see Chapter 3, Making Rules for Issuing Certificates (Certificate Profiles) . To test whether end users can successfully enroll for a certificate using the authentication method set: Open the end-entities page. In the Enrollment tab, open the customized enrollment form. Fill in the values, and submit the request. Enter the password to the key database when prompted. When the correct password is entered, the client generates the key pair. Do not interrupt the key-generation process. Upon completion of the key generation, the request is submitted to the server to issue the certificate. The server subjects the request to the certificate profile and issues the certificate only if the request meets all the requirements. When the certificate is issued, install the certificate in the browser. Verify that the certificate is installed in the browser's certificate database. If PIN-based directory authentication was configured with PIN removal, re-enroll for another certificate using the same PIN. The request should be rejected.

Commands:
http s ://server.example.com: 8443/ca/ee/ca
8.186. procps 8.186.1. RHBA-2014:1595 - procps bug fix and enhancement update Updated procps packages that fix two bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The procps packages contain a set of system utilities that provide system information. The procps packages include the following utilities: ps, free, skill, pkill, pgrep, snice, tload, top, uptime, vmstat, w, watch, and pwdx. Bug Fixes BZ# 950748 The /lib64/libproc.so development symbolic link was present in both the main procps package and its devel sub-package. This caused file conflicts when installing the devel sub-package. This update removes the duplicate symbolic link from the main package so that the devel sub-package can be installed without problems. BZ# 963799 The 'free' command always displayed zero in the 'shared' column as the procps-ng library was attempting to read from non-existent 'MemShared' field in /proc/meminfo file. With this update, the 'shared' column is reused for a value representing the 'MemShared' field, thus fixing this bug. This update also introduces a new '-a' option for the free command that enables a new column that represents a recently added field called 'MemAvailable'. The kernel does not export this field by default, so it needs to be explicitly enabled. Refer to the free(1) man page for more details. In addition, this update adds the following Enhancements BZ# 977467 Previously, only one configuration file could be passed to the 'sysctl' tool with the '-p' option. This update allows users to pass multiple configuration files with this option. As a result, users can perform shell expansion by using braces and wildcard characters. BZ# 1105125 With this update, the 'top' and 'watch' tools accept floating point numbers representing the polling or refresh intervals. Both widely used floating point separators ('.' and ',') can be applied, regardless of the locale settings in use. BZ# 1034337 This update introduces man pages for the openproc(), readproc() and readproctab() functions available in the libproc library. These manuals help writing applications that utilize the aforementioned functions. BZ# 1060681 This update introduces a new 'q' option (alternatively '-q' or '--quick-pid') to the 'ps' command. This option is essentially a speed-optimized enhancement of the 'p' option. The new option is recommended in cases where users only need to specify a list of PIDs to be shown, and do not need other selection and sorting options. BZ# 1011216 , BZ# 1082877 , BZ# 1089817 This update also enhances several man pages. Users of procps are advised to upgrade to these updated packages, which fix these bugs.

Commands:
1.2. Features and Usage Modes The following table presents a list of features and indicates the usage mode for each feature. Red Hat JBoss Data Grid 7.0 includes full support for both Remote Client-Server mode and Library mode. Table 1.1. JBoss Data Grid Features Feature Remote Client-Server Mode (Supported) Library Mode (Supported) File Cache Store and Loading JDBC Cache Store and Loading LevelDB Cache Store and Loading Cassandra Cache Store and Loading Cache Passivation Remote Cache Store Cluster Cache Store Asynchronous Store Cluster Configuration Using UDP Cluster Configuration Using TCP Mortal and Immortal Data Eviction Strategy Expiration Unscheduled Write-behind Cache Store Write-through Cache Store Clustering Mode (local) Clustering Mode (replicated) Clustering Mode (invalidation) Clustering Mode (distribution) Asynchronous Clustering Modes Marshalling Management Using JMX Cross-Datacenter Replication and State Transfer JBoss Operations Network (JON) Integration and Plugin Asymmetric Cluster Command Line Interface (CLI) Role-based Access Control Node Authentication and Authorization Encrypted Communication Within the Cluster Per Invocation Flags Handling Network Partitions Spring Integration Apache Camel Component for JBoss Fuse Querying (by values) Continuous Queries Clustered Listeners and Notifications for Cache Events Near Caching JSR-107 Support CDI Asynchronous API Distributed Streams 1 Deploy custom cache store to JDG Server Connection Pooling with JDBC Cache Stores REST Interface Memcached Interface Hot Rod Java client Hot Rod C++ Client Hot Rod .NET Client Hot Rod Node.js Client Data Compatibility Between Client-server Protocols Data Compatibility Between Hot Rod Java and C++ Client Rolling Upgrades for Hot Rod Cluster Rolling Upgrades for REST Clusters Controlled Shutdown and Restart of Cluster Authentication and Encryption over Hot Rod (Java client) JBoss Data Grid's Hot Rod Client as a JBoss EAP Module Externalizing HTTP sessions from JBoss EAP 7 to remote JDG cluster Remote Task Execution Apache Spark Integration Apache Hadoop Integration Administration Console READ_COMMITTED and REPEATABLE_READ Isolation Modes Lazy Deserialization Using the infinispan.xml File in Conjunction with APIs Custom Interceptors 2 Grouping API Java Transactional API (JTA) Support and Configuration Java Transactional API (JTA) Deadlock Detection Transaction Recovery Transaction and Batching Key Affinity Distributed Execution Framework JPA Cache Store JBoss Data Grid as a JBoss EAP Module JDG as Lucene Directory 1: Distributed Streams are available in JBoss Data Grid's Remote Client-Server Mode via Remote Task Execution. 2: Custom Interceptors are deprecated in JBoss Data Grid 7.0.0, and are expected to be removed in a subsequent version. Report a bug

Commands:
3.2. CPU Performance Options Several CPU related options are available to your guest virtual machines. Configured correctly, these options can have a large impact on performance. The following image shows the CPU options available to your guests. The remainder of this section shows and explains the impact of these options. Figure 3.3. CPU Performance Options 3.2.1. Option: Available CPUs Use this option to adjust the amount of virtual CPUs (vCPUs) available to the guest. If you allocate more than is available on the host (known as overcommitting ), a warning is displayed, as shown in the following image: Figure 3.4. CPU overcommit CPUs are overcommitted when the sum of vCPUs for all guests on the system is greater than the number of host CPUs on the system. You can overcommit CPUs with one or multiple guests if the total number of vCPUs is greater than the number of host CPUs. Important As with memory overcommitting, CPU overcommitting can have a negative impact on performance, for example in situations with a heavy or unpredictable guest workload. See the Virtualization Deployment and Administration Guide for more details on overcommitting. 3.2.2. Option: CPU Configuration Use this option to select the CPU configuration type, based on the intended CPU model. Click the Copy host CPU configuration check box to detect and apply the physical host's CPU model and configuration, or expand the list to see available options. Once you select a CPU configuration, its available CPU features/instructions are displayed and can be individually enabled/disabled in the CPU Features list. Figure 3.5. CPU Configuration Options Note Copying the host CPU configuration is recommended over manual configuration. Note Alternately, run the virsh capabilities command on your host machine to view the virtualization capabilities of your system, including CPU types and NUMA capabilities. 3.2.3. Option: CPU Topology Use this option to apply a particular CPU topology (Sockets, Cores, Threads) to the virtual CPUs for your guest virtual machine. Figure 3.6. CPU Topology Options Note Although your environment may dictate other requirements, selecting any intended number of sockets, but with only a single core and a single thread usually gives the best performance results.

Commands:
Chapter 1. Red Hat build of OpenJDK overview The Red Hat build of OpenJDK is a free and open source implementation of the Java Platform, Standard Edition (Java SE). It is based on the upstream OpenJDK 8u, OpenJDK 11u, OpenJDK 17u, and OpenJDK 21u projects and includes the Shenandoah Garbage Collector in all versions. Multi-platform - The Red Hat build of OpenJDK is now supported on Windows and RHEL. This helps you standardize on a single Java platform across desktop, datacenter, and hybrid cloud. Frequent releases - Red Hat delivers quarterly updates of JRE and JDK for the Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, and Red Hat build of OpenJDK 21 distributions. These are available as rpm , portables, msi , zip files and containers. Long-term support - Red Hat supports the recently released Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, and Red Hat build of OpenJDK 21 distributions. For more information about the support lifecycle, see OpenJDK Life Cycle and Support Policy . Java Web Start - Red Hat build of OpenJDK supports Java Web Start for RHEL.

Commands:
Chapter 2. Installation This chapter guides you through the steps to install AMQ Core Protocol JMS in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To build programs with AMQ Core Protocol JMS, you must install Apache Maven . To use AMQ Core Protocol JMS, you must install Java. 2.2. Using the Red Hat Maven repository Configure your Maven environment to download the client library from the Red Hat Maven repository. Procedure Add the Red Hat repository to your Maven settings or POM file. For example configuration files, see Section B.1, "Using the online repository" . <repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository> Add the library dependency to your POM file. <dependency> <groupId>org.apache.activemq</groupId> <artifactId>artemis-jms-client</artifactId> <version>2.16.0.redhat-00005</version> </dependency> The client is now available in your Maven project. 2.3. Installing a local Maven repository As an alternative to the online repository, AMQ Core Protocol JMS can be installed to your local filesystem as a file-based Maven repository. Procedure Use your subscription to download the AMQ Broker 7.9.0 Maven repository .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-broker-7.9.0-maven-repository.zip On Windows, right-click the .zip file and select Extract All . Configure Maven to use the repository in the maven-repository directory inside the extracted install directory. For more information, see Section B.2, "Using a local repository" . 2.4. Installing the examples Procedure Use your subscription to download the AMQ Broker 7.9.0 .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-broker-7.9.0.zip On Windows, right-click the .zip file and select Extract All . When you extract the contents of the .zip file, a directory named amq-broker-7.9.0 is created. This is the top-level directory of the installation and is referred to as <install-dir> throughout this document.

Commands:
<repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository>
<dependency> <groupId>org.apache.activemq</groupId> <artifactId>artemis-jms-client</artifactId> <version>2.16.0.redhat-00005</version> </dependency>
unzip amq-broker-7.9.0-maven-repository.zip
unzip amq-broker-7.9.0.zip
3.4.3. Updating Users' Authentication When running the basic useradd username command, the password is automatically set to never expire (see the /etc/shadow file). If you want to change this, use passwd , the standard utility for administering the /etc/passwd file. The syntax of the passwd command look as follows: You can, for example, lock the specified account. The locking is performed by rendering the encrypted password into an invalid string by prefixing the encrypted string with an the exclamation mark ( ! ). If you later find a reason to unlock the account, passwd has a reverse operation for locking. Only root can carry out these two operations. Example 3.8. Unlocking a User Password At first, the -l option locks robert 's account password successfully. However, running the passwd -u command does not unlock the password because by default passwd refuses to create a passwordless account. If you want a password for an account to expire, run passwd with the -e option. The user will be forced to change the password during the login attempt: As far as the password lifetime is concerned, setting the minimum time between password changes is useful for forcing the user to really change the password. The system administrator can set the minimum (the -n option) and the maximum (the -x option) lifetimes. To inform the user about their password expiration, use the -w option. All these options must be accompanied with the number of days and can be run as root only. Example 3.9. Adjusting Aging Data for User Passwords The above command has set the minimum password lifetime to 10 days, the maximum password lifetime to 60, and the number of days jane will begin receiving warnings in advance that her password will expire to 3 day. Later, when you cannot remember the password setting, make use of the -S option which outputs a short information for you to know the status of the password for a given account: You can also set the number of days after a password expires with the useradd command, which disables the account permanently. A value of 0 disables the account as soon as the password has expired, and a value of -1 disables the feature, that is, the user will have to change his password when the password expires. The -f option is used to specify the number of days after a password expires until the account is disabled (but may be unblocked by system administrator): For more information on the passwd command see the passwd (1) man page.

Commands:
passwd option(s) username
passwd -l username passwd -u username
~]# passwd -l robert Locking password for user robert. passwd: Success ~]# passwd -u robert passwd: Warning: unlocked password would be empty passwd: Unsafe operation (use -f to force)
passwd -e username
~]# passwd -n 10 -x 60 -w 3 jane
~]# passwd -S jane jane LK 2014-07-22 10 60 3 -1 (Password locked.)
useradd -f number-of-days username
8.35. crash-trace-command 8.35.1. RHBA-2014:1462 - crash-trace-command bug fix update Updated crash-trace-command packages that fix one bug are now available for Red Hat Enterprise Linux 6. The crash-trace-command packages provide the trace extension module for the crash utility, allowing it to read ftrace data from a core dump file. Bug Fix BZ# 895899 Previously, crash-trace-command displayed incorrect "Packager" and "Vendor" information. With this update, crash-trace-command prints "Red Hat, Inc." in these fields as expected. Users of crash-trace-command are advised to upgrade to these updated packages, which fix this bug.

Commands:
Part IV. Designing a decision service using guided decision tables As a business analyst or business rules developer, you can use guided decision tables to define business rules in a wizard-led tabular format. These rules are compiled into Drools Rule Language (DRL) and form the core of the decision service for your project. Note You can also design your decision service using Decision Model and Notation (DMN) models instead of rule-based or table-based assets. For information about DMN support in Red Hat Process Automation Manager 7.13, see the following resources: Getting started with decision services (step-by-step tutorial with a DMN decision service example) Designing a decision service using DMN models (overview of DMN support and capabilities in Red Hat Process Automation Manager) Prerequisites The space and project for the guided decision tables have been created in Business Central. Each asset is associated with a project assigned to a space. For details, see Getting started with decision services .

Commands:
1.4. DM-Multipath Setup Overview DM-Multipath includes compiled-in default settings that are suitable for common multipath configurations. Setting up DM-multipath is often a simple procedure. The basic procedure for configuring your system with DM-Multipath is as follows: Install device-mapper-multipath rpm. Edit the multipath.conf configuration file: comment out the default blacklist change any of the existing defaults as needed save the configuration file Start the multipath daemons. Create the multipath device with the multipath command. Detailed setup instructions for several example multipath configurations are provided in see Chapter 3, Setting Up DM-Multipath .

Commands:
A.4. Reserved Keywords For Future Use ALLOCATE ARE ARRAY ASENSITIVE ASYMETRIC AUTHORIZATION BINARY CALLED CASCADED CHARACTER CHECK CLOSE COLLATE COMMIT CONNECT CORRESPONDING CRITERIA CURRENT_DATE CURRENT_TIME CURRENT_TIMESTAMP CURRENT_USER CURSOR CYCLE DATALINK DEALLOCATE DEC DEREF DESCRIBE DETERMINISTIC DISCONNECT DLNEWCOPY DLPREVIOUSCOPY DLURLCOMPLETE DLURLCOMPLETEONLY DLURLCOMPLETEWRITE DLURLPATH DLURLPATHONLY DLURLPATHWRITE DLURLSCHEME DLURLSERVER DLVALUE DYNAMIC ELEMENT EXTERNAL FREE GET GLOBAL GRANT HAS HOLD IDENTITY IMPORT INDICATOR INPUT INSENSITIVE INT INTERVAL ISOLATION LARGE LOCALTIME LOCALTIMESTAMP MATCH MEMBER METHOD MODIFIES MODULE MULTISET NATIONAL NATURAL NCHAR NCLOB NEW NONE NUMERIC OLD OPEN OUTPUT OVERLAPS PRECISION PREPARE RANGE READS RECURSIVE REFERENCING RELEASE REVOKE ROLLBACK ROLLUP SAVEPOINT SCROLL SEARCH SENSITIVE SESSION_USER SPECIFIC SPECIFICTYPE SQL START STATIC SUBMULTILIST SYMETRIC SYSTEM SYSTEM_USER TIMEZONE_HOUR TIMEZONE_MINUTE TRANSLATION TREAT VALUE VARYING WHENEVER WINDOW WITHIN XMLBINARY XMLCAST XMLDOCUMENT XMLEXISTS XMLITERATE XMLTEXT XMLVALIDATE

Commands: