You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/topics/about-cli-guide.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,4 +6,4 @@
6
6
[id="about-cli-guide_{context}"]
7
7
= About the {UserCLIBookName}
8
8
9
-
This guide is for engineers, consultants, and others who want to use the {ProductName} ({ProductShortName}) to migrate Java applicationsor other components. It describes how to install and run the {CLIName}, review the generated reports, and take advantage of additional features.
9
+
This guide is for engineers, consultants, and others who want to use the {ProductName} ({ProductShortName}) to migrate Java applications, .NET applications, or other components. In {ProductShortName} 7.1 and later, you can use {ProductShortName} to analyze applications written in languages other than Java. To run analysis on applications written in languages other than Java, add a custom rule set and do not specify a target language. This guide describes how to install and run the {CLIName}, review the generated reports, and take advantage of additional features.
// DO NOT USE THIS SNIPPET. DEVELOPER PREVIEW FEATURES ARE NOT DOCUMENTED IN CORE OPENSHIFT DOCS.
2
+
3
+
// When including this file, ensure that {FeatureName} is set immediately before the include. Otherwise it will result in an incorrect replacement.
4
+
5
+
[IMPORTANT]
6
+
====
7
+
[subs="attributes+"]
8
+
{FeatureName} is a Developer Preview feature only. Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features provide early access to upcoming product features in advance of their possible inclusion in a Red Hat product offering, enabling customers to test functionality and provide feedback during the development process. These features might not have any documentation, are subject to change or removal at any time, and testing is limited. Red Hat might provide ways to submit feedback on Developer Preview features without an associated SLA.
9
+
====
10
+
// Undefine {FeatureName} attribute, so that any mistakes are easily spotted
You can install the {CLINameTitle} on Linux, Windows, or macOS operating systems.
11
-
10
+
You can install the {CLINameTitle} on Linux, Windows, or macOS operating systems using the downloadable `.zip` file.
12
11
13
12
.Prerequisites
14
13
15
-
* Red Hat Container Registry Authentication for `registry.redhat.io`. Red Hat distributes container images from registry.redhat.io, which requires authentication. For more details, see link:https://access.redhat.com/RegistryAuthentication[Red Hat Container Registry Authentication].
16
-
* Podman must be installed
17
-
18
-
+
19
-
[NOTE]
20
-
.Podman
21
-
====
22
-
Podman is a daemonless, open source, Linux-native tool designed to make it easy to find, run, build, share, and deploy applications using Open Containers Initiative (OCI) Containers and Container Images.
23
-
Podman provides a command-line interface (CLI) familiar to anyone who has used the Docker Container Engine.
24
-
For more information on installing and using Podman, see link:https://podman.io/docs/installation[Podman installation instructions].
25
-
====
14
+
* Red Hat Container Registry Authentication for `registry.redhat.io`. Red Hat distributes container images from `registry.redhat.io`, which requires authentication. For more details, see link:https://access.redhat.com/RegistryAuthentication[Red Hat Container Registry Authentication].
26
15
27
16
[id="installing-downloadable-cli-zip_{context}"]
28
17
== Installing the {CLINameTitle} `.zip` file
29
18
30
19
.Procedure
31
20
32
-
To install using the downloadable `.zip` file:
33
-
34
21
. Navigate to the link:{DevDownloadPageURL}[{ProductShortName} Download page] and download the OS-specific CLI file or the `src` file:
@@ -46,35 +33,164 @@ When you encounter `<{ProductShortName}_HOME>` in this guide, replace it with th
46
33
[id="installing-using-podman_{context}"]
47
34
== Installing the {CLINameTitle} using Podman
48
35
36
+
You can install the {CLINameTitle} using `podman pull`.
37
+
49
38
.Prerequisites
50
39
51
-
* Red Hat Container Registry Authentication for `registry.redhat.io`. Red Hat distributes container images from registry.redhat.io, which requires authentication. For more details, see link:https://access.redhat.com/RegistryAuthentication[Red Hat Container Registry Authentication].
40
+
* Red Hat Container Registry Authentication for `registry.redhat.io`. Red Hat distributes container images from `registry.redhat.io`, which requires authentication. See link:https://access.redhat.com/RegistryAuthentication[Red Hat Container Registry Authentication] for additional details.
52
41
42
+
* Podman must be installed.
53
43
54
-
.Procedure
44
+
[NOTE]
45
+
.Podman
46
+
====
47
+
Podman is a daemonless, open source, Linux-native tool designed to make it easy to find, run, build, share, and deploy applications using Open Containers Initiative (OCI) Containers and Container Images.
48
+
Podman provides a command-line interface (CLI) familiar to anyone who has used the Docker Container Engine.
49
+
For more information on installing and using Podman, see link:https://podman.io/docs/installation[Podman installation instructions].
50
+
====
55
51
56
-
To install using `podman pull`:
52
+
.Procedure
57
53
58
-
. To use Podman to authenticate to registry.redhat.io:
54
+
. Use Podman to authenticate to `registry.redhat.io` by running the following command:
55
+
+
56
+
[source,terminal]
57
+
----
58
+
$ podman login registry.redhat.io
59
+
----
60
+
+
61
+
Enter the user name and password:
59
62
+
60
63
[source,terminal]
61
64
----
62
-
podman login registry.redhat.io
63
65
Username: <username>
64
66
Password: <***********>
65
67
----
66
-
. Issue:
68
+
69
+
. Copy the binary `PATH` to enable system-wide use by running the following command:
This command will copy the binary `PATH` for system-wide use.
74
-
+
75
76
[WARNING]
76
77
====
77
78
Although installation using Podman is possible, downloading and installing the `.zip` file is the preferred installation.
78
79
====
79
80
81
+
[id="installing-using-docker_{context}"]
82
+
== Installing the {CLINameTitle} for use with Docker on Windows (Developer Preview)
83
+
84
+
You can install the {CLINameTitle} for use with Docker on Windows. This is the required approach when migrating applications built with .NET framework 4.5 or later on Windows to cross-platform .NET 8.0.
85
+
86
+
.Prerequisites
87
+
88
+
* A host with Windows 11+ 64-bit version 21H2 or higher.
89
+
90
+
* You have download the Docker Desktop for Windows installer. See link:https://docs.docker.com/desktop/install/windows-install/[Install Docker Desktop on Windows] for additional details.
91
+
92
+
.Procedure
93
+
94
+
. Open a PowerShell with Administrator privileges.
.. Double-click `Docker_Desktop_Installer.exe` to run the installer. By default, Docker Desktop is installed at `C:\Program Files\Docker\Docker`.
118
+
119
+
.. Deselect the *Use WSL 2 instead of Hyper-V* option on the Configuration page to ensure that Docker will run Windows containers as the backend instead of Linux containers.
80
120
121
+
. In PowerShell, create a folder for {ProductShortName}:
Copy file name to clipboardExpand all lines: docs/topics/migration-paths.adoc
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,11 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
11
11
* Migrating from third-party enterprise application servers, such as Oracle WebLogic Server, to JBoss Enterprise Application Platform (JBoss EAP).
12
12
* Upgrading to the latest release of JBoss EAP.
13
13
14
+
* Migrating from a Windows-only .NET 4.5+ Framework to cross-platform .NET 8.0. (Developer Preview)
15
+
14
16
{ProductShortName} provides a comprehensive set of rules to assess the suitability of your applications for containerization and deployment on Red Hat OpenShift Container Platform (RHOCP). You can run an {ProductShortName} analysis to assess your applications' suitability for migration to multiple target platforms.
@@ -49,7 +51,8 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
49
51
50
52
|JBoss EAP 4
51
53
|{icon-x}footnoteref:[note2,Although {ProductShortName} does not currently provide rules for this migration path, Red Hat Consulting can assist with migration from any source platform to JBoss EAP 7.]
52
-
|{icon-check} |{icon-check}
54
+
|{icon-check}
55
+
|{icon-check}
53
56
|-
54
57
|-
55
58
|-
@@ -146,3 +149,16 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
. Copy your application to the {ProductShortName} directory. The following command clones the link:https://github.com/sixeyed/nerd-dinner[Nerd Dinner] application as an example application:
. Analyze the application. The following command analyzes the link:https://github.com/sixeyed/nerd-dinner[Nerd Dinner] application for migrating from Windows .NET 4.5 or later to cross-platform .NET 8:
0 commit comments