mtpti5iD/redhat-docs_dataset huggingface dataset:
9.4. Threading Considerations Although, you can find information about all JBoss Data Virtualization settings using the Management CLI (see Section 10.1, "JBoss Data Virtualization Settings" ), this section provides some additional information about those settings related to threading. max-threads Default is 64. The query engine has several settings that determine its thread utilization. max-threads sets the total number of threads available in the process pool for query engine work (such as processing plans, transaction control operations, and processing source queries). You should consider increasing the maximum threads on systems with a large number of available processors and/or when it is necessary to issue non-transactional queries involving a large number of concurrent source requests. max-active-plans Default is 20. This value should always be smaller than max-threads . By default, thread-count-for-source-concurrency is calculated by (max-threads / max_active_plans) * 2 to determine the threads available for processing concurrent source requests for each user query. Increasing the max-active-plans should be considered for workloads with a high number of long running queries and/or systems with a large number of available processors. If memory issues arise from increasing the max-threads and max-active-plans, then consider decreasing the amount of heap held by the buffer manager or decreasing the processor-batch-size to limit the base number of memory rows consumed by each plan. Increasing max-active-plans should be considered for workloads with a high number of long running queries and/or systems with a large number of available processors. If memory issues arise from increasing max-threads and max-active-plans , then consider decreasing buffer-service-processor-batch-size to limit the base number of memory rows consumed by each plan. thread-count-for-source-concurrency Default is 0. This value should always be smaller than max-threads . This property sets the number of concurrently executing source queries per user request. 0 indicates to use the default calculated value based on 2 * ( max-threads / max-active-plans ). Setting this to 1 forces serial execution of all source queries by the processing thread. Any number greater than 1 limits the maximum number of concurrently executing source requests accordingly. Using the defaults, each user request would be allowed 6 concurrently executing source queries. If the default calculated value is not applicable to your workload, for example, if you have queries that generate more concurrent long running source queries, you should adjust this value. Also see Section 9.6, "Transport Considerations" for max-socket-threads .

Commands:
4.257. qpid-cpp 4.257.1. RHBA-2011:1670 - qpid-cpp bug fix and enhancement update Updated qpid-cpp packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The qpid-cpp packages provide a message broker daemon that receives, stores, and routes messages using the open AMQP (Advanced Message Queuing Protocol) messaging protocol along with runtime libraries for AMQP client applications developed using Qpid C++. Clients exchange messages with an AMQP message broker using the AMQP protocol. The qpid-cpp package has been upgraded to upstream version 0.12, which provides numerous bug fixes and enhancements over the version. (BZ# 706949 ) Bug Fixes BZ# 695777 In the version of Red Hat Enterprise Linux, when an attempt to convert a negative value of a Variant Qpid type into an unsigned short type value was made, an exception was issued. In Red Hat Enterprise Linux 6, no exception was issued and the value was converted, e.g. "-5" became "65531". This bug has been fixed and the exception is now properly issued in the described scenario. BZ# 735058 Previously, non-static "isManagementMessage" class member was sometimes passed an uninitialized value. This bug has been fixed and only initialized values are now passed in the described scenario. BZ# 740912 The XML-Exchange library (as part of the qpid-cpp-server-xml package) is only available on x86, Intel 64, and AMD64 architectures. Previously, this caused additional dependencies on the xqilla and xerces-c packages to be added to the qpid-cpp RPM package. However, functionality of these two packages is not needed for the Matahari agent infrastructure. This update removes the dependency on these two packages for the PowerPC and IBM System z architectures. Enhancement BZ# 663461 Previously, qpid-cpp was only built for x86, Intel 64, and AMD64 architectures. This update adds support, which is needed to provide the Matahari agent infrastructure on PowerPC and IBM System z architectures. Users of qpid-cpp are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 4. Managing organizations in automation controller An organization is a logical collection of users, teams, projects, and inventories. It is the highest level object in the controller object hierarchy. After you have created an organization, automation controller displays the organization details. You can then manage access and execution environments for the organization. 4.1. Reviewing the organization The Organizations page displays the existing organizations for your installation. Procedure From the navigation panel, select Access Organizations . Note Automation controller automatically creates a default organization. If you have a Self-support level license, you have only the default organization available and must not delete it. You can use the default organization as it is initially set up and edit it later. Note Only Enterprise or Premium licenses can add new organizations. Enterprise and Premium license users who want to add a new organization should see the Organizations section in the Automation controller User Guide . 4.2. Editing an organization During initial setup, you can leave the default organization as it is, but you can edit it later. Procedure Edit the organization by using one of these methods: From the organizations Details page, click Edit to the organization you want to modify. From the navigation panel, select Access Organizations . Select the organization you want to modify and edit the appropriate details. Save your changes.

Commands:
Chapter 5. Limited Availability features Important This section describes Limited Availability features in Red Hat OpenShift AI 2.18. Limited Availability means that you can install and receive support for the feature only with specific approval from Red Hat. Without such approval, the feature is unsupported. This applies to all features described in this section. Tuning in OpenShift AI Tuning in OpenShift AI is available as a Limited Availability feature. The Kubeflow Training Operator and the Hugging Face Supervised Fine-tuning Trainer (SFT Trainer) enable users to fine-tune and train their models easily in a distributed environment. In this release, you can use this feature for models that are based on the PyTorch machine-learning framework.

Commands:
5.115. ipvsadm 5.115.1. RHBA-2012:0865 - ipvsadm bug fix update Updated ipvsadm packages that fix one bug is now available for Red Hat Enterprise Linux 6. The ipvsadm package provides the ipsvadm tool to administer the IP Virtual Server services offered by the Linux kernel. Bug Fix BZ# 788529 Prior to this update, the ipvsadm utility did not correctly handle out-of-order messages from the kernel concerning the sync daemon. As a consequence, the "ipvsadm --list --daemon" command did not always output the status of the sync daemon. With this update, the ordering of messages from the kernel no longer influences the output, and the command always returns the sync daemon status. All users of ipvsadm are advised to upgrade to these updated packages, which fix this bug.

Commands:
5.322. system-config-keyboard 5.322.1. RHEA-2012:0852 - system-config-keyboard enhancement update Updated system-config-keyboard packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The system-config-keyboard packages provide a graphical user interface that allows the user to change the default keyboard of the system. Enhancement BZ# 771389 Prior to this update, the Red Hat Enterprise Virtualization Hypervisor pulled too many dependencies from the system-config-keyboard package to support keyboard selection capability for non-US keyboards. This update adds the system-config-keyboard-base package that contains the core python libraries. All users of system-config-keyboard are advised to upgrade to these updated packages, which add this enhancement.

Commands:
Chapter 42. Standalone perspectives in Business Central Business Central provides specialized editors for authoring assets based on the asset's format. Business Central has a feature that enables you to use these editors individually. This feature is known as the standalone perspective mode of the editor or simply the standalone perspectives . As a business rules developer, you can embed a standalone perspective in your web application and then use it to edit rules, processes, decision tables, and other assets. After embedding a perspective you can edit an asset in your own application without switching to Business Central. You can use this feature to customize your web application. In addition to standalone perspectives you can also embed standalone custom pages (dashboards) in your applications. You can access a standalone perspective by using a specific web address in a browser with the standalone and perspective parameters. A standalone perspective's web address may also contain additional parameters.

Commands:
17.3. Network Address Translation By default, virtual network switches operate in NAT mode. They use IP masquerading rather than Source-NAT (SNAT) or Destination-NAT (DNAT). IP masquerading enables connected guests to use the host physical machine IP address for communication to any external network. By default, computers that are placed externally to the host physical machine cannot communicate to the guests inside when the virtual network switch is operating in NAT mode, as shown in the following diagram: Figure 17.3. Virtual network switch using NAT with two guests Warning Virtual network switches use NAT configured by iptables rules. Editing these rules while the switch is running is not recommended, as incorrect rules may result in the switch being unable to communicate. If the switch is not running, you can set the public IP range for forward mode NAT in order to create a port masquerading range by running:

Commands:
iptables -j SNAT --to-source [start]-[end]
8.3. Create a New Relational View Model 8.3.1. Create a New Relational View Model To create a new empty relational view model: Launch the New Model Wizard . Specify a unique model name. Select Relational 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 relational view model, the following builder options are available: Copy from existing model of the same model class. Transform from existing model. 8.3.2. Copy an Existing Relational 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 relational model by copying contents from another relational view model, complete first 4 steps from the Create a New Relational 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 relational model from the workspace using the browse button. Select the Copy all descriptions option if desired. Click Finish . 8.3.3. Transform from an Existing Relational View Model This option is only applicable for creating a relational view model from a relational source model with the added feature of creating default transformations ( SELECT * FROM SourceModel.Table_X ) for each source table. The steps are the same as for the Copy from Relational View Model section described above. There is an additional option in the second dialog window of the wizard which can automatically set the relational table's supports update property to false. If this is not selected, the default value will be true.

Commands:
Chapter 1. Introduction Migration Toolkit for Runtimes product will be End of Life on September 30th, 2024 All customers using this product should start their transition to Migration Toolkit for Applications . Migration Toolkit for Applications is fully backwards compatible with all features and rulesets available in Migration Toolkit for Runtimes and will be maintained in the long term. 1.1. About the Introduction to the Migration Toolkit for Runtimes This guide is for engineers, consultants, and others who want to use the Migration Toolkit for Runtimes (MTR) to migrate Java applications or other components. It provides an overview of the Migration Toolkit for Runtimes and how to get started using the tools to plan and run your migration.

Commands:
Chapter 3. Enabling Linux control group version 1 (cgroup v1) As of OpenShift Container Platform 4.14, OpenShift Container Platform uses Linux control group version 2 (cgroup v2) in your cluster. If you are using cgroup v1 on OpenShift Container Platform 4.13 or earlier, migrating to OpenShift Container Platform 4.14 will not automatically update your cgroup configuration to version 2. A fresh installation of OpenShift Container Platform 4.14 will use cgroup v2 by default. However, you can enable Linux control group version 1 (cgroup v1) upon installation. Enabling cgroup v1 in OpenShift Container Platform disables all cgroup v2 controllers and hierarchies in your cluster. cgroup v2 is the current version of the Linux cgroup API. cgroup v2 offers several improvements over cgroup v1, including a unified hierarchy, safer sub-tree delegation, new features such as Pressure Stall Information , and enhanced resource management and isolation. However, cgroup v2 has different CPU, memory, and I/O management characteristics than cgroup v1. Therefore, some workloads might experience slight differences in memory or CPU usage on clusters that run cgroup v2. You can switch between cgroup v1 and cgroup v2, as needed, by editing the node.config object. For more information, see "Configuring the Linux cgroup on your nodes" in the "Additional resources" of this section. 3.1. Enabling Linux cgroup v1 during installation You can enable Linux control group version 1 (cgroup v1) when you install a cluster by creating installation manifests. Procedure Create or edit the node.config object to specify the v1 cgroup: apiVersion: config.openshift.io/v1 kind: Node metadata: name: cluster spec: cgroupMode: "v2" Proceed with the installation as usual. Additional resources OpenShift Container Platform installation overview Configuring the Linux cgroup on your nodes

Commands:
apiVersion: config.openshift.io/v1 kind: Node metadata: name: cluster spec: cgroupMode: "v2"
Chapter 16. Concepts to automate Data Grid CLI commands When interacting with an external Data Grid in Kubernetes, the Batch CR allows you to automate this using standard oc commands. 16.1. When to use it Use this when automating interactions on Kubernetes. This avoids providing usernames and passwords and checking shell script outputs and their status. For human interactions, the CLI shell might still be a better fit. 16.2. Example The following Batch CR takes a site offline as described in the operational procedure Switch over to the secondary site . apiVersion: infinispan.org/v2alpha1 kind: Batch metadata: name: take-offline namespace: keycloak 1 spec: cluster: infinispan 2 config: | 3 site take-offline --all-caches --site=site-a site status --all-caches --site=site-a 1 The Batch CR must be created in the same namespace as the Data Grid deployment. 2 The name of the Infinispan CR. 3 A multiline string containing one or more Data Grid CLI commands. Once the CR has been created, wait for the status to show the completion. oc -n keycloak wait --for=jsonpath='{.status.phase}'=Succeeded Batch/take-offline Note Modifying a Batch CR instance has no effect. Batch operations are "one-time" events that modify Infinispan resources. To update .spec fields for the CR, or when a batch operation fails, you must create a new instance of the Batch CR. 16.3. Further reading For more information, see the Data Grid Operator Batch CR documentation .

Commands:
apiVersion: infinispan.org/v2alpha1 kind: Batch metadata: name: take-offline namespace: keycloak 1 spec: cluster: infinispan 2 config: | 3 site take-offline --all-caches --site=site-a site status --all-caches --site=site-a
-n keycloak wait --for=jsonpath='{.status.phase}'=Succeeded Batch/take-offline
26.5. Allowing IdM to Start with Expired Certificates After the IdM administrative server certificates expire, most IdM services become inaccessible. You can configure the underlying Apache and LDAP services to allow SSL access to the services even if the certificates are expired. If you allow limited access with expired certificates: Apache, Kerberos, DNS, and LDAP services will continue working. With these services active, users will be able to log in to the IdM domain. Client services that require SSL for access will still fail. For example, sudo will fail because it requires SSSD on IdM clients, and SSSD needs SSL to contact IdM. Important This procedure is intended only as a temporary workaround. Renew the required certificates as quickly as possible, and then revert the described changes. Configure the mod_nss module for the Apache server to not enforce valid certificates. Open the /etc/httpd/conf.d/nss.conf file. Set the NSSEnforceValidCerts parameter to off : Restart Apache. Make sure that validity checks are disabled for the LDAP directory server. To do this, verify that the nsslapd-validate-cert attribute is set to warn : If the attribute is not set to warn , change it: Restart the directory server.

Commands:
NSSEnforceValidCerts off
systemctl restart httpd.service
ldapsearch -h server.example.com -p 389 -D "cn=directory manager" -w secret -LLL -b cn=config -s base "(objectclass=*)" nsslapd-validate-cert dn: cn=config nsslapd-validate-cert: warn
ldapmodify -D "cn=directory manager" -w secret -p 389 -h server.example.com dn: cn=config changetype: modify replace: nsslapd-validate-cert nsslapd-validate-cert: warn
systemctl restart dirsrv.target
probe::netfilter.arp.in Name probe::netfilter.arp.in - - Called for each incoming ARP packet Synopsis netfilter.arp.in Values ar_hln Length of hardware address nf_stop Constant used to signify a 'stop' verdict nf_accept Constant used to signify an 'accept' verdict ar_tha Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address ar_data Address of ARP packet data region (after the header) outdev_name Name of network device packet will be routed to (if known) outdev Address of net_device representing output device, 0 if unknown nf_repeat Constant used to signify a 'repeat' verdict arphdr Address of ARP header indev_name Name of network device packet was received on (if known) nf_stolen Constant used to signify a 'stolen' verdict length The length of the packet buffer contents, in bytes ar_pln Length of protocol address ar_sha Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address pf Protocol family -- always " arp " nf_drop Constant used to signify a 'drop' verdict ar_pro Format of protocol address ar_sip Ethernet+IP only (ar_pro==0x800): source IP address indev Address of net_device representing input device, 0 if unknown ar_tip Ethernet+IP only (ar_pro==0x800): target IP address ar_hrd Format of hardware address ar_op ARP opcode (command) nf_queue Constant used to signify a 'queue' verdict

Commands:
Chapter 36. Scanning iSCSI Targets with Multiple LUNs or Portals With some device models (for example, from EMC and Netapp), however, a single target may have multiple logical units or portals. In this case, issue a sendtargets command to the host first to find new portals on the target. Then, rescan the existing sessions using: You can also rescan a specific session by specifying the session's SID value, as in: If your device supports multiple targets, you will need to issue a sendtargets command to the hosts to find new portals for each target. Then, rescan existing sessions to discover new logical units on existing sessions (i.e. using the --rescan option). Important The sendtargets command used to retrieve --targetname and --portal values overwrites the contents of the /var/lib/iscsi/nodes database. This database will then be repopulated using the settings in /etc/iscsi/iscsid.conf . However, this will not occur if a session is currently logged in and in use. To safely add new targets/portals or delete old ones, use the -o new or -o delete options, respectively. For example, to add new targets/portals without overwriting /var/lib/iscsi/nodes , use the following command: To delete /var/lib/iscsi/nodes entries that the target did not display during discovery, use: You can also perform both tasks simultaneously, as in: The sendtargets command will yield the following output: Example 36.1. Output of the sendtargets command For example, given a device with a single target, logical unit, and portal, with equallogic-iscsi1 as your target_name , the output should appear similar to the following: Note that proper_target_name and ip:port,target_portal_group_tag are identical to the values of the same name in Section 27.2, "iSCSI Initiator Creation" . At this point, you now have the proper --targetname and --portal values needed to manually scan for iSCSI devices. To do so, run the following command: Example 36.2. Full iscsiadm command Using our example (where proper_target_name is equallogic-iscsi1 ), the full command would be: [8] For information on how to retrieve a session's SID value, refer to Section 27.2, "iSCSI Initiator Creation" . [9] This is a single command split into multiple lines, to accommodate printed and PDF versions of this document. All concatenated lines - preceded by the backslash (\) - should be treated as one command, sans backslashes.

Commands:
iscsiadm -m session --rescan
iscsiadm -m session -r SID --rescan [8]
iscsiadm -m discovery -t st -p target_IP -o new
iscsiadm -m discovery -t st -p target_IP -o delete
iscsiadm -m discovery -t st -p target_IP -o delete -o new
ip:port,target_portal_group_tag proper_target_name
10.16.41.155:3260,0 iqn.2001-05.com.equallogic:6-8a0900-ac3fe0101-63aff113e344a4a2-dl585-03-1
iscsiadm --mode node --targetname proper_target_name --portal ip:port,target_portal_group_tag \ --login [9]
iscsiadm --mode node --targetname \ iqn.2001-05.com.equallogic:6-8a0900-ac3fe0101-63aff113e344a4a2-dl585-03-1 \ --portal 10.16.41.155:3260,0 --login [9]