mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. JBoss EAP 8.0 update methods You can update JBoss EAP 8.0 using the following methods: JBoss EAP Installation Manager Management CLI Web console RPM From JBoss EAP 8.0 onward, the JBoss EAP server can be updated in either online or offline mode. These modes are supported by all the update methods. Online update: You can update JBoss EAP directly from an online repository. You must have access to the Red Hat repositories or their mirrors to use this mode. This option always updates to the latest available JBoss EAP 8.0 update. Offline update: You can update JBoss EAP from a local file-system. Use the offline update mode if you do not have online access to the Red Hat repositories or their mirrors. You will need to download the latest update and distribute it to your systems. Depending on your requirements, choose one of the listed update methods. The following table provides a brief overview of each type of update method. Table 1.1. Update Methods Method Description JBoss EAP Installation Manager Use this method if you want to update a local JBoss EAP 8.x server that is not running. Management CLI Use this method if you want to update a remote JBoss EAP 8.x server. Web console Use this method if you want to update a 8.x server that is running either in a standalone or managed domain mode using management console GUI. RPM Installation Use this method if you want to update a JBoss EAP 8.x server installed using the RPM installation method. You can run JBoss EAP on the following cloud platforms. This documentation does not cover provisioning on other cloud platforms. See the related documentation. JBoss EAP on OpenShift. Additional resources JBoss EAP on OpenShift .

Commands:
Chapter 43. Using the standalone library perspective You can use the library perspective of Business Central to select a project you want to edit. You can also perform all the authoring functions on the selected project. The standalone library perspective can be used in two ways, with and without using the header=UberfireBreadcrumbsContainer parameter. The difference is that the address with the header parameter will display a breadcrumb trail on top of the library perspective. Using this link you can create additional Spaces for your projects. Procedure Log in to Business Central. In a web browser, enter the appropriate web address: For accessing the standalone library perspective without the header parameter http://localhost:8080/business-central/kie-wb.jsp?standalone=true&perspective=LibraryPerspective The standalone library perspective without the breadcrumb trail opens in the browser. For accessing the standalone library perspective with the header parameter http://localhost:8080/business-central/kie-wb.jsp?standalone=true&perspective=LibraryPerspective&header=UberfireBreadcrumbsContainer The standalone library perspective with the breadcrumb trail opens in the browser.

Commands:
Chapter 177. Jing Component Available as of Camel version 1.1 The Jing component uses the Jing Library to perform XML validation of the message body using either RelaxNG XML Syntax RelaxNG Compact Syntax Maven users will need to add the following dependency to their pom.xml for this component: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-jing</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> Note that the MSV component can also support RelaxNG XML syntax. 177.1. URI format Camel 2.16 jing:someLocalOrRemoteResource From Camel 2.16 the component use jing as name, and you can use the option compactSyntax to turn on either RNG or RNC mode. 177.2. Options The Jing component has no options. The Jing endpoint is configured using URI syntax: with the following path and query parameters: 177.2.1. Path Parameters (1 parameters): Name Description Default Type resourceUri Required URL to a local resource on the classpath or a full URL to a remote resource or resource on the file system which contains the schema to validate against. String 177.2.2. Query Parameters (2 parameters): Name Description Default Type compactSyntax (producer) Whether to validate using RelaxNG compact syntax or not. By default this is false for using RelaxNG XML Syntax (rng) And true is for using RelaxNG Compact Syntax (rnc) false boolean synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean 177.3. Spring Boot Auto-Configuration The component supports 2 options, which are listed below. Name Description Default Type camel.component.jing.enabled Enable jing component true Boolean camel.component.jing.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 177.4. Example The following example shows how to configure a route from the endpoint direct:start which then goes to one of two endpoints, either mock:valid or mock:invalid based on whether or not the XML matches the given RelaxNG Compact Syntax schema (which is supplied on the classpath). 177.5. See Also Configuring Camel Component Endpoint Getting Started

Commands:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-jing</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>
jing:someLocalOrRemoteResource
jing:resourceUri
Chapter 1. Red Hat Process Automation Manager Spring Boot business applications Spring Framework is a Java platform that provides comprehensive infrastructure support for developing Java applications. Spring Boot is a lightweight framework based on Spring Boot starters. Spring Boot starters are pom.xml files that contain a set of dependency descriptors that you can include in your Spring Boot project. Red Hat Process Automation Manager Spring Boot business applications are flexible, UI-agnostic logical groupings of individual services that provide certain business capabilities. Business applications are based on Spring Boot starters. They are usually deployed separately and can be versioned individually. A complete business application enables a domain to achieve specific business goals, for example, order management or accommodation management. After you create and configure your business application, you can deploy it to an existing service or to the cloud, through OpenShift. Business applications can contain one or more of the following projects and more than one project of the same type: Business assets (KJAR): Contains business processes, rules, and forms and are easily imported into Business Central. Data model: Data model projects provide common data structures that are shared between the service projects and business assets projects. This enables proper encapsulation, promotes reuse, and reduces shortcuts. Each service project can expose its own public data model. Dynamic assets: Contains assets that you can use with case management. Service: A deployable project that provides the actual service with various capabilities. It includes the business logic that operates your business. In most cases, a service project includes business assets and data model projects. A business application can split services into smaller component service projects for better manageability.

Commands:
Chapter 10. Predictive Model Markup Language (PMML) Predictive Model Markup Language (PMML) is an XML-based standard established by the Data Mining Group (DMG) for defining statistical and data-mining models. PMML models can be shared between PMML-compliant platforms and across organizations so that business analysts and developers are unified in designing, analyzing, and implementing PMML-based assets and services. For more information about the background and applications of PMML, see the DMG PMML specification . 10.1. PMML conformance levels The PMML specification defines producer and consumer conformance levels in a software implementation to ensure that PMML models are created and integrated reliably. For the formal definitions of each conformance level, see the DMG PMML conformance page. The following list summarizes the PMML conformance levels: Producer conformance A tool or application is producer conforming if it generates valid PMML documents for at least one type of model. Satisfying PMML producer conformance requirements ensures that a model definition document is syntactically correct and defines a model instance that is consistent with semantic criteria that are defined in model specifications. Consumer conformance An application is consumer conforming if it accepts valid PMML documents for at least one type of model. Satisfying consumer conformance requirements ensures that a PMML model created according to producer conformance can be integrated and used as defined. For example, if an application is consumer conforming for Regression model types, then valid PMML documents defining models of this type produced by different conforming producers would be interchangeable in the application. Red Hat Process Automation Manager includes consumer conformance support for the following PMML model types: Regression models Scorecard models Tree models Mining models (with sub-types modelChain , selectAll , and selectFirst ) Clustering models For a list of all PMML model types, including those not supported in Red Hat Process Automation Manager, see the DMG PMML specification .

Commands:
20.5.2. Port Forwarding SSH can secure otherwise insecure TCP/IP protocols via port forwarding. When using this technique, the SSH server becomes an encrypted conduit to the SSH client. Port forwarding works by mapping a local port on the client to a remote port on the server. SSH can map any port from the server to any port on the client; port numbers do not need to match for this technique to work. To create a TCP/IP port forwarding channel which listens for connections on the localhost, use the following command: Note Setting up port forwarding to listen on ports below 1024 requires root level access. To check email on a server called mail.example.com using POP3 through an encrypted connection, use the following command: Once the port forwarding channel is in place between the client machine and the mail server, direct a POP3 mail client to use port 1100 on the localhost to check for new mail. Any requests sent to port 1100 on the client system are directed securely to the mail.example.com server. If mail.example.com is not running an SSH server, but another machine on the same network is, SSH can still be used to secure part of the connection. However, a slightly different command is necessary: In this example, POP3 requests from port 1100 on the client machine are forwarded through the SSH connection on port 22 to the SSH server, other.example.com . Then, other.example.com connects to port 110 on mail.example.com to check for new mail. Note, when using this technique only the connection between the client system and other.example.com SSH server is secure. Port forwarding can also be used to get information securely through network firewalls. If the firewall is configured to allow SSH traffic via its standard port (22) but blocks access to other ports, a connection between two hosts using the blocked ports is still possible by redirecting their communication over an established SSH connection. Note Using port forwarding to forward connections in this manner allows any user on the client system to connect to that service. If the client system becomes compromised, the attacker also has access to forwarded services. System administrators concerned about port forwarding can disable this functionality on the server by specifying a No parameter for the AllowTcpForwarding line in /etc/ssh/sshd_config and restarting the sshd service.

Commands:
ssh -L local-port : remote-hostname : remote-port username @ hostname
ssh -L 1100:mail.example.com:110 mail.example.com
ssh -L 1100:mail.example.com:110 other.example.com
Chapter 2. Configuring SSO for Argo CD using Dex After the Red Hat OpenShift GitOps Operator is installed, Argo CD automatically creates a user with admin permissions. To manage multiple users, cluster administrators can use Argo CD to configure Single Sign-On (SSO). Note The spec.dex parameter in the ArgoCD CR is no longer supported from Red Hat OpenShift GitOps v1.10.0 onwards. Consider using the .spec.sso parameter instead. 2.1. Configuration to enable the Dex OpenShift OAuth Connector Dex is installed by default for all the Argo CD instances created by the Operator. You can configure Red Hat OpenShift GitOps to use Dex as the SSO authentication provider by setting the .spec.sso parameter. Dex uses the users and groups defined within OpenShift Container Platform by checking the OAuth server provided by the platform. Procedure To enable Dex, set the .spec.sso.provider parameter to dex in the YAML resource of the Operator: # ... spec: sso: provider: dex dex: openShiftOAuth: true 1 # ... 1 The openShiftOAuth property triggers the Operator to automatically configure the built-in OpenShift Container Platform OAuth server when the value is set to true . 2.1.1. Mapping users to specific roles Argo CD cannot map users to specific roles if they have a direct ClusterRoleBinding role. You can manually change the role as role:admin on SSO through OpenShift. Procedure Create a group named cluster-admins . USD oc adm groups new cluster-admins Add the user to the group. USD oc adm groups add-users cluster-admins USER Apply the cluster-admin ClusterRole to the group: USD oc adm policy add-cluster-role-to-group cluster-admin cluster-admins 2.2. Disabling Dex by replacing .spec.sso To disable dex, either remove the spec.sso element from the Argo CD custom resource or specify a different SSO provider.

Commands:
spec: sso: provider: dex dex: openShiftOAuth: true 1
oc adm groups new cluster-admins
oc adm groups add-users cluster-admins USER
oc adm policy add-cluster-role-to-group cluster-admin cluster-admins
Chapter 2. Content Management Types Overview With Red Hat Satellite, you can manage the following content types: RPM Packages Import RPM packages from repositories related to your Red Hat subscriptions. Satellite Server downloads the RPM files from Red Hat's Content Delivery Network and stores them locally. You can use these repositories and their RPM files in Content Views. Kickstart Trees Import the kickstart trees for creating a system. New systems access these kickstart trees over a network to use as base content for their installation. Red Hat Satellite also contains some predefined kickstart templates as well as the ability to create your own, which are used to provision systems and customize the installation. You can also manage other types of custom content in Satellite. For example: ISO and KVM Images Download and manage media for installation and provisioning. For example, Satellite downloads, stores, and manages ISO images and guest images for specific Red Hat Enterprise Linux and non-Red Hat operating systems. You can use the procedure to add custom content for any type of content you require, for example, SSL certificates and OVAL files.

Commands:
1.5.2. Firewall Marks Firewall marks are an easy and efficient way to a group ports used for a protocol or group of related protocols. For instance, if LVS is deployed to run an e-commerce site, firewall marks can be used to bundle HTTP connections on port 80 and secure, HTTPS connections on port 443. By assigning the same firewall mark to the virtual server for each protocol, state information for the transaction can be preserved because the LVS router forwards all requests to the same real server after a connection is opened. Because of its efficiency and ease-of-use, administrators of LVS should use firewall marks instead of persistence whenever possible for grouping connections. However, administrators should still add persistence to the virtual servers in conjunction with firewall marks to ensure the clients are reconnected to the same server for an adequate period of time.

Commands:
7.189. sblim-sfcb 7.189.1. RHBA-2015:1432 - sblim-sfcb bug fix update Updated sblim-sfcb packages that fix several bugs are now available for Red Hat Enterprise Linux 6. Small Footprint CIM Broker (sblim-sfcb) is a Common Information Model (CIM) server conforming to the CIM Operations over the HTTP protocol. The SFCB CIM server is robust and resource-efficient, and is therefore particularly-suited for embedded and resource-constrained environments. The sblim-sfcb package supports providers written against the Common Manageability Programming Interface (CMPI). Bug Fixes BZ# 1102477 Due to incorrect buffer handling in the sblim-sfcb server, the wbemcli CIM client returned an error message when trying to connect to sblim-sfcb over the HTTPS protocol. A patch has been provided to fix this bug, and sblim-sfcb is now reachable over HTTPS without any errors. BZ# 1110106 When a sblim-sfcb server was used in combination with Openwsman and the openwsmand service connected locally to the sblim-sfcb server, a defunct process was left behind. As a consequence, a new process could not be created by the system. With this update, Openwsman defunct processes no longer occur after terminating the connection to the sblim-sfcb server. BZ# 1114798 Due to a memory leak in the sblim-sfcb server, the amount of memory consumed by the sfcbd service process was increased. The underlying source code has been modified to fix this bug, and the sfcbd service process no longer causes an unwanted memory consumption increase. Users of sblim-sfcb are advised to upgrade to these updated packages, which fix these bugs.

Commands:
4.19. RHEA-2012:0853 - new packages: usbredir New usbredir packages are now available for Red Hat Enterprise Linux 6. The usbredir packages provide a protocol for redirection of USB traffic from a single USB device to a different virtual machine then the one to which the USB device is attached. The usbredir package contains a number of libraries to help implement support for usbredir. This enhancement update adds the usbredir package to Red Hat Enterprise Linux 6. (BZ# 758098 ) Users who wish to use the new USB redirection for Spice are advised to install these new packages.

Commands:
Chapter 3. The Project Tab The Project tab provides an interface for viewing and managing the resources of a project. Set a project as active in Identity > Projects to view and manage resources in that project. The following options are available in the Project tab: Table 3.1. The Compute Tab Parameter Name Description Overview View reports for the project. Instances View, launch, create a snapshot from, stop, pause, or reboot instances, or connect to them through the console. Volumes Use the following tabs to complete these tasks: Volumes - View, create, edit, and delete volumes. Volume Snapshots - View, create, edit, and delete volume snapshots. Images View images, instance snapshots, and volume snapshots created by project users, and any images that are publicly available. Create, edit, and delete images, and launch instances from images and snapshots. Access & Security Use the following tabs to complete these tasks: Security Groups - View, create, edit, and delete security groups and security group rules. Key Pairs - View, create, edit, import, and delete key pairs. Floating IPs - Allocate an IP address to or release it from a project. API Access - View API endpoints, download the OpenStack RC file, download EC2 credentials, and view credentials for the logged-in project user. Table 3.2. The Network Tab Parameter Name Description Network Topology View the interactive topology of the network. Networks Create and manage public and private networks and subnets. Routers Create and manage routers. Trunks Create and manage trunks. Requires the trunk extension enabled in OpenStack Networking (neutron). Table 3.3. The Object Store Tab Parameter Name Description Containers Create and manage storage containers. A container is a storage compartment for data, and provides a way for you to organize your data. It is similar to the concept of a Linux file directory, but it cannot be nested. Table 3.4. The Orchestration Tab Parameter Name Description Stacks Orchestrate multiple composite cloud applications using templates, through both an OpenStack-native REST API and a CloudFormation-compatible Query API.

Commands:
Part II. Managing projects in Business Central As a process administrator, you can use Business Central in Red Hat Decision Manager to manage new, sample, and imported projects on a single or multiple branches. Prerequisites Red Hat JBoss Enterprise Application Platform 7.4 is installed. For details, see the Red Hat JBoss Enterprise Application Platform 7.4 Installation Guide . Red Hat Process Automation Manager is installed and configured with KIE Server. For more information, see Installing and configuring Red Hat Decision Manager on Red Hat JBoss EAP 7.4 . Red Hat Decision Manager is running and you can log in to Business Central with the developer role. For more information, see Planning a Red Hat Decision Manager installation .

Commands:
9.2. XML Representation of a Data Center Example 9.1. An XML representation of a data center

Commands:
<data_center href="/ovirt-engine/api/datacenters/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"> <name>Default</name> <description>The default Data Center</description> <link href="/ovirt-engine/api/datacenters/00000000-0000-0000-0000-000000000000/storagedomains" rel="storagedomains"/> <link href="/ovirt-engine/api/datacenters/00000000-0000-0000-0000-000000000000/clusters" rel="clusters"/> <link href="/ovirt-engine/api/datacenters/00000000-0000-0000-0000-000000000000/networks" rel="networks"/> <link href="/ovirt-engine/api/datacenters/00000000-0000-0000-0000-000000000000/permissions" rel="permissions"/> <link href="/ovirt-engine/api/datacenters/00000000-0000-0000-0000-000000000000/quotas" rel="quotas"/> <local>false</local> <storage_format>v3</storage_format> <version major="4" minor="0"/> <supported_versions> <version major="4" minor="0"/> </supported_versions> <status> <state>up</state> </status> <mac_pool href="/ovirt-engine/api/macpools/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"/> </data_center>
32.2. How Do You Perform a Kickstart Installation? Kickstart installations can be performed using a local DVD, a local hard drive, or via NFS, FTP, HTTP, or HTTPS. To use kickstart, you must: Create a kickstart file. Create a boot media with the kickstart file or make the kickstart file available on the network. Make the installation tree available. Start the kickstart installation. This chapter explains these steps in detail.

Commands: