mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 27. Python (DEPRECATED) Overview Python is a remarkably powerful dynamic programming language that is used in a wide variety of application domains. Python is often compared to Tcl, Perl, Ruby, Scheme or Java. The Python support is part of the camel-script module. Important Python in Apache Camel is deprecated and will be removed in a future release. Adding the script module To use Python in your routes you need to add a dependency on camel-script to your project as shown in Example 27.1, "Adding the camel-script dependency" . Example 27.1. Adding the camel-script dependency Static import To use the python() static method in your application code, include the following import statement in your Java source files: Built-in attributes Table 27.1, "Python attributes" lists the built-in attributes that are accessible when using Python. Table 27.1. Python attributes Attribute Type Value context org.apache.camel.CamelContext The Camel Context exchange org.apache.camel.Exchange The current Exchange request org.apache.camel.Message The IN message response org.apache.camel.Message The OUT message properties org.apache.camel.builder.script.PropertiesFunction Function with a resolve method to make it easier to use the properties component inside scripts. The attributes all set at ENGINE_SCOPE . Example Example 27.2, "Route using Python" shows a route that uses Python. Example 27.2. Route using Python Using the properties component To access a property value from the properties component, invoke the resolve method on the built-in properties attribute, as follows: Where PropKey is the key of the property you want to resolve, where the key value is of String type. For more details about the properties component, see Properties in the Apache Camel Component Reference Guide .

Commands:
<!-- Maven POM File --> <dependencies> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-script</artifactId> <version>USD{camel-version}</version> </dependency> </dependencies>
import static org.apache.camel.builder.script.ScriptBuilder.*;
<camelContext> <route> <from uri="direct:start"/> <choice> <when> <langauge langauge="python">if request.headers.get('user') = 'admin'</langauge> <to uri="seda:adminQueue"/> </when> <otherwise> <to uri="seda:regularQueue"/> </otherwise> </choice> </route> </camelContext>
.setHeader("myHeader").python("properties.resolve( PropKey )")
39.4. Hardware If you are having trouble configuring your hardware or just want to know what hardware is in your system, you can use the Hardware Browser application to display the hardware that can be probed. To start the program from the desktop, select System (the main menu on the panel) => Administration => Hardware or type hwbrowser at a shell prompt. As shown in Figure 39.4, " Hardware Browser " , it displays your CD-ROM devices, diskette drives, hard drives and their partitions, network devices, pointing devices, system devices, and video cards. Click on the category name in the left menu, and the information is displayed. Figure 39.4. Hardware Browser The Device Manager application can also be used to display your system hardware. This application can be started by selecting System (the main menu on the panel) => Administration => Hardware like the Hardware Browser . To start the application from a terminal, type hal-device-manager . Depending on your installation preferences, the graphical menu above may start this application or the Hardware Browser when clicked. The figure below illustrates the Device Manager window. Figure 39.5. Device Manager You can also use the lspci command to list all PCI devices. Use the command lspci -v for more verbose information or lspci -vv for very verbose output. For example, lspci can be used to determine the manufacturer, model, and memory size of a system's video card: The lspci is also useful to determine the network card in your system if you do not know the manufacturer or model number.

Commands:
00:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06) 00:00.1 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06) 00:01.0 VGA compatible controller: S3 Inc. Savage 4 (rev 04) 00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08) 00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 50) 00:0f.1 IDE interface: ServerWorks OSB4 IDE Controller 00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 04) 01:03.0 SCSI storage controller: Adaptec AIC-7892P U160/m (rev 02) 01:05.0 RAID bus controller: IBM ServeRAID Controller
8.4. Understanding the Network Teaming Daemon and the "Runners" The Team daemon, teamd , uses libteam to control one instance of the team driver. This instance of the team driver adds instances of a hardware device driver to form a " team " of network links. The team driver presents a network interface, team0 for example, to the other parts of the kernel. The interfaces created by instances of the team driver are given names such as team0 , team1 , and so forth in the documentation. This is for ease of understanding and other names can be used. The logic common to all methods of teaming is implemented by teamd ; those functions that are unique to the different load sharing and backup methods, such as round-robin, are implemented by separate units of code referred to as " runners " . Because words such as " module " and " mode " already have specific meanings in relation to the kernel, the word " runner " was chosen to refer to these units of code. The user specifies the runner in the JSON format configuration file and the code is then compiled into an instance of teamd when the instance is created. A runner is not a plug-in because the code for a runner is compiled into an instance of teamd as it is being created. Code could be created as a plug-in for teamd should the need arise. The following runners are available at time of writing. broadcast (data is transmitted over all ports) round-robin (data is transmitted over all ports in turn) active-backup (one port or link is used while others are kept as a backup) loadbalance (with active Tx load balancing and BPF-based Tx port selectors) lacp (implements the 802.3ad Link Aggregation Control Protocol) In addition, the following link-watchers are available: ethtool (Libteam lib uses ethtool to watch for link state changes). This is the default if no other link-watcher is specified in the configuration file. arp_ping (The arp_ping utility is used to monitor the presence of a far-end hardware address using ARP packets.) nsna_ping (Neighbor Advertisements and Neighbor Solicitation from the IPv6 Neighbor Discovery protocol are used to monitor the presence of a neighbor's interface) There are no restrictions in the code to prevent a particular link-watcher from being used with a particular runner, however when using the lacp runner, ethtool is the only recommended link-watcher.

Commands:
Chapter 12. The Memcached Interface Memcached is an in-memory caching system used to improve response and operation times for database-driven websites. The Memcached caching system defines a text based protocol called the Memcached protocol. The Memcached protocol uses in-memory objects or (as a last resort) passes to a persistent store such as a special memcached database. Red Hat JBoss Data Grid offers a server that uses the Memcached protocol, removing the necessity to use Memcached separately with JBoss Data Grid. Additionally, due to JBoss Data Grid's clustering features, its data failover capabilities surpass those provided by Memcached. Report a bug 12.1. About Memcached Servers Red Hat JBoss Data Grid contains a server module that implements the memcached protocol. This allows memcached clients to interact with one or multiple JBoss Data Grid based memcached servers. The servers can be either: Standalone, where each server acts independently without communication with any other memcached servers. Clustered, where servers replicate and distribute data to other memcached servers. Report a bug

Commands:
4.7. Online Data Relocation You can move data while the system is in use with the pvmove command. The pvmove command breaks up the data to be moved into sections and creates a temporary mirror to move each section. For more information on the operation of the pvmove command, see the pvmove (8) man page. Because the pvmove command uses mirroring, it is not cluster-aware and needs exclusive access to a volume. For information on activating logical volumes on individual nodes in a cluster, see Section 4.8, "Activating Logical Volumes on Individual Nodes in a Cluster" . The following command moves all allocated space off the physical volume /dev/sdc1 to other free physical volumes in the volume group: The following command moves just the extents of the logical volume MyLV . Since the pvmove command can take a long time to execute, you may want to run the command in the background to avoid display of progress updates in the foreground. The following command moves all extents allocated to to the physical volume /dev/sdc1 over to /dev/sdf1 in the background. The following command reports the progress of the move as a percentage at five second intervals.

Commands:
pvmove /dev/sdc1
pvmove -n MyLV /dev/sdc1
pvmove -b /dev/sdc1 /dev/sdf1
pvmove -i5 /dev/sdd1
Appendix A. Revision History Note that revision numbers relate to the edition of this manual, not to version numbers of Red Hat Certificate System. Revision History Revision 10.3-0 Tue Feb 22 2022 Florian Delehaye Various fixes for 10.3. Revision 10.2-0 Wed Jul 14 2021 Florian Delehaye Various fixes for 10.2. Revision 10.1-2 Fri Feb 27 2021 Florian Delehaye Corrections for setting up HSMs in FIPS mode and various minor edits. Revision 10.1-1 Mon Jan 25 2021 Florian Delehaye Various fixes and improvements. Revision 10.1-0 Wed Dec 3 2020 Florian Delehaye Red Hat Certificate System 10.1 release of the guide. Revision 10.0-1 Tues Nov 3 2020 Florian Delehaye Added Upgrade and Migration procedures for RHCS 10. Revision 10.0-0 Thur Sep 17 2020 Florian Delehaye Red Hat Certificate System 10.0 release of the guide.

Commands:
Chapter 12. Activating or deactivating a KIE container on KIE Server You can now stop the creation of new process instances from a given container by deactivating it but at the same time continue working on its existing process instances and tasks. In case the deactivation is temporary, you can activate the container again later. The activation or deactivation of KIE containers do not require restarting of KIE server. Prerequisites A KIE container has been created and configured in Business Central. Procedure Log in to Business Central. In the main menu, click Menu Deploy Execution Servers . From the Server Configurations pane, which is on the left of the page, select your server. From the Deployment Units pane, select the deployment unit you want to activate or deactivate. Click Activate or Deactivate in the upper-right corner of the deployment unit pane. You cannot create a process instance from a KIE container once it is deactivated.

Commands:
2.13. Using the Notification API The cgroups notification API allows user space applications to receive notifications about the changing status of a cgroup. Currently, the notification API only supports monitoring of the Out of Memory (OOM) control file: memory.oom_control . To create a notification handler, write a C program using the following instructions: Using the eventfd() function, create a file descriptor for event notifications. For more information, refer to the eventfd(2) man page. To monitor the memory.oom_control file, open it using the open() function. For more information, refer to the open(2) man page. Use the write() function to write the following arguments to the cgroup.event_control file of the cgroup whose memory.oom_control file you are monitoring: where: event_file_descriptor is used to open the cgroup.event_control file, and OOM_control_file_descriptor is used to open the respective memory.oom_control file. For more information on writing to a file, refer to the write(1) man page. When the above program is started, it will be notified of any OOM situation in the cgroup it is monitoring. Note that OOM notifications only work in non-root cgroups. For more information on the memory.oom_control tunable parameter, refer to Section 3.7, "memory" . For more information on configuring notifications for OOM control, refer to Example 3.3, "OOM Control and Notifications" .

Commands:
<event_file_descriptor> <OOM_control_file_descriptor>
5.2. GFS2 File System Hangs and Requires Reboot of One Node If your GFS2 file system hangs and does not return commands run against it, but rebooting one specific node returns the system to normal, this may be indicative of a locking problem or bug. Should this occur, gather the following data: The gfs2 lock dump for the file system on each node: The DLM lock dump for the file system on each node: You can get this information with the dlm_tool : In this command, lsname is the lockspace name used by DLM for the file system in question. You can find this value in the output from the group_tool command. The output from the sysrq -t command. The contents of the /var/log/messages file. Once you have gathered that data, you can open a ticket with Red Hat Support and provide the data you have collected.

Commands:
cat /sys/kernel/debug/gfs2/ fsname /glocks >glocks. fsname . nodename
dlm_tool lockdebug -sv lsname .
2.28. RHEA-2011:0605 - new package: perl-TermReadKey A new perl-TermReadKey package is now available for Red Hat Enterprise Linux 6. The Term::ReadKey module provides a mechanism for Perl scripts to control various terminal driver modes, perform non-blocking reads, and interact with a terminal. This enhancement update adds the perl-TermReadKey package to Red Hat Enterprise Linux 6. (BZ# 665415 ) All users who require the Term::ReadKey Perl module should install this new package.

Commands:
Appendix C. Using AMQ Broker with the examples The AMQ JMS examples require a running message broker with a queue named queue . Use the procedures below to install and start the broker and define the queue. C.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> . C.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 ... C.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named queue . USD <broker-instance-dir> /bin/artemis queue create --name queue --address queue --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. C.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:26:53 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 queue --address queue --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
Chapter 2. Eclipse Temurin features Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. For the list of changes and security fixes that the latest OpenJDK 17 release of Eclipse Temurin includes, see OpenJDK 17.0.9 Released . 2.1. New features and enhancements Review the following release notes to understand new features and feature enhancements included with the Eclipse Temurin 17.0.9 release: Increased default group size of TLS Diffie-Hellman In OpenJDK 17.0.9, the JDK implementation of TLS 1.2 uses a default Diffie-Hellman key size of 2048 bits. This supersedes the behavior in releases where the default Diffie-Hellman key size was 1024 bits. This enhancement is relevant when a TLS_DHE cipher suite is negotiated and either the client or the server does not support Finite Field Diffie-Hellman Ephemeral (FFDHE) parameters. The JDK TLS implementation supports FFDHE, which is enabled by default and can negotiate a stronger key size. As a workaround, you can revert to the key size by setting the jdk.tls.ephemeralDHKeySize system property to 1024 . However, to mitigate risk, consider using the default key size of 2048 bits. Note This change does not affect TLS 1.3, which already uses a minimum Diffie-Hellman key size of 2048 bits. See JDK-8301700 (JDK Bug System) . Output of -XshowSettings:locale option includes tzdata version In OpenJDK 17.0.9, the -XshowSettings launcher option also prints the tzdata version that the JDK uses. The tzdata version is displayed as part of the output for the -XshowSettings:locale option. For example: See JDK-8305950 (JDK Bug System) . Certigna root CA certificate added In OpenJDK 17.0.9, the cacerts truststore includes the following Certigna root certificate: Name: Certigna (Dhimyotis) Alias name: certignarootca Distinguished name: CN=Certigna Root CA, OU=0002 48146308100036, O=Dhimyotis, C=FR See JDK-8314960 (JDK Bug System) . 2.2. Deprecated features Review the following release notes to understand pre-existing features that have been either deprecated or removed in Eclipse Temurin 17.0.9: SECOM Trust Systems root CA1 certificate removed OpenJDK 17.0.9 removes the following root certificate from the cacerts truststore: Alias name: secomscrootca1 [jdk] Distinguished name: OU=Security Communication RootCA1, O=SECOM Trust.net, C=JP See JDK-8295894 (JDK Bug System) . Revised on 2024-05-03 15:37:37 UTC

Commands:
Locale settings: default locale = English default display locale = English default format locale = English tzdata version = 2023c
7.237. xorg-x11-fonts 7.237.1. RHBA-2015:1270 - xorg-x11-fonts bug fix update Updated xorg-x11-fonts packages that fix one bug are now available for Red Hat Enterprise Linux 6. The xorg-x11-fonts packages provide X.Org X Window System fonts. Bug Fix BZ# 1089118 Previously, the Japanese TrueType fonts provided by the ipa-gothic-fonts package were not available through the core X11 font system. This update fixes the xorg-x11-fonts packages, which now correctly provide the required encodings.dir directory listings. As a result, the Japanese TrueType fonts are now available in the core X11 font system as expected. Users of xorg-x11-fonts are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 11. Monitoring Kafka Monitoring data allows you to monitor the performance and health of Streams for Apache Kafka. You can configure your deployment to capture metrics data for analysis and notifications. Metrics data is useful when investigating issues with connectivity and data delivery. For example, metrics data can identify under-replicated partitions or the rate at which messages are consumed. Alerting rules can provide time-critical notifications on such metrics through a specified communications channel. Monitoring visualizations present real-time metrics data to help determine when and how to update the configuration of your deployment. Example metrics configuration files are provided with Streams for Apache Kafka. You can employ the following tools for metrics and monitoring: Prometheus Prometheus pulls metrics from Kafka, ZooKeeper and Kafka Connect clusters. The Prometheus Alertmanager plugin handles alerts and routes them to a notification service. Kafka Exporter Kafka Exporter adds additional Prometheus metrics. Grafana Grafana Labs provides dashboard visualizations of Prometheus metrics. OpenTelemetry OpenTelemetry complements the gathering of metrics data by providing a facility for end-to-end tracking of messages through Streams for Apache Kafka. Cruise Control Cruise Control monitors data distribution and performs data rebalances, based on workload data, across a Kafka cluster.

Commands:
Chapter 46. Installing and running IBM WebSphere Application Server IBM WebSphere Application Server must be installed and running for you to apply many of the configurations that accommodate KIE Server. This section describes how to install and start IBM WebSphere. For the most up-to-date and detailed installation instructions, see the IBM Knowledge Center . Procedure Download IBM Installation Manager version 1.8.5 or later from the IBM Installation Manager and Packaging Utility download links page. IBM Installation Manager is required for installing IBM WebSphere. Extract the downloaded archive and run the following command as the root user in the new directory: The IBM Installation Manager opens. Go to File Preferences and click Add Repository . In the Add Repository window, enter the repository URL for IBM WebSphere 9.0. You can find all the repository URLs in the Online product repositories for IBM WebSphere Application Server offerings page of the IBM Knowledge Center. In your command terminal, navigate to the IBM WebSphere Application Server folder location that you specified during the installation. Change to the /bin directory and run a command similar to the following example to create an IBM WebSphere profile, user name, and password. A profile defines the run time environment. The profile includes all the files that the server processes in the runtime environment and that you can change. The user is required for login. In your command terminal, navigate to the bin directory within the profile that you created (for example, /profiles/testprofile/bin ) and run the following command to start the IBM WebSphere Application Server instance: Replace <SERVER_NAME> with the IBM WebSphere Application Server name defined in Servers Server Types IBM WebSphere Application Servers of the WebSphere Integrated Solutions Console. Open the following URL in a web browser: <HOST> is the system name or IP address of the target server. For example, to start the WebSphere Integrated Solutions Console for a local instance of IBM WebSphere running on your system, enter the following URL in a web browser: When the login page of the WebSphere Integrated Solutions Console appears, enter your administrative credentials.

Commands:
sudo ./install
sudo ./manageprofiles.sh -create -profileName testprofile -profilePath /profiles/testprofile -adminUserName websphere -adminPassword password123
sudo ./startServer.sh <SERVER_NAME>
http://<HOST>:9060/ibm/console
http://localhost:9060/ibm/console
Part III. Red Hat OpenShift Container Platform Bare Metal Hardware Certification Note This chapter is applicable only for Red Hat OpenShift Container Platform bare metal hardware certification. The Red Hat OpenShift Platform Bare Metal hardware certification verifies that your bare-metal servers are ready to be orchestrated and deployed remotely in an OpenStack environment. The certification has two components: Installer-provisioner infrastructure (IPI) Assisted installer You can certify your bare-metal server for either component or both. The following sections will give you detailed instructions for each of them when applicable.

Commands: