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: documentation/2.0/content/_index.md
+16-13Lines changed: 16 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,9 @@
1
+
---
2
+
weight: 1
3
+
pre: "<b> </b>"
4
+
hideHeader: true
5
+
---
6
+
1
7
## WebLogic Kubernetes Toolkit UI Documentation
2
8
3
9
The WebLogic Kubernetes Toolkit (WKT) is a collection of open source tools that help you provision WebLogic-based
@@ -9,15 +15,14 @@ applications to run in Linux containers on a Kubernetes cluster. WKT includes t
9
15
images for running WebLogic domains.
10
16
-[WebLogic Kubernetes Operator (WKO)](https://github.com/oracle/weblogic-kubernetes-operator) - A Kubernetes operator
11
17
that allows WebLogic domains to run natively in a Kubernetes cluster.
12
-
-[WebLogic Remote Console](https://github.com/oracle/weblogic-remote-console) - A lightweight console for managing
13
-
WebLogic Server domains running anywhere.
14
18
15
-
The WKT UI provides a graphical user interface that wraps the WKT tools, Docker, Helm, and the Kubernetes client
19
+
The WKT User Interface (WKT UI) provides a graphical user interface that wraps the WKT tools, Docker, Helm, and the Kubernetes client
16
20
(`kubectl`) and helps guide you through the process of creating and modifying a model of your WebLogic domain, creating
17
21
a Linux container image to use to run the domain, and setting up and deploying the software and configuration
18
22
necessary to deploy and access the domain in your Kubernetes cluster.
19
23
20
-
Be sure to check out the [Quick Start]({{< relref "/setup/quickstart/" >}}) guide for a tutorial, which will step you through WebLogic Kubernetes Toolkit UI (WKTUI) functionality and familiarize you with its capabilities.
24
+
Be sure to check out the [Quick Start]({{% relref "/setup/quickstart/" %}}) guide for a tutorial, which will step you
25
+
through WKT UI functionality and familiarize you with its capabilities.
21
26
22
27
### Current release
23
28
@@ -26,15 +31,14 @@ WebLogic Kubernetes Toolkit UI version and release information can be found [her
26
31
### About the Documentation
27
32
For detailed user information, read the following:
28
33
29
-
-[About the WKT UI Application]({{< relref "/concepts/" >}})
Settings are also used to store internally used values that impact the appearance of the application. For example, the
94
-
Window size is stored so that the application will open the window with your last known window size. The list of
101
+
window size is stored so that the application will open the window with your last known window size. The list of
95
102
such appearance-related settings will likely grow over time.
96
103
97
104
##### Proxy Configuration
@@ -101,18 +108,38 @@ must configure the proxy server settings to allow Internet access. Currently, t
101
108
`github.com` to access release information and download new releases of the WKT tools and the UI itself. This connectivity
102
109
is used in various places to determine default values for input data (for example, the default image tag to use for installing the
103
110
WebLogic Kubernetes Operator) and providing updated features for the WKT tools bundled with the application, as
104
-
well as updating the WKT UI application itself when a new release becomes available. Depending on the project configuration,
105
-
the application may also require access to other sites, such as Docker Hub and other container registries, Helm chart
111
+
well as updating the WKT UI application itself when a new release becomes available.
112
+
113
+
Depending on the project configuration,
114
+
the application may also require access to other sites, such as Docker Hub (or other container registries), Helm chart
106
115
download sites, and cloud-provider sites for authenticating to and accessing remote Kubernetes clusters.
107
116
108
-
To configure the proxy environment, use the `Preferences` menu to add or update the
117
+
To configure the proxy environment, use the `File` > `Preferences` menu to add or update the
109
118
following fields, as needed:
110
119
111
120
-`HTTPS Proxy URL` - The full URL to the proxy server (for example, http://my-proxy-server.mycompany.com:80).
112
-
-`Bypass Proxy Hosts` - The comma-separated list of DNS or IP patterns that should not go through the proxy.
121
+
-`Bypass Proxy Hosts` - A comma-separated list of DNS or IP patterns that should not go through the proxy.
113
122
For example, a value of `.us.mycompany.com,.emea.mycompany.com,.apac.mycompany.com` will skip the proxy for any
114
123
DNS name that ends in one of the three domain names.
115
124
125
+
##### GitHub API Credentials
126
+
127
+
GitHub rate limits anonymous API requests, which can negatively impact WKT UI functionality. You can bypass the anonymous API rate limits by creating a personal access token on your GitHub account and then providing the token value in the `GitHub Token` field. WKT UI will
128
+
use this token for all API calls. Note that this token does not require
129
+
any permissions on your own projects, it is simply attached to the API requests so that GitHub knows who is making them.
130
+
131
+
##### Linux Disable Hardware Acceleration
132
+
133
+
This section is only visible when running WKT UI on Linux. The `Disable Hardware Acceleration` switch allows you to
134
+
tell Electron's embedded Chromium browser to disable hardware acceleration, in case hardware acceleration is causing
135
+
problems.
136
+
137
+
##### AppImage WKT Tools Configuration
138
+
139
+
This section is only visible when running the Linux AppImage executable. Since WKT UI cannot update the executable,
140
+
the `WKT Tools External Staging Directory` allows you to specify a location where updated versions of the embedded WKT
141
+
tools should be stored. This directory must be writable by the user running WKT UI.
142
+
116
143
##### Logging Configuration
117
144
118
145
Using this section, you can configure the logging output level and control the log file directory. The defaults are:
@@ -122,6 +149,14 @@ Using this section, you can configure the logging output level and control the l
122
149
-`Log File Directory` - The directory to which log files are written. The default is the user's temporary directory, as
123
150
defined by the operating system.
124
151
152
+
##### Startup Internet Connectivity Test Configuration
153
+
154
+
WKT UI depends on Internet access for its functionality and, as such, tests connectivity to `https://github.com` on
155
+
startup. The `Request Timeout Seconds` default value of 5 seconds should generally be enough but you can increase or
156
+
decrease the value using this parameter. Oracle recommends that you not decrease this value below 5 seconds, since that
157
+
may increase the number of false positive error screens that you see when starting the application and the Internet
Copy file name to clipboardExpand all lines: documentation/2.0/content/developer/_index.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,8 @@
1
-
+++
2
-
title = "Developer Guide"
3
-
date = 2019-02-22T15:27:38-05:00
4
-
weight = 4
5
-
pre = "<b> </b>"
6
-
+++
1
+
---
2
+
title: "Developer Guide"
3
+
weight: 4
4
+
pre: "<b> </b>"
5
+
---
7
6
8
7
The WebLogic Kubernetes Toolkit UI is a desktop application designed to help WebLogic users move their applications to run in a Kubernetes environment.
9
8
@@ -31,7 +30,8 @@ The WebLogic Kubernetes Toolkit UI is a desktop application designed to help Web
31
30
is, by default, case-insensitive!**
32
31
33
32
5. Clone the git repository on GitHub at [https://github.com/oracle/weblogic-toolkit-ui](https://github.com/oracle/weblogic-toolkit-ui).
34
-
6. Open a command line in the `weblogic-toolkit-ui` directory and run `npm install` to download and install the JavaScript dependencies required by the project.
33
+
6. Open a command line in the `weblogic-toolkit-ui` directory and run `npm install` to download and install the
34
+
JavaScript dependencies required by the project.
35
35
7. Open a command line in the `weblogic-toolkit-ui/electron` directory and run `npm run install-tools`.
36
36
8. Open a command line in the `weblogic-toolkit-ui/webui` directory and run `npm start`.
37
37
9. After the server from the previous step is fully running, open a command line in the `weblogic-toolkit-ui/electron` directory and run `npm start`.
0 commit comments