Version 2.0

electron/main.js

@@ -321,6 +321,16 @@ function makeMenu() {
                 }
               }
             )
+            .catch(err => {
+              dialog.showMessageBox(window,
+                {
+                  title: 'Connection Issue',
+                  buttons: ['Ok'],
+                  type: 'info',
+                  message: 'Could not reach update site'
+                }
+              );
+            });
           }
         }
     );

frontend/src/js/core/runtime.js

@@ -25,7 +25,7 @@ define(['ojs/ojlogger', './adapters/file-adapter', './cbe-types', './types', './
     properties['console-backend.providerId'] = "";
     properties['console-backend.domain'] = "";
     properties['console-backend.domainConnectState'] = CoreTypes.Domain.ConnectState.DISCONNECTED.name;
-    properties['console-backend.weblogic.username'] = "weblogic";
+    properties['console-backend.weblogic.username'] = "";
 
     FileAdapter.readYaml('config/console-frontend-jet.yaml')
       .then((data) => {

frontend/src/js/microservices/connection-management/domain-connection-manager.js

@@ -36,7 +36,6 @@ define(['../../core/runtime', '../../apis/data-operations', '../../core/cbe-type
         // properties, when this function is called from the
         // useConnection(dataProvider) function.
         Runtime.setProperty(Runtime.PropertyName.CBE_DOMAIN_URL, data['domainUrl']);
-        Runtime.setProperty(Runtime.PropertyName.CBE_WLS_USERNAME, data['username']);
         // data.state will only be "connected", if this function
         // is called from the useConnection(dataProvider) function.
         if (data.state === CoreTypes.Domain.ConnectState.CONNECTED.name) {

frontend/src/js/viewModels/content-area/dataproviders.js

@@ -1046,6 +1046,7 @@ define(['ojs/ojcore', 'knockout', 'ojs/ojarraydataprovider',  '../../microservic
         // runtime mode (e.g. "connected", "disconnected")
         // the CFE is running in.
         Runtime.setProperty(Runtime.PropertyName.CBE_DOMAIN_CONNECT_STATE, dataProvider.state);
+        Runtime.setProperty(Runtime.PropertyName.CBE_WLS_USERNAME, dataProvider.username);
         // Send signal about domain being changed, if
         // this is an "adminserver" data provider.
         if (dataProvider.type === DataProvider.prototype.Type.ADMINSERVER.name) {

hugo/2.0/content/_index.md

@@ -8,7 +8,7 @@ description: An introduction to the WebLogic Remote Console.
 
 The WebLogic Remote Console is a lightweight, open source console that you can use to manage domain configurations of WebLogic Server Administration Servers or WebLogic Deploy Tooling (WDT) metadata models.
 
-The advantage of the WebLogic Remote Console is that it does not need to be colocated with the WebLogic Server domain. You can install and run the WebLogic Remote Console from one computer and connect to a domain running anywhere: a physical or virtual machine, in a container, Kubernetes, or in the Oracle Cloud. The WebLogic Remote Console connects to your domain using WebLogic REST APIs.
+The advantage of the WebLogic Remote Console is that it does not need to be collocated with the WebLogic Server domain. You can install and run the WebLogic Remote Console from one computer and connect to a domain running anywhere: a physical or virtual machine, in a container, Kubernetes, or in the Oracle Cloud. The WebLogic Remote Console connects to your domain using WebLogic REST APIs.
 
 As for the WDT metadata models, they are descriptions of a WebLogic Server domain configuration, generally written in YAML but occasionally JSON. These models are not connected to a live domain and you edit them 'offline' before using the WebLogic Deploy Tooling (WDT) to build or modify live domains from the models. See the [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) documentation for more information.
 
@@ -49,8 +49,8 @@ Documentation for prior releases of the WebLogic Remote Console: [1.1.0](https:/
 
 #### Need more help? Have a suggestion? Come and say, "Hello!" {id="help"}
 
-We have a **public Slack channel** where you can get in touch with us to ask questions about using the Remote Console or give us feedback or suggestions about what features and improvements you would like to see.  We would love to hear from you. To join our channel, please [visit this site to get an invitation](https://weblogic-slack-inviter.herokuapp.com/). The invitation email will include details of how to access our Slack workspace.  After you are logged in, please come to `#remote-console` and say, "hello!"
+We have a **public Slack channel** where you can get in touch with us to ask questions about using the WebLogic Remote Console or give us feedback or suggestions about what features and improvements you would like to see.  We would love to hear from you. To join our channel, please [visit this site to get an invitation](https://weblogic-slack-inviter.herokuapp.com/). The invitation email will include details of how to access our Slack workspace.  After you are logged in, please come to `#remote-console` and say, "hello!"
 
 #### Related Projects {id="rel_projects"}
 
-* [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/)
+* [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/)

hugo/2.0/content/reference/troubleshoot.md

@@ -8,6 +8,10 @@ weight: 3
 
 This page provides guidelines to help troubleshoot console issues.
 
+## Check log files for errors
+
+The WebLogic Remote Console provides log files for both front and back end processes. For instructions on how to access these log files, see [Check Log Files]({{< relref "userguide/logging" >}}).
+
 ## Diagnose invalid WebLogic configuration issues {id="invalid"}
 
 ### Administration Server

hugo/2.0/content/setup/admin-console-diff.md

@@ -6,10 +6,10 @@ description: An overview of the differences with the Oracle WebLogic Administrat
 weight: 5
 ---
 
-The WebLogic Remote Console is distinct from the WebLogic Server Administration Console that is deployed as part of your WebLogic domain. As you explore the WebLogic Remote Console, you'll notice key differences between the two consoles:
+The WebLogic Remote Console is distinct from the WebLogic Server Administration Console that is deployed as part of your WebLogic Server domain. As you explore the WebLogic Remote Console, you'll notice key differences between the two consoles:
 * The user interface has been completely redesigned to conform to the Oracle Redwood theme included with Oracle JET.
 * The configuration and monitoring runtime content is separated into separate pages in the Remote Console. In the WebLogic Server Administration Console, the configuration and runtime information is presented on one page.
 * The Change Center is now expressed as a shopping cart.
-* Instead of logging directly into the Administration Console deployed in a WebLogic domain, the Remote Console connects to the Administration Server in a WebLogic domain, with the credentials supplied by the user, using WebLogic REST APIs.
+* Instead of logging directly into the Administration Console deployed in a WebLogic Server domain, the Remote Console connects to the Administration Server in a WebLogic Server domain, with the credentials supplied by the user, using WebLogic REST APIs.
 
 For information on the WebLogic Server Administration Console, see the online help for [12.2.1.3](https://docs.oracle.com/middleware/12213/wls/WLACH/index.html), [12.2.1.4](https://docs.oracle.com/en/middleware/fusion-middleware/weblogic-server/12.2.1.4/wlach/index.html), or [14.1.1.0](https://docs-uat.us.oracle.com/en/middleware/standalone/weblogic-server/14.1.1.0/wlach/index.html).

hugo/2.0/content/userguide/advanced-settings.md

@@ -12,12 +12,12 @@ You can customize the default connection settings of the WebLogic Remote Console
 * [Java system properties](#system_prop)
 
 Some possible customizations:
-* [Connect to a WebLogic domain using SSL/TLS ](#ssl)
+* [Connect to a WebLogic Server domain using SSL/TLS ](#ssl)
 * [Specify a listen address for the WebLogic Remote Console host](#listen_address)
 * [Change the network timeout settings for the server ](#network_timeout)
-* [Disable host name verification in the connections to the WebLogic domain ](#hostname)
+* [Disable host name verification in the connections to the WebLogic Server domain ](#hostname)
 * [Set the SameSite cookie attribute if required for web browser support ](#samesite)
-* [Connect to a WebLogic domain running on kubernetes ](#k8s)
+* [Connect to a WebLogic Server domain running on kubernetes ](#k8s)
 
 
 ### Edit Java system properties in the desktop application {id="desktopapp"}
@@ -64,11 +64,11 @@ java -Dserver.host=0.0.0.0 -jar <console_home>/console.jar
 |javax.net.ssl.trustStore |`<java-home>/lib/security/jssecacerts` or `<java-home>/lib/security/cacerts` | javax.net.ssl.trustStore | -Djavax.net.ssl.trustStore |
 |javax.net.ssl.trustStoreType | jks | javax.net.ssl.trustStoreType | -Djavax.net.ssl.trustStoreType |
 
-## Connect to a WebLogic domain using SSL/TLS {id="ssl"}
+## Connect to a WebLogic Server domain using SSL/TLS {id="ssl"}
 
-If you specify HTTPS for the domain URL in the Connect to WebLogic Domain window, then the WebLogic Remote Console uses SSL/TLS to communicate with the WebLogic domain.
+If you specify HTTPS for the domain URL in the Connect to WebLogic Domain window, then the WebLogic Remote Console uses SSL/TLS to communicate with the WebLogic Server domain.
 
-The SSL/TLS connection requires trust in the WebLogic domain, where the trust configuration is handled by the underlying JDK JSSE support. By default, the JDK uses the `cacerts` truststore provided with the JDK. If the WebLogic domain requires additional trust, separate trust, or is using the WebLogic demo trust (`demotrust.jks`), then you can use the JDK system properties when starting the Remote Console.
+The SSL/TLS connection requires trust in the WebLogic Server domain, where the trust configuration is handled by the underlying JDK JSSE support. By default, the JDK uses the `cacerts` truststore provided with the JDK. If the WebLogic Server domain requires additional trust, separate trust, or is using the WebLogic demo trust (`demotrust.jks`), then you can use the JDK system properties when starting the Remote Console.
 
 You can configure SSL/TLS trust with the JDK using one of these options:
 - Import the required trust certificates into the `cacerts` truststore supplied with the JDK using the [`keytool`](https://docs.oracle.com/en/java/javase/11/tools/keytool.html) command.
@@ -130,7 +130,7 @@ To specify a listen address when running `console.zip`:
 
 1. In the Connect to WebLogic Domain window, enter the Administrator user name, password, and the URL of the domain.
 
-      When the Remote Console is not running on the same computer as the browser, the WebLogic domain URL must be accessible to the computer running the Remote Console process.
+      When the Remote Console is not running on the same computer as the browser, the WebLogic Server domain URL must be accessible to the computer running the Remote Console process.
 
 ### Desktop application
 
@@ -162,19 +162,19 @@ When you connect to a Remote Console process running on a different computer, yo
 
 1. In the Connect to WebLogic Domain window, enter the Administrator user name, password, and the URL of the domain.
 
-      When the Remote Console is not running on the same computer as the browser, the WebLogic domain URL must be accessible to the computer running the Remote Console process.
+      When the Remote Console is not running on the same computer as the browser, the WebLogic Server domain URL must be accessible to the computer running the Remote Console process.
 
 ## Change the network timeout settings for the server {id="network_timeout"}
 
-To change the defaults for the connection and read timeout settings used with a WebLogic domain from the Remote Console, change the following Java system properties:
+To change the defaults for the connection and read timeout settings used with a WebLogic Server domain from the Remote Console, change the following Java system properties:
 - Set `console.readTimeoutMillis=<millis>` for the timeout when waiting on a response, _Default:_ `20 seconds`
 - Set `console.connectTimeoutMillis=<millis>` for the timeout when waiting to connect, _Default:_ `10 seconds`
 
 For example:
 ```
 java -Dconsole.readTimeoutMillis=60000 -Dconsole.connectTimeoutMillis=30000 -jar <console_home>/console.jar
 ```
-In this example, <console_home> represents the directory where you unzipped the installer, and will result in the console waiting `60 seconds` before giving up on a response from the WebLogic domain.
+In this example, <console_home> represents the directory where you unzipped the installer, and will result in the console waiting `60 seconds` before giving up on a response from the WebLogic Server domain.
 
 or in `config.json`, add:
 ```
@@ -186,8 +186,8 @@ or in `config.json`, add:
 
 When changing network timeout settings, the primary impact will be the response time for Console threads, while the browser will show no data when a timeout occurs.  Examples of where timeouts may happen include requests where WebLogic experiences longer initialization or execution times such as for runtime monitoring actions of servers.
 
-## Disable host name verification in the connections to the WebLogic domain {id="hostname"}
-When using WebLogic demo trust to connect to the WebLogic domain, you may need to disable host name verification. Disabling host name verification causes the Remote Console to skip the verification check of ensuring that the host name in the URL to which a connection is made matches the host name in the digital certificate that the server sends back as part of the SSL connection.
+## Disable host name verification in the connections to the WebLogic Server domain {id="hostname"}
+When using WebLogic demo trust to connect to the WebLogic Server domain, you may need to disable host name verification. Disabling host name verification causes the Remote Console to skip the verification check of ensuring that the host name in the URL to which a connection is made matches the host name in the digital certificate that the server sends back as part of the SSL connection.
 
 {{% notice note %}}
 We do not recommend using the demo certificates or turning off host name verification in production environments.
@@ -237,5 +237,5 @@ or
 ```
 results in the HTTP session Cookie including the `SameSite` attribute with a value of `Lax`.
 
-## Connect to a WebLogic domain running on kubernetes {id="k8s"}
-One of the benefits of the WebLogic Remote Console is the ability to connect to, and manage, a WebLogic Server domain running on Kubernetes. For details about how to setup access to WebLogic Server domains running on Kubernetes, see [Use the Remote Console](https://oracle.github.io/weblogic-kubernetes-operator/userguide/managing-domains/accessing-the-domain/admin-console/) in the *WebLogic Kubernetes Operator User Guide*.
+## Connect to a WebLogic Server domain running on kubernetes {id="k8s"}
+One of the benefits of the WebLogic Remote Console is the ability to connect to, and manage, a WebLogic Server domain running on Kubernetes. For details about how to setup access to WebLogic Server domains running on Kubernetes, see [Use the Remote Console](https://oracle.github.io/weblogic-kubernetes-operator/userguide/managing-domains/accessing-the-domain/admin-console/) in the *WebLogic Kubernetes Operator User Guide*.

hugo/2.0/content/userguide/edit-domain-config.md

@@ -11,15 +11,15 @@ The domain configuration process in the WebLogic Remote Console is similar to th
 Configuration locks do not apply to WDT model files. As WDT model files are not connected to live domains, they do not require any locks to prevent conflicting changes. Additionally, you do not have to save *and* commit changes; once you save your changes, they are saved to the WDT model file.
 
 #### WDT model tokens {id="model_tokens"}
-When editing the domain configuration for a WDT model File, you can substitute model tokens instead of real field values. Model tokens are variables that you can enter into domain configuration settings. Rather than restricting a setting to a single value, the value will update according the variable.
+When editing the domain configuration for a WDT model file, you can substitute model tokens instead of real field values. Model tokens are variables that you can enter into domain configuration settings. Rather than restricting a setting to a single value, the value will update according the variable.
 
 There are several types of model tokens including variable tokens, file tokens, and so on. Model tokens follow this format: `@@TYPE:KEY@@`, where `TYPE` is the model token type and `KEY` is the variable value. For example, you could declare variable token by entering `@@PROP:ABCDE@@` into a field.
 
 See [WDT Model Tokens](https://oracle.github.io/weblogic-deploy-tooling/concepts/model/#model-tokens) for more information.
 
 ## Shopping cart {id="shopping_cart"}
 
-The Shopping Cart (equivalent to the Change List in the WebLogic Server Administration Console) holds all the pending changes for the current session in the WebLogic Remote console. In the shopping cart, you can see if any changes are pending, commit those changes or discard them entirely. If you installed the console extension, `console-rest-ext-1.0.war`, you can also see the specific changes you've made and the status of the lock in the Change Manager. Unfortunately, there is currently no support for removing individual items from the shopping cart.
+The Shopping Cart (equivalent to the Change List in the WebLogic Server Administration Console) holds all the pending changes for the current session in the WebLogic Remote Console. In the shopping cart, you can see if any changes are pending, commit those changes or discard them entirely. If you installed the console extension, `console-rest-ext-1.0.war`, you can also see the specific changes you've made and the status of the lock in the Change Manager. Unfortunately, there is currently no support for removing individual items from the shopping cart.
 
 The configuration change lock does not prevent you from making conflicting configuration edits using the same administrator user account. For example, if you obtain a configuration change lock in the WebLogic Remote Console, and then use the Administration Console or WebLogic Scripting Tool (WLST) with the same user account, you will access the same edit session that you opened in the WebLogic Remote Console and you will not be locked out of making changes with the other tools.
 
@@ -73,4 +73,4 @@ In most other cases, when you create a new MBean on a page, you are prompted to
 
 {{% notice note %}}
 When you configure a bean property that references another bean, you must first create the other bean. For example, if you want to assign Server1 to Cluster1, you need to create Cluster1 first, unlike in the WebLogic Server Administration Console where you can choose to create Cluster1 during server creation.
-{{% /notice %}}
+{{% /notice %}}