mtpti5iD/redhat-docs_dataset huggingface dataset:
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 Web Console This guide is for engineers, consultants, and others who want to use the Migration Toolkit for Runtimes (MTR) to migrate or modernize Java applications or other components. It describes how to install and use the web console to manage migration or modernization projects and analyze applications. 1.2. About the Migration Toolkit for Runtimes What is the Migration Toolkit for Runtimes? The Migration Toolkit for Runtimes (MTR) is an extensible and customizable rule-based tool that simplifies the migration and modernization of Java applications. MTR examines application artifacts, including project source directories and application archives, and then produces an HTML report highlighting areas needing changes. MTR supports many migration paths, including the following examples: Upgrading to the latest release of Red Hat JBoss Enterprise Application Platform Migrating from Oracle WebLogic or IBM WebSphere Application Server to Red Hat JBoss Enterprise Application Platform Containerizing applications and making them cloud-ready Migrating from Java Spring Boot to Quarkus Updating from Oracle JDK to OpenJDK Upgrading from OpenJDK 8 to OpenJDK 11 Upgrading from OpenJDK 11 to OpenJDK 17 Upgrading from OpenJDK 17 to OpenJDK 21 Migrating EAP Java applications to Azure Migrating Spring Boot Java applications to Azure For more information about use cases and migration paths, see the MTR for developers web page. How does the Migration Toolkit for Runtimes simplify migration? The Migration Toolkit for Runtimes looks for common resources and known trouble spots when migrating applications. It provides a high-level view of the technologies used by the application. MTR generates a detailed report evaluating a migration or modernization path. This report can help you to estimate the effort required for large-scale projects and to reduce the work involved. How do I learn more? See the Introduction to the Migration Toolkit for Runtimes to learn more about the features, supported configurations, system requirements, and available tools in the Migration Toolkit for Runtimes. 1.3. The MTR web console By using the web console for the Migration Toolkit for Runtimes, a team of users can assess and prioritize migration and modernization efforts for a large number of applications. You can use the web console to group applications into projects for analysis and provide numerous reports that highlight the results.

Commands:
Chapter 8. Developer Previews Developer preview features included with Streams for Apache Kafka 2.9. As a Kafka cluster administrator, you can toggle a subset of features on and off using feature gates in the Cluster Operator deployment configuration. The feature gates available as developer previews are at an alpha level of maturity and disabled by default. Important Developer Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete; therefore, Red Hat does not recommend implementing any Developer Preview features in production environments. This Developer Preview feature provides early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. For more information about the support scope, see Developer Preview Support Scope . 8.1. Tiered storage for Kafka brokers Streams for Apache Kafka now supports tiered storage for Kafka brokers as a developer preview, allowing you to introduce custom remote storage solutions as well as local storage. Due to its current limitations , it is not recommended for production environments. Remote storage configuration is specified using kafka.tieredStorage properties in the Kafka resource. You specify a custom remote storage manager to manage the tiered storage. Example custom tiered storage configuration kafka: tieredStorage: type: custom remoteStorageManager: className: com.example.kafka.tiered.storage.s3.S3RemoteStorageManager classPath: /opt/kafka/plugins/tiered-storage-s3/* config: # remote storage manager configuration 1 storage.bucket.name: my-bucket config: ... rlmm.config.remote.log.metadata.topic.replication.factor: 1 2 1 Configure the custom remote storage manager with the necessary settings. The keys are automatically prefixed with rsm.config and appended to the Kafka broker configuration. 2 Streams for Apache Kafka uses the TopicBasedRemoteLogMetadataManager for Remote Log Metadata Management (RLMM). Add RLMM configuration using an rlmm.config. prefix. Note If you want to use custom tiered storage, you must first add the tiered storage plugin to the Streams for Apache Kafka image by building a custom container image. See Tiered storage (early access) .

Commands:
kafka: tieredStorage: type: custom remoteStorageManager: className: com.example.kafka.tiered.storage.s3.S3RemoteStorageManager classPath: /opt/kafka/plugins/tiered-storage-s3/* config: # remote storage manager configuration 1 storage.bucket.name: my-bucket config: rlmm.config.remote.log.metadata.topic.replication.factor: 1 2
15.2. Using RPM RPM has five basic modes of operation (not counting package building): installing, uninstalling, upgrading, querying, and verifying. This section contains an overview of each mode. For complete details and options, try rpm --help or refer to Section 15.5, "Additional Resources" for more information on RPM. 15.2.1. Finding RPM Packages Before using an RPM, you must know where to find them. An Internet search returns many RPM repositories, but if you are looking for RPM packages built by Red Hat, Inc, they can be found at the following locations: The Red Hat Enterprise Linux CD-ROMs The Red Hat Errata Page available at http://www.redhat.com/apps/support/errata/ A Red Hat FTP Mirror Site available at http://www.redhat.com/download/mirror.html Red Hat Network - Refer to Chapter 16, Red Hat Network for more details on Red Hat Network

Commands:
4.21. IBM iPDU Table 4.22, "IBM iPDU (Red Hat Enterprise Linux 6.4 and later)" lists the fence device parameters used by fence_ipdu , the fence agent for iPDU over SNMP devices. Table 4.22. IBM iPDU (Red Hat Enterprise Linux 6.4 and later) luci Field cluster.conf Attribute Description Name name A name for the IBM iPDU device connected to the cluster into which the fence daemon logs by means of the SNMP protocol. IP Address or Hostname ipaddr The IP address or host name assigned to the device. UDP/TCP Port udpport The UDP/TCP port to use for connection with the device; the default value is 161. Login login The login name used to access the device. Password passwd The password used to authenticate the connection to the device. Password Script (optional) passwd_script The script that supplies a password for access to the fence device. Using this supersedes the Password parameter. SNMP Version snmp_version The SNMP version to use (1, 2c, 3); the default value is 1. SNMP Community community The SNMP community string; the default value is private . SNMP Security Level snmp_sec_level The SNMP security level (noAuthNoPriv, authNoPriv, authPriv). SNMP Authentication Protocol snmp_auth_prot The SNMP Authentication Protocol (MD5, SHA). SNMP Privacy Protocol snmp_priv_prot The SNMP privacy protocol (DES, AES). SNMP Privacy Protocol Password snmp_priv_passwd The SNMP privacy protocol password. SNMP Privacy Protocol Script snmp_priv_passwd_script The script that supplies a password for SNMP privacy protocol. Using this supersedes the SNMP privacy protocol password parameter. Power Wait (seconds) power_wait Number of seconds to wait after issuing a power off or power on command. Power Timeout (seconds) power_timeout Number of seconds to continue testing for a status change after issuing a power off or power on command. The default value is 20. Shell Timeout (seconds) shell_timeout Number of seconds to wait for a command prompt after issuing a command. The default value is 3. Login Timeout (seconds) login_timeout Number of seconds to wait for a command prompt after login. The default value is 5. Times to Retry Power On Operation retry_on Number of attempts to retry a power on operation. The default value is 1. Port (Outlet) Number port Physical plug number or name of virtual machine. Delay (optional) delay The number of seconds to wait before fencing is started. The default value is 0. Figure 4.16, "IBM iPDU" shows the configuration screen for adding an IBM iPDU fence device. Figure 4.16. IBM iPDU The following command creates a fence device instance for an IBM iPDU device: The following is the cluster.conf entry for the fence_ipdu device:

Commands:
ccs -f cluster.conf --addfencedev ipdutest1 agent=fence_ipdu community=ipdusnmpcom ipaddr=192.168.0.1 login=root passwd=password123 snmp_priv_passwd=snmpasswd123 power_wait=60 snmp_priv_prot=AES udpport=111
<fencedevices> <fencedevice agent="fence_ipdu" community="ipdusnmpcom" ipaddr="ipduhost" login="root" name="ipdutest1" passwd="password123" power_wait="60" snmp_priv_passwd="ipduprivprotpasswd" snmp_priv_prot="AES" udpport="111"/> </fencedevices>
Chapter 11. Log file locations During the deployment process, progress information is displayed in the web browser. This information is also stored on the local file system so that the information logged can be archived or reviewed at a later date, for example, if the web browser stops responding or is closed before the information has been reviewed. The log file for the Web Console based deployment process is stored in the /var/log/cockpit/ovirt-dashboard/gluster-deployment.log file by default. The log files for the Hosted Engine setup portion of the deployment process are stored in the /var/log/ovirt-hosted-engine-setup directory, with file names of the form ovirt-hosted-engine-setup-<date>.log .

Commands:
Chapter 3. File System Structure 3.1. Why Share a Common Structure? The file system structure is the most basic level of organization in an operating system. Almost all of the ways an operating system interacts with its users, applications, and security model are dependent upon the way it organizes files on storage devices. Providing a common file system structure ensures users and programs are able to access and write files. File systems break files down into two logical categories: Shareable vs. unsharable files Variable vs. static files Shareable files are those that can be accessed locally and by remote hosts; unsharable files are only available locally. Variable files, such as documents, can be changed at any time; static files, such as binaries, do not change without an action from the system administrator. The reason for looking at files in this manner is to help correlate the function of the file with the permissions assigned to the directories which hold them. The way in which the operating system and its users interact with a given file determines the directory in which it is placed, whether that directory is mounted with read-only or read/write permissions, and the level of access each user has to that file. The top level of this organization is crucial. Access to the underlying directories can be restricted or security problems could manifest themselves if, from the top level down, it does not adhere to a rigid structure.

Commands:
Chapter 6. Server Management 6.1. Targeting the JBoss Data Virtualization Server 6.1.1. Targeting the JBoss Data Virtualization Server The JBoss Data Virtualization Server is the destination for Teiid Designer's modeling. It is essential to define the correct server version that models will be deployed to. This is achieved either by setting the server version preference or defining the JBoss Data Virtualization Server in the Servers View. 6.1.2. Server Version Preference The default server version preference allows the target server version to be changed without actually having to define a JBoss Data Virtualization Server in Teiid Designer . The preference's list of possible values is determined by which teiid runtime client plugins have been installed into the application. Figure 6.1. Default Server Version Preference 6.1.3. Defining JBoss Data Virtualization Server You can preview and test the deployment of the models by defining a JBoss Data Virtualization Server. There is no limit to the number of servers that can be defined. However, the default server will always be used for previewing and deployment, unless you use the context menu actions in the Server View section. The Guides View provides the following JBoss Data Virtualization Server actions. Configure New JBoss Server Edit JBoss/Teiid Instance Properties Set the Default JBoss/Teiid Instance Refresh Teiid Instance Figure 6.2. Teiid Server Category in the Guides View The Configure New JBoss Server action will display the wizard outlined in the Setting Up a Server section and steps through the process of creating both the JBoss Data Virtualization instance and its parent JBoss server in the Server View. Should more than one JBoss Data Virtualization Server be defined in the Server View then the Set the Default JBoss/Teiid Instance action allows for the default server to be changed appropriately. The JBoss Data Virtualization server that is currently selected in the Server View is considered as the default server. However, should nothing be selected then a dialog will be displayed inviting you to choose the default server. Note The version of the defined JBoss Data Virtualization server always takes precedence over the server version selected in the Preference window. 6.1.4. Server Version Status Panel Whether the server version preference has been modified or a server defined, the server and server target version will be updated in the default server status panel which is located in the Connections view. This will always reflect the current server version being targeted and the server being used to preview or deploy against. Figure 6.3. Default Server Status Panel

Commands:
5.7. Configure CXF for a Salesforce Data Source Prerequisites You must have configured a Salesforce data source. Procedure 5.5. Configure CXF for a Salesforce Data Source Run the following command from within the Management CLI, specifying the CXF configuration file for the data source: Specify the port configuration by running the following command from within the Management CLI, using the port QName (local part only) for the value, in this case Soap : Open/create the EAP_HOME / MODE /configuration/ CONFIG-FILE .xml configuration file. Set the namespace URI for the QName to {urn:partner.soap.sforce.com} , using Soap as the value for EndPointName : The following is an example of a CXF file that configures timeout values: Note CXF configuration for Salesforce data sources is only used for http bus configuration. It is not used for WS-Security. Salesforce has its own security authentication.

Commands:
/subsystem=resource-adapters/resource-adapter=salesforce/connection-definitions=sfDS/config-properties=ConfigFile:add(value= CONFIG-FILE .xml)
/subsystem=resource-adapters/resource-adapter=salesforce/connection-definitions=sfDS/config-properties=EndPointName:add(value=Soap)
<http-conf:conduit name="{urn:partner.soap.sforce.com} Soap .http-conduit"> </http-conf:conduit>
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:http-conf="http://cxf.apache.org/transports/http/configuration" xsi:schemaLocation="http://cxf.apache.org/transports/http/configuration http://cxf.apache.org/schemas/configuration/http-conf.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <http-conf:conduit name="{urn:partner.soap.sforce.com}Soap.http-conduit"> <http-conf:client ConnectionTimeout="120000" ReceiveTimeout="240000"/> </http-conf:conduit> </beans>
Chapter 11. Configuring project settings Starting with Red Hat Process Automation Manager 7.13, Business Central contains additional project setting categories in the new process designer. Prerequisites You have created a Business Central project. Procedure To access the project Settings tab, in Business Central go to Menu Design Projects . Click the project name. Click Settings to view or modify the following project settings: General Settings - Enables users to set the project's Name , Description , Group ID , Artifact ID , Version (GAV), and Development Mode attributes. It also includes the following options: URL - Use to specify a read-only URL for cloning a project as a git repository. Disable GAV conflict check - Determines whether to enable or disable the GAV conflict check. Disabling this feature enables projects to have the same GAV values. Allow child GAV edition - Allows GAV editions for sub-projects. Dependencies - Used to add dependencies either manually, by entering the Group ID , Artifact ID , and Version or from a repository project in Business Central. For each dependency, set select All or None for the Package white list option. KIE Bases - The new name for what was previously called Knowledge bases . You must specify a KIE base as the default. Provide the following details to add a Kie base: Name Included KIE bases Package Equal Behavior - Identity or Equality Event Processing Model - Stream or Cloud KIE sessions External Data Objects - Data objects are not explicitly defined within a project or project dependencies that a rule author may require. External data objects are usually provided by the Java runtime, for example, java.util.List . Validation - Maven repositories that are used to check the uniqueness of a project's GAV when creating a new project or module or when installing or deploying a project to a Maven repository. Service Tasks - The following service tasks can be added to a project: BusinessRuleTask - Execute a business rule task Decision Task - Execute a DMN decision task Email - Send email JMSSendTask - Send JMS Message Rest - Perform a Rest call ServiceTask - Execute a service task WebService - Perform a web service call Deployments - Deployments are divided in to the following categories: General Settings - Runtime Strategy , Persistence Unit Name , Persistence Mode , Audit Persistence Unit Name , and Audit Mode Marshalling strategies Global Event listeners Required roles Remoteable classes Task event listeners Configuration Environment entries Work item handlers Persistence - Persistence is divided in to the following categories: Persistence Unit Persistence Provider Data Source Properties - Used to set values for the following properties and also to create new properties: hibernate.dialect hibernate.max_fetch_depth hibernate.hbm2ddl.auto hibernate.show_sql hibernate.id.new_generator_mappings hibernate.transaction.jta.platform Project Persistable Data Objects Branch Management - Provides branch role access based on the branch name and assigned user roles. Click Save .

Commands:
Chapter 3. Deploying Kafka components using the Streams for Apache Kafka operator When installed on Openshift, the Streams for Apache Kafka operator makes Kafka components available for installation from the user interface. The following Kafka components are available for installation: Kafka Kafka Connect Kafka MirrorMaker Kafka MirrorMaker 2 Kafka Topic Kafka User Kafka Bridge Kafka Connector Kafka Rebalance You select the component and create an instance. As a minimum, you create a Kafka instance. This procedure describes how to create a Kafka instance using the default settings. You can configure the default installation specification before you perform the installation. The process is the same for creating instances of other Kafka components. Prerequisites The Streams for Apache Kafka operator is installed on the OpenShift cluster . Procedure Navigate in the web console to the Operators > Installed Operators page and click Streams for Apache Kafka to display the operator details. From Provided APIs , you can create instances of Kafka components. Click Create instance under Kafka to create a Kafka instance. By default, you'll create a Kafka cluster called my-cluster with three Kafka broker nodes and three ZooKeeper nodes. The cluster uses ephemeral storage. Note If you prefer to create a Kafka cluster in KRaft mode, you can use one of the example KRaft-based deployment files provided with Streams for Apache Kafka. To use deployment files to install Streams for Apache Kafka, download and extract the files from the Streams for Apache Kafka software downloads page . Paste the configuration in the YAML view before starting the installation of the Kafka instance. Click Create to start the installation of Kafka. Wait until the status changes to Ready .

Commands:
4.363. yp-tools 4.363.1. RHEA-2011:1561 - yp-tools enhancement update An enhanced yp-tools package that provides an enhancement is now available for Red Hat Enterprise Linux 6. The Network Information Service (NIS) is a system which provides network information (login names, passwords, home directories, group information) to all of the machines on a network. NIS can enable users to login on any machine on the network as long as the machine has the NIS client programs running and the user's password is recorded in the NIS passwd database. NIS was formerly known as Sun Yellow Pages (YP). Enhancement BZ# 699666 When using the passwd.adjunct file, the ypasswd client program did not recognize the salt used for hashing a new password and therefore chose DES as the default hash function. A new environment variable YP_PASSWD_HASH, which allows users to choose the hash algorithm, was added. Users of yp-tools are advised to upgrade to this updated package, which adds this enhancement.

Commands:
5.104. hwdata 5.104.1. RHEA-2012:0879 - hwdata enhancement update An updated hwdata package that adds two enhancements is now available for Red Hat Enterprise Linux 6. The hwdata package contains tools for accessing and displaying hardware identification and configuration data. Enhancements BZ# 737467 With this update, the monitor database has been updated with information about the Acer 76ie monitor. Also, several duplicate monitor entries have been removed from the database. BZ# 760014 The pci.ids database has been updated with information about the Atheros wireless network adapter, Killer Wireless-N 1103. All users of hwdata are advised to upgrade to this updated package, which adds these enhancements.

Commands:
Chapter 6. Accessing the dashboard After you have installed OpenShift AI and added users, you can access the URL for your OpenShift AI console and share the URL with the users to let them log in and work on their models. Prerequisites You have installed OpenShift AI on your OpenShift cluster. You have added at least one user to the user group for OpenShift AI as described in Adding users to OpenShift AI user groups . Procedure Log in to OpenShift web console. Click the application launcher ( ). Right-click on Red Hat OpenShift AI and copy the URL for your OpenShift AI instance. Provide this instance URL to your data scientists to let them log in to OpenShift AI. Verification Confirm that you and your users can log in to OpenShift AI by using the instance URL. Additional resources Logging in to OpenShift AI Adding users to OpenShift AI user groups .

Commands: