mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Projects Projects are a logical collection of rulebooks. They must be a git repository and only http protocol is supported. The rulebooks of a project must be located in the path defined for Event-Driven Ansible content in Ansible collections: /extensions/eda/rulebooks at the root of the project. 3.1. Setting up a new project Prerequisites You are logged in to the Event-Driven Ansible controller Dashboard as a Content Consumer. You have set up a credential, if necessary. For more information, see the Setting up credentials section. You have an existing repository containing rulebooks that are integrated with playbooks contained in a repository to be used by automation controller. Procedure Log in to the Event-Driven Ansible controller Dashboard. From the navigation panel, select Projects Create project . Insert the following: Name Enter project name. Description This field is optional. SCM type Git is the only SCM type available for use. SCM URL HTTP[S] protocol address of a repository, such as GitHub or GitLab. Note You cannot edit the SCM URL after you create the project. Credential This field is optional. This is the token needed to utilize the SCM URL. Options The Verify SSL option is enabled by default. Enabling this option verifies the SSL with HTTPS when the project is imported. Note You can disable this option if you have a local repository that uses self-signed certificates. Select Create project . Your project is now created and can be managed in the Projects screen. After saving the new project, the project's details page is displayed. From there or the Projects list view, you can edit or delete it. 3.2. Projects list view On the Projects page, you can view the projects that you have created along with the Status and the Git hash . Note If a rulebook changes in source control you can re-sync a project by selecting the sync icon to the project from the Projects list view. The Git hash updates represent the latest commit on that repository. An activation must be restarted or recreated if you want to use the updated project. 3.3. Editing a project Procedure From the Projects list view, select the More Actions icon ... to the desired project. Select Edit project . Enter the required changes and select Save project . 3.4. Deleting a project Procedure From the Projects list view, select the More Actions icon ... to the desired project. Select Delete project . In the popup window, select Yes, I confirm that I want to delete this project . Select Delete project .

Commands:
4.5. Uploading the Image into Google Cloud Storage You must log in using gcloud auth login command before uploading the image to the Google cloud. Running the command will open a browser and prompts for google account credentials. The PROJECT_ID is set by default and follow the subsequent CLI instructions and make changes if required. Use Google's gsutil command to create the storage bucket and upload the image.

Commands:
gsutil mb gs://rhgs_image_upload gsutil cp disk.raw.tar.gz gs://rhgs_image_upload
Chapter 27. Adding the IdM CA service to an IdM server in a deployment with a CA If your Identity Management (IdM) environment already has the IdM certificate authority (CA) service installed but a particular IdM server, idmserver , was installed as an IdM replica without a CA, you can add the CA service to idmserver by using the ipa-ca-install command. Note This procedure is identical for both the following scenarios: The IdM CA is a root CA. The IdM CA is subordinate to an external, root CA. Prerequisites You have root permissions on idmserver . The IdM server is installed on idmserver . Your IdM deployment has a CA installed on another IdM server. You know the IdM Directory Manager password. Procedure On idmserver , install the IdM Certificate Server CA:

Commands:
[root@idmserver ~] ipa-ca-install
Chapter 299. Service Component Available as of Camel version 2.22 299.1. Using the service endpoint 299.2. URI format 299.3. Options The Service component supports 3 options, which are listed below. Name Description Default Type service (advanced) Inject the service to use. ServiceRegistry serviceSelector (advanced) Inject the service selector used to lookup the ServiceRegistry to use. Selector resolveProperty Placeholders (advanced) Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. true boolean The Service endpoint is configured using URI syntax: with the following path and query parameters: 299.3.1. Path Parameters (1 parameters): Name Description Default Type delegateUri Required The endpoint uri to expose as service String 299.3.2. Query Parameters (4 parameters): Name Description Default Type bridgeErrorHandler (consumer) Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. false boolean exceptionHandler (consumer) To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. ExceptionHandler exchangePattern (consumer) Sets the exchange pattern when the consumer creates an exchange. ExchangePattern synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean 299.4. Spring Boot Auto-Configuration The component supports 4 options, which are listed below. Name Description Default Type camel.component.service.enabled Whether to enable auto configuration of the service component. This is enabled by default. Boolean camel.component.service.resolve-property-placeholders Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. true Boolean camel.component.service.service Inject the service to use. The option is a org.apache.camel.cloud.ServiceRegistry type. String camel.component.service.service-selector Inject the service selector used to lookup the ServiceRegistry to use. The option is a org.apache.camel.cloud.ServiceRegistry.Selector type. String 299.5. Implementations Camel provide the following ServiceRegistry implementations: camel-consul camel-zookeeper camel-spring-cloud 299.6. See Also Configuring Camel Component Endpoint Getting Started

Commands:
service:serviceName:endpoint[?options]
service:delegateUri
E.2.20. /proc/modules This file displays a list of all modules loaded into the kernel. Its contents vary based on the configuration and use of your system, but it should be organized in a similar manner to this sample /proc/modules file output: Note This example has been reformatted into a readable format. Most of this information can also be viewed via the /sbin/lsmod command. The first column contains the name of the module. The second column refers to the memory size of the module, in bytes. The third column lists how many instances of the module are currently loaded. A value of zero represents an unloaded module. The fourth column states if the module depends upon another module to be present in order to function, and lists those other modules. The fifth column lists what load state the module is in: Live , Loading , or Unloading are the only possible values. The sixth column lists the current kernel memory offset for the loaded module. This information can be useful for debugging purposes, or for profiling tools such as oprofile .

Commands:
nfs 170109 0 - Live 0x129b0000 lockd 51593 1 nfs, Live 0x128b0000 nls_utf8 1729 0 - Live 0x12830000 vfat 12097 0 - Live 0x12823000 fat 38881 1 vfat, Live 0x1287b000 autofs4 20293 2 - Live 0x1284f000 sunrpc 140453 3 nfs,lockd, Live 0x12954000 3c59x 33257 0 - Live 0x12871000 uhci_hcd 28377 0 - Live 0x12869000 md5 3777 1 - Live 0x1282c000 ipv6 211845 16 - Live 0x128de000 ext3 92585 2 - Live 0x12886000 jbd 65625 1 ext3, Live 0x12857000 dm_mod 46677 3 - Live 0x12833000
10.5. Dynamically Changing a Host Physical Machine or a Network Bridge that is Attached to a Virtual NIC This section demonstrates how to move the vNIC of a guest virtual machine from one bridge to another while the guest virtual machine is running without compromising the guest virtual machine Prepare guest virtual machine with a configuration similar to the following: Prepare an XML file for interface update: Start the guest virtual machine, confirm the guest virtual machine's network functionality, and check that the guest virtual machine's vnetX is connected to the bridge you indicated. Update the guest virtual machine's network with the new interface parameters with the following command: On the guest virtual machine, run service network restart . The guest virtual machine gets a new IP address for virbr1. Check the guest virtual machine's vnet0 is connected to the new bridge(virbr1)

Commands:
<interface type='bridge'> <mac address='52:54:00:4a:c9:5e'/> <source bridge='virbr0'/> <model type='virtio'/> </interface>
cat br1.xml
<interface type='bridge'> <mac address='52:54:00:4a:c9:5e'/> <source bridge='virbr1'/> <model type='virtio'/> </interface>
brctl show bridge name bridge id STP enabled interfaces virbr0 8000.5254007da9f2 yes virbr0-nic vnet0 virbr1 8000.525400682996 yes virbr1-nic
virsh update-device test1 br1.xml Device updated successfully
brctl show bridge name bridge id STP enabled interfaces virbr0 8000.5254007da9f2 yes virbr0-nic virbr1 8000.525400682996 yes virbr1-nic vnet0
5.3.5. Use Kerberos Authentication One of the most glaring flaws inherent when NIS is used for authentication is that whenever a user logs into a machine, a password hash from the /etc/shadow map is sent over the network. If an intruder gains access to an NIS domain and sniffs network traffic, usernames and password hashes can be quietly collected. With enough time, a password cracking program can guess weak passwords, and an attacker can gain access to a valid account on the network. Since Kerberos uses secret-key cryptography, no password hashes are ever sent over the network, making the system far more secure. For more about Kerberos, refer to the chapter titled Kerberos in the Reference Guide .

Commands:
7.3. Understanding the pkispawn Utility In Red Hat Certificate System, you set up the individual public key infrastructure (PKI) subsystems using the pkispawn utility. During the setup, pkispawn : Reads the default values from the /usr/share/pki/server/etc/default.cfg file. For further details, see the pki_default.cfg (5) man page. Important Do not edit the /usr/share/pki/server/etc/default.cfg file. Instead, create a configuration file and that overrides the defaults, and pass it to the pkispawn utility. For details about using a configuration file, see Section 7.7, "Two-step Installation" . Uses the passwords and other deployment-specific information provided depending on the setup mode: Interactive mode: The user is asked for the individual settings during the setup. Use this mode for simple deployments. Batch mode: The values are read from a configuration file the user provides. Parameters not set in the configuration file use the defaults. Performs the installation of the requested PKI subsystem. Passes the settings to a Java servlet that performs the configuration based on the settings. Use the pkispawn utility to install: A root CA. For details, see Section 7.4, "Setting Up a Root Certificate Authority" . A subordinate CA or any other subsystem. For details, see Section 7.6, "Setting up Additional Subsystems" . Note See Section 7.4, "Setting Up a Root Certificate Authority" on how to set up a root CA using the pkispawn utility. For a setup of a subordinate CA or non-CA subsystems, see Section 7.8, "Setting up Subsystems with an External CA" . For further information about pkispawn and examples, see the pkispawn (8) man page.

Commands:
Chapter 6. Uninstalling a cluster on Azure Stack Hub You can remove a cluster that you deployed to Azure Stack Hub. 6.1. Removing a cluster that uses installer-provisioned infrastructure You can remove a cluster that uses installer-provisioned infrastructure from your cloud. Note After uninstallation, check your cloud provider for any resources not removed properly, especially with user-provisioned infrastructure clusters. There might be resources that the installation program did not create or that the installation program is unable to access. Prerequisites You have a copy of the installation program that you used to deploy the cluster. You have the files that the installation program generated when you created your cluster. While you can uninstall the cluster using the copy of the installation program that was used to deploy it, using OpenShift Container Platform version 4.13 or later is recommended. The removal of service principals is dependent on the Microsoft Azure AD Graph API. Using version 4.13 or later of the installation program ensures that service principals are removed without the need for manual intervention, if and when Microsoft decides to retire the Azure AD Graph API. Procedure On the computer that you used to install the cluster, go to the directory that contains the installation program, and run the following command: USD ./openshift-install destroy cluster \ --dir <installation_directory> --log-level info 1 2 1 For <installation_directory> , specify the path to the directory that you stored the installation files in. 2 To view different details, specify warn , debug , or error instead of info . Note You must specify the directory that contains the cluster definition files for your cluster. The installation program requires the metadata.json file in this directory to delete the cluster. Optional: Delete the <installation_directory> directory and the OpenShift Container Platform installation program.

Commands:
./openshift-install destroy cluster --dir <installation_directory> --log-level info 1 2
Chapter 33. XQuery Overview XQuery was originally devised as a query language for data stored in XML form in a database. The XQuery language enables you to select parts of the current message, when the message is in XML format. XQuery is a superset of the XPath language; hence, any valid XPath expression is also a valid XQuery expression. Java syntax You can pass an XQuery expression to xquery() in several ways. For simple expressions, you can pass the XQuery expressions as a string ( java.lang.String ). For longer XQuery expressions, you might prefer to store the expression in a file, which you can then reference by passing a java.io.File argument or a java.net.URL argument to the overloaded xquery() method. The XQuery expression implicitly acts on the message content and returns a node set as the result. Depending on the context, the return value is interpreted either as a predicate (where an empty node set is interpreted as false) or as an expression. Adding the Saxon module To use XQuery in your routes you need to add a dependency on camel-saxon to your project as shown in Example 33.1, "Adding the camel-saxon dependency" . Example 33.1. Adding the camel-saxon dependency Camel on EAP deployment The camel-saxon component is supported by the Camel on EAP (Wildfly Camel) framework, which offers a simplified deployment model on the Red Hat JBoss Enterprise Application Platform (JBoss EAP) container. Static import To use the xquery() static method in your application code, include the following import statement in your Java source files: Variables Table 33.1, "XQuery variables" lists the variables that are accessible when using XQuery. Table 33.1. XQuery variables Variable Type Description exchange Exchange The current Exchange in.body Object The body of the IN message out.body Object The body of the OUT message in.headers. key Object The IN message header whose key is key out.headers. key Object The OUT message header whose key is key key Object The Exchange property whose key is key Example Example 33.2, "Route using XQuery" shows a route that uses XQuery. Example 33.2. Route using XQuery

Commands:
<!-- Maven POM File --> <dependencies> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-saxon</artifactId> <version>USD{camel-version}</version> </dependency> </dependencies>
import static org.apache.camel.component.xquery.XQueryBuilder.xquery;
<camelContext> <route> <from uri="activemq:MyQueue"/> <filter> <language langauge="xquery">/foo:person[@name='James']</language> <to uri="mqseries:SomeOtherQueue"/> </filter> </route> </camelContext>
Chapter 9. Batch Processing Batch processing allows multiple operation requests to be grouped in a sequence and executed together as a unit. If any of the operation requests in the sequence fail, the entire group of operations is rolled back. Note Batch mode does not support conditional statements. Enter batch mode with the batch management CLI command. Batch mode is indicated by the hash symbol ( # ) in the prompt. Add operation requests to the batch. Once in batch mode, enter operation requests as normal. The operation requests are added to the batch in the order they are entered. You can edit and reorder batch commands. You can also store a batch for processing at a later time. See Batch Mode Commands for a full list of commands available for working with batches. Run the batch. Once the entire sequence of operation requests is entered, run the batch with the run-batch command. The entered sequence of operation requests is completed as a batch and prints the result to the terminal: The batch executed successfully. Batch Commands in External Files Frequently-run batch commands can be stored in an external text file and can be loaded either by passing the full path to the file as an argument to the batch command or executed directly by being passed as an argument to the run-batch command. You can create a batch command file by using a text editor and placing each command on its own line. The following command will load the myscript.txt file in batch mode. The commands from this file can then be edited or removed. New commands can be inserted. Changes made in this batch session do not persist to the myscript.txt file. The following will immediately run the batch commands stored in the file myscript.txt The entered sequence of operation requests is completed as a batch.

Commands:
batch
run-batch
batch --file=myscript.txt
run-batch --file=myscript.txt
Chapter 2. Configuring notifications and integrations for Insights tasks events You can configure the notifications service on the Red Hat Hybrid Cloud Console to send notifications whenever the Red Hat Insights tasks service detects certain events that occur during the start and execution of a task. Using the notifications service can provide an alternative to having to continually check the tasks Activity tab for events related to a task's status. You can find the notifications service settings at Red Hat Hybrid Cloud Console > Settings > Notifications . When you begin to think about configuring events for which you want notifications for Insights tasks, it is important to understand the difference between an Insights task, an Insights task execution, and an Insights task job, and how they work to accomplish a specific task. Insights task: a predefined script or playbook that is designed to accomplish a specific task. Insights task execution: an instance of running that script or playbook on one or more systems. Insights task job: the execution of a specific task on a specific system. For example, you can configure the notifications service to automatically send an email message when an Insights task starts, completes, or fails. As another example, you can configure the notifications service to automatically send an email message when an Insights task job starts or completes. In addition to sending email messages, you can configure the notifications service to send event data in other ways: Using an authenticated client to query Red Hat Insights APIs for event data Using webhooks to send events to third-party applications that accept inbound requests Integrating notifications with applications such as Splunk to route tasks events to the application dashboard, or to your preferred messaging application such as Slack or Microsoft Teams. Configuring the notifications service to inform members of your Red Hat account of tasks events requires three main steps: An Organization Administrator creates a User Access group with the Notifications administrator role, and then adds account members to the group. A Notifications administrator sets up behavior groups for events in the notifications service. Behavior groups specify the delivery method for each notification. The Notifications administrator selects the event types to make available for the specified group of users. For example, a behavior group can specify whether to send email notifications to all users, or just to Organization Administrators. Members on the account who want to receive email notifications about events must set their user preferences so that they receive individual emails for each event. Note You must be a Notifications administrator to view configurable tasks events. You can learn more about events and notifications by using resources in the following Additional Resources section. ADDITIONAL RESOURCES See Configuring notifications on the Red Hat Hybrid Cloud Console for more information about how to set up notifications for tasks events.

Commands:
Chapter 11. Known issues in Red Hat Process Automation Manager 7.13.2 This section lists known issues with Red Hat Process Automation Manager 7.13.2. 11.1. Red Hat OpenShift Container Platform PostgreSQL 13 Pod won't start because of an incompatible data dirctory [ RHPAM-4464 ] Issue: When you start a PostgreSQL pod after you upgrade the operator, the pod fails to start and you receive the following message: Incompatible data directory. This container image provides PostgreSQL '13', but data directory is of version '10'. This image supports automatic data directory upgrade from '12', please carefully consult image documentation about how to use the 'USDPOSTGRESQL_UPGRADE' startup option. Workaround: Check the version of PostgreSQL: If the PostgreSQL version returned is 12.x or earlier, upgrade PostgreSQL: Red Hat Process Automation Manager version PostgreSQL version Upgrade instructions 7.13.1 7.10 Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 12.x. 7.13.2 7.10 1. Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 12.x. 2. Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 13.x. 7.13.2 7.12 Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 13.x. Verify that PostpreSQL has been upgraded to your required version:

Commands:
postgres -V
postgres -V
Appendix A. Using your subscription Integration is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing your account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading zip and tar files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Scroll down to INTEGRATION AND AUTOMATION . Click Red Hat Integration to display the Red Hat Integration downloads page. Click the Download link for your component. Revised on 2024-03-22 13:11:14 UTC

Commands: